4 ms·
There are still companies who refuse to believe this and still put Senior+ devs through hell during an interview process with junior level algorithm memorizatio
by reactordev 2mo ago
There are still companies who refuse to believe this and still put Senior+ devs through hell during an interview process with junior level algorithm memorization.
In all aspects there will be dinosaurs and deniers and there will be embracers.
- watwut 2mo agoThere is no such thing as "junior level algorithm". And one does not memorize algorithms.
- saulpw 2mo agobubblesort has entered the chat
- Izkata 2mo agoBetter example, leetcode interviews became so popular because people were memorizing FizzBuzz and they needed an alternative (but said interviewers didn't fully understand the purpose of FizzBuzz and though "harder means better, right?").
- watwut 2mo agoleetcode interviews be ame a thing, because many believed solving leetcode style puzzles makes you superior. Not because someone would memorize fizzbuzz. This thinking was popularized by coding competions which existed before leetcode and inspired leetcode. Schools themselves produced people who believed these puzzles are what makes you superior developer - one of us, special and choosen.
- spacechild1 2mo agoHow can you assess the output of coding agents if you don't know about algorithms and other fundamentals of software engineering?
- foldr 2mo agoI don’t particularly mind algorithmic interview questions (they’re at least self-contained, somewhat objective, and something you can prepare for), but most software engineering has always been done by people with no knowledge of algorithms or compsci fundamentals. What’s being lost is coding fluency, not compsci knowledge.
- skeledrew 2mo agoUser acceptance testing.
- reactordev 2mo agoI think you misread. I never said not to learn it. In fact, for your entry level I would recommend testing for it. At senior+ it should be more about software architecture, design patterns, and distributed systems.