What I think when I see "foo == false"?
Guy doesn't get booleans. Guy needs to stay away from my upstream code.
What I think when I see "foo == false"?
Guy doesn't get booleans. Guy needs to stay away from my upstream code.
@realmerlyn said:
I've been fighting this battle for years now... people writing "validation" regex for "email" addresses who haven't seen RFC[2]822, and ignoring the standard ways of doing this. Of course, we have other people who copy those people, so it's really becoming this bad virus of what "email" addresses are. Most of the time, these regex would reject my test address <fred&barney@stonehenge.com>, which has been in place for about a dozen years now. (Go ahead, try it... it's an autoresponder.) There is no inherent insecurity in accepting '822. It just means you coded bad somewhere else. Never let an email address near an unescaped SQL parameter or shell command line! It's not hard, people!
Oh, for grins, google for: site:regexlib.com "wrong wrong wrong"
You'll see all the times I've been fighting this in a place intending to exchange regular expressions for things.
@morbiuswilters said:
You're looking at this the wrong way: this is an agile, scalable, NoSQL data store. This guy invented NoSQL before NoSQL was cool.
More like NoNoSQL.
@Viverae said:
Viverae
A leading health management company designed to impact the health of our clients’ population by managing chronic conditions, compliance and lifestyle behavior to reduce the overall cost of health care. We strive to make health management accessible for clients and members through personalized programs that create awareness. Learn more about our Executive Leadership Team.
Viverae Mission Statement:
Viverae partners with companies to impact the health of their population by managing chronic conditions, compliance and life-style behavior to reduce the overall cost of health care.
Viverae Vision Statement:
To make health management accessible for clients and members through personalized programs that create awareness, drive engagement and empower change.
Is the next paragraph "Learn more about our Executive Team"?
I'm upgrading to a new release of some software. I have an existing account on their site with a username and a strong password that has some punctuation in it.
As I'm "registering" the new upgraded software, it asks for my username and password. I enter the proper username and password, and it rejects the password with "your password cannot have punctuation in it". Oh, ok, so I remove the punctuation, and try again. "Your password doesn't match the password we have on record". No s**t, sherlock.
Good thing there's a "register later" button so I can finish the installation.
@FrostCat said:
@random said:Yep, instead of specifing the radix , they decided to remove leading zeros from the input using a regex.
Sounds like the PHP way!
This is why sales tax is just nonsensical in general. Any tax that taxes the provision of goods or services that does not take into consideration the cost to prepare or acquire the good or service is just wrong. Otherwise, it ends up being a "tax-on-tax-on-tax" once something has been aggregated a few times, and hurts some industries far more than others. I'm very happy to live in a sales-tax-free state, and I hope it stays that way.
Friends don't let friends use MySQL. It's almost a shuttered project at Oracle now... all the good devs went with Monty to his new team for MariaDB.
If you must maintain compatibility with legacy MySQL, use MariaDb.
If you want a better more free (BSD-licensed) database, hop over the PostgreSQL.
Sadly, in a workshop, I saw Guido van Rossum doing precisely this... testing the class of an object, then calling a distinct method based on that. This completely made me turn away from Python. How could I trust Python to do the right thing, when the creator of Python DOES NOT UNDERSTAND OO PROGRAMMING.
This is probably using DateTime underneath. Apparently, $datetime_object->add('1 day') doesn't just return the next day, it modifies the object. You have to say $datetime_object->clone->add('1 day') instead. Ugh.
@GNU Pepper said:
What's surprising about Coffeescript is the sheer number of developers who are willing to be so public about their refusal to just use Javascript correctly. Yes, JS is an awkward language, but retreating into a fucking transpiler smacks of the kind of weak-willed learning aversion that is the hallmark of the mediocre developer. "I give up, just make it look like Ruby", it seems to say.
Actually, Dart makes large projects in javascript finally sane. And it'll probably run native in an upcoming Chrome release, but fall back to trans-compiled javascript in all the other browsers.