Zanfa

It hasn't even been a few weeks since I had AI use a button + onClick handler for navigation instead of a simple anchor tag...

Not to mention that effectively reviewing code is a much more difficult skill than writing it. Without a good mental map of how it affects other parts of the system, it’s basically a rubber stamping ceremony.

Github’s poor PR UI doesn’t help either, there’s limited tooling to navigate around the codebase not directly changed (but affected) to identify and highlight problems.

Over time the gems will rise to the top

I’m not sure this can be assumed. Discovery was already one of the biggest hurdles when releases were bottlenecked by human output. Increasing output 10x is only going to make it worse.

Same as with Google, where they’ve lost the SEO war against AI spammers and valuable content has become close to impossible to find.

This seems exactly backwards. Most commits should not exist, because the majority of people can't already help themselves from committing "wip" "fix lint", let alone anything more granular.

I don't know what NPM is doing, but yarn installs deps much faster than NPM

Can you elaborate about the practical value of having the history of back and forth, in a PR or even in the commit log? In my 20ish years of experience, I can’t recall a single instance where I’ve solved something thanks to having this work-in-progress state persisted in the repo history.

It’s exclusively been the other way around where having a smaller number of larger squished commits (post merge) that’s made the project be more maintainable.

It’s not that. The sort of issues all of the above have caused are fundamental, eg not using anchor tags for navigation. It’s not in any way easier to use a button or div with an onclick handler. It’s also not easier to serve megabytes of JS to render 5kb of comments.

You hate BAD react SPAs that break the fundamentals of how the web works.

But that’s all of them? If Github, Reddit, LinkedIn and Facebook and others are unable to build SPAs that don’t constantly break the fundamentals while also choking the browser, maybe it is a tech problem.

Not surprising. It’s placed exactly where the regular search results used to be (when navigating away from image results) and muscle memory is strong. Haven’t clicked it intentionally once though.

There are external devices that can be attached to the camera to record gyro data, e.g https://docs.gyroflow.xyz/app/advanced-usage/using-external-... I just ordered one a few weeks ago and haven't received it yet, so can't talk about personal experience, but there's no technical reason it couldn't work well.

It's been awhile, but the best experience I've had desoldering ICs with many pins was with JBCs hot air extractors. They're little metal funnels you put around the component you want to desolder to contain hot air, with a tiny suction cup to lift the part once solder starts to melt.

JBCs stations are expensive though, but you should be able to use just the heat deflectors and a pair of tweezers, rather than a vacuum pump as long as you already have a hot air station.

Outright lie about the problem and the scope of it.

One of my favorites was “EU is banning juice”, when the definition of juice was being standardized and local producers of fruit-flavored sugar water couldn’t keep selling their beverages as “juice” anymore.

It’s always been interesting to me that multi-million and even billion dollar tech companies don’t have perfect websites in terms of UX.

This, but for online shops, especially clothing. Horrendously buggy, laggy, with broken navigation (especially when navigating back), filters that don't work on > 95% of online stores. Why they wouldn't fix their primary (or at the very least highest margin) income stream is beyond me, but I've had to abandon so many shopping carts just because the checkout flow is literally broken.

This is my exact experience, but with Google Maps. Constantly suggesting gravel (or worse) side roads instead of highways and hallucinating multiple turn lanes etc on a country road about 1 car wide. It's been a few years, but I still remember the time I was in Berlin and buses didn't run due to bad weather, but I had a flight to catch so I had to walk to the Tegel airport and the route Google maps recommended ended up being quite an adventure, having to crawl through a hole in a linked fence on an unlit dead-end road next to the airport.

Clearly the real issue is their 27001 expired on 15/12/2025

I thought A16Z were a top-tier VC wanting to create long-term value.

That hasn’t been the case since they publicly went all-in into crypto scams.

It might be a bit facetious, but if I had 10m invested with them I'd be asking questions about their investment thesis.

Their fund sizes have skyrocketed since.

