4 ms·
interestingly, your examples revolve around making things faster. Which basically is understood as : "well, we've already too much pressure and our PM wants to
by wiz21c 7y ago
interestingly, your examples revolve around making things faster. Which basically is understood as : "well, we've already too much pressure and our PM wants to put even more pressure on us". Going faster (or being more efficient) always mean being able to take more work.
- scarejunba 7y agoNo, it doesn't. For instance, at a place I worked at, we wanted to build a particular ad tech product to reinforce strength in a different area. The correct answer to "how do we make this faster" was "buy the guys who do it and then integrate via a bunch of CSVs on GCS and some RPC". We canned our forays into the space and bought them. Less work for all the engineers and data scientists. More work for M&A but they like doing that so it's not upsetting. At a more granular level, in a different project, the answer to "how do we develop this faster" was "lose these requirements, and just use AWS services for those". Less work in total.
- deanCommie 7y agoThe horse/car example isn't really about going faster. It's an example of hitting the limit of a certain technology, saying any further improvements are "impossible", while not recognizing that a "better horse" might just not be a horse at all. It's not a metaphor for faster project delivery, but a meaningful technological difference that someone may not be able to see.