As a parent of a kid that has special needs (at a minor level), there really is a separate set of skills needed to teach to these kids, as well as needing a better student teacher ratio. It made a huge difference for my kid.
Correct but the point is that the salaries of the developers are not treated as an expense to net out, they are treated as an asset that depreciates over some period of time.
(Even though some "developer" work might be day to day maintenance, rather than building a new feature.)
- How do they take a business problem and model it into code
- How do they debug their own code
- Is their code easy to read
- Do they name their variables/fields/methods/classes in easy to understand and consistent ways or are the names confusing or inaccurate
- How do they take constructive criticism
- How collaborative are they
- Do they think about the problem first or do they just start hacking away
- When asked to add a feature to existing code, do they start hacking or do they write out a test describing the new functionality first
- When confronted with vague requirements, how well do they ask questions to get the information they need
- How much experience do they have with algorithms, database design, systems design, building things so they scale well