How do they allocate headcount to different teams? How often is that rebalanced?

Claude does an okay job of translating from other languages into Ada. It works especially well if you write the specification (.ads) file and let it write the body (.adb)

Ada’s strictness about types and a preference to allocate on the stack rather than the heap means more bugs are caught at compile time. Claude Code is really good at iterating on compile time errors without much user intervention.

Please don’t scrape my site.

The complexity you introduce trying to achieve 100% uptime will often undermine that goal. Most businesses can tolerate an hour or two of downtime or data loss occasionally. If you set this expectation early on, you can engineer a much simpler system. Simpler systems are more reliable.

We had single-datacenter resiliency (meaning n+1 on power, cooling, network + isp, servers) and it was fine. You still need offsite DRS strategy here - this is one of the things having that hybrid cloud is great for: you can replicate your critical workloads like databases and services to the cloud in no-load standby, or delta-copy your backups to a cheap cloud provider for simplified recovery in a disaster scenario (ie: entire datacenter gets taken out). The cost of this is relatively low since data into the cloud is free and you're only really incurring costs in a disaster recovery scenario. Most virtualized platforms (veeam etc) support offsite secondary incremental backups with relative ease, recovery is also pretty straightforward.

That being said I've lost a lot of VMs on ec2 and had entire regions go down in gcp and aws in the last 3 years alone, so going to the public cloud isn't a solves it all solution - knock on wood the colo we've been using hasn't been down once in 12+ years.

Much less expensive too.

I think in general that expectation is NOT acceptable though especially around data loss. Because the non engineering stakeholders don't believe it is.

Engineers don't make decisions in a vacuum, if you can manage the expectations, good for you. But in most cases that's very much an uphill battle which might make you look incompetent because you cannot guarantee no data loss.

Could work well as an Onshape App.

Looking at the build PDF, you'd need a pretty large printer to do a single piece like that. Would need to split it into a few panels and have some sort of joinery or fasteners to make it fit on most consumer printers.

This (breaking it up and adding the "jointery") is handled right in the slicer now, easy peesie.

What do you mean by this? I’ve only used bambu’s slicer and never seen anything to indicate it can automatically add “jointery”?

You're going to love it!

https://youtu.be/zTZOH6XkUPU?si=MoOx8Hqy6xvMKvn6

Huzzah! Thanks for that!

A directory called “git” with a bunch of bare repos accessed over ssh. You don’t need to make this complicated.

but then you don't have the pull request feature, do you?

You push a branch and send an email.

Someone even made a simple walkthrough: https://git-send-email.io/

Software was developed before the pull request. Typically proposed diffs were emailed around. Presumably this is what the pull request is trying to emulate.

The anti-UI people want to use e-mail and command line tools.

It’s not a direct equivalent to pull requests because it lacks all of the easy history, inline commenting, comment status tracking, and ease of use, among other things.

Agreed, but for laptops it’s nice to keep a copy of the DVD iso on disk and in your apt sources so that you can install stuff offline.

Thank you.

Maybe they should design an API that doesn't require constant polling for updates? Pubsub isn't exactly new technology.