"Take him to a psychologist" was standard playbook in soviet block to silence dissent. Everyone knows of the gulag archipelago but just declaring someone insane was part of the toolkit.
If you need this stuff in production I recommend getting a good computer graphics textbook.
These cheat sheets are convenient _if you already know what you are doing_ and _are confident the cheat sheet uses same presentation as your problem domain_.
That said I'm not sure if there is a nice book that would be both exact and practical at the same time.
"The boss" is not who says what is good enough. Ultimately it's the customer. In many industries it seems good enough is not very good.
Then there are industries where the customer complains if code is slow. They will actually hire expensive consultants to analyze and benchmark the code. And while the consultants likely are not more talented than inhouse staff, now you have both sides very interested at looking at the problem from engineering perspective.
I guess they can say "Made in China, designed by Apple in California" in the packaging but at least they still take pride in the design. With AI it sounds you are disavowing also the authorship of the design.
"Founding cannot be a commodity. If it is, you have no moat or point, meaning you instantly collapse again, because you are an interchangeable commodity."
IMHO you still need to find the product and PMF
There are bunch of books startup world recommends which sort of all start from the principle of product, users, traction.
This is sort of scaffolding around that. It's not entirely insane to try to formalize this process - there already are books that do this (Bill Aulet, Disciplined entrepreneurship).
"nor does it make sense for society to have people founding businesses at a scale"
Maybe not at scale of moving lawns but I'm pretty sure the world is full of nichces that still lack specific software offering or where options of software offerings are limited.
This is like "Uber for logging" or "time reservation system for cat dentists" level of "take existing product category and apply to a domain you know".
So not every cat dentist needs to found a cat dentist time reservation app but I'm sure there are niches withing niches with business opportunities awaiting.
This! The only way to get to a stable system at least with c/c++ source, where you can hunt bugs, is to have a fairly large unit test coverage. When something fails - add that as test case; run ctest - pray that this is discoverable with tests.
So wasm is a really strange compilation target for systems programming languages.
I mean there _are_ ways to debug it in a browser but they sort of suck.
"I think most of us are happy to believe that most companies simply have bad leadership"
I don't believe this for a second.
I don't know if this makes me the minority or not though!
It trivializes forces influencing large public companies.
Yes - there can be good and bad leadership - and bad leadership is just bad.
But good leadership can be totally helpless in a public company.
Not recognizing this is a huge gap.
The other forces that incluence a company:
- Board
- Shareholders (via board)
- Banks. Lots of companies have loans. The banks generally have the companies by the balls and can dictate many things when things go south - either due to leaderhip or just prevailing market winds
As an example of shareholder/board direct and rapid influence: an activist purchases shares. Installs board member. Causes rapid change in one or more aspects of business structure or strategy to support _their_ portfolio strategy (of course aligned with interests of other shareholders).
"the crazy part to me is how blatant the executives of bricks and minifigs are in saying go ahead and try to sue us, we’ll drag this out "
To my experience this is a common strategy in disputes when the corporate party has people who operate as uncivilized brutes. I think it's part of the McKinseyfication of companies - profits at all cost - and here's the playbook.
My personal experience is from private parking control. Rather than be professional about my reclamation, their first response was "only criminals dispute these and we win all the court cases".
So I think trying to be imposing and villanous to scare the other non-corporate party to back off is a common global corporate playbook in situations in matters where companies enter contractual complex space with individuals.
In my mind design and theory are inseparable. Design is the accumulation of many design decisions. Theory explains what influenced those decisions.
Design needs theory to be intentional. It can of course be accidental (”seems to work, I guess”) or intuitive (”i know in my guts this is right but cant explain it”).
While both can end up with functional systems, if you cant vocalize the design journey the system is not very maintainable in the industrial sense (hence - theory is the vocalization of the design and the forces that influenced it).
Another point of view is that LLM:s perform to an extent on the same level as outsourcing does. This interface requires a bit more contract mass than doing everything within single team.
Having worked in CAD for over a decade previously, I think the users want a product surface, and the people paying for the engineers time want a reliable trainable solution that will exist exactly as it is today in five years. They are happy to pay for it in monthly installments.
This is a separate dimension to alternative high quality modeling solutions alone.
Now, some of the users especially are _proud_ of their product specific skill set. They don't _want_ to switch a package.
And - it's much easier to get professional engineers to use extensions to packages their engineering office already uses.
And this comes before any technical side-by-side feature comparison.
The routine in Tabata’s original HIIT work was just cycling.
Crossfit afaik is a more complex affair than just cycling.
So is the risk of injury due to specific movement or the interval quality of the movement?