<?xml version="1.0" encoding="utf-8"?><feed xmlns="http://www.w3.org/2005/Atom" ><generator uri="https://jekyllrb.com/" version="4.3.3">Jekyll</generator><link href="https://dellacorte.me/feed.xml" rel="self" type="application/atom+xml" /><link href="https://dellacorte.me/" rel="alternate" type="text/html" /><updated>2026-07-12T20:34:42+01:00</updated><id>https://dellacorte.me/feed.xml</id><title type="html">Andrea Della Corte</title><subtitle>Organisational coach &amp;amp; aspiring expert</subtitle><author><name>Andrea Della Corte</name></author><entry><title type="html">What does a 1:1 actually need to produce to be worth the time?</title><link href="https://dellacorte.me/essays/worth-the-time/" rel="alternate" type="text/html" title="What does a 1:1 actually need to produce to be worth the time?" /><published>2026-07-04T00:00:00+01:00</published><updated>2026-07-04T00:00:00+01:00</updated><id>https://dellacorte.me/essays/worth-the-time</id><content type="html" xml:base="https://dellacorte.me/essays/worth-the-time/"><![CDATA[<p><em>This is a work in progress, published early on purpose. See <a href="#request-for-comments">Request for comments</a> at the end.</em></p>

<p>I have run thousands of 1:1s over my career. Almost everyone in an organisation has one or two of them standing on their calendar, and yet very few people would say they are genuinely good at them. That gap is what I find interesting. Getting the best out of a recurring half hour with another person is a real skill, and quietly honing it has been one of the pleasures of my working life. It is also a puzzle I have never quite finished solving, which is why I wanted to write this down.</p>

<p>My calendar looks like a mess because of it. Every 1:1 runs a bit differently, tuned to whoever I’m sitting across from, and I’m always tweaking the format as I get to know someone better. I look forward to these conversations. There’s usually an adjustment period where neither of us has quite found the right shape for the time, and then it clicks, and after that they become some of the most valuable half hours in my week.</p>

<p>After enough of them, I have landed on a simple idea. Everything good about a 1:1 rests on caring about the person on the other side of the table. The rest, the agendas, the cadence, the format, is machinery built on top of that. But the machinery matters, because caring on its own does not tell you what to do with the next thirty minutes. What does is knowing which phase the relationship is in.</p>

<h2 id="can-you-build-the-caring">Can you build the caring?</h2>

<p>If everything rests on caring about the person across the table, the obvious worry is what happens with someone you did not choose and do not naturally warm to. I do not think a good manager gets to opt out of that. Caring about your team is part of the work, not a lucky accident of chemistry. A good manager can develop a real sense of appreciation for every member, find what motivates each of them, and invigorate them.</p>

<p>And it can start quickly. You do not need years of shared history to build a working relationship. You need aligned objectives, transparency about where you each stand, and a few principles held in common: hard work, belief in what you are doing, a willingness to be straight with each other. Get those in place early and the caring has something to grow from. It is less a feeling you wait for than a thing you cultivate on purpose.</p>

<p>It helps to stop judging a 1:1 session by session. The conversation where someone finally tells you they are thinking of leaving, or that a strategic project is quietly failing, looks identical on the calendar to the forgettable one before it. What you can actually read is something slower: where the relationship is, and whether the 1:1 is doing the work of that stage. A get to know you conversation in the first month is the meeting doing its job. The same conversation in month eighteen is a sign something has gone wrong.</p>

<p>In practice a 1:1 moves through four phases, and each one is for something different:</p>

<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>caring runs through all of it
          │
          ▼
   1 · GET TO KNOW  (trust)
   informal, no agenda
          │
          ▼
   2 · SHARE CONTEXT  (momentum)
   principles, challenges,
   ways of working
          │
          ▼
   3 · SHARED AGENDA  (structure)
   items added ahead,
   prioritised together
          │
          ▼
   4 · MAINTAIN  (insurance)
   candour, early warnings,
   the itch to leave

   the structure tells you
   when to move: too heavy,
   go forward; needed again,
   go back

   status and reports move
   out into wider org rhythms
</code></pre></div></div>

<h2 id="phase-one-getting-to-know-each-other">Phase one: getting to know each other</h2>

<p>The first phase starts sooner than most people expect. I do not wait for a reason to book the first 1:1. The early ones are deliberately informal, no agenda, no tracking document, just getting on the same page about how we each work. It is tempting to call this unproductive. That is the point. The whole job of phase one is trust: the caring stops being a claim and becomes something the other person has evidence for. You cannot credibly care about someone you never bothered to know.</p>

