I think I was being too specific when I mentioned a computer science degree. What I wanted to convey is that these types of entry level, or “layperson” ways of specifying behaviour can seem threatening to those who have invested in a career in software development. Understanding pointers and memory management and compilation is often orthogonal to solving the problem at hand, unless the solution would benefit from such understanding (maybe due to performance or memory constraints, or a level of complexity that warrants it). This is, after all, why the industry has developed higher level ways of writing software, like scripting languages or higher level compiled languages. These tools let us trade off low level control for higher productivity. I think another axis of abstraction is in the UI of software development itself: trading away some of the ability to build arbitrarily complex systems in any domain in order to lower the barrier to entry.