3 ms·
In my engineering days there was a saying: you can have it quick and cheap and high quality, but you can only have 2 of those 3. Spunss like you work somewhere
by LatteLazy 6y ago
In my engineering days there was a saying: you can have it quick and cheap and high quality, but you can only have 2 of those 3.
Spunss like you work somewhere quick and cheap. That's not wrong per se. If lives depend on the outcome, you need quality. But I worked in plenty of financial places that were quick and cheap. Especially back office.
Ask yourself: would the organisation be better off if we were higher quality BUT it meant we were slower or more expensive. If speed is more important, welcome to spaghetti code land.
- UK-Al05 6y agoIt not quick though. All of these things their missing allows you iterate fast.
- karatestomp 6y agoSkipping tooling & processes below a certain (not very low) point isn't doing it "cheap and fast". It's saying "I want you to build my house but I want it to be cheap so don't buy any more hammers, it's too much money and we can't afford the time for you to run to the hardware store, just all share the one hammer you already have". It's doing it cheap (but actually expensive) and slow and low-quality.
- LatteLazy 6y agoYou really want to build that house and I respect that, but the client just wants a tent and the hammer budget is zero. And since a storm is 10 minutes away they're not wrong...
- ju-st 6y agoAnd you can build a tent quick, cheap and fast. Getting customers to tell you want they really need is the silver bullet.