What Sun Tzu gets right about starting a tech career

The Art of War is a strange place to look for career advice, but one piece of it turns out to translate almost directly into how someone should approach a first move into tech: know yourself, and know the terrain you're entering. Most of what goes wrong early in an IT career comes from skipping one half of that pairing, usually the self-knowledge half, and jumping straight to whatever skill happens to be trending.

Know yourself before you chase the landscape

The first move isn't picking a specialization off a list of in-demand roles. It's getting honest about what actually holds your interest: front-end development, cybersecurity, data science, or something else entirely. That self-assessment can be structured rather than guessed at, plenty of platforms offer free skill assessments that gauge aptitude for different languages or specializations, and researching actual job roles, their responsibilities, required skills, and realistic career progression, turns a vague interest into an actual direction.

Only once that's reasonably clear does it make sense to study the terrain itself: following industry publications, attending meetups, and connecting with working professionals to understand where the field is actually moving. Emerging areas like artificial intelligence, cloud computing, and blockchain are worth tracking specifically, along with which languages, frameworks, and tools are genuinely in demand rather than just discussed. Doing the self-assessment first is what keeps landscape research from turning into chasing whatever's loudest at the moment.

Once you know the direction, maneuver toward it deliberately

Understanding yourself and the field is only the setup. The actual progress comes from what Sun Tzu would call maneuvering for advantage: upskilling with intent and building something that proves it.

That starts with choosing a single learning path based on the direction from the first step, rather than spreading effort across everything at once, and using structured resources, online platforms, bootcamps, even degree programs, to build real depth in it. None of that substitutes for consistent practice, though: regular coding challenges, personal projects, and contributions to open-source work are what actually convert study time into demonstrable skill.

The other half of maneuvering is visibility. A professional website or portfolio that actually shows finished projects and real accomplishments does more for a career than a resume alone. Contributing to open-source projects on GitHub does double duty here, it proves you can solve real problems and puts you in contact with experienced developers who might otherwise never see your work. And building a genuine professional network, at events, in forums, through direct connections, compounds all of it: opportunities in tech rarely arrive purely through job postings.

The two moves work together, not in sequence

Self-knowledge without landscape awareness produces someone chasing an interest with no market for it. Landscape awareness without self-knowledge produces someone credentialed in something they don't actually want to be doing five years from now. The two Sun Tzu principles that map onto an early tech career, know yourself and know the terrain, only work as a career strategy when they're applied together, continuously, not as a one-time exercise before your first job search. That combination, more than any specific language or certification, is what actually determines whether the next few years of a tech career go somewhere deliberate or somewhere accidental.