Nobody will take care of us. Ever.

We also need a metric ton of opinionated linting to sheep-herd codebases into a smaller amount of possible shapes -- which I'm strongly in favor of and see it as the next iteration (of the concept of a single code formatter a la Rust) because it'll put many other bikeshedding time-wasters to rest, hopefully forever.

To be honest though, it's mostly hypotheses and feelings; nobody has truly figured it out yet -- and if some have, they're keeping the secret sauce to themselves.

But also, everyone says "it's the harness" and almost nobody ever gives good examples, it gets a bit tiring to read everywhere, as if everyone wants to sell a harness to us.

Also what kind of problems did you have with LiveView?

We should never underestimate people's weird desires but this is mostly not it IMO. There was a new generation that felt the need to rebel against old established stuff and of course is now painfully rediscovering why this stuff was established in the first place.

Infuriating to watch, mind you. But also predictable, like watching bots play StarCraft against each other.

It becomes a very heavy and difficult exercise of it walking you through the implementation and the judgment calls it had to make along the way. VERY exhausting.

There's a silver lining though: you do get to gradually clarify a proto project spec and various requirements, but boy does it take time and energy to re-contextualise when the bot tells you that you should make decisions.

Just last two weeks I had to slap Fable, three times, to stop writing 1000-2000 lines of defensive code... because of DB columns I just forgot should be NOT NULL. That was it. Nothing else. I told it that, boom, -4800 coding lines: gone.

LLMs defend the status quo and they regularly lose sight of everything bigger than the current PR they are working on.

I too am gradually making peace with the fact that LLM-maintained code does not have to be 100% readable for humans.

But this is not about readability. It's about the data model. So one concession I am willing to make is: don't care too much about the code _BUT_ manually curate the data model. So far: small wins on iteration turns and code volume producing. Too early to tell but for now I am happy with the results.

What do the EU investors do outside of demanding guaranteed profit with zero risk for them? How many are ready to absorb 10-30 years of new infrastructure investments and play the long game?

If the EU wants to compete, well, here's the global market, right that way. ==>

Get to it. Nobody is actually stopping you.

But if you have no appetite for risk, don't complain when one day you realize you don't have EU alternatives.

Try https://github.com/tomnomnom/gron.

Yet they kind of did. I've limited participation in my libraries with GitHub's setting that nobody who made an account in the last 6 months can do anything in my repos (after some misguided hustler thought they're an easy target and posted an ad).lp

Time's marching forward though. Wonder what will happen after a few more months. We'll have bot spam accounts that are no longer as fresh.

You don't owe the world anything at all. If you're conscientious, then give a little -- here and there. Don't turn it into an unpaid job.

Managers and executives though? Those I do blame. Surely at this point it should be blindingly obvious their current strategy is not working.

After you get comfortable and learn the important idioms, you go through the development loop quite quickly.

Compilation/linking speed can still suck though.

I am tired of only ever being gauged by immediate usefulness. You hiring?

Also when you emphasize "exactly", you are not giving any actual reasons.

Next: proficient engineering managers, not just people who immediately bend a knee to the middle manager.

Oh wait, I went into sci-fi territory again. My bad.

Jokes aside, yes, quite correct. Even frontier models like Fable have very obvious limits.