I find the article amusing but it feels like it is missing a clear closing statement about why this matters.
My take is that "dumb and get things done" is dangerous because they can do harm quickly, unlike dumb and lazy which at least doesn't get on the way. These are the ones that pump thousands of lines of spaghetti code, copy pasting all over the place and creating a unmaintainable big ball of mud. They are the ones that implement the first solution that comes to mind before considering alternatives. Are the ones that never refactor or tidy their code and simply add another if statement.
The irony is that in certain companies these people might be seen as heroes. After all, isn't it more impressive to produce hundreds of complicated lines of code in half the time rather than a few dozen of clean and maintainable lines of code in twice the time.
My take is that "dumb and get things done" is dangerous because they can do harm quickly, unlike dumb and lazy which at least doesn't get on the way. These are the ones that pump thousands of lines of spaghetti code, copy pasting all over the place and creating a unmaintainable big ball of mud. They are the ones that implement the first solution that comes to mind before considering alternatives. Are the ones that never refactor or tidy their code and simply add another if statement.
The irony is that in certain companies these people might be seen as heroes. After all, isn't it more impressive to produce hundreds of complicated lines of code in half the time rather than a few dozen of clean and maintainable lines of code in twice the time.