The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
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, orderdates or 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 dates to var orders.
Then, an orderdate should have an orderlinenr, so I ask him if with orderlinenr he meant indexnr because I didn't have any other properties besides productnr and subproductnr.
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
His best programming buddy keeps variables in hidden text boxes on forms
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
Visual Studio just had an update for me... I know it's been there since yesterday.
So I install it, as I usually do with VS updates, and the installer starts.
Update installs and I need to restart my computer.
So I restart and I fire up VS again.
Only to be prompted by an error that the VS installer did not complete correctly and that I have to run it again to fix the issue.
Open up the installer, but it's up to date and there's nothing to report.
I'm now doing a repair with the installer, resetting all my preferences and losing even more time.
Hopefully this will indeed fix the issue, but what the hell Mickeysoft?
I don't know about 2019, but with VS2017, if you're trying to keep all installer files up to date (since MS no longer regularly publishes updated ISOs), it's already well over 20GB each time a new update is published.
(I'm not talking about letting VS get updates within itself, which just updates the components you have installed--rather, I'm talking about letting the installer update everything that's different from your setup folder)
Going back a little while I used to like V's thing. As CCC has returned as WSO CCC with the originator in Political based silence, what about WSO MQOTD ?? Opions please...
Maybe not WSO but there has not been an APOD for some time also.