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…
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…
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
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…
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…
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