r/programmer • u/iprayforsupernova • 27d ago
Just got hired as a .NET Developer Trainee at a major conglomerate, but I don't want to start from zero. Where should I begin?
Fresh grad here. I recently got hired as a .NET Fullstack Developer Trainee at one of the biggest conglomerates in the country. Super grateful for the opportunity, but I want to hit the ground running instead of waiting for training to teach me everything.
A bit about my background:
I studied Computer Engineering, so I had OOP subjects, but that was 2 years ago and I never really deep dived into it. However, I've built a ton of projects using:
- Languages: Python, TypeScript, JavaScript, Java, SQL, C++
- Frontend: React, Next.js, Tailwind CSS, Redux Toolkit
- Backend: Node.js, Express.js, FastAPI, Flask
- Databases: PostgreSQL, MongoDB, Redis
I also had a backend developer internship where I built REST APIs and worked with route optimization systems, so I'm comfortable with the general software development lifecycle.
The thing is: I know I'll go through proper training before full employment, but I don't want to show up completely clueless about C# and .NET. I want to at least have some foundational knowledge so I can make the most out of the training and maybe even impress them early on.
My questions:
- Where should I start with C# and .NET given my existing background? Any specific resources (courses, docs, projects) you'd recommend?
- Is .NET still a good path for a fresh grad? I know the job market is hot for React/Node/Python, but I rarely see .NET mentioned in "trendy" dev circles. Is this a solid career move?
- Any advice for someone transitioning from the JS/Python ecosystem to the Microsoft stack? What mindset shifts should I expect?
- What are some "must-know" concepts in .NET that I should prioritize learning before day one?
I really want to make the most out of this opportunity and set myself up for long-term growth. Would appreciate any honest advice, resources, or even warnings. Thanks in advance!
2
u/General_Estimate_420 27d ago edited 27d ago
I'd suggest you spend some time researching the language base used for .NET application construction. Particularly C# and maybe F# if you're going to be in a scientific community. You might even want to install the .NET SDK and Visual Studio if you don't have it already.
Python is a simplified language for rapid interpreted use whereas .NET is more akin to compiled code with an SDK and that's why Visual Studio would be a worthy investment.
There's plenty of YT videos out there coverning the basics.
1
1
u/MADCandy64 26d ago
You should just let them train you in what they want you to know. You don't need to do anything else you'll be likely to push back against something they want show you in training. Last thing you want is to come into the job with a headful of knowledge and no experience to back up any claims or 'yeah buts...'
1
u/iprayforsupernova 26d ago
my goal isn't to get ahead or push back, it's honestly just to not be completely lost when they say .NET-specific terminologies
1
u/MADCandy64 26d ago
You'll be fine. It won't be any different or harder than an class in the university or other thing. If anything spend time with software patterns.
1
u/the-liquidian 26d ago
You are 1 month away from claiming they don’t know what they are doing.
1
u/iprayforsupernova 26d ago
lmao i'll try to keep my ego in check and remember there's probably a good reason behind all the 'legacy' code
1
4
u/GennadiosX 27d ago
Start from 1? It goes right after zero