3 ms·
I enjoyed this post quite a lot. I'd like to see a companion post on specifically engineering time-wasters - e.g. did you find that evaluating new technologies
by javajosh 15y ago
I enjoyed this post quite a lot. I'd like to see a companion post on specifically engineering time-wasters - e.g. did you find that evaluating new technologies to solve problems to be an unnecessary risk, or a pleasant surprise that ended up saving time and effort in the long run? What about the tension between "one size fits all" tools and tools that are so specialized that you need a tool to select the right tool?
- erichocean 15y agoDeveloping general solutions to specific problems is an engineering timewaster, in my experience. Using complicated tools and tooling where simpler tooling would cover your actual needs with less effort. Developing a solution that attempts to meet all needs with a lot of effort, instead of developing a product that meets the needs that can be effectively addressed. I'm guilty of the last one, so what I do is develop two solutions: 1. a solution that actually "solves" the problem with engineering (the "right" way to do it), and 2. a second approach that is an order of magnitude (sometimes a few orders) easier to implement that partially solves the problem, but requires a bit of management to stay "solved" over time. Engineers seem to prefer engineering solutions (go figure), but especially in business, a combination of engineering and management is usually the most cost-effective approach.
- kylebrown 15y agoThe way I see it, the time cost/benefit curve of evaluating new technologies and other research-like activities is considerably risky. But there's also a definite big fat tail of rewards, however elusive..