Just a reminder that all bug prioritisation schemes in practice degenerate to three scheduling categories: do it now, do it later, never do it.
If you have a numbered system with many priority levels, what you actually have is a bureaucratic system of denial.
"What are the non-functional requirements for the system?"
"We don't have any."
"Sorry?"
"We want the system to function."
"Oh, I see... in software we often use 'non-functional' to mean something else."
"In English we use non-functional to mean non-functional."
#UseTheRightWords
Computer Science: Sorting algorithms, sorting algorithms, more sorting algorithms...
Everyone: Yeah, yeah, we know!
Facebook: Here are your notifications from 31, 49, 26, 29 and 55 minutes ago 🤦♂️
The common obsession with speed (a.k.a. velocity) in agile approaches is not healthy. We should take a cue from the Slow Food movement and promote Slow Agile, e.g., replace sprints with walks, with a preference for strolls over brisk walks.
Once more, with feeling:
• POJO does not mean DTO.
• POJO does not mean that a class has to be as dumb as rocks, with nothing more than getters and setters.
• POJO means that a class is not tied to a particular framework, whether by inheritance or annotation.
Programming is not a zero-sum game. Teaching something to a fellow programmer doesn't take it away from you. I'm happy to share what I can, because I'm in it for the love of programming.
— John Carmack
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.
— Edsger W Dijkstra
Something I keep hearing from developers is "Our PO/manager/business says that customers won't pay for refactoring/testing/architecture/quality/etc."
OK, time to call bullshit on this: I'll put good money on the customer never being presented with this option.
I wish developers felt they could slow down and look around, think about what they were doing, etc.
In many cases, verbose code, inconsistencies, weird logic, etc. are all a consequence of organisational culture, giving rise to unwitting ignorance and ingraining of poor habits.
