Pretty sure they’re referring to class names describing the visual style being applied, rather than what that class represents semantically.
E.g. .red-bold
vs. .error-text
Pretty sure they’re referring to class names describing the visual style being applied, rather than what that class represents semantically.
E.g. .red-bold
vs. .error-text
I’m in this no-experience-to-apprenticeship program and everyone in my class thinks type coercion is the greatest thing ever.
Ah, but you thought about it for more than a quarter of a second. That’s not allowed.
The elephant and rope parable rings its bell of sound morals!
Not so much the realizing what NaN means; that’s more relevant to that XKCD which I probably don’t need to describe here.
Marked as solution.
Const goo =
backspace backspace
const Foo
backspace
const foo = obj. Val;.
*deep breaths
How has the actual process of developing your idea been different from your initial expectations and assumptions?
Do you have previous experience with a creative hobby/skill/profession (even if it’s another sect of software development), and what challenges have you faced in the shifting of your creative paradigm? What’s different?
Yeah, it’s definitely convenient in most cases, I would say. Though it can also be inconvenient when messaging, because sometimes said need to add context can read very unnaturally in an otherwise grammatically correct sentence.
https://thedailywtf.com/articles/gotta-catch-em-all
Dear God.
try
{
/* ... some important code ... */
}
catch (OutOfMemoryException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (OverflowException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (InvalidCastException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (NullReferenceException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (IndexOutOfRangeException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (ArgumentException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (InvalidOperationException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (XmlException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (IOException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (NotSupportedException exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
catch (Exception exception)
{
Global.Insert("App.GetSettings;", exception.Message);
}
Ironically, autotune is more akin to pixelating an image.
They likely meant to say “adverbial phrase.”
Verbose HTTP is looking great.
I just want to point out that English’s future tense does exist, but it’s just non-distinct in many cases because, well, as you’ve said, English is fucked.
“We’re eating steak.”
You need context to determine whether this statement is talking about the present or the future. So much of the language is implied contextually that you can just drop off words and assume the listener will understand.
“What are we eating?” vs. “What are we eating tonight?”
It’s so funny because whereas a lot of other languages have rules with defined exceptions here and there, speaking English is more of a theoretical approach.
It feels like English just happened one day and we’re all trying to figure out why.
True Neutral
Could one argue that your conscious choice to not pick an RGB backlit keyboard is in part because of your aversion to it, therefore making it somewhat of an aesthe-
RGB == FPS bro
Someone’s not getting it.
Most people also don’t see a multitude of different moons on a day-to-day basis.
Floating points included for thoroughness!