Cloudflare Dev Workshop 2020
In mid-February, I had the privilege to attend the first Melbourne Cloudflare dev event. This was just one of a series of sessions they ran across the country to reach out to developers and help educate people around their thinking and the...
Out at Shine's various client sites, our teams often meet to discuss the pros and cons of various technical solutions. And in the past, there was one particular Shine manager who, if he was in attendance, would regularly pipe up and ask the question: what's the problem we're actually trying to solve?
When I started out as a developer the internet was made of wood and owl feathers, held together with spit, pluck, gumption and whatever else it is that you kids today no longer seem to have (job security? the possibility of owning your own home? a habitable climate?). We had to chisel our code out of the rocks 26 hours a day, 10 days a week, wait two years for it to compile, and the only way of knowing if it worked was if the old wise woman of the company divined the error messages in the entrails of a junior developer. I am now that wise old woman, and so I must pass on the things I have learned.
From time to time, developers will come to my desk seeking advice. There's a problem they're trying to solve, they've got a couple of possible solutions, but they're not sure which one to choose. I have a standard approach for dealing with this.
Adobe Experience Manager is designed to cater for content authoring of multiple sites by multiple content authors. Naturally, this process needs to be governed by strict Access Control Lists (ACLs) to manage who is allowed to do what at any given time. In this post, I’ll cover various approaches that can be used to manage authorizables and ACLs in AEM that should help you make a more informed decision when picking a permissions management strategy for your next project.
In 2010, Patrick McKenzie wrote the now-famous blog “Falsehoods Programmers Believe About Names”, in which he listed 40 things that were not universally true about names.
Did programmers sit up, take notice and change their attitudes to names? Sadly, not really. We still get asked to fill our names out in online forms which assume we have a first name and a last name (in that order) and which refuse to allow us to continue unless we have filled out both. They assume our names can be entered in alphabetic characters, often only ASCII.
I fear that part of the reason that this blog post had less impact than I hoped was that Patrick did not give examples of how each assumption can be false. But having worked in a previous life on IBM's Global Name Management product, I can assure you that it's all true.
Still not convinced? In this post I'm going to list all 40 of Patrick's original falsehoods, but give you an example (or two) drawn from my experiences working in this space. Ready? Let's go!