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.
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.
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.
> 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.
> 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.
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.