> For the complete documentation index, see [llms.txt](https://guide.ivanzakutnii.com/the-hard-way-to-swe-excellence/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.ivanzakutnii.com/the-hard-way-to-swe-excellence/basic-understanding/choosing-first-language-and-thinking-about-potential-career-path.md). # Choosing first language and thinking about potential career path Choosing your first programming language often becomes a serious obstacle for beginning developers, but this choice isn't as critical as it might seem at first glance. Most general-purpose programming languages give you ways to represent data, transform it, control evaluation, organize code, and handle failure. They express those ideas differently, but learning one model deeply makes the next language easier to understand. The main thing in programming is developing algorithmic thinking and problem-solving ability; the specific syntax of the language is secondary. Nevertheless, choosing the right first language can significantly ease your path into the profession, and here you should be guided by several key factors. First, consider your desired specialization and the quality of the learning path available to you: * For web development, JavaScript or TypeScript is the usual browser starting point; backend choices also include Python, JavaScript/TypeScript, PHP, Java, C#, and many others * For native mobile development, Kotlin is common on Android and Swift on Apple platforms; cross-platform frameworks have their own language choices * Python has a large ecosystem for data analysis and machine learning, where mathematics and SQL matter as much as syntax * C, C++, and Rust are relevant to systems and embedded work; C# and C++ are common in game development depending on the engine * Java and C# have mature ecosystems for backend and business applications If a good mentor or a coherent course teaches through a particular language, that learning environment can matter more than popularity rankings. Also consider the language's learning curve. Python offers quick feedback and a relatively small surface for basic programs. JavaScript is easy to run but comes with browser and package-ecosystem complexity. Statically typed languages such as Java, C#, Kotlin, or Rust expose more concepts early, but their tools can catch many mistakes for you. C++ exposes memory, compilation, and language complexity that can overwhelm a complete beginner without good guidance. That does not make it a bad first language; it makes the quality of the curriculum more important. Also consider the availability of learning resources: popular languages have extensive documentation, many online courses, active developer communities, and lots of learning materials. Read the curriculum, inspect a few exercises, and try one tiny program before choosing. Your first direction may not become your final career; the important thing is to make a reasonable choice and start learning. > Do not spend weeks optimizing this choice. Pick a defensible option, start learning, and revisit the decision when you have evidence that the language or course is blocking you. Right now, the most important thing is persistence in learning: you need to deeply study one programming language rather than superficially try several. When you master the fundamental concepts of programming in your first language, learning subsequent languages will become significantly easier, as you'll already understand the basic principles and can focus on syntax specifics and special features of the new language. Libraries, frameworks, and AI assistants can supply a great deal of syntax. They do not remove the need to understand the language's data model, runtime behaviour, error model, and tools well enough to inspect what those systems produce. Therefore, don't worry too much about choosing your first language - it's more important to start writing code, solve practical problems, and develop your algorithmic thinking. Over time, you'll likely master several programming languages, and each new language will expand your understanding of programming and add new tools to your professional arsenal :) *** ## What area of IT interests you? As I mentioned earlier, realizing the answer to this question might make it easier for you to choose your first programming language. Let's briefly look at the main professional paths, what corresponding specialists do, and why you need to know about this at all. ## Main Programming Areas ### Web Development The most common entry point into programming. Involves building websites and web applications. **What you'll work with:** * Frontend: Making interfaces work well in browsers and browser-based clients (HTML, CSS, JavaScript/TypeScript) * Backend: Implementing application behaviour, APIs, data access, and integrations on servers **Good for you if:** * You like seeing immediate visual results * You enjoy building things people interact with * You like a short visual feedback loop * You are comfortable with a fast-moving ecosystem ### Backend/Server Development Building the "engine" that powers applications. **What you'll work with:** * Databases * APIs * Business logic * Server systems **Good for you if:** * You enjoy solving complex problems * You like working with data and systems * You prefer working on behaviour and data over visual presentation * You're interested in system architecture ### Mobile Development Building apps for phones and tablets. **What you'll work with:** * Android (Java/Kotlin) * iOS (Swift) * Cross-platform tools (React Native, Flutter) **Good for you if:** * You want to build apps people use daily * You're interested in mobile user experience * You don't mind learning platform-specific rules ### Game Development *A note of caution: game development combines programming with engine constraints, performance, tooling, and often mathematics or physics.* **Reality check:** * Roles vary widely between engine, gameplay, tools, graphics, networking, and technical art * Working conditions and compensation depend heavily on the studio and region, so investigate the actual market you may enter * Some roles require strong mathematics, physics, or low-level performance skills * A playable result can require substantial non-programming work Only choose this path if you're truly passionate about games and understand the challenges. ### Data Science Working with data analysis and machine learning. **Important to know:** * Requires statistics and enough mathematics to reason about the models you use * Includes data collection, cleaning, validation, analysis, and communication, not only model training * Python, SQL, and notebooks are common tools; other languages and platforms appear by domain Choose this if you love mathematics and data analysis. ### Systems and Infrastructure Building the layers that applications run on: operating systems, networks, cloud platforms, developer tooling, reliability, and observability. **Good for you if:** * You are curious about what happens below an application framework * You like debugging interactions between several systems * You care about performance, reliability, deployment, and operational feedback * You are willing to learn both code and the environments in which it runs AI-assisted development cuts across every area above. Treat AI as a tool inside a specialization, not as a replacement for learning the domain that gives its output meaning. ## Key Takeaways for Beginners 1. Choose a path with a short feedback loop, solid learning material, and people who can review your work 2. Consider what you enjoy and what work is available to you; salary alone is a poor learning compass 3. Be ready to learn continuously in any path 4. Do not feel locked in; many developers change paths during their careers Remember: Your first choice isn't permanent. Many developers start in one area and move to others as they gain experience.