Live data from Hacker News

Show HN: Coding Career Handbook

learninpublic.org

111–120 of 140 posts

Re: Show HN: Coding Career Handbook

#111

Earlier quoted context omitted.

Honestly I don't know. There is so much cargo culting nowadays in software development (agile, GitHub, white board interviews, hacker rank, tdd, add, ci, cd, redux, etc etc) and so many new people ( I worked in 3 different React projects in the last 2 years with 3 different teams. Only one required something as complex as Redux (and most likely Flux or other simpler state libraries would do). You know what? All of th…

I'm a Redux maintainer. FWIW, we've _always_ tried to clarify when it actually makes sense to use Redux: https://redux.js.org/faq/general#when-should-i-use-redux https://medium.com/@dan_abramov/you-might-not-need-redux-be4...

I know, and I thank you for that. I have read and shared those links (and others).

Unfortunately it falls on deaf ears and it is still overused pretty much everywhere.

Re: Show HN: Coding Career Handbook

#112

Any free version I can audit? Not convinced this is worth the money since you have 2 years of experience, but I am willing to invest some time to prove myself wrong.

hi Anton - there wasn't - but now there is! i've put up 4 chapters for you to evaluate - no email needed. https://www.learninpublic.org/#learn-more

Re: Show HN: Coding Career Handbook

#113

The book may be an excellent resource, but this appears to be just an advert - are there free examples you can point us to? It would be better to link directly to that page I think.

hi! - there wasn't - this is a result of my noobyness doing this - but now there is! i've put up 4 chapters for you to evaluate - no email needed. https://www.learninpublic.org/#learn-more

Re: Show HN: Coding Career Handbook

#115

Earlier quoted context omitted.

I highly doubt sales would increase by 10x, or even 2x. This book isn't trying to sell itself by saying "hey, buy me and you'll be entertained for three hours, which is a better value than a movie ticket". This book is trying to convince potential customers that it will help them graduate from junior engineer at local_company to senior engineer at FAANG. It's no coincidence that the author mentioned right here in his…

Lol that job title doesn't mean shit to anyone except clowns like this chasing money. The guy has 2 years experience and you're pointing to his job title as if he's some genius... That's why this book is actually devoid of any novel content

> your pointing to his job title as if he's some genius

No, that's just you projecting.

Re: Show HN: Coding Career Handbook

#116

Earlier quoted context omitted.

Lol that job title doesn't mean shit to anyone except clowns like this chasing money. The guy has 2 years experience and you're pointing to his job title as if he's some genius... That's why this book is actually devoid of any novel content

> your pointing to his job title as if he's some genius No, that's just you projecting.

Then why does him being a "senior level faang employee" matter so much? This doesn't qualify him for anything.

Re: Show HN: Coding Career Handbook

#117

Earlier quoted context omitted.

> your pointing to his job title as if he's some genius No, that's just you projecting.

Then why does him being a "senior level faang employee" matter so much? This doesn't qualify him for anything.

I did not point to him being a senior engineer at FAANG, I pointed to him mentioning that he's a senior engineer at FAANG, as evidence that the book is marketed towards people who also want to become senior engineers at FAANG.

As mentioned in my original comment, I fully realize that plenty of people couldn't care less about becoming senior engineers at FAANG, and am not making any claims about the intelligence or qualifications of the author or the quality of the book.

Re: Show HN: Coding Career Handbook

#119
post #72

I typically don’t trust anyone who uses the word “coding”.

naming is hard... so the background on this is that the book was originally called "Cracking the Coding Career" for the alliteration and for the mirror with "Cracking the Coding Interview". I nearly even shipped with that name - until Gayle McDowell got in touch and said this would break her trademark. So I had to tweak it. I considered maybe a dozen other names but believe it or not they were worse :(

Gayle's usage, "coding interview," specifies which part of the interview loop her book focuses on. Of course there are many other attributes and skills assessed in an interview loop: design, architecture, debugging, technical communication, experience, domain knowledge, leadership, etc.

The usage of "coding" with respect to the job often comes off as a polemic against those other facets. Sometimes this is what you want! Maybe you're breaking free of all that architecture astronomy and faux-agile BS to just build stuff. Maybe you're differentiating yourself from your senior colleagues who seem to write only documents. Maybe you want to hire someone to shut up and type, not pester you about tech debt. But these are all fighting words.

It gets old when people pick up this usage and repeat it without even meaning it.

Post reply on HN