<p>So I open on their side of the table. Something that happened, or a real question about them and how they are doing. One of my favourites is “tell me something I don’t know,” though it wears out if you lean on it, so I keep it occasional. Most of the time “how are things?” or “how have you been?” does the same work. What I am really doing is learning to read their weather: the health, the family, the good and bad months that sit behind the work and explain most of it. Get that right and, much later, they will bring you the hard things. Miss it and they never will.</p>

<h2 id="phase-two-sharing-context">Phase two: sharing context</h2>

<p>At some point the conversations earn more than familiarity, and the job becomes momentum. The content shifts from the people to the work as each of us sees it: the principles we operate on, the challenges we are carrying, our preferred ways of working. If phase one produced trust, phase two produces alignment, shared context both of us can spend later without having to renegotiate it every time. Once you agree on where you are going and how you each like to travel, you can move fast together and stop relitigating the basics.</p>

<h2 id="phase-three-working-from-a-shared-agenda">Phase three: working from a shared agenda</h2>

<p>Somewhere in here, structure emerges on its own, and it is worth leaning into. The most useful form I have found is a shared document that we both keep between meetings. When something comes up that is worth the other person’s time, it goes on the list. At the start of the meeting we look at what has gathered and decide together what actually matters today, and in what order. The preparation happens before we sit down, so the time together goes to the conversation and not to working out what the conversation should be about.</p>

<p>This is the most deliberately structured a 1:1 gets, and that is a feature. A living agenda means nothing important waits a full week to be raised, and nothing quietly falls through the cracks between sessions. It also makes the meeting legible to both of us: we can see what we are choosing to spend the time on, and what we are choosing to let go.</p>

<h2 id="phase-four-maintenance">Phase four: maintenance</h2>

<p>For a long time I did not draw a hard line between the structured phase and what comes after it. The split was a proposal from John, a direct report of mine and a genuinely sharp one. He suggested we stop using our 1:1 to cover things that were better handled in wider forums. I was glad to agree. Once we drew that line, our 1:1s got sharper and the wider forums did their job better too, and we ended up both more efficient and more widely aligned.</p>

<p>That is phase four, and its real purpose is insurance. By now the operational load, status updates, reports, post mortems, has moved into our wider organisational rhythms, where it belongs and where it scales. What is left is what no other channel carries. This is where the candour you earned in phase one finally gets spent: the disagreement someone would never voice in a room, the doubt about a decision, the project that quietly worries them while it is still cheap to fix. It is where the itch to leave shows up as restlessness, long before it hardens into a resignation, if there is somewhere safe to say it. On any given week this can look like nothing happened. That is what insurance looks like most of the time. It is also the phase everything before it was building toward, a protected slot where half formed worries surface while they are still easy to act on.</p>

<h2 id="whose-meeting-is-it">Whose meeting is it?</h2>

<p>There is a fashionable answer: the 1:1 belongs to the report. They set the agenda, the manager listens. I find the idea appealing, and there is something in it, but it is not how I actually run them. In my book a 1:1 is manager led, or better, coach led. I come with topics. I come with opportunities I have been turning over, especially when the results are there or the time we are spending together feels promising. I am never just a passenger.</p>

<p>The arrangement that has worked best sits between the two chairs: the report sets the agenda, and the manager prioritises it. The report brings the raw material of what matters to them. The manager brings the judgement of what to spend the scarce half hour on. Neither owns it alone, and the meetings I am proudest of are the ones where the question of who owns it stops having an answer, because both of us showed up with something.</p>

<h2 id="the-other-chair">The other chair</h2>

<p>Turn it around. As a report, you have more control over the phasing than you might expect, because you are usually the one bringing the agenda, and most of the resulting actions sit with you. That control comes with a responsibility: it is on you to judge honestly whether you have done the groundwork of the early phases before you push the relationship forward too fast.</p>

<p>Used well, your manager’s 1:1 is some of the best time you get for managing upward: setting expectations, and asking for help before you are drowning. It is also the channel whose health I would watch most closely. You do not want to arrive at a moment, well into your tenure, where you need your manager for something that genuinely matters and find the channel is not there: the 1:1 gone stale, the habit of candour never built. That capability has to exist before you need it. Keeping the manager 1:1 in good working order, even when nothing about it feels urgent, is just paying the insurance premium before you have to make a claim.</p>

<h2 id="knowing-when-to-move">Knowing when to move</h2>

