HNHacker News
TopNewBestAskShowJobs

mkozlows

3,439 karma · joined March 5, 2014

submissionscomments
mkozlows··on Professional software developers don't vibe, they control
I'm not remotely cutting edge (just switched from Cursor to Codex CLI, have no fancy tooling infrastructure, am not even vaguely considering git worktrees as a means of working), but Opus 4.5 and 5.2 Codex are both so clearly more competent than previous models that I've started just telling them to do high-level things rather than trying to break things down and give them subtasks.

If people are really set in their ways, maybe they won't try anything beyond what old models can do, and won't notice a difference, but who's had time to get set in their ways with this stuff?

mkozlows··on The future of software development is software developers
... and people kept using Uber.
mkozlows··on Stranger Things creator says turn off “garbage” settings
There is! That is precisely how TVs work! Specs like BT.2020 and BT.2100 define the color primaries, white point, and how colors and brightness levels should be represented. Other specs define other elements of the signal. SMPTE ST 2080 defines what the mastering environment should be, which is where you get the recommendations for bias lighting.

This is all out there -- but consumers DO NOT want it, because in a back-to-back comparison, they believe they want (as you'll see in other messages in this thread) displays that are over-bright, over-blue, over-saturated, and over-contrasty. And so that's what they get.

But if you want a perfect reference TV, that's what Filmmaker Mode is for, if you've got a TV maker that's even trying.

mkozlows··on Stranger Things creator says turn off “garbage” settings
"Warm" or "Warm 2" or "Warm 50" is the correct white point on most TVs. Yes, it would make sense if some "Neutral" setting was where they put the standards-compliant setting, but in practice nobody ever wants it to be warmer than D6500, and lots of people want it some degree of cooler, so they anchor the proper setting to the warm side of their adjustment.

When you say that "HDR is static" you probably mean that "Dynamic tone-mapping" was turned off. This is also correct behavior. Dynamic tone-mapping isn't about using content settings to do per-scene tone-mapping (that's HDR10+ or Dolby Vision, though Samsung doesn't support the latter), it's about just yoloing the image to be brighter and more vivid than it should be rather than sticking to the accurate rendering.

What you're discovering here is that the reason TV makers put these "garbage features" in is that a lot of people like a TV picture that's too vivid, too blue, too bright. If you set it to the true standard settings, people's first impression is that it looks bad, as yours was. (But if you live with it for a while, it'll quickly start to look good, and then when you look at a blown-out picture, it'll look gross.)

mkozlows··on Stranger Things creator says turn off “garbage” settings
The whites in Filmmaker Mode are not off. They'll look warm to you if you're used to the too-blue settings, but they're completely and measurably correct.

I'd suggest living with it for a while; if you do, you'll quickly get used to it, and then going to the "standard" (sic) setting will look too blue.

mkozlows··on Stranger Things creator says turn off “garbage” settings
It's true that Filmmaker Mode might at some point in the future be corrupted, but in the actual world of today, if you go to a TV and set it to Filmmaker Mode, it's going to move most things to correct settings, and all things to correct settings on at least some TVs.

(The trickiest thing is actually brightness. LG originally used to set brightness to 100 nits in Filmmaker Mode for SDR, which is correct dark room behavior -- but a lot of people aren't in dark rooms and want brighter screens, so they changed it to be significantly brighter. Defensible, but it now means that if you are in a dark room, you have to look up which brightness level is close to 100 nits.)

mkozlows··on Karpathy on Programming: “I've never felt this much behind”
I think you should ask yourself: If it were true that 1) these things do in fact work, 2) these things are in fact getting better... what would people be saying?

The answer is: Exactly what we are saying. This is also why people keep suggesting that you need to try them out with a more open mind, or with different techniques: Because we know with absolute first-person iron-clad certainty what is possible, and if you don't think it's possible, you're missing something.

