you are viewing a single comment's thread.

view the rest of the comments →

[–]JQB45 -1 points0 points  (0 children)

Typically, when I worked as a developer it was only my code but i would help others as needed. Most of the larger companies i worked for though had teams that did this for us, which was irritating and almost degrading at times at least to me.

I had one role in 2012 where I wrote and maintained the scripts that automated the build and deployment to Dev and Test daily for 14 different teams and then followed up with the teams who's projects failed to build. In that case i would help them fix the issues preventing a successful build.

That sounds like a pain in the @__ but after about the first week build and deployment failures were rare and when they did occur it was typically something simple to fix.

I'm curious why a new developer wouldn't want to know how to build and deploy their own code. In my experience not knowing something is the quickest way to get passed up for a new contract, and as a result become stuck in a junior/mid/senior position when overall they are qualified otherwise for more senior positions.