No this is Patrick!

@dbx12@programming.dev looks like it really is an AI bot. Good comment.

If you are an "autonomous worker" you should disclose yourself as bot in your fedi profile.

Weird how you're not dogfooding this project to collect feedback.

Agreed that the solution to metastasized slop debt is to just rewrite it. That's kind of another way of saying that your entire codebase was written at prototype quality, except worse because of all the hidden decisions no one made.

I think the solution is a radical shift in how we test and review code. If your coworkers weren't thorough at testing and code review before 2026, then you are probably suffering right now.

I'm guessing LLM advocates want to solve this problem by throwing more LLMs at it, I.e.adversarial review bots, harness engineering, etc. And those are probably good ideas to raise the competency of LLMs, but I don't think they can replace the better judgement of humans anytime soon.

If your workplace culture already had strong testing and code review standards, then a sloppy PR is going to fail the smell test quickly.

And the biggest problem I see is simply with lazy people who don't review their own slop but expect others to review it. It's infuriating and completely unacceptable.

Assuming everyone is trying their best, there is really no substitute for getting your hands dirty and making sure you at least understand all of the code you submit and take the time to interrogate the surrounding code as well. I don't think there is a hard rule to know that you've adequately "digested" and refined the LLM output. But even before LLMs, I used to review my own code and iterate to make it more readable. It's like writing prose: you read, edit, re-read, until it's good.

Fun story: I'm an electronics engineer and have been working as a manufacturing engineer for the last 15 years. The company I'm with right now is basically forced me into software development. I learned c++ and python in school but never really did much with them professionally, work on a bunch of side projects at home but software development has never been a part of my career until the last year and a half. I've been asked to start developing production tests and other production applications in our electronics assembly department. Mostly this is creating small python applications that program and test pcbas, nothing large maybe a half a dozen files and a couple thousand lines of code. But now they've asked me to start developing an integration with our erp and they want it to real time push production data from each bench, operator scans a PCB loads it into a jig presses a button it gets programmed and tested, "my" software reads the erp and pushes all of this information back into the erp slowly moving jobs forward eventually closing them out as operators hit counts. My new manufacturing execution software was written entirely with cloud code and is now two dozen files and almost 100,000 lines of code. No one at work cares. But it all works, we haven't found any real problems yet. I've been encountering bugs as operators use the mes but it's dumb stuff like not understanding operator behavior and trying to code around that, ie I didn't log out I didn't scan a unit I forgot to do x y or z... I am both incredibly impressed and insanely worried. This new system changes money in our erp, and no one who actually knows software development has ever looked at this ever.

Yeah, I find it really tricky, because LLMs excel at adding yet another implementation to the side, whereas they will barely ever introduce an abstraction to cover both requirements.

And the humans often don't really read the code anymore either. They ask the LLM to make a suggestion, then check the diff for plausibility and that's it. They don't have to solve it themselves, so they never properly dig into the surrounding context and therefore cannot notice the missing abstraction either.

And in the end, it's not just that the humans don't know the code, it's also that it becomes near-impossible to refactor, because it's just too much code to fit into a brain at a time.

You can't anymore realize that one part of the codebase should've been solved by an already-existing abstraction.
Instead, you find five places in the codebase that really look like they should've been solved with a shared abstraction and then good luck figuring out what the common denominator is and how each of those places should be adjusted to fit this common abstraction, oh and also you didn't see two more places that really should also be solved that way, but for them your chosen abstraction doesn't make sense anymore, and then you ask the others and they tell you, oh man, that never made sense, we never really thought about it, because it was so easy to just tell the LLM to build it, and now that feature has to be removed in its entirety, so you just wasted two weeks trying to understand code that never made any sense in the first place.

Ask me how I know. 😑

I'm not sure if I follow the question, let's me try to understand.

If you are talking about a self-hosting. This isn't the governance, this is the "deployment" of a software. I know that I talk heavily on this point on the essay, but the focus is regarding that self host is a act on the individual level, while governance is about who use the system and have a say on it.

I'll grab a example, (I'll avoid the Uber cliche, but maybe I need to take this one)

Imagine a N-unit building, cooperative software replaces the landlord with a transparent governance dashboard (I'm assuming that all residents own each of the units in this building). Residents propose maintenance tasks (e.g., roof leaks) and collectively vote on fund allocation using a one-unit-one-vote system. The software automatically tracks each unit's financial contributions, schedules shared laundry slots via a consensus calendar, and logs inspection reports viewable by all. When a major expense arises, the platform facilitates a binding poll, calculates each owner's share, and executes payment only when the quorum is met, ensuring every resident has equal say over their shared physical assets.

This is the example of governance that I was talking about. The people who use and own the building have a say on it. When something arives everyone have a way to discuss and talk, using the software as a tool to support then. Self-host is just the deployment for this system, but the focus is on the helping then to mitigate and ensure that everyone have a say in it.

I hope I got your point right.

Like what lf does for the projects they host? Please say more

What kit did you get?

I tried visiting the website but it didn't seem helpful... Just a map of purple dots that don't do anything if you click on them (maybe it's a mobile problem? seems like a major oversight in that case, as most web traffic nowadays is mobile). Also no pinch to zoom?

Am I missing something?

What a lovely reason to visit Italy again! 🖖🏼

How are they funded? 3 devs for something like this is impressive!

!twnw@fedia.io

Imagine what a #WealthTax could do for opensource projects.

Well that does sound easier... I only use GIMP for basic hobby projects so i havent learned all the ins and outs and am probably doing a bunch if things the hard way around haha.
Cheers friend

Is the solution "hash puzzle answers and store those hashes"?

Edit: no this is just open sourcing most of it. Separate server git submodule for puzzles and answers

You could also use the select tool to draw a single circle, then go to the Select menu and click Border which will create the outer and inner selections with the width you specified between them. Much easier than selecting a circle and de-selecting the centre hole.

Do you understand how bitmaps and raster drawing works?

Yes I know the difference between vector and bitmaps

Everything is represented as a 2d array of pixels.

Only after the rasterization has taken place.

The circle selection before you paint can be moved/scaled/etc and then when you actually want to draw the circle trace the path with the appropriate thickness and use antialiasing if you need to smooth it.

The problem is that the selection itself can lose information, it's handled internally as a raster mask. That's why you should use a real vector shape.

If you want to make vector drawings, take a look at InkScape. GIMP is the wrong tool for that, so use the right tool for the job if that’s what you want to do.

No. Raster editors can support vector shapes. They vectors are rasterized during the final export, not while creating the shape (which is lossy and what selection shapes are).

Look at how to create, move and transform a circle in photoshop (or if you don’t want to give adobe money, use photopea).

Exactly what i do.

1. pick a grid coordinate and use ctrl+shift with circle selection tool to the size i want.
2. then using the same starting grid coordinate i create a second inner selection but hold down (shift i think?) to do [ - ] selection instead of [ + ] selection and once the negative selection is started press ctrl+shift again to lock it to circle and expand until i have the circle outline i wanted.

This is really fucking cool

Step 1: make a circle in geogebra

Step 2: copy/paste it into gimp

Step 3: there is no step 3

I want to be able to draw four lines perpendicular to each other. That's my bottom line and I won't settle for anything less.

Just for the sake of completion, I'm going to throw Banjoon out there, but I like Baloonjo better.