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.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
No game suggestions, friend requests, surveys, or begging.
No Let’s Plays, streams, highlight reels/montages, random videos or shorts.
No off-topic posts/comments, within reason.
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.)
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.
Smart, job security is a must now a days.
Found blizzard.
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