technology occupies a growing share of our lives. building it well means deciding what deserves our time, which burdens we can remove, and which capabilities should belong to the people who use it.
in on the happy life, seneca starts with the destination: speed can take us further from our goal when we choose the wrong path. in on the shortness of life, he examines the time we give away without noticing. our approach to building starts with those two questions: where are we going? what are we spending our lives on?
we have limited time. what we choose to do with it matters.ataraxy · a reading of on the shortness of life
speed matters when it serves a chosen purpose. automation matters when it removes a real burden. a delivery is complete when it leaves people with the ability to act, understand and decide.
seneca opens on the happy life with a warning: moving faster in the wrong direction takes us further from our destination.
on the happy life · 1
before choosing tools, we define the problem, who it affects, and which outcome would justify building. we also agree on what to leave out.
a feature without a clear purpose goes back into discussion before it enters development.
in on the shortness of life, we protect our possessions while allowing our time to slip away.
on the shortness of life · 1–3
we consider the time required to build, learn, use and maintain a system. its cost includes the attention it will keep demanding after delivery.
we evaluate automation by the work it removes and the exceptions, reviews and new tasks it creates.
seneca describes lives consumed by occupations that leave people unable to direct their own time. a full schedule can lack a chosen direction.
on the shortness of life · 2 and 7
every meeting, integration and release must contribute to an outcome. we simplify a process before making it faster.
if a step can disappear, we remove it before writing software to perform it.
on the happy life examines our relationship with possessions: using them well requires retaining our freedom in relation to them.
on the happy life · 21–26
we choose AI and software for their usefulness, limits and costs. people remain accountable for decisions, and we consider the consequences for those affected.
when a simpler solution solves the problem better, that is what we propose.
both essays invite us to examine how much of our lives and time we can actually direct.
a reading of both essays
we plan for transfer from the start: access to code and data, useful documentation, understandable operations and the knowledge needed to make decisions.
the client should be able to operate the system, change providers and make informed decisions about its future.
we embed to understand. we build with a purpose. we transfer so the capability stays in your organization. that is the relationship we seek between technology, work and autonomy.
let’s discuss what is worth building ↗see how we work ↗