mkozlows
Joined 12 years ago
Karma
3,431
Submissions
535
Member since
Mar 5
Recent submissions
Comment · 12 days ago
Comment · 16 days ago
This is why I use Firefox on mobile; I'm addicted to the ad-free browsing life.
Comment · 23 days ago
They show a barely visible line down the middle after three years of intense usage. If I were planning to use my OLED monitor that way (I am), seeing those results wouldn't dissuade me at all (they haven't).
Comment · 23 days ago
Yeah, I'm using one (the Alienware 3926), and it's fine. You'd never know it wasn't IPS except that it's better off-axis and has vastly better blacks and no light bleed.
Comment · 1 month ago
It always did, we just had the norm that in a liberal democracy, we put that to the side for our dealings with people. Same thing as religion -- a huge deal that shapes people's values and attitudes about the most core aspects of life -- and there was a norm of "no politics or religion" in polite conversation.
Comment · 2 months ago
I believe that this is your opinion, but my own opinion (having also tried them, and used multiple generations of B&W ones before this) is that the screens look just fine, and that the slight downgrade of contrast isn't a big deal at all.
Comment · 2 months ago
Yes, I replaced a B&W Sage with the Libra Colour, and used them for a bit side-by-side. Contrast (not sharpness) of B&W text is slightly worse with the color one, but not by so much that you'd notice it if you weren't comparing them next to each other. The resolution of actual color is worse, but obviously you can't get color at all on the B&W one, so hard to argue that this is a downgrade.
Unless you're a real contrast freak, I think most people would be slightly happier with the color than the B&W; but it's definitely not worth paying extra for.
Comment · 2 months ago
It's true that developing junior devs is challenging (but it always was), but that's not what this is about: This is about the kind of not-that-good, mid-ass programmers who make up the silent bulk of the industry. The ones who have 20 years of experience, but who you still wouldn't trust to write fizzbuzz.
Those people are doomed. Which is fine in a lot of ways, but will be devastating for their economic prospects.
Comment · 2 months ago
No, free tier was total garbage with GPT-5.
Comment · 2 months ago
I think the article actually _does_ call that out, noting that the reason for some of these things is due to how wealth propagates through society, even noting the minimum wage specifically. (But it does bring to mind the Agatha Christie quote about never imagining she'd be so rich as to afford a car, nor so poor as to not have a maid.)
Also, though, I think some of the weird poverty-culture stuff of the Netherlands is just a culture thing. Netherlanders are absolutely rich enough to buy paper towel if they wanted to, it's just a cultural thing that they don't. And air conditioning is a whole cultural hot button flashpoint issue for reasons that have nothing to do with money.
Comment · 2 months ago
Yes, but their newer write-up discusses that (and shows that the self-reported numbers have gone up radically, in a way that suggests that even if there is some inflation, the numbers are almost certainly positive if you deflate).
They also have an update -- linked from the original study! -- explaining that it's out of date and no longer reliable, and explaining why they had to cancel a follow-up study because it was understating productivity gains (but also was showing wins for the people who carried over from their previous study): https://metr.org/blog/2026-02-24-uplift-update/
The authors of this paper decided to ignore all of METR's follow-up data and discussion, and to report only the ancient number from early 2025 (a time when Windsurf was state of the art). And then, rather than apologizing for it, and caveating it as a number not to be taken seriously, they described it as a study done "recently."
That's either shockingly dishonest or incredibly out-of-touch.
Comment · 2 months ago
Your PM can write the ticket, and your QA can test the output.
Comment · 2 months ago
Yeah, this seriously drives me nuts.
That meeting that you spent an hour in to understand the requirements? You don't need that meeting if you're not writing the code. That sync up with the QA engineer you did to hand it off to them? Don't need that meeting if you're not writing the code. That half hour you spent installing vim extensions? Don't need 'em if you don't open vim anymore.
There are engineers whose jobs go well beyond coding, of course. Staff engineers and principal engineers have had their jobs radically change because of AI, but not because it's writing all their code.
But there are also a lot of engineers -- your standard mid-level engineer, or even senior engineers at a lot of orgs with title inflation -- whose job is almost entirely about delivering code, and who spend all day either writing code or engaging in scaffolding around code-writing activities. Let's not pretend that automating away that code writing is a 15% boost.
Comment · 2 months ago
I feel like all you need to know about how seriously to take this is that they cite that ancient early-2025 METR study, and describe it in the text as "recently one even found..."
Comment · 3 months ago
It's not a scam. Connecting to the grid has enormous value, and keeping the grid up has real costs. A model where your generation pays you retail prices doesn't make sense.
California's current net metering system, which is more reflective of the true benefits and costs of solar to the power system, has been incentivizing people to add storage to keep their solar rather than get paid big money to feed back midday low-value solar, which is a big win.
Unfortunately, I don't have a lot of first-person advice for you; as I say in that essay, I was also a bottom-up programmer for a long time and was deeply skeptical of top-down approaches. What changed my opinion and my practice was just doing things for long enough that I started having a sense of where things were going to go before I did the exploratory work to find it out, and eventually the exploratory work was unnecessary and I could create a basically-correct top-down design early on. I don't know how you build that experience without actually getting in the reps (which has some implications for future generations of developers, if we have any).
That said, my second-person advice would be to use the agents for the design part of things, too. "Here's the problem, how would you design it?" and then have a conversation with them, push back on the things that seem wrong, imagine reviewing this as a finished design from a coworker and seeing where it looks right and where it doesn't. Ask why it designed things a certain way; suggest alternatives for it to evaluate and think about what it's weighing. Basically borrow the robot's experience to augment and build up yours.