Please spare me from having to get in touch with that shit I wrote back then
-
I thought I had it worked out, how to sort of strike a balance so I can keep my focus intact and let it be helpful without wasting time constantly correcting its stuff or shying away from actually paying attention to the code. But I think my strategy of "let the LLM generate a bunch of vomit to get things started and then take on the correct and augmentation from a human standpoint" has let the overall designs at a high level get a lot sloppier than they used to be.
Yeah, you might be right, it might be time to just set the stuff aside except for very specialized uses.
Specialised domains are where LLMs really show how thoroughly they can hallucinate bullshit.
-
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.
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??
-
This post did not contain any content.
Had this multiple times. Reading code from 2 years ago and being like "what idiot wrote this" only to find out the culprit was me. Then the memories came back and I remember why the compromises were made. What I learned from that is not to judge people too much on their code. What you see is a combination of both their skill and also a whole bunch of necessary compromises for which you may not know the reason. Nowadays I don't get too annoyed if the code is a bit messy. As long as it's well tested and documented.
-
Had this multiple times. Reading code from 2 years ago and being like "what idiot wrote this" only to find out the culprit was me. Then the memories came back and I remember why the compromises were made. What I learned from that is not to judge people too much on their code. What you see is a combination of both their skill and also a whole bunch of necessary compromises for which you may not know the reason. Nowadays I don't get too annoyed if the code is a bit messy. As long as it's well tested and documented.
Yes — I think part of the lesson is to document the rationale and the compromises as much or more than the intended functionality.
-
This post did not contain any content.
That's scary as shit
-
This post did not contain any content.
I had a less experienced person with me looking at some code.
I pointed out that a particular section of code is shit; just bad form, hard to debug and generally unpleasant to work with. I noted that the person that wrote this didn't really know what they were doing, sure the code works and has been working for a long time, but this is not how we would do things.
They asked "wow, who wrote this?" I replied "it was me 13 years ago"; it is a great ice breaker, in a non-critical part of the system, new people realize we all have to start somewhere.
It also allows me to go over the standards we use, why we use them and how to simplify debugging.
-
And this is why you comment your code
It's not that it's purpose or implementation is unclear, it's how bad I was at coding
2 years6 months2 monthslast week -
I had a less experienced person with me looking at some code.
I pointed out that a particular section of code is shit; just bad form, hard to debug and generally unpleasant to work with. I noted that the person that wrote this didn't really know what they were doing, sure the code works and has been working for a long time, but this is not how we would do things.
They asked "wow, who wrote this?" I replied "it was me 13 years ago"; it is a great ice breaker, in a non-critical part of the system, new people realize we all have to start somewhere.
It also allows me to go over the standards we use, why we use them and how to simplify debugging.
That's a great approach, hope you don't mind I'm gonna copy
-
That's a great approach, hope you don't mind I'm gonna copy
Happy to help
-
This post did not contain any content.
Fourth panel should just be him dead. I'd have already pulled my hand out
