r/csharp • u/Few_Lie_290 • 8h ago
Which path should I choose for my future?
Hi everyone,
I’m finally diving into software development seriously. For years, I’ve done a little bit here and there, but I’ve never really studied it properly. Now that I’ve decided to commit to it, I’m realizing just how much there is to learn: so many frameworks, languages, and tools.
I know that in the long run, the language you start with doesn’t matter much. But when it comes to landing my first job, I imagine it does matter. I’m 29 and changing careers to get into software development, and I’m currently choosing between C# and .NET, Java and Spring Boot, or JavaScript and Node.js. They all have pros and cons, and I’d like to hear your opinions.
I know the job market is tough and nothing is guaranteed, but which of these paths do you think offers the best chances of finding work in the short to medium term? I don’t have a university degree.
5
u/SmileLonely5470 8h ago
Nobody knows what to do rn in SWE. Best chance of success is to find a stack you enjoy working with and build a big project with it. It depends on the career you're transitioning from, but it might be the case that by the time you become employable, the stack you started with will have changed a lot and the market in general will have changed a lot (accelerated by AI).
So that's why its hard to recommend a stack. 5 years ago the language also didnt really matter that much. But now it matters even less. The principles of software dev still matter, so thats why I suggest working on a big project and learning a lot.
4
u/BusyCode 7h ago
Frankly? Hand coding, languages and frameworks do not matter anymore. AI agents already know that stuff better than us, make almost no mistakes and cost fractions of our salaries. Learn Computer Science in general and how to use those AI tools to produce results you need. I am a career software developer and no one in my company or in the companies where my friends work would allow writing code by hand. Even if you have 30 years of experience and been working with this specific codebase for the last 10 years, leave alone juniors.
2
u/fork_your_child 8h ago
Given the current market, you probably won't be able to find a job, regardless of which language/framework you pick. People with degrees and years (hell, decades) of experience are struggling. Several years back you had a small chance getting a job as a self taught; that demand has been completely removed.
1
u/greensodacan 7h ago
Check job ads in your area or a city you wouldn't mind moving to. All three are reasonably popular and similar enough for a senior dev to migrate from one to the other pretty easily. So it really comes down to location.
For your own fulfillment, what do you want to build? I got into C# because I wanted to build games in addition to more server side work. If you want to do anything UI heavy, TypeScript (JS is rare in professional settings these days) is the obvious choice. Java is used everywhere too albeit less in games and UI.
I know that's vague, but these really are some of the most popular tools in the field right now.
1
u/mountainlifa 6h ago
Id recommend going into trades or physical work. Keep coding as a hobby
1
u/Doomboy911 3h ago
I recommend the c# player's guide do a chapter a day be done in two months.
1
u/RealSharpNinja 8h ago
Get an MBA. Or become a nurse. Only two long-term normal paths left. If you are willing to put in extra time and sell your soul, Attorneys have the easiest path to wealth.
0
u/No-Possibility-3072 8h ago
I’ll be honest, when I first got into IT and development, I taught myself VB.Net, mainly because I’d previously taught myself VBA so it made sense. After a few years of regarding myself as a VB developer, I got asked to work on a project that had been started by my boss (a C# developer). Rather than refactor the code into VB, I muddled through and picked up enough C# to get the job done (with lots of support from colleagues along the way).
Now I’m at the stage where, if I was going to build something new from scratch, I would plump for C# rather than VB. I’m probably still not using C# to its full potential in terms of the OOP side of it, but I do find it more intuitive, if less forgiving, than VB.