Creating a worktree became instant, but the bottleneck shifted from that to git needing to build its index. Claude code runs `git status` in the background, meaning any speed gains are instantly gone.

By default. Generally your primary database is in a completely different failure category than a kubernetes node running an ephemeral workflow pod.

In short: SQLite is not all you need, unless you’re just experimenting don’t actually care about durability, in which case you also need litestream + object storage.

Right.

Classic

Perhaps sharing your take home exercise might be a more useful avenue for feedback?

I’m not sure how large the market is for ASP.NET developers, but the skills you’ve learned so far are more transferable than you think. Try creating some projects with Django or Rails and spread your wings a bit. Don’t be a monoglot.

A portfolio helps, as well as a personal narrative. Being a solo developer for 2.5 years is good and bad depending on the audience. For example it means you don’t have much recent experience working with a team, and I imagine clunky Belfast ASP.NET companies are not exactly hotbeds of entrepreneurial spirit. Maybe look for smaller companies or startups?

Extremely personally, Azure certifications and such things are worthless, bordering on a negative signal depending on the context. But some people/companies may value them.

Saying you think reading “C# in a Nutshell” is a good idea is concerning because you say you’ve got 6+ years of ASP.NET experience. Was this not using C#? Revision is always good, but identifying why you’re not already comfortable with C# is a good starting point.

Build some solo projects with C#, not using ASP.NET, with some artificial constraints (speed, memory, etc). Then smash them. Could be as simple as parsing a 20GB CSV into memory: start dumb and slow then make it as fast as you possibly can. For me this beats a book on data structures.

And are laptops a primary deployment target?

That is still quite a small pool, and there are other network effects preventing any Joe blogs with that much capital from launching an exploitation campaign.

This sets a nice price bar for exploitation. Is someone willing to pay 10+ million dollars to get access to your phone?

The obvious caveat here is that for a lot less than 10 million dollars someone can be hired to hit you with a metal pipe until you give up your passcode.

> click total compromise that can trivially worm to take down hundreds of millions of iPhones simultaneously

Where is the profit motive in doing this? Possibility is one thing, but a realistic threat is another.

No? So it’s not purely a function of disk size.

If you’re not then this seems quite paranoid, bordering on LARPing.

Anything else?

The problem with this take is that it’s stuck in the early 2000’s, where all servers are pets to be cared for and lovingly updated in place.

It’s also circular: you have the same problem with the current model if you don’t have a test environment. And if you do have a test environment, releases can be tested and validated at a much higher cadence.

Walk me through that please