2 ms·
I'd say pick mostly boring technologies but step out of your comfort zone once in a while. That way you take on some risk but not a lot. Worst case you have to
by jillesvangurp 6y ago
I'd say pick mostly boring technologies but step out of your comfort zone once in a while. That way you take on some risk but not a lot. Worst case you have to change your plan but you always learn something. Best case your bets pay off and you end up with something that provides you some benefits. And you learn something.
- greenkey 6y agoThis is good advice. Another thing to consider is cost-to-benefit ratio. If you don’t know cost, first look at: Product costs: free < one-time cost < recurring cost or recurring “one-time” costs Resource alignment costs: (Re-)hiring + severance + knowledge lost or transferred to competitors Refitting and development costs: converting or re-writing code + (re-)training + architectural changes + design changes Time + impact to other initiatives and maintenance Don’t stop after costing! Then listen to the perceived benefits or need again, being careful to communicate and discuss the perceived costs, so that those selling the idea within the company understand, because if they don’t, their good idea will be poor morale fodder later. This is much quicker and easier than it seems. If you still haven’t convinced the elements within the company to back down on their idea, and you’ve done a good job listening and considering their points, then either those elements are onto something or they’re “on something” (drinking the kool-aid). Make your decision.