qes

There is compared to shared memory.

If you actually need to scale and don't have an in-memory cache layer over Redis you're likely going to get hurt.

30 seconds and I can be quite sure there are no ads, malware, popups, and impeccable video quality.

They're all still being seeded with enough bandwidth to max my 100+ Mbps cable connection, too.

It's just a configuration file for a formatting library that someone else(s) wrote.

Running on how many CPU cores? Were you writing code for a supercomputing cluster? Otherwise for what kind of system could 10,000 threads possibly be an ok strategy?

That said, very few refrigerators out of the large number of available models (many more than say dishwashers or clothes washer/dryers) have the same interior layout.

Even two nearby models from the same manufacturer with minor feature differences will have significantly different layouts, to the point that you can't just choose to get a fridge with or without feature X without also choosing between differences in the likely more important aspect of layout.

Only if you're completely clueless.

I'm the lead developer at my company, who I've been with for 10 years. In my late teenage years I ran my small own software company for a couple years and then a small custom pc builder company for a couple years. I've done manual labor at times. I built furniture for a while.

I'm a bit of a homebody, and feel lazy at times, but thinking also of the list of personal hobbies and projects I've done in the last 20 years, I can't really say I'm very lazy at all.

I'm also an active father, and polyamorous and in two long-term relationships.

In my non-legal mid-western state, quality indoor (I suppose you could call it spectacular) fetches $300/oz all day long.

It was crazy. If you didn't buy a new CPU just about every year you were woefully behind.

The last two CPU generations I bought made it almost 5 years, and frankly there wasn't much difference from upgrading.

We integrate with dozens of 3rd party APIs, making over 10M external HTTP calls per day. That leads to a lot of variability in runtime characteristics.

No they don't.

SS316 is an option, but not the most common. NI200 is still by far the most common coil material.

Nailed it.

Huh, that's weird, because I've been writing in Angular & React and using the same basic libraries for years now. And before that it was jQuery and Handlebars and a lot of the same basic libraries for years.

I've made two large shifts in JS development over a decade.

Not sure why you seem to need to switch every month?

I still primarily code but also do lots of long term tech strategy like cloud? and which, as well as business planning with the rest of our leadership level, hiring, training new devs, keeping all the devs up to date with new stuff, breaking down and delegating work, reviewing code, monitoring & alerting and understanding a system that's practically a living organism and being able to anticipate trouble spots rising, planning and executing what are sometimes multi-year efforts (e.g., significantly refactoring major parts of a 10+ year old code base).

Personally, I like it, though it has its difficulties. It also makes me an exceptionally valuable person for this size of company - big enough to really need breadth and depth of experience, but not in a position to have several tech people with a decade or two of experience. Find the right company (I was lucky to) and it's a golden ticket.

I last upgraded my CPU when it was nearing 6 years old, and I could barely tell the difference. My current CPU is nearing 5 years old, and if it wasn't for some of the enticing stuff AMD's recently put out, a CPU update wouldn't even be on my mind at all yet - in fact I was surprised to recently notice it had been more than 4 years since I last bought a workstation CPU.

I expect I'll buy 2 workstation CPU updates between now and 2030, 3 at most. and even that would take something special to drop in the early-to-middle of my normal timeline.

I used to work there, albeit years ago, but the amount of misinformation spewed by "product specialists" rivaled politics.

As SF? Are you making, say, over $400K in Atlanta?

Sure, IDE's are easy (though many people use multiple IDE's and/or editors across multiple machines).

I've also got a couple diff tools, a few VCS's, also the online parts of VCS like web-based pull request review UI's.

Tabs also tend not to play as nice with vertically aligned elements, if you prefer that for things like say the '.' on multi-line chained method calls, or longer function parameter lists.

Microsoft's also been developing and using ASICs in Azure. I guess they're just not contracting NVIDIA for any part of the process.

I find their sales tactics and pricing strategies aggressive and unfriendly.

In my experience there have been plenty of significant refactorings that simply would not have been done if we didn't allow ourselves to get into this state where there is simultaneously an old and a new way of doing something.

Especially if it's an area that sees frequent addition - it's not helpful to have people constantly adding code in the old way while off to the side people are trying to create a new way and completely finish switching everything over to it before integrating.

Managing risk and balancing other active tasks in the pipeline also push towards integrating smaller pieces over time while multiple ways of doing the same thing exist.

But you need to have organizational continuity, which can be rare when everyone is trying to hop jobs for better salary every couple of years.

I was just ranting about the dialer UI they added to the web UI, but after a few days they updated it so that it auto-hide if your viewport is narrow enough.