Usually the first project when I'm learning how to use some new language or environment is super-shitty. I can tell it's very bad, usually I don't like interacting with it if I have to make changes, but it's still not overly painful. It's just bad code. And that one exception aside I generally like looking at my code.

[–] corroded@lemmy.world 21 points 2 days ago (2 children)

I think age of code plays a big part. 2 years ago: Yeah, I could do better, but it's workable. 15 years ago: Delete everything and just start from scratch.

[–] PhilipTheBucket@piefed.social 10 points 2 days ago* (last edited 2 days ago) (1 children)

IDK, I just popped open a project from 10 years ago and it's perfectly clean, it's actually better than some of my modern code because it's not LLM-ified to save time.

I think it has a lot more to do with whether it was made in that "kind of crappy IDK what I'm doing" phase of programming. Some of your old stuff is going to be in that category sure. As long as you're out of that, however long it took you to get there or however far away it was in time, your code should be good.

[–] black_flag@lemmy.dbzer0.com 12 points 2 days ago

it's actually better than some of my modern code because it's not LLM-ified to save time.

Hmm that seems like an indication you're rushing things and maybe ought not do that?? 🤦

load more comments (8 replies)