The importance of naming
-
We have a system, let us call it Brian. Brian has a Windows service that communicates between two other systems, let us call them Emma and Jim. This service that is part of Brian has been called EmmaJim. EmmaJim fell over today, an incident was raised, the problem was resolved. I am responsible for Jim, Jim is my baby, I suddenly realised when I saw the incident report, the genius that the name EmmaJim was for the developers of Brian, and mentioned this to them. All anyone knew at this point was that data was not getting to Emma, and when they get told that EmmaJim had caused a problem they would assume it was either Emma or Jim that was an issue and ignore Brian completely. Sure enough, a resolution notice went around minutes later "An issue was identified with a service within Jim".
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
-
We have a system, let us call it Brian. Brian has a Windows service that communicates between two other systems, let us call them Emma and Jim. This service that is part of Brian has been called EmmaJim. EmmaJim fell over today, an incident was raised, the problem was resolved. I am responsible for Jim, Jim is my baby, I suddenly realised when I saw the incident report, the genius that the name EmmaJim was for the developers of Brian, and mentioned this to them. All anyone knew at this point was that data was not getting to Emma, and when they get told that EmmaJim had caused a problem they would assume it was either Emma or Jim that was an issue and ignore Brian completely. Sure enough, a resolution notice went around minutes later "An issue was identified with a service within Jim".
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
-
We have a system, let us call it Brian. Brian has a Windows service that communicates between two other systems, let us call them Emma and Jim. This service that is part of Brian has been called EmmaJim. EmmaJim fell over today, an incident was raised, the problem was resolved. I am responsible for Jim, Jim is my baby, I suddenly realised when I saw the incident report, the genius that the name EmmaJim was for the developers of Brian, and mentioned this to them. All anyone knew at this point was that data was not getting to Emma, and when they get told that EmmaJim had caused a problem they would assume it was either Emma or Jim that was an issue and ignore Brian completely. Sure enough, a resolution notice went around minutes later "An issue was identified with a service within Jim".
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
Yes, Life of Brian is not the easiest :-\
-
We have a system, let us call it Brian. Brian has a Windows service that communicates between two other systems, let us call them Emma and Jim. This service that is part of Brian has been called EmmaJim. EmmaJim fell over today, an incident was raised, the problem was resolved. I am responsible for Jim, Jim is my baby, I suddenly realised when I saw the incident report, the genius that the name EmmaJim was for the developers of Brian, and mentioned this to them. All anyone knew at this point was that data was not getting to Emma, and when they get told that EmmaJim had caused a problem they would assume it was either Emma or Jim that was an issue and ignore Brian completely. Sure enough, a resolution notice went around minutes later "An issue was identified with a service within Jim".
Some men are born mediocre, some men achieve mediocrity, and some men have mediocrity thrust upon them.
Naming is everything! I recently helped someone with a piece of code. He just created a database table that day,
orderdatesor something like that, and needed to fill it with product ids. So my code goes like:var dates = context.orderdates.Where(...); // Actually it was VB, but I will spare you all and make a rough translation.
He goes "well, actually they're not dates, but orders..." Alright, unexpected, but I change
var datestovar orders. Then, anorderdateshould have anorderlinenr, so I ask him if withorderlinenrhe meantindexnrbecause I didn't have any other properties besidesproductnrandsubproductnr. He "thought" they were, but he wasn't completely sure. He created that table just that afternoon, but his own naming confused even him after only a few hours :doh: His best programming buddy keeps variables in hidden text boxes on forms X| The scary part is that this guy has always delivered working software (but woe the poor sod who has to update or maintain it) within budget, where others ("professional" companies) have failed to deliver completely even when going far above budget :wtf:Best, Sander sanderrossel.com Continuous Integration, Delivery, and Deployment arrgh.js - Bringing LINQ to JavaScript Object-Oriented Programming in C# Succinctly
