u/elizabethfraser123

Most career advice starts with questions like:

What pays well?

What's growing?

What should I learn?

the idea I came across asked a different question: What kind of work makes you lose track of time?

not because every enjoyable activity should become a career, but because it's a clue. If you naturally spend hours writing, designing, coding, teaching, or solving problems without constantly checking the clock, there's probably something worth paying attention to. the second part of the advice was just as interesting. Once you've found that thing, stop chasing motivation and build a routine around it.

Three focused hours every day beats one weekend of burning yourself out. That's probably the part we underestimate. Careers usually aren't built through huge bursts of effort. They're built through boring consistency that compounds over years. i don't think "follow your passion" is always realistic.

but I do think it's worth noticing the work that gives you energy instead of draining it. That seems like a much better place to invest your time than simply following whatever happens to be trending.

i'm starting to think that's the wrong question. AI can already generate code, explain APIs, refactor functions, and even fix bugs surprisingly well. but the more code we generate, the more we have to understand.

Someone still has to decide if the architecture makes sense. Someone still has to review trade-offs. someone still has to catch edge cases, think about security, figure out why production broke at 2 a.m., and decide whether the AI's solution is actually the right one.

in a weird way, AI doesn't just generate code. It generates more responsibility. The barrier to building software is definitely getting lower, and I think that's a good thing. More people can prototype ideas, learn by doing, and ship projects that would've taken weeks before. but lowering the barrier to writing code isn't the same as lowering the bar for good engineering.

Maybe that's the real shift.

Less time fighting boilerplate.

More time making decisions.

I'm curious whether other people are seeing the same thing, or if you've noticed AI changing the way you work in a completely different way.

your resume is full of things you've already done. But when someone interviews you, they're usually trying to answer a different question. "can I picture this person succeeding here?"

That's why two people with similar resumes can have completely different interview outcomes. one person spends the whole interview proving they were good at their last job. The other helps the interviewer imagine what they'll contribute to the next one. That shift changed the way I look at interviews.

they're not just about defending your past.

They're about connecting your past to someone else's future.

i read that in a discussion a while back and it made more sense the longer I thought about it. The first project is mostly about getting something to work. The second project is where you start questioning everything you did the first time. why did I structure it like this? why is this component impossible to reuse? Why did I hardcode everything?

You suddenly notice all the shortcuts you took because now you're the one maintaining them. That's why rebuilding something isn't wasted effort. You're not just repeating yourself, you're comparing the way you used to think with the way you think now. sometimes the biggest sign you're improving isn't that your new project is more complicated.

It's that your old one makes you cringe a little.

"If someone looked at your calendar for the last three months, what career would they assume you're trying to build?" not your goals. mot your LinkedIn headline. Your actual calendar. Where your evenings go. What you read. ehat you practice. Who you talk to.

It made me realize careers are usually shaped by habits long before they're shaped by job titles. you don't accidentally become good at something. you quietly spend hundreds of hours around it. Maybe that's why career change feels so difficult. Sometimes the first thing that has to change isn't your resume.

It's how you're spending your ordinary Tuesdays.

"the easiest code to maintain is the code you never had to write."

At first I thought it was just another programming quote. but the more I thought about it, the more it explains why experienced developers seem so cautious about adding features. when you're learning, building more feels like progress. When you've maintained software for a while, you start realizing every new line of code is something you'll eventually have to debug, update, or explain to someone else.

That's probably why senior developers ask "Do we actually need this?" more often than "Can we build this?" writing code is fun. Maintaining unnecessary code usually isn't.

one thing that keeps standing out to me whenever I read career stories is how different everyone's path actually is.

someone graduates at 22 and gets their dream job.

someone else spends years figuring things out.

someone changes careers at 35.

someone gets laid off and ends up somewhere better.

but when we're living our own lives we tend to compare timelines instead of trajectories.

we see someone reaching a milestone before us and immediately feel behind.

The weird thing is that if you zoom out far enough, a lot of those differences stop mattering.

I've read stories from people who thought they ruined their careers because they picked the wrong major, accepted the wrong job, or spent years doing work they didn't enjoy. Then five or ten years later those same experiences ended up helping them in ways they couldn't have predicted.

I think that's why career planning can be so frustrating. We're trying to judge a story before we've read enough of it.

Maybe the better question isn't "am I behind?"

Maybe it's "am I moving in a direction that makes sense for me?"

something I've noticed from reading developer communities is that beginners often imagine there's a point where they'll finally know enough to start applying for jobs.

almost like there's some invisible finish line.

then you read posts from people with years of experience and they're still learning new things every week.

I came across a discussion recently where someone said they finally got hired and one of the biggest surprises was realizing that being job ready didn't mean knowing everything. It meant being able to figure things out without completely falling apart when you hit something unfamiliar.

That honestly makes more sense to me.

Most jobs aren't paying you because you already know every answer. They're paying you because they trust you can find answers, ask good questions, and keep making progress when things get messy.

I think that's why projects matter so much. Not because employers care about another todo app, but because projects force you into situations where nobody is telling you the next step.

