There is a lot to unpack here.
We all know the meme of “What the customer wants vs. What was implemented”.
Well, insert some nature inspired development algorithms, which are dependent on a bunch of environmental factors, and you get a real live version of the meme.
Not much to say, accept the Software You Can Love conference was wonderful.
What about this weather we’re having?
Ah well, at least the laws of equal exchange agree with exchanging screen time with fresh air.
But let’s discuss balancing tree structures.
Adding new nodes and branches is usually quite a straightforward operation. Most of the time you don’t have to do anything, the structure grows on its own. But without any kind of supervision or maintenance, it will grow into a random, hard to traverse mess that just wastes resources.
So it is important to either implement proper growing algorithems into the structure itself or do some manual pruning manualy.
Now, whether it be databases or file system structures, it is best practice to do the balancing operations at off peak activity times.
And if you’re developing custom algorithms, document them! Take good snapshots of before and after states for studying.
These are definitely words in the title, but what do they mean? A long-awaited adventure!
By now, the probably obsolete and forgotten RiscV version of MangoPi has been on my TODO list for a while. Fashionable late, but sometimes you have to let things take their time.
What we have here is bare bone blinking of an LED on the MangoPi SBC with Allwinner D1 RiscV chip.
Quite a few steps to get to this point, from figuring out the boot procedure, architecture, pin-out, tool chains, itd…
The condensed version of the steps and code is here.
And there might be some notes as well.
Just because nothing worth writing about is happening, doesn’t mean nothing is happening. Sometimes you just have to bear through the grind to reach a new point.
That does not mean you should completely abandon everything. Repetition keeps things in memory. So a post for the sake of the process of creating a post on this system.
So what have You done on this additional day of the year?
Continuing the previously discussed topic, of daring to be stupid for the sake of learning, sometimes you just have to do something for the sake of doing something.
So why not a fictional calendar with 17 months, with names based on subatomic particles? Why? Why not? And while we’re at it, let’s try out some of the current generation of generating tools.
Some interesting takeaways from this adventure, besides the calendar being useless for tracking anything useful, are as such. The number of months with 21 and 22 days switches depending on whether it’s a leap year or not (lazy day redistribution). And the image generation model used returned a spherical motive with a center and an outer ring always when the description contained a subatomic particle in one form or another.
Any way, here is the whole thing for anyone with too much time: Quantum Chronos 2024