An irrelevant but interesting take is that this applies as an analogue to a lot of stuff in electronics related space.
It is harder to receive data than to transmit it, because you need to do things like:
match your receiver’s frequency with that of the transmission (which might be minutely different from the agreed upon frequency), to understand it
know how long the data will be, before feeding into digital variables, or you might combine multiple messages or leave out some stuff without realising
this gets even harder when it is wireless, because now, you have noise, which is often, valid communication among other devices
Getting back to code, you now need to get in the same “wavelength” as the one who wrote the code, at the time they wrote the code.
I weirdly love reading code and figuring out what it’s doing. Debugging is cathartic.
It might take a while and I might be cussing up a storm saying, wtf is this shit? Why the fuck would you do it this way? Why the fuck did you make this convoluted for no reason?
Right now it’s unfucking some vibe coded bs where instead of just fixing an API to get the info we needed accurately, it’s trying to infer it from other data. Like, there is a super direct and simple route, but instead there are hundreds of lines to work around hitting the wrong endpoint and getting data missing the details we need.
Plus letting the vibe add so much that is literally never used, was never needed, and on top of that returns incorrect information.
the “target” is to get useful software out. The ai is the tool. In this example, the ai is the gun. It is the tool used to achieve the goal.
Anyone can make an improvised hammer. Stick a rock or a piece of metal on a stick. But that doesn’t make them carpenters, even though they made their own tools.
if they build software using mainly ai generated code, then they are a bad coder
deleted by creator
exactly, you can only really verify the code if you were capable of writing it in the first place.
And it’s an old well known fact that reading code is much harder than writing it.
An irrelevant but interesting take is that this applies as an analogue to a lot of stuff in electronics related space.
Getting back to code, you now need to get in the same “wavelength” as the one who wrote the code, at the time they wrote the code.
i like the analogy
I weirdly love reading code and figuring out what it’s doing. Debugging is cathartic.
It might take a while and I might be cussing up a storm saying, wtf is this shit? Why the fuck would you do it this way? Why the fuck did you make this convoluted for no reason?
Right now it’s unfucking some vibe coded bs where instead of just fixing an API to get the info we needed accurately, it’s trying to infer it from other data. Like, there is a super direct and simple route, but instead there are hundreds of lines to work around hitting the wrong endpoint and getting data missing the details we need.
Plus letting the vibe add so much that is literally never used, was never needed, and on top of that returns incorrect information.
enjoying it is a different issue. You probably enjoy it because it’s more difficult, which is perfectly valid reasoning
Exactly how I feel about it as well.
Even if they build the AI doing it from scratch, all by themselves?
yes. Because that would still mean they didn’t code the app.
“killing is bad!” “but what if the murderer 3d printed his own gun?”
More like: “killing is bad” “but what if the ‘murderer’ designed, build and produced their own target?”
You can’t kill a robot, so it isn’t killing.
the “target” is to get useful software out. The ai is the tool. In this example, the ai is the gun. It is the tool used to achieve the goal.
Anyone can make an improvised hammer. Stick a rock or a piece of metal on a stick. But that doesn’t make them carpenters, even though they made their own tools.