7
jchw
7y

By always striving to do better each time. Making code less sloppy every time I write GL code. Better performance everytime I write an algorithm. Lower memory usage every time I write application state. Learning a new trick for an old problem, one at a time.

Learning best practice in one go is impossible, but taking it a bit at a time makes things more reasonable.

Comments
  • 1
    One caveat though which I have learned is either you need to own your code completely or the team needs to understand too.

    I feel like the nanny on my team, whenever things blow up, I'm the one cleaning them up. Why do they blow up though? because of shitty code....
  • 1
    @allanx2000 in my experience it is totally a culture thing. I've struggled with this exact problem and it seems possible that with time and enough effort, things are tilting toward higher quality code and more experienced devs. I think that it's not only good for satisfying your urges to keep code clean but for the team as a whole.
  • 0
    @jchw banks seem to think anyone will do though... Just hire whoever is cheapest... And there is no culture...
Add Comment