Not so large that it is too large to show on a GitHub page.

Maybe not applicable in this case, but Github has a ridiculously low threshold for when it starts hiding diffs. Probably a limitation of their new React frontend.

In short term profits vs long term benefits, we all know who wins.

And is the reputational risk worth it?

Yes! The only metric that matters is assets under management, since that’s where funds take their cut. Nothing else matters.

A16Z used to be a respected investor, then they went crazy deep into crypto scams and their AUM exploded, so they made more money than ever before.

If your first contact with rails is version 7+ and you’re only comfortable with JS/TS, then you’re not going to get it and might actually strongly dislike it

This is the primary issue with Rails in my experience. It takes intentional effort to internalize the idioms before it clicks and you unlock the magic that makes it so insanely productive. JS devs will keep trying to force backend business logic into Franken-React Stimulus components and complaining it's not very good.

Those people don't choose frameworks. It'll be chosen for them by some LLM and given the prevalence of JS, it'll likely be some flavor of React.

Accelerate your agents with convention over configuration. Ruby on Rails scales from PROMPT to IPO. Token-efficient code that's easy for agents to write and beautiful for humans to review

This is so painful... I can't help but wonder who they're trying to target with such inane slogans.

Rails is amazing, but "token-efficiency" is not on the list of reasons why.

Having grown up playing with LEGOs, I can still distinctly remember the feeling of sore fingers pulling tiny pieces apart after a long session. It wasn't until a few years ago I learned there's an official brick separator tool [1]. Would've changed my life as a kid.

[1] https://www.lego.com/en-us/service/help-topics/article/lego-...

But I prefer Rust over Zig. The main difference is Rust chooses a "closed world" model while Zig chooses an "open world" model: in Rust, you must explicitly implement a trait while in Zig as long as the shape fits, or the `.` on a structure member exists (for whichever type you pass in), it will work (I don't use Zig so pardon hand wavy description).

Do you happen to have a more specific example by any chance? I’d be interested in what this looks like in practice, because what you described sounds a bit like Go interfaces and from my understanding of Zig, there’s no direct equivalent to it, other than variations of fieldParentPtr.

It _worked_ why did you break it? Who gained what out of you breaking it?

This applies to so much of modern software it's not even funny.

I went with the T18 board since it’s passively cooled. IIRC it could also do PD through USB-c, but that would require additional cooling and I just don’t trust noname Chinese manufacturers to do that correctly anyway, so I typically have it hooked up via HDMI. So far it’s been perfectly stable, without any issues. I think there might have been a small addon board to be able to use full brightness as well. There’s a built-in retro display monitoring menu, but I haven’t had a need to use it really, most configurations work from Mac OS, including color profiles and brightness control.

For cables, my iMac had an opening in the back for RAM sticks, which I popped out and wired all cables through. I mounted the driver board on a piece of plexiglass so that most of the ports are accessible directly to the RAM opening. For power, I use a regular third party power brick I had laying around, though some people have reused the iMac’s original power cable with an internal power supply.

Honestly, the hardest parts were identifying the correct driver board and gluing the front glass back on after assembly.

Did exactly that a while ago to salvage the nano texture panel from my 5k iMac. It takes a bit of research to figure out the correct driver board for the specific panel / peripheral combo, but the build process itself was pretty straightforward and it works like a charm.

It wasn't the migration to Azure that completely borked their PR UI.

The extra hour of daylight in the evening on summer time is even more valuable in the winter.

Nothing personal and I wish you the best of luck with wasp.sh, but the constant churn of new libraries that will revolutionize JS development, but are never quite finished and are eventually abandoned in a semi functional state is exhausting and exactly the main issue I have with the JS ecosystem in general.

At this point, I'm convinced there's a secret global conspiracy to prank JS developers. For example 1 person maintaining 3 similar-but-distinct decimal libraries for Javascript, or the top 3 PDF processing libraries silently producing blank outputs.