After two decades spent designing, optimising and troubleshooting complex IT architectures, I decided to change direction. I left behind lines of code, servers and data flows to turn my attention to life sciences, supporting people and managing our own energy.<\/p>\n\n\n\n
At first glance, this 180-degree shift looks like a radical break. Yet, as I\u2019ve gained more experience, one thing has become clear: The laws governing the stability of a computer system and those governing a human being\u2019s equilibrium are closely linked.<\/strong> Changing career paths didn\u2019t mean I had to forget my past, but rather that I had to translate my systemic skills from one language to another.<\/p>\n\n\n\n Here are the key lessons that twenty years in IT have taught me about understanding and nurturing human energy.<\/p>\n\n\n\n In computing, bandwidth refers to the maximum capacity of a channel to transmit data. If you overload a network with requests, the system slows down, packets are lost, and this leads to crash<\/em>.<\/p>\n\n\n\n Human beings function in exactly the same way. Our attention and our nervous energy constitute our own bandwidth.<\/p>\n\n\n\n \u2018Technical debt\u2019 is a concept well known to developers: to get things done quickly, we write imperfect code, promising ourselves we\u2019ll fix it later. But if it builds up, the system becomes inflexible, unstable and impossible to evolve.<\/p>\n\n\n\n When I moved into bioengineering, I discovered the biological debt<\/strong>.<\/p>\n\n\n\n To ensure that a website or app never goes down, IT engineers use the principle of redundancy<\/strong> : if one server goes down, another takes over immediately. This is the basis of high availability.<\/p>\n\n\n\n Applied to humans, this principle becomes the key to psychological and physical resilience:<\/p>\n\n\n\n A computer system receives inputsinputs<\/em>, processes them, and generates outputsoutputs<\/em>. If the input data is corrupted, the result will be too (Garbage in, garbage out<\/em>).<\/p>\n\n\n\n Living organisms follow this same logic of flow, governed by thehomeostasis<\/strong> \u2014 an organism\u2019s ability to maintain its internal balance despite external stresses.<\/p>\n\n\n\n Moving from maintaining machines to caring for living beings has not taken me far from my core identity as an engineer. In both worlds, it is a matter of analysing weak signals, diagnosing malfunctions, respecting rest cycles and optimising limited resources.<\/p>\n\n\n\n The main difference? Living organisms cannot be reprogrammed with lines of code or instant fixes. They require time, respect for their natural rhythms, and a deep willingness to listen. Twenty years in IT have taught me the rigour of structures; the engineering of living organisms is now teaching me humility in the face of life\u2019s complexity.<\/p>\n\n\n\n <\/p>","protected":false},"excerpt":{"rendered":" Un regard sur la transition de l’ing\u00e9nierie des syst\u00e8mes \u00e0 l’ing\u00e9nierie du vivant \u2014 et ce que ces deux mondes ont en commun. Apr\u00e8s deux d\u00e9cennies pass\u00e9es \u00e0 concevoir, optimiser et d\u00e9panner des architectures informatiques complexes, j’ai choisi de bifurquer. J’ai quitt\u00e9 les lignes de code, les serveurs et les flux de donn\u00e9es pour me…<\/p>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","footnotes":""},"categories":[8],"tags":[],"class_list":["post-168","post","type-post","status-publish","format-standard","hentry","category-pratique"],"yoast_head":"\n1. Emotional bandwidth and cognitive load<\/h2>\n\n\n\n
\n
2. From technical debt to biological debt<\/h2>\n\n\n\n
\n
3. The importance of redundancy and resilient architectures<\/h2>\n\n\n\n
\n
4. Input, Output and Homeostasis: the Law of Flows<\/h2>\n\n\n\n
\n
Conclusion: The source code changes, but the logic remains the same<\/h2>\n\n\n\n