this post was submitted on 06 Jun 2024
477 points (89.3% liked)

Technology

60033 readers
2947 users here now

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


founded 2 years ago
MODERATORS
 

We all knew it

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 19 points 6 months ago (3 children)

I witnessed a huge number of failed projects in my 25-year career. The cause was almost always the same: inexperienced developers trying to create a reusable product that could be applied to imagined future scenarios, leading to a vastly overcomplicated mess that couldn't even satisfy the needs of the original client. Made no difference what the language or framework was or what development methodology was utilized.

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

I feel like that's the same underlying issue: The requirements are not understood upfront.

If a customer cannot give you any specific information, you cannot cut any corners. You're pretty much forced to build a general framework, so that as the requirements become clearer, you're still equipped to handle them.

I guess, the alternative is building a prototype, which you're allowed to throw away afterwards. I've never been able to do that, because our management does not understand that concept.

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

I feel like that’s the same underlying issue: The requirements are not understood upfront.

Actually on most of these failed projects the requirements of the original customer were pretty clear. But the developers tried to go far beyond those original requirements. It is fair to say that the future requirements were not well understood.

the alternative is building a prototype, which you’re allowed to throw away afterwards

Lol I've done many prototypes. The problem is that management sees them and says "oh, so we're finished with the project already? Yay!"

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

I've seen a lot of contractors over promising timelines too. "No matter how hard you push and no matter what the priority, you can't increase the speed of light."

But yeah exactly.

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

Preach brother!