BossingAround

I mean, even Valve has tried it in the past, and it was a failure. Look up Steam Machines from 2010s. I consider the success of Steam Deck (thanks to flawless execution this time) as almost a minor miracle.

It's not very crazy to me. Most corporate teams are overrun with feature creep that "is very simple" (i.e. it takes 3x as long as estimated, because the codebase is a mixture of overengineered spaghetti for that one customer with edge-case requirements and legacy, combined with tests that are meant to be run in a jenkins job which takes 4h to complete).

Then, the engineers are expected to write the docs in between these tickets, and doc is seen as something "to be done within 30 minutes" - of course the docs will be comically (or tragically, depending on your perspective) bad.

Most people have 0 idea on how to write good docs, so in 30 minutes, they write stream-of-consciousness docs and return back to the ticket hell.

When debugging multi-threaded env with debugpy & VSCode, VSCode jumps to code that is active in currently active thread. Is DAP something different? From briefly looking at the docs, it seems like DAP calls debugpy for Python debugging, so we're probably talking about the same experience?

So, IIUIC, new capabilities:

- It'll be possible to print stack traces without modifying or stopping the program.

- It'll be possible to exec into a program at runtime without modifying it.

I'm not sure why the author mentions remote_pdb - this has been with Python for some time, and works since Py 2.7? Not sure what changes in 3.14 for remote_pdb.

What I'm hoping though is improved tooling around debugging Python. Currently, in my experience, VSCode (more specifically, debugpy) provides pretty much unmatched remote debugging capabilities, and I'm really hoping we can have a standardized way to connect any IDE to remote Python processes with the same UX as VSCode.

I would love to use something like Zed, but without remote debugging abilities, the IDE is pretty useless for me. Perhaps better devs don't need remote debugging, but I depend on it more than a junior in college CS program depends on AI :)

It's probably docs... If it can hallucinate an answer, it's docs with probably the most infuriating UX one can imagine.

I remember being taught that no docs is better (i.e. less frustrating to the user) than bad/incorrect docs.

In a very simplistic way:

- Smoking brings cancer and damages lungs.

- Vaping damages lungs (more research needed on other possible conditions).

- Nicotine pouches damage teeth.

I suppose the healthiest way of ingesting nicotine would be nicotine pills, which exist to help people quit smoking (and which is why they are very expensive).

Ah well that explains things, I have a one-page Europass CV.

Why would it be considered a negative flag? I've been using it my whole professional life (~15 years, multiple jobs) and never had an issue with it.

It's just a PDF in the end.

That's why you rotate everyone, not just those that "volunteer"... This way, you're spreading knowledge to everyone, e.g. if I'm forced to deal with an issue on code you wrote, I'm forced to learn about it.

Of course, I might have to ping you and get you to help me with it, so it's less efficient. Then again, if you leave the company, I have some knowledge about the feature, so... There's tradeoffs for sure.

In my company, we rotate every 5 months. So every 6th month, I get put into the customer-facing team for 1 month. Every other month, a different team member is on the customer-facing team.

This is still annoying, but gives you enough time to work on features, and enough time to try and crack some customer cases (though I could even see being in the customer-facing team for more than 1 month, as sometimes, this is not enough to debug the issue and provide a fix).

I've got to admit, as much as I dislike being on the customer team, it's certainly less annoying than working on features, and have constant customer issues interruptions though.

Presumably, if US already has all of the minerals it needs, the minerals' deal is going to do as much good as is current status quo.

After all, why would the US get involved when they don't need the minerals they'd have to lose?

This looks horrible for anything but personal scripts/projects. For anything close to production purposes, this seems like a nightmare.

Wouldn't this be very well mitigated by the use of an air purifier?