Frustrating that the best solution is still, “well, if that’s important to you, then set that up in your home lab or rent some extra (pet) VMs in the cloud.”
878 karma · joined February 11, 2011
Frustrating that the best solution is still, “well, if that’s important to you, then set that up in your home lab or rent some extra (pet) VMs in the cloud.”
# if >10 then was_created_by_agent = true
$ grep -oP '\p{Emoji}' vulns.md | wc -lI came back to it recently after the Leptos 0.7 release, though, and it’s MUCH smoother.
Still early days for a framework like this, but I think it’s got a lot of magic.
Maintaining and modernizing these critical systems is important work.
Biggest limiter is memory, where the need for it grows linearly with table index size. Postgres really really wants to keep the index pages hot in the OS cache. Gets very sad and weird if it can’t: will unpredictably resort to table scans sometimes.
We are running on AWS Aurora, on a db.r6i.12xlarge. Nowhere even close to maxed out on potential vertical scaling.
You enforce API contracts in a monolith (or any codebase, really) via an at-least-modest amount of typing and a compiler. You diagnose performance issues via any number of tools, prominently including metrics and profilers.
My context for this is a lot of years working with backend languages like Java, Rust, etc. though the same assurances and tooling are available for most every platform I’m aware of.
I was rather skeptical on the value of having this stuff as a shell built in, but it won me over. Very convenient!
I’ve also had the pleasure of working directly with the team at MITRE that owns it on a consulting engagement (we needed some improvements to it) and they are a delight to work with.
(Strongly reminiscent of the Cortex podcast’s “yearly themes”. Which I like! But… I’m not running one of the world’s largest companies, am I?)
I spent some time going through all of their basic examples in Rust, which was just delightfully silly.
Doesn’t it seem reasonable to you to design and engineer cherry pickers such that the bucket can’t be moved unless a safety harness is attached?
That has to be a typo, right? Or sarcasm?
I weep for what we’ve all done to the beautiful speed and simplicity of the web.
versus:
“The plan’s rates have gone up.”
(Since I use sway on Ubuntu, rather than gdm, I’d argue it’s a capital offense, but YMMV.)
The losses can be somewhat mitigated. As mikewarot’s comment here hints, you can slow down the meetings and take care to encourage everyone’s thoughtful participation. It requires a lot of intentional awkwardness, but I actually hope I carry this skill back to in-person meetings. “Let’s give folks a minute to think about that before we move on,” and “what are your thoughts Sally and Bob?” are useful phrases.
There are many important positives to virtual meetings. I work with a couple of new parents whose lives are greatly improved by being able to attend meetings while keeping an eye on their littles. Meetings can be much more casual and that can help us open up to each other. Meetings are often taken outside when the weather is accommodating, which is just incredibly refreshing. Folks are less able to randomly interrupt my workday just by walking by. Most importantly, time lost to commutes is returned to us and our families.
There are also negatives he left out. The biggest, by far, is just how many more meetings everyone is scheduling. Without the added back pressure of commutes, conference room availability, and real lunch breaks… everyone has gone meeting-crazy. It’s really hurting my office’s productivity.
On balance, though? Remote wins. By a mile.
Clock skew is an insidious problem: things may look like they’re working, but they’re not. Given all of the clock bugs out there it’s sometimes not even safe to rely on the clock on a single machine. Across multiple machines it’s hopeless.
Please note that this doesn’t apply if you have a fancy time source like Google uses in their fancy cloud DB (whose name escapes me at the moment).
And that’s just one example out of many.
Your observation is, in general, quite correct! Back in the 80s or thereabouts, the conservative administrations started a MASSIVE shift towards outsourcing of federal government work. This was for all of the usual, largely shortsighted and inaccurate “cost saving” and “efficiency” reasons.
The worst part of it is that they outsourced ALL of the technical expertise in many agencies, leaving them without the expertise needed to effectively manage the work being outsourced.
This is starting to shift, thanks to recent efforts like the USDS, 18F, and such but it’s the work of decades to really change. Come join us!