6
sjwsjwsjw
17h

trying to make sense of code you wrote more than half a year ago

Comments
  • 3
    treasure!
  • 2
    Easy learning to write better code, naturally fixing it later on as you revisit it and realise the mistakes you did!
  • 2
    When you revisit old code and it's better than what you write today
  • 1
    that's why every developer is taught to comment their code. and why a handful of _good_ developers sometimes actually do so.
  • 1
    @tosensei wow guys we have Sherlock over here
  • 3
    Trying to make sense of code you wrote yesterday
  • 5
    @jestdotty or, what fuckin idiot wrote this?!
  • 3
    And when you don‘t believe git telling you that you wrote it.
  • 2
    Luckily, I've worked with so many old code bases that comments mean nothing to me, and I just look for the thing I want to change and work from there.
  • 0
    Well, my code quality was way better a half year ago 😂 If the structure of your project is OK, is more important than code quality imho. Code graded a six is good. Higher than eight is waste of money and time. Sometimes when I see a piece of code that just doesn't feel right, i select that source in vim and tell it to refractor and move on. When it's just a smal piece, it's mostly correct.
Add Comment