How Do You Know a Developer Is Doing a Good Job?

Re:How Do You Know a Developer Is Doing a Good Job? by handojin on Friday February 10, 2017 @02:00AM (#13613739)

   > There are a lot of things between aesthetics and domain
   > knowledge that are audit-able.

I don't disagree with you. The pertinent question is 'does anyone care'?

   > A lot of code bases you can walk into and see a million
   > n+1 queries right away and the architectural patterns
   > that lead to them. Another canary is the test
   > complexity that reveals various anti-patterns like
   > active record. Another is correct IOC usage, a lot of
   > code bases will use it for creating POCO objects for
   > example. These are all very common and quickly
   > discoverable.

Again, I don't disagree. You're right, possibly even corrrect. But we're talking business plans yes? So feel free to buy that expensive suit (or hire a beard) and see if you can explain these issues and why they matter to the people with the money.

"If dogs could talk, perhaps we would find it as hard to get along with them as we do with people."

[ Parent | on HN ]

Re:How Do You Know a Developer Is Doing a Good Job? by flukus on Friday February 10, 2017 @02:46AM (#13613879)

I get what you mean but I do think the care factor could be broken down a bit better. Some simply don't care, talking to them is a waste of time. Some don't care because the can't, they don't have the visibility into things so they're pointless to worry about.

The final group does care, often because there arse is on the line and are often a CXO. These are the ones that love Agile/scrum because they think it'll identify problems early and/or they don't trust their Devs.

Whether a solid business case could be sold I'm not sure, but I think everyone that ever hired a scrum consultant would be the target market.

[ Parent | on HN ]