please recommend Books on Large Continuous Software-Development projects
August 16, 2014 7:15 PM Subscribe
I've been tossed into the deep end of a large continuous software-development project. Agile software development processes? Development, System Testing, Acceptance Testing and Production? Separated Presentation (Web) Tier, Application Tier, and Data Tier server environments? ITIL Best-practices?? What BOOKS do you recommend so I can get a handle on all this stuff?
Note: Although I would indeed appreciate any useful web pages and websites you suggest, what I'm really after is a recommendation of the BOOK(s) that you got the most useful information from, about this topic. Because I am so old-school, that I intend to read the dead-trees version, in my favorite comfortable chair.
Note: Although I would indeed appreciate any useful web pages and websites you suggest, what I'm really after is a recommendation of the BOOK(s) that you got the most useful information from, about this topic. Because I am so old-school, that I intend to read the dead-trees version, in my favorite comfortable chair.
Release it! is great: http://www.amazon.com/gp/aw/d/0978739213?pc_redir=1408078452&robot_redir=1
Also check out the 12 factor app: http://12factor.net
Both of these should serve as jumping off points for more information.
posted by askmehow at 5:02 AM on August 17, 2014
Also check out the 12 factor app: http://12factor.net
Both of these should serve as jumping off points for more information.
posted by askmehow at 5:02 AM on August 17, 2014
The Phoenix Project is being widely read around my company as an intro to these topics. I found it an easy and actually somewhat enjoyable read. The authors have a blog where they delve into these topics in a more non-fiction format and they also reference additional books there. Their post on more resources for implementing the concepts lists additional books to read.
posted by elmay at 5:36 AM on August 17, 2014
posted by elmay at 5:36 AM on August 17, 2014
While not a "how to" book, Dreaming in Code is an excellent recounting of an attempted rollout.
http://www.amazon.com/gp/aw/d/1400082471?pc_redir=1408114617&robot_redir=1
posted by qldaddy at 1:40 PM on August 17, 2014
http://www.amazon.com/gp/aw/d/1400082471?pc_redir=1408114617&robot_redir=1
posted by qldaddy at 1:40 PM on August 17, 2014
Best answer: I think you'd get better answers if you clarified what your role is on this project and what your background is in general. Your question history makes it look like you're basically a lead devops guy -- is that right? The things you're asking about are generally developer practices and not ops practices, so are you just asking to make it easier to work with developers? Or are you moving into more of a developer role and trying to figure things out?
posted by inkyz at 7:49 PM on August 17, 2014
posted by inkyz at 7:49 PM on August 17, 2014
Response by poster: inkyz, you introducing me to the term "DEVOPS" is the best thing that has happened to me in this AskMefi thread. Thank you! The word I was looking for is "DEVOPS".
posted by shipbreaker at 7:53 PM on August 18, 2014
posted by shipbreaker at 7:53 PM on August 18, 2014
This thread is closed to new comments.
posted by migurski at 12:20 AM on August 17, 2014