|
AI might be a cheaper option.
Imagine Brexit (simplified) being discussed by an AI 
AI: EXIT NOW (What is my score for this answer?)
AI: REMAIN (What is my score for this answer?)
On questioning whether to remain or not, AI will simply state the answer with the highest score.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
"Hey man, how's the new job?"
"It's alright, drug dealers occasionally hang out with me."
|
|
|
|
|
Where can I apply? I executed a lot over the command line 
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.
|
|
|
|
|
I'm also putting in my experience with databases.
Familiarity with using a TRUNCATE TABLE should be useful.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
I must get real … I thought it was a joke …
|
|
|
|
|
https://www.youtube.com/watch?v=dU1xS07N-FA
I think it's something that has code and it's able to decode a mystery !!!
Ya especially others code...
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
None of them say "I wanna be a muppet"!
Given the percentage of muppets in society, this displays blatant anti-diversity and muppetism!
Tear it down! Burn the witch!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
34. Stone operating with axes (4)
|
|
|
|
|
34) ONYX - a stone: operating (ON) with axes(X,Y)
Good one! 
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!
|
|
|
|
|
|
I see @sanderrossel hasn't added a Sound of the Week (too much studying for that test?). For anyone who wants to warp their mind, here's an old classic that came up recently. Or for something not so warping that I'd never heard before, some new-ish Pop music. Have a great weekend!
|
|
|
|
|
|
|
Mark_Wallace wrote: Seriously?
Chill, Dude! Do the Salmon Dance!
|
|
|
|
|
fb and twitter fads ain't trippy; they're lowest-common-denominator marketing, which too many people fall for.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
 Hope your weekend goes better than your present, even if it needs chemicals to do so. Have a beer or something! That's a chemical or so! ![Beer | [beer]](https://www.codeproject.com/script/Forums/Images/beer.gif)
|
|
|
|
|
Hey, I never touch "chemicals" -- but don't denigrate beer!
The only two liquids worth bothering with are beer and Tabasco sauce!
(But not simultaneously, obviously)
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
|
|
Hello,
I was curious if anyone has had experience using the MSIX packaging tool. Will this be a true successor to MSI Installs?
|
|
|
|
|
Sorry, but ms told me that it "provides a modern packaging experience", so I ran a mile.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
what happen to wiX?
Caveat Emptor.
"Progress doesn't come from early risers – progress is made by lazy men looking for easier ways to do things." Lazarus Long
|
|
|
|
|
I've never been convinced MSIX was necessary.
The "X" in MSIX seems out of place to me. It should be used to cross out the whole thing.
|
|
|
|
|
I have just had a heated argument cage fight lively discussion with some of my team members about ReSharper's suggestion of refactoring code to replace nested ifs with a series of multiple early return statements. This caused horribly messy code that ReSharper actually described in it's help as "more readable"!
Using a version of their example code (which is a lot simpler than the actual code in question):
void SomeFunction(SomeThing s)
{
if (s != null)
{
if (s.Thing != null)
{
.
.
.
}
}
}becomes:
void SomeFunction(SomeThing s)
{
if (s == null) return
if (s.Thing == null) return;
.
.
.
}This makes a complete hash of the natural flow of the code and introduces an execution statement (return) on the same line as the "if" which is bad coding practice, and then does it again, and then drops though to do some actual processing.
If I was to refactor the code it would do this:
void SomeFunction(SomeThing s)
{
if (s != null && s.Thing != null)
{
.
.
.
}
}or possibly:
void SomeFunction(SomeThing s)
{
if (s?.Thing != null)
{
.
.
.
}
}Which is a lot cleaner!
...and this isn't even considering a method that returns a value of some sort.
Opinions?
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
I agree.
I will use multiple returns when doing otherwise would be less readable or less efficient, but otherwise I prefer one return.
And I don't listen to anyone who says that a throw or a yield is the same as a return.
modified 15-Feb-19 17:57pm.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
