scrobble.life
Snapie

Thinking of frameworks, AI and two kinds of Devs

I was reading one of those posts stained with bitterness. A post from a Senior Developer resisting, painfully rejecting, the current status quo.

image.png

To him, the very idea that so many people are now using AI to code seems to hurt his soul, and he's concerned that frameworks will go away.

What are frameworks? I can almost hear you asking.

Without getting too technical, but to make the point clear, frameworks are layers of software built and designed to make working on a specific technology a lot friendlier to us humans.

In other words, frameworks that I'm sure you've heard of before, like React or Angular, may very well become less relevant to the average human developer. Maybe they will eventually disappear altogether, an extinction of sorts, as he puts it.

I guess I'm tempted to believe this to be the case.

After all, quality of life for developers, the concept at least, is very much a whole different conversation. With the focus shifting toward AI tooling and efficient automated workflows, who would put more time and money into making developers happy?

Happy here being a word that changes meaning in the current timeline.

With that said, and fully acknowledging this developer's point, I don't think he's correct.

I don't think frameworks are going away.

I think they're changing hands.

After all, AI is largely fed by us. It is trained on the structures, language and knowledge we've created. In that sense, you could say, and you would not be exaggerating too much, that we are AI, or that AI is us.

Frameworks aren't just conveniences. They are structures and constraints that make complex problems manageable. They give us patterns, abstractions and guidelines that allow us to build things without having to reinvent the wheel every five minutes.

And that's not something AI suddenly makes unnecessary.

If anything, I think frameworks will simply evolve once again.

For decades, we've been building abstractions so humans don't have to worry about everything underneath them.

Assembly gave way to higher-level languages. Libraries gave us reusable pieces. Frameworks gave us structures. APIs gave us interfaces into increasingly complicated systems.

And now AI is becoming another layer of abstraction.

A new kind of client has entered the store, and he's perfectly fine with a simplified syntax.

Actually, he's perfectly fine with syntax that humans might barely see at all.

The more I think about this, the more I fall into the notion that we're walking head-on into a world where software is built by two distinct audiences.

The ones with car payments and mortgages.

And the ones that measure their outputs in tokens.

Who'da thunk it?

Not me... not me.

But here we are.

MenO

Comments · 7

  • @novacadian(66)· 2d

    Any technology comes with pros and cons. My feeling is that AI is bringing empowerment to the average user.

    Other than the doomers that see The Terminator in AI's growth, most others that decry against it (like programmers) remind me of the attitude of Banks against crypto. It threatens their monopoly.

    Imagine the near future with a local version of AI running on your laptop and to be able to look over your shoulder and advise you about everything from car repair to household maintenance. That is about as self sovereign as a hardware wallet in my opinion.

  • @bozz(83)· 2d

    I've been playing around with some AI coding lately, but I definitely wouldn't take any credit for anything that has been created. I just wrote a post yesterday about an app I had it create for me. It's pretty impressive, but I can understand the push back on it.

  • I also think of AI as another abstraction. A framework gives you a metaphorical home for your work. You don't need to worry if the AI put in plumbing or electricity when you didn't think to ask for it. So, facets such as logging, security and accessibility come with your framework.

    But, who knows where this will go? Who needs an OS? It's a framework. Just tell the AI to write an app that boots on your hardware....

  • @waleedraza(60)· 2d
  • @nicklewis(70)· 2d

    I’m very much caught up in all of this. I use AI as a tool to help me learn new things, rather than vibe coding, I like to vibe learn! My day to day work involves, probably much the same as you, an instance of VS Code running with a terminal panel open, a Claude panel running and the code itself. If working with a new piece of code, it helps me navigate around it and can help me understand it faster, especially if working with a new framework or language.

  • @mayt(75)· 2d

  • @uniquey(55)· 2d

    There is clearly a divide between developers who take advantage of AI to avoid the effort of learning and those who utilize it to enhance their existing skills. It is the engineers who understand how frameworks do things regarding security, edge cases, and state who can effectively review and deliver AI-enhanced code.