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

treasure!

Easy learning to write better code, naturally fixing it later on as you revisit it and realise the mistakes you did!

When you revisit old code and it's better than what you write today

that's why every developer is taught to comment their code. and why a handful of _good_ developers sometimes actually do so.

@tosensei wow guys we have Sherlock over here

Trying to make sense of code you wrote yesterday

@jestdotty or, what fuckin idiot wrote this?!

And when you don‘t believe git telling you that you wrote it.

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.

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.

@tosensei I hate finding code comments in my old code, too

I don't wanna read all that

I don't trust my old code any more than I trust someone else's code I guess. which is kind of interesting

@int32 a cute idiot 🥺

meeeee! 😊
I AM THE JUNIOR NOW

@retoor why was it better half a year ago?

@cafecortado wow i never saw that you're paying for devRant++. I didn't think that even now some people would do it.

@SidTheITGuy actually I stopped paying months ago but devRant is so unmaintained that the subscription status doesn't update

@cafecortado seriously though what happened to devrant? did devs die or something?