I love that article. Again harsh reality is that on average interview for a developer in London they will ask you all those questions and much more. And if you get hired by any chance in fintech you will most probably spend majority of your time on meetings and working with Excel spreadsheet... never touching any code.
Things I Don’t Know as of 2018
21–30 of 119 posts
Re: Things I Don’t Know as of 2018
#22This article really makes me feel good as a current intern and comp sci student. I thought I clearly defined what a junior dev could be if I worked at it for another year. Having read all the stuff this guy doesn't know and what I've learned at my internship, it's almost any hint of imposter syndrome I might of had went away.
Now I'm not saying he doesn't know how to program. I'm just saying it's very interesting to me how little you actually have to specialize in to make it in this field. What my internship has taught me, it really makes me feel secure job wise knowing I won't have difficulty being employed in the areas I know. I hate sounding so cocky but when I first started schooling again geared toward comp sci, I thought programmers knew just absurd amounts of stuff. Now I've found, they typically are just the average tech savvy individuals that weren't afraid to poke around in an OS.
Re: Things I Don’t Know as of 2018
#23Earlier quoted context omitted.
But you can also apply JIT to learning as well. Depending on your work, you may come across a situation that needs these things anywhere on the continuum from often to never. As the OP is a Facebook employee working as a core React team member, not knowing all these things clearly hasn't been a huge blocker. But similarly, he might well know these things to an above-average level, and just think that he doesn't.
"As the OP is a Facebook employee working as a core React team member, not knowing all these things clearly hasn't been a huge blocker." In a practical sense that should be fine, given the level of specialization that a company like Facebook can have given its size and scope. But I wonder if Dan would make it through the average Facebook engineer interview without his Redux cred however. He is also the rare person wh…
Now you got me wondering how people who got more well known creating open source projects go through hiring process at these big tech cos. I know creator of Homebrew still had to go through typical google interview.
I am talking about people like Jon Gjengset who got hired to work on Rust at AWS.
Re: Things I Don’t Know as of 2018
#24This is common. I think there are few people that are masters at everything. Instead you should focus on building a talent stack or a skills mosaic. (Choose whichever term you want). The point is you might not be a master in any one subject but you might be pretty good at a handful of things. That permutation is enough to make you valuable and unique.
Re: Things I Don’t Know as of 2018
#25This article really makes me feel good as a current intern and comp sci student. I thought I clearly defined what a junior dev could be if I worked at it for another year. Having read all the stuff this guy doesn't know and what I've learned at my internship, it's almost any hint of imposter syndrome I might of had went away. Now I'm not saying he doesn't know how to program. I'm just saying it's very interesting to…
Shush you, you're giving away the secret to my 6 figure salary.
Re: Things I Don’t Know as of 2018
#26I'd love to see lists like this from more high-profile programmers. What does John Carmack not know? What does Dan Bernstein not know? What does Bryan Cantrill not know?
Probably more than you'd think, although they'd not be so dumb as to vocalise it as one's career depends entirely on one's percieved capabilities.
Re: Things I Don’t Know as of 2018
#27There is a finite amount things we know and an infinite amounts of things we don't. Hence trying to list ones we do not know is futile. :)
It's not a comprehensive list of things this individual doesn't know. It's limited to technologies which other people assume they would know.
Re: Things I Don’t Know as of 2018
#28I'd love to see lists like this from more high-profile programmers. What does John Carmack not know? What does Dan Bernstein not know? What does Bryan Cantrill not know?
> What does John Carmack not know?
Vim or Emacs IIRC.
Re: Things I Don’t Know as of 2018
#29This article really makes me feel good as a current intern and comp sci student. I thought I clearly defined what a junior dev could be if I worked at it for another year. Having read all the stuff this guy doesn't know and what I've learned at my internship, it's almost any hint of imposter syndrome I might of had went away. Now I'm not saying he doesn't know how to program. I'm just saying it's very interesting to…
[deleted]
Re: Things I Don’t Know as of 2018
#30From the list, I would suggest to learn C, because a lot of stuff is written in it or at least uses its ABI. So understanding that will give you a lot of leverage. Besides that, a deep dive into operating systems (yes, that means to get rid of MacOS if you use it) will give you a solid foundation to understand networking, containers and even more.
> I would suggest to learn C, because a lot of stuff is written in it
Does it also mean we all need to learn how to design integrated circuits?