The broadest problem that I see in the software industry is that companies are unwilling to engage in strategies that only show results in the long term. Or, more specifically, that organizations…
Whenever you engage in some activity, it’s a good idea to have some idea of what the purpose of that activity is. What is the end goal, and why are you doing…
This title might seem a bit like a contradiction to my last post! Well, you really shouldn’t break your API, if you can help it. But sometimes, maintaining backwards compatibility for any…
An API is a sort of a promise–“You can always interact with our program this way, safely and exactly like we said.” When you release a new version of your product that…
Software developers throw around this word, “overengineering,” quite a bit. “That code was overengineered.” “This is an overengineered solution.” Strangely enough, though, it’s hard to find an actual definition for the word…
Sometimes, I think, people are worried that if they make their code too simple, then either: Somehow they’re not demonstrating how intelligent they are, or how valuable they are, to their managers,…
A fast way to get complicated is to violate the purpose of what you’re doing. For example, what’s the purpose of a web page? To give and receive information. Mostly to give…
There is only a certain amount of the future you can know. You can know with some certainty that you’ll be breathing in the next few minutes. You can know with some…