I work with a group of friends who take on freelance projects, mostly involving web and mobile development. They have several years of experience with different technologies, while I only started web development this year and currently learn under their guidance. Our usual stack is React, TypeScript, and Next.js, but we want to accept a wider range of projects, which could require Symfony, Flutter, C#, or other tools. My personal interest is much more focused on open-source C and C++ work, which I have been learning since I first started programming about two and a half years ago. How do developers handle switching between unfamiliar technologies, especially when the work is not aligned with their main interests? I find the learning phase particularly difficult and sometimes lose motivation. Is there a good way to adjust mentally and stay productive while building skills in several different areas?
3 Answers
That situation is extremely common. Many developers have a favorite language or ecosystem they enjoy personally, but their job or freelance work may involve writing TypeScript, Java, C#, or something else. It helps to treat each new technology as a tool to understand rather than as a replacement for your preferred language. You can keep C and C++ as your long-term passion while learning other stacks because they are useful for specific projects and clients.
Different technologies exist because they solve different problems. A web application with a rich browser interface will naturally involve JavaScript-based tools, while a mobile project or a backend service may call for an entirely different stack. You do not need to love every language you use. Learn enough to contribute effectively, stay open-minded, and reserve some personal time for the C and C++ projects that keep you interested. Having both practical work and a personal area of enthusiasm can make the variety easier to manage.
If you work as part of a team, learning the tools the team uses is part of being a developer. Projects often involve maintaining older code or adopting a framework that is outside your comfort zone, and the shared language and toolset make collaboration easier. Try not to judge yourself during the early, awkward stage. Focus on understanding the fundamentals, follow the team's conventions, and let familiarity build through real tasks. The initial effort usually pays off later.
I appreciate that perspective. I suppose becoming comfortable with unfamiliar technology is simply part of the career.
That makes sense. I mostly struggle with getting into the right mindset when I am still a beginner in the new language, since the lack of familiarity makes the work feel less enjoyable.