this post was submitted on 03 Feb 2024
316 points (96.5% liked)

PC Gaming

8576 readers
347 users here now

For PC gaming news and discussion. PCGamingWiki

Rules:

  1. Be Respectful.
  2. No Spam or Porn.
  3. No Advertising.
  4. No Memes.
  5. No Tech Support.
  6. No questions about buying/building computers.
  7. No game suggestions, friend requests, surveys, or begging.
  8. No Let's Plays, streams, highlight reels/montages, random videos or shorts.
  9. No off-topic posts/comments, within reason.
  10. Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)

founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 94 points 9 months ago (4 children)

Fast, cheap, reliable. You can have any two you want.

[–] [email protected] 21 points 9 months ago (1 children)

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?

[–] captainlezbian 15 points 9 months ago (2 children)

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.

[–] BluesF 11 points 9 months ago (2 children)

I just go for bad, slow, and expensive. This way everyone leaves me alone.

[–] Specal 10 points 9 months ago

Found blizzard.

[–] [email protected] 2 points 9 months ago

Smart, job security is a must now a days.

[–] [email protected] 3 points 9 months ago

so its stands true that what you make can be good, fast (as in be delivered quckly) and cheap and you can only have two like everything else, huh

[–] [email protected] 13 points 9 months ago (1 children)

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.

[–] [email protected] 17 points 9 months ago

In this context “fast” refers to speed of the system, not time to implement.

[–] SirQuackTheDuck 6 points 9 months ago

I'll take fast twice.

Double fast, yeah 😎

[–] [email protected] 6 points 9 months ago (1 children)

On spec, on time, on budget. Failure to meet those goals is a result of piss poor planning.

[–] fidodo 3 points 9 months ago* (last edited 9 months ago)

Those are all the same attributes, just the planned out version of it where the balance of speed, reliability and cost are decided upon ahead of time.