![]() I never managed to reach "right" in my entire life anyway. Wish I told my young self to stop being so obsessed with doing things right or even working on important problems. ![]() ![]() Don't even have a register form, I hard coded them :) I show that to my friends that were asking me wtf I was doing with this, and 4 people asked me an account, one a trial for doctors for addiction programs (!). I just splatted a wall of tailwind regurgitated by chatgpt and pupetted by HTMX. Took me half a decade to add encryption to it, because symlinking the file from a veracrypt container was sufficient and required little work.Ģ months ago I wanted a timer to top up a time budget when I do sport, and consume it when I play video games (. I needed a cli for totp years before any existed, I just fired Python and dumped, in clear text, the seeds in TOML. I've been using that terrible stack of forms for 10 years, and it did the job. I didn't, I just used django-admin and called it a day instead of trying to craft some slick UI. I wanted to code a contact software because all the ones I tried didn't do what I wanted. ![]() He didn't write unit tests, but he always tested everything manually again and again by playing with the result like a kid. He didn't sweat the small stuff, he worked more, way more, as well. I noticed how in the end he accomplished more than I did. Half of the time he's not sure what the code is really doing. I worked with him on a lot of fun projects, because we get along well, and he really doesn't know what he is doing, copy / pasting all other the place, no archi, no design, bad naming. Learned that by coding with a friend I considered a terrible coder. TLDR (by me): Don't share best practices, share your experience and let others draw their own conclusions from that. Or I might instead feel like "oh no, I'm going to do the best practice you recommended, because I do not want that thing to happen to me". Maybe I feel like - the computer did that to you? That's okay, I can deal with that problem, I don't mind. The reason I prefer stories to best practices is if I know the story about how the bash hurt you, I can take that information and decide for myself how I want to proceed. If someone has a strong opinion like "nobody should ever use bash", I want to hear about the story! What did bash do to you? I need to know. > One way I see people kind of trying to share terrible things that their computers have done to them is by sharing "best practices".īut I really love to hear the stories behind the best practices! A great talk overall, but I particularly liked this bit about "best practices" which I think describes the issue beautifully. There was a talk by Julia Evans recently shared here on HN. I find I keep coming back to maintain and improve the fun projects, but the serious projects languish and die once I move on. Ironically, the code I'm most proud of has often ended up being the stuff I did for fun. Its funny - over the years I've written a lot of code to solve Serious Problems and I've written a lot of code on a whim, to scratch my own itch. I got the first data syncing yesterday! Its really exciting. And at the moment I'm writing a simple CRDT based local first database. I've recently written my own protobuf-style library for binary serialization (to try out some fun ideas around schema evolution). So instead, I'm trying to have a lot more fun with the code I write and I'm finding I've been writing way more code. Life is for living, and I squeeze the fun out of software when I try too hard to do it "right". I went to clown school recently (thats a whole story) and I realised I've been focusing way too much on trying to get projects "right" or "do them well".
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |