How Do I Know if a Tech Career Is Right for Me?

The social media version of tech work: creative breakthroughs, espresso, minimalist desk setups, "building the future," and six-figure salaries. The reality is different.

A typical developer day: reading code someone else wrote (often confusing), debugging why something broke (often frustrating), sitting in meetings about requirements (often tedious), writing new features (satisfying when it works), deploying to production (nerve-wracking), and fixing bugs that appear at 4 PM on Friday (always).

The ratio is roughly: 20% creating new things, 40% fixing and maintaining existing things, 20% reading and understanding other people's code, 20% communication (meetings, messages, documentation). If the "creating new things" part is the only part that appeals to you, the daily reality will disappoint, because it is the smallest portion of the job.

For a detailed look at what developers actually do, see our article on what a software developer does all day.

• You enjoy figuring out how things work. When something breaks, is your first instinct to understand why rather than just get someone else to fix it? That curiosity is the core personality trait of successful developers.
• You can tolerate being stuck. Coding involves being stuck regularly. Not occasionally. Regularly. Multiple times per day. If you find being stuck infuriating in a way that makes you want to quit, coding will be miserable. If you find it frustrating but satisfying when you finally solve it, coding will suit you.
• You are comfortable with constant change. The tools, languages, and frameworks change every few years. You will never stop learning. If you enjoy learning new things, this is energising. If you prefer mastering one skill and doing it forever, this is exhausting.
• You like working independently for long stretches. Development is largely solitary focus work. You sit with a problem, think, type, test, debug. If you need constant social interaction to stay engaged, the daily reality of coding may not suit you.
• You are interested in building things people use. The ultimate reward in development is seeing people use something you built. If that idea motivates you, the frustration along the way is worth it.

• Your only motivation is money. Developer salaries are good. But the learning curve is steep enough that money alone will not carry you through the hard parts. People motivated purely by salary tend to quit around week 3-4 of learning, when it stops being easy and starts requiring real problem-solving. If you have no interest in what developers actually do, the pay will not compensate for the daily experience.
• You strongly prefer physical, social, or outdoor work. Development is screen-based, indoor, and largely individual. If sitting at a desk for 8 hours is genuinely unbearable for you (not just unfamiliar, but deeply unpleasant), a different career will make you happier regardless of the salary.
• You expect coding to feel creative most of the time. It is creative sometimes. It is tedious maintenance most of the time. If your expectation is that every day feels like an artistic breakthrough, the reality will disappoint.
• You need certainty and clear rules. Software development is full of ambiguity, trade-offs, and "it depends." If you thrive in environments with clear, unchanging rules and correct answers, the constant ambiguity of development will be stressful.

If these warning signs resonate, consider non-coding tech roles: product management, UX design, data analysis, tech sales, and QA are all well-paying tech careers that involve different daily realities.

No article, quiz, or personality assessment will tell you whether tech is right for you. Only one thing can: trying it.

Spend 2 weeks actually coding. Not watching videos about coding. Not reading articles about coding. Writing code, running it, breaking it, fixing it.

Options:

• Free: freeCodeCamp first certification (start right now at freecodecamp.org)
• Free, more realistic: The Odin Project Foundations (more challenging, more representative of real work)
• Paid, structured, Africa-focused: McTaba Tech Foundations (KES 2,999)

After 2 weeks, notice your honest reaction:

• "That was hard but I want to keep going." Tech is probably right for you. The difficulty does not go away, but the satisfaction of solving problems is enough to sustain you.
• "That was hard and I dreaded every session." Tech might not be right for you, or this specific format might not be right for you. Try a different approach (different language, different style) once more. If the dread persists, listen to it.
• "I didn't actually do the 2 weeks." That is also information. If you cannot sustain 2 weeks of curiosity-driven effort, a 6-12 month learning journey is unlikely to work without significant external structure (a cohort bootcamp at minimum).

The test costs KES 2,999 or nothing. It saves you months and potentially KES 100,000+ of commitment to something that is not right for you. Or it confirms that this is exactly what you should be doing. Either answer is valuable.