![]() Have a post-build step, perhaps something with a regular expression like s*?$ in it, that auto-cleans extra spaces checked into source control. ![]() I have a full-body itchiness just talking about it.ĭepending on how far down the rabbit-hole you want to go, there's any number of things you could do here: Well, those are the nightmares OCD horror movies are made of. Now to imagine, to our dismay, that there's all this stupid, useless whitespace at the ends of our lines. We got into this industry because, quite frankly, we are control freaks. If one semicolon is out of place, everything goes sideways. Not because we want to, you understand, but because the world explodes when we don't. You don't appreciate what it's like to spend every freaking minute of every freaking day agonizing over the tiniest details of the programs you write. But I humbly submit that, well, you're not one of us. If you're not a programmer, you may be looking at these two images and wondering what the big deal is. Take this perfectly innocent code, for example. These are the questions that drive young programmers to madness. ![]() But did you know that even the code you can't see may be wrong, too? ![]() Ever have one of those days where everything you check into source control is wrong?Īlso, how exactly is that day is different from any other? But seriously.Ĭode that is visible is code that can be wrong. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |