91–100 of 116 posts
I agree with others on the thread that "maintenance or innovation" is a false dichotomy. In particular, I think we need innovative maintenance. For e.g., this article about new ways to fix potholes: https://www.economist.com/news/science-and-technology/217003...
I mean, I think the best way to start with this is to use a word other than "maintenance." That's not really the most sexy word if you really want people to get behind it. Furthermore it just suggests that the work is keeping something as good as it was from the beginning. Filling in holes, giving it a coat of paint every now and then. What it really should be called is "refinement." The innovation ends up being incr…
The problem seems to be that we've invested far too much federal money into projects that have to be maintained by local sources of funding. Big federal grants for development that will not produce enough tax revenue to offset the externalities and infrastructure costs that are required to maintain that development are just albatrosses around states and cities' necks. https://www.strongtowns.org/journal/2017/1/10/poo…
https://www.strongtowns.org/journal/2014/8/19/is-a-street-an...
Earlier quoted context omitted.
How is that relevant
The parent to my original post is an example of exigology. Paraphrasing: "My code will be gone next year, so I don't care about code style"
> "I'm not good at this because I don't try, so I won't try"
> "Girls don't like me because I have bad hygiene, so why should I bother with hygiene?"
etc.
This would only apply to what I wrote if my code was disappearing because it's not formatted to pass a linter. You and I both know that this isn't the reason code gets deleted. It gets deleted because it gets refactored, or the feature/product it's implementing gets killed.
Furthermore, code quality is not the same thing as code style.
I mean, I think the best way to start with this is to use a word other than "maintenance." That's not really the most sexy word if you really want people to get behind it. Furthermore it just suggests that the work is keeping something as good as it was from the beginning. Filling in holes, giving it a coat of paint every now and then. What it really should be called is "refinement." The innovation ends up being incr…
Earlier quoted context omitted.
The parent to my original post is an example of exigology. Paraphrasing: "My code will be gone next year, so I don't care about code style"
The SMBC comic mocks the people for not being self-aware enough to realize that they are causing their own problem by being apathetic. > "I'm not good at this because I don't try, so I won't try" > "Girls don't like me because I have bad hygiene, so why should I bother with hygiene?" etc. This would only apply to what I wrote if my code was disappearing because it's not formatted to pass a linter. You and I both know…
I did misparaphrase you. My apologies for that. Fixed.
But as for the other argument, I think the comic's examples and your case represent feedback loops in which two factors are both cause and consequence of each other.
I believe you that you started not caring about code style after you noticed your code tends not to last. Similarly, life was short already before bacon existed. Would you agree that your code is more likely to dissapper now that you don't care about style?