Learning New Skills: The Engineering Mindset for Growth

Learning a new skill—whether it's pixel art, touch typing, 3D modeling, or a programming language—is a long-term investment that pays dividends for life. For engineers, this is especially relevant: our field demands constant adaptation, and the ability to learn effectively is a meta-skill that compounds over time.

The Real Cost of Learning

Most people underestimate the initial discomfort. When you start something new, you will not feel good. In fact, it often sucks. Your brain and muscles get tired, and performance degrades toward the end of a session. This is normal—it's your system gathering data for overnight processing. Sleep is when improvements actually happen.

If you work 80-hour weeks or have infants bouncing around like screaming DVD logos, this might not be the right season. But if you spend time scrolling your phone while half-watching Netflix, you have the bandwidth.

Practical Advice for Engineers

Start small: 30–45 minutes of deliberate practice per day. Longer sessions just ingrain mistakes. Focus on the basics—don't jump into advanced topics before you're ready. Rushing doesn't accelerate progress; it just builds a shaky foundation.

Resources are abundant: YouTube, Reddit, wikis, books. Avoid information overload and sales funnels. Find a starting point that works for you and go at your own pace.

The Plateau of Mediocrity

After climbing Mt. Awful, you'll hit the long logarithmic plateau of being a mediocre intermediate. At this stage, you're good enough to use the skill practically, and incidental practice becomes easier. Most people never make it this far, but if you do, the real growth begins.

Learning anything is a long-term project. Nothing meaningful changes in a day, but in months or years, a lot can happen. This sense of control over your circumstances is invaluable—especially in a field as dynamic as software engineering.