3 ms·
i think its a fair question and you've been very polite about it :) I basically deal with it by being super open about it (it's pretty much the first thing any
by swyx 6y ago
i think its a fair question and you've been very polite about it :)
I basically deal with it by being super open about it (it's pretty much the first thing anyone knows about me) and letting people decide if they still want to read me or not. enough do. in a free market, that's plenty.
so the question then becomes: what confidence do I have in what I think I know? it comes from 3 places:
- Empirical foundation: study and read others. this book has 1419 external links and quotes to advice from people way more credible and established than me. I provide curation and context.
- Theoretical foundation: I do my best to ensure what i see in real life is backed up by indisputable logical/psychological axioms. This is important for replicability.
- Personal Experience: I apply what I learn to myself.
Every weakness can be a strength (funny enough, i spend a whole chapter talking about this). In my case, i've basically made a career out of putting out what i learn as i learn it, before i'm an expert, with the responsible disclaimer that I am not an expert but I do put a ton of work into thinking and research. it's the opposite of "fake it til you make it", its being real that you havent made it yet but you do not let that stop you trying. I am at the exact point where my voice and perspective on things (being a recent beginner) let me explain things to beginners in ways that experts can't.
Yes it's uncomfortable af. But you see tremendous growth when you are both intellectually honest and doggedly persistent at this.
As I wrote this book I was also overcome with this personal insight - me 5 years from now would probably not pick this book to write. I would be interested in different things, different challenges. This is pretty much the only time I would ever write a junior-dev-to-senior-dev book: right after having done it.
I suspect this is why so few junior-dev-to-senior-dev books exist - people wait too long, and then by the time they feel qualified to write a book, they care more about management or architecture or what have you.
short answer: no i don't feel very qualified right now. i do intend to update this for a few years. how long until i am qualified? we shall see.
- claudiulodro 6y agoThanks for clarifying. I think I will give it a read, even if just to see what your fresh perspective looks like. The personal branding stuff sounds very interesting and useful also. EDIT: I would like to note that the IMHO most mentally and technically difficult part of a developer career is maintaining the same mission-critical legacy codebase for years at a time. That's not something I really expect to get a lot of insight around from this book and your personal experience, but I'm also not sure what exactly advice around that problem would look like (probably just the tried-and-true military motto of "embrace the suck"). Either way, just my 2 cents about coding careers.
- swyx 6y agothank you for having an open mind, and also being willing to say what others are already thinking, but doing it nicely :) agreed on the maintaining legacy bit. I spent some time on that in the sr dev chapter, but it was mostly collating what others have said. i think its impt that jr devs be aware this is a big part of the job, and also that "technical debt" often pays incredibly well because it is so challenging and the skillset to handle it well is so rare.
- stephc_int13 6y agoAll of this seems kinda legit, learning and be open and using both your experiences and your interactions with others to fix or reinforce your assumptions, but this is not what people usually expect to find in a book... I still have the feeling that there is a bit of greed here, trying to find shortcuts, this is not blatantly wrong but I have the intuition that this is a potentially harmful mindset, not unlike the Move Fast and Break Things mindset.