SCdF

It is endlessly... amusing (?) to me, that we as a community spent decades trying to make it clear that our productivity is not easily measured because what we're doing is complicated and long running, only for AI to come along and suddenly LoC, Nx multipliers, tickets / week etc are held up as useful if not objective measurements.

The reasons we rejected LoC and other measurements have not changed (broadly: code output isn't important, quality output is). AI has all the same problems people do. But for whatever reason we are throwing what we've learnt away. It's kind of embarrassing.

Jesus fucking Christ. On a bicycle.

LLMs should be treated as untrusted. At all times.

The mind boggles at the attitudes that seem to have have led to LLMs being an excuse to throw any of the "science" in computer science we've managed to get into production out the window and go elbow deep into treating computers like mystical alchemy.

The next decade is going to be a bumpy ride.

This is perhaps a very American-centric article? I realise that ZIRP was near-global, but "When banks hiked interest rates, almost every tech company immediately laid off 5-20% of their engineers." does not track with my or my friends' experiences.

And, fundamentally, in countries with employee rights, as an employee I do not give two shits about interest rates the company I work at borrows on. My philosophy on software design does not change. You can argue that the company might pick and choose who it makes redundant, and they might value people who produce "more product", but companies have always valued that visibility. It's your responsibility, if you care, to sell your actions in a commercial context. I don't think ZIRP changes that, and I have not personally noticed a change there.

So currently there are people who are buying grey market peptides[1], marked "not for human consumption" and injecting themselves with them based on dubious anecdotes and vibes, to make their skin clearer, build muscle mass, and so on.

Are they are all suddenly turning into zombies? No. Do they have any real idea what that is going to do to their body a few years down the line? Also no. Could it be catastrophic? Maybe!

I think about this when I think about how violently much of the industry has pivoted into AI being the primary generator of code in the last 6ish months. AI is the peptide, your codebase[2] is the body. Literally no one knows how maintainable this approach is, because there simply hasn't been enough time to find out. It could be fine. It could be a complete mess, with your entire engineering team falling asleep at the wheel, lulled into thinking they understand what is being built when they don't, completely impotent to fix or maintain it once the LLM is no longer able to.

[1] https://www.bbc.co.uk/news/articles/cdr268m5pxro

[2] Well, _their_ codebase. I've stopped doing it with my own personal codebases, unless I genuinely don't care about maintainability or longevity

Interesting project!

I would say some of the indicators are a little odd.

Some of them are questionable in terms of capturing the spirit of the idea ("violent crime" being the same in the UK and the US is a surprising one to me for example. It's capturing serious assault per 100k, but is then not considering murder as violent crime. You have murder later, but maybe combine / group them?).

Some are confusing because they are not clear politically: everyone wants less violent crime, but I don't know your politics and so have no idea which direction you have weighted net migration and asylum/capita.

It wouldn't be atomic, and so would break transaction semantics.

If you committed a row update but didn't update the index, a subsequent query using the not yet updated index would not find the updated row correctly.

It would also only work for certain types of indexes, you couldn't do it for uniqueness constraint for example.

I do agree that in theory you could have some extension to the index declaration that covers all that, but my worry there would be that it would be non obvious and a foot gun. Doing it the way described above makes that break in semantics clear.

Yes, many times. Roughly once a week this year my team or an associated team can't ship changes because PRs, GitHub Actions, or some other associated mechanism is down.

Not to be glib, but being dead lowers your night time heart rate more then exercise as well.

Is having a lower night time heart rate the core goal of exercise? Is it even a goal at all? Or is it just an indicator of other goals being reached? I'm genuinely curious, I wasn't aware that the number mattered, more than what that number actually represents.

If you use scrum, and if you have a scrum master. You categorically don't need to do either of those things though.

Another way of phrasing this though, is that it's in the team's power to determine process (or the lack thereof).

Regardless of success or failure you can say to what degree this is true, and to me this is really that only part of "agile" that is worth locking in.

That's a really good idea, imma steal it.

I will say I specifically don't sync git repos (they are just local and pushed to github, which I consider good enough for now), and I am aware that syncthing is one more of those tools that does not work well with git.

syncthing is not perfect, and can get into weird states if you add and remove devices from it for example, but for my case it is I think the best option.

Ironically the only place I encounter this is using google news, where news sites seem to detect you're in google news (I don't think these same sites do it when I'm just browing normally?), and try to upsell you their other stories before you go back to the main page.

After mucking around with various easy to use options my lack of trust[1] pushed me into a more-complicated-but-at-least-under-my-control-option: syncthing+restic+s3 compatible cloud provider.

Basically it works like this:

- I have syncthing moving files between all my devices. The larger the device, the more stuff I move there[2]. My phone only has my keepass file and a few other docs, my gaming PC has that plus all of my photos and music, etc.

- All of this ends up on a raspberry pi with a connected USB harddrive, which has everything on it. Why yes, that is very shoddy and short term! The pi is mirrored on my gaming PC though, which is awake once every day or two, so if it completely breaks I still have everything locally.

- Nightly a restic job runs, which backs up everything on the pi to an s3 compatible cloud[3], and cleans out old snapshots (30 days, 52 weeks, 60 months, then yearly)

- Yearly I test restoring a random backup, both on the pi, and on another device, to make sure there is no required knowledge stuck on there.

This is was somewhat of a pain to setup, but since the pi is never off it just ticks along, and I check it periodically to make sure nothing has broken.

[1] there is always weirdness with these tools. They don't sync how you think, or when you actually want to restore it takes forever, or they are stuck in perpetual sync cycles

[2] I sync multiple directories, broadly "very small", "small", "dumping ground", and "media", from smallest to largest.

[3] Currently Wasabi, but it really doens't matter. Restic encrypts client side, you just need to trust the provider enough that they don't completely collapse at the same time that you need backups.

This is very silly. It's just a combination of that Derren Brown astrology experiment [1] and madlibs.

[1] https://www.youtube.com/watch?v=haP7Ys9ocTk

If you're interested, Community Fibre is a yes from this website

The US didn't refill it's own strategic oil reserve before it attacked and raised its own oil prices, there is no foreseeable exit strategy where Iran doesn't now effectively own and charge usage for the straight, and Russia (and Iran but I digress) are now more able to sell their oil than before, bolstering their economy and helping them continue to attack Ukraine.

Yeah, I couldn't be bothered getting my accurate chest strap out, but my watch (which is generally very close to the strap) was anywhere from 10-20 off what it was reporting. This is sitting down, 30min after a run.

tbf they have been saying they've started doing this since December, so we're only a few months in. And like most software it's an iceberg: 99% of work on not observable by users, and in spotify's case listeners are only one of presumably dozens of different users. For all we know they are shipping massive improvements to eg billing

If it indicates, culturally in the current zeitgeist, that an AI wrote it, it becomes a bad structure.

Yes, I have not bought a few books after reading their free chapters and getting suspicious.

Honestly: there is SO much media, certainly for entertainment. I may just pretend nothing after 2022 exists.

Agreed, and were gonna see this everywhere that AI can touch. Our filter functions for books, video, music, etc are all now broken. And worst of all that breaking coincides with an avalanche of slop, making detection even harder.

There is this real disconnect between what the visible level of effort implies you've done, and what you actually have to do.

It's going to be interesting to see how our filters get rewired for this visually-impressive-but-otherwise-slop abundance.

> In my mind, besides the self declared objectives, frameworks solve three problems .. “Simplification” .. Automation .. Labour cost.

I think you are missing Consistency, unless you don't count frameworks that you write as frameworks? There are 100 different ways of solving the same problem, and using a framework--- off the shelf or home made--- creates consistency in the way problems are solved.

This seems even more important with AI, since you lose context on each task, so you need it to live within guardrails and best practices or it will make spaghetti.

Blockchain as a vehicle for immutable data has passed. Crypto has given up pretending it's anything other than a financial vehicle for gambling.

Also, the recruitment attempts I've gotten from crypto have completely disappeared compared to the peak (it's all AI startups now).

You should still use swap. It's not "2x RAM" as advice anymore, and hasn't been for years: https://chrisdown.name/2018/01/02/in-defence-of-swap.html

tl;dr; give it 4-8GB and forget about it.

You need to take every comment about AI and mentally put a little bracketed note beside each one noting technical competence.

AI is basically an software development eternal september: it is by definition allowing a bunch of people who are not competent enough to build software without AI to build it. This is, in many ways, a good thing!

The bad thing is that there are a lot of comments and hype that superficially sound like they are coming from your experienced peers being turned to the light, but are actually from people who are not historically your peers, who are now coming into your spaces with enthusiasm for how they got here.

Like on the topic of this article[0], it would be deranged for Apple (or any company with a registered entity that could be sued) to ship an OpenClaw equivalent. It is, and forever will be[1] a massive footgun that you would not want to be legally responsible for people using safely. Apple especially: a company who proudly cares about your privacy and data safety? Anyone with the kind of technical knowledge you'd expect around HN would know that them moving first on this would be bonkers.

But here we are :-)

[0] OP's article is written by someone who wrote code for a few years nearly 20 years ago.

[1] while LLMs are the underlying technology https://simonwillison.net/tags/lethal-trifecta/

Presumably the Epstein files, but I'm not on twitter so not sure

It's not clear why this is being upvoted.

There is not a sample chapter to check, the two authors own the website and appear to be just some developers who know go, and frankly the cover looks AI generated.

As a go developer, why am I supposed to care about this?

Sorry, I was referring less to the sarcastic elements of this article and more the not sarcastic elements of the Claude Code engineer's post on Twitter / Bsky.

So erm, is this a good thing?

I've only been using it for a month, but it quickly becomes incredibly laggy. I have to kill it completely and reopen it[1]. I've also had some unique hard locks never before seen on my machine[2], only while it's open and doing things.

I also haven't noticed it outputting anything that would warrant it being more complex than ncurses or the current fashionable equivalent?

[1] /clear helps but not 100%, and the time to get back to lag land increases each time

[2] (Framework 13" AMD 7840U 32GB RAM)