Re:Ask HN: How do you define a junior developer?
by pigpigs on Friday September 23, 2016 @02:50AM
(#12562793)
I agree with you. My observation is that most graduates out of college are able to formulate strategies to high level problems, rapidly create working solutions and generally be productive.
What sets us apart from the senior developers as pointed out by the CTO of my company seems to be experience in writing good, scalable code. More often than not this means adhering to best practices, linting and testing extensively and many other things that in general come with experience.
Re:Ask HN: How do you define a junior developer?
by seangrogg on Thursday September 22, 2016 @01:37PM
(#12558580)
The previous post made it pretty clear that there are no timelines attached to their perception of developers - a person that brings business value to your company without supervision should not be a junior developer, regardless of whether they have decades of industry experience or are fresh out of college.
This is what people here like to believe. But I don't think it is really true. A kid straight out of college can generate immediate business value if he/she can set up an online shopping cart in Php to give a business an online presence. I am pretty sure that the same kid can code up any business requirement of most of the local organisations that does not need to scale much or work with great reliability.
Also, it is not true that a junior dev requires supervision. Anyone with sufficient motivation and an internet connection can figure stuff out by themselves. I mean, they can get things done, even if in a fantastically stupid fashion.