The only possible Revolution I see is not using the DOM. JS + WASM is fast enough, the DOM is not fast enough, or good enough, enough here meaning enough for creating highly dynamic 60FPS experiences. Main issue with leaving it behind is A11Y though.

I care about ops because if the ops are bad it affects how quickly and effectively I can deliver new functionality and resolve issues.

I don't want to do ops, but I will if they're holding back development.

Learning about these kinds of things is one thing motivating me to try for a big tech company job.

I want to build my own company, but I want it to have this kind of tooling, that I don’t fully understand yet.

Sounds really interesting, would love to see it used more.

I don’t know what the conventional wisdom is these days, but speaking for myself, I felt much more equipped to tackle the huge undertaking of being more entrepreneurial after seeing how a really serious software shop is run.

As for getting the big company job, it’s a weird time over like the last two months and the next two months, but this will soon pass.

Everyone hates leetcode interviews. I hated being interviewed in that format, and I hated interviewing in that format. It is what it is. It’s a test like the SAT or LSAT or GMAT or anything, arguably not as hard. It’s basically nothing to do with the job at the lower seniorities. I think people would be less psyched out about it if they viewed it the same as cramming for any other test. A high score on the LSAT doesn’t make you a good lawyer, it’s a loose proxy metric at best, and you game it by studying.

By virtue of a) hanging out on HN and b) hanging out in a thread about Nix you’re clearly curious and paying attention, so go get that marquee job, and take the experience with you when you start your venture! I’ll be rooting for your success!

An alternative is a multi step build, then running with Google’s Distroless https://github.com/GoogleContainerTools/distroless

This has saved me many times. Memory is cheap these days, this should probably be a more common editor feature, on by default.

I wonder if part of why microseconds work for some companies is the hype helps justify the work to management.

> We need to convert to microservices.

Sounds like a cool shiny new approach enabling better scaling and organization.

> We need to refactor this mess.

Sounds like complaining, why is it a mess anyways?

These two things may essentially be doing the same thing, organizing/breaking up the code logically, one just might sound more appealing to management.

There will always be incompatibilities between versions. Ideally the tool would manage its own version, maybe with vendoring. Yarn does this optionally and it works well

At least with this you wouldn’t need to manage versions of the package manager and runtime separately

Well, I can't even run npm install on latest NodeJS LTS version. So, I can't even install yarn to begin with.

npm ERR! Unexpected token '.'

What you talk about last is referred to as documentation driven development or readme driven development

I think it's great for greenfield work. Forget existing solutions, if you were looking for a solution, write out how you'd ideally like it to work, after it's written, figure out if you can create something that works like that

One of the best PMs I have had used to be a dev. The company we were working with used a terrible Jira like piece of software I don't remember the name of, but he had the devs just use Trello. He would go through and update the other thing for stakeholders. Worked great

Browsers should implement setting the preferred scheme per site at some point.

It would also be interesting if they could support more than just light and dark.

Boy I really hope so. As it stands a lot of people implement their own toggles and only use „prefers-color-scheme“ for the initial setting of the theme. Using the plain media query everywhere would be much preferable and actually reduce the amount of CSS needed by a fair amount.