Is Learning Dead?


When I was first learning how to code, I spent tens - maybe hundreds - of hours glued to online courses. Video after video. Tutorial after tutorial.

Once I “made it,” though, I found myself more drawn to books. Maybe it was because my employer stopped paying for PluralSight. Maybe because I suddenly had an O’Reilly subscription. Or maybe because I realized video pacing never matches what I need - either way too slow (wasting hours) or too fast (forcing me to rewind endlessly, or drop the playback speed to 0.5x).

These days, I don’t pay for either. AWS won’t reimburse for O’Reilly (Seattle residents get it free through their library - unfortunately, I’m not one of them). And while we do have access to AWS SkillBuilder, it feels more like marketing fluff or entry-level intros - stuff I can figure out on my own just by clicking around.

To be honest, I haven’t read a technical book or followed a structured course in over two years. I just read the docs. And when I need clarity? I ask ChatGPT.

Which brings me to the real question: Are tech tutorials even necessary anymore?


Experimenting with AI Learning

Last week, I thought: maybe it’s worth learning about AI through structured courses, since we’re already using it so much. So I tried “ChatGPT Prompt Engineering for Developers” and went through AI Coding University on Cline’s site.

And what happened? I realized I didn’t learn much that I didn’t already know. Because I’d already learned the hard way - by doing.

Still, there was a part of me that liked the structure. Even if I didn’t immediately need every feature, at least I came away knowing those features exist. Sometimes, awareness is its own kind of learning.


When Structure Still Matters

So no, I’m not done with courses or books forever. But I think they serve a narrower purpose now:

  1. Starting something new - When you have no idea where to begin, a course can guide your first steps.
  2. Expanding your breadth - When you want to know what you don’t know, structure helps you discover blind spots.

Outside of those cases? Documentation, experimentation, and AI explanations usually get you there faster.


The Bigger Question

Maybe the real question isn’t whether we should keep learning - that answer is obvious. We should.

The question is: What’s worth learning in a structured way - and what’s better learned by doing?

So I’ll turn it back to you: What are your go-to sources for learning these days?

Cheers!

Evgeny Urubkov (@codevev)

600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246
Unsubscribe · Preferences

codevev

codevev is a weekly newsletter designed to help you become a better software developer. Every Wednesday, get a concise email packed with value:• Skill Boosts: Elevate your coding with both hard and soft skill insights.• Tool Tips: Learn about new tools and how to use them effectively.• Real-World Wisdom: Gain from my experiences in the tech field.

Read more from codevev

Last week, I ran into this tweet: the tweet It kinda triggered me. Why would someone pay $0.40 per secret per month when you could just use AWS Parameter Store and store them as SecureStrings FOR FREE? That’s what I use for oneiras.com, so I was determined to find out if I’d missed something. Am I unknowingly paying per secret? Or is there actually a reason to use AWS Secrets Manager instead? Turns out, there are a couple, but only if you really need them. The Big One: Automated Secrets...

Well, the global AWS outage happened just four days after I sent a newsletter about COEs and how “nobody gets blamed.” Great timing, right? I wish I could’ve been in the weekly global ops meeting to see the temperature in the room. That’s the one where teams present their recent issues and learnings. I can only imagine how lively that one must’ve been. Turns out the culprit was a DNS failure in the Amazon DynamoDB endpoint in the us-east-1 region. And while that sounds region-specific, it...

Someone pushes a new feature to prod the same day you go on-call. Hours later, your phone goes off - not a gentle buzz, but a full-blown siren that could wake up the entire neighborhood. You open the alert, and it’s for a feature you didn’t even touch. Maybe it’s unhandled NPEs, maybe something else. Doesn’t matter. You’re the one on-call, so it’s your problem now. When Things Break In those moments, it’s usually faster to just debug and fix it - even without full context. I’m pretty good at...