Zenith

I’d rather hunt mammoths

If a genie in a lamp offered me a single wish, I would seriously consider transporting myself to the Neolithic. To practice hunting and gathering. To live in communion with a small tribe. Building temples for the gods in the spring, hunting mammoths in the summer, migrating to the forests in the winter.

In that era, the chance of dying torn apart by a saber-toothed tiger would be much higher. But at least it would be a life with a deeply human plot. And the fatal agony would last only a few minutes.

Contemporary life, by comparison, may well be an absurd and meaningless eternity. Even “pop” historians like Yuval Harari admit: there is no evidence that we are on average happier today than we were 20,000 years ago. Technical progress exists, but not necessarily existential progress.

Useful bureaucrats

And this is our context: a society in which, if you haven’t inherited a fortune, you will need to work for others. Sociologist Jessé Souza explains that for those who do not possess material capital—land, factories, real estate, investments—only one dignified alternative remains: to accumulate cultural capital. In other words, learning to do something that has some value and utility for others.

Looking closely, the middle class is exactly that: a social layer of useful bureaucrats. It is the portion of the population that holds a considerable stock of language, technical knowledge, and the ability to navigate institutions. To make projects move from paper to reality.

Still, members of the middle class rarely manage to become capitalist owners. Generally, they work their entire lives to perhaps acquire a couple of properties. Or not even that.

A guide

That being said, I think I’ve made it clear that I don’t romanticize work. If I could, I would live differently. But having to work, let it be done with some intelligence.

With this in mind, I have created a synthesis of eight principles that contribute to this end. For pure fun, I call them zenith. Each principle has a funny acronym in English to help with memorization. They are guidelines for those who, like me, need to produce—but above all, want to breathe.

These rules are the result of a modest work trajectory, mainly academic. The emphasis is much greater for information bureaucrats who, like me, live by operating digital computers and seek project-based results. Scientists and technicians are the primary focus, as opposed to physiotherapists, for example. But I believe these are generic enough principles for other professions.

Obviously, beyond my own experience, this list was influenced by a dozen books, videos, and lectures on personal growth and self-help—some very good, others not so much. Amidst the chaos of authors, I strongly recommend the tips from Cal Newport and Greg McKeown.

The principles

The principles follow English nomenclature, but I also present a free translation. The following equations summarize the core idea of each principle.

1. CALM: Time = Life
2. PRINT: Publish = Exist
3. GRACE: Beauty = Value
4. DRY: Reuse = Efficiency
5. KISS: Simplicity = Flexibility
6. DOCS: Documentation = Memory
7. LOOP: Improve = Learn
8. SYNC: Scale = Cooperation

1. CALM – Conscious Allocation of Life and Momentum

Time = Life

Explanation

Put life first. Work is a means. Life is the end. The purpose of work is to serve a full life—not to consume it. A meaningful life must be lived not just in the future, but in the present: for joy, fun, rest, sports, relationships, nature, and anything that brings meaning. Work should enable these things, not postpone them indefinitely. Structure time to protect life. Design a calendar that balances effort with presence. Optimize processes not just for productivity, but to make room for what truly matters—now and later.

Implication

Use time to prioritize life.

• Divide work into creative (value), administrative (enabler), and networking (future-building);
• Group these types of work into deep sessions and schedule them carefully to reduce cognitive switching costs;
• Structure time across all scales—day, week, season, and year;
• Apply rigorous boundaries between work and life to protect time for health, fun, and presence;
• Optimize systems and workflows to create intentional space for meaning and rest;

Moderation

CALM is not passivity—it is controlled rhythm.

• CALM is not simply taking it easy—it is the conscious design of effort and rest;
• Work with focus and discipline during structured time;
• Accept moments of intense effort when they serve a launch, delivery, or responsibility;
• Recover intentionally after marathons, but do not avoid them when necessary;
• Live fully in the present, but build systems that support a meaningful future;

2. PRINT – Publish Results or It’s Not There

Publish = Exist

Make work visible to everyone. Every project should produce a shareable result that is beautiful, understandable, and impactful. If it isn’t visible, it’s as if it doesn’t exist. Clear the path for public recognition and peer respect. Publish or vanish.

Implication

Visibility is proof of existence.

• Deliver public and citable results at the end of each project;
• Prioritize projects that allow for publicity rather than hidden, dead-end work;
• Focus on printable, paper-oriented results—paper can last for centuries;
• Extract and share publishable fragments when full disclosure is not possible;
• Let publication demonstrate utility and leave a portfolio trail;

Moderation

Publishing is not a goal, but an indicator for impact.

• Let refinement support relevance for the audience, not for yourself;
• Avoid dumping superficial content and production volume;
• Publish only when quality and clarity are present;
• Respect project constraints—reuse material, data, and models later if necessary;
• Do not confuse visibility with impact—align both;

3. GRACE – Give Results A Clear Elegance

Beauty = Value

Explanation

Make the work beautiful. Let every result—figure, text, report, dataset, codebase—carry a sense of elegance, clarity, and expressive form. Beauty gives meaning to effort. A well-crafted diagram, a carefully named function, a clean layout—everything elevates the work beyond mere utility. Use creativity, visual clarity, and narrative style to inspire. Let the result reflect care.

Implication

Beauty is value made visible—and preferred.

