Remember; human function names and object names are for human consumption. We could write a whole lot less if not for all the programmers who need context. We

Remember; human function names and object names are for human consumption. We could write a whole lot less if not for all the programmers who need context. We know from our hardware platforms what we can and cannot compute; their spec defines the limits. We don’t need dozens of competing languages when our goal is “reserve memory, compute values in that memory in this order, free memory when done”. My startup is focusing on learning what code shapes are ok from the context of security and developing a filtering tool to avoid allowing merging commits that violate that spec. We have a lot of interest from DOD and SV companies, in the form of “pre-emptively avoid security issues via coders who write stupid code.” Eventually we’ll have tailor made hardware with little to no generally programmable surface area. Because our generation of computing is behind us. Kids now just want the thing to emit results. The thing that’s holding them back is maintenance of “career oriented job life”. Rather than build programs, software people babysit dependency lists and process. Google products are a mess because it’s about capturing worker and customer agency, not engineering novel things.