|
You are a master at this.
I, for one, like Roman Numerals.
|
|
|
|
|
Clowns are silly
Clowns go to field trips on a bus
Therefore, Clowns go to field trips of a syllabus
Would that be a sylla-logism?
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Interviewer: How do you explain this 4 year gap on your resume?
Me:That's when I went to Yale.
Interviewer:That's impressive, you're hired.
Me:THanks, I really needed this Yob!
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Mike Hankey wrote: nterviewer: How do you explain this 8 year gap on your resume?
Me: I worked for the government. Do you want to know more about that time?
Interviewer: Uhm... no
Me: Good. I would have hated to strap you to a missile and shoot you into the stratosphere.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I hope this is a yoke! 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
Never argue with a fool. Onlookers may not be able to tell the difference.
Mark Twain
|
|
|
|
|
Eggsactly!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
You shell pay for that!
/ravi
|
|
|
|
|
White did I do now?
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
Fight between Ravi and OG!
Whats the ova/under on the outcome?
I, for one, like Roman Numerals.
|
|
|
|
|
You crack me up!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
One of them will crack under the pressure!
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Will it be over easy, or they will chicken out?
I, for one, like Roman Numerals.
|
|
|
|
|
Scrambled I'm thinking! 
They call me different but the truth is they're all the same!
JaxCoder.com
|
|
|
|
|
Bacon is what I'm thinking now...
Mmmmmmm Baaaaconnnnn! 
I, for one, like Roman Numerals.
|
|
|
|
|
This one made me genuinely laugh.  
|
|
|
|
|
you like that? can see the wheels turning [in a happy way].
begs the question: so how many years were you in for are missing on your CV? 
Message Signature
(Click to edit ->)
|
|
|
|
|
lopatir wrote: so how many years were you in for are missing on your CV?
Oh, I filled the gaps in nicely. No worries. Just takes a little more ink.
|
|
|
|
|
I just turned my message analysis on...
And in the see of 400 warning for library I am look at right now. I think I spotted 2 useful comment....
They really need to improved this feature... :/ (i.e. I can't spot the 0.5% useful comments most time)
like style | possible error | pattern recommendation
EditorConf seems all about style as far as I can see... 
EditorConfig settings - Visual Studio | Microsoft Docs
I certainly don't care about style consistency in my home project. Better yet, I like to change style over time! Ha! Take that stupid style enforcer!
[EDIT]
Found a solution.. instead of simply ignoring code analysis.. I create a ruleset, disable everything and the cherry pick a few promising looking rules...
what I really would like to know is, how easy to make new one?
I'd like to create a warning when people to await Task object (which throw no warning in non async method by default)...
Would caught some bug in our project... :/
[EDIT2]
I checked those 3 rules
- Avoid excessive inheritance
- Avoid excessive complexity
- Avoid unmaintainable code
Now I am curious to see where it will apply ^^
[EDIT3]
The fracking ruleset doesn't work! (in Visual Studio 2019 Community)
I told it to ignore rule 2208, restarted Visual Studio, it still warns me about it...
That's it, stuff it, I can't be bothered to use it anymore... there might be 0.5% useful warning, but they are just too hard to use...
modified 19-Nov-19 10:02am.
|
|
|
|
|
I never quite got this obscession with style anyway. The computer does not care about it at all, as long as the parser can make sense of what it has been fed. And I have also seen enough pigs with stylish lipstick, yet still most developers do their best to ignore the real problems and just make a big fuss to prevent the lipstick from getting smeared.
Sometimes I think this is some sort of modern supersticion. They invent arcane rituals with arcane rules which don't really help very much, but are fanatically persued anyway.
I have lived with several Zen masters - all of them were cats.
His last invention was an evil Lasagna. It didn't kill anyone, and it actually tasted pretty good.
|
|
|
|
|
I never understood it either...
I suspect (maybe smug intolerance at play) that it is due to the influence of a larger than expected number of average or below programmers... 
|
|
|
|
|
Definitely. To me, it also explains the explosion of languages for this and that which are supposed to "make it easier." Plus, there is this movement that says, "everyone can code." Unfortunately, we can not add the adverb "well" to the end of that sentence. It would be more like, "sort of."
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
|
|
|
|
|
Style is important because you're writing code for developers to read, not for computers.
When style is consistent, code will look familiar at first sight and it will save any other developer, or you next year, the trouble of first deciphering the syntax before actually trying to understand what it does.
When I see code that's not properly formatted or otherwise inconsistent I immediately assume the developer is lacking in skill and/or professionality and I'm usually right.
It's really easy to keep code consistent, especially with today's tools, and it saves a lot of effort when reading it so why not just do it?
|
|
|
|
|
the problem when people go into fight over style, not only it is an endless pointless waste of time, but also people have extremely simplistic style guideline. like the eternal recurring waste of time "always use brace after an if"
sorry, but I have like 5 bracing style depending on context and length of enclosing statement.... and your over simplification is as irking to me as I am to you....
But go ahead, restyle my code, I don't mind....
Further.. I found many case where this obsession over style and patterns over functionality was getting in the way of fixing bug and was in fat creating new ones...
In a way, I am NOT an Apple person.
modified 19-Nov-19 9:34am.
|
|
|
|
|
Pick a style, stick to it.
I don't really care that one person uses a bit more white space or has a funny way of naming variables (as long as it's clear) or uses var instead of the type name.
But there should be some sort of unity in a code base.
The basic ctrl + k, d together with things Visual Studio warns about (for example camelCase where PascalCase is expected and vice versa) should suffice.
|
|
|
|
|
Super Lloyd wrote: But go ahead, restyle my code, I don't mind....
This is what Ctrl-K Ctrl-D is for. It allows me to restyle your code for me to read easier.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
