Governance development sequence for noobs :
1a. Executives : carry ( "critical path" ) skills
1b. Executives : support skills
2. Trainers : of basic skills (1.). ( Do NOT separate from Supervisors : of basic skills. )
3a. Managers : of non-managers (1. and 2.).
3b. Managers : of managers (3a.).
... ( 3. is end-to-end, the entire human resource lifecycle. )
4a. Trainers : of managers (3a.).
4b. Trainers : of manager-managers (3b).
This is the way. The whole way.
Chatting with a friend from a bulge bracket bank with 8 layers of management. I said, once anyone moves from the lowest layer into a non-IC, line manager, role : at least 70% of their work should be dedicated to force-multiplication via talent management.
This means board mandates, organisational architecture, project and task definition, role design, candidate search, evaluation, hiring, development, retention, and termination. You need to brain laws. But most companies are bad at this :P
Memory consolidation, is the pinnacle of operational priorities.
All other activities are subsumed by it. We eat, sleep, regulate emotions of both attraction and aversion, build muscle, and accumulate social and material capital of other kinds, simply in its service.
This is not to say we choose this religiously. Evolutionary biology presents an inversion of naive control. We exist only because no other optimisation target mattered. Civilisation progress from second to second, only because it remembers the past.
This gives us an insight into how societies develop, based on the narratives that they provide individuals, about the use of memory. In some societies, the future of this world is not something to aspire to, as it is forecasted to decay - hence memory consolidation in such subjects focuses on other-worldly objectives.
- Thoughts before getting out of bed today. I remain a student of students.
... a case of (A) Getting annoyed because A's opinion is ignored ...
Me : I did this today
A : you know, you should do that instead
Me : I don't plan on doing that
A : why did you ask my opinion?
Me : I didn't ask your opinion
A : I am annoyed
Me : I am not annoyed
... vs. (B) getting annoyed because B receives an unsolicited opinion ...
B : I did this today
Me : you should do that instead
B : I don't want solutions, I want to be heard
Me : you were heard, and the solution is provided for free
B : I didn't ask your opinion
Me : I am not annoyed
B : I am annoyed
So you see ... the problem is not who is giving unwanted opinions ... the problem is ... who gets annoyed lol.
The greatest gift my parents gave me : was a sense of infinite boredom. They were/are religious folks, whereas you might say I am agnostic. I did not appreciate the structure of their faith in God - but I did appreciate their epistemic tenacity ... which you might call their faith in their own faith : pure arrogance, summoned and dismissed at will, deployed for either operational, political, or epistemic purposes ( some long-term, some short ). The fact that I live in a politically religious country, may have something to do with all of this, but that's a distraction.
I began adult work, with some basic assumptions, after college some 20 years ago ...
... so I did that for that much time, with some breaks in between.
More recently I was talking to a close friend who often taunts me about how, I "have not accomplished much" in life. I thought this was really funny. Step 2 in the Klein sequence is ridicule, following willful ignorance, and step 3 is resistance, so I offered, "well, I considered myself over-accomplished at the age of 20, and so all my time since then has been spent trying to figure out how to carry that accomplishment with some modesty".
I write about this often : the absence of satisfaction, drives much of commercial success. The culture of business is to maximise gain by force, tempered only by socialist tendencies. So ruthless domination of peers becomes a defining factor of winning, and moated comparative advantages are the key to trade-dominance. Ruthlessly self-satisfied people don't get into business ... they go into the arts, and social work.
Read again, the title of this essay.
... some notes on structuring math at the primary school level. It turns out that throwing symbols at kids is a lot harder to digest than throwing reified geometry.
(1) Erlang/OTP NODES are : named virtual machines, in a distributed network of such nodes.
(2) Erlang/OTP MODULES are : encapsulations for Erlang instructions ("code"), which may be loaded onto NODES. MODULES can be VERSIONED, and VERSIONS may be hot-code-swapped on a NODE. A NODE can have only TWO VERSIONS of a a MODULE.
(3) Erlang/OTP PROCESSES are : userspace runtime processes, executing on NODES, reifying Erlang code which may or may not have been encapsulated in a MODULE. ( The availability of [erl_parse, erl_eval] provides a side-channel for loading non-MODULE code. )
(3.1.) PROCESSES persist, even when their calling & called-into MODULES are VERSION-swapped. If a PROCESS has called into VERSION (N) of a MODULE, but not yet called into VERSION (N+1), and if the NODE loads VERSION (N+2), then the PROCESS will be killed. ( PROCESSES cannot skip upgrades to their runtimes : going from VERSIONS (N) to (N+2) is not allowed. )
(4) C-nodes : a C program running independently, can present itself as a NODE, using well-documented protocols. ( Therefore it seems reasonable that C middleware could wrap any other system that wants to present as a NODE. ) This is the loose coupling.
(5) Native Implemented Functions ( NIFs ): a compiled C library, can be linked into MODULES, and thus called by PROCESSES. This is the tight coupling.
(5.1.) When a NODE loads a MODULE, it initiates all that MODULE's NIFs within the NODE's own operating system process ( thus making the NODE susceptible to memory leakage and/or corruption introduced by the NIF ).
(5.2.) An NIF is initialised ONCE by a NODE, regardless of how many MODULES on that NODE link into the NIF. So, an NIF's static variables may introduce persistent storage in memory, for the lifetime of the NODE. This introduces shared memory, between every PROCESS that calls the NIF, via any MODULE on the NODE which links into the same NIF, weakening the NODE's "shared-nothing" protocol guarantees for PROCESSES. The NIF's is evacuated by the NODE, only if/when its calling MODULE is evacuated by the NODE ... NIFs should take precautions to clean up their own C-based memory allocations, as there is no way for NODE to do so.
Remarkable : library research of concurrency models in user space has turned up ... zero common examples, except Erlang's BEAM VM ... of preemptively scheduled, stackful, multitasking architectures.
BEAM's famous limitations are the cold-starts, and fudgy burst capability, which prevents code from approaching C speeds.
Since I am learning C, I should some exercises to understand why this is architecturally impossible ( null hypothesis ).
---
In other news : Didn't think I'd have to pick up C++. But here we are 18 years after my first job in a bank with the title "quant". Malaysia, after all these years is STILL low-tech, and low-financial-sophistication.
( to check with execution later )
Learning pointer syntax today. I've tentatively decided that the best way to pronounce "*" is "via", and "&" is "address of" :
Setting :
chinaman *(via) address = NULL
chinaman name = "Lee" who lives at "birch street"
address = &(address of)name
Implies :
address == "birch street"
*(via) address == "Lee"
"I like working on investment, risk, ops, law, and stakeholder happiness. I study cybernetics. I moderate a discipline of disavowing credibility. That pretty much sums up my entire life.
1990-2000 : Chinese language, math, science @ Malaysia
2001-2005 : B.A. ( philosophy ) @ Bates.edu USA
2005-2023 : commercial fieldwork @ Malaysia
2023-2032 : consolidation of study : maths, stats, programming, macroeconomics, physiology"
Humility is deciding to be happy when you wake up ( "grateful" ).
It is deciding to be productive today ( "engaged" ).
It is deciding to expect no further days ( "content" ).
This is the way.
( Probably the lazy way.)
Top-students in Malaysia need to know, the job market is meritocratic - but the rule isn't "how smart you are" it's "how much money you protect".
MPT : Money, power, and time are the same. You can be a dumb shit, and make lots of MPT by protecting MPT for other people.
You can also be a smart shit, and receive 0 chances to make more MPT, because you are not protecting any significant amount of other people's MPT.
It's inherently political!
Know the game!
Maybe you don't want to make money.
