3 ms·
Memorizing a bunch of algorithms doesn't make you a software engineer. A software engineer should be able to read an algorithm's description, without having eve
by theli0nheart 9y ago
Memorizing a bunch of algorithms doesn't make you a software engineer. A software engineer should be able to read an algorithm's description, without having ever seen it before, and implement it correctly in code. Too many people equate memorization with aptitude or skill.
It's too bad that most interview processes don't differentiate between these, and this guide perpetuates that problem.
- vanillapepsi 9y agoAnd how does one does that? That's right, by studying algorithms in and out.
- iandanforth 9y agoLet me reframe this. You need to be able to 1. Clearly describe a problem 2. Notice when that problem can be mapped to one or more known solutions or algorithms 3. Be able to implement a system which takes those core solutions and makes them work together in a robust, efficient, scalable, and useable way.
- sidlls 9y agoAlmost none of which requires one to be able to implement said algorithms from scratch on demand in a 45 minute interview. Yet, here we are where exactly that is the norm in certain circles. Just one more reason why I consider the state of the industry to be closer to farce than reason.
- pbhjpbhj 9y agoOf those who can do iandanforth's 3 steps what's the intersection with the group who can program algorithms from scratch under interview conditions. The latter is supposed to be a proxy for the former, not a test of it, surely?