<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Nicolò Ammendola on Medium]]></title>
        <description><![CDATA[Stories by Nicolò Ammendola on Medium]]></description>
        <link>https://medium.com/@nicoammendola?source=rss-61c1109726f2------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*4lit9LjGcfe5h351JHUz2Q.jpeg</url>
            <title>Stories by Nicolò Ammendola on Medium</title>
            <link>https://medium.com/@nicoammendola?source=rss-61c1109726f2------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 21:22:25 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nicoammendola/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Il leader vulnerabile]]></title>
            <link>https://medium.com/@nicoammendola/il-leader-vulnerabile-613522bb9acb?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/613522bb9acb</guid>
            <category><![CDATA[psychotherapy]]></category>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[corporate-culture]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Wed, 06 Sep 2023 20:02:18 GMT</pubDate>
            <atom:updated>2023-09-07T08:20:50.842Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KUPNoL73jHLpyw2cHfjX4Q.jpeg" /></figure><p>Sono stati mesi più complicati questi miei ultimi. Non complicati in termini assoluti, sono abbastanza in forma e ho la fortuna di passare il mio tempo con persone di valore a fare cose che mi piacciono.</p><p>Gli assoluti però lasciano il tempo che trovano. Tutto è relativo, compresi problemi e sofferenza. Ognuno misura le proprie difficoltà con il suo metro. Per me, gli ultimi 18 mesi sono stati complicati. Così complicati che mi sono accorto ben presto che sarebbe stato meglio non affrontarli da solo.</p><p>Così un bel giorno — e non era nemmeno la prima volta — ho deciso di iniziare un percorso di terapia, ho cercato una professionista e ho cominciato a raccontarle la mia vita. Che fatica!</p><p>Dei tanti pensieri che sono nati dalle nostre chiacchierate ce n’è uno in particolare che mi sta a cuore forse più degli altri ed è legato alla vulnerabilità, al mostrarsi fallibili, imperfetti, rotti.</p><p>Credo che una vita densa sia fatta di relazioni significative e di cose ben fatte; e mi sono convinto che mostrarsi vulnerabili sia un ingrediente necessario, benché non sufficiente, per costruire relazioni significative, che sono poi molto utili per fare le cose per bene.</p><p>Parto un po’ da lontano. Ahimè questi pezzi sono sempre più lunghi di come li immagino prima di iniziare.</p><p>Sono stato un bambino timido e sensibile, spesso mi imbarazzavo per gli altri. Poi un ragazzino curioso e molto competitivo. Non tanto nello sport quanto sui banchi di scuola. Quando gran parte dei miei compagni studiavano il sesso, io credo di aver iniziato a studiare, e presto a disprezzare, il “sistema”. Ero, e sono, un nerd.</p><p>Con questo mix di conoscenza e di disprezzo per le regole mi sono conquistato la simpatia di alcuni miei compagni di classe (e di qualche ragazza) e l’antipatia dei maestri che meno stimavo. Fatto sta che quando mi sono accorto che il mio comportamento influenzava quello di qualcun altro, ho sentito che non avrei potuto mostrarmi debole.</p><p>Alla fine del liceo i miei genitori si sono separati. Io sono partito per gli Stati Uniti. Mio fratello minore è rimasto a casa. Così anche sul fronte familiare la sensazione che ebbi fu quella di non poter mollare. Non c’era in me, almeno in quello che vedevano tutti, spazio per la debolezza. Non avrebbe fatto bene né alla mia famiglia, né a mio fratello.</p><p>Mi ci è voluta più di un’altra vita intera — all’epoca avevo 17 anni, ora ne ho 35 — per capire quanto mi sbagliassi.</p><p>Non ho molti amici e faccio un lavoro che è sì di sistemi e software ma è anche — forse soprattutto — di persone. Di persone da ascoltare, conoscere, capire, motivare, formare, accompagnare.</p><p>È un mestiere, quello di chi sta al timone di una delle barche, nella flotta che è l’azienda, che richiede uno sforzo di auto-esame costante. È fatto di conversazioni difficili, di caratteri diversi, di modi di sentire e di pensare anche molto lontani dal mio.</p><p>Dal momento che sono intimamente convinto che un’organizzazione cresce se crescono le sue persone, considero buona parte del mio lavoro aiutare le persone che lavorano con me a crescere.</p><p>Questo significa avere parecchie conversazioni ruvide. Conversazioni che quando riescono ricordano il platonico “sfregamento di anime”. È un’immagine questa, di due anime che si sfregano, che mi porto dietro dal liceo. Ve le immaginate queste due anime, vicine abbastanza da farsi un po’ male, ma non abbastanza da distruggersi, che sono ruvide e si abradono l’un l’altra? Deve far male, no? La filosofia è ricca di immagini come questa, penso ai porcospini di Schopenhauer, vicini abbastanza da scaldarsi, lontani abbastanza da non pungersi. Cerco così, anche nel lavoro, di avvicinare la mia anima a quella dell’altro, per sfregarle quel tanto che basta a rendere significativo l’incontro.</p><p>L’anima però ha una corazza, che è veloce come il paguro nella conchiglia. Se si chiude, è impossibile sfregarla. Da qui la ricetta, testata con discreto successo negli ultimi mesi, di mostrarmi quanto più spesso per quel che sono: vulnerabile.</p><p>A volte non serve molto, anche solo un <em>“dovrai perdonarmi se non trovo le parole più giuste per dirti quello che ti devo dire. Ci ho pensato molto e questo è il meglio che riesco a fare”</em> può ribaltare le sorti di un confronto.</p><p>Ai più navigati sembrerà una sciocchezza ma portare l’attenzione su una propria difficoltà, un proprio limite, non per forza risolto, non ancora superato dimostra consapevolezza e affetto.</p><p>Ti lascio entrare, guarda qui che bel caos che c’è! Ti sto dicendo: mi fido di te, non c’è nulla che tu possa rompere oltre, qui dentro. Guarda tu stesso, dimmi cosa ne pensi. Dammi una mano.</p><p>Non sempre funziona, ma quando funziona, sembra che, quasi per magia, quell’angolino di macerie ti sembri familiare. Capirai così che sono sincero quando ti dico che ti voglio aiutare. Non è la panacea. Alcuni paguri sono nella conchiglia da anni e non hanno più i muscoli per uscire. Ma quando funziona ci faccio caso e penso: in fondo siamo buoni ed è bello che riusciamo a sfregarci così.</p><p><em>Post scriptum</em></p><p>Dimostrarsi vulnerabili non è mai stato facile e credo purtroppo che stia diventando più difficile. Penso principalmente per due motivi.</p><p>Il primo è perché contrario alla logica della performance che sembra essersi impossessata di molte organizzazioni, forse della società intera.</p><p>Il secondo, forse più subdolo, è perché va contro all’esaltazione dell’individuo propria dei nostri tempi in cui, con buona pace dei social network, la comunità sta sparendo. Se l’obiettivo del singolo è affermarsi come individuo, che sta meglio, è più felice, va in vacanza dove l’acqua è più blu, mostrarsi rotti, deboli, vulnerabili è controproducente.</p><p>Allora forse tutto quello che possiamo fare è mostrarci più vulnerabili. Io ci provo.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=613522bb9acb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The IT-less (tech) company]]></title>
            <link>https://medium.com/@nicoammendola/the-it-less-tech-company-ffc2e4a791d1?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/ffc2e4a791d1</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[company-culture]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Mon, 21 Aug 2023 18:41:07 GMT</pubDate>
            <atom:updated>2023-08-21T19:15:45.768Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Or on how any company can (and must) become a tech company by dropping its IT department altogether and investing in a solid IT culture.</em></p><p>My carrier path has been unusual. I worked in consulting (<a href="https://www.bpilearn.com/">BPI</a>), then co-founded 3 startups (Redooc, <a href="https://www.weschool.com/">WeSchool</a>, <a href="https://home.trainup.fit/">TrainUp</a>), now I’m a manager with <a href="http://www.basic.net/">BasicNet</a>, a 1.000 people multi-national company based in Torino, Italy.</p><p>The question that I constantly ask myself at work (and outside, too) is: what should I spend my time on? In other words, what is the task on which I should focus that maximizes the impact of my work?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e8v9jr_CCGS4jRCnMfMF2w.jpeg" /><figcaption><em>Image Credits: iStock/Grandfailure</em></figcaption></figure><p>As a nerd, and a software-builder the answer has to do with building software. But that’s not all.</p><p>I recently became aware that the most important job for someone in my position has little to do with building software and all to do with building culture.</p><p>I believe that any company wishing to last, wanting to play the “infinite game”, must be a tech company, or else it’ll disappear. But what does it mean exactly? Below are a few thoughts.</p><h3>No IT is the best IT</h3><p>What sets a tech startup or a big tech company apart from a traditional company? The former usually do not have an IT department. This does not mean that startups or big tech companies such as Google have no developers. On the contrary, they have plenty. Yet if you walked around the Google campus in Mountain View, you won’t find any IT building. At Google, everyone is — or should be — an IT person. Everyone in the company thinks of himself as a creator of technology.</p><p>It doesn’t mean that everyone is a coder or a software architect or a database administrator, of course; but it means that everyone firmly believes that:</p><ul><li><strong>Virtually anything can be automated;</strong></li><li><strong>Anything that can be automated should be automated.</strong></li></ul><h3>“Imagination is more important than knowledge”</h3><p>Some say if you can dream it you can build it. Unfortunately, very few people are capable of dreaming of it. Yet, we all dream — sometimes very imaginative dreams — at night in our beds. For some reason though, once we step into the office, we lose our creativity and prefer having a path to follow. Perhaps it’s the fear of being wrong, making a mistake, or being mocked by our colleagues.</p><p>Yet, how many times did we find ourselves doing something mechanical, and monotonous that we dream of automating it? What happens next? Most of the time nothing.</p><p>What would happen if every time anyone in the company spotted an opportunity for automation this became a task for a team of developers to develop a new feature or tweak an existing one? What if every glitch in any operational flow was treated as a bug in a software application?</p><p>It all starts with one step: imagining it.</p><h3>Build a factory, not a product</h3><p>Technology should be seen not just as “another product” of the company but as <em>the</em> product. To say it with Elon Musk’s words <em>“building a factory is ‘100 times’ as hard as building a car”</em>. This is true for Tesla and even truer for SpaceX.</p><p>To achieve this, the company should be structured accordingly. No IT department, enough imagination, sufficient software production capacity, and very close contact between operations and software makers.</p><p>The coders, those actually building the applications, should be everywhere and in constant contact with the people doing the “office work”. Just like a factory where the designers of the production line work hand in hand with those who keep the line running.</p><h3>Your colleagues are your customers</h3><p>In any relationship, we as humans, especially after a while, tend to take the good things for granted, while we’re great at remembering the bad ones and the pain. The same applies to our relationship with software.</p><p>You can have an application, at work or in your personal life, that works great 90% of the time but fails, or is hard to use, for the remaining 10% and you’d view this application as a faulty one. Even if it works for most things, those tasks for which it does not work will become a very tangible source of frustration.</p><p>This is also due to the fact that technology, like all things, must be sold. And we surely spend too little time selling technology internally. We should be telling stories, and helping people to understand the great advantages of what we’re building.</p><p>All hands sessions are useful. People need to be involved. When there’s no IT anymore, everyone is a maker of software. This does not mean that everyone codes, or that there’s no structured orderly process to develop a new feature. On the contrary, if you want extensive participation the rules must be extensive, strict, and clear. It simply means that everyone is involved in the process. Each for what he or she can contribute.</p><h3>Spread the word</h3><p>Lastly, it’s necessary that everyone in a position to influence people inside the company be intimately convinced of the strategic importance of software development; and everyone should make an active effort to spread the belief.</p><p>As far as my job at BasicNet is concerned, I’ve come to the realization that there are two key components to it:</p><ul><li>Contribute to the company culture in line with the company’s values</li><li>Understand when a piece of technology has become a commodity and avoid making the mistake of rebuilding the wheel myself, if I can buy a more performing, more reliable, and more flexible one.</li></ul><p>As a nerd, a developer, a software architect, and a product guy my excitement at work lies in pushing the boundaries of automation, not to replace people but to free them. This makes for happier employees and ultimately a faster, more reliable, and more flexible company, one that I would want to help thrive.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ffc2e4a791d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[42]]></title>
            <link>https://medium.com/@nicoammendola/42-9f754e2ac4d1?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/9f754e2ac4d1</guid>
            <category><![CDATA[politica]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Mon, 14 Aug 2023 10:08:49 GMT</pubDate>
            <atom:updated>2023-08-14T10:11:05.289Z</atom:updated>
            <content:encoded><![CDATA[<p>Purtroppo non è solo – ricordando Douglas Adams – la risposta alla domanda fondamentale sulla vita, l’universo e tutto quanto.</p><p>Quarantadue è il numero di persone che si sono uccise nelle carceri italiane, dall’inizio dell’anno a oggi. Due nel tremendo carcere di Torino solo negli ultimi giorni. L’ultima una donna di poco più di quarant’anni, con tutta una vita davanti. Nel 2023.</p><p>Come è possibile che, mentre testiamo razzi nella speranza di raggiungere Marte, costruiamo auto che si guidano da sole e discutiamo di reddito universale, in Italia, l’anno dopo il record del 2022 (84 suicidi in carcere), più di una persona a settimana abbia preferito uccidersi che rimanere in carcere.</p><p>Mentre parlottiamo, sconclusionati, con argomentazioni anacronistiche e spesso bigotte, della riforma radicale di cui necessita da anni – forse decenni – il nostro sistema penale, le persone di cui dovremmo, come comunità, prenderci cura si ammazzano.</p><p>Quanto è buio e vicino l’orizzonte di chi decide di farla finita? Perché non parliamo di come riaccendere un lumino di speranza nel cuore di chi è costretto a sognare la vita che non è stata, o forse sì, e che tornerà, o forse no, da dietro le sbarre? Perché non parliamo di come trasformare le sbarre in trampolini? Perché non discutiamo di come trasformare la professione del secondino, e di tutti gli operatori delle carceri, da guardiani a maestri?</p><p>Ad Alcatraz, nell’America ispirazione di un occidente miope, c’è una lavagna su cui i visitatori sono invitati a scrivere la ragion d’essere di un carcere. L’anno scorso ci sono stato. Solo una persona, dalla calligrafia ordinata, aveva scritto che “Prisons should reform ppl in theory”. Non si parla di riabilitazione, di istruzione, di reinserimento.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wPqU1dtRJuWrHBDW_bKuGg@2x.jpeg" /></figure><p>Forse invece di certezza o inasprimento delle pene, sarebbe più utile – e interessante – parlare del perché puniamo, non per punire ma per riabilitare. Se non per una ragione morale, anche solo e più banalmente per convenienza, senza alcuna contraddizione con i principi di utilità capitalistica tanto cari ai più.</p><p>Un condannato riabilitato e reinserito nella società conviene. Costa meno e ha maggiori possibilità di contribuire al benessere collettivo.</p><p>Invece no, lasciamo che uomini e donne si ammazzino, nella speranza di lanciare un ultimo grido d’aiuto, se non per sé per chi resta. Poi prendiamo quel grido, figlio di tutte le forze rimaste, segno del fallimento di un intero sistema, e ci scriviamo un trafiletto, nelle lettere al direttore.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9f754e2ac4d1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[3 simple uses of AI (LLMs) in software development]]></title>
            <link>https://medium.com/@nicoammendola/3-simple-uses-of-ai-llms-in-software-development-a2e1ee634e08?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2e1ee634e08</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[llm]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Mon, 01 May 2023 15:39:28 GMT</pubDate>
            <atom:updated>2023-05-01T15:39:28.687Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pjvE2zLXSBCx_OsXlveoYQ.png" /></figure><p>Amid the debate around whether or not AI is truly a revolution — like the internet— or just another hype in the quest for the future, here are three easy, very valuable things that AI can do for you if you’re in software development.</p><p>If you’ve ever worked on a piece of software, an app, or anything written in a language that is not plain English, you know how important it is to have some guidance prior to diving into it to decipher and improve it.</p><p>As we all should know by now, what we generally refer to when talking about AI these days are so-called Large Language Models or LLM for short.</p><p>An LLM is basically, a very intricate (I’d say obscure), corpus of code that is very good at one thing: predicting the next word in a sentence. It is so good at doing it that when it does it it feels as if the thing was reasoning.</p><p>In some LLMs, such as ChatGPT, this capability is very advanced in many languages. It is probably most advanced in English, but it is surely very advanced in programming languages too. Also, given that programming languages are much more rigid than spoken languages, the ability of the LLM in this “guess-the-next-word” game is probably even more developed and reliable.</p><p>So without further ado, here are the 3 examples of things you can task your LLM of choice with doing.</p><h3><strong>Review/refactor</strong></h3><p>Give it a piece of code and ask it to make it better. In the example below I structured the following prompt “Can you improve this code file?” and then pasted the entire file in the prompt input.</p><pre>import { client, q } from &#39;../config/db&#39;;<br>export const getAllProducts = client<br>  .query(q.Paginate(q.Match(q.Ref(&#39;indexes/all_products&#39;))))<br>  .then(response =&gt; {<br>    const productRef = response.data;<br>    const getAllDataQuery = productRef.map(ref =&gt; {<br>      return q.Get(ref);<br>    });<br>    return client.query(getAllDataQuery).then(data =&gt; data);<br>  })<br>  .catch(error =&gt; console.error(&#39;Error: &#39;, error.message));<br><br>export const createProductItem = name =&gt;<br>  client<br>    .query(<br>      q.Create(q.Collection(&#39;products&#39;), {<br>        data: {<br>          name<br>        }<br>      })<br>    )<br>    .then(ret =&gt; ret)<br>    .catch(error =&gt; console.error(&#39;Error: &#39;, error.message));<br><br>export const deleteProductItem = productId =&gt;<br>  client<br>    .query(q.Delete(q.Ref(q.Collection(&#39;products&#39;), productId)))<br>    .then(ret =&gt; ret)<br>    .catch(error =&gt; console.error(&#39;Error: &#39;, error.message));</pre><p>Here’s how ChatGPT responded</p><p><em>While the code you provided is clear and follows good practices, there are a couple of things that could be improved to make it more robust and maintainable:</em></p><p><em>1. </em><strong><em>Error Handling</em></strong><em>: Instead of just logging the error message, you could throw an error to allow the calling function to handle it. This gives more control to the caller and makes your functions more predictable.</em></p><p><em>2. </em><strong><em>Code Duplication</em></strong><em>: There’s some repetition in your error handling that could be abstracted into a separate function.</em></p><p><em>3. </em><strong><em>Return Values</em></strong><em>: For `createProductItem` and `deleteProductItem`, you don’t need to use `then(ret =&gt; ret)`. The promise returned by `client.query` will automatically resolve to the return value.</em></p><p>And then it provided the refactored code:</p><pre>import { client, q } from &#39;../config/db&#39;;<br><br>const handleQuery = async (query) =&gt; {<br>  try {<br>    return await client.query(query);<br>  } catch (error) {<br>    console.error(&#39;Error: &#39;, error.message);<br>    throw error;<br>  }<br>};<br><br>export const getAllProducts = async () =&gt; {<br>  const response = await handleQuery(q.Paginate(q.Match(q.Ref(&#39;indexes/all_products&#39;))));<br>  const productRef = response.data;<br>  const getAllDataQuery = productRef.map(ref =&gt; {<br>    return q.Get(ref);<br>  });<br>  return await handleQuery(getAllDataQuery);<br>};<br><br>export const createProductItem = (name) =&gt; {<br>  return handleQuery(<br>    q.Create(q.Collection(&#39;products&#39;), {<br>      data: {<br>        name,<br>      },<br>    })<br>  );<br>};<br><br>export const deleteProductItem = (productId) =&gt; {<br>  return handleQuery(q.Delete(q.Ref(q.Collection(&#39;products&#39;), productId)));<br>};</pre><p>And explained what it did:</p><p><em>In this refactored version, I’ve introduced an `async/await` syntax to make the promise handling more readable and intuitive. I’ve also added a `handleQuery` function to centralize the error handling logic. Please note that this code assumes that the error should be thrown and handled by the calling code, which may not always be the case. Adjust error handling according to your specific use case.</em></p><h3><strong>Comment/explain</strong></h3><p>I then asked it to integrate the refactored file with comments. Here’s the result.</p><pre>// Import the necessary modules from the db configuration file<br>import { client, q } from &#39;../config/db&#39;;<br><br>// Function to handle the database queries and errors<br>// This function accepts a query, executes it, and returns the result<br>// If an error occurs during the execution of the query, it logs the error message and then throws the error<br>const handleQuery = async (query) =&gt; {<br>  try {<br>    return await client.query(query);<br>  } catch (error) {<br>    console.error(&#39;Error: &#39;, error.message);<br>    throw error;<br>  }<br>};<br><br>// Function to get all products<br>// This function first gets the references of all products using the &#39;all_products&#39; index<br>// Then it retrieves the actual data of all products using their references<br>// If an error occurs during the execution of the queries, it is handled by the handleQuery function<br>export const getAllProducts = async () =&gt; {<br>  const response = await handleQuery(q.Paginate(q.Match(q.Ref(&#39;indexes/all_products&#39;))));<br>  const productRef = response.data;<br>  const getAllDataQuery = productRef.map(ref =&gt; {<br>    return q.Get(ref);<br>  });<br>  return await handleQuery(getAllDataQuery);<br>};<br><br>// Function to create a new product<br>// This function accepts a name and creates a new product with that name in the &#39;products&#39; collection<br>// If an error occurs during the execution of the query, it is handled by the handleQuery function<br>export const createProductItem = (name) =&gt; {<br>  return handleQuery(<br>    q.Create(q.Collection(&#39;products&#39;), {<br>      data: {<br>        name,<br>      },<br>    })<br>  );<br>};<br><br>// Function to delete a product<br>// This function accepts a product ID and deletes the corresponding product from the &#39;products&#39; collection<br>// If an error occurs during the execution of the query, it is handled by the handleQuery function<br>export const deleteProductItem = (productId) =&gt; {<br>  return handleQuery(q.Delete(q.Ref(q.Collection(&#39;products&#39;), productId)));<br>};</pre><h3><strong>Document</strong></h3><p>Finally, I tasked the model to write a brief paragraph to add to the documentation of the solution, using markdown, to explain what the index.js file that it had just refactored does.</p><p>Here’s the output.</p><pre>## `index.js` - Database Operations<br><br>The `index.js` file located in our project root is responsible for managing the core database operations in our application. It includes functions to get all products, create a new product, and delete a product from our database.<br><br>### Functions<br><br>1. **`handleQuery(query)`**: This is an internal function that isn&#39;t exported from the module. It accepts a database query, executes it, and returns the result. If an error occurs during the execution of the query, it logs the error message and then throws the error. This function is used to handle the query execution and error logging for all other functions in this file.<br><br>2. **`getAllProducts()`**: This function retrieves all products from our database. It first gets the references of all products from the &#39;all_products&#39; index, then retrieves the actual data of each product using their references. The data of all products are returned as an array.<br><br>3. **`createProductItem(name)`**: This function creates a new product in our &#39;products&#39; collection. It accepts a `name` parameter, which is used as the name of the new product. The function returns the newly created product.<br><br>4. **`deleteProductItem(productId)`**: This function deletes a product from our &#39;products&#39; collection. It accepts a `productId` parameter, which is the ID of the product to delete. The function returns the deleted product.<br><br>### Error Handling<br><br>All functions in this file use the `handleQuery` function for executing database queries. This centralizes the error handling logic, making the functions more maintainable and predictable. If an error occurs during the execution of a query, it is logged and then thrown. This allows the calling code to handle the error in a way that suits the specific requirements of the application.<br><br>Please note that this file relies on the `client` and `q` modules from the `db` configuration file. Make sure to properly configure these modules according to your database setup.<br></pre><h3><strong>Conclusions</strong></h3><p>While these three things can seem trivial, these are tasks that can be very easily automated and that can be run without the need for any sophisticated or customized prompting.</p><p>In the example used we just fed one single and very simple file to the model, but one could of course feed it an entire application or even multiple applications that work inside the same ecosystem.</p><p>There are clearly potential security risks that need to be evaluated and managed but to me the power of these models for anyone crafting software is unmatched.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2e1ee634e08" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[La guerra invisibile]]></title>
            <link>https://medium.com/@nicoammendola/la-guerra-invisibile-10a38c984314?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/10a38c984314</guid>
            <category><![CDATA[italia]]></category>
            <category><![CDATA[democracy]]></category>
            <category><![CDATA[china]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Mon, 14 Sep 2020 13:08:21 GMT</pubDate>
            <atom:updated>2020-09-14T13:09:26.792Z</atom:updated>
            <content:encoded><![CDATA[<p>Chissà quando ci accorgeremo che siamo (da anni) in guerra. In guerra contro un nemico spietato che ragiona con un orizzonte temporale di almeno un ordine di grandezza superiore a quello dei nostri governi, quindi anche per questo difficilissimo da battere.</p><p>Xi Jinping, imperatore a vita, da una parte. <br>I vari Trump, Macron, Merkel, Johnson, preoccupati del risultato delle prossime elezioni, dall’altra.</p><p>Il treno della guerra commerciale è passato. La classe media cinese genera ormai abbastanza domanda interna da rendere cosa di poco conto, le battaglie sui dazi.</p><p>L’unica vera speranza, e quindi l’unica minaccia per l’impero, sono i giovani cinesi. Solo loro potrebbero rallentare e forse arrestare la folle corsa. Ma potrebbero davvero, considerati il sistema educativo, la censura, l’intelligence e la forza repressiva del partito? E anche potessero, vorrebbero? Guardando lo stato in cui versano le nostre democrazie più progredite non viene certo molta voglia di replicarle. Incerte, incapaci di agire da sole e di concerto, impotenti di fronte all’allargarsi inesorabile di quel divario tra ricchi e poveri che è la nostra piaga.</p><p>Abbiamo fatto, senza far nulla, un errore enorme: dare per scontata la democrazia, la nostra grande conquista come popolo della Terra.</p><p>Ci vuole coraggio, bisogna (ri)cominciare a prendersene cura, ritrovando un entusiasmo che va contro la nostra indole di facilmente annoiati da tutto ciò che non è nuovo. Bisogna ricominciare ad accudire questa povera vecchina. Perché sarà lei, ringiovanita, aggiustata, ripensata, accudita, rinnovata, amata anche se oggi dimenticata, a porgerci la mano per uscire dalla palude.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10a38c984314" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Giù le mani dalle statue]]></title>
            <link>https://medium.com/@nicoammendola/gi%C3%B9-le-mani-dalle-statue-1ac7781271b7?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ac7781271b7</guid>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Thu, 11 Jun 2020 13:27:52 GMT</pubDate>
            <atom:updated>2020-06-26T10:02:55.964Z</atom:updated>
            <content:encoded><![CDATA[<h4>Negli ultimi giorni cadono statue. Quando cade una statua qualcosa sta cambiando, non sempre per il meglio.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QBy2cCLN17QVT29BWPGKdg.jpeg" /><figcaption>Illustrazione di Martina Antoniotti (aka @amaranto sull’Instagram)</figcaption></figure><p>L’ultima che ricordo cadere fu quella di Saddam Hussein a Baghdad. Era la primavera del 2003. L’hanno tirata giù gli Americani. Rimpiazzata in breve tempo dalla bandiera a stelle e strisce. L’Iraq liberato. Il peggio alle spalle. Viva la democrazia! Viva i pollici sporchi d’inchiostro!</p><p>Sono passati 17 anni e dubito che in Iraq si stia particolarmente meglio, ovviamente.</p><p>Saddam era un dittatore, un guerriero sanguinario, un sovversivo. La non conformità del sistema sociale iracheno con quello occidentale e le mai trovate armi batteriologiche ne hanno fatto preda facile per i poliziotti della plutocrazia. Quella statua era il simbolo di un ostacolo sulla strada del capitalismo imperialista nonché l’icona di un criminale: andava tirata giù.</p><p>Se riconosciamo nella democrazia una delle maggiori conquiste dell’umanità, siamo d’accordo che <strong>non c’è spazio per le statue dei dittatori</strong>. Punto.</p><p>Nei giorni scorsi però, sono state vandalizzate anche, tra le altre, una statua di Cristoforo Colombo, negli Stati Uniti, e alcune di Churchill, in Gran Bretagna. Per organizzarsi e coordinare i prossimi interventi, questi rivoluzionari della domenica, hanno anche redatto una “<a href="https://news.sky.com/story/george-floyd-protests-activists-draw-up-hit-list-of-uk-statues-they-want-removed-12004101">hit list</a>” con i prossimi obiettivi.</p><p>Nella lista ci sono anche:<br>• <strong>Nelson</strong>, l’ammiraglio che di impedì a Napoleone di conquistare la Gran Bretagna e al contempo diede il colpo di grazia alla conquista spagnola del mondo; <br>• <strong>Drake</strong>, il navigatore a cui è intitolato il passaggio all’estremo sud del continente americano, che per primo ha circumnavigato il mondo;<br>• <strong>Cromwell</strong>, l’uomo che sfidò la monarchia inglese, si batté per la repubblica e fece decapitare re Carlo I, abolendo la monarchia e istituendo il Commonwealth repubblicano. <br>Poi anche altre statue di Cristoforo Colombo, per non farsi mancare nulla.</p><p>La loro colpa? Aver preso parte agli affari legati agli schiavi. Mica roba da poco.</p><p><strong>Tirare giù una statua significa mettere in discussione il posto del soggetto nella Storia</strong>. Se decapito Colombo per me su quel piedistallo Colombo non ci deve stare.</p><p>In base a cosa ragioni chi tira giù le statue — ammesso che lo faccia — non è dato saperlo. Immagino lo faccia in base a un sistema di valori, un quadro etico e morale contemporaneo, proprio. Forse l’unico che conosce…</p><p><strong>E qui casca l’asino.</strong> Che Cristoforo Colombo e i suoi compagni di viaggio, sebbene in missione per conto di Dio, non fossero dei santi non è una novità. Hanno discriminato, maltrattato, conquistato, abusato. Hanno esagerato. <br>Ma hanno sbagliato? Hanno senza dubbio compiuto azioni riprovevoli, che oggi nessuno esiterebbe a giudicare come sbagliate. Ma è giusto dire che — nel sistema di valori di allora — fossero sbagliate?</p><p>Per rispondere dovremmo conoscere a fondo il sistema di valori dell’epoca e ricordarci nella sua analisi di due cose: a) i sistemi di valori morali ed etici non sono statici — per fortuna! — e b) i<strong> sistemi di valori sono figli degli uomini, ma a loro volta gli uomini sono figli dei sistemi di valori delle loro società.</strong> Bisogna quindi essere cauti prima di mettersi la toga.</p><p>Era giusto che Drake nelle sue navi ci mettesse (anche) gli schiavi?</p><p>Oggi diciamo di no. Ma il suo posto nella storia Drake se l’è già conquistato nel 1500. E forse il nostro compito oggi non è metterlo in discussione, quanto comprendere come e perché se lo sia conquistato, quel posto, senza relativismi morali e inutili revisionismi. <strong>Forse dovremmo anche chiederci se Drake, come Colombo prima di lui, avesse gli strumenti per valutare le sue azioni così come le valuteremmo noi oggi. </strong>Io credo di no.</p><p>Maltrattare il diverso è un atto riprovevole e sbagliato. Non ci piove. <strong>È giusto condannare chi si è macchiato di questi crimini in un momento in cui questi crimini non solo non erano considerati crimini anzi erano incoraggiati e sostenuti, perfino dai rappresentanti di Dio sulla Terra?</strong> Forse. O forse no.</p><p><strong>Le statue vanno lasciate dove sono</strong>. E bisogna farlo principalmente per due motivi: a) Colombo ha fatto anche qualcosa di buono, se il mondo viaggia alla velocità a cui ha viaggia lo dobbiamo anche a chi, come lui, ha osato far rotta oltre le colonne d’Ercole, e b) perché <strong>le atrocità</strong> <strong>non vanno</strong> <strong>rimosse dalla Storia</strong> ma scritte a caratteri cubitali e ricordate continuamente. E dobbiamo allarmarci ogni volta che qualcuno ci invita a dimenticare.</p><p>Certo, ragionare così è rischioso. <strong>Se diamo per scontato che il sistema etico e morale cambi nel tempo apriamo alla possibilità che qualsiasi atto sia giustificabile</strong>. Tutto quello che serve è un sistema etico di riferimento che lo permetta. Questo è uno dei motivi per cui quando si ragiona di questi argomenti serve approfondimento sul contesto. Approfondimento che costa tempo e fatica, ed è quindi merce sempre più rara.</p><p>Poi <strong>serve un accordo sul termine di paragone per la valutazione morale delle azioni</strong>. Cioè bisogna identificare e condividere gli strumenti e la scala con cui misuriamo. Non so quale sia lo strumento giusto per “codificare” il sistema etico e morale di riferimento di una società in un dato momento nel tempo. <strong>Quello che più gli si avvicina è la Legge, con la L grande</strong>.</p><p>Semplificando, senza illuderci che tutto ciò che è immorale sia riconosciuto come sbagliato nei codici, forse dovremmo cominciare a chiederci se le atrocità di Drake, Nelson, Cromwell e Colombo fossero atti criminali, quindi in violazione delle leggi dell’epoca. E — visto che non lo erano — forse potremmo anche riconoscerle come funzionali al cambiamento — sempre tardivo — nella Legge delle nostre società che è seguito.</p><p><strong>Sono felice che Colombo, Nelson, Drake e Cromwell siano passati di qua e che abbiano fatto quello che hanno fatto.</strong> Sono felice che si siano trafficati schiavi per secoli? Ovviamente no, ma sono nato nel 1988 e non ho fatto granché, e sarei piuttosto arrogante se mi ergessi a loro giudice.</p><p><strong>Lascerei i piedistalli e le statue dove sono.</strong> Non ho alcuna stima e poco rispetto per chi invece oggi sulle statue ci piscia, le imbratta o le getta nei fiumi. Sarebbe di gran lunga più utile si leggesse un libro, uno qualsiasi, meglio se di storia.</p><p>Poi c’è chi imbratta le statue di Churchill. A costoro è utile ricordare solo una cosa: <strong>se non ci fosse stato Churchill questo mondo, in cui tu imbratti le statue, non esisterebbe</strong>.</p><p>Ma per saperlo — di nuovo — serve un libro di storia.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ac7781271b7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Covid-19 in Italy: the days ahead of us in Italy]]></title>
            <link>https://medium.com/@nicoammendola/covid-19-in-italy-the-days-ahead-of-us-in-italy-84e280f93308?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/84e280f93308</guid>
            <category><![CDATA[italy]]></category>
            <category><![CDATA[covid19]]></category>
            <category><![CDATA[epidemic]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Sun, 22 Mar 2020 15:37:04 GMT</pubDate>
            <atom:updated>2020-03-22T17:57:53.523Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Disclaimer: I’m not an epidemiologist nor a scientist. I’m just an Italian citizen who’s passionate about numbers and is trying to make sense of what we are going through, by communicating the data we have to the best of his ability with the hope of doing good in raising awareness both in Italy and elsewhere.</em></p><p>Here in Italy, we have been in lockdown for over 10 days. <strong>This is a brief analysis that departs from one key concept, I called “relative strength” of the epidemic, to estimate probable future developments of the Covid-19 epidemic in Italy. </strong>One of the goals of the article is to highlight the importance of social distancing.</p><p>In the analysis I took a rather “linear” approach. I did not take into consideration “shocks” such as an overwhelmed public health system or anything of that kind. The only key assumption I made is the continuous steady decline of the relative strength of the epidemic, which is greatly dependent on the successful enforcement of social distancing measures. Yet the estimates I came to are shocking, and I am grateful to anyone willing to point out flaws in my reasoning.</p><h4><strong>The “Relative Strength” of the Covid-19</strong></h4><p>What is “Relative Strength”? It’s a simple ratio: <strong>the number of new cases (in a day) over the number of total cases</strong>. This ratio can, of course, be presented as a percentage. What does this ratio tell us? The way I think of it is the “power” of contagious people, so called “spreaders”, to do damage by spreading the disease and infecting other people.</p><p>Another way you can think of it is, over the course of any two days:</p><ul><li>Day 0: we have 100 infected people. These 100 people roam around and infect others. Let’s say that in one day they infect 10 new people. The relative strength of the epidemic is 10 over 100, or 10%. This can also be read as: 1 out every 10 infected people has managed to infect another 1.</li><li>Day 1: we have now 110 infected people. The original 100 plus the 10 newly infected on Day 0. If the epidemic had the same strength of the day before, the 110 people should infect 11 new people, which is equal to 10% of 110. If they infect less than 11 new people, the relative strength of the epidemic is lower than the day before. And this would clearly be a good sign.</li></ul><p>As time goes by, the total number of people who can infect others grows. This means that, all else equal, the illness gains strength in absolute terms. However, if the number of newly infected people in a day over the total number of infectious people decreases, this means that the epidemic is losing<em> relative</em> strength. In other words, if — as the number of spreaders grows — less people become infected, the efficiency of the spreading mechanism is decreasing.</p><h4><strong>Relative Strength in Italy over the last 20 days</strong></h4><p>What we have been witnessing in Italy in the last 20 days is the epidemic losing its <em>relative</em> strength. How much so? You can clearly see it in the graph below. <strong>The epidemic is losing approximately 7% of its relative power every day</strong>. This is the most tangible effect of the so-called social distancing we are (or should be) all committing too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*wNk44gdNrifJO2xL" /><figcaption>What I call “Epidemic Relative Strength”, or the number of newly infected people in a day as a percentage of total active “spreaders”. It indicates the ability of infectious people to spread the disease to others.</figcaption></figure><blockquote><strong>Key takeaway</strong>: social distancing measures are probably working as we are witnessing a decreasing over time of the “relative strength” of the Covdi-19 epidemic.</blockquote><h4><strong>Will it continue to lose strength?</strong></h4><p>Very simply put: it probably will, at one condition. That one condition being: IF we manage to follow our Government’s guidelines and are able to abide to strict social distancing.</p><h4><strong>For how long should social distancing be enforced?</strong></h4><p><strong>If the decline in relative strength continued on the same path</strong>, that is if it continued declining by approximately 7% each day, <strong>the epidemic would have lost all its strength in 15 days from today</strong>. This means that around April the 5th, there will be no new contagions. If this happened, at the beginning of April we would have approximately 100.000 officially reported Covid-19 cases, as shown in the two charts below.</p><blockquote><strong>Key assumption of the following estimates</strong>: relative strength of the epidemic keeps on declining by 7% each day</blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*w9HPrrtdx8e1ECLi" /><figcaption>New official cases by day in Italy, in blue actual numbers, in red estimates calculated using projected relative strength (see above)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*xcJzUNxbng7KiebV" /><figcaption>Cumulated active cases in Italy, just another way of visualising the data in the chart above</figcaption></figure><p>If these estimates were somewhat accurate, we would have:</p><ul><li>Peak in contagions should be reached around the 25th of March, with approximately 5.000 new contagions per day;</li><li>Decline from the 25th of March onwards, reaching 0 new daily contagions in approximately 10 days, around the 3rd of April;</li><li>Total number of active cases around the 3rd of April of around 100.000</li></ul><p><strong>Note</strong>: even if the <em>official </em>number is not the <em>real </em>number of cases, this has no impact on the analysis of this article, given that the number of <em>official</em> cases is assessed consistently over time.</p><h4><strong>How do these estimates compare to the Province of Hubei, in China?</strong></h4><p>In the Province of Hubei the peak was reached around 24 days after the start of the epidemic and it took approximately another 20 days for new cases to drop to around 0. So I’m being optimistic when I estimate that it will take Italy around half as many days.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*fsDwGVgubLlvUcFi" /><figcaption>Comparison of contagions between Province of Hubei (around 58M people, more densely populated than Italy) and Italy (around 60M people), in blue actual numbers for Italy, in red estimates calculated using “relative strength” (see above)</figcaption></figure><h4><strong>Impact on deaths</strong></h4><p>Unfortunately deaths are “only” a consequence of contagions. A consequence that manifests itself with <em>n</em> days of delay. Where <em>n </em>is the difference in days from contagion to death, for those who do not make it.</p><p>From what I understood so far there are no easy questions when it comes to analyzing epidemics, let alone a pandemic. Again: this is not my job, I’m not an epidemiologist, nor a scientist, I’m just a person trying to make sense of the numbers we see everyday.</p><p>To understand how the trend of contagions is reflected, days later, on the trend of deaths, we need a key number, the <em>n</em> number of days I mentioned earlier. We need to know how many days it takes a patient, who is not going to make it, to lose his battle.</p><p>The only somewhat reliable figure I found is contained in <a href="https://www.thelancet.com/journals/lancet/article/PIIS0140-6736(20)30566-3/fulltext">this study conducted on Chinese patients</a>. It indicates approximately 18.5 days from contagion to death. I assumed Chinese people are stronger than we Italians are, since — on average — they are much younger. Assuming this “contagion-to-death” lag is 7 days, we would be looking at a peak in deaths 10–12 days from today, around the 3rd of April. The number 7 is a “guesstimate”, it could be 4, it could be 20. What this number tells us is how much down the line of time we should look for the impact of contagions on deaths.</p><p>Since we may be reaching the peak in contagions these days, the smaller this number the better. If this number were 7 that would mean that we could expect the daily death toll to rise for 7 days after we reached contagion peak. If this number were 20, we should be expecting the death toll to rise for 20 days, before it’ll eventually start to slow down.</p><h4><strong>How many deaths would we be looking at?</strong></h4><p>Anyone wanting to come up with a somewhat “reasonable” estimate of this number, ought to make some assumptions. Here are the ones I made.</p><blockquote><strong>First key assumption to estimate number of deaths: </strong>number of daily deaths continues to increase at a rate of 15% per day, which is a bit less than what it’s been doing for the last 7 days;</blockquote><blockquote><strong>Second key assumption to estimate number of deaths: </strong>once it reaches the peak (around the 3rd of April), the number decreases at the same speed at which contagions would have been decreasing.</blockquote><p>Under these assumptions <strong>we would be looking at a number of around 50.000 deaths</strong>, with a daily count in the hundreds all the way up to the last days of the first half of April. See charts below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JgX6cy11hzT416qE" /><figcaption>Number of Deaths by day, with a time difference between contagion and death of 7 days</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Ggsx3q1fJKikzpih" /><figcaption>Total number of deaths, again under the assumption that the deaths we are recording today are those of patients who, on average, got sick 7 days ago</figcaption></figure><h4><strong>Conclusion</strong></h4><p>A very basic look at these numbers paints a frightening picture of what could be ahead of us. Please take care of yourself and of those around you and remember that <strong>the real damage most of us can do is infecting others</strong>, since for the vast majority of us Covid-19 is not a killer disease. <strong>Staying home and following guidelines is an act of civilization and altruism.</strong></p><p>Let’s remember Margaret Mead’s words when she said the first sign of civilization was a healed femur. The evidence of compassion is what defines us as humans. The ability to take care of the sick and wounded, and not letting a broken leg kill us, as it would for any other animal, is what sets up apart.</p><p>Everything else will take care of itself. Or will it not? Here’s where the ethical debate begins.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=84e280f93308" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Did we defeat time?]]></title>
            <link>https://medium.com/@nicoammendola/did-we-defeat-time-4d4ccc831429?source=rss-61c1109726f2------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d4ccc831429</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[time]]></category>
            <category><![CDATA[space]]></category>
            <category><![CDATA[tech]]></category>
            <category><![CDATA[meaning-of-life]]></category>
            <dc:creator><![CDATA[Nicolò Ammendola]]></dc:creator>
            <pubDate>Fri, 27 Dec 2019 11:01:13 GMT</pubDate>
            <atom:updated>2019-12-27T11:01:59.765Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zyGerh30u3v8pOCIYtQNiA.png" /></figure><p>Capitalism and technological progress are not always the fairytale they teach us in schools. They have drawbacks. Some more concrete, some more abstract. One of these less obvious ones is the illusion that time can be beaten with technology.</p><p>The mantra of the race for efficiency is to make more out of less, less resources but also less time. We go from Rome to Milan in less than three hours without leaving the ground. We will get there in only 25 minutes if the pneumatic postal inspired system to shoot people around, called Hyperloop, ever gets build. The new iPhone cover is delivered to your front door by tomorrow morning with Prime, in just two hours with Prime Now, in only an hour with Prime Now and a few extra euros. You download a movie in 15 seconds, with a 300 megabit/s connection. Your new bank account will be born through an app in just a few taps. Your next startup is online in a matter of hours and zero lines of code. You feel alone and want to meet someone? Fire up Tinder!</p><p>It’s all very beautiful.</p><p>Where’s the rip off? The speed with which we reach our goal (we should still wonder if the destination is the actual goal) deludes us that the journey is simple and deemed to getting simpler. We believe that difficult things have become easy only because it takes less time to do them. Every possible thing seems near, or nearer at least, not just within reach but within our reach.</p><p>How long does it take to sleep with someone you don’t know? A few well timed lines, a drink or two, it depends. How long to start a company? A few months, two dollars and you’re ready to go, we are all startuppers. How much to change your mind again? Just another message, an excuse, whatever.</p><p>Then we are surprised that the things we build do not last, that nothing of what we built overnight is still standing. We are often caught in the “missed opportunity trap”: it looks so achievable that what a wasted opportunity would it be if we did not go for it.</p><p>We have become very quick to think, to write, to love, to build. But then everything we so quickly build, at the first gust of wind, trembles, falters and often, just as quickly, disappears.</p><p>Our patience is deteriorated by the misuse of technology and the distance we put between ourselves and nature. We have come to believe that patience is optional, that we can very well strive without it. Unfortunately we can’t. You still have to wait an entire year before the field can be harvested again, it still takes nine months to give birth to a child, a lifespan to build a company, years to write a poem, thousands of hours to get to know someone.</p><p>We strive to build something that will outlast us because we can’t stand the undeniable truth of death. We long for a sense of purpose that often comes from building things that will outlive us: a son, a song, a company, a painting. But in the rush to build we just keep on sketching. Because we don’t know what to bet on, nor which relationships to invest our time in. We have no time to waste. So, in an effort to diversify risk, we often throw it all away.</p><p>Instead, perhaps, we must slow down. And very much so. Because one must go slowly to go far. Napoleon used to suggest to his staff to dress him slowly, because he was in a hurry. Blue Origin, Jeff Bezos’ venture into space, adopted the latin motto <em>gradatim ferociter</em>, step by step ferociously, to keep as a light in the night of perhaps the hardest of human endeavours: the conquest of space.</p><p>In the illusion of having defeated time we are defeating ourselves. We devote millions of neurotic fractions of time to building things that unravel the very moment we turn away, and live in terror of turning around and not even seeing our footprints. We must foster our patience, perhaps our must valuable resource, for only through properly and cautiously investing our time we will achieve anything of lasting value.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4d4ccc831429" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>