bGl2YW5j

This is really good perspective and an interesting story, thanks for sharing.

What do you reckon would work well for Aus?

I'm Australian and am increasingly ok with this approach. I'm growing slowly out of a protectionist mindset, toward one of cautious, and considered collaboration. Singapore follows this approach and it has worked well for them so far.

This is awesome. It's sad that examples like this are few and far between.

I reckon there's a limit to how long this abstraction can go on before not understanding underlying mechanisms will seriously hamstring you.

I very much agree! It feels like it's going to be exceptionally challenging in the coming years to convince non-technical people of the value of true SWE; by that I mean, SWE is not just coding, it's everything around that too.

I've also been loving the speed Claude has enabled me to move at, and now agree that the coding part of SWE has become LLM-wrangling instead. I now see interacting with an LLM, to build all parts of software, as the new "frontend".

Following this idea, what do people think "backend" work will involve? Building and tweaking models, and the infra around them? Obviously everyone will shift more into architecture and strategy, but in terms of hands-on technical work I'm interested in where people see this going.

I like the analogy and will ponder it more. But it didn't take long before the article started spruiking Kasava's amazing solution to the problem they just presented.

Yes, but whether they admit it or not, as humans subjectivity, whether informed by culture, opinion, experience, etc, creeps in. There's also variation in how a judge applies objective assessment to law; my interpretation of law may be different to someone else's.

"Outperforms" ... how can performance be judged when it doesn't make sense to reduce the underlying "reasoning" to a well-known system? The law isn't black and white and is informed by so many things, one of which is the subjectivity of the judge.

I reckon this opinion is more prevalent than the hyped blog posts and news stories suggest; I've been asking this exact question of colleagues and most share the sentiment, myself included, albeit not as pessimistic.

Most people I've seen espousing LLMs and agentic workflows as a silver bullet have limited experience with the frameworks and languages they use with these workflows.

My view currently is one of cautious optimism; that LLM workflows will get to a more stable point whereby they ARE close to what the hype suggests. For now, that quote that "LLMs raise the floor, not the ceiling" I think is very apt.

LinkedIn is full of BS posturing, ignore it.

This is a really cynical take. People work differently and get value from different things. It’s probably safe to assume most aren’t virtue signalling about writing.

Great point about the conflation. This makes me realise: for me, writing code is often a big part of thinking through the problem. So it’s no wonder that I’ve found LLMs to be least effective when I cede control before having written a little code myself, ie having worked through the problem a bit.

I like Nord Dark because it uses only 3 colours. It’s available as an extension.