• Design results to be clear, readable, and aesthetically pleasing;
• Use expressive documentation and thoughtful language to elevate perception;
• Name processes and structures creatively when appropriate, preserving clarity;
• Refine figures and layouts for visual harmony, not just accuracy;
• When technical quality is equal, the more elegant and beautiful result will win the audience’s trust;

Moderation

GRACE must serve communication, not the ego.

• Let elegance enhance understanding—not replace it;
• Do not over-perfect—publish once clarity is achieved;
• Avoid treating every project like a masterpiece—keep learning for the next project;
• Adapt beauty to the audience—keep results accessible, not overly personal or obscure;
• Use creativity in overarching concepts, but maintain clarity and standardization in technical nomenclature;

4. DRY – Don’t Repeat Yourself

Reuse = Efficiency

Explanation

Avoid duplication. Build reusable systems. Every effort should contribute to long-term infrastructure through modular code, templates, structured data, and automated processes.

Implication

Let your work accumulate over time.

• Evaluate how each project can contribute to some form of useful resource for other projects (now and in the future);
• Use automation to reduce manual repetition of predictable and tedious protocols;
• Create templates for everything: projects, notes, documents, presentations, code, etc.;
• Write reusable code by writing generic modules, packages, and libraries;
• Design a system to store, retrieve, and update datasets so you don’t have to download and organize them every time;

Moderation

Not all reuse starts on day one.

• Reuse is a horizon—not a prerequisite;
• Avoid over-building before patterns emerge;
• Use simple documentation to implement quick solutions when time is short;
• Expand generality only when there is demand;
• Improve systems iteratively, not all at once;

5. KISS – Keep It Simple and Smart

Simplicity = Flexibility

Explanation

Favor simplicity. Let complexity emerge from simple parts. Build systems with maximum interoperability. Choose open tools, transparent formats, and modular design. Avoid hype, over-engineering, and black-box dependencies.

Implication

Start simple—scale only with necessity.

• Use lightweight tools and avoid unnecessary dependencies;
• Favor modular structures instead of tangled systems;
• Write code and documentation that are clear without deep explanations;
• Choose tools that are open, inspectable, and adaptable;
• Minimize interface complexity while maximizing clarity;

Moderation

Simplicity is a guide—not a limit.

• Seek elegance, not emptiness;
• Accept necessary complexity when justified by function and efficiency;
• Avoid superficial minimalism that undermines robustness;
• Upgrade tools only when the value outweighs the cost;
• Use sophistication with intention, not ego;

6. DOCS – Document Or Considered Scrap

Documentation = Memory

Explanation

Undocumented work is disposable trash. Documentation is the memory, the entry point, and the survival layer of all systems. Without it, nothing can be reused, transferred, or resumed later.

Implication

If it can’t be explained, it can’t be reused.

• Create a README or a clear entry point note for every project;
• Use notes and comments strategically;
• Apply standard naming rules and automate documentation whenever possible;
• Preserve context, logic, and instructions for quick reentry;
• Keep documentation updated and clear;

Moderation

Documentation must evolve—not suffocate.

• Clarify what matters—revise as systems mature;
• Avoid documenting features that may be quickly discarded;
• Use lightweight formats and update progressively;
• Focus documentation on reuse, not bureaucracy;
• Avoid documenting the obvious;

7. LOOP – Launch, Observe, Optimize, Progress

Improve = Learn

Explanation

Start first. Improve later. Deliver a functional minimum viable product, observe its use, and then adjust only where it matters. Don’t perfect in isolation—respond to reality. Let natural feedback shape the path forward. Learn by doing.

Implication

Draft, then improve with purpose.

• Start with a functional minimum viable product and publish it early to gain momentum;
• Observe real-world use to guide refinement;
• Adjust results that are visible or impactful;
• Treat the first version as an operational test or benchmarking;
• Improve iteratively—and move on when it is sufficient;

Moderation

Launch fast—but not carelessly.

• Avoid refining invisible systems unless necessary;
• Ensure early public versions meet minimum quality thresholds;
• Perfect the interface (form) more than the back-end (function);
• Balance speed with reliability and usability;
• Iterate only when feedback or usage justifies it;

8. SYNC – Scale Yield by Network Collaboration

Scale = Cooperation

Explanation

Work multiplies when done in collaboration. Parallel action across diverse skills creates a synergistic effect that far exceeds individual effort. Collaboration is not merely additive—it is multiplicative. Each collaborator brings a unique role, and through well-defined interfaces and shared understanding, the team becomes a system.

Implication

Scale emerges from structured cooperation.

• Form compact teams with distinct roles and a shared sense of ownership;
• Design clear interfaces between roles while maintaining an understanding of the complete system;
• Use the team structure to promote co-responsibility and built-in quality control;
• Share credit, visibility, and rewards—avoid hoarding resources or recognition;
• Build communication systems with pre-scheduled meetings, asynchronous decision logs, and minimal friction;

Moderation

Syncing doesn’t mean creating a crowd.

• Avoid oversized teams that dilute responsibility and reduce attachment to the work;
• Maintain a peer-based structure with diverse functions—but a shared commitment to excellence;
• Deep creative work is only possible during immersive isolation, so respect colleagues’ autonomy;
• Avoid communication overhead by grouping messages on a weekly scale or higher;
• Assign quality oversight roles—do not overpopulate the review process;