As developers we have a unique advantage over everybody else dealing with the way AIgen is revolutionizing careers:
Everybody else is dealing with AIgen is suffering the AI spitting out the end product. Like if we asked AI to generate the compiled binary instead of the source.
Artists can't get AIgen to make human-reviewed changes to a .psd file or an .svg, it poops out a fully formed .png. It usurps the entire process instead of collaborating with the artist. Same for musicians.
But since our work is done in text and there's a massive publicly accessible corpus of that text, it can collaborate with us on the design in a way that others don't get.
In software the "power of plain text" has given us a unique advantage over kinds of creative work. Which is good, because AIgen tends to be clumsy and needs guidance. Why give up that advantage?
But you will also fail to keep the comments and code synchronized, and the comment will at some point no longer describe why the code is doing whatever it does
Which is why you're reviewing changes. I haven't memorized what every line of code does, if it was worth commenting then it was confusing-enough that it needed the comment and so I'll read the comment to make sense of the code being changed. If I don't read the comment that means the comment was too far from the confusing code.
Alternately, you can say the same about informative variable names or informative function names. "If I change the function then the name is no longer accurate". You don't say that because function names and variable names are short and clear and are close to the problem at hand. Do the same with comments.
Which is why the copilot hyper-verbosity is harmful. Comments need to be terse so your eyes don't filter them out as noise.
Honestly the aggressive verbosity of github copilot is half the reason don't use its suggested comments. AI generated code comments follow an inverted-wadsworth-constant: Only the first 30% is useful.
There's some repos I'm unashamedly keeping alive with Claude alone and he gets co-authorship - basically stuff in "maintenance mode" that I still use that I've forked and had Claude drag it into 2026
A quick PR where I've found the bug myself in the code, and ask Claude to write the fix because it's faster, and verified it - I don't include Claude's co-authorship.
Claude is not a person and AI doesn't gain authorship let alone copyright.
Unless you literally vibe coded it, Claude is just a tool. This is the equivalent of Apple appending "Sent from my iPhone" as a signature to outgoing emails. It's advertising tool use, not providing attribution. The intent isn't to disclose that AI was used in creating the code, the intent is to advertise the AI product.
Hmm... It's an interesting question: at what point, in a conversation, document, image, story, does human authorship end and AI authorship begin? How would you know? Is it a tell tale or is it advertising?
> Unless you literally vibe coded it, Claude is just a tool.
Stop with the selective bias, two are birds of the same feather, they are using a "tool" to write the code for them from whatever (questionable) mashed up source they are trained from, in the same way someone is using AI as a "tool" to fabricate their curriculum and cheat a job
> The intent isn't to disclose that AI was used in creating the code, the intent is to advertise the AI product
That is a wild mental gymnastic to justify dishonestly submitting code you didn't write (or own) as yours. It has nothing to do with advertisement but proper attribution, you know it.
It's only dishonest not to include Claude in commit/PR attribution if it's also dishonest not to include StackOverflow, or VSCode, or VIM, or Windows, or any of the other tools you used to complete the work!
That's a so invalid analogy, editors are effectively tools just like as a hammer because they require constant human input to produce something, the human is in constant control over the whole production process so they don't need to give attribution to the individual tools they used to build a house...
Unlike a black magic box where you just tell it to build something and it does all the production for you while you sit back.
I'm curious - for power consumption, considering that you can get RaspPi products for so cheaply, is a discarded laptop more or less impactful on your electrical bill than a RaspPi?
Like is the "free" laptop going to cost you more in the long-run then a nice little power-sipping ARM like a Pi5? Or do you need those extra operations-per-second that the more power-hungry x86 CPU gets you?
Laptop/desktop wattage varies with processor and peripheral load. Unless you are pushing 10gbit and leaving the screen on 24x7, even an old box will be mostly in an idle state, with actual draw well below 30W.
Even if that were not the case, paying an extra $2.50 / mo to not do ghetto fabulous bs with rpi and vlans seems like money well spent to me.
That heavily depends on the Dem primaries. I think after the unpopularity of Biden and the 2024 loss by Harris there might be more appetite to rock the boat instead of getting another establishment caretaker.
However, the more radical wing of Democrats still have some anti-globalism in them (eg Bernie). But still, imho: Unusual outcomes are on the table for Democratic party leadership at this point.
At this point I don't see a solution to the arms-race of autobesity besides regulation. Cars that represent a larger threat to other road users need to have that externality internalized onto the driver.
Because otherwise we just get things like the Hummer EV which is literally over 9000 lbs.
Everybody else is dealing with AIgen is suffering the AI spitting out the end product. Like if we asked AI to generate the compiled binary instead of the source.
Artists can't get AIgen to make human-reviewed changes to a .psd file or an .svg, it poops out a fully formed .png. It usurps the entire process instead of collaborating with the artist. Same for musicians.
But since our work is done in text and there's a massive publicly accessible corpus of that text, it can collaborate with us on the design in a way that others don't get.
In software the "power of plain text" has given us a unique advantage over kinds of creative work. Which is good, because AIgen tends to be clumsy and needs guidance. Why give up that advantage?
reply