Nice overview, I like the theme of "broken environment". I might like to see a little more focus on that one theme so that it feels like it has a clear set of takeaways.
Working for a small (mostly front-end) dev shop, I never really understood exactly how much a fragmented dev environment can mess up development. Moving forward, I'll be making sure to put these techniques into practice to correct problems before they break things.
Jacob did a great job of clarifying the problem scenario and presenting the methods by which he sought to fix it. Helpful slide graphics were included. He also provided valuable information about what happened after his solution was implemented - how well the problem was solved, how well changes were received by the team, how he was able to keep things moving ahead. It was a great overview of not just how to go about fixing the problem, but what to expect after, and along the way.
I found the title of this talk strange and misleading, and the talk in general was not applicable to me. There was some very good points, in particular, the importance in fixing situations where environment bugs aren't caught in dev. But if the moral of the talk was that developers should spend a year setting up their environments, I very much disagree. The more detailed this talk got, the more convinced I became that the tasks of setting up dev environments like this should not be tasked to developers. But maybe that's just me.
Comments
Comments are closed.
Nice overview, I like the theme of "broken environment". I might like to see a little more focus on that one theme so that it feels like it has a clear set of takeaways.
Great depth. Made me realize that for as much planning I've put into our dev environment, there's a lot I've missed. Thanks, Jacob!
Great talk, Jacob. Matching dev to production is key! :D
excellent review of the process to bring a developer environment online.
Good talke
Great overview of the problems of getting dev and production to match, and real world examples of getting a system up and going.
Really helpful information about some of the pitfalls in getting a solid dev environment.
Interesting journey in building a dev enviroment.
Working for a small (mostly front-end) dev shop, I never really understood exactly how much a fragmented dev environment can mess up development. Moving forward, I'll be making sure to put these techniques into practice to correct problems before they break things.
Jacob did a great job of clarifying the problem scenario and presenting the methods by which he sought to fix it. Helpful slide graphics were included. He also provided valuable information about what happened after his solution was implemented - how well the problem was solved, how well changes were received by the team, how he was able to keep things moving ahead. It was a great overview of not just how to go about fixing the problem, but what to expect after, and along the way.
I found the title of this talk strange and misleading, and the talk in general was not applicable to me. There was some very good points, in particular, the importance in fixing situations where environment bugs aren't caught in dev. But if the moral of the talk was that developers should spend a year setting up their environments, I very much disagree. The more detailed this talk got, the more convinced I became that the tasks of setting up dev environments like this should not be tasked to developers. But maybe that's just me.