News for hackers. Stuff that matters.

iddogino

Still don't get why people are constantly surprised at the difficulty of building a career and having kids. Having kids is a life choice with upsides (awesome upsides imo) and downsides. Same goes for having a career in tech. Wanna do both? You can, but YOU WILL have to work 2x harder than all the people doing only one of these (arguably, you'll also get a lot more).
Re:Exploring CLI Best Practices on Tuesday October 11, 2016 @05:22PM (#12688625)
Reminds me of this super useful thread from SO http://programmers.stackexchange.com/questions/307467/what-a...
In my opinion this is a very important battle, even if this will be a 100% internal API. Think about the possible scenario - no one touches one of the endpoints for 18 months. A new developer comes in and wants to use it. There are no docs and no one remembers what's going on there. == mess.
I'd argue that this should go the other way around. Your developers should be creating the 'docs' - the API design and boilerplate, before programing it. If they actually sit down and design the API before setting of to write the code you'll end up with: (a) the documentation you want. (b) an API that this designed consistently and consciously. Would you let your front end developers build something without at least a wire frame / functional design?