Phone numbers aren’t actually numbers
If one group is making guesses about another group’s datatypes, your project wasn’t ready for go-live. →
For multivalued Marketo fields, consider URL-encoding instead of JSON or semicolons
There’s no One Best Way™ to store complex data. To find the best fit, consider what — and who — will be doing the encoding and decoding. →
So You Think You Can Unicode, Quiz #2
> Update 2022-03-18: The prize goes to Shivam, who DM’d me the correct answer: 31 bytes. I’ll explain in the next post! Another encoding-related quiz, this time with →
Two DKIM records (for the same selector) will break stuff. Pretty much all the stuff.
Last night we heard from a user that 90%+ of their Marketo emails were flagged as spam. They’d only made a minor DNS change — or rather, what they thought →
So you think you know what a string’s “length” is now, big shot?
If Unicode has been starting to make sense, this’ll set you back a bit (sorry!). →
What does the “max length” of a form field actually count?
The “maxlength” of a ˂textarea˃ element is the maximum number of — well, *somethings* — the end user can enter. What that something is may surprise you. →
Use an established URL parser (I’ll say it again!)
It’s impossible to write a UTM parser without understanding how the wide world constructs (totally valid) URLs! The shorter the code, the more likely it misses tons of cases. So instead of some dude’s one- or two-liner, use a tested library. →
A common form translation mistake, and how to avoid it using DOM Range
You can’t get away with setting textContent and innerHTML all the time. Sometimes you‘ve gotta bring the big stick: DOM Range. →