mkozlows··on The future of software development is software developers
Agree. But it's increasingly the case, IME, that for a a lot of tasks, you can start with that. If it does it well, great. If it does something stupid, it's easy enough to ask it to completely rework the stupid thing in a better way, and it can do it quickly. That's still a huge shift compared to the olden days (three months ago) where you needed to really break things down into small chunks for it to get to a success state.
mkozlows··on The future of software development is software developers
Honestly, even this isn't really true anymore. With Opus 4.5 and 5.2 Codex in tools like Cursor, Claude Code, or Codex CLI, "just do the thing" is a viable strategy for a shockingly large category of tasks.
mkozlows··on Karpathy on Programming: “I've never felt this much behind”
"The future is already here, it's just unevenly distributed."

At some companies, most developers already are using it in their day to day. IME, the more senior the developer is, the more likely they are to be heavily using LLMs to write all/most of their code these days. Talking to friends and former coworkers at startups and Big Tech (and my own coworkers, and of course my own experience), this isn't a "someday" thing.

People who work at more conservative companies, the kind that don't already have enterprise Cursor/Anthropic/OpenAI agreements, and are maybe still cautiously evaluating Copilot... maybe not so much.

mkozlows··on Karpathy on Programming: “I've never felt this much behind”
It's because the models keep getting better! What you could do with GPT-4 was more impressive than what you could do with GPT 3.5. What you could do with Sonnet 3.5 was more impressive yet, and Sonnet 4, and Sonnet 4.5.

Some of these improvements have been minor, some of them have been big enough to feel like step changes. Sonnet 3.7 + Claude Code (they came out at the same time) was a big step change; Opus 4.5 similarly feels like a big step change.

(If you don't trust vibes, METR's task completion benchmark shows huge improvements, too.)

If you're sincerely trying these models out with the intention of seeing if you can make them work for you, and doing all the things you should do in those cases, then even if you're getting negative results somehow, you need to keep trying, because there will come a point where the negative turns positive for you.

If you're someone who's been using them productively for a while now, you need to keep changing how you use them, because what used to work is no longer optimal.

mkozlows··on AI is forcing us to write good code
Because a) the benefits are bigger, and b) the effort is smaller. When something gets cheaper and more valuable, do more of it.
mkozlows··on AI is forcing us to write good code
I like this. "Best practices" are always contingent on the particular constellation of technology out there; with tools that make it super-easy to write code, I can absolutely see 100% coverage paying off in a way that doesn't for human-written code -- it maximizes what LLMs are good at (cranking out code) while giving them easy targets to aim for with little judgement.

(A thing I think is under-explored is how much LLMs change where the value of tests are. Back in the artisan hand-crafted code days, unit tests were mostly useful as scaffolding: Almost all the value I got from them was during the writing of the code. If I'd deleted the unit tests before merging, I'd've gotten 90% of the value out of them. Whereas now, the AI doesn't necessarily need unit tests as scaffolding as much as I do, _but_ having them put in there makes future agentic interactions safer, because they act as reified context.)

mkozlows··on Mozilla appoints new CEO Anthony Enzor-Demeo
How's that work for you on Android? Firefox on Android with uBlock is the huge win.
mkozlows··on Quill OS: An open-source OS for Kobo's eReaders
KOReader has built in Progress Sync, which works well for the purpose.
mkozlows··on Steam Machine
Valve has said it won't have console-like pricing, so.
mkozlows··on The Silent Scientist: When Software Research Fails to Reach Its Audience
The question is whether spherical cow research tells you anything that holds up once you introduce the complications of reality into it. In physics, it clearly does. In economics, I think it does in a lot of cases (though with limits). In software engineering... well, like I say, there are areas where I'm sure it does, but research about e.g. strong typing or unit tests or PR review or whatever just doesn't have the juice, IME.
mkozlows··on The Silent Scientist: When Software Research Fails to Reach Its Audience
Because it's usually not that useful. I have a friend who was software-adjacent, and would post all these exciting studies showing that this or that practice was a big deal and massively boosted productivity. And without fail, those studies were some toy experiment design that had nothing to do with actual real-world conditions, and weren't remotely strong enough to convince me to up-end opinions based on my actual experience.

