7

Why are most projects only fun at the beginning? I feel like there should be a "first half" and a "second half" during development.

So if I have worked the whole of first half someone else should work the other half with full bar and zeal just like a football match because honestly most times I feel like I'm gonna die towards the end of the project hoping for another developer to come on as a substitution.
However, in this case instead of going to seat on the bench after being substituted, I am willing to play another match immediately.

Comments
  • 5
    My interpretation: You like doing the fun/challenging parts, but it stops being fun when the puzzle is solved or novelty wears off and then you're left with the boring parts. Probably quite normal and not an issue if you can manage it, i.e. actually finish things.
  • 5
    If you don't like doing maintenance and refactoring, projects become boring and annoying as technical debt piles up.
  • 2
    I feel like this doesn't apply to me. Probably mostly because size of projects. Also using new technologies helps much. Last three projects were finished in 1-2 months (relatively small microservices). So, I guess size of the project increases your likeliness to get bored because tasks will eventually get repetetive.

    @Oktokolo yeah also this. I like refactoring. Seeing 0 technical debts and 95%+ coverage on sonar feels awesome
  • 3
    "He looks at the fire, looks at the fire extinguisher, and thinks for a minute, says "Ah! A solution exists!" and goes back to work."

    ...the fun part is often in figuring out "how" and not in implementing and maintaining the solution
Add Comment