3 ms·
And you really need everyone in your group to be the same type or you will have a lot of butting heads. I was once contracting on a project where I was buildin
by jedberg 5y ago
And you really need everyone in your group to be the same type or you will have a lot of butting heads. I was once contracting on a project where I was building code to solve urgent business problems. By necessity of the timeline, the code was ok but not perfect.
Then they brought on a new manager, who immediately ran all my code through a linter and told me to stop all work until the linter came up clean. I told him that I was hired to make working code that solves an immediate problem, and he told me my services were no longer required.
I found out later the project was quickly moved to another team because his team was unable to meet the tight timelines.
- userbinator 5y agoThat's the difference between process-oriented and result-oriented thinking. I've also heard the two extremes being referred to as "tool-worshipping fools" and "rule-breaking fools".
- vkou 5y agoOrganizations tend reward process-oriented thinking regardless of whether it succeeds or not, and results-oriented thinking only if it succeeds.
- geoduck14 5y ago>Organizations tend reward process-oriented thinking regardless of whether it succeeds or not I'm not sure if my experience aligns with this
- kqr 5y agoThis seems incorrect. The archetypal process-oriented professional in my book is the money-making poker player. In poker, you cannot control the result of any hand -- not even the result of a week's play. To achieve long-term success, you must have a good process for your playing, and not be influenced by the results. A good process sets you up for the best chance of success, but it cannot guarantee success. If you start to adjust based on results (and not deeper changes to the causal matrix -- these are process-informed changes) you'll do worse. Edwards Deming called this "tampering". The same thing applies, of course, in business. The greatest process will produce bad results if you're unlucky with uncontrollable external factors. A bad process can by chance produce good results if you're lucky with uncontrollable external factors. You cannot judge a process by its results in individual instances alone. Judgment of a process must be made in terms of theory, repeated experiment, and long-term tendencies of the outcomes. And, as in poker, any long-term successful business is process-oriented. They carefully build processes that set them up for greatest chance of repeated success. Any results-oriented business has -- by de-emphasising the process -- no way to influence the outcome. They are "driving on the highway by looking at the centre line in the rear view mirror" as someone put it. Theory and process is the only thing that can tell you anything about future results. I strongly recommend reading Deming's The New Economics.
- reidjs 5y agoLinters, Test Coverage, and Code quality reports are amazing and important. But these things don’t affect your customers directly. I think some engineers like spearheading these types of projects because they are safe to implement and easy to understand.