Software Cycles
v2: ~ $ core_add
Software is best developed in cycles.
Each cycle should have a different objective and the main point of each turn should be establishing order and building in undeniable consistency. The reason so much of the software we are forced to use feels poorly designed is because it is.
Software is best built in cycles because this way of building allows the end result to have established and undeniable consistency.
That consistency is what makes the software intuitive. I build all of my software in cycles so that one day the software is able to be used by others, but until it is consistent, I understand it will only be used by me.
Many businesses that are in the software development business do not understand this concept and their engineers don't know how to build anything worth using because of it. Software worth using must be developed in cycles where each rotation is an iteration of establishing consistency first and foremost.
That's the opposite of what many in the industry do now. Software was once built in this way more often. Now, the primary focus of most software development agencies is on a single point deliverable. I've never seen software that's worth using that's developed like this. Mostly all of the software that is "great" was built out from an origin, and later, through cycles, became what you know it as today.
I think this is why a lot of the best projects get built by 1 or maybe just 2 engineers. If there were more than that, how can the project maintain consistency? That's why I think it's more important than ever at product-facing organizations that anyone touching the product actually has the tools to build the product alone if need be. You can always tell when a product is the victim of too many cooks.
The best products get built over the years out of necessary cycles, and eventually, much like a sculpture, the stone is set and form is worth admiring. That's really when it should be put into the public square.
As for what my next batch of iterations are - I would like to think they're now approaching the "final" initial stage before public distribution. My work is now at a point where the consistency is the primary focus, not the functionality or project focus.
By the end of 2023, I will have some of the most refined social-oriented software developed in the world. It didn't just get built. I built it with my own hands and although it wasn't easy, completion was the objective - but not just as a single point of delivery. The goal was to deliver the software as the result of the required cycles - no matter how many cycles it had to take on.
What's been built was refined and ordered over cycles that took many years. Now, each new cycle cleans up just a little more - and soon, there will be nothing left to amend.
Note #18,004 Added
v2: ~ $ _