51–60 of 157 posts
Oh, you will feel much better once you have mastered: 1. Programming chips in binary, machine code, and C. You need a variety of chips. Try to learn at least 5 from each manufacturer. 2. Learn at least 37 Javascript frameworks, as evenly divided between front-end and server side as you can. (Good news: angular 1 and 2 count as 2 frameworks). 3. Learn Scala, Rust, Haskell, C, C#, Java. (Python and Ruby go without sayi…
Oh, you will feel much better once you have mastered: 1. Programming chips in binary, machine code, and C. You need a variety of chips. Try to learn at least 5 from each manufacturer. 2. Learn at least 37 Javascript frameworks, as evenly divided between front-end and server side as you can. (Good news: angular 1 and 2 count as 2 frameworks). 3. Learn Scala, Rust, Haskell, C, C#, Java. (Python and Ruby go without sayi…
37? Only?
Attempting to be as accomplished/skilled as the union of people you read on the Internet is a fool's errand. You have to accept you'll never know everything and that, for almost all things, there will be someone -- or a lot of someones -- much better than you. Pretend you were working at a company with a hundred engineers. Do you understand how easy it is for every single one of them to simultaneously feel like you d…
Also, do realize that not everybody is right on here all of the time either, despite some of their egos.
Despite occasionally butting heads with some of the people on here, I really do appreciate the community here for what it is; you really can't find a smarter group of people on the Internet.
Oh, you will feel much better once you have mastered: 1. Programming chips in binary, machine code, and C. You need a variety of chips. Try to learn at least 5 from each manufacturer. 2. Learn at least 37 Javascript frameworks, as evenly divided between front-end and server side as you can. (Good news: angular 1 and 2 count as 2 frameworks). 3. Learn Scala, Rust, Haskell, C, C#, Java. (Python and Ruby go without sayi…
You forgot entrepreneurial skills. Obviously at the top of that list should be the ability to raise funds from VCs.
I don't know if I can recommend "learning" to raise from VCs but you're right they should practice all aspects of launching and running a company a few times by doing it.
Oh, you will feel much better once you have mastered: 1. Programming chips in binary, machine code, and C. You need a variety of chips. Try to learn at least 5 from each manufacturer. 2. Learn at least 37 Javascript frameworks, as evenly divided between front-end and server side as you can. (Good news: angular 1 and 2 count as 2 frameworks). 3. Learn Scala, Rust, Haskell, C, C#, Java. (Python and Ruby go without sayi…
You forgot entrepreneurial skills. Obviously at the top of that list should be the ability to raise funds from VCs.
If a business is solid, no funding is needed. Or, if it is needed, it's easy to get.
Oh, you will feel much better once you have mastered: 1. Programming chips in binary, machine code, and C. You need a variety of chips. Try to learn at least 5 from each manufacturer. 2. Learn at least 37 Javascript frameworks, as evenly divided between front-end and server side as you can. (Good news: angular 1 and 2 count as 2 frameworks). 3. Learn Scala, Rust, Haskell, C, C#, Java. (Python and Ruby go without sayi…
1. An in depth understanding of Physics, History, Literature, and Philosophy. You can just make up whatever you want in Economics, Sociology, and Bitcoins as fits your political leanings.
2. Learn to resist weapons grade grammar analysis.
3. Learn to recognize sarcasm in short, written text.
Fill your bowl to the brim and it will spill. Keep sharpening your knife and it will blunt. Chase after money and security and your heart will never unclench. Care about people's approval and you will be their prisoner. Do your work, then step back. The only path to serenity. -- Tao Te Ching , Stephen Mitchell translation ( http://acc6.its.brooklyn.cuny.edu/~phalsall/texts/taote-v3.h... )
I think this is a perspective problem. You need to stop comparing yourself to everyone in all things. That isn't what I come here for. I just come here to gratify my intellect and enrich my life. You don't need to compare to people here. You need to compare yourself to people you are in actual competition with at work or compare yourself to the work standards you are expected to meet. Don't come here and do that. It will only lead to misery.
I've found that it's not often that I need to be as intimately acquainted with a subject as those who are feature on HN appear to be. In fact, just knowing about something has been enough for me to intelligently answer an interview questions, converse with a senior engineer, or make the right decision on a project. And usually that's because what's most important is being curious and asking questions - e.g. admitting to myself that I'm not an expert.
Now, instead of being a testament to my ignorance and personal failings, HN is portal that let's me feed my curiosity.
You may want to do some research on the impostor syndrome. It's been my experience that anyone who's any good at anything is convinced they'll never "catch up."
I can usually cure it by going to a Sharepoint developers' meetup, or something similar. Running into people who there who are doing consulting work and doing very, very well for themselves while working significantly less that 40 hours a week and using almost none of the cool stuff that gets mentioned on HN.
I suppose the lesson there might be to avoid a game of one-upmanship with alpha nerds. And I don't say 'alpha nerds' in a derogatory sense. It's just that on HN, you're going to encounter lots of people who will run circles around you in one domain or another. And some people love being the absolute expert in their particular technical domain.
That's okay. Good for them, actually! Everyone should do what makes them happy. You might find you're actually happier in a role that is more concerned with the business problems you're solving than with needing to be an expert in everything you see mentioned on HN. Your technical skills will be important, but not as important as your ability to use those skills to help a business 1) save money, 2) make more money, or 3) both.