OptionOfT

If you want to run as another user, you need to manually add an /etc/group & /etc/password (or generate them in a stage before that and copy them over).

If you need ca-certificates, you need to install ca-certificates in a stage before that and copy over /etc/ssl/certs/ca-certificates.crt from that stage to your current one.

QuickBooks has annoying suggestions that shift the whole UI and cannot be disabled. Misclicks now happen.

The AI in my robot vacuum is... just a label? I don't want to talk to it. I want it to deterministically clean my stuff.

My TV got an upgrade to Gemini. Why? I don't talk to the TV, and it's in my face. (I'm think about getting a device that can do Plex->Atmos streaming).

But when Docker scans my image and notices that there is a CVE in one of those binaries, my image is currently out of compliance.

FROM scratch just reduces the surface.

So we start at compiling the codebase (Rust) against MUSL. That way we can run it with FROM scratch images.

If we need more tooling available at runtime, then we look at alpine, but still using MUSL.

If MUSL itself is proving problematic, or if some of the libraries we use need glibc then we can look at using some locked down image.

The cool part about FROM scratch images is that you'll never have to update your base image to address CVEs. Only your software and its (compiled) dependencies.

Does Mozilla have a contract with Google to not build one in as part of the search contract?

I myself have never worked with C++/CX or C++/WinRT. My Rust journey has been exclusively on POSIX systems, so seeing windows-reactor and getting a UI in a couple of lines is pretty cool.

I would never (at least not in its current state) recommend it for production though, as the crate containing reactor isn't even on crates.io.

Could you share some of the promises made that were abandoned? (I just realized that question sounds like AI... I promise you it's not).

https://github.com/microsoft/windows-rs/tree/master/crates/s...

It's a react-style API for WinUI3 apps, meaning it's not trying to mimic the Windows LAF. It's merely a binding.

But the problem is that for many people they now believe it's ok to present a 10k line vibe-coded PR that only has been verified against external behavior, and some Senior Engineer needs to review it, in time, under pressure, without too much push-back, and lastly, it's the Senior Engineer that gets paged at 2am because something has fallen over.

Also, those scripts tend to start a life of their own, and because it looks good enough, people don't look at them again.

I recall a bug of someone vibe-coding a cleanup script for folders older than $x (on Windows).

Get the CreationDate, and sort. Delete older than $x. Except CreationDate can be null and null is always smaller than $x.

Oops.

~~I _think_ this is the one.~~

God I miss this podcast.

Edit: this IS the one.

Yes, and juniors aren't known for their productive work in the beginning. That's not their purpose. Their purpose is to do the mundane work, because it is important for them to become less junior and more senior.

That is robbed of them.

Which in 5-10 years means the need for senior developers is gonna shoot through the roof.

Everybody had to go to a store and have their ID read by the system, and if they didn't, the phone number would be shut down.

Unsure how that worked for MVNOs though.

Now I live in the USA and am well-familiar with the spam calls. I wonder if this new rule will reduce/prevent them. I think in general the ability to spoof numbers should be banned / controlled. Someone from India should not be allowed to call me with a caller ID from Mayo Clinic.

Yes, yes you can, but you can't force the LLM user to _understand_ your feedback so that they reduce the burden on you, as the reviewer.

I installed iOS 27 yesterday.

I asked it: please notify me when the temperature goes above 80F (so I can close the windows).

Siri responded: it'll be 99F today in Phoenix.

...

And I am absolutely sick of having to justify my job against people who feel they can now vibecode an application without understanding the code.

Kinda like how someone thinks they can build a house without understanding the different layers.

And it's made worse that the way these applications are now built: from the outside, with zero regards towards how it's actually put together.

I understand that execution speed matters over elegance of code. I'm not looking for elegance. I'm looking for code that is clear, well abstracted, well reasoned, so that it not only serves the business purpose, but is also technically sound, non-DRY, with clear indicators of where YAGNI was invoked etc.

I'm genuinely tired of having to defend my job. And the world is using the AI revolution to get rid of so many people. When you call 911 in my city you now talk to AI. You call the local dealer, you get AI.

So AI is presented as this 10x modifier, but I'm not working 1/10, I'm working the same if not harder to verify my PM's slop, because it's me who gets paged at 2PM, not my PM.

I'm tired boss.

I've seen plenty of code that was LLM generated but the commit message itself did not have the co-author attached to it. This only seems to happen when someone's interface to the codebase is completely though Claude/Codex/..., and those are usually the most verbose commits, and yet they say the least, because they just summarize the code changes, not the why.

On the other hand I've seen developers using Claude as a tool. They have VSCode open and a terminal window with Claude and go back and forth, ensuring they write correct code, and leave the plumbing to Claude.

So maybe the author of the code started off small and it grew over time?

If not, and the current defacto standard gem server doesn't accept v1 anymore, we're good I suppose?

`http::Uri` does, and it accepts both `%` and `%25`.

https://play.rust-lang.org/?version=stable&mode=debug&editio...