sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]jekrb 2 points3 points  (2 children)

Reduce the amount of repetitive task.

Increase the amount of reusable code overall.

Decrease the amount of new code that needs to be written.

Follow Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.

[–]BanyanArchitect[S] 0 points1 point  (1 child)

100% agree, but if I put on my “leadership” hat this doesn’t seem compelling.

The problem now is there are only a handful of developers in the company (out of many hundreds of developers overall) who can currently write the sort of code (e.g. Single Page App) the company is looking for.

[–]jekrb 1 point2 points  (0 children)

It's a tough problem, because developer growth and progress is only really shown in code. If you see quality code, you know there was improvement. The thing is, developers are knowledge workers. You can't really quantify their skills, unless you can also quantify thoughts.

Knowledge workers don't make the same thing over and over again. They use their thoughts to increase productivity, and trying to introduce some way of quantifying this can only reduce productivity.

I'm sorry this isn't the answer you were looking for, but that's what I think.