|
He's not too bad, one the less hyper members of the team!
|
|
|
|
|
|
Well yes... but less Carbon Fibre & Steel
|
|
|
|
|
Doesn't that giant hole make it hard to maintain a vacuum?
|
|
|
|
|
|
|
It all sounds rather familiar.
Except the last bit*
* Except for my boss and a few in senior management, no one's fool enough to come near me to ask for anything without good cause. It's all a matter of training . . .
| Ravings en masse^ |
|---|
| "The difference between genius and stupidity is that genius has its limits." - Albert Einstein | | "If you are searching for perfection in others, then you seek disappointment. If you seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
glennPattonWork wrote: Got in at Silly O'Clock this am to get some tests done. Test were fully done by 09:30 Successfully.
See, you did that wrong. You should have spent the rest of the day relaxing and posted the successful tests at 4:53 PM. 
|
|
|
|
|
And the number one thing the Visual Code update gives us this month is;
Quote: New product icons
We've updated all of our product icons to be uniform in style, color, and size. We went through various iterations and the community was helpful in providing feedback through every step of the process.
Whew sure am glad they got that straightened out!
Technician
1. A person that fixes stuff you can't.
2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge.
JaxCoder.com
|
|
|
|
|
What a relief, or should I say "Comic Relief" 
|
|
|
|
|
Mike Hankey wrote: We've updated all of our product icons to be uniform in style, color, and size. We went through various iterations and the community was helpful in providing feedback through every step of the process.
...yet icons in VS these days remain as unusable as ever. IMNSHO, 2008, and maybe 2010 to some extent, were "peak VS" for me. Then everything went south when MS declared its war on color.
|
|
|
|
|
I agree they're uglier than hell.
Technician
1. A person that fixes stuff you can't.
2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge.
JaxCoder.com
|
|
|
|
|
They're all the same now?
|
|
|
|
|
For now?
Technician
1. A person that fixes stuff you can't.
2. One who does precision guesswork based on unreliable data provided by those of questionable knowledge.
JaxCoder.com
|
|
|
|
|
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.
|
|
|
|
|
great Scott!
Message Signature
(Click to edit ->)
|
|
|
|
|
Shirley it was Brian's fault.
|
|
|
|
|
Yes, Life of Brian is not the easiest
|
|
|
|
|
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(...); 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? 
|
|
|
|
|
If you are signed in via an account it should remember your settings.
But yes, it sucks. Not sure if it still does, but I think cancelling it really messed up the install.
|
|
|
|
|
But I didn't cancel it
It works again though, but even though I'm signed in it forgot all my preferences.
|
|
|
|
|
Mine hasn't needed a restart, but it did lose my style preferences and move all my curly brackets this morning. Which was annoying enough in it's own way.
I'm starting to really hate the VS settings dialog.
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Luckily, I use most defaults, so it wasn't very hard to get my configuration back 
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