<p>The phases do not come with dates, and the transitions are a judgement call. The most reliable signal I have is the structure itself. When the shared agenda starts to feel like overhead, when the items on it are increasingly things that could have gone somewhere else, that is the cue to lighten and move forward. When a relationship that had settled into maintenance suddenly needs the scaffolding back, that is the cue to move back. The felt weight of the structure is the instrument. Too heavy for what is actually happening, go forward. Too light, go back.</p>

<p>Organisational change moves the needle too, often more than anything the two people do. A management relationship can dissolve into a mentorship, and the machinery can relax. A company pivot, a role change, or a promotion can reset a settled relationship several phases back. The caring survives the reset. The context usually does not, and pretending otherwise is how good 1:1s quietly die.</p>

<h2 id="when-a-11-goes-wrong">When a 1:1 goes wrong</h2>

<p>That gives the failure mode a sharper name than unproductive. A bad 1:1 is usually a phase error. When one feels pointless, it is rarely the person; it is a phase mismatch, or a misread of how the other person likes to work. Running status theatre in a slot that should carry uncertainties. Forcing a prioritised agenda on someone you have not yet gotten to know. Keeping the shorthand of a settled relationship going after a reorg has quietly erased the shared context it relied on. The sessions are rarely the problem. The reading of where you are is.</p>

<h2 id="time-not-the-hour">Time, not the hour</h2>

<p>It is also why the question at the top asks whether the 1:1 is worth the <em>time</em>, not worth the <em>hour</em>. Mine usually run thirty minutes, not the default hour everyone’s calendar reaches for. By the maintenance phase, cadence can loosen too. Weekly can become fortnightly, because maintenance does not need the urgency that building context did. The phase sets the format, length, frequency, structure, and the honest answer changes as the relationship does.</p>

<p>So, what does a 1:1 actually need to produce to be worth the time? It depends on where you are. First trust, two people who actually know how each other works. Then momentum, shared context and aligned principles you do not have to keep rebuilding. Then structure, a working agenda that keeps the important things from waiting. And finally insurance, the uncertainties and early warnings no other channel would ever have carried. Underneath all four sits the same principle: you hold 1:1s because you care about the other person. That is the one thing that makes all the rest of it worth doing.</p>

<h2 id="request-for-comments">Request for comments</h2>

<div class="rfc">

  <p>This essay is a working draft, and I’d genuinely like it argued with. These are the questions I dropped from the essay because I could not land a strong answer on my own. <strong>Click one to drop it into the comment box</strong> and take it on, or <a href="mailto:andrea@dellacorte.me">email me</a>. The essay will be revised as the answers come in.</p>

  <ul>
    <li><a class="rfc-q" href="#comments">Does this model actually hold up? Have you lived through a similar shift in how a working relationship needed to be run?</a></li>
    <li><a class="rfc-q" href="#comments">Does the phase arc stretch to peers, where neither of you owns the relationship?</a></li>
    <li><a class="rfc-q" href="#comments">Why are some 1:1s energising and others flat, even within the same phase?</a></li>
    <li><a class="rfc-q" href="#comments">How do you end a 1:1 relationship? When do you cancel the series entirely, and what does that signal to the other person?</a></li>
    <li><a class="rfc-q" href="#comments">What does the reset conversation actually sound like after a pivot or a promotion?</a></li>
  </ul>

</div>]]></content><author><name>Andrea Della Corte</name></author><category term="essays" /><category term="work" /><category term="management" /><category term="meetings" /><summary type="html"><![CDATA[This is a work in progress, published early on purpose. See Request for comments at the end.]]></summary></entry><entry><title type="html">dellacorte.me</title><link href="https://dellacorte.me/about/dellacorte-me/" rel="alternate" type="text/html" title="dellacorte.me" /><published>2026-02-17T00:00:00+00:00</published><updated>2026-02-17T00:00:00+00:00</updated><id>https://dellacorte.me/about/dellacorte-me</id><content type="html" xml:base="https://dellacorte.me/about/dellacorte-me/"><![CDATA[<p>In this page I write about things I learn during my day from others, books or just my experiences.</p>

<p>All typing, local dev and pushing is done via <a href="https://cursor.com">Cursor</a>. Task tracking is done via <a href="https://github.com/hmans/beans">beans</a>.</p>

<p>The blog is built on <a href="https://jekyllrb.com/">Jekyll</a>. The theme is based on <a href="https://fvsch.github.io/remarkdown/">ReMarkdown</a>.</p>