I'm sure there are sub-fields where academic papers are more important -- AI research, or really anything with "research" in the name -- but if you're just building normal software, I don't think there's much there.

mkozlows··on Kafka is Fast – I'll use Postgres
If what you want is a queue, Kafka might be overkill for your needs. It's a great tool, but it definitely has a lot of complexity relative to a straightforward queue system.
mkozlows··on Nearly 90% of Windows Games Now Run on Linux
There are apparently are some semi-experimental FFB drivers out there for a few wheels... but yeah, most hardware has a zero percent chance of working, because it's a niche of a niche. And then if you're doing online racing, they all(?) have anti-cheat stuff that won't work for you anyway.

If games transition to SteamOS/Linux in general, I think this niche is going to be one of the slower ones to move, but never say never.

mkozlows··on Apple Vision Pro upgraded with M5 chip
Shiftall Meganex 8K is out, and Pimax Dream Air is upcoming. But those are PCVR headsets, not... whatever the AVP is.
mkozlows··on Apple Vision Pro upgraded with M5 chip
The xReal ones are extremely workable. Like, you wouldn't want to do it by preference if a good monitor was available, but easily good enough for a situation where you don't want to use a monitor or don't have one.
mkozlows··on AV2 video codec delivers 30% lower bitrate than AV1, final spec due in late 2025
"Not any better than Blu-ray" is the same as saying "much better than streaming."
mkozlows··on Vibe engineering
I really wish I could like this term, because I agree the world needs a pithy, memorable one for what you're describing. But alas, I don't think this is it, either.
mkozlows··on Why did Crunchyroll's subtitles just get worse?
And what makes the one streaming service stay good, with no competitors?
mkozlows··on Samsung now owns Denon, Bowers and Wilkins, Marantz, Polk, and more audio brands
Samsung has owned Harman Kardon and its stable of brands for a long time, and they've been mostly fine. Mainly, I think Samsung doesn't care about them except as names to license in "exclusive" partnerships with automakers.
mkozlows··on Thoughts on Mechanical Keyboards and the ZSA Moonlander
Try something like a Sinc: https://keeb.io/products/sinc-rev-4-split-staggered-75-keybo...

It's still mechanical, it's still split, it's still QMK programmable, it's got hotswap sockets so you can try different switches... but it's also an extremely normal staggered layout with function keys and everything.

I think it's worth trying the ortho 'n' layers approach, because it has real wins to it; but if you've tried it and don't like it, this is one step closer to normalcy, while still keeping many of the wins.

mkozlows··on Thoughts on Mechanical Keyboards and the ZSA Moonlander
It is! If you want a keyboard that you never think about, a programmable wacky layout keyboard is not for you.

But if you use your keyboard a lot, keyboard hobbyism can be rewarding to a certain point.

mkozlows··on Thoughts on Mechanical Keyboards and the ZSA Moonlander
So a) that seems like a nightmare to me no matter what keyboard I'm on, but b) if you have frequently-used shortcuts that are a pita to get to, you can put them on a layer where you just use them.

Like, I legitimately don't know anymore how you take a screenshot on MacOS, but I know that I hit the modifier key and then this one other key, and that takes a screenshot. Also don't know what you press to move from virtual screen to virtual screen, but mod-m and mod-comma go left and right for me. And in a browser, mod-s and mod-f do ctrl-shift-tab and ctrl-tab.

It's a terrible idea to do this for rarely-used shortcuts, as you'll never remember them; but for ones you use frequently, it's better-than-native, because you can put them on convenient keys that are easy to hit, rather than whatever contortions you'd need to do to hit Ctrl-Shift-F12.

mkozlows··on Claude for Chrome
The strong sense I got from reading this is that they don't believe it's possible to safely do this sort of thing right now, and they want to warn people away from Perplexity etc. so they can avoid losing market share while also not launching a not-yet-ready product.

(The more interesting question will be whether they have any means to eventually make it safe. I'm pretty skeptical about it in the near term.)

← PreviousPage 4 of 18Next →