1. all programmers who aren't morons work primarily from example 2. when your tech debt hangs around this causes it to be used as an example Murphy's corollary: the worst of your tech debt will be most frequently used as an example
-
-
that's a bit glib but I don't mean it just as a quip. while it's possible to write usefully on software engineering topics, I don't believe this can be done in a typical blog on the subject. software engineering thoughts are either tweet length or book length.
-
and then there is the problem of reference: most programming is done (at least partially) from example. the internet is now a minefield of harmful examples promoted in blog posts as if they are good ideas when in truth they are tech debt traps waiting for you to spring them.
-
a tweet is short enough to not have much capacity for harm. a book is long enough to explain the edge cases and offer guidance on adapting the pattern to your situation. a blog post is the perfect length to show the bad example without enough pitfall avoidance.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.