Live data from Hacker News

On Being a Junior Developer

mattsencenbaugh.com

11–20 of 73 posts

Re: On Being a Junior Developer

#11
I really, really wish TDD, or any concept of unit testing had been taught in my courses. Nothing has improved my ability to understand decoupling, orthogonality, and the importance of naming conventions than test writing. And on days when I can't muster the energy to write heavy code, I can at least write the tests that I know I'll need to pass...and the next day, that heavy code task is practically done.

TDD is both a good practice and a great psychological boost.

Re: On Being a Junior Developer

#12

The biggest one I'd recommend is "find a mentor." And I don't mean a manager (unless you're going on that path), but rather a technical leader that you can meet with once a week to month whose opinion you value and can provide you honest feedback on your work. You should plan to drive these meetings; count on them only to show up, drink coffee, and answer your questions. If it is not your most valuable hour of the we…

Can I ask what those issues are?

Re: On Being a Junior Developer

#13

The biggest one I'd recommend is "find a mentor." And I don't mean a manager (unless you're going on that path), but rather a technical leader that you can meet with once a week to month whose opinion you value and can provide you honest feedback on your work. You should plan to drive these meetings; count on them only to show up, drink coffee, and answer your questions. If it is not your most valuable hour of the we…

I agree with this. I had an internship, and the mentor really made it what it was. Even if you can only end up at a mediocre company, if you have a good mentor it will be a success.

Re: On Being a Junior Developer

#15

I would fault some of the points listed, like "Embrace Unit Testing", to a failure of Software Engineering as a discipline. Mechanical Engineering, Electrical Engineering, Physics, Doctors, etc. all have bodies of knowledge. We, as an industry and discipline, have no real body of knowledge. Do Doctors have the ability to make up procedure on the operating table? Why is it, then, that we don't have standard practices,…

Software engineering as a thing is less than thirty years old, those other careers have been around for hundreds if not thousands of years, the body of knowledge will come in time.

Re: On Being a Junior Developer

#16

The biggest one I'd recommend is "find a mentor." And I don't mean a manager (unless you're going on that path), but rather a technical leader that you can meet with once a week to month whose opinion you value and can provide you honest feedback on your work. You should plan to drive these meetings; count on them only to show up, drink coffee, and answer your questions. If it is not your most valuable hour of the we…

Great advice on technical mentor! Will start looking for one myself now.

Re: On Being a Junior Developer

#17

I would fault some of the points listed, like "Embrace Unit Testing", to a failure of Software Engineering as a discipline. Mechanical Engineering, Electrical Engineering, Physics, Doctors, etc. all have bodies of knowledge. We, as an industry and discipline, have no real body of knowledge. Do Doctors have the ability to make up procedure on the operating table? Why is it, then, that we don't have standard practices,…

No.

They are part of the curriculum in a good SE degree. There is a SWEBOK. http://www.computer.org/portal/web/swebok

Re: On Being a Junior Developer

#18
am i the only one who finds the article only marginally related to "being a junior/senior/antique developer"?

i would summarize it as: be smart constantly learn find people that are better than you.

but then again, most "seniors" probably never did any of the aforementioned. i met an ex oxford(or cambridge) cs prof who's now doing his own startup a while back.

The main thing that struck me was that how willing he was to accept advice, even though he tought one of the first cs courses in the uk.

Re: On Being a Junior Developer

#19

This is only tangentially related: I work a relatively big startup and I'm not not in the technical side of the company. A piece of "simple"* software was built and deployed about 4 months ago, it was a week of one developers time start to finish. Ever since deployment there has been bug after bug after bug, every time they fix one bug they break something else. This is an extremely simple system that should (in my e…

It's hard to say without all the details. It's also the kind of thing that can be hard to gauge from outside the project. It could be new developers making rookie mistakes. It could be simple incompetence. Or it could be that what sounds simple to you on the surface balloons in complexity after being forced to fully engage with the problem and all its edge cases.

If it's closer to the second, it could signify more of a failure of process than a failure of engineering if engineers are being pushed to release quickly at the expense of planning, time for refactoring, qa, unit tests, etc. That "this should be easy, why's it taking so long??!" attitude can create a toxic environment if it's coming from people who don't understand the issues involved.

Re: On Being a Junior Developer

#20
I recommend contributing to open source projects, particularly well-known ones. It is a good way to see how other people and projects work, expand your resume experience, and network with people in other companies.
Post reply on HN