Code Anatomy: Not bad meaning *could be better*, but bad meaning *bad*
Like obscenity [https://en.wikipedia.org/wiki/I_know_it_when_I_see_it], or good-smelly cheese, or how that one network sitcom I swear, totally subverts the genre, bad →
Code Anatomy: Grouping array items into subarrays of a certain size
Something I need surprisingly often when doing front-end templating is the ability to take a one-dimensional list of data, like a product list, and output it in multiple dimensions. Check →
Customizing the robots.txt for Marketo LPs
If you want to tweak your robots.txt [http://www.robotstxt.org/robotstxt.html] for protection against unwanted search engine indexing, the widely-circulated answer [https://nation.marketo.com/thread/41091-how-to-stop-pdf-files-hosted-in-marketo-being-indexed] →
Why customer “branding domains” *were* affected by the Marketo DNS outage
Not that anybody asked me about this yet! But I felt like explaining why branding (i.e. click tracking) domains were indeed affected by Tuesday's outage. Originally, the →
Keeping Thank You pages on the same CNAME as Marketo LPs
This was a nice catch by user AD on the Community [https://nation.marketo.com/thread/41040-lp-cname-upon-form-submission] and something I somehow missed before! It has significant effects on tracking and →
We coulda seen it coming...
Today's epically embarrassing (until we forget about it next week!) Marketo outage was unfortunately predictable — if you were tuned in to a certain underrated, overlong DNS outage in →
Dealing with unencoded URLs in query params (an Agical special feature)
A PHP-related post! Weird way to get back to blogging after a couple months, yep. I don't roll much with PHP these days, but… disclosure… Agical.io* is →
Code Anatomy: Turning Google Sheets API results into (better) objects, Part I
Many APIs return data structures that are pretty wacky, at least relative to how you want to process the data in your app. The property names and values are all →