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.
while SEO has made search worse, i don't think it's the core reason why things are impossible to find, i think it's simply the fact that, over time, google has been butchering the ability to search for exact terms in favour of "natural language" searching, which makes simple things like "how do i make an orange cake" or whatever return useful results, but makes any actually technical query return a lot of pure garbage
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 about having it in the commit history. I've seen a few cases where the back and forth revealed that the AI reviewer was offering bad advice (and a few others where I suspect bad local AI advice is why people keep sending me the same category of mistake).
> 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.
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.
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.
There's the classic "bendy banana law" which British tabloids pushed a lot to paint the EU as an inefficient bureaucracy.
In reality it was a way to harmonise banana grading, no one was forbidden to sell abnormally shaped bananas, it would just be classed lower than the "Extra" class.
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.
reply