Startup posts (#14)

* initial draft * Getting 11ty to run again * View on local network * improve formatting * All posts on the front page - I'll paginate one day * Add markdown footnotes * Improve spacing on bullet points * Bold is same grey as headers * Post updates * Update publish date * Trigger deploy * Update .nvmrc
ucg8j · Dec 1, 2023 · 18c1b96 · 18c1b96
1 parent 3b51499
commit 18c1b96
Show file tree

Hide file tree

Showing 11 changed files with 224 additions and 8 deletions.
diff --git a/.eleventy.js b/.eleventy.js
@@ -4,6 +4,7 @@ const pluginRss = require("@11ty/eleventy-plugin-rss");
 const pluginSyntaxHighlight = require("@11ty/eleventy-plugin-syntaxhighlight");
 const pluginNavigation = require("@11ty/eleventy-navigation");
 const markdownIt = require("markdown-it");
+const markdownItFootnote = require("markdown-it-footnote");
 const markdownItAnchor = require("markdown-it-anchor");
 const lazyImagesPlugin = require('eleventy-plugin-lazyimages');
 
@@ -88,7 +89,7 @@ module.exports = function(eleventyConfig) {
     permalink: true,
     permalinkClass: "direct-link",
     permalinkSymbol: "#"
-  });
+  }).use(markdownItFootnote);
   eleventyConfig.setLibrary("md", markdownLibrary);
 
   // Browsersync Overrides
@@ -105,7 +106,9 @@ module.exports = function(eleventyConfig) {
       },
     },
     ui: false,
