Logo

dev-resources.site

for different kinds of informations.

Finding What Drives You

Published at
1/13/2025
Categories
ai
career
softwareengineering
Author
stuffbreaker
Categories
3 categories in total
ai
open
career
open
softwareengineering
open
Author
12 person written this
stuffbreaker
open
Finding What Drives You

Every year there are predictions that "'x' will massively change 'y'" or "'a' will be the death of 'b'".

AI continues to be a disruptor (for better or for worse) in many industries and one of the 2025 predictions is that "AI will be the death of the software engineer". As a software engineer, my knee-jerk reaction is to balk at the idea that AI could replace my craftsmanship. I love building software and AI appears to be positioned to threaten my livelihood and my passion.

There's no putting the proverbial AI toothpaste back in the tube. It's here to stay and here to change things. Despite that, I don't think this is an accurate prediction, but my pragmatic side made me pause and think, "Well, what if...? Would I be ok? Would I be happy? Could I find a job that I enjoy as much as I like this?". To find some sense of safety in this, I've had to do a little self-reflection to understand why I love what I do.

Finding My Drive

After I graduated high school, I was in South Korea teaching an English lesson. One of the stories in the book we were using was the allegory "The King's Highway". It's short, so I've included it here for your viewing pleasure and to help provide context.

The King's Highway

Once a king had a great highway built for the members of his kingdom. After it was completed, but before it was opened to the public, the king decided to have a contest. He invited as many as desired to participate. Their challenge was to see who could travel the highway the best.

On the day of the contest the people came. Some of them had fine chariots. Some ran along the highway and others rode horses, mules, or donkeys.

People traveled the highway all day, but each one, when he arrived at the end, complained to the king that there was a large pile of rocks and debris left on the road at one spot and this got in their way and hindered their travel.

At the end of the day, a lone traveler wearily crossed the finish line and walked over to the king. He was tired and dirty, but he addressed the king with great respect and handed him a bag of gold. He explained, "I stopped along the way to clear a pile of rocks and debris that was blocking the road. This bag of gold was under it all. I want to give it to you so you can return it to its rightful owner."

The king replied, "You are the rightful owner."

The traveler replied, "Oh no, this is not mine. I've never known such money."

"Oh yes," said the king, "you've earned this gold, for you won my contest."

"He who travels the road best is he who makes the road smoother for those who will follow."

The lesson in this story struck me deeply. It has stuck with me and I believe it has influenced my actions ever since. While I get paid as a software engineer, I don't get paid for any of my open-source projects, speaking events, or volunteering at hackathons. I'm not saying I'm above any of that, so if you'd like to pay me for those things, I'll gladly take your money. πŸ˜‰ What I am saying is that I would do these things whether I was getting paid or not because I like to help smooth the road for other travelers.

What does this mean?

Making the road smoother for others is a driving force for me, and software engineering is a mechanism for me to express that. I don't believe this is the sum of who I am, but this is a way I feel I can provide value.

I have no plans to stop software engineering any time soon, but this helps me disassociate my identity from my profession. It now frees me to be open to the idea of growing beyond my trade and pivoting to something else if needed. This also allows me to feel less threatened by AI and opens me up to opportunities to embrace changes it may bring that could improve my existing experience.

Find your drive and keep making cool shit!

softwareengineering Article's
30 articles in total
Favicon
Mastering Essential Software Architecture Patterns: A Comprehensive GuideπŸ› οΈ, Part 6
Favicon
Mastering Essential Software Architecture, Part 6 IS FINALLY OUT !!!!
Favicon
Stop Turning Your Code Into a Therapy Session for Past Bugs
Favicon
Things About Contexts in Front-end Projects
Favicon
πŸš€ Week 3 Recap: Learning in Public – Software Engineering with DevOps πŸš€
Favicon
5 Advanced Python Web Crawling Techniques for Efficient Data Collection
Favicon
7 Essential React Accessibility Strategies for Inclusive Web Apps
Favicon
5 Advanced Java Multithreading Techniques for High-Performance Applications
Favicon
Microsoft Project in 2025
Favicon
The System of UI Components in Front-end Projects
Favicon
Finding What Drives You
Favicon
Journey to Clean Architecture: Wrestling with a 10k Line Flutter Legacy Codebase
Favicon
An Initiation to Domain-Driven Design
Favicon
Things About Modules in Front-end Projects
Favicon
Binary embedding: shrink vector storage by 95%
Favicon
6 Advanced Python Techniques for Efficient Text Processing and Analysis
Favicon
Mastering CSS Grid: Expert Techniques for Responsive Web Design
Favicon
7 Essential Design Patterns for JavaScript Developers: Boost Your Coding Mastery
Favicon
CDNs in Distributed Systems: Beyond Caching for Better Performance
Favicon
Patterns of Directory Structure in Front-end Projects
Favicon
Emergent Software Principles I've Learned
Favicon
What I Learned After Coding for 24 Hours Straight
Favicon
Mastering Go's encoding/json: Efficient Parsing Techniques for Optimal Performance
Favicon
Reason for Talking About Front-end of Web-based Management Systems
Favicon
7 Powerful Python Libraries for Advanced Data Visualization: A Developer's Guide
Favicon
8 Key Strategies for Building Scalable Microservices Architecture
Favicon
The System of Front-end UI Components
Favicon
How a Software Developer's Life Is More Stressful Than You Think
Favicon
My Journey as a First-Year Software Engineering Student
Favicon
Code That Belongs in a Museum, Not a Repository

Featured ones: