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.

[–] Jankatarch@lemmy.world 4 points 2 days ago* (last edited 2 days ago) (2 children)

Yeah but surely I should have at least thought there is a better way.

When I was making my first python project (a caesar cypher) I did not know about loops in general.

But while I did not know the concept of loops, I did deduce functions from how main() is being used. Big mistake.

Entire thing was one big recursion.

[–] PhilipTheBucket@piefed.social 6 points 2 days ago

Yeah, that sounds about right lol. All my python projects for years were basically writing C in python. It actually took me all the way up until I got to look at the code ChatGPT likes to generate that I learned idiomatic python. My first database project was based on the Unix philosophy, where everything was strings (no ID keys, no normalization), because Unix is good.

The client wasn't happy when they looked at the DB code lmao. Whatever, it worked, they still paid us and I didn't do it again.

load more comments (1 replies)

load more comments (9 replies)