|
This should be given careful consideration by every developer, because of how much microsoft's standards have soared, over the last 13 years.
Oops! Typo, sorry.
I meant "soured".
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Masterful! Stupendous! I laughed, I cried!
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: I laughed, I cried!
Well, we've all laughed at "Year of the Linux Desktop" jokes, and cried because microsoft's making it happen.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
On the other hand, you have to consider all the technologies MS walked away from leaving developers high and dry: COM/OLE, VB6, XAML, Windows Mobile, UWP, ...
|
|
|
|
|
gstolarov wrote: On the other hand, you have to consider all the technologies MS walked away from leaving developers high and dry: COM/OLE, VB6, XAML, Windows Mobile, UWP, ...
They're very good about it, though.
They give everyone long enough to get so far into it that almost everything they do revolves around it, before they kill something off.
At least google kills stuff before you've even heard of it.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The moon you know and love might not be alone. There’s a possibility a new miniature version is orbiting Earth now as well. That's no... oh, wait. Yes, it is. (for a while)
|
|
|
|
|
The astronauts being sent up have been told to trust The Force
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
His code, ↑ ↑ ↓ ↓ ← → ← → B, A, Start, has lived on for over three decades and continues to be a comical Easter egg in many games today. I shall wrap my controller in black ribbon while I mash buttons
|
|
|
|
|
Kent Sharkey wrote: His code, ↑ ↑ ↓ ↓ ← → ← → B, A, Start
Double bubble permanent buff?
R.I.P. ![Rose | [Rose]](https://codeproject.global.ssl.fastly.net/script/Forums/Images/rose.gif)
M.D.V. 
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
I hear he had quite an eventful life.
Please tell me that I don't have to actually type the punchline to that.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Just don't try it on your CodeProject profile page. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: Just don't try it on your CodeProject profile page.
Must... Resist...
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I have a SQUILLION CP points! Gonna trade them in for cash and retire! W00t! 
TTFN - Kent
|
|
|
|
|
Kent Sharkey wrote: I have a SQUILLION CP points! Gonna trade them in for cash and retire! W00t!
mmm... not buying that.
OG is still here, if there were prizes, he would have already retired  
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Intel's security plans sound a lot like "we're going to catch up to AMD." The bad news: it's only Caesar Cipher
Or maybe it just converts everything into Pig Latin for storage?
I wonder how long it will take before someone finds a hole in this one?
|
|
|
|
|
Kent Sharkey wrote: I wonder how long it will take before someone finds a hole in this one?
I fear that it will be not that long.
Real good and secure code needs time, time is money, and todays companies (or better said the people running them) don't want to invest 1 coin (no matter which currency) more than what is absolutely needed, so they can fill their pockets even more (although some of them already have more money than some countries).
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
You've just described the state of play in the US.
It's not quite as bad in Europe, and it's completely different in India and China.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Software developers need testers to be their shield in the fight against software defects. QA professionals want programmers to know how to strengthen this alliance. At least the ones that can be put into print
I'm sure there are a few "bluer" items out there
|
|
|
|
|
Kent Sharkey wrote: QA professionals want programmers to know how to strengthen this alliance.
Communication is a two directions process. If one of them is broken, it brings nothing.
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
Oh, for God's sake!
If you want devs to help you out, don't, for crying out loud, try to use logical arguments or facts -- most devs subscribe to one or more "alternative logics" based on "different facts", so it's a lost battle before it begins.
Just tell them that you need them to be your Mighty, Shining Guardian, equipped with their Mithril Sword of (insert programming language name here), and Legendary Shield of Infinite Knowledge.
They'll be eating out of your hand.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
By contrast there's only two things I wished testers knew.
1) if you find a bug raise a ticket for it, don't come and interrupt me every time you find a bug to tell me....you are not going to get a cookie
2) If you can't give me reproduction steps, don't raise a ticket.
|
|
|
|
|
And if you still come to me, ignoring #1 and #2...
3) Explain it without ambiguities in a way I can understand it.
4) Don't flip out if I start asking questions to delimitate the scope and to be sure I have understand understood you correctly.
EDIT: 
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified 27-Feb-20 13:13pm.
|
|
|
|
|
F-ES Sitecore wrote: 2) If you can't give me reproduction steps, don't raise a ticket.
So you say: Completely ignore heisenbugs, POM-errors, race conditions ... all sorts of intermittent errors. You don't want to hear about them. You don't want to log them. You don't want to spend any time on trying to see if you can reproduce them (e.g. by overloading the system to create more resource conflicts). Those problems are not real. You do not want to even consider them.
If a test fails one of a thousand runs, you say: Forget it! If one of a hundred runs fails: Forget it! If one of ten runs fails: Forget it! You can't reliably reproduce it, so forget it! Where do you draw the line? What if every second run, on the average but not consistently, fails?
So I do not agree with your second point. I'd rather say: "If you can't give me reproduction steps, don't take for granted that I will have it fixed, neither tomorrow, in a week or in a year. But please: If it happens again, report it again, with as many details as possible, and we will try to see if there is some recurring patteren in all the reports of this problem".
|
|
|
|
|
Member 7989122 wrote: So you say: Completely ignore heisenbugs, POM-errors, race conditions ... all sorts of intermittent errors. You don't want to hear about them. You don't want to log them. You don't want to spend any time on trying to see if you can reproduce them
Did I stutter? 
Obviously I was talking about bugs that are easily reproducible, like "certain email addresses fail validation" - which addresses? "I loaded an image and it broke the layout" - which image? I entered an invalid age and it didn't work - which age? "I clicked on a link and got a 404" - which link?
Seriously, the garbage you get on tickets from testers. I find almost all testers have zero knowledge of their own job. Which is understandable as no-one gets a degree in testing, no-one goes on a testing course, no programmer wants to make the switch to tester, so you usually just get a bunch of chancers.
IMHE.
|
|
|
|
|
I'd like to add another point which is slightly on the side - the problem is not with the testers, but with advanced users:
3) Please don't make workarounds for a bug/problem without informing me! Let me know of all bugs!
I guess this is mostly a problem with technically advanced users, in particular in my situation, when I was developing some tools for strictly in-house use. Several times I discovered bugs that should have caused problems for the projects using that functionality, but I hadn't heard a word about it. So I visit that project team, to learn why the bug didn't manifiest itself with them. Oh, sure, that bug had always been there, but if we do this and that little trick, we can work around the bug! But you haven't reported it to me! Shrugs. Why should we? This workaround was good enough for us...
In one case, a project group had had a workaround for two years, until another project started using the same functionality, but unaware of the workaround. In such cases, I must fight to keep a polite, friendly image, hiding my anger (towards the first project group, not the second). We are working in the same company, in the same building, on the same floor. Yet you think it is too much "bother" to raise a ticket, or drop me an email, or mention it in passing in the coffee corner? Is that how we keep up the quality of our tools? Is that how we relate to other projects - keeping secret that something doesn't work as it should, letting the other group fight with the bugs?
Bug handling is not an arena for glossing over and excessive politeness. I would much rather that someone comes to scream in my face than that they let my bug live on in the code. Screaming is less insulting than secretly saying: "We will preserve his faults and mistakes, we'll let them prevail!" I see that as a sort of mild form of slandering. Please don't be "kind" to me - tell me what is wrong, so that I get a chance to correct it!
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