<p>This website code is hosted on  <a href="https://www.netlify.com/">Netlify</a>.</p>]]></content><author><name>Andrea Della Corte</name></author><category term="about" /><category term="meta" /><category term="personal" /><summary type="html"><![CDATA[In this page I write about things I learn during my day from others, books or just my experiences.]]></summary></entry><entry><title type="html">Invitation to connect</title><link href="https://dellacorte.me/about/invitation/" rel="alternate" type="text/html" title="Invitation to connect" /><published>2026-02-17T00:00:00+00:00</published><updated>2026-02-17T00:00:00+00:00</updated><id>https://dellacorte.me/about/invitation</id><content type="html" xml:base="https://dellacorte.me/about/invitation/"><![CDATA[<p>This is a standing invitation: if we have <a href="/">common interests</a>, I want to talk to you.</p>

<p>My email address is <a href="mailto:andrea@dellacorte.me">andrea@dellacorte.me</a>.</p>

<ul>
  <li>
    <p>I love discussing stuff via email. Email works best for me as I’m not on social network nowadays, but sort through my mail many times a day. Additionally, writing helps me organise my mind and reshape my thinking. I promise I’ll read 100% of your emails and get back to 90%+ of your emails.</p>
  </li>
  <li>
    <p>I love reading suggestions. If you see something on the internet worth discussing, send it over. Good content is priceless - I have a huge <a href="https://fs.blog/2013/06/the-antilibrary/">library of unread ideas</a> I jump hectically around.</p>
  </li>
  <li>
    <p>I love making friends. If you live in London or you’re just visiting for a while, let’s meet up for coffee in the city, my treat.</p>
  </li>
  <li>
    <p>I love hearing about ways to make an impact. If you know of charities who’d benefit by mentoring, coaching, career guidance, hit me up. Same as you’d like me to help you out with one of your challenges.</p>
  </li>
</ul>

<blockquote>
  <p>Note: This page was inspired by <a href="https://www.kalzumeus.com/standing-invitation/">Kalzumeus’ Standing Invitation</a></p>
</blockquote>]]></content><author><name>Andrea Della Corte</name></author><category term="about" /><category term="meta" /><category term="personal" /><summary type="html"><![CDATA[This is a standing invitation: if we have common interests, I want to talk to you.]]></summary></entry><entry><title type="html">Template x Code</title><link href="https://dellacorte.me/presentations/code/" rel="alternate" type="text/html" title="Template x Code" /><published>2024-01-21T00:00:00+00:00</published><updated>2024-01-21T00:00:00+00:00</updated><id>https://dellacorte.me/presentations/code</id><content type="html" xml:base="https://dellacorte.me/presentations/code/"><![CDATA[<script>
// Constructor receives a selector that indicates
// where to inject the demonstration in your page.
const demo = new GDemo('#container');

const code = `
function greet(){
console.log("Hello World!");
}

greet();
`

demo
.openApp('editor', {minHeight: '350px', windowTitle: 'demo.js'})
.write(code, {onCompleteDelay: 1500})
.openApp('terminal', {minHeight: '350px', promptString: '$'})
.command('node ./demo', {onCompleteDelay: 500})
.respond('Hello World!')
.command('')
.end();

