Code does not wear company colours

After a few projects and some nasty burns, eventually, any engineer understands that the code doesn’t care. It will compile, or it will be interpreted, it will run, and it will fail or succeed, but in the end, it will not care.

If you’ve been out and about in the community, you’ll probably read or listen something along the lines:

“It is not X programming language job to stop you from shooting your foot. If you so choose to do so, then it is X programming language job to deliver Mr Bullet to Mr Foot in the most efficient way it knows.”¹

Code will do what is programmed to do, but it really doesn’t care.

So, when your sprinkle your company name, that you value so much, on variables, classes, components, agents and even on your bare metal machines (Use the Cloud Luke), code still doesn’t care. It will not read clearer, run faster nor debug quicker even if you try to dress it with your company colours.

And up to this point, you think that I’m right but not adding much. You do know that code doesn’t care and singularity is far ahead. So why should you bother with names…and why this rambling?

Well, I’ll end it with a word: Rebranding.

Drop’s the mic and leaves the building.

---