One thing software developers do very well is name things. Typically, after an engineer gets done developing a piece of software or a concept, they look around for a name. Quite literally, they look around at objects that are sitting near them and adopt that as the name for their new widget. If you’ve been developing anything recently, you will see many funny names. For example, I had no clue this actually existed, but I searched for “bananajs” and guess what!? Github hosts a project called BananaJS. You get my point? We know that there are many funny names for libraries, but I’ve always been intrigued by that text file the browser uses to store data about your session, the Browser Cookie! How did browser cookies get their name?
Since the dawn of the computers, us software developers have been in pursuit of the holy grail of computer programming. We have long sought after the achievement of writing code in a way that is elegant and beautiful in design. Code that inspires tears from our peers who can appreciate the beauty of how you painstakingly woven together such a beautiful piece of art. In fact, at the beginning of each new software development project, as any developer will tell you, it is another opportunity not to screw up the code for this one. We all start off with a statement like “this time…this code will be the most elegant code ever written!” Going into each project with this state of mind, we are often let down by how awful our code turns out as we are thrown challenges like time/budget constraints and missed features. Often, we create tech depts and @todos to go back and fix our shortcomings in code. But never return as there is no time or money to do so.