Programmer Humor

32715 readers

658 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

Posts must be relevant to programming, programmers, or computer science.
No NSFW content.
Jokes must be in good taste. No hate speech, bigotry, etc.

founded 5 years ago

MODERATORS

[email protected]

722

Got no time to code (sh.itjust.works)

submitted 6 months ago by [email protected] to c/[email protected]

96 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 39 points 6 months ago* (last edited 6 months ago) (1 children)

Problems caught early are much easier to fix than problems caught later. This applies to any project (I'm not a programmer, but an engineer in the traditional sense).

Just "doing it" without coordination and review is a great way to waste a bunch of effort down the line with re-work.

Edit: typo

[–] [email protected] 7 points 6 months ago

While i agree with the principal statement, this also requires two things to work:

First: The scope should be defined properly, so people can contextualize what they are actually doing and reviewing.

Second: If the scope is subject to change, or parts of it are unclear, there needs to be room to consider, develop and try different variants

This is were good management is crucial, which includes giving breathing room at the start. What we tend to experience is the expectation of already good detailed results, that can be finalized but still work if things change significantly.