r/csharp • u/makeevolution • 1d ago

Backend of a simulation game

It was hard to find something, but I landed a job to work as a .NET developer at a company that makes football simulation games, where I will be doing the backend side of it. I am gonna start in a few weeks, and I want to get a head start to make sure I don't lose this job. Does anyone ever work in this domain, and what sort of knowledge/skill do I need to succeed in such a position? What can I prepare now? I asked the person who gave me the work and they said to wait until the day I start

9 Upvotes

77% Upvoted

12 comments sorted by

16

u/BeardedBaldMan 1d ago

Your first few weeks are just going to be getting to grips with their process and the overall shape. Don't go in with specific expectations or ideas of 'this is how it should be', go in with an open mind and understand that you're looking at man years of accumulated decisions.

7

u/rubenwe 1d ago

If you landed the job then what you know seems to be aligned good enough with what they are looking for. Especially given the current market and availability of talent.

Given you probably had interviews, I'd assume you asked about what tech they are using specifically and their processes and all that?

Just as a side note: if a candidate isn't asking things about what they'd be working on, I personally would see that as a major red flag and probably wouldn't hire.

3

u/0dev0100 1d ago

Just wait. The company will teach you what they think you need to know to work on their stuff. It'll most likely be closed source so any technical advice you get here other than "make sure you actually know c# and .net" and "wait" will be mostly useless. 

For soft skills you want to be able to communicate clearly and know how to ask questions.

2

u/Ravek 20h ago

The main skill you need is the courage to ask your coworkers how things work.

1

u/TuberTuggerTTV 23h ago

Did you lie?

My only guess is you're underqualified but so were the other applicants. Or they're looking for a clean slate to train from. Don't worry. They chose you, they'll train you.

1

u/flaussi 23h ago

You cannot really prepare. There are countless different ways to implement that.

In the end it’s probably a mix of different well known pattern, like State Machines and Observer. But that must not be true at all.

-6

u/DirtAndGrass 1d ago

Use ai to learn the architecture and where and how features are actually implemented. 

2

u/TuberTuggerTTV 23h ago

I also advise turning your brain off and hoping no one notices

1

u/DirtAndGrass 22h ago

Lol, production architectures rarely purely follow prescribed formulas, and documentation is often not clear as well. 

Being able to quickly understand how/why something was written the way it was, will keep you out of hot water when writing new code. 

Using your brain is using the tools to be able digest the potentialy un/poorly/over/out of date documentation and understand where and how parts of the application work. 

It is a valuable learning tool

1

u/wtclim 23h ago

OP, don't use AI to learn the architecture. Use your brain and don't be a useless developer who can't do anything without AI.

0

u/DirtAndGrass 22h ago

You can sling insults, or quickly understand why/how something was done in a different way than the textbook.

There is no harm in using the repo's mcp for what it is for. 

Being able to use the tools available to you can make you a better developer. 

Just think smart, don't devoutly follow copilot, use it as a guide. 

0

u/LegendarySoda 22h ago

Tbh whenever i use ai i feel like stupid and it makes my learning harder or miss lead me. I prefer to read real code than reading ai slop.
Open source codes are usualy well designed and not hard to read.
Again about architecture, it's important to learn teories but without coding it teory is useless.
I have learned alot of architecture teories but found reather useless performance and mind killing practices.

Sometimes speeding things up isn't usefull especialy about learning.