Maybe "job ready" isn't a knowledge threshold.

Maybe it's the point where you become comfortable learning things you don't know yet.

I was reading about Stanford's Designing Your Life framework recently, and one idea stuck with me.

Instead of asking, "What's the right career for me?", ask, "what experiment can I run next?"

that small shift changes the way you think. You stop believing every decision has to be perfect. Instead, you start collecting information.

Maybe that's an internship. Maybe it's a certification. maybe it's talking to someone who's already doing the work you think you want. Even if you decide that path isn't for you, you've learned something valuable about yourself.

I think that's why so many people end up changing careers. it's not always because they made the wrong choice. Sometimes it's because they finally gathered enough real-world experience to make a better one.

The goal isn't to predict your entire career at 22.

It's to make the next decision that gives you the most useful information.

every week I see someone asking whether Claude Code is better than Cursor, or whether Windsurf is worth switching to.

After reading through Anthropic's documentation and some of the open-source projects around claude Code, I don't think the model is the interesting part anymore.

The interesting part is the workflow.

for example, Anthropic recently open-sourced Agent Skills, which isn't another coding assistant. it's a collection of engineering workflows that AI can follow while building software.

Instead of asking AI to "write a feature," the workflow encourages things like writing a specification first, breaking work into smaller tasks, reviewing code before shipping, and thinking about security and testing throughout the process.

that feels much closer to how experienced engineering teams already work.

It also made me realize that the biggest productivity gains probably won't come from whichever model scores highest on benchmarks next month.

They'll come from developers who build repeatable systems around whatever model they're using.

Models will change.

Good workflows will probably outlast them.

A lot of career advice starts with the wrong question. "what career should I pursue?" I think the better question is: how do I make good career decisions?"

most people are encouraged to choose a career based on salary, prestige, or what's popular at the time. That's why so many people end up changing careers a few years later.

Instead of chasing a specific job title, i'd focus on collecting evidence about myself.

Things like:

 * What kind of problems do I genuinely enjoy solving?

* Do I prefer working with people, data, ideas, or systems?

* Do I like structured work or figuring things out as I go?

* What type of work gives me energy instead of draining it?

 

You don't figure those things out by reading career lists. you figure them out by trying things.

Take internships. Volunteer. Build projects. Shadow professionals.

talk to people who are five or ten years ahead of you. every experience teaches you something about the kind of work you'll enjoy long-term. I also think we put way too much pressure on choosing the "perfect" career early in life.

 Very few people have everything figured out at 18. Most careers are built through a series of small decisions, not one perfect decision. the goal isn't to find the perfect career on your first try.

 The goal is to get better at making career decisions as you learn more about yourself.

One thing I've noticed is that people spend a lot of time comparing AI coding tools like Claude Code, Cursor, Windsurf, and Copilot.

i think that's focusing on the wrong problem.

the best developers aren't just using AI. They're building repeatable workflows around it.

I recently came across an open-source project called "Agent Skills". instead of being another AI coding tool, it's a collection of engineering workflows that guide AI through the entire software development lifecycle.

Things like:

* Writing a spec before coding.

* Breaking work into small tasks.

* Using test-driven development.

* Reviewing code before shipping.

* Security, performance, and documentation checklists.

What I found interesting is that it treats AI less like an autocomplete tool and more like a junior engineer that needs a structured process. whether you use Claude Code, Cursor, Gemini, or something else, I think this is the direction AI-assisted development is heading.

The advantage won't come from choosing the "best" model. It'll come from building better systems around whatever model you're using.

If you're experimenting with AI for development, i'd spend as much time improving your workflow as you do comparing models.

I've seen resumes that looked perfectly fine on paper but still struggled to get interviews. a lot of the time, it wasn't because the experience was weak. it was because the resume tried to be relevant for every job instead of this job.

recruiters aren't looking for the most impressive person. They're looking for the person who looks like the closest match. That means highlighting different projects, skills, or accomplishments depending on the role you're applying for.

A resume shouldn't answer, "what have I done?" It should answer, "Why am I a good fit for this position?"

every bootcamp promises the same thing: new skills, career support, and job-ready projects. The better question is what do their graduates actually look like six months later? a curriculum tells you what you'll study.

Graduate outcomes tell you whether that curriculum worked. Before enrolling, i'd spend more time looking for things like:

-What kinds of projects graduates are building.

-Whether alumni are getting interviews.

-If graduates are active in developer communities.

-How transparent the bootcamp is about employment outcomes.

Marketing tells you what a bootcamp wants to be known for. Graduates tell you what it actually produces.

sometimes i look back and realize i stressed way too much over things that barely mattered in the long run

bad interview, rejected application, awkward first week at a job, stuff like that

what's something you thought was a disaster at the time but turned out to be just a small bump?

before starting, i thought the hard part would be understanding concepts

turns out, for me at least, the harder part is being okay with not understanding things immediately and not feeling like i'm falling behind every other day

kind of curious if anyone else found the mental side harder than the technical side