</script>]]></content><author><name>Andrea Della Corte</name></author><category term="presentations" /><category term="presentations" /><category term="code" /><summary type="html"><![CDATA[]]></summary></entry><entry><title type="html">Template x Presentation</title><link href="https://dellacorte.me/presentations/presentation/" rel="alternate" type="text/html" title="Template x Presentation" /><published>2024-01-21T00:00:00+00:00</published><updated>2024-01-21T00:00:00+00:00</updated><id>https://dellacorte.me/presentations/presentation</id><content type="html" xml:base="https://dellacorte.me/presentations/presentation/"><![CDATA[name: inverse
layout: true
class: center, middle, inverse
---
#remark
[ri-mahrk]
.footnote[Go directly to [project site](https://github.com/gnab/remark)]
---
## What is it and why should I be using it?
---
layout: false
.left-column[
  ## What is it?
]
.right-column[
  A simple, in-browser, Markdown-driven slideshow tool targeted at people who know their way around HTML and CSS, featuring:

- Markdown formatting, with smart extensions

- Presenter mode, with cloned slideshow view

- Syntax highlighting, supporting a range of languages

- Slide scaling, thus similar appearance on all devices / resolutions .red[*]

- Touch support for smart phones and pads, i.e. swipe to navigate slides

.footnote[.red[*] At least browsers try their best]
]
---
.left-column[
  ## What is it?
  ## Why use it?
]
.right-column[
If your ideal slideshow creation workflow contains any of the following steps:

- Just write what's on your mind

- Do some basic styling

- Easily collaborate with others

- Share with and show to everyone

Then remark might be perfect for your next.red[*] slideshow!

.footnote[.red[*] You probably want to convert existing slideshows as well]
]
---
.left-column[
  ## What is it?
  ## Why use it?
]
.right-column[
As the slideshow is expressed using Markdown, you may:

- Focus on the content, expressing yourself in next to plain text not worrying what flashy graphics and disturbing effects to put where

As the slideshow is actually an HTML document, you may:

- Display it in any decent browser

- Style it using regular CSS, just like any other HTML content

- Use it offline!

As the slideshow is contained in a plain file, you may:

- Store it wherever you like; on your computer, hosted from your Dropbox, hosted on Github Pages alongside the stuff you're presenting...

- Easily collaborate with others, keeping track of changes using your favourite SCM tool, like Git or Mercurial
]
---
template: inverse

## How does it work, then?
---
name: how

.left-column[
  ## How does it work?
### - Markdown
]
.right-column[
A Markdown-formatted chunk of text is transformed into individual slides by JavaScript running in the browser:

```remark
# Slide 1
This is slide 1

---

# Slide 2
This is slide 2
```

.slides[
  .first[
  ### Slide 1
  This is slide 1
  ]
  .second[
  ### Slide 2
  This is slide 2
  ]
]

Regular Markdown rules apply with only a single exception:

  - A line containing three dashes constitutes a new slide
  (not a horizontal rule, `&lt;hr /&gt;`)

Have a look at the [Markdown website](http://daringfireball.net/projects/markdown/) if you're not familiar with Markdown formatting.
]
---
.left-column[
  ## How does it work?
  ### - Markdown
  ### - Inside HTML
]
.right-column[
A simple HTML document is needed for hosting the styles, Markdown and the generated slides themselves:

```xml
<!DOCTYPE html>
<html>
  <head>
    <style type="text/css">
      /* Slideshow styles */
    </style>
  </head>
  <body>
*    <textarea id="source">
      <!-- Slideshow Markdown -->
    &lt;/textarea&gt;
*    <script src="remark.js">
    </script>
    <script>
      remark.create();
    </script>
  </body>
</html>
```

You may download remark to have your slideshow not depend on any online resources, or reference the [latest version](http://remarkjs.com/downloads/remark-latest.min.js) online directly.
]
---
template: inverse

## Of course, Markdown can only go so far.
---
.left-column[
  ## Markdown extensions
]
.right-column[
To help out with slide layout and formatting, a few Markdown extensions have been included:

- Slide properties, for naming, styling and templating slides

- Content classes, for styling specific content

- Syntax highlighting, supporting a range of languages
]

---
.left-column[
  ## Markdown extensions
  ### - Slide properties
]
.right-column[
Initial lines containing key-value pairs are extracted as slide properties:

```remark
name: agenda
class: middle, center

# Agenda

The name of this slide is .
```

Slide properties serve multiple purposes:

* Naming and styling slides using properties `name` and `class`

* Using slides as templates using properties `template` and `layout`

* Expansion of `` expressions to property values

See the [complete list](https://github.com/gnab/remark/wiki/Markdown#slide-properties) of slide properties.
]
---
.left-column[
  ## Markdown extensions
  ### - Slide properties
  ### - Content classes
]
.right-column[
Any occurences of one or more dotted CSS class names followed by square brackets are replaced with the contents of the brackets with the specified classes applied:

```remark
.footnote[.red.bold[*] Important footnote]
```

Resulting HTML extract:

```xml
<span class="footnote">
  <span class="red bold">*</span> Important footnote
</span>
```
]
---
.left-column[
  ## Markdown extensions
  ### - Slide properties
  ### - Content classes
  ### - Syntax Highlighting
]
.right-column[
Code blocks can be syntax highlighted by specifying a language from the set of [supported languages](https://github.com/gnab/remark/wiki/Configuration#highlighting).

Using [GFM](http://github.github.com/github-flavored-markdown/) fenced code blocks you can easily specify highlighting language:

.pull-left[

<pre><code>```javascript
function add(a, b)
  return a + b
end
```</code></pre>
]
.pull-right[

<pre><code>```ruby
def add(a, b)
  a + b
end
```</code></pre>
]

A number of highlighting [styles](https://github.com/gnab/remark/wiki/Configuration#highlighting) are available, including several well-known themes from different editors and IDEs.

]
---
.left-column[
  ## Presenter mode
]
.right-column[
To help out with giving presentations, a presenter mode comprising the
following features is provided:

- Display of slide notes for the current slide, to help you remember
  key points

- Display of upcoming slide, to let you know what's coming

- Cloning of slideshow for viewing on extended display
]
---
.left-column[
  ## Presenter mode
  ### - Inline notes
]
.right-column[
Just like three dashes separate slides,
three question marks separate slide content from slide notes:

```
Slide 1 content

*???

Slide 1 notes

---

Slide 2 content

*???

Slide 2 notes
```

Slide notes are also treated as Markdown, and will be converted in the
same manner slide content is.

Pressing __P__ will toggle presenter mode.
]
???
Congratulations, you just toggled presenter mode!

Now press __P__ to toggle it back off.
---
.left-column[
  ## Presenter mode
  ### - Inline notes
  ### - Cloned view
]
.right-column[
Presenter mode of course makes no sense to the audience.

Creating a cloned view of your slideshow lets you:

- Move the cloned view to the extended display visible to the audience

- Put the original slideshow in presenter mode

- Navigate as usual, and the cloned view will automatically keep up with the original

Pressing __C__ will open a cloned view of the current slideshow in a new
browser window.
]
---
template: inverse

## It's time to get started!
---
.left-column[
  ## Getting started
]
.right-column[
Getting up and running is done in only a few steps:

1. Visit the [project site](http://github.com/gnab/remark)

2. Follow the steps in the Getting Started section

For more information on using remark, please check out the [wiki](https://github.com/gnab/remark/wiki) pages.
]
---
name: last-page
template: inverse

## That's all folks (for now)!

Slideshow created using [remark](http://github.com/gnab/remark).]]></content><author><name>Andrea Della Corte</name></author><category term="presentations" /><category term="presentations" /><category term="template" /><summary type="html"><![CDATA[name: inverse layout: true class: center, middle, inverse --- #remark [ri-mahrk] .footnote[Go directly to [project site](https://github.com/gnab/remark)] --- ## What is it and why should I be using it? --- layout: false .left-column[ ## What is it? ] .right-column[ A simple, in-browser, Markdown-driven slideshow tool targeted at people who know their way around HTML and CSS, featuring:]]></summary></entry><entry><title type="html">On Aging</title><link href="https://dellacorte.me/notes/on-aging/" rel="alternate" type="text/html" title="On Aging" /><published>2021-12-26T00:00:00+00:00</published><updated>2021-12-26T00:00:00+00:00</updated><id>https://dellacorte.me/notes/on-aging</id><content type="html" xml:base="https://dellacorte.me/notes/on-aging/"><![CDATA[<h3 id="sylvia-plath">Sylvia Plath</h3>

<p>I saw my life branching out before me like the green fig tree in the story. From the tip of every branch, like a fat purple fig, a wonderful future beckoned and winked. One fig was a husband and a happy home and children, and another fig was a famous poet and another fig was a brilliant professor, and another fig was Ee Gee, the amazing editor, and another fig was Europe and Africa and South America, and another fig was Constantin and Socrates and Attila and a pack of other lovers with queer names and offbeat professions, and another fig was an Olympic lady crew champion, and beyond and above these figs were many more figs I couldn’t quite make out. I saw myself sitting in the crotch of this fig tree, starving to death, just because I couldn’t make up my mind which of the figs I would choose. I wanted each and every one of them, but choosing one meant losing all the rest, and, as I sat there, unable to decide, the figs began to wrinkle and go black, and, one by one, they plopped to the ground at my feet.</p>

<p><a href="https://www.goodreads.com/quotes/7511-i-saw-my-life-branching-out-before-me-like-the">The Bell Jar</a></p>

<h3 id="honkykat">Honkykat</h3>

<p>Part of growing older is mourning the person you could have been.</p>

<p><a href="https://news.ycombinator.com/item?id=29687195">HackerNews</a></p>]]></content><author><name>Andrea Della Corte</name></author><category term="notes" /><category term="personal" /><category term="philosophy" /><summary type="html"><![CDATA[Sylvia Plath]]></summary></entry><entry><title type="html">Coaches’ rules for life</title><link href="https://dellacorte.me/notes/coaches-rules-for-life/" rel="alternate" type="text/html" title="Coaches’ rules for life" /><published>2021-07-06T00:00:00+01:00</published><updated>2021-07-06T00:00:00+01:00</updated><id>https://dellacorte.me/notes/coaches-rules-for-life</id><content type="html" xml:base="https://dellacorte.me/notes/coaches-rules-for-life/"><![CDATA[<p>From <a href="https://curiouslog.com/the-playbook-a-coachs-rules-for-life/" title="&quot;The Playbook – A coach’s rules for life&quot;, curioslog.com">“The Playbook – A coach’s rules for life”, curioslog.com</a></p>

<p><a href="https://en.wikipedia.org/wiki/Doc_Rivers">Doc Rivers</a> (Basketball)</p>

<ul>
  <li>Pressure is a privilege <em>(what a way to shift our mindset – from stress to gratitude)</em></li>
  <li>finish the race</li>
  <li>you will not be a victim</li>
  <li>ubuntu – I am because we are</li>
  <li>champions keep moving ahead</li>
</ul>

<p><a href="https://en.wikipedia.org/wiki/Jill_Ellis">Jill Ellis</a> (Soccer)</p>

<ul>
  <li>not just about how you become the best, but stay the best. mountaintops are small and air is thin</li>
  <li>hold fast , stay true. Believe in yourself</li>
  <li>risk is opportunity</li>
  <li>be true to yourself</li>
  <li>if you want to be heard, make a statement <em>(references the equal pay protest)</em></li>
</ul>

<p><a href="https://en.wikipedia.org/wiki/Jos%C3%A9_Mourinho">Jose Mourinho</a> (Soccer)</p>

<ul>
  <li>understand your audience</li>
  <li>if you are prepared for the worst, you are prepared</li>
  <li>the underdog attack</li>
  <li>some rules are meant to be broken</li>
  <li>the train doesn’t stop twice</li>
  <li><strong>don’t coach the player, coach the team</strong>. They already know how to play. Teach them how to play in that team <em>(my favorite)</em></li>
</ul>

<p><a href="https://en.wikipedia.org/wiki/Patrick_Mouratoglou">Patrick Mouratoglou</a> (Tennis)</p>

<ul>
  <li>your biggest weakness can be your greatest strength</li>
  <li>never be afraid to get fired</li>
  <li>mistakes are inevitable but don’t let them define you</li>
  <li>emotions are the worst adviser</li>
  <li>let them know they are not alone. <em>(Amazing story about why players tank their games even at the highest levels)</em></li>
  <li>a good lie can become the truth <em>(how a lie helped Serena Williams during the Wimbledon)</em></li>
  <li>everything depends on you</li>
</ul>

<p><a href="https://en.wikipedia.org/wiki/Dawn_Staley">Dawn Staley</a> (Basketball)</p>

<ul>
  <li>bring your own ball</li>
  <li>growth takes place outside of the comfort zone</li>
  <li>create a home court advantage <em>( build a community of supporters/fans)</em></li>
  <li>when you make someone feel better, they want to help you succeed</li>
  <li>24 hrs rule- move on from a win or loss in 24 hrs <em>(I loved this – can sure be mantra for our lives too)</em></li>
  <li><strong>what is delayed is not denied</strong>. It will happen.</li>
</ul>]]></content><author><name>Andrea Della Corte</name></author><category term="notes" /><category term="coaching" /><category term="personal" /><summary type="html"><![CDATA[From “The Playbook – A coach’s rules for life”, curioslog.com]]></summary></entry><entry><title type="html">No-nos</title><link href="https://dellacorte.me/notes/no-nos/" rel="alternate" type="text/html" title="No-nos" /><published>2021-07-06T00:00:00+01:00</published><updated>2021-07-06T00:00:00+01:00</updated><id>https://dellacorte.me/notes/no-nos</id><content type="html" xml:base="https://dellacorte.me/notes/no-nos/"><![CDATA[<p>From the <a href="http://fooledbyrandomness.com/AUBCommencement.pdf">Commencement Address at the American University in Beirut by Nassim Nicholas Taleb</a></p>

<p>The following are no-nos:</p>

<ul>
  <li>Muscles without strength,</li>
  <li>friendship without trust,</li>
  <li>opinion without risk,</li>
  <li>change without aesthetics,</li>
  <li>age without values,</li>
  <li>food without nourishment,</li>
  <li>power without fairness,</li>
  <li>facts without rigor,</li>
  <li>degrees without erudition,</li>
  <li>militarism without fortitude,</li>
  <li>progress without civilization,</li>
  <li>complication without depth,</li>
  <li>fluency without content,</li>
  <li>and, most of all, religion without tolerance.</li>
</ul>]]></content><author><name>Andrea Della Corte</name></author><category term="notes" /><category term="coaching" /><category term="personal" /><summary type="html"><![CDATA[From the Commencement Address at the American University in Beirut by Nassim Nicholas Taleb]]></summary></entry><entry><title type="html">Manual</title><link href="https://dellacorte.me/about/manual/" rel="alternate" type="text/html" title="Manual" /><published>2021-04-22T00:00:00+01:00</published><updated>2021-04-22T00:00:00+01:00</updated><id>https://dellacorte.me/about/manual</id><content type="html" xml:base="https://dellacorte.me/about/manual/"><![CDATA[<p>This is a playbook on everything Andrea. It captures more about me and how I operate in a working environment.</p>

<h3 id="-overview">🏠 OVERVIEW</h3>

<ul>
  <li><a href="https://www.16personalities.com/enfj-personality">ENFJ-A</a> - Extraverted, Intuitive, Feeling, and Judging personality traits. Warm, forthright, love helping others.</li>
</ul>

<h3 id="-strengths">👍🏼 STRENGTHS</h3>

<ul>
  <li>Both Barrel and Ammunition (see <a class="backlink" href="/notes/barrels-and-ammunitions/">Barrels and Ammunitions</a>): Love taking initiative, organising and pointing people in the right direction, but not afraid to get my hands dirty and put in the work.</li>
  <li>Dependable: Very high ‘say-do’ ratio.</li>
</ul>

<h3 id="-weaknesses">👎🏼 WEAKNESSES</h3>

<ul>
  <li>Operating without context: I struggle contributing to decisions where I don’t have sufficient context or background.</li>
  <li>Going too fast: Sometimes I can jump into things too fast and skip a few steps in my communication. While I do my best to explain the “why” of what I’m doing don’t be afraid to rein me in.</li>
</ul>

<h3 id="-principles">🛠 PRINCIPLES</h3>

<ul>
  <li>Leave it better than you found it: What I do should have a positive impact on society, my family, myself.</li>
  <li>This too shall pass: Some periods are ups, some periods are down. Be modest in the highs, bear and learn during the lows.</li>
</ul>

<h3 id="-favorite-books">📚 FAVORITE BOOKS</h3>

<ul>
  <li>The Dark Tower: The Gunslinger, by Stephen King</li>
  <li>How to Fail at Almost Everything and Still Win Big, by Scott Adams</li>
  <li>A Little Life, by Hanya Yanagihara</li>
  <li>1984, by George Orwell</li>
</ul>

<h3 id="-favorite-quote">🙏🏼 FAVORITE QUOTE</h3>

<blockquote>Those who say it cannot be done should not get in the way of those who are doing it. — Bernard Shaw</blockquote>

<h3 id="-get-in-touch">📲 GET IN TOUCH</h3>

<p>If you want to get in touch, I’m most responsive over <a href="mailto:andrea@dellacorte.me">email</a>. Let me know what’s on your mind!</p>]]></content><author><name>Andrea Della Corte</name></author><category term="about" /><category term="meta" /><category term="personal" /><summary type="html"><![CDATA[This is a playbook on everything Andrea. It captures more about me and how I operate in a working environment.]]></summary></entry><entry><title type="html">Barrels and Ammunitions</title><link href="https://dellacorte.me/notes/barrels-and-ammunitions/" rel="alternate" type="text/html" title="Barrels and Ammunitions" /><published>2021-04-22T00:00:00+01:00</published><updated>2021-04-22T00:00:00+01:00</updated><id>https://dellacorte.me/notes/barrels-and-ammunitions</id><content type="html" xml:base="https://dellacorte.me/notes/barrels-and-ammunitions/"><![CDATA[<p>Source: <a href="https://www.youtube.com/watch?v=w19IBxDu2Y4">How to Operate with Keith Rabois (How to Start a Startup 2014: Lecture 14)</a></p>

<p>A really clever way to view organizations - The quote from Rabois summarizes the idea nicely:</p>

<blockquote>If you think about people, there are two categories of high-quality people: there is the ammunition, and then there are the barrels. You can add all the ammunition you want, but if you have only five barrels in your company, you can literally do only five things simultaneously. If you add one more barrel, you can now do six things simultaneously. If you add another one, you can do seven, and so on.
In short, the output of your organization is dependent on the number of people that can own projects and see them through to the end.</blockquote>

<p>Excellent deep dive by <a href="https://www.conordewey.com/blog/barrels-and-ammunition/">Conor Dewey</a></p>]]></content><author><name>Andrea Della Corte</name></author><category term="notes" /><category term="productivity" /><category term="metaphors" /><category term="writing" /><summary type="html"><![CDATA[Source: How to Operate with Keith Rabois (How to Start a Startup 2014: Lecture 14)]]></summary></entry></feed>