Instructions for installation, normal operation, communication, maintenance and fault diagnosis. Read before first contact. Retain for future reference.
Accepted input
Context + evidence
Nominal output
Software + opinions
Communications
Async / distributed
A1 / OPERATORCAL. 1991–12FIG. 00 — FRONT ELEVATION / NOT TO SCALE
CALIBRATION TRACECH–01 / 0.8 V
SECTION 01
Precautions & initial setup
Read all notices before placing the unit in service.
1.1 Before commissioning
WARNINGEN / 01
Serious or fatal emotion injuries can occur from not reading this document in advance. To prevent this situation you must acknowledge what's on the manual with the included attached pun jokes.
ATENCIÓCA / 02
Risc de lesions emocionals series o fatals és poden produir si no es llegeix aquest document. Per prevenir aquesta situación vosté ha de comprendre allò qué está escrit en el manual. Incloses les bromes dolentes.
ADVERTENCIAES / 03
Pueden producirse lesiones emocionales graves o fatales si no lee este documento. Para evitar dicha situación, debe entenderse lo que se encuentra escrito en el manual. Incluidas las bromas adjuntas.
SECTION 02
Illustrated component inventory
Confirm component count before placing the unit in service.
Success isn't vertical. Nor a straight path. Resiliency is the real success. Failing over and over, until you get there.
But there's more. All the winds are bad if a ship doesn't know where's heading. You need a goal, a clear one. And to focus on it.
In the software industry. You need also to find a balance between achieving your perfect goal and being quick. We work in a fast-paced world. Every minute counts, make it valuable.
Finally, there's no winning without honour. The rule is simple: if it's not right, don't do it.
Right to the point. I don't like blatantly. Short yet accurate sentences. I appreciate funny messages, as well. I don't think you're more righteous if you speak more seriously.
Everything is about the content. The envelope is nice but focus on the content. Don't waste anyone's time. Make sure that you checked first.
Async and distributed over everything else. Does this need to be a meeting? Probably could be an email. Or a slack message. Rule of thumb: think about me as if I'm working from Jupiter thus real-time comms don't work.
I can be too harsh sometimes. Well, not really. I can sound too harsh. It's probably a side-effect caused by the async comms. It takes a lot for me to get angry, so don't worry about it.
I don't want to listen to opinions (if I don't ask for them). I'm driven by data only. I already have an opinion about almost anything. And I don't need another.
I have a dark sense of humour. If I offend you I'm sorry. Really I am. Please, let me know and I'll adapt my jokes to you.
CAUTION — Confirm tone before diagnosing hostility.
Loyalty is the best. Lying is the worst. I can understand almost anything. Just try to explain it. Don't lie to me.
Now, regarding day-to-day work. Taking ownership of your task is a massive trust boost. I deeply respect people with such mindset.
Does that mean that you have to work extra hours? Extra effort? Extra extra? Nope, that's bad. In my culture, such behaviour means that you need to overwork to achieve your goals. If there's something that goes bad, just be transparent. No big deal.
I'm thoughtful. I'm strategic and I like to plan. Having a good amount of data around me to make the right decision.
I'm also stubborn but in a good way. Since I try to not be opinionated, I have a clear focus and a well-defined goal. So, being stubborn means a better output.
I understand. Understand other problems and needs. Understand business operations and the market. Understand the context. This life is about adapting.
SECTION 06
Troubleshooting
Consult the fault table before escalating.
Fault diagnosis & corrective action
Observed condition
Probable cause
Corrective action
Reply contains one line
Deep-work mode; no malfunction detected
Send one asynchronous ping and wait. Do not escalate to a call.
Review contains many questions
Request or PR arrived without context
Add the rationale, constraints and evidence; request review again.
Unit asks “do we have data on this?”
Opinion supplied without evidence
Attach numbers or clearly label the input as a hypothesis.
Unscheduled ███ event
factory field anomaly
Return HOME, restore context and act normal.
Maintenance record — to be completed by the operator
