> even before LLMs could spot my bugs in an instant
I guess it depends on the bugs.
LLMs even INSIDE the (VS) debugger couldn't work out some of the more recent bugs I have been looking at. Never mind by statically looking at the code base.
I too have been burned by the BBOC, although not as badly as this:
I picked out a random short ethernet cable that looked nice (it was flat) to connect my wifi AP to my router.
It took me about a month to realize my 100mbit internet connection had dropped down to about ~85-90mbit, but more importantly, transferring files between a wifi client and the wired network was also only ~90mbit.
Turned out the cable was so bad that it only connected at 100mbit...
I have now gone the other way and I actually curate the BBOC:
All cables I get for 'free' with random appliances now go straight to the bin (unless they are specialised) and I only keep cables I specifically bought and know they adhere to a standard.
The mass of unneeded cars will be at the periphery. The equivalent of taxi stands will have needed cars within reasonable distance.
Back in the PRT days we simply planned to store 1-2 vehicles in-station waiting for walk-ups, and if a drop-off comes in they just push out the waiting vehicles and they circle back. The efficiency remains crazy supportive of that model vs empty buses or trains.
If you live in the US, it's not worse. If you live anywhere else in the (developed) world, it is worse.
My hope is that the bottom-of-the-barrel US approach isn't shoved down the throats of everyone else just when we're finally managing to rebuild cities for people, not for cars.
The only connection off the top of my head is that mL of water increases by 1˚C if heated with 1 calorie. Which is annoying because 1 Calorie is 1000 calories.
It basically makes it impossible to have it build a very large feature incrementally.
I am currently building a very large feature and the only way to do this properly is to do it in small steps.
No matter what I prompt, I always have to spend a bunch of time reigning it in during planning (and implementation!) because it tries to solve the whole thing end-to-end or add enough boilerplate so that a code path (that is still under construction) returns a meaningful (but wrong) value.
And then of course every time I start a new session it gets very upset that the feature I am trying to implement will never work because the main user entry point has a 'not fully implemented' exception that definitely needs to be removed immediately!
I typically see the exact opposite problem when giving Claude the reins on a large undertaking.
Claude will, without prompting, break the implementation into 6 phases, and write AI slop “code as English” specs for each phase, each one with glaring errors and unintelligible terse jargon. It will review them all several times with major findings every time and tons of design churn…
Then it will implement a total heap of garbage over many hours of many agents, despite it working in “lanes” and in parallel, and with regular input needed.
Just thousands and thousands of lines of junk, which auto review then plays whack-a-mole to polish and fix. All the while it is able to see the errors and edge cases, yet fails to see the key architectural blunders that led to them in the first place.
I’ve had to fully rethink my approach to LLM tasks like this. For example, for library-esque modules, I have found that isolating the problem outside of the codebase is one useful approach. Something about the lack of noise. It can land on a cleaner solution that can be retrofitted.
I also find that asking it to implement end to end in one fell swoop with a very high level plan actually saves time and creates a cleaner result.
The garmin has so much battery life that when it's at 10% and starts complaining that the battery is close to dying I still have about 2 days to remember to charge it.
And obviously you don't get penalised for charging it more often. Just charge it every Sunday if routine is a big issue.
It almost seems like we need laws that information about public services have to be available on a public website (as opposed to a third-party website that requires registration).
I personally do not know anyone in real life with a twitter account (although I have one, I have not used it in over 15 years), I wonder how many people just go without this information and are angry that it's (seemingly) not available.
There's no way France have no clause in its law everywhere that can be creatively interpreted to be used for that purpose. But that won't get enforced unless there will be a better option than Twitter that average Paris Metro employees understand; they would not be dumb, but they would not care. Average people today can barely grasp the concept of a password.
> some kind of admin panel where employees can easily CRUD some updates
In my experience this is usually the crux. That software always rots, and needs whatever (minimal) on-ramping for employees, as well as access management.
If I could wave a wand at those solutions I'd stop fighting the user and let them post to Twitter or wherever, and just have a public facing page pull those posts as updates for consumers outside of whatever walled garden they originate from.
Access management is already a problem - just maybe they haven’t run into it. What happens when the employee who has the twitter password leaves? (This is France so the only way is probably retirement).
A bespoke system with an interface similar to twitter sounds like it’d be a suitable solution. And I bet it can be vibe coded in 5 minutes.
I'm in the UK and tired of basic public services like the railway company posting service updates to X first. I keep a bookmark to the local train company (Northern in my case) on XCancel but while it was down, I was a bit under-informed. The stuff is on their own website, but it seems to appear there after it appears on X, the layout is crap, and there's no way to contact the company other than via X.
A lot of private companies do the same thing - no way to effectively contact them privately, but as soon as you whinge publicly on X they're "on it". Octopus Energy is one of the worst for that.
More or less the same over here in Germany, except with WhatsApp, which is only slightly better than X, but at least you are likely to already have it installed because of all your contacts that refuse to use a more secure messaging app...
I don't think it's even about being in anyones pocket. They want the publicity. And unless they are all forced to stop using it, everyone has to use it.
> And unless they are all forced to stop using it...
I was talking about the political will to mandate "forcing them to stop using it".
The UK doesn't actually have the economic and political will to put together a national Mastodon or Bluesky instance and mandate that all public agencies use it for their announcements. I'm sure there are three fact-finding committees about it at the moment though.
The problem is that if they did put together those instances the general public wouldn't use them. Most of the public don't want to see a politicians tweets. They share them on Twitter because people will have it put in front of them regardless of desire.
The issue being discussed is important notices from Government agencies that affect people's lives immediately, that shouldn't be behind a login wall. Think train service cancellations and such.
Partially true. We can make better front ends just for this information. Imagine traindelays.com or whatever. If it's better than Twitter then people will go there, and then we can get a direct feed from the train company, and then they can abandon Twitter.
I don't disagree and I'm not a mastodon user but, as far as I know, if you local gov hosted an instance and your state gov did too, you could, essentially, join both and see them together?
RSS aggregation seems like the solution to me but I think we've got to admit defeat on that one because it's been around forever and people don't use it.
Pretty much every podcast in the world and all of their listeners are using RSS. WordPress powers something like 30% of the Web, and most of the operators behind those sites are publishing RSS whether they know it or not.
I thought I was more clear than I was being about rss in the context of the conversation about text based news.
How many people consuming text via rss the same way people consume audio via podcasts?
We're talking about text here. We all know how this sentence ends, "You should start a ..." and it isn't rss feed. Everyone used to have a blog and nobody really cared. Now everyone has a podcast and (more) people do. People don't know what an rss feed is.
> We all know how this sentence ends, "You should start a ..." and it isn't rss feed.
I don't know what this means. I'm guessing the correct answer is supposed to be "podcast"? Even so, weird false dichotomy.
That looking at tweets and listening to podcasts is more popular than reading long-form blog posts via RSS has a lot more to do with people's revealed preference for looking at tweets and listening to podcasts versus reading long-form blogs than it has to do with RSS.
(The actual context was delivery of notices by public services through non-Twitter feeds, anyway. Not blogging.)
> People don't know what an rss feed is.
I don't know why you think this is relevant here. It seems that when you're referring to using "RSS", what you mean is for people to care about RSS—in the way that Gemini, Secure Scuttlebutt, etc. have always been about caring about (and almost exclusively using them to talk about) Gemini, Secure Scuttlebutt, etc. than they ever were actually expected to be used organically and non-self-referentially.
The fact is that people (already/still) use RSS today. It hasn't been defeated. And Twitter could turn into an RSS-based feed reader tomorrow that works basically the same as it works today, and then suddenly everyone would be using RSS but no one would drop out because of it. Because people don't know (read: care) what an RSS feed is.
You can follow them both from your own mastodon account on a third server.
It's a technically bad solution though, because mastodon is push. The government server has to maintain a list of everyone who's subscribed and make an HTTP request to all of those random domains, and have some timeout and removal policy because sites die all the time. Pull-based, like RSS, is way cleaner.
We need to stop focusing on the specific protocol when it's not relevant and focus more on the patterns. Wanting RSS, specifically, made sense back when everyone had an RSS reader, the same way it makes sense to have an HTML website today because everyone has a web browser. But since very few people have RSS readers now, there's infinite flexibility in the format you use to provide your feed. The most useful is probably a phone app that vibrates your phone with a notification when your train is delayed. RSS can be provided as an option.
A more practical consideration for most people, though, is that the app is full of shit. I mean really full of shit. You open the app and it just spews a torrent of shit at your eyeballs until you close it, mixed with the occasional nugget of gold.
Governments should also be worried about sovereignty.
Definitely slower to use a card or your phone in London.
I remember when they first allowed card use more than a decade ago and it broke the flow quite a bit at rush hour as people were so used to the Oyster card's timing that they'd run into the back of people using cards or people using cards would run into the gate as it had not opened as quickly as they were used to. Quite a bit of commentary around it during that time:
One of the many reasons I moved away from ipods is because iTunes (which was awful; some of the worst software I've used) did the same thing to me just before I went on a trip.
I thought to myself: "I better add these two new albums to my ipod so that I can listen to them while away".
I plug in the ipod, itunes loads up, I walk away.
I come back 10 minutes later and it had not finished yet and I wonder what is going on.
Turns out it deleted my entire 40gb library off my ipod and started re-syncing.
I had to leave so I unplugged the ipod but it was basically useless at that point.
I do agree with Microsoft in general but Apple seems to be very much the same in my experience.
iTunes was great in the beginning. If you can, find someone with a G3/G4 and OSX 10.4/10.5 and see just how snappy that thing feels even with a 100th the RAM of today and a spinning disk. A real nice piece of software.
But then they just started dumping everything onto it and it eventually crumbled under the weight.
reply