Learning their stack is good advice. You'll impress folks if you can hit the ground running. Another area that I'd recommend is start to learn the business domain. If your company builds accounting software - start to learn some basic accounting principles. If your company builds healthcare insurance software, start to learn about the relationships between healthcare providers, insurance providers, health plans, etc.…
Ask HN: How can I prepare for my new job as a software developer?
11–20 of 45 posts
Re: Ask HN: How can I prepare for my new job as a software developer?
#12You will also want to be familiar with some tools to debug code for their stack. They'll likely give you some bugs to track down to start off with. Definitely install and play with whatever database they are using.
Re: Ask HN: How can I prepare for my new job as a software developer?
#13It would've been useful if you'd at least posted the language. My recommendation is this: be pragmatic. I've been asked plenty of times to forgo software development principles to get a product out the door ("hardcode this", "copy/paste that"). I never copy/paste, but I have hardcoded things to get a product shipped on time. You may have a better idea of how to do a lot of things, but only bring it up when you unders…
Re: Ask HN: How can I prepare for my new job as a software developer?
#14Re: Ask HN: How can I prepare for my new job as a software developer?
#15Learn the stack they use, play with it, make sure you understand it. Also, find out what version control system they use and get comfortable using it - source control's vital stuff when working in a team and something that you may well have not really used so far in CS.
Re: Ask HN: How can I prepare for my new job as a software developer?
#16Learning their stack is good advice. You'll impress folks if you can hit the ground running. Another area that I'd recommend is start to learn the business domain. If your company builds accounting software - start to learn some basic accounting principles. If your company builds healthcare insurance software, start to learn about the relationships between healthcare providers, insurance providers, health plans, etc.…
Unfortunately, much of this can even be business specific. It would be helpful to find out if they have any of this documented. It probably isn't documented within the software team, but, it most likely is for other business units!
Re: Ask HN: How can I prepare for my new job as a software developer?
#17Don't be the guy that spends two weeks on a problem that could've been solved in 15 minutes by asking someone for help.
Re: Ask HN: How can I prepare for my new job as a software developer?
#18Re: Ask HN: How can I prepare for my new job as a software developer?
#19If you already got hired, I would just relax. Get some exercise, find a couple good books [1] you can read later when you want to take your mind off work. Then, when you start work, pour over the source code. Understand it. Ask or research anything you don't understand. Make a list of things that suck about it -- there likely will be a lot of technical debt, but who knows... If you want to get ahead, combine working…
The company pays you to learn their stuff.
Re: Ask HN: How can I prepare for my new job as a software developer?
#20Make sure you keep your ears open for advice from more senior folks in the company, and ask questions when you don't understand something or get stuck. You'll be fine. Don't be the guy that spends two weeks on a problem that could've been solved in 15 minutes by asking someone for help.
This! I am eternally repeating this to our first line support people where we need to resolve things with 8-16 working hours. If they're still scratching heads after 4-5 hours then they should be hitting up the back room team for advice and guidance.
In addition, we then make sure that the "how the issue was resolved" is written up so, stuck into our internal KB wiki for future reference.
But yes, bottom line don't be afraid to ask, and don't be afraid to ask more if you still don't quite understand the solution/reasoning. I'd rather you kept asking until you "totally get it" rather than you wandering off with a vague understanding and breaking a production environment.