4 ms·
> Can only imagine what this is doing to code quality... Why would studying algorithms and data structures affect code quality? They would similarly be able to
by triceratops 7y ago
> Can only imagine what this is doing to code quality...
Why would studying algorithms and data structures affect code quality? They would similarly be able to learn to write quality code once they're inside the company, no?
- _hardwaregeek 7y agoBecause you get the college applications problem, where you stop getting the people who have a real passion for programming and coincidentally have problem solving and algorithms skills, and start getting people who are really good at problem solving and algorithms and may or may not have a passion for programming.
- triceratops 7y ago> start getting people who are really good at problem solving and algorithms and may or may not have a passion for programming. Why is "passion" so important? And what even is passion? For professionals in every other field, competence, ability to deliver results, and getting along with people, are what matter. Many pros are passionate, in the sense of loving their work, but passion isn't a prerequisite for being a pro.
- povertyworld 7y agoMost programming is not solving tricky puzzles, but grinding out code.
- triceratops 7y ago> most programming is not solving tricky puzzles, but grinding out code. Sounds like most jobs need dispassionate guns-for-hire who'll do excellent work, no matter how tedious, get paid, and go home. In other words: pros.
- deleted 7y ago[deleted]
- _hardwaregeek 7y agoOy vey. I didn't mean passion in the "I'll work 80 hours a week for little pay mister!" kind of way. I mispoke. I meant that before, if you based your interview process off data structures and algorithms, you'd get competent professionals who just happened to be good at algorithms. While now you'll get a bunch of people who have specifically trained to be good at algorithms. Which has no bearing on competence.
- triceratops 7y agoWhy can't people who study to get good at algorithms also study to write better code? They've already demonstrated their aptitude for learning difficult things.
- _hardwaregeek 7y agoFor one, interviewing requires extremely short term knowledge. Almost everybody I know who plays the interviewing game learns just enough to pass the interviews, then immediately forgets it until the next time. So it's not really comparable to learning and refining a difficult topic over the course of a few years, as in the case of software development practices. Also, it's two completely different skillsets! There's something very weird about interviewing for X but then demanding Y. I don't ask my primary care physician how good he is at surgery, then be like "he knows how to learn difficult tasks, so we're good".
- triceratops 7y ago> Almost everybody I know who plays the interviewing game learns just enough to pass the interviews, then immediately forgets it until the next time Presumably the first time they learned computer science fundamentals it took them some time right? People usually go to college for several years to learn this stuff - or 6-month bootcamps for 40-60 hours/week. Subsequently of course it'll take less time to refresh their knowledge. > Also, it's two completely different skillsets! There's something very weird about interviewing for X but then demanding Y I'm not disagreeing here. I just think most companies that use this interviewing style figure that X (easy to measure in 45-minute interviews) is a reasonable proxy for Y (much harder to measure). And Y (writing good code) is easier to train new employees to do as long as current employees maintain standards in code reviews.
- jjav 7y agoThis race to the bottom, as parent poster said, is from a generation of developers hyper-specializing in interview-style problems. These problems are tiny and self-contained and have a slick solution which can be regurgitated onto a whiteboard in about 30 minutes give or take. While that is not a negative skill to have, it is also not a skill that I'd list anywhere in the Top-25 of most valuable skills for productive developers.
- 13thThief 7y agoJust curious, could you list the top 25 (anecdotal?) valuable skills for a productive developer? Thanks.
- codingslave 7y agoBecause these people are just memorizing coding problems. It's like a spelling b
- lawn 7y agoBecause these problems encourages you to write unreadable code. It makes sense when you write it, because you can fit it in your head, but you never have to revisit it after having passed the problem. It encourages one letter variable names and other quick hacks in the name of speed. They work against creating readable, understandable and debuggable code which is much more important in general than being able to solve algorithimical problems you'll almost never see in real life. I've seen this first hand where some were brilliant at these problems but wrote the worst code imaginable. I would rather hire someone who can write clean and simple code and teach them how to solve these problems than the reverse.
- username90 7y ago> I would rather hire someone who can write clean and simple code and teach them how to solve these problems than the reverse. Why? Teaching people to write readable code happens automatically during code reviews, teaching people how to think is a lot harder.
- lawn 7y agoBecause producing simple and good code is much more important. It's quite condescending and narrow-minded to say that solving algorithmic problems is thinking, but writing clean and simple code isn't. Writing readable code is much more than just formatting code and using decent variable names. It's about simplifying your design just enough. Code reviews is not enough to teach someone this.
- triceratops 7y ago> Because these problems encourages you to write unreadable code. First off, no, writing good code in an interview wins you additional points. Second, why do you think candidates can (or will) continue doing that on the job? New employees aren't allowed free rein to check in code from day 1 at most places - trust has to be earned. And I don't think any decent company allows check-ins without review.
- closeparen 7y ago