> logging into MS Teams

I mean, this is one application nobody should ever log into!

That's nice.

I, however, like getting my paycheck, and so I have no choice.

Of course. But I suppose you run Teams on a company provided/managed, or at least paid for by the company, device?

Just don’t use that machine for anything private.

Is anyone using their private devices for work? (Also there is teams for Linux and on the web, if that is not prevented by the policy of your org.)

In the startup world, BYOD is/was exceedingly common. All but two jobs of my career were happy to allow me to use my own Linux laptop and eschew whatever they were otherwise going to give me.

Obviously enterprises aren’t commonly BYOD shops, but SMBs and startups certainly can be.

… whether the people who would do such BYOD things are at all likely to be Windows users who care about this Bitlocker issue, is a different debate entirely.

Then the founders do something really stupid, and the law decides that your equipment may be evidence.

Unless you're a founder, you should always use company provided equipment.

I know BYOD was common (although getting a fully specced MacBook Pro was often one of the “perks”), but typically you did get (some) budget or reimbursement for using your own device. So in a sense the company was paying for your device which allows you to buy a dedicated machine.

I also notice that it helps in segmenting in the brain to use separate devices for private and business use.

I’ve been diving down the BYOD rabbit hole recently. At enterprise scale it’s not “hook in with your vpn, job done”, it’s got to be managed. Remote wipe on exit, prove the security settings, disk encryption, EDR.

What this means for the user is your personal device is rather invasively managed. If you want Linux, your distro choice may be heavily restricted. What you can do with that personal device might be restricted (all the EDR monitoring), and you’ll probably take a performance and reliability hit. Not better than just a second laptop for most people.

All of that won't stop anyone from exfiltrating whatever they want to exfiltrate.

Of course, but like so many of these things, it’s about compliance audits and insurance. Actual effectiveness is a distant concern.

Any good reading tips on doing managed Linux devices in a startup/SMB?

>All but two jobs of my career were happy to allow me to use my own Linux laptop

But they wouldn't have provided you with a corporate device if you asked?

teams works fine in website form for me because it IS a website (that uses an extra ~1gb of ram running as a desktop app because its also a separate browser)

Reportedly, that’s how they’re making the Start Menu now, too.

That means you’ll do that on the work machine provided by your employer, not on your personal machine.

Teams in the browser, on Linux. That is reasonably harmless.

>I personally can't accept shipping unreviewed code. It feels wrong. The product has to work, but the code must also be high-quality.

Sadly review isn't enough. I just today I found some code that I reviewed 2 months where the developer clearly used an agent to generate the code and I completely missed some really dumb garbage the agent put in. The agent took a simple function that returns an object with some data and turned it into a mess that required multiple mocks in the tests (also generated by the agent).

The dev is a junior and a clear example of what is to come, inexperienced people thinking coding is getting an agent to get something to pass CI.

The tech debt is accelerating exponentially!

Those people on the boeing flights would have appreciated a little more of the correct motivations.

Instead they got McDonnell Douglas'd

As it turns out the motivations matter way more than you might think.

Another key difference is that wood itself has built in visual transparency as to the goodness of the solution - as it is pretty easy to figure out that a cabinet is horrible (I do get that there are defects in wood joining techniques that can surface after some time due to moisture, etc - but still, lot of transparency out of the box). Software has no such transparency built in.

The advantage of hand coded solutions is that the author of the code has some sense of what the code really does and so is a proxy for transparency, vibe coded solutions not so much.

I mean, it is 2025 and still customers are the best detectors of bad software over all quality apparatus to date.

Now we have LLMs, the Medium Density Fiber Board of technology. Dice up all the text of the world into fine vectorized bits and reconstitute them into a flimsy construct that falls apart when it gets a little wet.

You want to pay me bank to rubber stamp bad code? Weird flex but alright!

3. ...

4. ...

5. Profit!

If your competition figures out a way to cut overhead by 10% and you don't, they win. This is the normal outcome between similar businesses

The only thing that will save RTO companies now is graft and corruption.

I'd love to. First you need to get Tim Cook to stop sabotaging mobile web.

I wonder how better DOM support would help a rust web application frontend framework like Leptos (https://leptos.dev)? Maybe a smaller WASM payload?

>(Shown above: my earnings from this bug.)

I lol'd!