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.
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
“Code -30% faster with GitHub Copilot”
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);
}
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
try {
Car.auto()
} catch (willCrashException) {
sleep(Number.MAX_VALUE)
}
In a few words, I’m reiterating the point that a professional software developer =/= professional cyber security expert. Yes, I know that I should, for example, implement auth; but I’m not writing the auth process. I’m just gonna use a library.
No one’s saying to ignore it.
If I own and run a sandwich shop, I don’t need to be on the farm picking and processing the wheat to make the flour that goes into my bread. I could do that, but then I’d be a farmer, a miller, and a sandwich maker. All I need to know is that I have good quality flour or bread so that I can make damn good sandwiches.
Maybe I misunderstood your comment. I’m talking from the layman’s perspective looking for a stable build of whatever the software is.
"
Anything outside of code repository stuff is outside their lane
" sounds like you’re talking about non-technical users when that was the context of the original comment. I understand what you mean now though, and I somewhat agree.
Gatekeeping OSS is a thing now?
It’s a cool experiment, but:
Over time, the negative feedback from these misfires has trained me to type more slowly and thoughtfully, burdening my mind with uncertainty that impedes my natural typing rhythm and unconscious flow of thoughts onto the computer screen.
I get using the modifiers as a potential accessibility solution. But if you’re otherwise able to type on the keyboard just fine, this is easily counterproductive.
In my opinion, any button in terms of graphical UI design simply dispatches an action with no arguments regarding state. There doesn’t exist a dichotomy between a “toggle” mechanic and a “standard” button as far as the button itself is concerned.
Whether or not you want to update the visual representation of that button is a separate concern.
Floating points included for thoroughness!