Rating:
Author: Brian W. Fitzpatrick
ISBN : B008EKF87S
New from $9.99
Format: PDF, EPUB
Download file now Free Team Geek: A Software Developer's Guide to Working Well with Others [Kindle Edition] for everyone book 4shared, mediafire, hotfile, and mirror link
In a perfect world, software engineers who produce the best code are the most successful. But in our perfectly messy world, success also depends on how you work with people to get your job done.
In this highly entertaining book, Brian Fitzpatrick and Ben Collins-Sussman cover basic patterns and anti-patterns for working with other people, teams, and users while trying to develop software. This is valuable information from two respected software engineers whose popular series of talks—including "Working with Poisonous People"—has attracted hundreds of thousands of followers.
Writing software is a team sport, and human factors have as much influence on the outcome as technical factors. Even if you’ve spent decades learning the technical side of programming, this book teaches you about the often-overlooked human component. By learning to collaborate and investing in the "soft skills" of software engineering, you can have a much greater impact for the same amount of effort.
Team Geek was named as a Finalist in the 2013 Jolt Awards from Dr. Dobb's Journal. The publication's panel of judges chose five notable books, published during a 12-month period ending June 30, that every serious programmer should read.
Books with free ebook downloads available Free Team Geek: A Software Developer's Guide to Working Well with Others [Kindle Edition]
- File Size: 3582 KB
- Print Length: 194 pages
- Page Numbers Source ISBN: 1449302440
- Simultaneous Device Usage: Unlimited
- Publisher: O'Reilly Media; 1 edition (July 13, 2012)
- Sold by: Amazon Digital Services, Inc.
- Language: English
- ASIN: B008EKF87S
- Text-to-Speech: Enabled
X-Ray:
- Lending: Not Enabled
- Amazon Best Sellers Rank: #59,633 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
- #6
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Project Management - #17
in Kindle Store > Kindle eBooks > Business & Investing > Industries & Professions > High-Tech - #27
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Development
- #6
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Project Management - #17
in Kindle Store > Kindle eBooks > Business & Investing > Industries & Professions > High-Tech - #27
in Kindle Store > Kindle eBooks > Computers & Technology > Programming > Software Design > Software Development
Free Team Geek: A Software Developer's Guide to Working Well with Others
Software development teams can often be repositories of really intelligent people who have no understanding of how to function in a team environment. The myth of the nerd buried alone is his parents' basement hacking up software actually has some basis in fact, sadly - not that engineers are literally working from their parents' basement, but the mentality often parallels one engendered from that environment. I work for Oracle, a very mature company that pre-dates the revolution in software development teams, started in the 90s dot-com boom but perfected by the likes of Google, Facebook, Twitter, etc. in more recent years. The work environment I find myself in is what I would, as kindly as I can, describe as 'old school'. I've heard tale of how engineering teams at these other types of companies function, and now, with Ben and Fitz's book, I finally have a full-fledged view into how a well-oiled team works.
The authors very methodically take the reader through what are the elements of a productive team: from how engineers should comport themselves, to how leaders can build and maintain the health of their teams, dealing with people who are working against you, navigating the organizational constraints (and, often, *re*straints), all the way through how to treat users of your software. No stone is left unturned, not even ones you perhaps wish *would* have been ignored (for example, how to handle nice but under-performing team members).
As a 17 year veteran of the software development industry, I found many of Ben and Fitz's stories intimately familiar, and I've stumbled my way onto a couple of their solutions through my own trial and error.