Didn’t write yesterday because, as I said in my sign-off Friday, I was livid about a work situation.<\/p>\n\n\n\n
First, if you schedule a meeting for 1500 on a Friday afternoon, you’re an asshole. Second, my general attitude towards meetings was very much in play. You need to publish an attendee list, take then publish minutes. If you don’t do that, you’re wasting the time of all but about the five most-active participants.<\/p>\n\n\n\n
Unfortunately, I was one of those five most-active on something I hadn’t really been following all that closely.<\/p>\n\n\n\n
The solution isn’t that difficult, but you have to know what you’re doing, and why you’re doing it. <\/p>\n\n\n\n
Lots of thoughts this week about how there’s so little appreciation of things that don’t last.<\/p>\n\n\n\n
Figure out what’s the problem you, and your team, are trying to solve. Solve the problem. Leave. None of the particulars about how you fixed the problem are important.<\/p>\n\n\n\n
And they shouldn’t persist.<\/p>\n\n\n\n
Though I was never even an adequate programmer, I’d understand that you don’t import libraries that you’re not going to use, then leave them around forever.<\/p>\n\n\n\n
Oh, look! There’s a smaller library that’ll allow you to do what you were trying to do more efficiently. Nawp. Can’t use that. We use this<\/em> library<\/strong>. There’s no other way to do it. Further, still, we don’t have the slightest clue about what we’re actually trying to do. Nope. We use this tool.<\/p>\n\n\n\n *headdesk*<\/p>\n\n\n\n Imagine refusing to use a toilet if the toilet wasn’t the manufacturer you prefer. Or if the toilet paper was different.<\/p>\n\n\n\n But that’s where things are so often in big IT.<\/p>\n\n\n\n We have to buy this expensive stuff. There is no alternative. Here’s an old document that says you have to use the expensive stuff.<\/p>\n\n\n\n To. Do. What?<\/p>\n\n\n\n
\n\n\n\n