Skip to the content
Software Made Clear
Search the whole site About

TOPIC 38 ARTICLES

Career & Craft

Practical decisions for a developer's career: choosing work, learning useful skills, earning trust, searching for a role, and growing without making work your whole life. Concrete examples, honest boundaries, and named sources.

Help me choose a first step
LATEST IN CAREER & CRAFT Does AI Actually Slow Down Junior Developer Learning?

EXPLORE THE TOPIC

Browse the articles

Pick a question that interests you, or narrow the list above.

DEEP DIVE Does AI Actually Slow Down Junior Developer Learning? One study found a 4.15-point quiz gap after AI-assisted coding. See what it measured, what it did not, and how to use AI without delegating the learning. Read it →
DEEP DIVE What actually changes between mid and senior See what a step up in seniority really asks for, why it is not more code, and how to tell whether you are already doing it in your current job. Read it →
DEEP DIVE A good developer career does not need to take over your life Define enough in terms of work, income, learning, and life outside the job. Choose ambition deliberately instead of treating every spare hour as career debt. Read it →
DEEP DIVE Ask for help without handing over the whole problem Explain what you are trying to do, what you observed, and where your reasoning stops. Make it easy for a colleague to help without hiding uncertainty. Read it →
DEEP DIVE Build a developer portfolio that shows judgement Use a small project to show decisions, tests, and honest limitations. Help a reviewer understand your contribution without a large unpaid side project. Read it →
DEEP DIVE Build a skill practice loop, not a course collection Choose a developer skill you can demonstrate, practise it on a bounded task, and use specific feedback to decide what to change on the next attempt. Read it →
DEEP DIVE Build career confidence from specific evidence Separate how confident you feel from what you can demonstrate. Use bounded practice, honest feedback, and clear limits instead of trying to sound certain. Read it →
DEEP DIVE Choose a stretch assignment with support, not just more risk Check the scope, authority, time, and review behind a development opportunity. Distinguish a useful stretch from unsupported responsibility. Read it →
DEEP DIVE Developer career advice: start with the decision in front of you A practical reading guide to 24 developer career questions: direction, workplace conversations, learning, job searches, and sustainable growth. Read it →
DEEP DIVE Evaluate a developer job by the working week Use concrete interview questions to investigate a developer role's actual work, support, and constraints before comparing offers or accepting a title. Read it →
DEEP DIVE Learn from a job rejection without inventing the reason Separate confirmed feedback from guesses, review your interview against observable criteria, and choose one improvement without rewriting your whole identity. Read it →
DEEP DIVE Make a lateral career move without starting from zero Translate existing experience into a new developer role, identify the gaps honestly, and agree on a transition that gives you a fair chance to learn. Read it →
DEEP DIVE Mentor a developer without taking over the work Give enough explanation and support for a learner to act, then check their understanding on another task. Distinguish teaching from urgent delivery. Read it →
COMPARISON Mentor or sponsor: ask for the help you actually need Distinguish advice from advocacy, make a specific request, and build useful career support without expecting one influential person to solve everything. Read it →
DEEP DIVE Negotiate a developer offer without bluffing Prepare an honest offer negotiation around the work, your priorities, and real alternatives. Make a specific request without inventing competing offers. Read it →
DEEP DIVE Network through useful relationships, not constant self-promotion Reconnect with colleagues and meet people through shared work. Ask clear, respectful questions without treating every contact as a potential transaction. Read it →
DEEP DIVE Onboard by mapping the work, not memorising the organisation Build a practical onboarding map of users, decisions, delivery steps, and people. Use a safe first change to discover what the documentation leaves out. Read it →
DEEP DIVE Use one-to-ones to make career decisions Bring a concrete development question to your manager, leave with a decision and owner, and keep routine project updates from consuming the whole meeting. Read it →
DEEP DIVE Say no by making the trade-off visible Respond to extra work with a clear account of capacity, alternatives, and decision ownership instead of a hidden promise to work longer. Read it →
COMPARISON Specialist or generalist: choose the problem before the label Decide where to deepen your skills and where breadth helps. Compare specialist and generalist work against an actual team problem, not a career stereotype. Read it →
DEEP DIVE Tell engineering interview stories without inflating your role Explain a real engineering contribution with enough context, decisions, and results to be useful, while preserving shared credit and uncertainty. Read it →
DEEP DIVE Test a career direction before you commit Try the work behind a job title before changing careers. Build a small experiment that tests one important assumption without betting your livelihood. Read it →
DEEP DIVE Turn vague feedback into a practice plan Translate feedback such as 'be more strategic' into a specific situation, expected behaviour, and a fair way to check whether your next attempt improves. Read it →
DEEP DIVE Unlearn a habit that no longer fits your role Keep the experience that still helps while changing a habit whose assumptions no longer fit. Test a replacement behaviour on a bounded piece of work. Read it →
DEEP DIVE When to stop pursuing a career plan Decide whether to continue, change, or stop a career plan by checking its assumptions and future costs, rather than defending the effort already spent. Read it →
DEEP DIVE Why software development involves so much arguing Software disputes often come from hidden technical work, split authority, and different incentives. Learn how to turn recurring arguments into decisions. Read it →
DEEP DIVE Write a developer CV with evidence, not a tool inventory Show what you did, why it mattered, and which skills the work demonstrates. Keep technology names useful and avoid invented metrics or keyword stuffing. Read it →
DEEP DIVE Write status updates that help someone decide Turn a list of engineering activity into a short update that explains what changed, what remains uncertain, and what decision or action is needed. Read it →
DEEP DIVE Reviewing without starting a fight Write code review feedback that names a problem, explains its consequence and distinguishes required fixes from suggestions, with a worked example. Read it →
DEEP DIVE Writing it down before you build it See why most design docs go unread, and how to write one that gets real comments before the build starts, instead of complaints after it ships. Read it →
DEEP DIVE When are you no longer a junior developer? No fixed year ends a junior role. Compare your team's level criteria with a worked example of taking a small feature from unclear request to checked result. Read it →
DEEP DIVE Why good developers become bad managers See why software companies promote people into roles they are not good at, how the Peter Principle shows up in engineering, and what actually fixes it. Read it →
DEEP DIVE Influencing a design you do not own See how to push back on a design you do not own without losing the argument or the relationship, by writing your case down first, in detail. Read it →
COMPARISON Senior, staff, and the ladder above See what actually separates a senior engineer from a staff one, and whether that title is worth chasing before your day-to-day scope changes. Read it →
DEEP DIVE Shipping without supervision See what actually earns you the right to ship without someone checking first, and how to keep that trust once nobody is looking over your shoulder. Read it →
DEEP DIVE Making the case to the people who fund it See how to make technical debt make sense to the people who fund the work, by trading it for scope instead of arguing over code quality itself. Read it →
DEEP DIVE Getting the title to match the work See what actually belongs in a promotion packet, and how to gather the evidence for it before the case has to be built entirely from memory. Read it →
DEEP DIVE Estimates you can defend See where estimates actually go wrong and why the error compounds across tasks, so you can give a number you are able to stand behind later. Read it →