1,154 reputation
317
bio website echl.in
location New York, United States
age
visits member for 2 years, 4 months
seen 22 mins ago

Ask the right question.


11h
comment The Definition of “Strong Type Systems”
@MichaelT I'm torn between upvoting the OP, because per Lippert's comment this dichotomy is completely ridiculous, but upvoting you, because, as nonsensical as the Wiki article is, the OP should be able to say that. e.g. "it just lists a bunch of different characteristics but doesn't say which ones make a language strong/weak typed".
11h
comment The Definition of “Strong Type Systems”
+1, beat me to it. Surprised that the founder of Scala is so loose with this.
12h
comment Beginning a sentence with a function name?
@KyleStrand it'd be nice to know why you should never never start a sentence with a symbol. "$\pi$ is..." v. "The mathematical constant $\pi$ is..." - you choose.
14h
comment How clean should new code be?
So does anything under 20 lines.
14h
comment How would you know if you've written readable and easily maintainable code?
@MichaelDurrant it still kind of is, since you can learn what unclear things you were doing six months ago, and not do those things today.
14h
comment Beginning a sentence with a function name?
I'm not sure I agree with the analogy. Symbols like $x$ are transient to an equation so it's weird to refer to them as though they have a global meaning. If a symbol like $\pi$ starts a sentence, I would feel comfortable as a reader.
Aug
23
comment Avoid Code Repetition in Condition Statements
@Ethosik That's a pretty obsolete opinion IMO. Exiting early is always more readable than { { { { } } } }-style pyramids like in your question. Seriously the logic is impossible to follow when it gets that deep and your eyes certainly cannot follow it top to bottom like reading a page.
Aug
12
revised What is your approach to debugging a transient problem
added 188 characters in body
Aug
12
answered What is your approach to debugging a transient problem
Jul
31
awarded  Nice Answer
Jul
28
comment Generally speaking, is it better to make all the functional parts or get UI working first - or a mix of the two?
This answer is still wr*ng. You seriously think there's a bigger risk of a perfect UI that looks too good, over a UI that invites a zillion feature requests small and large that reveal the original spec was all wr*ng?
Jul
28
comment Generally speaking, is it better to make all the functional parts or get UI working first - or a mix of the two?
UI couples to and informs feature development. Therefore UI is highest risk and changes the requirements as it develops. This is true for technical risk in the backend ("whoops there's no algorithm to do this fast enough for what the user requires") but in practice far far less.
Jul
25
comment Why would programmers ignore ISO standards?
@Aaronaught actually a more accurate reading is "supposing you would want this decoupling for whatever reason..." which is why it's wrong to quote the original answer this way.
Jul
25
comment Why would programmers ignore ISO standards?
@Aaronaught you mean like in the original answer that that quote was sampled from?
Jul
25
comment Why would programmers ignore ISO standards?
Right, decoupling is good. Downvote stands for the thick layer of caricature added on a reasonable opinion.
Jul
25
comment Why would programmers ignore ISO standards?
I can't see "similar question," only displays to OP if only one (or <= 4) duplicate vote.
Jul
25
comment Why would programmers ignore ISO standards?
Questions linked where?
Jul
25
comment Why would programmers ignore ISO standards?
-1 for assuming won't interface with other applications. This is contrary to the entire programming industry.
Jul
25
comment Why would programmers ignore ISO standards?
-1 for your caricature of experienced, anti-ISO programmers.
Jul
25
comment Why would programmers ignore ISO standards?
Wait, why 20140201 and not 1391212800? Aw darn, which is standard.