Is the 300x performance boost attributable to the threading model vs process model?
Was the code for the threading model written by hand or was it translated from the WIP threading model the human PG team is busy with as part of the 2028 roadmap?
This is a fascinating topic, some of the comments are interesting too. I wonder whether some folks who knowingly or unknowingly use this technique to their advantage are the ones recently insisting the end to WFH and a return to the office? It's possible they're not given a chance to unleash their alter ego at home while the family members are around?
There is no default life script. Everyone is a myth legend. A hero. You can't fault an opinion piece like the posted article, but there's a chink in this thinking. Such opinions - give agency early and it will yield dividends not just for the individual but for humanity as a whole appeals to our most primal human conundrum: our sense of purpose and our destiny in life. The idea of the one individual making geometrically disproportionate impact for all humanity is mythologised. And it's an error. The flip-side of this myth is the ugly face that if we as a society stop producing such myth legends (the original author claims it might have stopped after ca 1968) we are failing as humanity, or worse that if you do not become that myth-legend you are unworthy of respect, or dignity. This is a terrible way to look at things. I do agree about the author's powerful comment that kids (adolescents) today are hardly considered useful for any form of vocational education outside the cookie-cut education systems. But can you orchestrate this paradigm like the CCP did in the late 60s/70s forcing urban kids to learn farming as part of their education? Or is it a naturally existing societal affordance to enable such evolution in kids?
There are many unspoken mythical legends living today, huddled in their numbered and anonymous cubicles. There are many unknown engineers who've done crucial work within their own boundaries of "scripted life" to prevent bridges from collapsing or payroll runs to be corrupted (just in time). No one hears about them. No one celebrates them. But there are billions of us on this planet achieving myth-level brilliance daily just by being responsible parents. Or just by being simply kind to fellow humans.
There is no default scripted life.
Edited: added "Or just by being simply kind to fellow humans."
>All that stuff is critical to know as part of analysis.
Exactly. I wonder if the frustration to get started as soon as possible ultimately results in data models that aren't ready yet and therefore brittle (IOW: insufficient analysis and logical testing of the data models before UI and other process logic commenced).
>I agree, and I've come to the conclusion that you should avoid designing a database schema until you have some clear understanding about how the application you're persisting data for will be used.<
I don't buy this argument, with due respect. (I see a lot of this thought these days and I'm genuinely worried we are about to swing the pendulum of software design into the dark ages where focus from the data model is taken away in favour of convenience of process design, front end design and data access frameworks).
In my experience: the objects from the problem domain will always have certain immutable relationships with each other right from the beginning. You have to look for them first before you do anything. They are clearly identifiable. What to persist and what not to persist are also discernible from existing manual business processes and the documents operational staff use daily (many of these are legal documents like tax invoices, contract confirmation, mandates and policy agreements etc ... a great way to start is to look at what reports users might need. Yes, those boring reports! Start there). Then, cardinalities and ordinalities will be known the moment you understand the objects relationships too (Can a client with product A also have product B? etc). Then, identifiers, business keys and other coding formats are also determined very early on in the project.
All of this before you even choose a front-end framework or the people's favourite ORM library.
I start with the data model. I use a good ER modeling tool to avoid frustrating myself when large changes are needed for my model. The models, when sufficiently complete, are printed in large format and pasted on walls for all to see daily. That is then considered holiest of holies.
(I understand that data models that need changes other than adding new columns or new sub entities can be painful to refactor ... but the fear of this eventuality should not automatically translate into turning the development process on its head.)
Option 3 is better than option 2 because it is more likely that a country with WMD will use them against a country without them (for fear of retaliation). Option 3 is an equal standoff.
Was the code for the threading model written by hand or was it translated from the WIP threading model the human PG team is busy with as part of the 2028 roadmap?