4 ms·
I also don't trust code from stackoverflow, colleagues, or even code I had written myself in the past. Is helpful to always be skeptical of code and try to get
by jaredsohn 2y ago
I also don't trust code from stackoverflow, colleagues, or even code I had written myself in the past.
Is helpful to always be skeptical of code and try to get an understanding of it.
Another way I think of it is I find it easier to revise than to write (both in English and code). So when I write something I just try to get my ideas out there and then skeptically reread it and recompose. LLMs let me just speed up that process.
- mindcrime 2y agoor even code I had written myself in the past. Aaawwww hellz no. I hate looking at my old code. I've had too many of those surreal experiences where something breaks, I start looking at how to fix it, and am suddenly stunned to realize "this could never have worked in the first place." There's one or two of those I'm still puzzling over, decades later. :-(
- zer00eyz 2y agoI have been writing go for a decade now. Good go is like brutalist architecture. Strip out all the cute, the smart the stupid coder tricks. Write ugly, blocky, verbose, spelled out, functional code. Test the ever loving shit out of it. Go is fast enough that if your going back to fix a "performance problem" you either did something head smackingly stupid (we all have) or you have a real bottleneck and it's time to roll up your sleeves and write that elegant solution. I tend to revisit code more often to add features or deal with edged case bugs than anything else. That clear and functional code without any magic is a win. Edit: you can do the above with almost any language but those that choose packages over standard libs make it HARD.