Quality vs quantity of course depends on the nature of work. If you are employee and all the working infrastructure is ready there to be used, you can "just" focus on doing something, what ever it is. If you are employer, you can't "just" even go to the work, because you have to use unpredicted amount of time to figure out what you even need to do or have and why.
Whether you are employee or employer, make sure you feel the practical progress, that is, e.g. once a week you can have status session, where you can show that now you have something that you didn't have at last session, and that it is important step for the end goal.
Try to explode different things, so you can see clear boundaries of each separate thing and to minimize redundancy.
Try to map the depencency graph of a thing. Every higher level thing is a make file / spreadsheet cell DAG.
Something better than CVS was needed. (I'm not being critical of CVS. I had to use the VCSes that can before, and CVS was amazing compared to them.) Monochrome gave me the idea of doing a distributed VCS and storing content in SQLite, but Monochrome didn't support sync over HTTP, which I definitely wanted. Git had just appeared, and was really bad back in those early years. (It still isn't great, IMO, though people who have never used anything other than Git are quick to dispute that claim.) Mercurial was... Mercurial. So I decided to write my own DVCS.
This turned out to be a good thing, though not in the way I expected. Since Fossil is built on top of SQLite, Fossil became a test platform for SQLite. Furthermore, when I work on Fossil, I see SQLite from the point of view of an application developer using SQLite, rather than in my usual role of a developer of SQLite. That change in perspective has helps me to make SQLite better. Being the primary developer of the DVCS for SQLite in addition to SQLite itself also give me the freedom to adapt the DVCS to the specific needs of the SQLite project, which I have done on many occasions. People make fun of me for writing my own DVCS for SQLite, but in the balance it was a good move.
Note that Fossil is like Git in that it stores check-ins an a directed acyclic graph (DAG), though the details of each node are different. The key difference is that Fossil stores the DAG in a relational database (SQLite) whereas Git uses a custom "packfile" key/value store. Since the content is in a relational database, it is really easy to add features like tickets, and wiki, and a forum, and chat - you've got an RDBMS sitting there, so why not use it? Even without those bonus features, you also have the benefit of being about to query the DAG using SQL to get useful information that is difficult to obtain from Git. "Detached heads" are not possible in Fossil, for example. Tags are not limited by filesystem filename restrictions. You can tag multiple check-ins with the same tag (ex: all releases are tagged "release".) If you reference an older check-in in the check-in comment of a newer check-in, then go back and look at the older check-in (perhaps you bisected there), it will give a forward reference to the newer one. And so forth.
https://sqlite.org/althttpd/doc/trunk/althttpd.md
Just like Fossil vs Git, SQLite vs $SomeRealSQLServer, I wish someday Althttpd would become a no-bullshit self-contained replacement for Nginx/Apache/whatever bloated HTTP servers. It has already proved its working by serving Fossil/SQLite, but configuration/features for serving actual web site is not yet "real production quality", at least that is how I feel.
Overall, what an amazing legacy this set of software has been to the world.
On the macOS side, it gets more locked and buggy and inconsistent with every release.
This is just a general comment for Apple OSs today, not specifically version 26.2.
I have fresh experience of setting up Azure/M365 and AppleDev for my startup. Those things are scary as f*uck, in many perspectives:
(1) Dark patterns everywhere (click this checkbox and we'll buy you a license, oops +xxxxx €/$ per year just came; get one-month trial for O365 to get bizaccount, select 1 license, see that there is 25 licenses (~ 4k €/$) to be renewed if I don't cancel).
(2) Microtransactions everywhere (e.g. Azure VM SSD I/O: every read/write operations costs), DDOS and 10/100 k€ bill coming. Everything "scales", especially bills. And no billing caps, of course.
(3) Codesign with Microsoft: I have option to wait weeks for freight ship to ship USB cert token (if it ever survives past toll/postal service after that), or use AzureKeyVault, but that is officially only for companies that has taxes/accounting for 3 years of operation. So no startup can use that by this requirement to codesign?!
(4) AppleDev (and kind of Azure/MS too) requires DUNS number, which takes 6 weeks to get in normal case. Apple's 5 bizday route doesn't exist anymore (at least not for non-US-based companies). Or just use D&B magic link from Grok and get it immediately in 5 mins.
(5) If you base your business on Azure/M365 and AppleDev and be obidient and compliant (as I am doing/being, because I'm building real legit and long-term company, not some hussle project), it still doesn't matter, because they can just can decide by human/ML to shut your business operations and means of living. And getting answers like in the title's article's screenshots with those emojis are just the most non-human interaction that there can be done for affecting so devastatingly to someone's life/business.
These are the most disgusting things that I know of.
Yeah, I can't quit Excel. Every day there are spreadsheets open in my taskbar, even right now :)