w001y

Determining the necessity for a technical explanation could be thought of as another separate skill in itself :)

Being able to translate tech to non-tech people. People who have great ideas and financial backing are fresh meat to technical sales folk, and that is a big stress factor for those who want to genuinely build something cool but don't have the confidence to verbalise their technical requirements. Translating the jargon to make them feel at ease and in control of the next step goes further than you might think.

Wordpress is, imo, the reason PHP has historically gotten a bad rap. Needle/haystack/type/performance PHP jibes aside etc etc, WP has been the single point of contact for situations where my company has had to remediate a hack/data breach/script kiddie scrawl. I've seen full hosted servers being unplugged with no comebacks, tens of thousands of dollars in rebuild costs, lost clients due to security concerns.. the culprit? pointing over there

The easy retort is "just keep it patched and up to date", natch. The ongoing costs/technical debt involved in maintaining a Wordpress install sometimes ends up being greater than what it cost to roll the thing out.

Wow, I'm getting old and complainy.

This is nice.

Well done on mentioning non-parents; a subset of the workforce usually overlooked in these conversations.

I'm building a dashboard interface for a REST API I built allowing folks to work game mechanics into their apps or processes for really cheap - https://gamify.ws