-    ghostMode: false
+    ghostMode: false,
+    host: "0.0.0.0"
+
   });
 
   return {

diff --git a/.nvmrc b/.nvmrc
@@ -1 +1 @@
-12
+18
diff --git a/README.md b/README.md
@@ -64,7 +64,7 @@ DEBUG=* npx eleventy
 ```
 
 ### Implementation Notes
-
+ 
 * `about/index.md` shows how to add a content page.
 * `posts/` has the blog posts but really they can live in any directory. They need only the `post` tag to be added to this collection.
 * Add the `nav` tag to add a template to the top level site navigation. For example, this is in use on `index.njk` and `about/index.md`.
@@ -76,3 +76,7 @@ DEBUG=* npx eleventy
   * `_includes/layouts/home.njk`: the home page template (wrapped into `base.njk`)
   * `_includes/layouts/post.njk`: the blog post template (wrapped into `base.njk`)
 * `_includes/postlist.njk` is a Nunjucks include and is a reusable component used to display a list of all the posts. `index.njk` has an example of how to use it.
+
+# LS notes
+- using node v18.3.0
+- may need to `export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:/System/Volumes/Data/opt/homebrew/Cellar/libarchive/3.7.2/lib/pkgconfig` to get `npm install` to work
diff --git a/_includes/postslist.njk b/_includes/postslist.njk
@@ -4,7 +4,7 @@
     <a href="{{ post.url | url }}" class="postlist-link">{% if post.data.title %}{{ post.data.title }}{% else %}<code>{{ post.url }}</code>{% endif %}</a>
     <br>
     <time class="postlist-date" datetime="{{ post.date | htmlDateString }}">{{ post.date | readableDate }}</time>
-    <p>{{post.data.excerpt}}...<a href="{{ post.url | url }}">read more</a></p>
+    <p>{{post.data.excerpt}}... <a href="{{ post.url | url }}">read more</a></p>
     {# {% for tag in post.data.tags %} #}
       {# {%- if collections.tagList.indexOf(tag) != -1 -%} #}
       {# {% set tagUrl %}/tags/{{ tag }}/{% endset %} #}

diff --git a/content/images/2023/top-problems.png b/content/images/2023/top-problems.png
diff --git a/content/images/2023/trough-of-sorrow.png b/content/images/2023/trough-of-sorrow.png
diff --git a/css/index.css b/css/index.css
@@ -32,16 +32,17 @@ h2 {
   margin-top: 1em;
 }
 strong {
-  color: #333;
+  color: #555;
 }
 p:last-child {
   margin-bottom: 0;
   margin-top: 5px;
 }
 p,
 .tmpl-post li,
-li:not(:last-child) {
+li:not(header li):not(:last-child) {
   margin-bottom: .75rem;
+  margin-top: .75rem;
 }
 img {
   display: block;

diff --git a/index.njk b/index.njk
@@ -5,6 +5,6 @@ eleventyNavigation:
   order: 1
 ---
 
-{% set postslist = collections.posts | head(-25) %}
+{% set postslist = collections.posts | head(-30) %}
 {% set postslistCounter = collections.posts | length %}
 {% include "postslist.njk" %}
diff --git a/package.json b/package.json
@@ -32,5 +32,9 @@
     "luxon": "^1.21.3",
     "markdown-it": "^8.4.2",
     "markdown-it-anchor": "^5.2.5"
+  },
+  "dependencies": {
+    "markdown-it-footnote": "^3.0.3",
+    "sharp": "^0.32.6"
   }
 }
diff --git a/posts/how-to-find-a-co-founder.md b/posts/how-to-find-a-co-founder.md
@@ -0,0 +1,81 @@
+---
+title: How to find a co-founder
+permalink: /how-to-find-a-co-founder/
+slug: how-to-find-a-co-founder
+date: 2023-12-01
+tags: tech, startups
+excerpt: Having found a co-founder twice. I formed a process that worked for me. Here is how I did it.
+layout: layouts/post.njk
+---
+
+I recently went on the hunt for a new co-founder.  This ended up being my process.
+
+# Starting principles
+- Meet as many as you can in parallel. Like a sales pipeline, you wouldn't only talk to a single customer at a time, nor should you for founders.
+- Give yourself a deadline, goal setting matters, it also creates urgency so you can close.
+- It takes longer than you think, several months for me and I know many others that took a lot longer.
+- Decide on some initial parameters:
+
+	- **Geography**: Initially for me, this was East coast US to Europe for some timezone overlap. This narrowed to UK and western Europe. I realised having the Atlantic ocean between us was going to be too big of a hurdle to de-risk the relationship.
+	- **Profile**: I started with 'either a CEO or CTO type'. Typically you'll have a CEO/CTO founding combo. Being technical myself and having [reflected on my previous venture](../startup-reflections/#self), I narrowed this to CEO.
+	- **Idea or not**: I was looking for someone with an idea, validated ideally.
+	- **Quit their job**: candidates that haven't quit don't have the same urgency. They are comfortable. And sometimes flirting with the idea of startups rather than being ready to commit now.
+	- **Not an existing duo**: you want to be on as equal terms with your co-founder(s) as possible. After meeting a few duos, I realised it was unlikely I would feel on the same level as the original duo.
+
+# The process
+This is somewhere between dating and hiring someone. You want to keep it natural and a lot of it is about getting to know the other person. But you have a deadline and a business to start!
+
+## Top of funnel - get swiping
+In dating the 'old way' was being set up by friends. The 'new way' is dating apps. Both work for co-founder leads, but just like Tinder, you'll get many more leads through [Y Combinator's co-founder matching app](https://www.ycombinator.com/cofounder-matching/).
+
+## 1. The first date
+This is the initial meet and greet. I kept these to a 30min video call or a quick in person coffee. The goals:
+
+✅ Get to know them. Do you vibe? Yep, it's a lot about vibes. If you don't vibe on a first date with someone, you don't go on a second date.
+✅ Do you respect them? This is really about whether you see them on eye level.
+
+## 2. The written assignment
+The aim here is to have the most time efficient process to get to know your potential co-founder. The [50 Founder questions](https://proof-assets.s3.amazonaws.com/firstround/50%20Questions%20for%20Co-Founders.pdf) get you to introspect on *why* you're founding a company, reveals your areas of expertise and raises thorny questions early like *how would you resolve a stalemate?* The best founders were already aware of the 50 Founder Questions. If someone hadn't heard of them, I'd give them time to get back to me.
+
+✅ Exchange [50 Founder questions](https://proof-assets.s3.amazonaws.com/firstround/50%20Questions%20for%20Co-Founders.pdf) - ensure values, expertise and thinking alignment.
+
+## 3. More dates - discuss the Founder Questions and any other questions
+If the potential co-founder's responses revealed a gap too large, I'd just say so in an email. If you only have minor flags, question marks and areas you want to dig deeper - have as many calls to work through them as required.
+
+✅ Each meeting is increasing your confidence in each other, to the point you are ready for a work trial.
+✅ With a view to commencing a work trial, if the co-founder is committed to an idea, get across the idea.[^1]
+
+
+## 4.  Part time work trial
+By this stage you've worked through values, any possible question marks you've had about each other and are ready to test out what it is like to work with each other. I did this with several people at the same time. Using the dating analogy, this is that tricky and tiring phase where you haven't committed to one person yet. You're switching contexts and trying to not mix up details about each person! The work trial can look quite different depending on each person. For example, with one they hadn't found an idea, so the working together was about making progress through the ideation phase. For another, it was about doing joint discovery calls and validating ideas.
+
+✅ Complete a timeboxed work trial together.
+
+## 5. Commit
+This doesn't mean you have incorporated. But from step 4 you need to pick one person to move forward. And hopefully you have a strong sense of who the right person is. Having committed to each other, set yourself ambitious goals that are aligned to each of your primary areas of responsibility. For me that looked like developing a prototype and for my co-founder it was securing design partnerships. If this all goes well, you're already a company, you just need to sign the dotted line. 
+
+Good luck!
+
+# Other inspiration
+- [Whalesync's trial period template](https://whalesync.notion.site/TEMPLATE-Cofounder-Trial-Period-cbc8b29c068c4150b9ccd71f40291f6e)
+- [YCs doc on co-founder matching](https://docs.google.com/document/d/1rXUOP-FcnIE8eNTkKlELkakZ-MLaIvEyIxUlBOLNZPw/edit) my highlights:
+	1. Someone you enjoy spending time with and get along with. **Would I want to be friends with this person?**
+	2. An exceptional person - smart and effective
+	3. **If you have hesitancy towards someone, listen to it.**
+	4. **Find people you have things in common with** - shared interests, hobbies and values
+	5. The person is more important than the idea
+	- **The median time between when the founders joined the site and when they matched with the person they ultimately ended up working with is 100 days**
+- [EF advice](https://medium.com/entrepreneur-first/the-co-founder-checklist-2f5be597e887)
+	- Both co-founders are technical, or technical with a domain expert
+	- Both co-founders are involved in everything
+	- No ‘pity founding’ - we're mates!
+	- A co-founder isn’t a ‘must-have’, a generic role that needs to be filled... they are a vital value-add
+	- "Each co-founder needs to have a strong relationship with each co-founder. In our experience, in a three this often isn’t the case. Someone is usually making a compromise and although that may seem ok in the short term, this doesn’t lead to harmonious founding teams in the long term."
+	- you have, or can quickly acquire the skills needed to build the product you want to build
+- [Paul Graham](http://www.paulgraham.com/really.html)
+	- "You haven't seen someone's true colors unless you've worked with them on a startup."
+	- "the relationship between founders was more important than ability"
+	- Share [startupschool FAQs](https://www.startupschool.org/faq) with them - aim to pick a trial project to work on together
+- More questions to ask each other from [YCs doc here](https://docs.google.com/document/d/1L4wY9qRk75K7B5y9_unueE4Tw0YLRarA9vaCTwfwL-4/edit#heading=h.xhucswxvxook)
+
+[^1]: This is a good opportunity to stress test the relationship too. Really question the idea, poke holes, debate it and see how they respond. What would it take to work on something else? You probably need to pivot in the future, which is a difficult conversation if you don't arrive at it at the same time.