@xylophilist I should probably add more photoness to my blog site: seen-by.davep.dev ;-)

@davep Seeing this projectlet evolve is making me think... I am so going to have to add blog ability to my own proper photo website at some point. Maybe, by the time I get round to it, I'll have something to say. ;)

@davep thank you!

@rohitfarmer Also paging @andyc - another one to add to your collection?

@rohitfarmer Looks really clean!

@davep I also wrote an SSG for my journaling website purely using AI.github.com/rohitfarmer/driftno

@cyclical_obsessive Yup. One thing I am finding is it’s generally a far more effective way of searching for a solution to coding problems.

@davep > 25 days with CopilotAt age 73, and writing code without deadlines and “code reviews”, I have been doing things the way I always have (well using LibreOffice Presentations in place of PowerPoint), but had not tried any “vibe coding”.Gave Gemini an issue I had been living with for over two years (since no robotics.stackexchange, no discourse.ros.org, and no other forum posts had solved). The first mod it suggested failed differently, but when fed the new error trace… fixed!

@xylophilist Not sure the music example tells me anything, I have zero knowledge of what that means.But the person doing this "AI rewrite" seems to have been clear in the past about the attempt to ignore the wishes of the original copyright holder and they're the current maint' of same project. Seems a straight up betrayal of trust issue to me really.Like I say: probably legally fine, but a dick move.

@davep Whenever I see developers getting uppity about copyright, I find myself thinking about copyright in photography and music.By the sound of it, this JPlag thing seems very cognate with the US legal definition of a photo ceasing to be derivative when folks can no longer recognize the origins.And without Mozart being a naughty boy we wouldn't have access to Allegri's Misereri... and so I stay pretty chill about it all (up until someone rips me off, of course ;)

@xylophilist Yeah, that one is wild. I’ve got lots of thoughts on that too (tl;db: possibly legally permissible but ethically vile).

@davep You seen theregister.com/2026/03/06/ai_ as well? Another couple of angles on the whole "teh AIs" thing there. Hadn't thought of the licensing ramifications in too much detail. #ai #llm #development #Programming #licensing

@davep There have always been problematic open source and free projects and it has always been legitimate to criticize them, even if you're not currently contributing yourself, but the best criticism is to fork the project and outcompete it.If you can't fork it, it's not open.

@Jeremiah I'm halfway through and can't stop nodding. Thanks for sharing!

"[W]riters have a say in the design of the calls. We aren’t passive participants. Instead, we have the right, if not the obligation, to get involved with design. This also touches on why writers need to know some programming. We are the objectivity developers sometimes miss. Too often, it’s an unchallenged assumption that the in-house developers, just because they are developers, are always thinking about the clients or have the client’s best interest in mind. That’s not always the case. Writers can help here. In this instance, if something too difficult to explain, it’s not the explanation at fault, it’s the parameters. They need to be reconsidered, literally at the source."

@davep The agent entertainment is real! 😄 I've been working on MCP tools that agents can use — web search, page scraping, DNS lookup etc. It's fascinating watching them chain these together in unexpected ways.

@davep lol! :D

I've skipped a lot of detail in this simplified explanation, for example how to handle open file descriptors and similar icky bits. Hack like this also is far from true fork(), since the parent and the child definitely are quite different from each other in several ways.

@internetross Oh I know. So is my post.

@Sempf this is a non-serious rage-baity article.

@manlycoffee also, sometimes the people who reply to my posts become the people I follow. I would encourage you to share your thoughts more often. If nothing else it is good exercise.

@manlycoffee so, I'm a random. Seems to me something is going to need to change as languages get more expressive.I was just listening to a talk by Herb Sutter on C++ contacts. Drastically increases the the expressiveness of the language at the cost of readability I think. Could be we need tooling that helps filter noise. Maybe we need standards across languages to make it simpler for the tools to identify different kinds of code to declutter.

@remixtures "they are a clear example of why LLMs do not understand the meaning of words, merely regurgitating terms that, in the absence of context, make no sense" - perfect description!

"This is a case where some docs aren’t better than none, because they signify the triumph of intellectual laziness over trust and accountability. While I’m not concerned about their impact (any enterprise customer would shred you to pieces if you provided docs like those), I think that they represent a trend that we must fight, because docs entirely written by AI are wrong.Let’s draw the line: docs generated entirely by AI should never ship to users. You can use AI judiciously to audit your docs for gaps, to spot inconsistencies, to generate first drafts that you’ll edit later. But the moment you let any LLM have the final word on what users will read, you’ve abandoned the basic contract of docs: that someone who understands the system has taken responsibility for explaining it truthfully."passo.uno/ai-wikis-docs-teathe