this is a server basterdization of “Good, Fast, Cheap” regarding producing just about anything I’m guessing, which tends to hold true in the real world quite well, yes?
As an engineer yeah, but honestly it’s usually pick one to prioritize, one to strive for, and one to ignore.
We can get it out fast, and it can be not bad but pretty expensive or it can be pretty cheap but not good. If we get it good we can try to do it cheaply and take our time, or we can try to do it quickly and it’ll be expensive.
Fast, cheap, reliable. You can have any two you want.
this is a server basterdization of “Good, Fast, Cheap” regarding producing just about anything I’m guessing, which tends to hold true in the real world quite well, yes?
As an engineer yeah, but honestly it’s usually pick one to prioritize, one to strive for, and one to ignore.
We can get it out fast, and it can be not bad but pretty expensive or it can be pretty cheap but not good. If we get it good we can try to do it cheaply and take our time, or we can try to do it quickly and it’ll be expensive.
I just go for bad, slow, and expensive. This way everyone leaves me alone.
Found blizzard.
That works for some contexts, but no amount of time can get you both total reliability and low costs, so in this case it’s pick one.
In this context “fast” refers to speed of the system, not time to implement.
On spec, on time, on budget. Failure to meet those goals is a result of piss poor planning.