5 ms·
> Basically, this question is to software engineers as FizzBuzz is to programmers I don't get this comment at the end or the follow-up article? What's the diff
by dirkc 3y ago
> Basically, this question is to software engineers as FizzBuzz is to programmers
I don't get this comment at the end or the follow-up article? What's the difference, sure, FizzBuzz is a simpler problem, but I would imagine it being a common interview question for software engineers
- 000ooo000 3y agoGarden-variety elitism. Safely ignored.
- brickteacup 3y ago"Expecting basic programming ability" isn't elitism, sorry
- ric2b 3y agoIf it's basic programming ability why bother making the distinction?
- ZephyrBlu 3y agoThe point he's making is that software engineering skills are about a lot more than just programming. Being able to navigate an existing codebase, implement new functionality and blend it into the surroundings is an important skillset that is pretty distinct to just writing code.
- UncleMeat 3y agoThat to me still feels very much like a programming task. To me, broadening to software engineering means things like requirements gathering, timeline estimation, prioritization, etc. If you just wanted to focus on code I'd choose things like writing programs that are extensible over writing extensions to existing programs.
- ZephyrBlu 3y agoAnd yet many people on this post are claiming that they cannot tackle this task for a variety of reasons non-programmming reasons (I.e. they don't even get to the programming bit of software engineering). Sure, it might not hit everything but it hits quite a lot of important skills.