One might think that a structure language is really desirable, but in fact, one of the biggest methods of functioning behind intelligence is stupidity. Let me explain: if you only innovate by piecing together lego pieces you already have, you'll be locked into predictable patterns and will plateau at some point. In order to break out of this, we all know, there needs to be an element of randomness. This element needs to be capable of going in the at-the-moment-ostensibly wrong direction, so as to escape the plateau of mediocrity. In gradient descent this is accomplished by turning up temperature. There are however many other layers that do this. Fallible memory - misremembering facts - is one thing. Failing to recognize patterns is another. Linguistic ambiguity is yet another, and that is a really big one (cf Sapir–Whorf hypothesis). It's really important to retain those methods of stupidity in order to be able to achieve true intelligence. There can be no intelligence without stupidity.
I've met countless Juliuses over the years. I kept track of the companies, and the Juliuses. My biggest revelation is that every company that was being in some substantial capacity led by a Julius (either at C level, VP, or high up in management) ended up one of two ways:
1. Shut down or shutting down (e.g. team reduced by > 50% since I've been there)
2. Julius removed, endlessly seeking work, keeps getting fired, and can't find a place to call home
The meteoric rise of the Julius is an exception - sooner or later their lucky streak ends and they face the cliff of adversity, towering above them with no way to climb it - no skills to help him actually do it.
I think in this case "your own" means under your control, rather than a service or license you pay for. "your own" as in ownership of artefacts, not as in being the creator.
One thing I would really appreciate in this repository (and many like it) would be a simple, short, snippet of code that shows a typical use case of whatever the repo is selling me. Life's too short to dig around in the guts of the repository to find stuff like this out, it should be front and center. I want to know about the ergonomics and hackability of what I'm about to delve into.
I question the wisdom of this limitation in monthly recurring threads. I think it should be special-cased for those specific instances.