My point today is that, if we wish to count lines of code, we should not regard them as "lines produced" but as "lines spent": the current conventional wisdom is so foolish as to book that count on the wrong side of the ledger.
As a dev I very much subscribe to this line of thought, but I also have to admit most of the business class people would disagree.
Engineers at higher levels, like staff engineers, are expected to still regularly code.
As they should. The non coding software developer is one of my pet peeves, call it architect if you want. I can appreciate the idea of collecting a paycheck producing wiki entries, drawing diagrams and making slideshows, but they are no substitute for leading by example. In fact, my empirical finding is that the tendency to describe software in prose is usually inversely correlated with the technical ability to create the executable.
As someone considering switching from Firefox, I don't trust Moz://a's willingness to disrupt the status quo. In fact, at the moment I'm not entirely sure they are not simply entrenching Chrome by blocking other niche browsers to gain market share.
As a dev I very much subscribe to this line of thought, but I also have to admit most of the business class people would disagree.