5 ms·

Hi, I wrote the article. I agree that I may have been too light on the details about why different technologies should be chosen. Tbh though that is a bit tange

Hi, I wrote the article. I agree that I may have been too light on the details about why different technologies should be chosen. Tbh though that is a bit tangential to the point. My point is that it benefits the developer to branch out and learn a diverse set of things, regardless of the details.

chris11 9y ago
That's a fair point that I agree with. My comment was more about the need for real analysis when making large architectural decisions. Experimenting with new tech in small projects is good, and fun. But I've worked at places that have made major investments new tech, sometimes based on small prototypes, and then ran into unexpected issues that were very frustrating after we were already committed.
scarface74 9y ago
Do you need to learn a diverse set of things are just be aware of a diverse set of things? For instance, we just moved to AWS. I am not going to spend hours upon hours learning in depth all of AWS's services. I did watch a few videos and subscribe to the AWS podcast so I could be aware of the different services to know what they have. When there is a business need to implement X, I'll know what's out there and then do a proof of concept to see if what AWS has fits our needs. Learning best practices transcend technology. We've had "consultants" come into the company where I'm the dev lead and question my choices of technologies. I ask them two questions - what's the business case and what industry standard best practices are we not following?
jimbokun 9y ago
"My point is that it benefits the developer to branch out and learn a diverse set of things, regardless of the details." Yes, but do you have any evidence that can lead to "10x" productivity, even anecdotally?