Learn More
Resend Email
9
Bacontaskmaster
7y

Why is it that every god damned time, i ask questions until i have a clear view of a clients project and flow. I present them this flow. They OK it and everything. I build said flow in an app. And then at the end of the line i always end up with a shit codebase because i designed it to be like the documented flow, but changes were being added (and obviously paid for) all the time. I made such a neat little app. And now it all gone to shit.

Is this just me? Am i that bad at programming or what?!

Stop changing half of the app functionality after the original design is created!

undefined

changes
Favorite
Ranter
Comments
  • 1
    7y
    Of course its not cool to get change requests in all the time, but a good programmer should be able to keep the codebase tidy. We get changes in at a daily basis but that doesn't harm the health of our codebase
  • 3
    7y
    Clients will never stop doing that, you'll have to learn to accept, that's all what agile is about !
  • 2
    7y
    You might want to separate your projects in multiple parts.

    Work with features/functions. A client can only add or remove features from his wish list. A change only means a removal of one feature and adding another.

    This way you also keep your code clean. A feature is a new branch and most likely is/are complete new classes.

    The most difficult part is to "grow balls" and tell your clients how it's going to work. But you will see that clients actually will listen.
  • 1
    7y
    @theZorgEffect maybe it is a combination of coding and not using object oriented coding (due to unity3d's way of doing things)
    It usually starts neat. Hut some changes go against the original designed flow, and thus have to be either hacked in or rewritten, and rewriting obviously takes too long for the client. Etc. Etc.
Related Rants
devRant © 2021 Hexical Labs LLC
Privacy Policy  |  Terms of Service
Add Comment