The Architecture of Open Source Applications

http://www.aosabook.org/en/index.html so called AOSA book. " Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another’s mistakes rather than building on one another’s successes. Our goal is to change that. In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program’s major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think." ...

The Architecture of Open Source Applications

http://www.aosabook.org/en/index.html so called AOSA book. " Architects look at thousands of buildings during their training, and study critiques of those buildings written by masters. In contrast, most software developers only ever get to know a handful of large programs well—usually programs they wrote themselves—and never study the great programs of history. As a result, they repeat one another’s mistakes rather than building on one another’s successes. Our goal is to change that. In these two books, the authors of four dozen open source applications explain how their software is structured, and why. What are each program’s major components? How do they interact? And what did their builders learn during their development? In answering these questions, the contributors to these books provide unique insights into how they think." ...

Assessing Technical Risks for Startups – New Tech Leader Series | kate{mats}

http://katemats.com/assessing-technical-risks-for-startups-new-tech-leader-series/ Good check list from Kate Matsudaira.

Assessing Technical Risks for Startups – New Tech Leader Series | kate{mats}

http://katemats.com/assessing-technical-risks-for-startups-new-tech-leader-series/ Good check list from Kate Matsudaira.

In praise of “boring” technology | Spotify Labs

http://labs.spotify.com/2013/02/25/in-praise-of-boring-technology/ More often than not, the right tool for the job is piece of software that has been around for some time, with proven success. One example would be writing a backend service in Java or Python instead of Go or Node.JS. Another example would be storing data in MySQL or PostgreSQL instead of MongoDB or Riak.

In praise of “boring” technology | Spotify Labs

http://labs.spotify.com/2013/02/25/in-praise-of-boring-technology/ More often than not, the right tool for the job is piece of software that has been around for some time, with proven success. One example would be writing a backend service in Java or Python instead of Go or Node.JS. Another example would be storing data in MySQL or PostgreSQL instead of MongoDB or Riak.

HN's favorite tech talks

http://bl.ocks.org/ricardobeat/raw/5343140/ Collection of great takes from Hacker News/YCombinator ppl. Full discussion https://news.ycombinator.com/item?id=5511466

HN's favorite tech talks

http://bl.ocks.org/ricardobeat/raw/5343140/ Collection of great takes from Hacker News/YCombinator ppl. Full discussion https://news.ycombinator.com/item?id=5511466

Developer Productivity Report 2012: Tools, Tech, Devs and Data | zeroturnaround.com

http://zeroturnaround.com/blog/developer-productivity-report-2012-java-tools-tech-devs-and-data/ We’re not much for fanfare here at ZeroTurnaround, but this is our most ambitious report that we’ve ever created. This year, over 1800 respondents shared their take on “the developer life” with us, with 1100 Java-focused surveys completed.

Developer Productivity Report 2012: Tools, Tech, Devs and Data | zeroturnaround.com

http://zeroturnaround.com/blog/developer-productivity-report-2012-java-tools-tech-devs-and-data/ We’re not much for fanfare here at ZeroTurnaround, but this is our most ambitious report that we’ve ever created. This year, over 1800 respondents shared their take on “the developer life” with us, with 1100 Java-focused surveys completed.