I’m always looking for great horror. Terror not so much.
I peruse movie sites, book stores, graphic novels, what have you. I dig into the ‘Horror’ section, and am very often left empty-handed.
Why? Is there not enough content? Oh no, there’s plenty upon plenty. Horror is a very popular genre. It hangs tough with action and romance, no doubt about that. Content-wise, there is a plethora of work in the Horror genre.
Is the stuff not scary enough for me? Well, a lot of the time — especially in movies and TV — the “scary” is the usual ghost in the mirror, killer just behind you, creepy thing running past in the shadows deal. Yeah, it’s scary, I guess. I mean, I jump when I’m expected to jump. My heart does that fear clench. …
It’s funny how often tech debt gets ignored by business people. Not haha funny, but ironically so. It is ironic, because it is such a common problem in software companies that the business / sales / boss types don’t seem to care about tech debt. The responses I’ve heard run the gamut of “We need features, not perfect code,” to “We can fix that another time,” to “that’s a tech thing, not a business problem”, as if we engineers / devs were climate scientists / pandemic experts.
It is a constant source of frustration for devs and engineers that no one seems to listen to the fact that tech debt is creeping like a malaise over the code base. Why won’t your boss or business people listen when you tell them the code is covered in tech debt, that it’s getting unmanageable, that we have a big problem if we don’t deal with it? …
Here’s the situation. I need to build a test harness to verify that when my software sends / receives data to some other system (a system outside my control), the data is not only received, but is in fact the data I expected to have been sent.
Pretty standard test harness stuff, right? The testers say they need this for manual and for automation testing suites. Internal customer need. Great.
So the developer starts rattling off software tools / languages we will use to build this test harness.
How did we get from a high level need to implementation that fast? Where are our requirements? Where are our user stories? Where the heck are even some simple sequence / flow diagrams to describe whussup? …