My list of things that I wish I knew before my first day as a Software Engineer.
I've been an Associate Software Engineer for a little o...
For further actions, you may consider blocking this person and/or reporting abuse
I hope that git will be the norm for Computer Science degree. My country does not require git in schools. They simply throw a boilerplate code and never bothered to use FOSS. They simply put "Paid IDEs" in their machine and make use of it.
Project Management, Methodology, Design System, Proper Documentation, and productivity.
I think that is the direction it's heading. While applying for positions here almost all of them wanted experience with Git in some form.
I can't blame the school for not providing proper real world team collaboration. It's just that, technology moves so fast and the professors don't let students collaborate with each other. We(me and my friend) held a small session teaching git for the students. They got bored because it was too complicated to use. We tried several methods but in the end, some were not interested and never bothered to learn anymore(we didn't force them to come btw).
My mistake for having a session is that
final_1,final_finallyproject.Hi Dennis, It's just not right that Git isn't taught in your school when company's are now requiring Git as a job pre-requisite. If I may suggest, there are a lot of free books on Git on Kindle that you may want to checkout. This is what I personally read when I get lost using Git
I hope this helps!
As a Senior dev, I feel the need to point out that only your last point actually matters for juniors.
If you took less than a working week to setup your new machine, awesome, you've beaten EVERY single junior I've ever worked with. Hell, I'm still changing things up on my office laptop!
Git/SCM... don't beat yourself up. I know Seniors that don't understand how a "pull --rebase" works. Find someone on your team that's comfy with the SCM, and pick their brains whenever you're stuck. Also, there's no shame in Googling.
Re the IDE, some firms mandate it, some don't. Generally the better employers realise that all that matters, is that the code is readable. If your IDE & plugins is mandated, as a junior, unfortunately you have to just suck up the learning curve. But communicate with the team as you go. If a junior came to me with a "how do I do X?" - I'd not only help them, but I'd also feed back to management that you're putting your best foot forwards, and I'd help you keep the project management team off your back.
Back to your last point: chill. You're new, you're a junior. Deep breaths, and use the Seniors & Leads - they get paid to help you out.
Hey Dave!
I really appreciate the feedback and I hope that some of the people this article was written for find it! You're right, the only point that really matters is the last point, technically everything else rolls into that point.
Cheers!
I do share your point of view. Mostly point 2,3,5. The IDE is somehow subjective but the rest just stands as-is.
Have fun being a junior developer. Once you go senior, you never go back :)
Ha, thanks! The IDE portion is definitely subjective. I agree!
Thanks for sharing this!
As someone who's starting a software engineering internship in a month, this was really helpful and made me reconsider how well I really know Git and my IDEs/tools.
Absolutely! I was pretty nervous starting at my job, but so far so good! Best of luck to you at your internship!
Definitely... I know that we're seen as "anti-social" but forcing us into at least one team project would be such a good experience as students.
I agree 2~4
Thanks for providing such type of useful and motivational information.
You're very welcome! I really appreciate your comment.
All of this is very basic. I would say obvious for passioned people but not obvious to the majority of average students as universities do not necessarily focus on this. Still good to mention it.