Ask HN: Why can't I find work with a well-documented code base? • Hacker News Board

Re: Ask HN: Why can't I find work with a well-documented code base?

#11

Post by yen223 » Mon, Jun 09, 2014, 1:32 PM UTC

joeq wrote: post #7

atmosx wrote: post #6

Earlier quoted context omitted.

Isn't that a weird thing? Every recruiter post I'm seeing talks about how to write unit test , write clear comments , choose methods (functions) name with care , document your code even if it looks silly and again write tests! . It's like what everyone wants, but then neither needs...

It seems as absurd to me as constructing a building without laying down foundations and having proper blueprints.

This is the perfect analogy - people might choose a house based on its size or its location. But nobody buys a house because it has strong foundations. Not that foundations aren't important, mind you.

Re: Ask HN: Why can't I find work with a well-documented code base?

#12

Post by GFischer » Mon, Jun 09, 2014, 2:40 PM UTC

SamReidHughes wrote: post #10

joeq wrote: post #8

Earlier quoted context omitted.

Yep, Code Complete, Mythical Man-Month. They are so highly regarded, but nobody seems to follow them!

One of those is highly regarded.

Can you ellaborate? Which one is which? I guess the Mythical Man-Month is the well-regarded one?

Re: Ask HN: Why can't I find work with a well-documented code base?

#13

Post by GFischer » Mon, Jun 09, 2014, 2:47 PM UTC

joeq wrote: post #9

anonymousdev wrote: post #4

Well this is the state of the industry. There certainly are companies with well-written, well-documented, well-tested code but they don't hire because they don't need to. Their code is easy to change and maintain, so why pay more people? This is all most project managers know - absolutely never improve the process or the tools, just throw more people at the problem, so that's why you were there.

Considering leaving the industry because of this. Which is a shame because I really do care about good software.

Don't (unless you really don't like writing software).

The answer I've come up with is either become a project manager (not working out so far, nobody wants to hire a PM without PM experience here, no matter the certifications), or start your own company (which might be the right answer in your case).

To be honest, I think both documentation and test cases are overrated, I do believe in lots of user testing and feedback, which is the most important thing (and that's why I believe any methodology that encourages frequent user feedback is a good thing).

What I'm writing about applies for the usual business or customer facing apps, I don't know about other fields (maybe for scientifical or medical or whatever apps it's a whole different story).