Kevin Gulledge

Front-End Developer exploring the future of AI, work, and tech. Building | Learning | Asking Questions
Dad of 3 humans | Coffee fueled ☕

[Kevin Gulledge @kev_the_webdev]

Hi, I’m Kevin 👋

Front-End Developer working in eCommerce.

I share things I learn about:

• Magento
• CRO & UX
• Web performance
• Debugging real production issues

Also a dad of 3 and fueled by coffee ☕

Follow along if you're building for the web.

[Kevin Gulledge @kev_the_webdev]

@dev_maims But? But? you work with computers right? so you should know all this? 🤦🏼‍♂️😂

[Kevin Gulledge @kev_the_webdev]

Most coding roadmaps are wrong.

They focus on languages.

HTML → CSS → JavaScript → React → etc.

But the real skill developers need is problem solving.

The best developers I know can learn any language quickly.

Because they understand systems.

[Kevin Gulledge @kev_the_webdev]

@BestofDem_szn Hi 👋🏻

[Kevin Gulledge @kev_the_webdev]

@vibeonX69 we haven’t talked about putting a “name” on it yet but yes that would be correct. 😂

[Kevin Gulledge @kev_the_webdev]

Nvidia just announced a $26B investment into open AI models.

This could be huge for developers:
• More open weights
• More local inference
• Less reliance on closed APIs

The AI wars are shifting from models → ecosystems

[Kevin Gulledge @kev_the_webdev]

@Tech_girlll Depends on what type of project I am working on.

[Kevin Gulledge @kev_the_webdev]

The developers who will struggle most with AI are the ones who only learned syntax.

The developers who understand systems, architecture, and problem solving will become even more valuable.

[Kevin Gulledge @kev_the_webdev]

After years in development, one thing has always been true:

The hardest part of programming isn’t writing code.

It’s understanding the problem.

AI is getting very good at generating syntax, but it still relies on someone who can break down a problem, understand the system, and guide the solution.

The future developer isn’t just a coder.
It’s a problem solver who knows how to work with AI.

[Kevin Gulledge @kev_the_webdev]

Good question.

AI will definitely change junior developer roles, but I don’t think it removes the need for them.

One thing I don’t see discussed enough is problem solving.

Coding has never really been about typing syntax — it’s about understanding a problem, breaking it down, and deciding how the system should work.

AI can help generate code, but it still needs someone who understands the problem space.

Developers who can think critically and solve problems will always have value.

[Kevin Gulledge @kev_the_webdev]

@Prathkum @csaba_kissi Ah memories, good memories. 😂

[Kevin Gulledge @kev_the_webdev]

@vibeonX69 AI can generate code.

But it takes experience to know where that code belongs, how it integrates with a system, and what breaks in production.

Current studies show AI code is correct only ~30–65% of the time.

AI will assist developers — not replace them.

[Kevin Gulledge @kev_the_webdev]

Everyone is celebrating AI replacing workers like that’s the whole story.

But here’s the real economic question:

If AI replaces enough people, and fewer people have wages, who buys the goods and services?

An economy doesn’t run on production alone.
It runs on purchasing power.

If the gains go only to capital owners while labor income falls, demand eventually breaks.

That’s not anti-AI.
That’s basic economics.

[Kevin Gulledge @kev_the_webdev]

@ManOfFocus_ Deeds, not words.

[Kevin Gulledge @kev_the_webdev]

@lunarfq 👋🏻 hello

[Kevin Gulledge @kev_the_webdev]

This is great, but I’m curious about your thoughts on the shift happening in search right now.

Google’s AI summaries reportedly capture 60%+ of engagement, meaning many users never click traditional results anymore.

Are we moving from SEO → GEO (Generative Experience Optimization) where the goal becomes being referenced by AI rather than just ranking?

With 20B+ voice searches monthly and AI interpreting images through alt text and structured data, discovery itself seems to be evolving.

[Kevin Gulledge @kev_the_webdev]

@Steezehuman You didn’t have to call me out like this.

[Kevin Gulledge @kev_the_webdev]

@DynamicWebPaige @AGIHouseSF We can simulate a fruit fly brain…

but we still can’t build a machine that washes, dries, folds, and puts away laundry.

Feels like our priorities might be off.

[Kevin Gulledge @kev_the_webdev]

@cb_doge Everyone out here arguing about which AI is better…

and I’m just trying to get CSS to behave the same in every browser.

[Pratham @Prathkum]

Writing code by hand used to be where developers found clarity.

While typing out every line, you naturally thought about the data flow, edge cases, naming, structure, props, etc. Bugs often got caught before the code even ran.

Now, AI generates code at lightning speed.

If your thinking isn’t clear, you will spend your day debugging AI hallucinations instead of solving actual problems.

Clear intent is the bigger bottleneck now.