A Senior Developer working mostly with PHP and JavaScript, with a bit of Python thrown in for good measure, all on Linux. My tooling is simple, it's GitLab and JetBrains where possible.
That's a lot to ask of a junior developer without giving more specific guidance. If expect that level of thought off the vague spec to be at a mid or senior level, where they have run into the issues before.
I wouldn't expect my junior developers to know about the devops process in the first couple of years. They should be learning about the application, tech stack, and how to think about the implications of their changes, and how to question a spec.
Not everyone has worked somewhere with devops in place. To say that someone who doesn't know it isn't a good developer is narrow minded and is a fallacy. I didn't cover any proper level of devops until about 8 years into my career. It simply wasn't done where I worked (and wasn't common parlance back then).
I've been in the development game a good amount of time. Outside og Gnome, KDE, Unity, and Cinnamon I don't know other Linux desktops. Xfce might be one but I never remember the right letters. I spend my day in a Ubuntu VM. Not knowing different ones doesn't make me a bad developer.
You don't specify a time limit on them producing the form. Do you expect all this to be done in an hour? A day? A week? Different time limits will change what should be provided, or at least researched and added to a road map document as part of the submission.
Finally, if you are expecting a junior to know all this, are you paying for them to learn it on the job? Or do you expect them to spend all their free time researching and learning? When I was a junior I had other hobbies outside work. Now I'm older I have a family. I can't spend most of my time outside of work learning new technology or trying to refine infrastructure setup. I need down time.
Hey Gary thanks for commenting. Agreed with you if you ask everything to a jr dev from list. Actually, article has three sections and intent to examine jr dev role : back-end , front end or Devops . Naturally, a jr dev will be assuming one of the role.
Not everyone has worked somewhere with devops in place. To say that someone who doesn't know it isn't a good developer is narrow minded and is a fallacy
+1 to your thought and I agree with you. But these questions only check the basic normals now. For example, a crud program without validation or secure is no use at commercial level. If Devops is not a role ... Why to put question?
You don't specify a time limit on them producing the form. Do you expect all this to be done in an hour? A day? A week?
All questions are for interviews (1-2 hrs).
I've been in the development game a good amount of time. Outside og Gnome, KDE, Unity, and Cinnamon I don't know other Linux desktops. Xfce might be one but I never remember the right letters. I spend my day in a Ubuntu VM. Not knowing different ones doesn't make me a bad developer.
Instead of asking about server types, we are asking about desktop environments. This is just to understand how he /she knows about linux world.
*
I think your expectations are unrealistic.*
Agreed, if you start asking Devops questions to frontend guy.
That's a lot to ask of a junior developer without giving more specific guidance. If expect that level of thought off the vague spec to be at a mid or senior level, where they have run into the issues before.
I wouldn't expect my junior developers to know about the devops process in the first couple of years. They should be learning about the application, tech stack, and how to think about the implications of their changes, and how to question a spec.
Not everyone has worked somewhere with devops in place. To say that someone who doesn't know it isn't a good developer is narrow minded and is a fallacy. I didn't cover any proper level of devops until about 8 years into my career. It simply wasn't done where I worked (and wasn't common parlance back then).
I've been in the development game a good amount of time. Outside og Gnome, KDE, Unity, and Cinnamon I don't know other Linux desktops. Xfce might be one but I never remember the right letters. I spend my day in a Ubuntu VM. Not knowing different ones doesn't make me a bad developer.
You don't specify a time limit on them producing the form. Do you expect all this to be done in an hour? A day? A week? Different time limits will change what should be provided, or at least researched and added to a road map document as part of the submission.
Finally, if you are expecting a junior to know all this, are you paying for them to learn it on the job? Or do you expect them to spend all their free time researching and learning? When I was a junior I had other hobbies outside work. Now I'm older I have a family. I can't spend most of my time outside of work learning new technology or trying to refine infrastructure setup. I need down time.
I think your expectations are unrealistic.
Hey Gary thanks for commenting. Agreed with you if you ask everything to a jr dev from list. Actually, article has three sections and intent to examine jr dev role : back-end , front end or Devops . Naturally, a jr dev will be assuming one of the role.
Not everyone has worked somewhere with devops in place. To say that someone who doesn't know it isn't a good developer is narrow minded and is a fallacy
+1 to your thought and I agree with you. But these questions only check the basic normals now. For example, a crud program without validation or secure is no use at commercial level. If Devops is not a role ... Why to put question?
You don't specify a time limit on them producing the form. Do you expect all this to be done in an hour? A day? A week?
All questions are for interviews (1-2 hrs).
I've been in the development game a good amount of time. Outside og Gnome, KDE, Unity, and Cinnamon I don't know other Linux desktops. Xfce might be one but I never remember the right letters. I spend my day in a Ubuntu VM. Not knowing different ones doesn't make me a bad developer.
Instead of asking about server types, we are asking about desktop environments. This is just to understand how he /she knows about linux world.
*
I think your expectations are unrealistic.*
Agreed, if you start asking Devops questions to frontend guy.
Figure out: how 'junior' a junior developer is!!! ( Now Answers)
manish srivastava ・ Nov 5 ・ 13 min read