The broadest problem that I see in the software industry is that companies are unwilling to engage in strategies that only show
MoreWhenever you engage in some activity, it’s a good idea to have some idea of what the purpose of that activity is.
MoreThis title might seem a bit like a contradiction to my last post! Well, you really shouldn’t break your API, if you
MoreAn API is a sort of a promise–“You can always interact with our program this way, safely and exactly like we said.”
MoreSoftware developers throw around this word, “overengineering,” quite a bit. “That code was overengineered.” “This is an overengineered solution.” Strangely enough, though,
MoreSometimes, I think, people are worried that if they make their code too simple, then either: Somehow they’re not demonstrating how intelligent
MoreA fast way to get complicated is to violate the purpose of what you’re doing. For example, what’s the purpose of a
MoreThere is only a certain amount of the future you can know. You can know with some certainty that you’ll be breathing
More