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
-
Show this thread
-
(brought to you by somebody in the engineering department meeting linking to a blog post on the topic of "technical debt contagion" and me being disgusted by the idea of needing a whole blog post for it)
1 reply 0 retweets 10 likesShow this thread -
-
Replying to @danlistensto @chaosprime
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.
1 reply 0 retweets 3 likes -
Replying to @danlistensto @chaosprime
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.
1 reply 0 retweets 1 like
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.
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.