It was Microsoft’s strategy for several decades (outsiders called it embrace, extend, extinguish, only partially in jest). It can work for some companies.
The fast bytecode is reduced to a simple operation that excludes certain knowns. For example if you have an instruction that stores A0 = A1 + 0, then knowing the immediate is zero, this can be reduced from reading a complex bit pattern to a bytecode that moves from one register to another, basically MV dst=A0, src=A1.
Get people to write the docs first. Not many people like writing docs after the fact, and much of the value of working documentation is lost if you do it after the implementation.
Assuming we’re not taking about user guide kind of docs, then a major benefit of writing docs first is to clarify your thinking. Being able to explain your intent in the written word is valuable because you will often uncover gaps in your thinking. This applies to a specification, or to acknowledging problem reports and updating with theories on what the cause of said problem is and an approach to confirming or fixing it. You can even reference that problem report in commits and merge requests. It pretty beneficial all around.
And docs don’t have to me masterpiece works of art. Just getting people to clarify intent is a huge win. Peer reviewers don’t have time to do a super deep dive into code. If they know what you intended code to do, that’s something many reviewers can check pretty quickly without having to know much context.
It’s selfish and naive to disregard basic documentation of intent.
> One of the things that separates ordinary people from smarter people is the topic of this article, the ability to imagine new concepts, questions, ideas. Colloquially we call this creativity, and it stems from a large degree of playfulness and enjoyment of the subject at hand.
Pretty sure we call that imagination. Creativity, shockingly enough, involves creation, not just imagination.
You can creatively destroy things as well. It’s kind of pedantic to say that creating in the mind does not count as “creating”, just imagining. What about solving abstract problems?
It's a typical corporate effect. Management, with no expertise or even competency, creates absurd schedules and goals and thinks that somehow, just by fiat and edict, they can bend physics and make it so.
Apparently it can be configured with shapes instead.
By the way, have you seen the Firefox extension "Let's Get Color Blind"? It can simulate colorblindness, but perhaps more importantly, it can Daltonize web pages on the fly to make them usable by the colorblind -- even including real-time stuff like video. It blew a protanopic coworker's mind. https://addons.mozilla.org/en-US/firefox/addon/let-s-get-col...
