Quote:
Originally Posted by derada4
So tomorrow will be Day 3 of my new job (junior C#/.NET developer for those who don't know/remember).
The first day was mostly filling out paperwork, signing off on SOP's, getting a tour, setting up my computer, etc. The senior engineer who it seems like is the guy in charge of me spent pretty much the whole day with me, explaining lots of stuff.
Monday (Day 2) when I came in, I asked him what I should do and he said to just look through the codebase and continue with my C# studies (I am new to the language). So I did that all day and also attended their standard Monday morning developers meeting which was interesting.
Today when I got in I just went to my desk and continued familiarizing myself with the codebase and teaching myself C#. Also attended a meeting with the VP of Software Development with a few other guys who are < 3 months at the company (although they were all QA), which was just a general overview of the services we provide to our clients. At one point the senior engineer sent me an email that he put some DB backups on the server and that he would come over at some point to configure it all. Towards the end of the day I just took it upon myself to configure the MSSQL server on my computer and restore the DB's and whatnot.
Is this pretty standard for a new developer's first few days? It's definitely slightly boring and I feel it's quite inefficient for me to just aimlessly be browsing through the codebase as opposed to giving me some kind of task to do and me just learning/figuring it out as I go along (something I'm pretty good at).
Tomorrow morning should I approach him with this or just go to my desk again and keep doing the same thing?
This is different than my experience, though I will say it may be a good sign that you took some initiative for yourself.
My internship went like this: dive in and get this done. Week one was really about getting the look of the home pages laid out with .Net and making a few silly mistakes.
He then set up a db and create the admin area with a repeater then changed his mind and told me to implement list view. I asked him how I should connect to the database and he told me to google it, then perhaps as a test of my knowledge, told me to just concatenate the queries. Of course, I didn't do such a thing...
I think its pretty cool that they are laid back enough to let you examine stuff and take it slow. Trust me, you will get stuck at some point and you will need to have someone call you out for an amateur (a'la .Net world) mistake, and I would imagine they are just waiting until there is someone available for you when you get really stuck.
That was my experience, and I'm not sure if that is standard either. I was basically tossed into the deep end.