this is literally the lesson i take from this. always do meetings on tablets

once you reach the stage, the only escape is to give up on it. and move on.

somethings are beyond your control and capabilities

Hi, I hope you are doing good. From my personal experience, complaining about your manager to skip level manager is called Career Suicide.

There is nothing good that can come out of it,, except getting fired.

It is, but “Microsoft runs on trust” they say. They also say the CEO’s inbox is always open, actually the CEO himself says it in the yearly mandatory training video on business conduct. So it should be safe, in theory, to openly speak out in the best interest of the customers, no? Rhetorical question :)

I feel like emailing the CEO in this case is just a no-op, the inbox is gatekeeped by his staff and very unlikely he saw your email.

That said, “inbox always open” means you should come with a problem AND a very well detailed solution. But question becomes if you had a detailed solution that was good, why wasn’t it ran up the org chart with buy in and why did it have to skip to the top.

The answer is “intricate politics and misplaced personal interests.”

But that's part of a great solution... it sounds like you might have had a good technical solution, but that's only half the solution in enterprise. If your technical solution requires another team to completely retool, its not a great solution overall.

it is not. the real world says one thing and does another.

here is how real world tech companies actually function: https://www.seangoedecke.com/how-to-ship/

Yes, there is how things are said to work, and how they actually work.

Most likely, the author was let go in mass layoff, and they forgot about NDA.

NDAs are usually signed when you join the company, not leave it.

Signing a non-disparagement agreement is often a condition for receiving severance, although I'm not sure what MSFT's policy on this is.

The part about prioritizing "aggressive feature velocity" over "core fundamentals" is true.

The push is as insane as push to AI.

At the same time fundamental improvements like migrating to .net core, or reducing logs is actively deprioritised. If it were not for compliance, we would not have any core engineering improvement at all

Honestly, I was not even aware of rust push, probably cause no one in my org could do rust. I am glad we did not move to AKS though

> This creates a secondary deception layer. After infection, running npm list in the project directory will report plain-crypto-js@4.2.0 — because npm list reads the version field from the installed package.json, which now says 4.2.0. An incident responder checking installed packages would see a version number that does not match the malicious 4.2.1 version they were told to look for, potentially leading them to conclude the system was not compromised.

WTF!!!! gaslighting your victims into believing they are not victims. the ingenuity of this is truly mindblowing. I am shocked at such thing is even allowed. like packages should not be able to modify their contents while they are being instaleld.

Vercel owns nuxt and sveltekit, so they do benefit. only nextjs suffers from not being on vite.

vite+ is a cli tool and open source, which is built on top of vite.

void is a deployment platform and sdk which is built on top of cloudflare and vite. void will be paid offerring

This was a big surprise. but a good one!

it is not. lack of plugin support is sufficient to block adoptions among other things.

but it has plugin support? what kind of plugins you mean?

look at plugin api limiation here:

https://esbuild.github.io/plugins/#svelte-plugin

esbuild's plugin support is limited which is why vite had to use rollup for prod build.