### Types of Structured Data There are many types of Structured Data you can embed on your site - [Google Search Central has a list of structured data features](https://developers.google.com/search/docs/appearance/structured-data/search-gallery) which that is worth a good look. Some examples of Structured Data include: - **Article**: For news, blog, and other article pages - **Events**: Showcases events like concerts, festivals, and other happenings - **FAQ**: Make your FAQ page more discoverable - **Product**: Details and information about a product you're selling - **Recipe**: Ingredients, cook time, and other details about a recipe - **Review Snippet**: A review of a product, service, or other item - **Video**: For pages that showcase video content Each of these formats are slightly different in content, but they use JSON-LD to describe the content in a way that search engines can understand. By way of example, this is the Structured Data for a post on my site about a livestream I did demonstrating [how to build a site with Astro, TypeScript, and React](https://mikebifulco.com/posts/live-astro-content-driven-website-rebuild): ```html ``` Not too bad, right? This JSON-LD tells Google that this page is a video, and gives Google some information about the video, like the title, description, and thumbnail. In theory, if someone searches for the title of the video, Google might show this video in the search results, with a thumbnail and a link to the video. Once you've got Structured Data embedded on your site, you can verify that it's working using [Schema.org's Structured Data Testing Tool](https://validator.schema.org/):
`, ``, ``, ``, and `` in html) will be be wrapped in links that point to themselves. This allows readers to link to _specific_ headings in your articles, jumping to relevant bits of content without forcing someone to read through an entire article. Generally speaking, it will look something like this:
```html
My first blog post
```
The `` tag here has an `href` value of `#some-unique-id` - this is the id of the heading tag. This is based on an HTML [standard defined by the W3C](https://www.w3.org/TR/html401/struct/links.html#h-12.2.3). In short, you can link to any element on an HTML page which has a unique `id` attribute defined, by appending `#[id]` to the end of the URL, like `www.example.com#id-of-the-element`.
## This is tricky with Markdown and MDX
In most static site generators and JAMStack frameworks which allow you to use Markdown and MDX to generate content, the goal is simple: give authors a _very_ simple way to author content using Markdown syntax. The unfortunate side effect in this case is that there's not a way to specify IDs for the headings in Markdown posts (at least, not one that I'm aware of).
A sample markdown post might look like this:
```md
---
title: Hello, world
---
# A fish called wanda
In this essay, I will explain the difference between...
```
This results in the following output:
```html
A fish called wanda
In this essay, I will explain the difference between...
```
Fantastic! That's a nice, easy way to write, but there's not a way to add an id to the heading tag. At least, not out of the box. This is where MDX's plugins come in handy.
## Automatically linking to headings in your mdx posts with rehype plugins
> _Note: This tutorial assumes you're using MDX with NextJS, althought it may be applicable to other systems. Feel free to [send me](https://twitter.com/irreverentmike) any hurdles you encounter with other frameworks, and I'll try to document them here._
### Step 1: Generate IDs for all headings automatically with rehype-slug
[`rehype-slug`](https://github.com/rehypejs/rehype-slug) is a plugin that works with MDX, and will automatically generate IDs for your headings by generating a slug based on the text they contain.
1. Install `rehype-slug` in your project by running `npm install --save rehype-slug` or `yarn add rehype-slug`
2. Add `rehype-slug` to the list of rehype plugins MDX uses. In the case of next.js sites, it is likely wherever you call `serialize()` from `next-mdx-remote`.
```jsx
import rehypeSlug from 'rehype-slug';
// ...
const options = {
mdxOptions: {
rehypePlugins: [
rehypeSlug, // add IDs to any h1-h6 tag that doesn't have one, using a slug made from its text
],
},
};
const mdxSource = await serialize(post.content, options);
// ...
```
**Note:** My site uses `serialize()` in several places, so I extracted `options` to its own file. This avoids repeated code, and allows me to manage my plugins for MDX from one place.
At this point, if you fire up your dev environment, and use your browser devtools to inspect any of the headings generated from markdown for your site, they should all have an `id` property added. For the example above, you'd see:
```html
A fish called wanda
```
We're halfway there - you can now link to `www.example.com#a-fish-called-wanda`, and the browser will automatically scroll to the heading.
### Step 2: use MDXProvider to customize the way heading tags render
[MDXProvider](https://mdxjs.com/docs/using-mdx/#mdx-provider) is a wrapper component which allows you to customize the way your MDX renders by providing a list of `components`.
This step will depend heavily on the UI frameworks you've chosen for your site - I use [Chakra UI](https://chakra-ui.com/) for my nextjs site, but you can use whatever you like - [tailwindcss](https://tailwindcss.com/), [Material UI](https://mui.com/), etc will all have similar parallels.
Here's a simplified version of the code, which I'll show just for `` - you'd want to extend this for all title tags, i.e. `` through ``:
```jsx
import Link from 'next/link';
const CustomH1 = ({ id, ...rest }) => {
if (id) {
return (
);
}
return ;
};
const components = {
h1: CustomH1,
};
// this would also work in pages/_app.js
const Layout = ({ children }) => {
return {children} ;
};
```
### Doing it with Chakra UI
Like I mentioned above, my site uses Chakra UI to compose page layouts. I've added a bit of customization to links on my site - including a hover behavior which adds a nice `#` character before headings when they're hovered over. If you're curious about [my implementation](https://github.com/mbifulco/blog/pull/577) with Chakra UI, it looks a bit like this:
```jsx
import NextLink from 'next/link';
import { Heading, Link } from '@chakra-ui/react';
const CustomHeading = ({ as, id, ...props }) => {
if (id) {
return (
);
}
return A fish called wanda
```
I hope you found this helpful! If you run into any trouble, feel free to [drop me a line on twitter](https://twitter.com/irreverentmike). Beyond that, I'd love it if you shared this post with someone who you think could benefit from it.
## Auto-linking headings with other frameworks
- Generic **HTML and JavaScript** - if you're looking for a platform-agnostic solution, you may want to check out this CSS Tricks Article, [On Adding IDs to Headings](https://css-tricks.com/on-adding-ids-to-headers/)
- **Jekyll** - a reader was kind enough to send me a tutorial for the same functionality in [Jekyll](https://jekyllrb.com/). Check it out on [David Darnes](https://twitter.com/DavidDarnes)' site here: [Adding heading links to your Jekyll blog](https://darn.es/adding-heading-links-to-your-jekyll-blog/)
- **11ty** - There doesn't seem to be a standard practice for this pattern with [11ty](https://11ty.dev/), but there was a great discussion on ways this might be implemented with plugins and shortcodes in this GitHub Issue: [Support generating IDs for headings, for section direct links ](https://github.com/11ty/eleventy/issues/1593)
- **Gatsby** - [Gatsby](https://www.gatsbyjs.org/) has a plugin which supports this behavior, called [gatsby-remark-autolink-headers](https://www.gatsbyjs.com/plugins/gatsby-remark-autolink-headers/)
## More reading
If you found this helpful, you may also be interested in:
- [JavaScript Tips: Nullish Coalescing (??)](https://mikebifulco.com/posts/nullish-coalescing-javascript)
- [JavaScript Tips: Using Array.filter(Boolean)](https://mikebifulco.com/posts/javascript-filter-boolean)
- [MDX: I should have done this sooner](https://mikebifulco.com/posts/moving-to-mdx)
]]>
`, ``, and `` in html) will be be wrapped in links that point to themselves. This allows readers to link to _specific_ headings in your articles, jumping to relevant bits of content without forcing someone to read through an entire article. Generally speaking, it will look something like this:
```html
My first blog post
```
The `` tag here has an `href` value of `#some-unique-id` - this is the id of the heading tag. This is based on an HTML [standard defined by the W3C](https://www.w3.org/TR/html401/struct/links.html#h-12.2.3). In short, you can link to any element on an HTML page which has a unique `id` attribute defined, by appending `#[id]` to the end of the URL, like `www.example.com#id-of-the-element`.
## This is tricky with Markdown and MDX
In most static site generators and JAMStack frameworks which allow you to use Markdown and MDX to generate content, the goal is simple: give authors a _very_ simple way to author content using Markdown syntax. The unfortunate side effect in this case is that there's not a way to specify IDs for the headings in Markdown posts (at least, not one that I'm aware of).
A sample markdown post might look like this:
```md
---
title: Hello, world
---
# A fish called wanda
In this essay, I will explain the difference between...
```
This results in the following output:
```html
A fish called wanda
In this essay, I will explain the difference between...
```
Fantastic! That's a nice, easy way to write, but there's not a way to add an id to the heading tag. At least, not out of the box. This is where MDX's plugins come in handy.
## Automatically linking to headings in your mdx posts with rehype plugins
> _Note: This tutorial assumes you're using MDX with NextJS, althought it may be applicable to other systems. Feel free to [send me](https://twitter.com/irreverentmike) any hurdles you encounter with other frameworks, and I'll try to document them here._
### Step 1: Generate IDs for all headings automatically with rehype-slug
[`rehype-slug`](https://github.com/rehypejs/rehype-slug) is a plugin that works with MDX, and will automatically generate IDs for your headings by generating a slug based on the text they contain.
1. Install `rehype-slug` in your project by running `npm install --save rehype-slug` or `yarn add rehype-slug`
2. Add `rehype-slug` to the list of rehype plugins MDX uses. In the case of next.js sites, it is likely wherever you call `serialize()` from `next-mdx-remote`.
```jsx
import rehypeSlug from 'rehype-slug';
// ...
const options = {
mdxOptions: {
rehypePlugins: [
rehypeSlug, // add IDs to any h1-h6 tag that doesn't have one, using a slug made from its text
],
},
};
const mdxSource = await serialize(post.content, options);
// ...
```
**Note:** My site uses `serialize()` in several places, so I extracted `options` to its own file. This avoids repeated code, and allows me to manage my plugins for MDX from one place.
At this point, if you fire up your dev environment, and use your browser devtools to inspect any of the headings generated from markdown for your site, they should all have an `id` property added. For the example above, you'd see:
```html
A fish called wanda
```
We're halfway there - you can now link to `www.example.com#a-fish-called-wanda`, and the browser will automatically scroll to the heading.
### Step 2: use MDXProvider to customize the way heading tags render
[MDXProvider](https://mdxjs.com/docs/using-mdx/#mdx-provider) is a wrapper component which allows you to customize the way your MDX renders by providing a list of `components`.
This step will depend heavily on the UI frameworks you've chosen for your site - I use [Chakra UI](https://chakra-ui.com/) for my nextjs site, but you can use whatever you like - [tailwindcss](https://tailwindcss.com/), [Material UI](https://mui.com/), etc will all have similar parallels.
Here's a simplified version of the code, which I'll show just for `` - you'd want to extend this for all title tags, i.e. `` through ``:
```jsx
import Link from 'next/link';
const CustomH1 = ({ id, ...rest }) => {
if (id) {
return (
);
}
return ;
};
const components = {
h1: CustomH1,
};
// this would also work in pages/_app.js
const Layout = ({ children }) => {
return {children} ;
};
```
### Doing it with Chakra UI
Like I mentioned above, my site uses Chakra UI to compose page layouts. I've added a bit of customization to links on my site - including a hover behavior which adds a nice `#` character before headings when they're hovered over. If you're curious about [my implementation](https://github.com/mbifulco/blog/pull/577) with Chakra UI, it looks a bit like this:
```jsx
import NextLink from 'next/link';
import { Heading, Link } from '@chakra-ui/react';
const CustomHeading = ({ as, id, ...props }) => {
if (id) {
return (
);
}
return A fish called wanda
```
I hope you found this helpful! If you run into any trouble, feel free to [drop me a line on twitter](https://twitter.com/irreverentmike). Beyond that, I'd love it if you shared this post with someone who you think could benefit from it.
## Auto-linking headings with other frameworks
- Generic **HTML and JavaScript** - if you're looking for a platform-agnostic solution, you may want to check out this CSS Tricks Article, [On Adding IDs to Headings](https://css-tricks.com/on-adding-ids-to-headers/)
- **Jekyll** - a reader was kind enough to send me a tutorial for the same functionality in [Jekyll](https://jekyllrb.com/). Check it out on [David Darnes](https://twitter.com/DavidDarnes)' site here: [Adding heading links to your Jekyll blog](https://darn.es/adding-heading-links-to-your-jekyll-blog/)
- **11ty** - There doesn't seem to be a standard practice for this pattern with [11ty](https://11ty.dev/), but there was a great discussion on ways this might be implemented with plugins and shortcodes in this GitHub Issue: [Support generating IDs for headings, for section direct links ](https://github.com/11ty/eleventy/issues/1593)
- **Gatsby** - [Gatsby](https://www.gatsbyjs.org/) has a plugin which supports this behavior, called [gatsby-remark-autolink-headers](https://www.gatsbyjs.com/plugins/gatsby-remark-autolink-headers/)
## More reading
If you found this helpful, you may also be interested in:
- [JavaScript Tips: Nullish Coalescing (??)](https://mikebifulco.com/posts/nullish-coalescing-javascript)
- [JavaScript Tips: Using Array.filter(Boolean)](https://mikebifulco.com/posts/javascript-filter-boolean)
- [MDX: I should have done this sooner](https://mikebifulco.com/posts/moving-to-mdx)
]]>
` in html) will be be wrapped in links that point to themselves. This allows readers to link to _specific_ headings in your articles, jumping to relevant bits of content without forcing someone to read through an entire article. Generally speaking, it will look something like this:
```html
My first blog post
```
The `` tag here has an `href` value of `#some-unique-id` - this is the id of the heading tag. This is based on an HTML [standard defined by the W3C](https://www.w3.org/TR/html401/struct/links.html#h-12.2.3). In short, you can link to any element on an HTML page which has a unique `id` attribute defined, by appending `#[id]` to the end of the URL, like `www.example.com#id-of-the-element`.
## This is tricky with Markdown and MDX
In most static site generators and JAMStack frameworks which allow you to use Markdown and MDX to generate content, the goal is simple: give authors a _very_ simple way to author content using Markdown syntax. The unfortunate side effect in this case is that there's not a way to specify IDs for the headings in Markdown posts (at least, not one that I'm aware of).
A sample markdown post might look like this:
```md
---
title: Hello, world
---
# A fish called wanda
In this essay, I will explain the difference between...
```
This results in the following output:
```html
A fish called wanda
In this essay, I will explain the difference between...
```
Fantastic! That's a nice, easy way to write, but there's not a way to add an id to the heading tag. At least, not out of the box. This is where MDX's plugins come in handy.
## Automatically linking to headings in your mdx posts with rehype plugins
> _Note: This tutorial assumes you're using MDX with NextJS, althought it may be applicable to other systems. Feel free to [send me](https://twitter.com/irreverentmike) any hurdles you encounter with other frameworks, and I'll try to document them here._
### Step 1: Generate IDs for all headings automatically with rehype-slug
[`rehype-slug`](https://github.com/rehypejs/rehype-slug) is a plugin that works with MDX, and will automatically generate IDs for your headings by generating a slug based on the text they contain.
1. Install `rehype-slug` in your project by running `npm install --save rehype-slug` or `yarn add rehype-slug`
2. Add `rehype-slug` to the list of rehype plugins MDX uses. In the case of next.js sites, it is likely wherever you call `serialize()` from `next-mdx-remote`.
```jsx
import rehypeSlug from 'rehype-slug';
// ...
const options = {
mdxOptions: {
rehypePlugins: [
rehypeSlug, // add IDs to any h1-h6 tag that doesn't have one, using a slug made from its text
],
},
};
const mdxSource = await serialize(post.content, options);
// ...
```
**Note:** My site uses `serialize()` in several places, so I extracted `options` to its own file. This avoids repeated code, and allows me to manage my plugins for MDX from one place.
At this point, if you fire up your dev environment, and use your browser devtools to inspect any of the headings generated from markdown for your site, they should all have an `id` property added. For the example above, you'd see:
```html
A fish called wanda
```
We're halfway there - you can now link to `www.example.com#a-fish-called-wanda`, and the browser will automatically scroll to the heading.
### Step 2: use MDXProvider to customize the way heading tags render
[MDXProvider](https://mdxjs.com/docs/using-mdx/#mdx-provider) is a wrapper component which allows you to customize the way your MDX renders by providing a list of `components`.
This step will depend heavily on the UI frameworks you've chosen for your site - I use [Chakra UI](https://chakra-ui.com/) for my nextjs site, but you can use whatever you like - [tailwindcss](https://tailwindcss.com/), [Material UI](https://mui.com/), etc will all have similar parallels.
Here's a simplified version of the code, which I'll show just for `` - you'd want to extend this for all title tags, i.e. `` through ``:
```jsx
import Link from 'next/link';
const CustomH1 = ({ id, ...rest }) => {
if (id) {
return (
);
}
return ;
};
const components = {
h1: CustomH1,
};
// this would also work in pages/_app.js
const Layout = ({ children }) => {
return {children} ;
};
```
### Doing it with Chakra UI
Like I mentioned above, my site uses Chakra UI to compose page layouts. I've added a bit of customization to links on my site - including a hover behavior which adds a nice `#` character before headings when they're hovered over. If you're curious about [my implementation](https://github.com/mbifulco/blog/pull/577) with Chakra UI, it looks a bit like this:
```jsx
import NextLink from 'next/link';
import { Heading, Link } from '@chakra-ui/react';
const CustomHeading = ({ as, id, ...props }) => {
if (id) {
return (
);
}
return A fish called wanda
```
I hope you found this helpful! If you run into any trouble, feel free to [drop me a line on twitter](https://twitter.com/irreverentmike). Beyond that, I'd love it if you shared this post with someone who you think could benefit from it.
## Auto-linking headings with other frameworks
- Generic **HTML and JavaScript** - if you're looking for a platform-agnostic solution, you may want to check out this CSS Tricks Article, [On Adding IDs to Headings](https://css-tricks.com/on-adding-ids-to-headers/)
- **Jekyll** - a reader was kind enough to send me a tutorial for the same functionality in [Jekyll](https://jekyllrb.com/). Check it out on [David Darnes](https://twitter.com/DavidDarnes)' site here: [Adding heading links to your Jekyll blog](https://darn.es/adding-heading-links-to-your-jekyll-blog/)
- **11ty** - There doesn't seem to be a standard practice for this pattern with [11ty](https://11ty.dev/), but there was a great discussion on ways this might be implemented with plugins and shortcodes in this GitHub Issue: [Support generating IDs for headings, for section direct links ](https://github.com/11ty/eleventy/issues/1593)
- **Gatsby** - [Gatsby](https://www.gatsbyjs.org/) has a plugin which supports this behavior, called [gatsby-remark-autolink-headers](https://www.gatsbyjs.com/plugins/gatsby-remark-autolink-headers/)
## More reading
If you found this helpful, you may also be interested in:
- [JavaScript Tips: Nullish Coalescing (??)](https://mikebifulco.com/posts/nullish-coalescing-javascript)
- [JavaScript Tips: Using Array.filter(Boolean)](https://mikebifulco.com/posts/javascript-filter-boolean)
- [MDX: I should have done this sooner](https://mikebifulco.com/posts/moving-to-mdx)
]]>
` through ``:
```jsx
import Link from 'next/link';
const CustomH1 = ({ id, ...rest }) => {
if (id) {
return (
);
}
return ;
};
const components = {
h1: CustomH1,
};
// this would also work in pages/_app.js
const Layout = ({ children }) => {
return {children} ;
};
```
### Doing it with Chakra UI
Like I mentioned above, my site uses Chakra UI to compose page layouts. I've added a bit of customization to links on my site - including a hover behavior which adds a nice `#` character before headings when they're hovered over. If you're curious about [my implementation](https://github.com/mbifulco/blog/pull/577) with Chakra UI, it looks a bit like this:
```jsx
import NextLink from 'next/link';
import { Heading, Link } from '@chakra-ui/react';
const CustomHeading = ({ as, id, ...props }) => {
if (id) {
return (
);
}
return A fish called wanda
```
I hope you found this helpful! If you run into any trouble, feel free to [drop me a line on twitter](https://twitter.com/irreverentmike). Beyond that, I'd love it if you shared this post with someone who you think could benefit from it.
## Auto-linking headings with other frameworks
- Generic **HTML and JavaScript** - if you're looking for a platform-agnostic solution, you may want to check out this CSS Tricks Article, [On Adding IDs to Headings](https://css-tricks.com/on-adding-ids-to-headers/)
- **Jekyll** - a reader was kind enough to send me a tutorial for the same functionality in [Jekyll](https://jekyllrb.com/). Check it out on [David Darnes](https://twitter.com/DavidDarnes)' site here: [Adding heading links to your Jekyll blog](https://darn.es/adding-heading-links-to-your-jekyll-blog/)
- **11ty** - There doesn't seem to be a standard practice for this pattern with [11ty](https://11ty.dev/), but there was a great discussion on ways this might be implemented with plugins and shortcodes in this GitHub Issue: [Support generating IDs for headings, for section direct links ](https://github.com/11ty/eleventy/issues/1593)
- **Gatsby** - [Gatsby](https://www.gatsbyjs.org/) has a plugin which supports this behavior, called [gatsby-remark-autolink-headers](https://www.gatsbyjs.com/plugins/gatsby-remark-autolink-headers/)
## More reading
If you found this helpful, you may also be interested in:
- [JavaScript Tips: Nullish Coalescing (??)](https://mikebifulco.com/posts/nullish-coalescing-javascript)
- [JavaScript Tips: Using Array.filter(Boolean)](https://mikebifulco.com/posts/javascript-filter-boolean)
- [MDX: I should have done this sooner](https://mikebifulco.com/posts/moving-to-mdx)
]]>
A fish called wanda
``` I hope you found this helpful! If you run into any trouble, feel free to [drop me a line on twitter](https://twitter.com/irreverentmike). Beyond that, I'd love it if you shared this post with someone who you think could benefit from it. ## Auto-linking headings with other frameworks - Generic **HTML and JavaScript** - if you're looking for a platform-agnostic solution, you may want to check out this CSS Tricks Article, [On Adding IDs to Headings](https://css-tricks.com/on-adding-ids-to-headers/) - **Jekyll** - a reader was kind enough to send me a tutorial for the same functionality in [Jekyll](https://jekyllrb.com/). Check it out on [David Darnes](https://twitter.com/DavidDarnes)' site here: [Adding heading links to your Jekyll blog](https://darn.es/adding-heading-links-to-your-jekyll-blog/) - **11ty** - There doesn't seem to be a standard practice for this pattern with [11ty](https://11ty.dev/), but there was a great discussion on ways this might be implemented with plugins and shortcodes in this GitHub Issue: [Support generating IDs for headings, for section direct links ](https://github.com/11ty/eleventy/issues/1593) - **Gatsby** - [Gatsby](https://www.gatsbyjs.org/) has a plugin which supports this behavior, called [gatsby-remark-autolink-headers](https://www.gatsbyjs.com/plugins/gatsby-remark-autolink-headers/) ## More reading If you found this helpful, you may also be interested in: - [JavaScript Tips: Nullish Coalescing (??)](https://mikebifulco.com/posts/nullish-coalescing-javascript) - [JavaScript Tips: Using Array.filter(Boolean)](https://mikebifulco.com/posts/javascript-filter-boolean) - [MDX: I should have done this sooner](https://mikebifulco.com/posts/moving-to-mdx) ]]>## So yeah, I'm back at it again... I recently started streaming again on the weekends - this time it's not the work I'm doing in my day-to-day at Google, but instead my personal projects which are all OSS. It's a great way to get back into coding for enjoyment, and to force myself to deliver results... I can crank out 2-3 hours of really good work when I'm on stream without getting (too) distracted. If you want to catch some of that, you can find me on twitch at https://www.twitch.tv/irreverentmike ]]>
Hi {name ? name : 'there'},
;
};
const BetterLetterIntro = ({ name }) => {
return Hi {name ?? 'there'}
;
};
```
Both of these are _valid_ syntax, but you might argue that the latter is easier to read, so long as you understand what the `??` operator is doing.
## Make sure to check compatibility on your project
Nullish coalescing is quickly becoming available for use in browsers and JavaScript / Node / Deno, but you should make sure that the project you're working on is using a compatible version of the language before you start to add `??` to all your code.
## Compatibility with Node and Deno
To ensure compatibility with Node, your project must be using **Node version 14.0.0** or later.
To ensure compatibility with Deno, you rproject must be using **Deno version 1.0.0** or later.
## Compatibility with modern browsers
Another thing to condier - as of the writing of this article, Nullish Coalescing isn't available in every web browser quite yet - Internet Explorer and Opera for Android are the two remaining holdouts. I'll leave it to you to decide whether or not that's a showstopper for you - and I don't know if I'd expect to see support in IE _ever_ given its [end-of-life](https://docs.microsoft.com/en-us/lifecycle/announcements/internet-explorer-11-end-of-support) announcement in mid 2021.
-
{people.map(person) => {
// this will crash if there's a null/undefined in the list!
return (
- {person.name}: {person.email} ); }}
-
{people
.filter(Boolean) // this _one weird trick!_
.map(person) => {
return (
- {person.name}: {person.email} ); } }
Fo ipsum dolor tellivizzle amet, my shizz adipiscing shizzle my nizzle crocodizzle. Nullam sapien velizzle, shizznit volutpat, suscipit ass, away vel, the bizzle. Dizzle fo shizzle tortizzle. Sizzle erizzle. Fusce izzle dolizzle dapibus fizzle tempus dope. Maurizzle pellentesque hizzle et turpis. Shiznit check out this fo shizzle. Pellentesque eleifend rhoncizzle shiznit. In hac habitasse platea dictumst. Donec dapibizzle. Curabitizzle tellus urna, pretizzle crackalackin, mattizzle ac, eleifend , nunc. Nizzle suscipizzle. Integizzle rizzle you son of a bizzle sizzle mofo.
Dizzle ut dolizzle. Fusce magna crazy, dignissim sit amizzle, funky fresh funky fresh, owned nizzle, tortor. Maecenas a nisi. Tellivizzle ghetto neque izzle get down get down. Shut the shizzle up stuff. Cras aliquet tristique turpizzle. Suspendisse gizzle ultricizzle dope. Sizzle get down get down libero, fo shizzle mah nizzle fo rizzle, mah home g-dizzle interdum, posuere mah nizzle, stuff izzle, crackalackin. Da bomb mofo tellizzle. Boom shackalack aliquizzle gangster sizzle amet dolor. For sure dapibizzle sheezy id mah nizzle. Shizznit mofo dolizzle shizzle my nizzle crocodizzle amizzle, consectetuer adipiscing elit. Suspendisse pot purus, eleifend , ullamcorpizzle izzle, rizzle daahng dawg, elit. Nizzle porta rutrum nunc.
...react component markup
; }; ``` There's a combination of things happening in the definition of the `singlePage` React component. Let's look at just that destructure, and simplify it a bit: ```jsx const { data, location, pageContext: { nextPagePath, previousPagePath }, } = props; ``` It took some staring, and some playing around to figure out what was being accomplished here, so let's run through it step by step: 1. The right side of this `const` is `= props` which tells us that all of these values are being destructured from an object called `props` . 2. The first two values, `data` and `location` make good sense - they look just like the examples above. This line will create a `const` from each of those two paths in the `props` object. 3. `pageContext` is where things get interesting - this is _another_ destructuring. Somewhat confusingly, the values that are being pulled from `props` here are `nextPagePath` and `previousPagePath` . There is no variable being created for `pageContext` . If that description didn't help - I don't blame you. It really took some practice for me to understand what's going on. I'm not even sure I would recommend using this syntax - it's not particularly easy to read, especially when tools like `prettier` squish it onto fewer lines. With that said, it seems to be the way-to-go when pulling data from GraphQL queries on Gatsby (and likely elsewhere). If you're going to be working in that world, it's a good idea to familiarize yourself with what's going on here. ## Homework I think the best way to get used to this syntax is just play around with it yourself. I've created a JSBin which you can use to experiment a bit. I'd love to hear how you do with it! [Check it out here](https://jsbin.com/kifizij/2/edit?js,console). Some challenges for you: - Rename the variable `displayName` to `currentUserName` - Extract `editedBy` into its own variable - Create an object called `meta` which contains everything in `directions` except for the `contactNumber` ## Wrapping up I'd love to hear how you fare with this - I found myself writing this post as a matter of self-help. Often times these things won't be made concrete until I practice in isolation for a while. What creative uses do you have for destructuring? Did I get anything wrong here? Let's talk about it. ]]>Ana Paes on Unsplash } /> If you take apart a Yeti, underneath that chic metal-grate dome, you'll actually find 3 microphone capsules - none of them pointed upwards. There is no combination of settings on the Yeti that will yield great audio if you're speaking into the top of the device. If you ask me (and you do), this isn't user error. The physical design of these types of microphones is ambiguous enough that their proper use isn't apparent. Folks who buy a Yeti are generally only exposed to microphones with a drastically different form factor - how are they supposed to know better? ## What to do about it At some level, as long as they're selling like gangbusters, there's nothing that should motivate Blue to ever change the sleek design of their Yeti. In fact, they've expanded their Yeti lineup since its inception. You'll notice this design challenge is now present across a good few of [Blue's microphones](https://www.bluemic.com/en-us/).
Turn your ideas into high-quality 3D assets faster, including product visualization, interior and home design, gaming, film, VR/AR, digital twins, robotics simulation, and interactive experiences. This is one reason I try not to say "users" when I can avoid it. The problem isn't with the word itself - but rather that it adds a layer of euphemism between designers and the _people_ they are trying to build for. It's a small abstraction that cuts both ways; at times designers say "users" to sound smart, and in other moments "users" is a way to forget the reality that there are people on the other side of these screens. The _person_ on the other side of the black mirror is probably busy. They may be distracted. They may be skeptical. They may be trying to get something done while their kid asks for a snack, their dog barks at the mailman, and their coffee gets cold. If you want to build good products, you have to keep remembering to [imagine others complexly](https://en.wikipedia.org/wiki/Wikipedia:Imagine_others_complexly). ## Except When You Are Every once in a while, though, you really are building for yourself. That's how my project [Guithub](https://guithub.org) started. Guithub is an online guitar tuner I recently built and published for myself ("recently" is doing a lot of work here. I've owned the domain since 2020, which means this tiny side project managed to take me roughly six years to finish!). I play guitar and sing, and for years I played a couple times a month at bars around town. Like most guitar players, I own tuners. They're fine - "does what it says on the tin", as they say, but for the most part they're designed to be _generically_ useful for a wide range of musicians in a wide range of contexts. Tuners have always bothered me in a few specific ways: Tuners are built around standard guitar tuning (EADGBE). Most assume you are tuning open strings. If you put a capo on after tuning, it starts to sound a little weird the further you move up the neck. And if, hypothetically, you play a lot of songs in alternate tunings because you spent too much time listening to _Bon Iver_ or _The Tallest Man on Earth_, you end up doing more mental translation than you want to do while standing in front of people. I also usually play with a laptop or tablet in front of me, with chord charts and lyrics - because I just don't have it all memorized. All this to say: a tuner _built for me_ isn't complicated -- but it _is_ fairly different from the one you'll pull out of the box from your local guitar shop. I wanted a tuner that worked the way I actually play. I wanted to open a browser, pick an instrument, pick a tuning, set a capo position, and get back to playing. That was the whole idea. Not a universal tuner for every musician in every context: a tuner for me. ## The Six-Year Side Project The annoying thing about Guithub is that I understood the basic problem pretty well. I studied computer science and mechanical engineering, so the math and physics behind a tuner are not especially mysterious. You listen to a sound, find the fundamental frequency, map that frequency to a note, and tell the musician whether they are sharp or flat. That sounds straightforward until you try to make it work in a browser, on real devices, in real rooms, with real instruments. Sound is messy. Instruments produce harmonics. Microphones vary wildly. Rooms are noisy. Browsers have their own constraints. And there is a big difference between understanding a Fourier transform and building a pitch detector that feels fast and reliable enough to trust. The first version I built could identify notes reasonably well, but not well enough that I would have wanted to use it on stage. So the project sat there for years, in the extremely crowded drawer where I keep ideas that are "basically working" and therefore nowhere near done. Then, eventually, I had the embarrassingly obvious thought that there might already be an npm package for this. Of course there was. With a library handling the core pitch detection, and an LLM helping me wire things together and test the important paths, I finally got past the part that had kept me stuck. That freed me up to work on the actual product. The product was never "can I implement signal processing from scratch?" The product was "can I tune quickly and get back to the song?" That distinction matters. A lot of side projects get stuck because the interesting technical problem disguises itself as the product. Sometimes it is. Often it's just the thing standing between you and the product. ## The Homepage Is the Product Because Guithub is built for the exact situation I kept running into, the homepage is the product. There is no ceremony: go to [guithub.org](https://guithub.org), modify default settings if you need to, and get to tuning. It supports guitar, bass, banjo, and ukulele. It supports different tunings. It supports capo positions. It is meant to be useful on the device I probably already have in front of me when I am playing. I have tried not to turn it into a fluffy product homepage, even though search engines and LLM indexers would prefer that. It's a funny tension: SEO wants explanation, but a great product experience is (in this case) just the thing itself. For this project, I'm trying to let the tool win. The best version of Guithub is not impressive. It's forgettable in the right way. It opens quickly, helps you tune, and lets you move on with your life. That is what I wanted as a musician - and if that's what other guitarists want, I'll be super happy to see it. ## Build the Thing That Keeps Bothering You This is the part where "you are not your user" gets complicated. You should not assume everyone is like you. That's a path to misguided products, confusing defaults, and founders confidently explaining that customers are wrong for not understanding the brilliant thing they built. But... _sometimes_ your own frustration is a useful starting point. Not because it makes you representative of the whole audience, but because it gives you access to details and compassion that are hard to fake. You have _felt_ existing options fail you. You know which parts are merely annoying and which parts actually matter. You know the little moment where you mutter under your breath and think, "why does this work this way?" That moment is worth paying attention to. [Craftwork](https://craftwork.com) came from a version of this too. Finding a reliable, professional, high-quality painting company for your home should not feel like a gamble, but it often does. That frustration was specific enough to give us a place to start. Specific frustration is not the same thing as product-market fit. It's not proof that other people care. It's not a business model. It's not distribution. But: it _is_ a signal. Sometimes the thing that keeps bothering you is just a thing that keeps bothering you. Sometimes it's the first draft of something useful. --- ## Guitarists, try my sweet tuner If you play music ([_like me!_](https://guithub.org/about)), I would love for you to try [Guithub](https://guithub.org). And if it breaks, annoys you, or gets in your way, please tell me. You can reply here or email me at [hello@mikebifulco.com](mailto:hello@mikebifulco.com). ]]>
## The Zeroth Loop: Before the First Use
The first encounter with a product usually happens in the wild: a landing page, a demo video, or a screenshot shared on social media.
The strongest marketing moments already contain a full behavior loop. When you watch a great 15-second demo, your brain performs a dry run. You see the cue, you recognize the action, and you anticipate the reward.
A good demo doesn't just explain features; it allows the user to experience the payoff ahead of time. By the time they click "Sign Up," the habit loop already exists in outline form. The **Zeroth Loop** has already closed.
## Where Your Products Lose Momentum
Product people tend to spend loads of time planning and building the nuts-and-bolts of how our apps work. We spend hours designing the perfect onboarding flow, the perfect settings page, the perfect error message.
Marketing people tend to think about the moments _before_ features matter - how do people find and engage with your product in the first place?
These two perspectives are hugely important, and they need to work together. Neither is optional for your product to be successful.
Builders who don't have marketing chops tend to overestimate intent. We see a signup as commitment, but often it's just curiosity. If a person's first interaction with your product doesn't produce a clear, immediate reward, the behavior never stabilizes.
When this happens, nothing _really_ breaks. The app just fades into the background. It stays installed, the tab stays open, and the user simply forgets it exists.
The habit never formed, and all your work goes to waste.
## Systems Over Memory
This is why thoughtful nudges are so important. Reminders often get a bad reputation because they're implemented poorly, but their cognitive role is simple: they reintroduce the cue before a new routine vanishes from memory.
` and other HTML elements, so this library is a huge benefit for us.
- I've spent quite a bit of time usingtThe Typescript SDK for the [Model Context Protocol (MCP)](https://github.com/modelcontextprotocol/typescript-sdk) as research for connecting AI tools to Craftwork's business logic; I think it's safe to say that I'm squarely in the _early adopted_ phase for this library. It's been a bit bumpy, but it's been evolving quickly.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[AI Prompt Secrets - what the leaks tell us]]>
https://mikebifulco.com/newsletter/learn-from-llms-leaking-their-prompts
https://mikebifulco.com/newsletter/learn-from-llms-leaking-their-prompts
Tue, 13 May 2025 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[I want to feel the hand of the f%#king creator]]>
https://mikebifulco.com/newsletter/passion-and-the-hand-of-the-creator
https://mikebifulco.com/newsletter/passion-and-the-hand-of-the-creator
Thu, 08 May 2025 00:00:00 GMT
Brought to you by Paddle
## Go on, put your back into it
North Carolina summers are like being slowly baked inside a damp sock. Triple-digit heat. Humidity so thick you could bottle it and sell it as soup. It’s the kind of weather that makes you question your life choices.
But the moment you step into a perfectly air-conditioned room: one that hits you with that crisp, fresh chill on a blistering day - that is what salvation feels like. Not just relief, but a stark, physical reminder of the incredible effort that has gone into the built environment.
Now and then, I get the same feeling from software, too. When someone really puts every bit of their intellectual might into making something that feels _alive_.
### Creative works that just feel different
**[Blue Prince](https://www.blueprincegame.com/)** and **[Animal Well](https://www.animalwell.net/)** are two recent games that twist themselves into meta-puzzles, daring you to notice every pixel. I hardly play games at all nowadays, but I can feel the love in every corner of these worlds. It’s intoxicating.
**Small touches added to Android** - instant translation of any text on any screen (even from an image!), no app-switching needed. Spam calls? Silenced. Texts from bots? Blocked. It feels like magic, but it’s just good design.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Serendipity isn't an accident]]>
https://mikebifulco.com/newsletter/serendipity-isnt-an-accident
https://mikebifulco.com/newsletter/serendipity-isnt-an-accident
Tue, 29 Apr 2025 00:00:00 GMT
Brought to you by Paddle
Opportunities don't "just happen" - they come from staying connected, helping others generously, and trusting your instincts when the right path shows up.
## Serendipity isn't magic
Opportunities don't "just happen" - they come from staying connected, helping others generously, and trusting your instincts when the right path shows up.
Years ago, when I was fresh out of college and living on my own for the first time, I read a book called _Never Eat Alone,_ by Keith Ferrazzi.
I don’t agree with everything in it - the title alone feels a little over the top - but the core idea stuck with me: Stay connected. Help when you can. Introduce people who can help each other.
I've carried that theme with me ever since.
Whether it’s friends, colleagues, or online pals (like the [developer community](https://apisyouaonthate.com) I run with two people I've never met in person), I try to be helpful when I can - without keeping score.
## Choosing to be helpful
Around 2018, I had the opportunity to watch some friends complete the Techstars startup accelerator, where I picked up another mantra:
_Give without the expectation of receiving._
Many people people are doing mental accounting all the time - who owes who what, who's "worth it." It's exhausting. For me, it misses the point.
The people I've encountered who seem to have endless opportunity around them are the ones who _help_ first, without asking what’s in it for them.
## Some people do suck
This is important - **you don't owe everyone your time.**
If someone makes a habit of taking advantage, wasting your energy, or treating you poorly, you are not obligated to stay engaged. Good faith should be earned - and kept.
Trust your internal barometer, use your powers for good.
### A framework for building your own luck
- Help people when you can. Make intros. Cheer people on. Share what you genuinely admire.
- Be open to new people and ideas. Take introductions seriously - you never know which one will change your life.
- Trust your instincts. Only you know the full context of your life and goals. When something feels right, follow it.
Most of all, **protect your time**. Being generous doesn’t mean being a doormat.
Serendipity isn’t magic. It’s built by your choices and actions over a longer period of time than you might expect.
---
## From Idea to Exit: SaaS Founders Spill Their Secrets
Why do some SaaS ideas soar while others stall? Paddle's panel of seasoned SaaS founders will talk on idea validation, bootstrapping vs VC funding, scaling tactics & hard-won lessons. It’s a founder therapy session disguised as a webinar.
**📆 Live Webinar**: April 30, 12–1pm EDT
[Save your seat](https://www.paddle.com/events/webinars/lessons-from-saas-founders-whove-done-it?utm_medium=website&utm_source=partner&utm_campaign=webinars_fy2025_q2_core_fireside_founder_chat_30apr&utm_content=tiny-improvements)
---
## What I'm reading
**[Never Eat Alone](https://amzn.to/4cSy23f)** by Keith Ferrazzi, helped forge my outlook on building a strong network, as a bright eyed college grad.
I just finished **[Careless People](https://amzn.to/3GubN7A)**, a memoir by Facebook's first Director of Public Policy. It is a gut-punch of a book, divulging some serious details about the casual relationship that Zuck and company had with ethics as they grew to an incomprehensibly large company. The book had me doing karate kicks in my living room.
A while back, I published a treatise on hiring called **[Your Resume Sucks](https://mikebifulco.com/newsletter/your-resume-sucks)**. A reader this week reached out with a great example of someone going the distance to stand out from other applicants: check out [The unhinged application I used to get a job at a fast-growing startup](https://userobsession.substack.com/p/the-unhinged-application-i-used-to) from Finn Lobsien.
Shout out to Rusty in Seattle for sharing!
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Freedom is a Feature: why competition is a good thing]]>
https://mikebifulco.com/newsletter/freedom-is-a-feature
https://mikebifulco.com/newsletter/freedom-is-a-feature
Tue, 22 Apr 2025 00:00:00 GMT
Brought to you by Paddle
**Freedom builds trust.** People don’t want to feel trapped by the products they use. In an ecosystem full of walled gardens, openness and interoperability are your competitive advantage.
---
## Freedom Is a Feature
**Platform lock-in is one of the tools of the trade for companies building products without a real moat.**
If you can’t win on quality or experience, maybe you can trap people just long enough to squeeze some revenue out of them.
But people feel it: Lock-in creates friction; it quietly drains trust.
The better path? Leave the door open, and make a product so good people don't want to leave.
### Enter MCP
That’s what makes **MCP** such a fascinating case study.
Introduced by Anthropic in 2024, **MCP (Model Context Protocol)** is an open standard that helps developers guide LLM agents to use specific tools and workflows-no more spray-and-pray guessing. It brought structure and predictability to AI automation in a way that hadn’t been possible before.
And crucially: **Anthropic [open-sourced](https://modelcontextprotocol.io/introduction) it.**
This has quickly sparked a shift across the industry. Since its launch in November 2024, MCP has become _the_ way to build reliable, agent-powered workflows.
Adoption has been explosive. It's gained so much traction, so quickly, that every major player has adopted it.
**OpenAI included.**
With $62B in funding and a massive head start (vs. Anthropic’s ~$18B), OpenAI could’ve tried to ignore MCP, or bury it with their own proprietary solution.
Instead, they embraced it.
Supporting MCP was the only reasonable move - and ultimately, a smart one.
**Openness won,** and builders, developers, and end users are all better off for it.
### Meanwhile, in Cupertino…
Apple’s absence from the LLM conversation is starting to look more and more like Microsoft’s infamous fumble on mobile in the early 2000s. Siri has missed the moment - and unless Apple makes a major acquisition soon or has a surprise launch in their back pocket, they may be sitting out the next platform shift entirely. 🍎
---
## From Idea to Exit: SaaS Founders Spill Their Secrets
Why do some SaaS ideas soar while others stall? Paddle's panel of seasoned SaaS founders will talk on idea validation, bootstrapping vs VC funding, scaling tactics & hard-won lessons. It’s a founder therapy session disguised as a webinar.
**📆 Live Webinar**: April 30, 12–1pm EDT
[Save your seat](https://www.paddle.com/events/webinars/lessons-from-saas-founders-whove-done-it?utm_medium=website&utm_source=partner&utm_campaign=webinars_fy2025_q2_core_fireside_founder_chat_30apr&utm_content=tiny-improvements)
---
## 🧠 Further Reading
- [**Model Context Protocol (MCP) Docs**](https://modelcontextprotocol.io/introduction)
The official intro to MCP; it's still early days and these docs are evolving quickly, but they are _the_ place to start.
- [**OpenAI Agents SDK – MCP Support**](https://openai.github.io/openai-agents-python/mcp/)
OpenAI’s implementation of MCP, complete with setup and examples.
- [Google's Agent Development Kit](https://cloud.google.com/blog/products/ai-machine-learning/build-and-manage-multi-system-agents-with-vertex-ai) mentions support for MCP as part of their three-pillar approach to building production AI products.
- 🎙️ [**Accidental Tech Podcast – Ep. 635: An Effective Operator**](https://atp.fm/635)
ATP digs into Apple’s LLM absence, and why it might haunt them long-term. (Marco’s comments on this feel… prophetic.)
---
## Sensing some subtext here?
For my 🇺🇸 readers:
Republicans in Congress have introduced the _SAVE Act_ - a bill that would make it nearly impossible for millions of eligible Americans to register to vote.
This bill would require in-person registration with a passport or birth certificate-which tens of millions of Americans don’t have easy access to. It's not about security. It’s about suppression.
So much for openness and freedom.
They’re counting on you to be too tired, too distracted, or too polite to fight back. Prove them wrong.
Save yourself from the worst type of vendor lock-in imaginable.
Call your goddamn senator, and give 'em hell.
👉 [5calls.org/issue/save-act-voter-suppression](https://5calls.org/issue/save-act-voter-suppression)
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[What to do when the bottom falls out]]>
https://mikebifulco.com/newsletter/what-to-do-when-the-bottom-falls-out
https://mikebifulco.com/newsletter/what-to-do-when-the-bottom-falls-out
Tue, 08 Apr 2025 00:00:00 GMT
Brought to you by Whalesync
---
Last weekend I saw [The Tallest Man on Earth](https://thetallestmanonearth.com/) play in Saxapahaw, NC. It was the first day of the Swedish singer-songwriter's North American tour, at a modest venue in a quaint mill town in the middle of nowhere.
Throughout the show, it ws obvious that he was going through something. Between songs, he talked about how he lived in the US for years, and that it's a country he's always loved - and that it's felt different lately.
I'll second that.
---
## Making a case for doing good things
If you need evidence benevolent behavior is good for business, look at who’s done it before:
- [Ben & Jerry’s](https://www.benjerry.com/values) has built their brand by showing up for people who can’t always speak up for themselves. They've made advocacy part of their product.
- [Notion](https://www.notion.com/product/notion-for-education) gives away tools to students and teachers as part of their mission to help people learn and grow.
- [Fastly](https://www.fastly.com/company)'s devtools platform is accompanied by a strong mission to make the internet a better place.
You don’t need an underground bunker. You just need to be one of the people who gives a damn when things feel uncertain.
This is when it matters most. ✌️
Give 'em hell out there,
- Mike
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Tools I Love - Resend and React Email]]>
https://mikebifulco.com/newsletter/tools-i-love-resend-react-email
https://mikebifulco.com/newsletter/tools-i-love-resend-react-email
Tue, 01 Apr 2025 00:00:00 GMT
I cannot overstate how difficult this process _used_ to be. That 👆🏾 is an extremely ambitious email format to build from scratch.
In the new world of Resend, it's a familiar pattern:
',
to: [email],
subject: "Subscription confirmed. I'm so glad you're here!",
react: WelcomeMessage,
text: await render(WelcomeMessage, { plainText: true }),
});
```
My next.js site is also set up to listen to a few webhooks from Resend, where I can track things like subscription events, opens, unsubscribes, and more.
There's more to it than that, and if you're interested in the nitty-gritty, my site's source code is [available on GitHub for you to check out](https://github.com/mbifulco/blog).
---
## What tools make you look good?
Tips, tricks, and recommendations from my dev-pals is something that I've always loved. When I get around to it, I've got a whole list of recommendations that I'm planning to share -- like the shortcuts I find most helpful with [Raycast](https://www.raycast.com/), and the process I'm using to make Cursor smarter while I code.
I'm really keen to hear from you.
What tools make you look good? What saves you time and makes your life easier? [Send me a note](mailto:hello@mikebifulco.com). I'm all ears!
---
## Some links to keep your brain wrinkling
I'll cop to it: I haven't had a lot of time for things other than work lately. When I have had some time to relax, these videos have stood out from the pack.
- [Frozen orange juice is actually super weird](https://www.youtube.com/watch?v=9wSQ9Zk_9gQ) is a fascinating video essay from Phil Edwards about the surprising economics of something that seems so simple.
- [How do we feel the wind?](https://www.youtube.com/watch?v=Q0_W4SWHeWY) - part of Complexly's recent video series where people ask Hank Green... well, anything. In this edition, musical supergenuis Jacob Collier does the asking. Really, really interesting to see to _absolutely brilliant_ people interact so candidly.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The 3 Mistakes New Creators Make]]>
https://mikebifulco.com/newsletter/mistakes-new-creators-make
https://mikebifulco.com/newsletter/mistakes-new-creators-make
Tue, 25 Mar 2025 00:00:00 GMT
**Do this instead:**
Harness your excitement and energy - use it to make something (a video, a blog post, a podcast, whatever it is you're trying to create), and share it. Then do that again. And again.
Your work will get better, and your audience will grow.
You can't buy creativity -- and you also can't buy more time. Don't waste your time and money on gear until it's the _only_ thing in the way of growth.
### 2. Don't skip the basics: how to find your niche
Many of the folks I talk to want to create something, and they fall on two extremes: (1) they want to create something on a _wide variety_ of topics, or (2) they can't decide what topic they want to create about.
These sound like different problems, but they're both symptoms of the same root cause: a lack of clarity on who you're creating for.
The most successful creators I know have a clear, focused niche, and a deep understanding of their audience.
### 3. There is no bar, but there should be a target
I'm the first to tell you that [there is no bar](https://chriscoyier.net/2022/06/27/there-is-no-bar/) when it comes to creating online. Step one is simple: publish. Put your work out there. Do it often.
Once you've built that habit, try aiming higher: create something a creator you admire would genuinely love. Seriously - keep them in mind as part of your process. When you share work you're proud of, and it resonates enough for someone you look up to to share it, that moment is both validating and a powerful way to grow your voice in your niche.
To be clear: this isn't about spamming people. It's about raising the bar for yourself - making something so thoughtful, useful, or entertaining that it naturally earns attention.
## The Takeaway:
Get good at one thing first. Create. Publish. Share.
Earn your audience, once post at a time. Then, once people care, _maybe_ it's time for the podcast, the YouTube channel, the empire.
Until then: focus.
---
## Some great creators to follow
There is nothing I love more than learning from people smarter than me. Here's a couple of my favorite voices on the internet:
- [Tony Mastrorio](https://www.threads.net/@tonydotcoms) is a fellow YC founder who has been exploring new audiences regularly over the past few months. He's done a great job of sharing his journey on Threads. It's inspiring to see his process: he's trying new things, and sharing them with his audience.
- [Amy Hoy](https://bsky.app/profile/amyhoy.bsky.social) is a great example of someone who has been building online for _years_. She co-created [30x500](https://30x500.com/academy/), and has _deep_ expertise in launching products online. Her Bluesky posts are a masterclass in sharing what she's passionate about - from photography and emerging tech tools to supporting civic engagement and progressive causes.
---
## Some useful links
- The most recent episode of Citation Needed, about [Audie Murphy](https://www.citationpod.com/audie-murphy-the-most-decorated-combat-soldier-of-ww2/) is a great reminder of why I love the podcast so much: I can simultaneously unwind, learn, and laugh a bit.
- There's a [_super important security update_ for Next.js](https://nextjs.org/blog/cve-2025-29927) that you should know about if you're using the framework. Not the type of thing I'd typically share here, but -- this feels like a big one.
---
## Give 'em hell
It might feel like you're paddling a tiny canoe in the shadow of looming battleships - but keep paddling, and stay nimble. There's plenty of room in the pond for all of us.
Bet on yourself. Bet on the people around you.
I'm rooting for you - and I want to see you win. ✌🏾
- M
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Steal these ideas to build new products]]>
https://mikebifulco.com/newsletter/steal-these-ideas-for-your-next-product
https://mikebifulco.com/newsletter/steal-these-ideas-for-your-next-product
Wed, 12 Mar 2025 00:00:00 GMT
Hype
It's tempting to chase AI quick wins, but remember:
- Existing data streams = sustainable business opportunities
- Value-add to available information = competitive edge
- Focused problem-solving > tech novelty
### Case Study: Weather Data
Weather apps are commodity products since [Apple killed Dark Sky](https://www.theverge.com/2020/3/31/21201666/apple-acquires-weather-app-dark-sky-shut-down-android-wear-os-ios) (RIP).
There are plenty of untapped goldmines, like [NOAA](https://www.weather.gov/documentation/services-web-api) and [OpenWeatherMap](https://openweathermap.org/api) data for _specific_ use cases that people will pay for.
**The opportunity:** Niche weather apps for specific use cases:
- For pilots: Visibility conditions and wind patterns
- For gardeners: Frost alerts and growing condition forecasts
- For skiers: Snow quality predictions based on temperature patterns
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Your MVP is too damn big]]>
https://mikebifulco.com/newsletter/your-mvp-is-too-damn-big
https://mikebifulco.com/newsletter/your-mvp-is-too-damn-big
Thu, 06 Mar 2025 00:00:00 GMT
Brought to you by Paddle
## Strip it bare
Earlier this week, I was invited to share my experience building companies with a class of promising entrepreneurship students, enrolled in the [Lean Startup course at Davidson University's Hurt Hub](https://hurthub.davidson.edu/event/building-a-lean-startup/), taught by [Rebecca Weeks Watson](https://www.linkedin.com/in/rebeccaweeks).
Many of them were working through planning out their first business, using a tool called the [Lean Canvas](https://leanstack.com/lean-canvas).
They'd interviewed potential customers and were defining their MVP. Their task: strip the idea to its core to test the riskiest assumption and find what customers would actually pay for.
When you have a big idea, it's tempting to spiral into features and complexity. But you don't need a fully-realized product to test if your idea has legs.
## Why we overreach
Most founders, especially first-timers, mis-scope their MVPs. About half the time, they add _way too much_ to their MVP for it to be built quickly. This is the trap of _it's not ready yet,_ or "if we build it, they will come". I have made this mistake - and I've seen it happen to others.
There's also at tendency to build an MVP that will lead to a `yes` no matter what. This usually means an MVP that's designed to reinforce the founder's belief in their idea, rather than challenge it. After all, founders who have made it this far into the journey of building something _are_ convinced they're onto something meaningful.
Whether they admit it ot not, this sector of founders is often more focused on protecting their ego than validating their idea. Red flag. 🚩
## So what's an MVP for?
There are plenty of ways to look at the outcome of an MVP, but I like to think of it as 2 simple yes/no questions:
**Is there a small, focused group of people who are feeling this pain?**
**Would they pay for a product that helps them solve this problem?**
If you don't get a confident "yes" to both of these questions, then you need to rethink your plan. You can always build more, but you can't recover wasted time building features nobody wants.
This can be accomplished with less than you think. A landing page with a video demo, a sign-up form for a waitlist, or a non-functional prototype.
### MVP for a coworking SaaS
My last startup, smpl, was a SaaS for managing coworking spaces. Our MVP was boiled down to the basics: we took the pain of collecting monthly membership dues out of our customers' hands. Version 0 was nothing more than a few manually configured Stripe subscriptions.
What did we learn? Coworking operators are great communicators, and rarely great at balancing a budget. Collecting _all_ member payments on the same day of the month made it _far_ easier for them to budget, track growth, and plan for the future. We spent the next year building a product that made it easy for them to onboard new members immediately, and to start their recurring payments on the first of the month.
(Side note: this is a trivial problem in 2025, but in 2017 it was on us to figure it out. Timing _really_ helped us!)
### MVP for a service business
[Craftwork's](https://craftwork.com) MVP boiled down to a simple question: will people hire a painting service online? We tested this with a landing page and a typeform -- and spent a month painting houses _at-cost_ for friends and family.
The amount we learned from that experience was worth the cost of the paint, and helped guide the way we hire paint crews (which has since changed several times), and how we price our services (which has also changed several times).
We focused exclusively on residential repaints for homeowners (not renters, not businesses, not commercial buildings). In doing so, we became very familiar with what our competition was lacking - a focus on considered homeowner experience, pricing transparency, and a commitment to quality.
## The value of embarrassment
In both of these cases, we were able to steer product development based on what we learned.
For smpl, an initial focus on member onboarding and billing brought much more value than building out a tiny social network for community members of a given coworking space.
For Craftwork, we learned that price transparency _alone_ wasn't enough to win over skeptical homeowners -- trust is earned through thoughtful communication, and a self-serve price quote wasn't enough to get people to slap the `Buy` button. We pivoted to a more consultative approach, and focused on building trust through a more personalized service. This also meant dropping our self-serve estimate form in favor of a literal contact form... can you imagine the time we'd have saved with a smaller MVP?
## Your challenge
If you're designing an MVP, take a step back.
What's the absolute minimum you could build to test your idea?
Is it **actually** testing your idea? If there's no outcome from your MVP that will cause you to change course, you're doing it wrong.
Is your MVP **actually** as minimal as it can be? If you're not sure, ask yourself:
- Is there a way to test this without spending money?
- Is there a way to test this while spending less time?
- Is there a way to test this while using fewer resources?
If you can't answer yes to all of these questions, you're probably over-engineering your MVP.
Launch something so minimal it makes you uncomfortable. You can always build more, but you can't recover wasted time building features nobody wants.
Do more with less - you'll be glad you did.
---
## Stop paying the app store tax.
Sell your app on the web with lower fees and full control. As a merchant of record, Paddle handles payments, taxes, and compliance - so you can focus on what matters: building your app.
Paddle acts as the reseller of your app, offering a solution similar to the App Store or Google Play Store but optimized for successfully selling your mobile app on the web, with significantly lower fees.
[Start selling smarter with Paddle.](https://www.paddle.com/resources/mobile-app-monetization-guide?utm_medium=website&utm_source=partner&utm_campaign=core_conversions_fy2025_web_monetization_brand_awareness&utm_content=tiny-improvements)
---
## Some resources to help you build less
- **[The Mom Test](https://amzn.to/41uVYEI)** - From author Rob Fitzpatrick, on how to listen to potential customers without misleading yourself.
- **[The Lean Startup](https://amzn.to/41I5PZ1)** - A legendary tome from Eric Ries, on how to build more with less. It's a book so good there are literal college courses built around it.
- This video from [Y Combinator on How to Build an MVP](https://www.ycombinator.com/library/Io-how-to-build-an-mvp) is a great primer on the topic, with some really useful examples of MVPs from cpmpanies you know.
What are you building right now that could launch with half the features? Hit reply and tell me what you'd cut first.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Design's Shakespearean Curse: Good UX Should Never Be Noticed]]>
https://mikebifulco.com/newsletter/good-ux-is-invisible
https://mikebifulco.com/newsletter/good-ux-is-invisible
Tue, 25 Feb 2025 00:00:00 GMT
Brought to you by Paddle
---
A well-crafted door handle never gets praised - it just works. But struggle with a door that needs instructions (why do "Push" signs exist?), and suddenly design screams for attention.
What did you like about the last stairwell handrail you used? Probably... nothing, right?
You've used hundreds without a second thought. But grab one that's too high or wide, and you'll notice immediately.
This is the Shakespearean curse of UX: The better you do your job, the less anyone sees you did it at all.
## Where to Look for Invisible Design in Software
This same principle defines great digital experiences. Here are three areas where invisible design matters most:
### AI and Conversational Design
Remember the first time you used ChatGPT? The interface was almost certainly not the thing that stood out - it was the quality of the answers you got. Nonetheless, the interface that surrounds any LLM you use has become a critical part of the experience.
That's the pinnacle of conversational design: total invisibility.
I spent a couple years working on Google Assistant in the pre-LLM times, when product teams would spend _countless_ hours trying to make a conversation with Assistant feel natural. It was a tall order, and it did not get there until Assistant entered a Bard-flavored chrysalis, and emerged a Gemini-powered Butterfly.
### Traditional Interface Design
Forms are invisible design's ultimate test. Nobody has ever hit "Submit" and felt a rush of joy -- but if you've ever been stuck on a page that _won't tell you what's wrong_, my god will you notice.
Ever gotten lost trying to find your account and routing numbers on your bank's website? There it is again - someone's design work, begging for attention.
### Friction as a feature
There _are_ cases where putting an obstacle or two between someone and their goal is a good thing.
Your phone's alarm clock is a great example - if it's _too_ easy to dismiss a wake-up alarm, they're far less effective.
Similarly - a confirmation / "are you sure?" dialog is a good thing when doing something destructive, irreversible, or executing a financial transaction.
## Notice me, senpai
If good design is invisible, how the heck do you get better at it?
As a designer, this becomes your burden: start paying attention to what you're _not_ noticing. What apps/tools/processes have been so smooth you barely had to think?
Study interfaces that fade away. Analyze forms you completed without cursing. Notice apps you use daily but couldn't describe if asked.
You don't always need to make people say "wow" - and to be perfectly honest, if that's where you're _starting_ from, I'd be worried.
Your best work will never get the praise it deserves because, if done right, no one will know you did anything at all.
That's the beautiful curse of great design.
---
## Stop paying the app store tax.
Sell your app on the web with lower fees and full control. As a merchant of record, Paddle handles payments, taxes, and compliance - so you can focus on what matters: building your app.
Paddle acts as the reseller of your app, offering a solution similar to the App Store or Google Play Store but optimized for successfully selling your mobile app on the web, with significantly lower fees.
[Start selling smarter with Paddle.](https://www.paddle.com/resources/mobile-app-monetization-guide?utm_medium=website&utm_source=partner&utm_campaign=core_conversions_fy2025_web_monetization_brand_awareness&utm_content=tiny-improvements)
---
## Tiny acts of Rebellion
Current events got you down? Me too.
Here's your reminder that unseen actions leave visible scars.
🎯 Target execs recently showed off their liquid spines by axing DEI programs, which resulted in a [dramatic drop in store traffic](https://finance.yahoo.com/news/target-put-dei-chopping-block-182500865.html).
Meanwhile, 98% of Costco shareholders confidently [voted to _preserve_ their DEI initiatives](https://www.axios.com/2025/01/23/costco-dei-shareholders-reject-anti-diversity-proposal).
There's no gambling required to predict which company's Q1 earnings report will tell the better story.
Often the most powerful design choices are the ones nobody sees happening - until the results become impossible to ignore.
## Fill your brain with design
If this resonates with you, here's some resources you'll appreciate:
- [The Design of Everyday Things](https://amzn.to/43b4R8E) by Don Norman is _the_ book on this topic. Can't recommend it enough.
- I rewatch [Do the Most Good](https://www.youtube.com/watch?v=fWivXkQpO2Q), a talk from legendary designer [Mina Markham](https://www.minamarkham.com/) about once a year. Mina is an icon, and her wisdom is worth learning from.
Until next time - give 'em hell.
Mike
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[AI is your intern (not your boss)]]>
https://mikebifulco.com/newsletter/ai-is-your-intern-not-your-boss
https://mikebifulco.com/newsletter/ai-is-your-intern-not-your-boss
Tue, 18 Feb 2025 00:00:00 GMT
Brought to you by Paddle
---
### AI Works Best When You Steer It
Most AI tools (Cursor, GitHub Copilot, ChatGPT) aren't great at figuring everything out on their own. They do best when you provide them with context. Although this guide is focused on software development with Cursor, the same principles apply to other tools and domains.
I have found that the best way to use LLMs is to treat them like an intern:
1. Tell them the goal. Spell out what you're building.
1. Give them the pieces. Feed them relevant files, not just one at a time.
1. Make a checklist. Break the work into steps you can track.
Here's an example of a recent set of instructions I gave to Cursor, while working on a new feature for Craftwork:
```
take a look at @timesheets_spec.rb - I need to produce an updated version of our timesheets API under the v2 namespace. It should use all of the same patterns as the other endpoints in @v2 do, and should use a new controller namespaced under api::v2 at `controllers/api/v2/timesheets_controller.rb`.
It needs a list view that can be filtered by a craftworker's id, by timesheet state (approved/inprogress/etc), and by production lead id.
The show view should return details for a single timesheet.
The update view should allow me to approve a timesheet, edit values, etc
```
That was enough to get me started working with Cursor, and it helped orient the LLM while building out the new feature. It had enough context for me to ask questions as I worked, and sped things up nicely.
### AI Will Get It Wrong (And That's Fine)
For any instructions you give 'em, LLMs will [confidently spit out answers](https://mikebifulco.com/posts/product-marketing-defy-expectations), regardless of how correct they are.
If you don't understand what they're doing, you're trusting a bad intern to run your company.
That's why you need to:
- Spot bad logic. If something seems off, it probably is.
- Debug iteratively. AI is great for refactoring-ask it to explain itself.
- Know when to take over. Sometimes, the best fix is writing the code yourself.
In the case of the Craftwork timesheets, I was able to spot a few issues, and after making some changes, steered the LLM to the right path (my typoes included -- LLMs actually deal with these really well!):
```
great, now can you llook at the controller and add any helpful missing scopes? You may want to peek at other controllers in the @v2 folder, as well as @timesheets_controller.rb
Alsothe .d.ts type definition declarations you made arne't needed - see @tsconfig.json and @javascript - they're likely in another folder already configured with typescript paths. If the components don't exist they'll need to be created
```
If you've ever onboarded a new teammate to a codebase, this kind of steering is not at all uncommon - you're helping them understand the codebase, and the context of the changes they're making.
### Tests Are More Important Than Ever
If you're letting AI write code, you better be _damn sure_ it works as expected. That means writing great tests before shipping anything.
- Test like a skeptic. Assume AI-generated code is flawed.
- Write failure cases. If AI wrote the function, you should write the test.
- Use AI to help debug. It's great at explaining why tests fail (sometimes).
## The Bottom Line
AI is a force multiplier - but only if you use it right. Treat it like an intern:
- Give it structure.
- Question everything.
- Make sure the work holds up.
Most importantly, remember that your great, big, juicy brain still need to do some work. Don't blindly trust the output of your copilot-of-choice - that's a hell of a lot to ask of an intern.
---
## Tests? What tests?
Most of us (hello, yes, me included) aren't great at writing tests -- but writing software tests is a skillset that is absolutely worth investing in. Here's some resources I've found helpful:
- (React) [Testing Library](https://testing-library.com/) provides documentation and set of tools for testing web applications, in a variety of frameworks. Whether you're a fan of react or svelte or vue or solidjs, this is a great resource.
- One of my favorite things about building with Ruby on Rails is the framework's first-class support for great testing. There are _so_ many thoughtful features for writing great tests for rails apps. Even if you're not a rails developer, it's worth giving their docs a look: [Rails Testing Guide](https://guides.rubyonrails.org/testing.html)
---
## Stop paying the app store tax.
Sell your app on the web with lower fees and full control. As a merchant of record, Paddle handles payments, taxes, and compliance - so you can focus on what matters: building your app.
Paddle acts as the reseller of your app, offering a solution similar to the App Store or Google Play Store but optimized for successfully selling your mobile app on the web, with significantly lower fees.
[Start selling smarter with Paddle.](https://www.paddle.com/resources/mobile-app-monetization-guide?utm_medium=website&utm_source=partner&utm_campaign=core_conversions_fy2025_web_monetization_brand_awareness&utm_content=tiny-improvements)
---
## Thinking about automation
I've spent a bunch of time working on small scripts to automate manual tasks lately - and I'm working on a couple quick video tutorial showing how you might use tools like Puppeteer, Faker, Skyvern and your copilot-of-choice to get things done more quickly than ever before.
If that sounds interesting, go chase me down on youtube at [@mikebifulco](https://www.youtube.com/@mikebifulco?sub_confirmation=1).
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[How I (Think I) Talk to AI]]>
https://mikebifulco.com/newsletter/how-to-talk-to-ai-llms
https://mikebifulco.com/newsletter/how-to-talk-to-ai-llms
Tue, 11 Feb 2025 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[How Clever Engineers Stay Ahead of the Curve]]>
https://mikebifulco.com/newsletter/how-clever-engineers-stay-ahead-of-the-curve
https://mikebifulco.com/newsletter/how-clever-engineers-stay-ahead-of-the-curve
Mon, 03 Feb 2025 00:00:00 GMT
Brought to you by Superhuman
How do you find out about new tech?
This is a question that came up recently during a chat with a friend (hello, Sean) - and for me at least, it's a tricky answer because I don't have one answer. My career path has been dictated by being vaguely aware of new trends in tools and tech at just the right time: from jQuery to React, create-react-app to gatsby to Next.js to Remix, to various focuses on the applied science of UX, I've been able to recognize and capitalize on new opportunities by keeping an eye out for signals that come from many sources.
All this to say: I don't ever really set out to _find_ new things, really. I do, however, have a whole bunch of places that I loosely pay attention to, in order to learn from people smarter than me.
Broken into a few simple lessons, here's how I do it:
### Lesson 1: Diversify Your Information Diet
Don't rely on just one source. Lately I've been learning from smart people on social media platforms like Bluesky, Threads, and Mastodon, and keep an eye on GitHub, Reddit, and Hacker News. This breadth allows me to spot trends, and to collect more signals on new tools, tech (and sometime people!) who are gaining traction.
### Lesson 2: Stay Curious and Open-Minded
I occasionally explore new frameworks or technologies - even those that don't seem immediately relevant. These little spikes help me to pull from the best of this-and-that for larger projects down the line. For example: I really love the DX of building interfaces in React, and I like the SEO the Remix framework makes available -- _and_ I'm a big fan of the database ORM used in Rails, called ActiveRecord. If I hadn't ever run `rails new` or `npx create-remix@latest`, I would have never known about these things.
### Lesson 3: Connect the Dots
The ability to link seemingly unrelated concepts can lead to innovative solutions. I learned about React way back when I was building my first company; at the time, it was the best way to create a web app that updated its interface without reloading the page. That was super helpful for the fitness IoT product we were building at the time.
## Common threads for a great product engineer
I've developed these habits by watching people admire do the same thing. Your path will vary based on where you are in your career, your goals, and your interests -- and that's a good thing. The engineers who I have seen build great things tend have a few things in common, which are correlated to the habits I've outlined above:
### Corollary 1: Embrace Side Projects
The smartest engineers often have side projects to experiment with the latest technologies. These projects are perfect for testing out new tools that might not fit into their professional work, helping to build their brand and skills.
### Corollary 2: Pursue Diverse Interests
It's beneficial to learn from different fields and backgrounds. Whether it's speech science at Google or community building in startups, integrating diverse knowledge can be a tremendous asset.
## What you can take away from this
Smart people don't just follow one path; they build a diverse, constantly updated network of knowledge sources. If you're working on growing into a successful career, consider building a diverse network of people who can help you learn and grow. For some of us, this may mean changing your social media habits - don't just chase endorphins: find ways to _learn_ while you scroll, and then go out and build something.
---
## How much is 4 hours of your time worth?
You're busy. Your inbox shouldn't slow you down. Superhuman helps founders, product leaders, and high-performing teams reclaim 4+ hours per week by making email **fast**.
That's 4 extra hours to build, ship, or make game-changing introductions-the kind that open doors and create new opportunities.
📩 **Tiny Improvements readers get their first month free** - [try it here](https://superhuman.com/ti?utm_medium=sponsor-callout&utm_source=mikebifulco-com).
---
## Some sample sources for you to explore
It's only fair if I share some of the brilliant folks I've learned from recently; here's some of what's been keeping my attention -
YouTuber Mitxela made an incredible [fluid simulation pendant necklace](https://www.youtube.com/watch?v=jis1MC5Tm8k) from off the shelf and custom machined parts. What I love most about this project is that it shows a great series of prototypes and iterations, and the final product is a beautiful piece of wearable art. It gets meta (even meta meta) along the way, and is a great peek into an inventor's creative process.
I've been reading the [Simple Sabotage Field Manual](https://www.gutenberg.org/ebooks/26184), a WWII-era handbook written by the US Office of Strategic Services (OSS), and declassified by the CIA in 2008. If you enjoy finding ways to make _good trouble,_ you'll love it. Best of all-it's free.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[My 2025 Developer Tech Stack]]>
https://mikebifulco.com/newsletter/developer-product-engineer-tech-stack-2025
https://mikebifulco.com/newsletter/developer-product-engineer-tech-stack-2025
Wed, 29 Jan 2025 00:00:00 GMT
Brought to you by Superhuman
## This is how I get things done
My work as an engineer and founder is split between two main activities:
1. Building products and features
2. Building the systems and processes that allow me to build products and features (I spend more time here each day)
I tend to stick with tools that amplify my productivity, help me get stay organized, and ones which don't get in the way when I'm finding flow state.
The best tools find their way into my workflow without much hassle.
## Princples for choosing tools
While I never consciously set hard rules for choosing the tools I use, I have found some consistent principles of what I look for in a tool:
1. **Simplicity:** I prefer tools that are simple to use and understand. I don't want to spend time learning how to use a tool - I want to spend time getting things done.
2. **Portability:** I prefer tools that are easy to set up and move between devices. This means that cloud sync is a huge plus for me - if my work laptop ever gets launched into the sun, it should be easy to set up a new machine and get back to work.
3. **Reduced key ~man~ tool risk**: Developers are notorious for customizing the hell out of their tools, often to a fault. I don't ever want to feel like I _can't_ get things done on someone else's computer. My team does lots of pair programming - and I never want to feel lost on someone else's machine because without _my dotfiles_.
---
## These are the tools I use in 2025
Alright, let's get into it. This is the tech stack I'm using in 2025:
### Hardware
- **Laptop: Macbook Pro 14"** - Up until a few weeks ago, I was using a 14" 2021 M1 Macbook Pro. I recently swapped to a 2023 variant with an M3 chip. These computers have been, without a doubt, the best I've ever used. I've switched between Windows and MacOS over the years - we're in an era where hardware is what makes the difference. These MFs are fast, and the battery life is incredible.
- **Phone: Pixel 9 Pro** - Hot take: I'm not a huge fan of some of the UX on IOS. My Pixel takes _stunning_ photos, and integrates with all the things I love for home, work, and play. Even still, I switch between Android and IOS every few years, because I believe it's helpful to know and understand what both options are like. It's a great way to keep learning and stay informed.
### Tools
- **Note-taking: Logseq** [LogSeq](https://logseq.com/) is a fantastically simple, privacy-first, markdown-based note taking app for building knowledge graphs. I switched to LogSeq last year from RoamResearch, and have been very happy with the experience. If you've tried Notion and haven't quite gotten along with it, I'd recommend giving LogSeq a try.
- **Email: Superhuman** - [Superhuman](https://superhuman.com/ti?utm_medium=body-rec) is a stunningly email client designed with efficiency in mind. It works _with_ my Gmail accounts, and lets me triage, filter, and respond to emails confidently - and without distraction. Their design team has done an incredible job of creating a product that's both beautiful and functional.
- **Swiss-army knife:Raycast** - [Raycast](https://www.raycast.com/) integrates with MacOS as a replacement for Spotlight (the little window that pops up when you hit command + Space on most Macs). It's more than just a launcher - I use it for launching apps, translating english ↔ spanish, checking fligth statuses, and countless other utilities during my workday.
### Devtools
- **IDE: Cursor** - [https://www.cursor.com/] is a fork of VS Code that is highly customized for AI-assisted coding. I have it customized with a set of prompts for each of my projects, and to index docs for libraries I use. While it's not a replacement for _thinking_ - it's like having a _very good_ pair programmer at your side all day. An instant productivity boost.
- **HTTP Client: Bruno** - I started using [Bruno](https://www.usebruno.com/) last year for testing and integrating with APIs. It's similar to Postman, open-source, and includes some really cool features, like a native git integration, so you can share your API specs with your team.
- **Design: Figma** - I've been using Figma for years, and over the past year have started using their layout tools to prototype interfaces as I build (shout out to my pal [Drucial](https://drew-white.dev/) for getting me up to speed on autolayout!). I believe design is a _critical_ skill for any engineer, and right now, Figma is the best tool for the job.
- **Project Management: Linear** - [Linear](https://linear.app/) is _the_ project management tool that we use at Craftwork for keeping our ever-changing backlog in order. It's like Jira, but with all of the garbage ripped out and replaced. If you haven't used it before, give it a try.
..and more. There's _definitely_ more that I use day to day - I'll share a follow-up post soon with details about the stack I use for _building_ products - the frameworks, libraries, and SaaS products I use to build Craftwork, this site, and APIs You Won't Hate.
### Your tools should work as hard as you do.
Superhuman keeps your inbox in check, so you can focus on building. Stay productive in 2025: prioritize, reply, and save 4+ hours a week. Thanks to Superhuman for giving Tiny Improvements readers their [first month free](https://superhuman.com/ti?utm_medium=sponsor-callout&utm_source=mikebifulco-com).
---
## What did I miss?
Is your favorite tool missing from the list? Did I miss something that's critical to your workflow? The best way for me to find out is by sharing - slap the reply button and let me know what I'm missing.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Focus Mode for the Defiant]]>
https://mikebifulco.com/newsletter/focus-mode-for-the-defiant
https://mikebifulco.com/newsletter/focus-mode-for-the-defiant
Tue, 21 Jan 2025 00:00:00 GMT
As a founder, your inbox is chaos-but it doesn't have to be. Superhuman cuts through the noise, prioritizes what matters, and drafts replies before you even open a message. Every action takes seconds, not minutes.
Start 2025 with clarity, focus, and 4+ hours saved every week. **Your first month is free.** What's stopping you?
## Focused learning for existential awareness
- What if maps were made to show the _time it takes_ to travel between points? YouTuber [Vaclav Volhejn explores this idea](https://www.youtube.com/watch?v=rC2VQ-oyDG0) with a fascinating visualization built in TypeScript.
- Creator of Million.js, Aiden Bai has been producing an incredible series of videos about how browsers work - his recent entry on [how browsers "paint" HTML](https://www.youtube.com/watch?v=yBkFjlPWpZ8) goes far deeper into browser rendering than I ever thought about.
## The Spinal Column 🩻
_Because staying informed is an excellent use of vertebrae._
_This is a new segment for Tiny Improvements. I thought it would be helpful to share \_one_ link related to current events that I've found interesting, educational, or poignant. I'd love to hear what you think - hit reply and let me know.\_
On a recent episode of the podcast Opening Arguments, the hosts dive into a sobering truth: the US president is now above the law. We're in uncharted territory, facing a challenging four years ahead.
Listen to it here: [We (Disrespectfully) Dissent](https://open.spotify.com/episode/5DD95dTspKjSOyKUPzZhpT?si=4544c33d9fe04f6a)
Thanks for tuning in. Keep pushing boundaries - and give 'em hell!
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Superfounder Superpowers: Sending Introductions]]>
https://mikebifulco.com/newsletter/superfounder-superpowers-sending-introductions
https://mikebifulco.com/newsletter/superfounder-superpowers-sending-introductions
Tue, 14 Jan 2025 00:00:00 GMT
As a founder, your inbox is chaos-but it doesn't have to be. Superhuman cuts through the noise, prioritizes what matters, and drafts replies before you even open a message. Every action takes seconds, not minutes.
Start 2025 with clarity, focus, and 4+ hours saved every week. **Your first month is free.** What's stopping you?
### A sample introduction email
Many of the introductions I send and receive look something like this:
> Subject: Mike, meet Sarah
> Hey gang -
> Sending over a quick note to connect you. You both have context, but think it would be great for you to meet! Will let you take it from here.
> T.
Brief, informative, and to the point. It gets the job done!
---
## From around the internet
I've come across a great deal of creative inspiration online this week - and I thought you'd appreciate these:
[Lofted Goods](https://thangs.com/designer/LoftedGoods) is a designer who creates simple, elegant, and functional 3d prints for use around the home. Their aesthetic really speaks to me, and I love the addition of thoughtful features, like an insert for wall-hung decor that makes it dead easy to decide where to drill holes for screws and wall anchors. Best of all? You can download the files for free and print them yourself.
My god do I love a good typeface. I recently came across [Taylor Penton's hand-drawn fonts](https://www.taylorpenton.com/fonts), and fell in love straight away. I've even hopped onboard as a paying member of their Type Club. I may even incorporate some of [Taylor's webfonts on my site](https://github.com/mbifulco/blog/pull/945) before long...
## What about you, friend?
As always, I'd love to hear what you're working on. Read something interesting recently? Launching your product soon? Hit reply and let me know. I do my best to respond to each and every one.
Note: Cover photo for this newsletter is from [MJ S](https://unsplash.com/@mjseka?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash) on Unsplash.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The Great Inbox Reset]]>
https://mikebifulco.com/newsletter/great-inbox-reset-for-founders
https://mikebifulco.com/newsletter/great-inbox-reset-for-founders
Tue, 07 Jan 2025 00:00:00 GMT
In the life of a founder, the inbox is both a necessity and a challenge. Every deal, opportunity, and conversation is buried under a flood of noise. Superhuman is designed to change that.
Imagine an inbox that knows what's most important and drafts replies to messages before you look at them - and every action takes seconds instead of minutes. Superhuman transforms email into a tool for clarity, focus, and action.
This January, start your year with a platform built to help leaders like you get more done and save 4+ hours every single week.
With your **first month free**, there's nothing holding you back.
### Your inbox is a tool, not a bottomless pit
Whether you use gmail, apple mail, Superhuman (shout out for sponsoring!), or Outlook, your inbox is a tool, and knowing how to use it is a game changer.
Treat your inbox like you would your favorite IDE or design tool-it's only as good as how you use it.
My approach:
- Only emails I need to respond to or act on live in my inbox.
- Labels and folders keep everything else neatly organized.
- Snoozing helps prioritize tasks for later without cluttering the present.
Think of your inbox as a task manager for important things, not a dumping ground for everything.
### Turn Off Notifications and Regain Your Focus
Real productivity happens when you're focused - and for me, sporadic email notifications are an unpredictable distraction.
**My tip**: Turn off email notifications entirely.
Seriously -- I turned 'em off. On my phone, in my browser, and in my email client.
This lets me check and triage messages in my inbox when I choose, ensuring I stay in the zone while working.
This practice eliminates the randomization of being distracted by notification bubbles. Being intentional about when and how you engage with your inbox keeps it from controlling you.
### A Clean Inbox = A Clear Mind
The value of an organized inbox goes beyond email:
- New, important emails are less likely to slip through the cracks
- Less notification spam is a free productivity boost
- It makes the _unread count_ on your email app's notification bubble _useful._ Imagine that!
### This sounds great, but I have 493287 unread emails
If you're sitting on hundreds of unread emails, it may be time to declare email bankruptcy.
Sometimes, the backlog becomes unmanageable - and that's okay.
Email bankruptcy isn't about giving up; it's about clearing your slate:
- Archive everything older than a certain date and triage the rest.
- Notify key contacts if they're waiting on something and ask them to resend anything crucial.
It's the fastest way to regain clarity and focus without drowning in old noise.
Use this reset as a chance to make email a tool that works for you-not against you.
## Start the new year fresh
Your inbox, like any great tool, works best when you know how to use it. A clean start at the beginning of the year can help you reclaim your time, focus on what matters, and build habits that last all year long.
Take control of your inbox, and you'll find yourself in control of your time, your focus, and your productivity.
---
## Who I'm learning from this week
By now, you know that I love functional 3D Prints. For me, the magic in this tech is in creating useful, customized tools to make your life better. It's a challenging process to master, which is why I really liked seeing this video on [designing 3D printed mods for a vintage Toyota](https://www.youtube.com/watch?v=hpxAcJaAXgk) on the _Fat Lip Collective_ YouTube channel. Even if you have no interest in old cars - there's lots to learn from the process used to develop a custom part.
If you haven't heard already, **you should uninstall the Honey extension from your browser** pronto. YouTuber [MagaLag created an exposé](https://www.youtube.com/watch?v=vc4yL3YTwWk&pp=ygUSaG9uZXkgc2NhbSBleHBvc2Vk) on the many ways the extension has been abusing creators and consumers, and it's a must-watch.
[Folklore (Kyle's version)](https://pca.st/0iqmt7xe) is the most recent episode of the podcast Hyperfixed, from Alex Goldman. This episode goes deep on something that at first glance seems trivial, but eventually touches on verbal tradition, craftsmanship, and some fundamental truths of the physical universe. A fantastic listen.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Themes Beat Resolutions Every Time]]>
https://mikebifulco.com/newsletter/themes-beat-resolutions-every-time
https://mikebifulco.com/newsletter/themes-beat-resolutions-every-time
Tue, 31 Dec 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Get lost in your work: the magic of flow state]]>
https://mikebifulco.com/newsletter/flow-state-and-getting-things-done
https://mikebifulco.com/newsletter/flow-state-and-getting-things-done
Tue, 17 Dec 2024 00:00:00 GMT
))
Flow state can make you feel _superhuman_. It's a state where focus, motivation, and productivity are at their peak.
If you've felt it, you know what I'm talking about.
## Why flow state is important
Engineering and product design are complex tasks, which are often best done without distraction. When I'm untangling a particularly complex bug or building a new feature, I am far more likely to be successful if I can focus on the task at hand.
For me at least, this doesn't always mean a silent, vacant room. I've found that I can get into a flow state in a busy coffee shop, while walking around the city, or at my desk in the office in the mdidle of a workday
## How I find flow state
Finding your flow state is one of those things where you need to know yourself and your brain a bit. Even for me, it varies a bit day to day: some days I work best from the comfort of my kitchen, or the counter at my local espresso bar, and other days I do best at my desk in the office, with two monitors and a good pair of headphones on.
Regardless of _where_ I am, there are a few things I do to help me get into a flow state:
1. Turn off notifications, and don't look at my phone
2. Close any apps or tabs that might distract me
3. Have a clear, specific task in mind
## Tips for getting in the zone
### Pomodoro is Italian for tomato
Minimalist Modern Timer}
href="https://amzn.to/4fmrhX1"
/>
The _pomodoro technique_ is simple: set a timer for 25 minutes, work until it rings, then take a 5-minute break. This method can effectively help you enter a flow state.
I learned this from a teammate at Google, who tracked his productivity with 🍅 emojis - each representing a pomodoro.
(Thanks for the inspiration, [Proppy](https://bsky.app/profile/proppy.bsky.social)!)
Many productivity apps include a pomodoro timer, like Logseq and Raycast. If you prefer a physical metaphor, you might like the [minimalist modern timer](https://amzn.to/4fmrhX1) above, which I recently snapped up for a few bucks on Amazon.
### Be selfish with your calendar
I regularly use Google Calendar's Focus Time feature to block off 90-min blocks of time to get things done. This gives me a guaranteed block of productive time, regardless of which meetings get added to my day. It's something I encourage my teammates to do, and if you've never tried it, I highly recommend it.
### Your phone can help
Whether you use an iPhone or an Android, your phone has support for Focus Modes. These are a great way to block out distractions and get into a flow state. If you haven't tried them before, here's a quick guide for each: [iPhone](https://www.theverge.com/23355242/ios-16-focus-modes-how-to-apple-iphone), [Android](https://www.androidcentral.com/phones/how-to-set-up-focus-mode-in-android-13).
If you're not a fan of focus mode, Do Not Disturb is a very effective cudgel for blocking out distractions.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[From 21 to 1000 - Lessons in Growth]]>
https://mikebifulco.com/newsletter/lessons-in-growth-from-21-to-1000
https://mikebifulco.com/newsletter/lessons-in-growth-from-21-to-1000
Tue, 03 Dec 2024 00:00:00 GMT
Growth has been uneven - spurts, plateaus, and lots of introspection - but every new dispatch and reader is a reminder of why I started sharing my work.
Here's what this journey has taught me:
1. **It takes guts to start.**
Sharing your work feels vulnerable at first. My first newsletter sat in drafts for months before I hit send. But once I did, the real growth - for the newsletter and for me - began.
2. **Feedback is fuel.**
Hearing from readers is always validating, whether it's close friends or strangers. If you've ever hit reply to one of my emails, know that your words mean more than you think.
3. **Writing changes you.**
This newsletter has made me more thoughtful-about my own work and about the content I consume. I notice lazy clickbait more than ever but also have a deeper appreciation for simple, impactful writing.
One unexpected highlight lately has been Bluesky. It's a refreshingly open and real space right now, and I've been connecting with incredible new people there. (Follow me: [@mikebifulco.com](https://bsky.app/profile/mikebifulco.com)).
---
### Why This Matters
Whether it's an article, video, app, or something else - sharing your work can feel daunting, but it's a great way to grow. Your journey will be different from mine, but every step will be valuable.
If you've been waiting for the “right time” to start, this is your sign: start today.
### Closing Thoughts
To each of you: thank you for letting me into your inbox. I'll keep writing, learning, and sharing, and I hope you'll do the same.
---
## Some Other Things I've Shared Recently
- [Migrating from next-sitemap to sitemap.ts](https://mikebifulco.com/posts/migrate-from-next-sitemap-to-app-directory-sitemap) I've been starting the process of migrating my personal site from Next's lovable Pages directory to the new App directory. While doing so, I put together a guide on migrating your sitemap, if you're looking to do the same.
- [APIs You Won't Hate: Mr. Bluesky](https://apisyouwonthate.com/newsletter/mr-blue-sky/) the latest newsletter from APIs You Won't Hate is all about Bluesky, and has some great articles about the platform and its API. You can find [APIs You Won't Hate on Bluesky](https://bsky.app/profile/apisyouwonthate.com), too!
- Speaking of lumpy growth and uneven solutions - I recently published a video series on [using Posthog to improve conversation rates](https://www.youtube.com/watch?v=4nWcB1a8M1s&list=PLhd5wwaTOKLuI6UNjGpBnPKxWiUW4iBhg) for 💌 Tiny Improvements signups. It was a fun experiment, and results were mixed! All part of the journey.
---
## Where I've been learning
- 📕 [Good Services](https://hardcover.app/books/good-services) by _Lou Downe_ - as recommended by my friend and colleague Niki, Good services is all about building services businesses, looking after customers and employees, and building systems that benefit both.
- 📗 [Supercommunicators](https://hardcover.app/books/supercommunicators) by _Charles Duhigg_ - This was a great lead in the run up to the election - coming to a better understanding of how great communicators listen to people and make connections. If you have challenging relationships at work, with family members, neighbors, or friends, this book has the capacity to be transformative.
- 🎙️ [Getting Ready to Interview Trump - an exercise](https://www.youtube.com/watch?v=gx7IDERbRWk) is the latest episode of the podcast _Question Everything_ from Brian Reed, who you may know from podcasts like _S-Town_ and _The Trojan Horse Affair_. Question Everything is an ongoing analysis and inspection of Journalism's role in society. Each episode so far is well-worth a listen.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[First Principles: Your Framework for Clarity]]>
https://mikebifulco.com/newsletter/first-principles-frameworks-for-clarity
https://mikebifulco.com/newsletter/first-principles-frameworks-for-clarity
Tue, 19 Nov 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Mad? Use It to Start Something Big]]>
https://mikebifulco.com/newsletter/your-anger-as-inspiration-for-change
https://mikebifulco.com/newsletter/your-anger-as-inspiration-for-change
Thu, 14 Nov 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Dunbar's number: focusing on your core supporters for network effect growth]]>
https://mikebifulco.com/newsletter/dunbars-number-and-network-effect
https://mikebifulco.com/newsletter/dunbars-number-and-network-effect
Tue, 05 Nov 2024 00:00:00 GMT
**Flex your product muscle**
Product for Engineers is a newsletter on building great products, the best practices of top startups, and lessons learned by PostHog. ## What it means for your product Most people talk about Dunbar's number in terms of 150, but the power lies in close-knit groups of 50. These 50 people are your advocates, your early adopters, your most vocal supporters. For product builders, focusing here first creates a foundation that grows beyond one-time use or sporadic engagement.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Get out and F*cking Vote]]>
https://mikebifulco.com/newsletter/voting-and-the-founder-mindset
https://mikebifulco.com/newsletter/voting-and-the-founder-mindset
Wed, 30 Oct 2024 00:00:00 GMT
### Beyond the Trade-Offs
Voting thoughtfully means thinking like a founder: weighing short-term gains against long-term consequences. It's about balancing immediate benefits with the impact on society, rights, and industries in the years to come. A single-issue endorsement may deliver short-term support for one area, but it's rarely worth compromising on the rest of what we value.
### Vote for the World You're Building
The best companies, and the best leaders, look beyond the next quarter, just as the best voters look beyond a single issue. So this election, think beyond one policy and consider how each candidate's values and actions align with the future you want to help create.
## Most importantly: Vote
If you're elligible to vote in this election, the moral and ethical imperative is to vote. It's shaping up to be a close race, and your voice is more likely than ever to make a difference.
You're not reading this newsletter because you're an apathetic person. You're reading this newsletter because of the active role you've taken in your life, and because you care about the future. So go out there and make your voice heard.
✌🏾
---
## Resources for staying informed on elections
### An interview with Mo Green
A special shout out this week: North Carolina's election for State Superintendent of Schools has gotten a ton of attention, and for good reason. Shortly after this newsletter goes out, an in-depth [interview with Democratic candidate Mo Green](https://www.youtube.com/watch?v=zN1mCjkpU-c) will be featured on the Primary Focus YouTube channel.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[First principles for UX design]]>
https://mikebifulco.com/newsletter/first-principles-for-ux-design
https://mikebifulco.com/newsletter/first-principles-for-ux-design
Tue, 15 Oct 2024 00:00:00 GMT
For example, if a setting can be toggled on or off, it can be tempting to render a button that shows two states - from a developer's perspective, it's easier to code, but the result can be confusing for the people using your product.
Instead, use a toggle switch to instantly communicate what the function is.
Small details add up to a more intuitive experience - does the mouse cursor change to a pointer when hovering over a button? Is there a visual difference between a clickable element and a non-clickable one? These small details can make a big difference in usability.
You're taking advantage of things we are already used to: toggle switches switch between states, and seeing a pointer when hovering over something indicates it can be clicked.
### 2. Your interface should be consistent
Once you've nailed down the patterns for individual bits of UI, they should be used consistently throughout your app.
If you're building features that your customers will use, you should build them with the same attention to detail as the rest of your app. I leave some room in my heart for easing up on superuser features that will never end up in the hands of a paying customer, but even that can be a slippery slope.
So - take the time and get your UI primitives working well, and use them consistently throughout your app. Heck, do yourself a favor and take advantage of a component library like [Shadcn](https://ui.shadcn.com/).
### 3. Your customers are already trained
People [spend more time in other apps than in yours](https://mikebifulco.com/newsletter/jakobs-law-design-ux). It's a reality that sounds depressing, but is actually good news for you. Your customers have been trained by _thousands_ of other apps and websites - they expect certain patterns and conventions when they're getting things done.
They know what an inbox looks like, and a calendar, and a search bar, and a settings page. People come with built-in expectations for credit card fields and push notifications and date pickers. Use these things to your benefit - don't reinvent the wheel where you don't have to.
---
## More reading on first principles
You don't need to listen to me (ever) - but you should at least _consider_ learning from people smarter than me:
### Thinking with Type
When I was studying Human-Computer Interaction in grad school, I read [Thinking with Type](https://www.amazon.com/Thinking-Type-Critical-Designers-Students-dp-1797226827/dp/1797226827) as part of a course I took on cognition. The professor who taught the course use to repeat the phrase "Words have meaning" often. He had a habit of showing us examples of how people's expectations for how things should work are shaped by the types of experiences they've had in other places. Words have meaning, and the _way we present words_ carries more meaning than you might think.
### Dan Mall on Design Systems
Dan Mall is a designer who has written a lot about design systems. He's got a great primer video on his YouTube channel - [What is a design system?](https://www.youtube.com/watch?v=hMSSg-pA9lk) is worth a watch for nailing down some first principles goodness.
---
## Hey though, go vote
We're less than a month from The U.S. presidential election. If you're one of my American pals, please go vote. If you're not, please consider reaching out to someone you know who is and asking them to vote.
You're going to be bombarded with ads for the next month - it's easy to get cynical and tune it out. Please don't. Your vote is too important.
Need to look up your polling place, or see who is on your ballot? I got you -> [vote.org](https://vote.org/) is a great resource.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Don't just listen. Interpret feedback wisely.]]>
https://mikebifulco.com/newsletter/interpret-feedback-wisely
https://mikebifulco.com/newsletter/interpret-feedback-wisely
Tue, 08 Oct 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Nobody Wants a Big Reveal: Why Keeping Secrets Hurts Your Work]]>
https://mikebifulco.com/newsletter/nobody-wants-a-big-reveal
https://mikebifulco.com/newsletter/nobody-wants-a-big-reveal
Tue, 01 Oct 2024 00:00:00 GMT
### Flex your product muscle
Product for Engineers is a newsletter on building great products, the best practices of top startups, and lessons learned by PostHog.
## Why the Big Reveal Falls Flat
The grand unveiling can often backfire. The truth is, a successful launch depends on much more than secrecy. It requires real-world feedback, adaptation, and a deep understanding of your audience's needs.
In my years building products, I've seen too many projects miss the mark because they held back until it was "perfect." Here's why that doesn't work:
1. **Audience of One**: Designing without input means building a product that only fits your vision - not your customers' needs.
2. **Perfection Paralysis**: Chasing perfection often leads to endless revisions and a product that's never finished.
3. **Out of Touch**: Without feedback, your product becomes a solution searching for a problem.
4. **Crickets at Launch**: When no one knows about your work, no one's waiting for the reveal.
5. **Echo Chamber Effect**: Without external voices, you risk becoming too invested in your own ideas and losing touch with reality.
## Why the Big Reveal Hurts Your Team
The big reveal doesn't just create problems for the product - it also disrupts your team. When people work in isolation and wait until something is "done" before sharing, they end up dumping a massive document or feature on their teammates with little context. This approach blindsides the team, creating confusion and misalignment.
Crowdsourcing feedback from peers along the way is a much better strategy. By sharing progress early, you keep everyone in the loop, build a sense of ownership across the team, and avoid surprises. Plus, it opens up the opportunity for valuable input that can course-correct mistakes before they become deeply ingrained in the project.
### Why this matters
- **Prevent Silos**: Sharing early keeps everyone informed and helps avoid working in isolation.
- Get **Stronger Team Buy-in**: When teammates are involved throughout the process, they're more invested and engaged.
- **Better Outcomes**: Crowdsourcing ideas and feedback from teammates improves the final product, as you benefit from a diverse set of perspectives.
## Embrace Transparency
The better strategy is openness. By sharing your progress, process, and even mistakes, you invite feedback and foster connections. This transparency helps keep your work grounded, adaptive, and aligned with market needs.
In fact, incremental transparency is not just better - it's essential. Here's why:
- **Feedback Loop**: Regular updates mean you can adapt and pivot when necessary.
- **Audience Investment**: Involving people early builds community and anticipation.
- **Faster Iterations**: You can make smaller, faster improvements rather than obsessing over a grand reveal.
## The Power of Public Failures
Being wrong in public is uncomfortable - but it's also incredibly powerful. Admitting mistakes invites feedback and accelerates learning. It fosters a culture of humility and adaptability, and helps you build better products, faster.
## The Bottom Line
The big reveal is a relic. Successful products today are built through transparency, iteration, and collaboration. By opening up your process, you not only avoid the pitfalls of secrecy but build better relationships with your users.
## Do this instead
Don't keep your work a secret. Share your progress early and often. Your users will thank you - and so will your product.
---
## Here's some links I've been keeping from you:
Or rather, I _could_ have kept these to myself, but where's the fun in that? Here's some cool stuff I've been enjoying lately:
### Product Analytics with PostHog: my A/B test results are in!
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[How Contrast Elevates Perception]]>
https://mikebifulco.com/newsletter/contrast-effect-cognitive-psychology
https://mikebifulco.com/newsletter/contrast-effect-cognitive-psychology
Tue, 17 Sep 2024 00:00:00 GMT
contrast effect shows how **presenting options in a particular way can dramatically change how they're viewed** - even more than the options themselves.
Here's why this matters for designers, developers, and product builders:
## Brand Perception is Reality
At [Craftwork](https://craftwork.com?utm_source=mikebifulco-com), we work hard to provide a seamless, well-branded experience for getting your home painted - in an industry where the bar for customer service is pretty low.
Cynically speaking, the _end result_ for our customers is essentially the same as what all of our competitors offer: a freshly painted home.
However, we have spent _countless_ hours refining the experience our customers have. From the moment they get in touch with us to the final brush stroke, we've designed every touchpoint to be as thoughtful, modern, and smooth as possible.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Stay Sane: Mental Health Strategies for Startups]]>
https://mikebifulco.com/newsletter/mental-health-for-startups-founders
https://mikebifulco.com/newsletter/mental-health-for-startups-founders
Wed, 04 Sep 2024 00:00:00 GMT
### Flex your product muscle
Product for Engineers is a newsletter on building great products, the best practices of top startups, and lessons learned by PostHog.
Managing mental health will be different for every founder and every team, and it's up to you to figure out what works best for your unique situation.
I have found these strategies to be effective:
### Be the teammate you want to have
The golden rule goes a long way. Remember that you're working with real, complex people who have real, complex lives. Their joy, anxiety, and stress come from more than just work, and it can be easy to forget that.
Look after your teammates. Check in on them, ask them how they're doing, and encourage them to take time off when they need it.
**tl;dr:** Ask your teammates how they're doing, not just what they're doing.
### Use routines as an anchor for stability
I've written about [my morning routine](/newsletter/continuous-self-improvement) before, and how it has been critical for me in managing stress, staying organized, and generally just feeling like I'm in control of my life.
I highly recommend starting with just 5 minutes of journaling and 5 minutes of meditation. It will sound _too_ simple, but it's amazing how quickly you start to feel like you have a handle on your day.
If you're reading this and rolling your eyes, prove me wrong: try it for a month and tell me how it goes. My inbox is always open: [hello@mikebifulco.com](mailto:hello@mikebifulco.com).
**tl;dr:** Pairing 5 minutes of journaling and 5 minutes of meditation together make an incredible tool for managing stress.
### Go outside more
The day-to-day of building a startup can be so consuming that it's easy to forget to take care of yourself. Moving your body is one of the most important things you can do.
When I managed a remote team at Google, I would regularly schedule walk-and-talk calls with people on my team. These conversations often felt different -- there's something that makes it more natural to open up when you're not sitting in a conference room or at your desk.
The great news is that this works in person, too. Take your next 1:1 meeting outside -- even in hot or cold weather. You can do it!
Outside of work, find ways to spend time outside each day. The more the merrier, really, but I've found that just 10-15 minutes can make a big difference.
**tl;dr:** Touch grass. That's the tip.
---
## My work this week
### I messed up my A/B test
The latest in my ongoing video series on [Product Analytics for developers](https://www.youtube.com/watch?v=aDCFlPzNXh4) is out. This time, I'm talking about how how I detected and fixed a problem with an A/B test I was running.
### State of the APIs Survey 2024
Check out the most recent APIs You Won't Hate newsletter for a primer on the [State of the APIs Survey 2024](https://apisyouwonthate.com/newsletter/2024-state-of-the-api-survey/), and to learn a bit about my cofounder Phil's reforestation and climate protection charity.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Inter and the Power of Fonts: Why Typefaces Matter More Than You Think]]>
https://mikebifulco.com/newsletter/features-of-fonts-and-typography
https://mikebifulco.com/newsletter/features-of-fonts-and-typography
Tue, 27 Aug 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[How you do one thing is how you do everything]]>
https://mikebifulco.com/newsletter/how-you-do-one-thing-is-how-you-do-everything
https://mikebifulco.com/newsletter/how-you-do-one-thing-is-how-you-do-everything
Tue, 20 Aug 2024 00:00:00 GMT
Right now, the template is used exclusively for that one email - but I wanted to make sure it looked and felt right. I spent some time [looking for inspiration](https://reallygoodemails.com/search/emails/confirmation), set up a quick [Figma prototype](https://www.figma.com/design/On4yRGLcYLORVBIhBejboA/mikebifulco.com?node-id=301-6&t=tQ2Y9fUL1T7EHk7Y-1), and then got to work building it using [React Email](https://react.email/).
## The Bigger Picture
It's a small detail that probably matters most to me, but once it was done, it felt like my integration with Resend was complete.
The thing is, nobody will ever notice that I spent time on this. It's likely that this email will get banished to my readers' email archives within seconds of being opened, but that's kind of the point. If I did it right, this message should be _consistent_ with everything someone experiences when they come across my work. Ideally, it goes almost entirely unnoticed, because it feels like it's connected to everything else I do.
The quick way out here would be to use a fairly basic, blank template, or to fall back completely to `An old-timey text email`. I feel fairly confident in saying that either of those would feel out of place. Part of my whole schtick is that devs should care about design; failing to put in the effort here would be a pretty big contradiction.
## If you're doing things right, nobody will notice
...and sometimes that's just the way it is. This is a quip from a [great little scene in Futurama](https://youtu.be/EL7e05pClKM?si=UHoj8_lORe2YH6Qe) -- and I think it's a great centering thought for design work in general. As unsatisfying as it sounds, this is a sign of a successful design.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[How to source and use expert knowledge for your work]]>
https://mikebifulco.com/newsletter/how-to-source-and-utilize-expert-knowledge
https://mikebifulco.com/newsletter/how-to-source-and-utilize-expert-knowledge
Wed, 14 Aug 2024 00:00:00 GMT
### Flex your product muscle
Product for Engineers is a newsletter on building great products, the best practices of top startups, and lessons learned by PostHog.
Fast forward 7 years, and I was leaving Microsoft to work as technical director at a code [Gymnasium](https://thegymnasium.com), the best damn online code school for creatives looking to dip their toes in the cool waters of web development.
I would be using completely new tools - going from .net and C# to Django and Python - and from a _massive_ network of people to a crack squad of just 5, where I was the only developer.
Suddenly I was an astronaut in a space station, cut off from the world. I had no one to ask for help, no one to bounce ideas off of, no one to tell me when I was doing something stupid.
I was on my own.
It didn't take long for me to realize that **developers have a unique advantage:** most of our peers are _chronically online_. The most knowledgeable people **in the world** are at your fingertips, as long as you know where to look.
From forums and blog posts to open-source projects, there is no shortage of places to find answers and learn. For me, the key to truly benefiting from this wealth of information came from active participation and engagement with the developer community.
It can do the same for you -- but you're gonna need to put yourself out there.
Here's 3 things you can do _right now_ to get started:
### Join a community
Whether it's a local meetup, a Slack channel, or a forum, find a community of people that you can engage with. This is a great way to meet like-minded people, share knowledge, and get advice.
### Give helpful feedback
When you're starting out, it can be intimidating to contribute to open-source projects or forums. But remember, you don't have to be an expert to provide valuable feedback. By giving constructive criticism and suggestions, you can help others improve their work and learn in the process.
### Keep an eye on trends
The tech industry moves fast, and it's important to stay up-to-date with the latest trends and technologies. This doesn't mean you have to _use_ every new tool or framework that comes out, but having a general understanding of what's happening in the industry can help you make informed decisions about your own work.
## The Pavlovian Power of constructive engagement
Someo of the best career advice I ever received is from pal Thomas: give and receive feedback in good faith, and you'll find yourself surrounded by people who are willing to help you grow.
This means being honest, respectful, and open to new ideas. It means being willing to admit when you're wrong, and to learn from your mistakes. It means being generous with your time and knowledge, and being willing to help others when they need it.
The inverse of this is all too common online - I'd wager to say that the vast majority of reddit, twitter, and youtube comments are people who are _not_ engaging in good faith. They're there to tear down, to belittle, to make themselves feel better by making others feel worse.
I'm sure you've seen and felt that, and it _sucks_ -- but it also means that when you come correct, you will really stand out.
It's a simple concept, but it's incredibly powerful. By engaging with your community with constructive, meaningful, and thoughtful feedback, you'll build a powerful reputation for yourself. You'll find yourself learning along the way, too.
Before long, you'll be the one people come to for advice.
---
## Helpful links from around the web
- I published the second in a series of videos on [Using Posthog to solve my conversion rate problem](https://www.youtube.com/watch?v=RaX8NeEhowU&t=1s) - and I'm stoked to say that after seeing the first video, Posthog is sponsoring Tiny Improvements and the next few videos I'm putting together. Give it a watch and let me know what you think!
- Over at APIs You Won't Hate, we published a great little tutorial on [pagination basics for APIs](https://apisyouwonthate.com/blog/api-design-basics-pagination/). It's a great primer on how to structure your API responses to make them easier to work with.
- My pal Andrew Peacock has been doing a great job of building his product for woodworkers in public. You can follow along on his journey on YouTube. his latest video talks about an important milestone: he [finally launched his MVP](https://www.youtube.com/watch?v=O0ryiXiSvVg)
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Debug tips from a lifetime newbie]]>
https://mikebifulco.com/newsletter/what-to-do-when-your-product-breaks
https://mikebifulco.com/newsletter/what-to-do-when-your-product-breaks
Tue, 06 Aug 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[You're 8 episodes away from being in the top 20%]]>
https://mikebifulco.com/newsletter/milestones-and-the-top-20-percent
https://mikebifulco.com/newsletter/milestones-and-the-top-20-percent
Wed, 31 Jul 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Struggling with TypeScript: why not?]]>
https://mikebifulco.com/newsletter/typescript-and-learning-hard-things
https://mikebifulco.com/newsletter/typescript-and-learning-hard-things
Tue, 09 Jul 2024 00:00:00 GMT
There's [plenty more adorable
gotchas](https://github.com/denysdovhan/wtfjs?tab=readme-ov-file#table-of-contents),
and they're all fun and games until you're debugging a production issue at
3am.
Building a product is hard enough without having to worry about whether `NaN === NaN` (it doesn't) or why `[] + []` is an empty string.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Open Sourcing my Design System]]>
https://mikebifulco.com/newsletter/open-sourcing-my-design-system
https://mikebifulco.com/newsletter/open-sourcing-my-design-system
Tue, 25 Jun 2024 00:00:00 GMT
The images I use go a long way in helping me communicate my ideas, and in getting people to click through to my articles. I take the time to create a unique Open Graph Header image for every article I write, so that each one stands out on social media.
I've spent a lot of time over the years organizing, refining, and refining this system, and I'm excited to share it with you.
## Why Open Source This?
The point of open-sourcing this Figma file is simple: there's nothing magical here. I'm not doing anything you can't do. Heck, the source code for the rest of my site is publicly viewable as well on github ([mbifulco/blog](https://github.com/mbifulco/blog)), so this is a perfect pairing.
Having a system like this helps every article I write stand out a bit more. And I hope it can help you too.
### A Tool for Efficiency
One of the biggest advantages of having everything organized in Figma is that it makes publishing easy. I've created a toolkit for myself that minimizes decision fatigue.
Need a header image for a new article? There's a template for that. Newsletter? Ditto. This means I can publish content faster without getting bogged down by the details every single time.
### Stay Organized
This file keeps me organized. If I need to add, remove, or edit anything in the future, I can come back to this file and do it seamlessly. No more hunting around for that one logo or header image from two years ago.
### Opportunity for more
My hope is that by sharing this publicly, I'll be keeping myself accountable. This figma file is the foundation of what will eventually become a full-blown design system.
If you've dabbled in design systems before, you'll notice It's missing some critical pieces, like specific color selections and layout mockups, but hey, it's a work in progress.
## The Epiphany
Last week, I hit a milestone: nearly 70 published newsletters and 60 full articles. That's when it hit me-sharing this file might inspire you to create your own system. So here it is, for you to poke around and hopefully find some inspiration.
Check out the Figma file here: [mikebifulco.com Design System](https://www.figma.com/design/On4yRGLcYLORVBIhBejboA/mikebifulco.com?node-id=0-2431&t=XlKb5D0viU7DPV4T-1). Explore it, use it, heck, feel free to model your own after it.
And as always, let me know what you think - hit reply and let me know if you have any questions or feedback.
---
## Show & Tell
In a recent newsletter, I asked Tiny Improvements readers to share your projects with me. I got some truly incredible responses - thank you to everyone who shared! I'm always amazed by the talent and creativity that you all have.
### An incredible graphing calculator artist
Jake Walker's youtube is built around his incredible skill for creating beautiful, creative works with the Desmos graphing calculator. Jake is a CS student at NC State University, and I promise you that you're going to be blown away by his work.
Here's a great example to get you started: [Galaxy And Quasar Art in the Desmos Graphing Calculator](https://www.youtube.com/watch?v=5ykRxcsZjG0).
Holy moly. 🌌
---
## More of my work online
- [Surviving Other People's APIs](https://leanpub.com/surviving-other-peoples-web-apis?ref=mikebifulco.com) is a book I've been co-authoring with my APIs You Won't Hate co-founder, Phil Sturgeon. If you find yourself consuming APIs in your day-to-day work, this book is for you. Part of each sale goes to [Protect.earth](https://protect.earth), Phil's reforestation charity.
- I'm readying my next YouTube video for release - and I'd love it if you subscribed to my channel: [youtube.com/@mikebifulco](https://youtube.com/@mikebifulco).
- I'm also more and more active on Threads these days - if you're on there, I'd love to hear from you: [@irreverentmike](https://threads.net/@irreverentimke).
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Impostor Syndrome: The monster in your head]]>
https://mikebifulco.com/newsletter/impostor-syndrome-is-a-monster
https://mikebifulco.com/newsletter/impostor-syndrome-is-a-monster
Tue, 18 Jun 2024 00:00:00 GMT
(Don't just take my word for it: [Cleveland Clinic](https://health.clevelandclinic.org/a-psychologist-explains-how-to-deal-with-imposter-syndrome), [Psychology Today](https://www.psychologytoday.com/us/blog/neuroscience-in-everyday-life/202308/overcoming-imposter-syndrome-6-evidence-based-strategies), and [BetterUp](https://www.betterup.com/blog/what-is-imposter-syndrome-and-how-to-avoid-it) all have great, science-based advice on overcoming imposter syndrome.)
## Go do it
One of the greatest gifts this newsletter has given me is the opportunity to meet and talk to so many people who are in the early days of their journey. Tiny Improvements readers include creators, developers, and startup founders (and more) who all share a common thread: we're pushing ourselves to grow, to learn, and to create.
Overwhelmingly, I feel like so many of the people I talk to are teetering on the very edge of _doing the thing they want to do_. Consider this your sign to hit the `publish` button: you've waited long enough, and you'll only get better if you _do the thing._
Oh, and by the way - [I hit publish this morning](https://youtu.be/Q7ZMlgbrZxQ).
---
## The push you need to get started
My **favorite blog post of all time** is Chris Coyier's [There is no bar](https://chriscoyier.net/2022/06/27/there-is-no-bar/). It's true -- when you're at the wheel as a creator, there is no bar to clear. You set the bar by doing the work, and the only way to get better is to keep doing it.
You may also enjoy my previous newsletter [There's no right way to do it](https://mikebifulco.com/newsletter/no-right-way-to-do-it) - a reminder that a change in perspective can be the push you need.
I've also writren a treatise on [The trick to publishing online](https://mikebifulco.com/newsletter/today-is-your-day-to-start). You'll be surprised how simple it is.
---
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Statistically, nobody has used your app]]>
https://mikebifulco.com/newsletter/jakobs-law-design-ux
https://mikebifulco.com/newsletter/jakobs-law-design-ux
Tue, 11 Jun 2024 00:00:00 GMT
people spend most of their time on other sites and apps . This means that people inherently prefer your site to work _the same way_ as all the other sites they already know.
**Jakob's Law** is named after UX pioneer Jakob Nielsen, who is a (now-retired) UX researcher and principal of the Nielsen Norman Group. He's been a leading voice in the field of usability for over 25 years.
In other words, if every list, page, and form on your site is built in a way that's familiar to users, they're more likely to understand how to use it. This is why design patterns are so important.
You can think of design patterns as the common solutions to common problems. They're the tried-and-true ways of doing things that users are already familiar with.
Some examples of design patterns include:
- **The hamburger menu** - a common way to hide navigation links on mobile devices
- **Infinite scrolling** - a way to load more content as users scroll down the page
- **The card layout** - a way to organize content into bite-sized chunks
These should all sound familiar -- and you probably know what they should feel like to use. By using common design patterns, people using your site will _already know how it works_, at least on some level.
Jakob's Law is a reminder that you don't have to reinvent the wheel. Instead, borrow bits and pieces that are common to other sites and apps. This will make your work feel more familiar, and therefore more usable, to your users.
### It can still _feel_ unique
Just because you're using design patterns doesn't mean your site has to look like every other site out there. You can still add your own unique touches to make your site stand out. Focus on getting the basics right first, and then tweak the details to make your site feel unique.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The Aesthetic-Usability Effect]]>
https://mikebifulco.com/newsletter/aesthetic-usability-effect
https://mikebifulco.com/newsletter/aesthetic-usability-effect
Tue, 04 Jun 2024 00:00:00 GMT
The Aesthetic-Usability Effect is a psychological phenomenon where users perceive more aesthetically pleasing designs as easier to use than less aesthetically pleasing designs.
> [More on Wikipedia](https://en.wikipedia.org/wiki/Aesthetic-usability_effect).
This means that if your app isn't designed well, users will perceive it as _harder to use_ than a more visually appealing app, even if the functionality is identical.
Read that again - and let it sink in a bit: the _exact same app_ can be perceived as harder to use (and thus _less valuable_) if it's ugly.
As a bit of a contrived example, which of these two ChatGPTs would you rather use?
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Three things school taught me (and Three things it didn't)]]>
https://mikebifulco.com/newsletter/what-i-learned-studying-cs
https://mikebifulco.com/newsletter/what-i-learned-studying-cs
Mon, 27 May 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Shrimps is Bugs: Red Lobster ate itself to death]]>
https://mikebifulco.com/newsletter/shrimps-is-bugs
https://mikebifulco.com/newsletter/shrimps-is-bugs
Tue, 21 May 2024 00:00:00 GMT
if you're working on your business plan, try not to include an all-you-can-eat
shrimp promotion in the mix.
That's it. That's the secret to business.
## The numbers matter as much as the product
Okay, look - here's the thing: if you want to have a business that pays the bills, understanding the financial model behind your products is crucial.
I'd bet a whole stack of clams that there was at least one accountant at Red Lobster who was red in the face trying to explain to their leadership that a "giving away free shrimps" business model was going to be a disaster.
Promotions and giveaways can be powerful tools to attract customers, but they need to be carefully planned and executed with a clear understanding of their impact on your business.
There's also a point to be made about the value of giving away _some_ services to early adopters to create hype and brand awareness. Promotions can certainly build buzz and loyalty, but as your product grows, you need to start getting paid to ensure sustainability and growth.
Generosity has its place, but it's essential to balance it with a sound financial strategy.
## Start with the basics: P&L
Many developers (myself included) don't have a background in finance - and that's okay! But it's crucial to understand the basics of your business's financials. Here are a few key terms to get you started:
- **Revenue**: The money you make from selling your product or service.
- **Cost of Goods Sold (COGS)**: The direct costs associated with producing your product or service.
- **Gross Profit**: Revenue minus COGS.
- **Operating Expenses**: The costs of running your business, like salaries, rent, and utilities.
- **Net Profit**: Gross profit minus operating expenses.
In developer terms, getting this right is about inputs and outputs: you're trying to build a machine that takes in more money than it costs to run.
Understanding these numbers will help you make informed decisions about your business and avoid making shellfish decisions that could sink your ship. (I'll stop.)
## Document your expenses
When you're building a product, it's easy to get caught up in the excitement of development and forget about the costs. But documenting your expenses is crucial to understanding your financial health. Keep track of everything you spend, from hosting fees to marketing costs, and make sure you're accounting for them in your financial model.
You don't need to use a fancy tool to do this: a spreadsheet will work just fine. The key is to be diligent about tracking your expenses and updating your financial model regularly.
## Understand your costs
Once you've documented your expenses, it's time to understand your costs. Calculate how much it costs to acquire a customer, including marketing and sales expenses. Then, match these against the price your customers pay. Determine how many months a customer needs to stay for you to break even and eventually make a profit.
Many developers who get into building products don't fully understand this, but it's crucial to go through this rigor. Even with a fast-growing product, overlooking these details can easily bury you in a failing business model.
If the math doesn't add up, it's time to reevaluate some combination of your pricing strategy, marketing efforts, and product features that drive costs up.
Your goal is to build a product that can pay for itself -- and much more, hopefully.
(also, shrimps is bugs. 🦐🦐🦐)
---
## Ya gotta get paid
If you're building a product, you need to get paid for it. It's as simple as that.
- [F\*ck you, pay me](https://www.youtube.com/watch?v=jVkLVRt6c1U) is a classic talk from Mike Monteiro about the importance of getting paid for your work. It's a must-watch for anyone who's ever struggled to get clients to pay up.
- If you're an Indiehacker building a SaaS, this post on Indiehackers has lots of great wisdom: [How to price your product](https://www.indiehackers.com/post/how-to-price-your-product-indie-hackers-shouldnt-follow-the-usual-advice-0b994f58f6)
- If you're building a developer product, you may find my recent [interview with the founder of Unkey](https://apisyouwonthate.com/podcast/unkey-globally-distributed-api-key-generation-with-cofounder-james-perkins/) interesting. We talked a bit about building API products with usage-based pricing, and how to make sure you're getting paid for the value you're providing.
---
## I want to hear from you!
If you've got books, videos, podcasts, or articles to recommend for engineers who want to build a better business, send them my way. I'm all ears!
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The Endowment Effect: why useful trials make for sticky products]]>
https://mikebifulco.com/newsletter/endowment-effect-and-designing-free-trials
https://mikebifulco.com/newsletter/endowment-effect-and-designing-free-trials
Wed, 15 May 2024 00:00:00 GMT
...In other words, for the exact same object, participants assigned a higher
value to the thing they owned versus the thing they were thinking about
buying.
The misalignment between these two prices is the endowment effect in action. People value things more highly when they own them.
## Free trials and the Endowment Effect
One way is to offer a free trial of your product. By giving people the opportunity to use your product before they buy it, you create a sense of ownership. They become attached to the product and are more likely to continue using it after the trial period ends.
Companies like **Spotify** and **Netflix** take advantage of the endowment effect by getting users hooked quickly. By offering free trials, they give new customers a chance to feel what it's like to _have_ access to their vast libraries of media.
This creates a sense of ownership, making it hard to part ways with the service when the trial period runs out. The value they see during the trial makes it easier to pay for the service, and keeps customers coming back for more.
Similarly, **Slack** and **Notion** use the endowment effect by empowering free users. By offering thoughtful free tiers, they make their products sticky and useful. Once they're onboard, it is really hard for customers to give up what they've gotten used to.
By the time their users get to the end of their trial period, they are so attached to the product that they can't imagine going back to the way things were before.
## Designing a great trial experience
To make the most of the endowment effect, it's important to design a great trial experience. Here are a few tips to get you started:
1. **Make it easy to sign up**: The easier it is for people to sign up for your trial, the more likely they are to do it. Remove any barriers to entry and make the process as simple as possible. In many cases, this means not requiring a credit card up front, as counterintuitive as that may seem.
2. **Show value early**: Give people a taste of what your product can do right away. Show them the benefits of using your product and how it can help them solve their problems. This may also mean giving unfettered access to your product during the trial period, and restricting access to premium features only after the trial ends.
3. **Measure success**: Track how people are using your product during the trial period. Look for patterns in usage and identify areas where people are getting stuck. Use this information to improve your product and make it stickier.
4. **Offer support**: Make sure people have the help they need to get started with your product. Offer tutorials, guides, and customer support to help them make the most of their trial. Use information collected through analytics to offer personalized tips and support to users.
You've spent countless hours building an great product - make sure people get a chance to see how great it is. Offering a free trial is a great way to do that, and the endowment effect can help you make your product stickier in the long run.
---
## Tools for making a valuable free trial
Setting up a free trial for your product doesn't have to be complicated. There are plenty of tools available to help you get started. Here are a few to consider:
1. If you use **[Stripe for subscriptions](https://docs.stripe.com/billing/subscriptions/trials)**, you can configure a free trial period for your customers. This allows them to try your product before they buy it, without having to enter their payment information up front.
2. It's nearly impossible to get your pricing strategy right on the first try. That's the thesis that my friends over at **[Stigg](https://www.stigg.io/)** have based their products on. They make it easy to test different pricing strategies and see which one works best for your business.
3. If you're building a developer product with usage-based billing, you should check out **[Unkey.dev](https://www.unkey.com/)** - they make it dead simple to add analtics and usage-based billing around API keys to your product.
---
## Some products-in-progress worth checking out
- [Pastmaps](https://pastmaps.com/plus?src=tinyimprovements) is a vast library of historical maps that you can overlay on modern maps. Seeing how your neighborhood has changed over time can be really eye-opening. Pastmaps has a 7-day free trial for its premium features, and is being built by Craig Campbell, who goes by [@that.map.guy.craig](https://www.threads.net/@that.map.guy.craig) on Threads.
- [PodCharm](https://podcharm.com/) is a product designed to help podcasters do a better job of growing their audiences. PodCharm's free tier is _super_ generous, and sends a strong signal: PodCharm will be successful only if its customers' shows are successful. That's a win-win alignment of incentives. Shout out to my dude [Tony Mastrorio](https://www.threads.net/@tonydotcoms) for building this. Give it a shot if you're a podcaster.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Beyond the walled garden: what Spotify and Substack get wrong]]>
https://mikebifulco.com/newsletter/beyond-the-walled-garden
https://mikebifulco.com/newsletter/beyond-the-walled-garden
Tue, 30 Apr 2024 00:00:00 GMT
On the other side of the park, what was once a quaint bungalow neighborhood on the city's outskirts has had one house after another bulldozed. It's now lined with freshly built mcmansions, built on speculation for suburbanites with deep pockets.
In the past couple months, one build in particular has caught my attention - a huge, swollen brick home built right to the edges of its boundaries. It's located on edge of the park, with its back yard oriented so that the sun rises perfectly through the trees, highlighting the simple wooden footbridge that crosses the creek, built years ago to give homeowners access to the park.
The new home has risen from its foundation quickly, and while I don't typically _love_ the design choices made by home builders in my area, this one really sticks in my craw. Someone made the decision to build an 8 foot fence around the perimeter of the yard - completely obscuring access to the park.
I know _someone else's home_ shouldn't make me this mad - this home will probably sell for close to $2M (if not more). But, to me, the builder has _completely_ lost the plot.
Why would someone buy such a beautiful plot of land and spend their money hiding from it?
## Spotify and Substack walled themselves in
This, I feel, is a great metaphor for strategic missteps by companies like Spotify and Substack. Two different products in different spaces, built to take advantage of a huge opportunity – have built very strange walled gardens around their products that sounded like a good idea at first.
Spotify established a huge user base as the de facto music subscription for many people. In the never ending search of growth, they wanted to make their platform the place where everyone goes to listen to podcasts as well.
Rather than build the best podcast player in the world, they bought up podcasts left and right, making them exclusive to Spotify.
For many people, this meant their only choice to listen to their favorite shows was to switch to Spotify.
Does that sound like a great way to build a sticky product? I'll let you decide, but it's safe to say that their [$1B Bet on podcasts isn't going well](https://www.wsj.com/podcasts/the-journal/spotify-1-billion-bet-isnt-going-well/75665f50-cabb-48c9-8f5c-d05e94d8f7f8).
In the creator world, newsletter authoring platform Substack was heralded as the author's best friend - they made it easy to write a newsletter and build an audience. It was among the first newsletter tools to promise network-effect growth by letting authors recommend one another's newsletters as a first-party platform feature. They added features for podcasters, as well as [some twitter-like features](https://techcrunch.com/2023/04/05/substacks-new-short-form-notes-feed-looks-a-lot-like-twitter/) as a response to Twitter's leadership collapse.
Then... they made some gutless decisions around content moderation.
Substack continues to [refuse to shut down alt-right, and hyper-conservative newsletters](https://mashable.com/article/why-are-people-leaving-substack-content-moderation-controversy) with _seriously_ weak reasoning for their [anti-censorship stance](https://www.theguardian.com/media/2024/jan/03/substack-user-revolt-anti-censorship-stance-neo-nazis):
> "...we don't think that censorship (including through demonetizing publications) makes the problem go away - in fact, it makes it worse."
Ah, _cool_.
I'm sure you can understand why authors are leaving the platform in droves - after all, one of Substack's value propositions is that they'll recommend _other authors' work_ to help newsletters grow.
Woof.
Meanwhile, competing product teams see opportunity knocking: Ghost announced that they're [adding fediverse features later this year](https://www.msn.com/en-us/news/technology/look-out-substack-ghost-will-join-the-fediverse-this-year/ar-AA1nvI4S).
## Sneak in while the walls are being built
There's a lot to be learned from the decisions companies make about their products once they get really large - these sorts of missteps can opens the door for thoughtfully built and well-timed products. As a builder, do your best to keep an ear to the ground for fissures opening up in the giants' walled gardens.
If you can find a way to build a product that solves a problem for users and takes advantage of a misstep by a competitor, you're in a great spot to grow quickly.
I'm not saying you should wait for a competitor to make a mistake - but if you're paying attention, of course - build your thing with conviction because it's a good idea, but also be ready to move quickly when opportunities arise.
You can be the one to build the footbridge over the creek, and let the sun shine through.
---
## Champagne for my real friends
I thought I'd share some work from people in my network this week. You're going to love these:
- Josh Finnie wrote a great article about [Adding JSON-LD to his Astro site](https://www.joshfinnie.com/blog/adding-json-ld-to-my-blog/) - it's a great read if you're looking to improve your site's SEO.
- CJ Avilla published an article about [Caching ViewComponents in Ruby on Rails](https://www.cjav.dev/articles/caching-viewcomponents), which we've been implementing at Craftwork recently.
- Over on Primary Focus, Ms. Natalie produced a great interview recently about [what parents need to know about ADHD and kids](https://www.youtube.com/watch?v=UsqG7m5NQ1E&t=7s). Her guest is super knowledgable and it's a great watch.
---
## Try these out though
Here's a few tools that I think are worth checking out:
### A podcast player for note takers
[Snipd](https://www.snipd.com/) is a podcast app that automatically transcribes podcasts and lets you take notes from them as "snips". It's a great idea - you may recall a few months back [I built a podcast summarizer with AI](https://mikebifulco.com/newsletter/build-something-useful-with-ai). I think the gang at Snipd are on to something really special here.
### Make storyboards that don't suck
[Storytribe](https://storytribeapp.com/) an app for creating storyboards using vector images. They have created an _immense_ library of customizable vectors that you can assemble to make some really compelling storyboards for your next product, feature, or presentation.
### Ghost is the CMS for creators
I mentioned [Ghost](https://ghost.org/?via=mike21) above (that's my referral link, btw) - it's a CMS that makes it easy for creators to build a website, write a blog, and publish a newsletter. They're adding some really interesting features this year, and I think they're a great alternative to Substack for authors who want to own their content and their audience. I actually help run 2 different sites with Ghost: [APIs You Won't Hate](https://apisyouwonthate.com) and [Primary Focus](https://primaryfocus.tv) both use it.
---
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Simple Habits for a Happier Team]]>
https://mikebifulco.com/newsletter/simple-habits-for-a-happier-team
https://mikebifulco.com/newsletter/simple-habits-for-a-happier-team
Tue, 23 Apr 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Designing for hospitality]]>
https://mikebifulco.com/newsletter/unreasonable-hospitality-and-design
https://mikebifulco.com/newsletter/unreasonable-hospitality-and-design
Tue, 09 Apr 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Keep your tools sharp]]>
https://mikebifulco.com/newsletter/keep-your-tools-sharp
https://mikebifulco.com/newsletter/keep-your-tools-sharp
Tue, 02 Apr 2024 00:00:00 GMT
### Zen Mode
[Zen Mode for VS Code](https://code.visualstudio.com/docs/getstarted/userinterface#_zen-mode) is a great way to tune your IDE to be more focused. I use it for writing articles and newsletters. It's _built in_ to VS Code, so you don't need to install anything. Just press `Ctrl + K, Z` to enter Zen Mode, or the `Toggle Zen Mode` command in the command palette.
Straight out of the box, Zen mode is pretty damn minimal - and that's not for everyone (myself included). To customize Zen mode, open up VS Code settings with `Command + ,` and search for `zenMode`. Y
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Why new frameworks make better developers]]>
https://mikebifulco.com/newsletter/why-new-frameworks-make-better-developers
https://mikebifulco.com/newsletter/why-new-frameworks-make-better-developers
Tue, 26 Mar 2024 00:00:00 GMT
In true extrovert fashion, I jumped into learning about Astro by building with it in public on a [YouTube Livestream](https://www.youtube.com/watch?v=wyJYInvZya8) last Saturday.
It... was tough, honestly.
Over the course of a few hours, go from explaining my approach and stream-of-consciousness thinking, to silently debugging a react-in-astro challenge for... a while.
Perhaps appropriately, the stream ended abruptly after my wife told me my webcam was no longer working... followed shortly by OBS (the streaming software I use) crashing. 🤦♂
## So learning in public wasn't a great success
The livestream was a struggle. I stepped away from my Astro project, and came back to it the next day.
Something clicked. I was able to get past the issue I was having, and my project really started to fly together quickly. I was able to get a lot done in a short amount of time, and I was feeling pretty good about it. (By the way: I'll be sharing the fruits of my labor in the coming weeks...)
My second day of building honestly felt a lot more like typical dev work does for me - I was in a flow state, juggling tiny tasks and debugging issues as they came up. I felt unfazed to be working with Astro; a completely different experience compared to just the prior day.
## It's familiar, but not too familiar
As I got to this point into the project, I could feel myself pulling from experience building with _all_ of the other web frameworks I've built with, whether directly or indirectly.
I've built production apps with many frameworks over the years: from create-react-app to Remix.run, Next.js to Ruby on Rails and now Astro. I've also poked around at countless CSS and UI libraries like Bootstrap, Tailwind, Chakra, and ShadCN UI. It's a little difficult to describe, but the time I spent with each of these tools has made me a better developer.
Of course, learning about Bootstrap doesn't inherently make me understand React -- but it did add to the foundation of skills I use to debug things, to research solutions when I'm stuck, and to ask for help when I need it.
That new error that just popped up? I've seen something like it before. Oh, this component isn't rendering correctly? I know how to debug that. This layout isn't quite right? I know how to fix it. You get the idea.
## The Hierarchy of Competence
In cognitive psychology, there is a model called the [Hierarchy of Competence](https://en.wikipedia.org/wiki/Four_stages_of_competence). It describes the stages of learning a new skill, from unconscious incompetence to unconscious competence:
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Take my money! Some of my favorite tools... and why I pay for them]]>
https://mikebifulco.com/newsletter/take-my-money-tools-i-pay-for
https://mikebifulco.com/newsletter/take-my-money-tools-i-pay-for
Tue, 19 Mar 2024 00:00:00 GMT
Being the nightmare-dev that I am, I've also sent the Transistor team a few support requests while poking around with the [Transistor API](https://developers.transistor.fm/), and they've always been quick to respond and helpful.
**Try it:** If you're thinking about starting your own podcast, and want to give Transistor a shot, you can use my referral link to get 15% off your first year: [Transistor.fm](https://transistor.fm/?via=mike-bifulco)
## Descript
**Price: $12/month**, which includes 10 hours of transcription per month, and 20 hours of screen recording per month.
Descript lets you edit audio and video files like they were a text document. Read that again. It's _wild_. I was an early adopter of Descript, and have been using it to edit Podcasts and videos for years now.
**Killer features:**
Do you say "um" and "uhhh" a lot when you're speaking? Descript can remove those for you. Do you want to add a section to your podcast where you're talking about a product, but you don't want to re-record the whole episode? Descript can do that for you. Do you want to add a video to your podcast episode? Descript can do that for you.
Descript can export video in portrait or landscape, which makes it trivial to create content for Instagram, TikTok, and YouTube.
I also love their audiogram feature, which you can use to make closed captioned clips from podcasts for social media.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[3 Tiny tips for better SEO]]>
https://mikebifulco.com/newsletter/tiny-tips-for-better-seo
https://mikebifulco.com/newsletter/tiny-tips-for-better-seo
Tue, 12 Mar 2024 00:00:00 GMT
Side note: SEO is a _massive_ topic - I'm far from an expert, but I've found it invaluable to learn a few basics. If I've got anything wrong here, or you know more than me, [I'd love to hear from you](https://threads.net/@irreverentmike)!
My position on SEO is this: it's a growth engine for your work, and when donse right, it can have a flywheel effect that will put your work in front of more people over time. It's not as immediately satisfying as racking up likes on a social media post, but it persists long-term, and can help you build a sustainable audience for your work.
It's slow-release dopamine, if you will.
I've been publishing articles under my own name for a few years now, and a steady investment in search now sends thousands of readers a month to my work. We've also been investing in SEO at [Craftwork](https://craftwork.com), and it's been fun to learn about how focusing on search for a local business differs from a personal website - but the principles are the same.
### Think about what your work will look like when it's shared
When someone comes across your work and they share it on their social media feed, you want it to look good, right? It should have a catchy, meaningful title, a useful description, and an image that draws people in. This is also what will show up when your work is shared on social media, or when it shows up in search results.
Functionally, this means you need to make sure your site has good metadata. Metadata is the information about your site that search engines use to understand what your site is about. It's also what social media platforms use to display your content when it's shared.
Here are a few tips to get you started:
- The `` and `<h1>` tags on the page are most likely to be used as the title of the page in search results. Make sure they're descriptive and accurate.
- The `<meta name="description" />` tag is used as the description of the page in search results. Try to keep it less than 150 characters, and make it a meaningful summary of the page's content.
- The `<meta property="og:image" />` tag is used as the image that shows up when your page is shared on social media. Make sure it's a high-quality image that represents the content of the page, and that it's at least 1200x630 pixels in size with an aspect ratio of 1.91:1 so it looks good on <s>all</s> most platforms.
### Use Structured Data with JSON-LD for enhanced search results
Picture a list of Google search results in your head. You're probably seeing a list of blue links with a short description below them. But have you ever seen a search result with a video thumbnail, or a recipe with a picture and a list of ingredients? That's no accident - it's the result of Google's crawlers finding something called _structured data_ on the result's page.
<Image
publicId="newsletters/tiny-tips-for-better-seo/enhanced-search-results"
alt="Enhanced search results"
/>
When your site shows up like this, it's called a _rich result_. It can help your site stand out in search results, and give your work a better chance of being seen.
There are many types of Structured Data which are supported by Google, including:
- Articles
- Videos
- Events
- Product
- Software App
...and more. Check out Google's list of [Structured data markup that Google Search supports](https://developers.google.com/search/docs/guides/search-gallery) to see if there's a type that fits your content. If there is, you can use something called JSON-LD to pages on your site to help Google understand what your content is about.
I recently did this for my website - pages that feature video now include `VideoObject` structured data. It's as simple as including a bit of JSON on the page in a `<script />` tag. Check out my recent Pull Request to see how I made it happen: [mbifulco/blog#775: Add Structured Data for Video](https://github.com/mbifulco/blog/pull/775).
<Image
publicId="newsletters/tiny-tips-for-better-seo/video-results"
alt="Structured Data"
caption="Structured Data inspection results for a video on my site. Success! Google can see it."
/>
### Keyword research is a great way to understand your audience
Alright, friends -- here's where I need to call _myself_ out - I'm not great at this. But I know it's important, and I'm working on it.
Here's the idea: when making something new, it's reallllly helpful to make sure you're creating content about things people are actually searching for. Keyword research to understand what people are searching for, and then create content that matches those searches.
<Image
publicId="newsletters/tiny-tips-for-better-seo/keyword-research"
alt="Keyword research"
caption="Keyword results for my site on both Google Search Console and Ahrefs Webmaster Tools"
/>
There are a lot of tools out there to help you with keyword research, but I've found that the best (free) tools for this are [Google Search Console](https://search.google.com/search-console) and [Ahrefs Webmaster Tools](https://ahrefs.com/webmaster-tools). Both of these tools will show you what people are searching for when they find your site, and what your site is ranking for. This can help you understand what people are looking for, and what you can do to make your site more relevant to those searches.
---
## Free tools to help you understand your site's SEO
### Make sure those titles and descriptions are just right
I really like the [SEO extension from Detailed](https://detailed.com/extension/) as a tool for inspecting the metadata on a page. It's a Chrome extension that shows you the metadata for the page you're on, and gives you a score for how well it's set up for search. It's a great way to quickly check if your titles and descriptions are set up correctly.
### For Structured Data
If you're adding Structured data to your site, you can use use [Google Search Central Schema Markup Testing Tool](https://developers.google.com/search/docs/appearance/structured-data) and [Schema.org's validator](https://validator.schema.org/#url=https%3A%2F%2Fmikebifulco-com-git-feat-metadata-mbifulco.vercel.app%2Fposts%2Flive-coding-satori-og-images-nextjs) to make sure your pages are set up correctly.
### Learn from the best
If you're looking for more, you may want to check out [Positional's fantastic SEO newsletter](https://www.positional.com/newsletter) - it's well-researched, highly informed, and a great way to learn more about SEO.
---
## More from me on SEO
- I wrote a tutorial on setting up [Self-healing URLs on your Next.js site](https://mikebifulco.com/posts/self-healing-urls-nextjs-seo) that you might find useful.
- Ever wonder [how to correctly add subtitles to your h1 tags](https://mikebifulco.com/posts/semantic-html-heading-subtitle)? I've got you covered.
- These are [the SEO tools I use to grow my sites to 20k+ vistors/month](https://mikebifulco.com/posts/seo-tools-for-new-web-projects).
]]></content:encoded>
<author>hello@mikebifulco.com (Mike Bifulco @irreverentmike)</author>
</item>
<item>
<title><![CDATA[The first year of being a technical startup cofounder]]>
https://mikebifulco.com/newsletter/reflecting-on-one-year-as-startup-cto
https://mikebifulco.com/newsletter/reflecting-on-one-year-as-startup-cto
Tue, 05 Mar 2024 00:00:00 GMT
### Their tech, Their products.... Their Stories.
Code Story is a podcast featuring founders, tech leaders, CTOs, CEOs, and software architects, reflecting on their human stories in creating world changing, disruptive digital products.
## You won't know some things until you try
I've spent a good deal of my career working in UX. I've gotten to work with some incredibly talented designers and UX researchers, and I do believe that good design is a competitive advantage. Even still, when building real features for real people, you can't always predict what will work and what won't.
Designing great software needs to be both proactive and reactive - you need to have a vision for what you want to build, but you also need to actively respond to feedback and data.
For example: the very first version of Craftwork's estimate builder was designed to be _extremely_ self-serve - we built a tool that would let customers scope out their entire project without needing to talk to us. We thought this would be a great way to let people get a feel for what we could do for them, and to be extremely transparent about what their project would cost.
In practice, we found that people were often overwhelmed by the number of choices they had to make. Over and over we saw people getting stuck playing with our estimate builder, weighing the cost of one little change against another. Many people got stuck on this process, and never actually submitted a request for painting.
On a hunch, we ran a quick A/B test to see if it would be more productive to have a conversation with one of our team members first, and the results were clear: our customers have lots of interesting questions, and a price calculator wasn't answering all of them.
We've since reworked the estimate process to be more of a guided conversation, and we've found that using it to create a human connection with our customers has been a great way to build trust and to get the ball rolling on a project.
## You can't do it alone
While building my last company, I was convinced that we could do everything with an exceptionally small team - we were just 3 people, from inception to acquisition. I'm proud to say we did the damn thing, but it was _really_ difficult. You'll often hear founding employees at startups talk about how they're "wearing many hats" - that's definitely true, and it makes work a lot of fun. It's also true that you can't wear _all_ the hats. It's _also also_ true that there exciting, beautiful new hats out there that you don't know you need to wear.
From my first day as a working professional, I've always wanted to be surrounded by people who are smarter than me. Building Craftwork has been no exception - my cofounders are dedicated, talented, and damn good at what they do. We have also hired some _truly_ amazing people to build our team.
### A few things I've learned about building the right team:
Engineers tend to undervalue the importance of understanding the mechanics of the business. Our growth team at Craftwork has been instrumental in helping us understand how to reach new customers, and how to build a _profitable_ product that people want.
Building a brand is like nurturing a garden. It takes time, patience, and a lot of care. Craftwork's brand has really grown into something special, and it's been a joy to watch it happen. Give our [Instagram](https://www.instagram.com/craftworkpaint/) a peek if you want to see what I mean.
At this stage in the startup journey, hiring engineers is really challenging. The perfect engineer for a startup is someone who is comfortable with a lot of ambiguity, who can work independently, and who can communicate well... in addition to being technically competent. It's a tall order, and it can be a challenge to find the right people.
When I have roles open on my team, hiring is the most important thing I do day to day. It is also a full-time job in itself. It requires a fair deal of patience to assemble the right team, as well as a drive to actively and creatively seek out the right people.
## Just enough (and nothing more)
I recently came across the Japanese Phrase ほどほど (hodohodo), which means "just enough." I've been trying to use it as a reminder to keep things simple, and to avoid overcomplicating things. My team is tasked with building the features we need most _today,_ with eyes on what we'll need in 6 months and a year... and that can be overwhelming. It's easy to spiral out of control with feature creep and over-engineering, and finding ways to help each other _just-enough-for-now_ is a team remit.
_Just enough_ spills over into many areas:
- **Build vs buy:** almost every feature our team needs can be bought from a SaaS vendor, or coach built by our product team. Making this decision can be nuanced and difficult, and it's something we revisit regularly.
- **Adopting tooling:** Engineers love to play with new tools - there's always a new framework, language, database, or library to poke around with. We've been very deliberate about what we adopt, and we've been very careful to avoid adopting things just because they're new and shiny. We have also adopted tools with good intentions, and found ourselves jettisoning them when they don't work out for one reason or another.
- **Shipping new features:** Adding new functionality for our customers and teammates is always tempting, but it's important to be mindful of the complexity that comes with each new feature. Our engineering team is small-and-mighty, and ever new feature we build means we have less time to support the features we've already built.
I used to say _Just enough (and nothing more)_ - there's a funny irony in that phrase. A year into this thing, this feels more accurate: Just enough (and nothing more).
---
## More on building startups
If you're inerested in a more detailed look at the past year, here's a few more links you might find interesting:
- 🎙️ [My interview on the podcast CodeStory](https://codestory.co/podcast/e14-mike-bifulco-craftwork/) was released today. Codestory's creator, Noah, was kind enough to reach out about sponsoring this newsletter as well. Telling Craftwork's origin story is a good reminder of how far we've come in a year.
- 🥽 [Learning is an infinite game](https://mikebifulco.com/newsletter/learning-is-an-infinite-game) tells a little bit about how we used 3D printing tech to produce tooling for large-scale paint projects, and what it was like to dive in to CAD modeling after years away.
- 📋 Hiring is hard. There have also been a ton of layoffs in the past year-and-change. I wrote [Your Resume Sucks. Here's how to fix it](https://mikebifulco.com/newsletter/your-resume-sucks) in an effort to help engineers represent themselves better when looking for a job.
---
## Thanks for reading
I'm grateful for the opportunity to reflect on the past year, and I'm grateful for the opportunity to share it with you. If you have any questions about what it's like to build a startup, I'd love to hear from you. Reply to this email and let me know what's on your mind.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[I hate Tailwind CSS. Here's why I use it.]]>
https://mikebifulco.com/newsletter/i-hate-tailwind-css-heres-why-i-use-it
https://mikebifulco.com/newsletter/i-hate-tailwind-css-heres-why-i-use-it
Tue, 27 Feb 2024 00:00:00 GMT
So in the end, do I hate Tailwind? No, of course not. I've come to appreciate it for what it is: a pragmatic choice that has helped us build better products, faster. And that's something I can get behind.
**I'd love to hear from you**. What are your thoughts on Tailwind? Do you have any tips for using it more effectively? Is there a UI Library you love that I missed? Maybe you have a wishlist of your own? Let me know by replying to this email.
---
## What I'm thinking about this week: Watching experts work
### 🎶 A musical savant showcasing mastry
There's something extremely satisfying about watching someone who's really good at their job do their thing. I've been sharing this video of musical composer [Jacob Collier using Logic masterfully](https://www.youtube.com/watch?v=tVHyuhsAles) to compose a song in real time. There's such a beautiful confluence of skill, creativity, and deep understanding in this video.
The best creative tools make superusers shine, and I think that's something we should all strive for in our work.
### 🔌 Plug kinda nerdy, but he chill
I was pretty deep in the YouTube rabbit hole when I came across [@AllThingsOnePlace](https://www.youtube.com/watch?v=-JkUcrlDtZ0). This is an electrical engineer whose videos are all about analyzing and reviewing power supplies and other electrical components. I promise it is _way_ more interesting than it sounds. I had no idea that you could measure the _quality_ of power coming from a USB charger!
---
## More from me
### 🎙️ [Every business is an API business](https://apisyouwonthate.com/podcast/allan-knabe-apiable-api-portal/)
In my recent podcast interview with Allan Knabe from Apiable for APIs You Won't Hate, we dicussed how Apiable is building an API Portal service that helps API teams to create, secure, market, and monetize API products. Catch it on the [APIs You Won't Hate feed here](https://apisyouwonthate.com/podcast/allan-knabe-apiable-api-portal/)), or wherever you listen to your podcasts.
### 🎥 [I've been more active on YouTube](https://youtube.com/@mikebifulco?sub_confirmation=1)
Over the past month or so, I've gotten back into live coding on YouTube on the weekends. I've also got plans to start publishing more dev tutorials and startup content. If you're interested in that kind of thing, [subscribe to my channel](https://youtube.com/@mikebifulco?sub_confirmation=1) to stay up to date.
---
Hey, one more thing: make sure you [register to vote](https://vote.org). It's important. Like, deeply, existentially important.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Gestalt: Design principles every developer should know]]>
https://mikebifulco.com/newsletter/gestalt-design-principles-for-developers
https://mikebifulco.com/newsletter/gestalt-design-principles-for-developers
Tue, 13 Feb 2024 00:00:00 GMT
On the left, the form is laid out in a way that feels familiar. On the right, complete unhinged madness. It's not _technically_ in violation of the geneva convention, but it's close.
### Proximity and Similarity: the power of grouping
Proximity and similarity are two of the most powerful tools in a designer's toolbox. They allow us to group elements together in a way that makes sense to the user. This is why one of the fundamental building blocks of most CSS design systems includes a grid system. It's a way to ensure that the space in your design is consistent and harmonious, guiding the user's eye and creating a sense of order and structure.
What does this mean? It means that the space around and between elements is just as important as the elements themselves. It's the difference between a cluttered, confusing design and a clean, intuitive one. Consistency is critical here: spacing between related elements should be consistent, and the space between unrelated elements should be distinct.
Take a look at this example:
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Build, measure, listen, rebuild]]>
https://mikebifulco.com/newsletter/build-measure-listen-rebuild
https://mikebifulco.com/newsletter/build-measure-listen-rebuild
Mon, 22 Jan 2024 00:00:00 GMT
## I've been Live Coding again
I spent a few hours last weekend live coding on my YouTube channel, [@mikebifulco](https://youtube.com/@mikebifulco?sub_confirmation=1). I've got aspirations to publish more pre-recorded content as well.
You can see the replay on YouTube, or here: [Configuring Resend Broadcasts for newsletters on my Next.js website](https://mikebifulco.com/posts/live-coding-resend-broadcasts-nextjs)
If you're interested in seeing more videos from me, please [subscribe](https://youtube.com/@mikebifulco?sub_confirmation=1)!
---
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Why your favorite apps and creators all pivot in January]]>
https://mikebifulco.com/newsletter/creators-startups-january-pivot
https://mikebifulco.com/newsletter/creators-startups-january-pivot
Tue, 16 Jan 2024 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Fitts' Law and the Beauty of Big Goals]]>
https://mikebifulco.com/newsletter/fitts-law-and-the-beauty-of-big-goals
https://mikebifulco.com/newsletter/fitts-law-and-the-beauty-of-big-goals
Tue, 09 Jan 2024 00:00:00 GMT
_Editor's note: Happy New Year, gang! Tiny Improvements took off for a few weeks at the end of the year so I could [fix my leg, lol](https://www.threads.net/@irreverentmike/post/C1GCgSVsZ5t), but we're back in action and will be coming to your inbox mostly-weekly for the foreseeable future. I hope you're well._
**Fitts' Law** is simple: the time required to move to a target is a function of the distance to the target and the size of the target. The further away and smaller the target, the longer it takes to reach it. The closer and larger the target, the faster it is to reach it. ([Wikipedia](https://en.wikipedia.org/wiki/Fitts's_law))
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The product design spectrum: crowdsourcing, user research, and the myopic approach]]>
https://mikebifulco.com/newsletter/crowdsourcing-vs-user-research-ux
https://mikebifulco.com/newsletter/crowdsourcing-vs-user-research-ux
Tue, 05 Dec 2023 00:00:00 GMT
Earlier this year, in what could be the best or worst decision ever made, Chinese smartphone maker ZTE turned to the general public for ideas for its next smartphone.
(cue foreboding music)
As you might imagine, after asking The Internet™️ to submit ideas for something, they ended up with _many_ varied responses. The result was a full on fever-dream of a phone, called _Hawkeye_. In addition to an array of typical features you'd expect from a smartphone, it also had:
- **Eye tracking**: the phone would scroll up and down based on where you were looking.
- **A self-adhesive back**: the phone would stick to any surface, like a wall or a window, so you could take selfies or watch videos hands-free
- **A vaguely defined split screen feature**: despite what you might guess, this was described as "...[a] feature that allows only the user to see what's on-screen". I'm honestly not sure what that means.
Don't get me wrong, if done well, at least one of these features could be really useful for accessibility. You could certainly never sell me on carrying a _sticky_ phone in my pocket (or holding one up to my face, for crying out loud). It's a confusing grab-bag of features that don't seem to have much in common, and it's hard to imagine how they would work together.
So, how did it turn out? Well... it didn't. After crowdsourcing ideas and building prototypes of the phone, ZTE launched a kickstarter campaign, likely in an effort to gauge interest in the phone. They raised $36k of their $500,000 goal, and the [project was cancelled](https://www.theverge.com/circuitbreaker/2017/2/17/14647990/zte-hawkeye-phone-kickstarter-campaign-end).
So what happened? Why did this campaign fail so spectacularly? Well, I think the nature of campaigns like this on the internet is not to find the best ideas, but to find the most _popular_ ideas. And the most popular ideas are not always the best ones, especially when there's so much clout to be gained from having your idea chosen (oh hey, _[boaty mcboatface](https://www.nytimes.com/2016/03/22/world/europe/boaty-mcboatface-what-you-get-when-you-let-the-internet-decide.html),_ didn't see you there!).
Think about it - how many of your least favorite products feel like they were designed by a committee? I can think of a few examples of products that I _used to_ love that have gotten bloated and confusing, particularly after an enterprise-scale company acquired them.
---
### The myopic approach: Why automakers don't have just _one_ designer
On the opposite side of the "let's crowdsource a product", there's the myopic approach. Putting trust in _just one person_ to design a product is exceedingly rare. To be successful, that person has to have an acute ability to understand the needs of the people who will use the product, and to design something that meets those needs, while also being technically feasible and financially viable.
This has happened in the automotive industry -- a place where R&D costs are immense, and the cost of a failed product can be catastrophic.
Imagine that: an auto manufacturer trusting _one person_ to design a car for broad public adoption, with a host of features that aren't exactly cohesive, a design that's... _unique_, and a pricetag that's higher than the competition.
The result is an odd amalgum of features that reveal a window into just-one-person's vision of what a car should be. This results in a list of headline features that nobody was asking for, an incoherent, polarizing, and difficult-to-manufacture design, and a product that has no clear target audience.
All with the capacity to bankrupt a company, and all because somehow all the decision-making power was given to a single, thoughtless, out-of-touch idiot, who was allowed to run amok with their own ideas.
[This is why we shouldn't throw rocks at a (window) to see what sticks](https://www.youtube.com/watch?v=EHGczDHTDpo).
---
## Conclusion: listen to your users, but don't let them design your product
Feedback is a gift - always. But setting yourself up to receive feedback that is actually useful is a skill. Taking a lazy or naive approach to feedback can be a costly mistake, especially if you're not able to separate what people are _saying_ from what they're telling you.
Of course, the other side of the spectrum is a myopic approach - not collecting data or feedback at all, and going with your gut to product development that doesn't take into account the needs of your users.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Learning is an infinite game]]>
https://mikebifulco.com/newsletter/learning-is-an-infinite-game
https://mikebifulco.com/newsletter/learning-is-an-infinite-game
Tue, 28 Nov 2023 00:00:00 GMT
This is not to say that I'm a particularly gifted engineer, or a brilliant 3D-print...ist. Instead, I think the important nugget here is something that I've learned over the years: **learning is a skill**, and as a founder, you need to be good at it.
Here are some tips that I've picked up over the years that have helped me learn new skills quickly and efficiently:
## 1. Learn from the best resources you have access to
You don't need to reinvent the wheel. There are people out there who have already done what you're trying to do, and they've probably written about it.
When I was learning about 3D printing, I found a number of great resources that helped me get up to speed quickly. From previous passing interests in 3D printing, I knew of a few youtube channels that ended up being super helpful. Thanks to my schooling, I also have a cadre of _actual_ mechanical engineers who I can rely on for advice (shout out to Sean, James, Andy, & Mike - y'all are the true MVPs here). I consulted my dad, who spent 40+ years doing CAD and mechanical engineering. I read tech reviews, and I read the documentation for [the 3D printer I ended up buying](https://us.store.bambulab.com/products/x1-carbon-combo).
My point is this: you don't need to go it alone. Find the best resources you have access to, and learn from them.
## 2. Learn by doing, and act quickly
I'm a big believer in learning by doing. I've found that I learn best when I'm working on a project that I care about, and I'm learning the skills I need to complete that project.
While researching for my project, there were many opportunities along the way to take what I was learning and _use_ it to make progress on my project. I could have spent more time researching, but time spent researching is time not spent building.
## 3. Learn from your mistakes
You're going to make a lot of mistonks -- and every one you learn from makes your understanding of the world around you that much more accurate.
I iterated on the design for our painting mask 5 times before I got it right. In 3D Printing, that means I'd spend some time modeling the mask, and then wait a few hours for it to print out. I'd then test it, and see what worked and what didn't. I'd then go back to the drawing board, and make changes to the design.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[3 Ways to use Annual Pricing to your advantage]]>
https://mikebifulco.com/newsletter/use-annual-pricing-build-loyalty
https://mikebifulco.com/newsletter/use-annual-pricing-build-loyalty
Tue, 14 Nov 2023 00:00:00 GMT
## 3. Give advance notice of upcoming charges
Once a customers has switched to annual pricing, it can be easy for them to forget that they're paying for your product. For this reason, it can be a good idea to send them an email a month or two before their annual billing cycle is set to renew. This will help ease the sting of the charge, and it will give them a chance to cancel if they're no longer using your product.
This is also a great time to remind customers of the value they're getting from your product. If you've got the analytics in place, consider including some stats about how they've used your product over the past year.
You might also want to include a link to your public release notes, or a short list of new features that you've added over the past year. This is a great way to show your customers that their money is helping to build a better product.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The Decoy Effect: More options for an easier choice]]>
https://mikebifulco.com/newsletter/decoy-effect-and-your-brain
https://mikebifulco.com/newsletter/decoy-effect-and-your-brain
Tue, 07 Nov 2023 00:00:00 GMT
You're given 3 options: the entry level MBP for $1599, a mid-tier build for $1799, and a high-end build for $1999.
Which one would you choose?
## Three options, but only two choices
If you're shopping on a tight budget, the entry level model might be a no brainer. But if you've got some room to breathe, you might be tempted to go for the mid-tier configuration. It's only $200 more, and you get twice as much storage.
But then... what about the high-end model? For a mere $200 more, you get a more CPU _and_ GPU cores, more than twice as much memory (8GB->18GB), and faster USB ports. Storage does go back down to 512GB, buuuut you can upgrade that, too, if you really want to.
It's a _slippery_ slope. I'm willing to bet Apple sells far more of the top-tier configuration than the mid-tier one.
### This is the Decoy Effect.
The Decoy Effect is a cognitive bias that causes people to have a strong preference between two options, when presented with a third option that is inferior to one of the original options.
Wikipedia explains it like this:
> **The decoy effect** is the phenomenon whereby consumers will tend to have a specific change in preference between two options when also presented with a third option that is asymmetrically dominated. An option is asymmetrically dominated when it is inferior in all respects to one option; but, in comparison to the other option, it is inferior in some respects and superior in others.
In practice, this means that when presented with two options, buyers have a hard time choosing between them. But if presented with a carefully crafted third option, the decision becomes much easier.
For real: giving your customers **more choice** makes it **easier** for them to make a decision.
## The Economist's pricing experiment
Perhaps the most famous example of this is from The Economist. In 2009, they ran an experiment where they offered two subscription options:
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[There's no right way to do it]]>
https://mikebifulco.com/newsletter/no-right-way-to-do-it
https://mikebifulco.com/newsletter/no-right-way-to-do-it
Tue, 31 Oct 2023 00:00:00 GMT
## There's no right way to do it
This had me thinking about the way we build products. I've talked to many founders and indiehackers who spend the early days of their product journey researching the "right" way to do things. They spend more time talking about _the thing_ than building it. They talk about the problem to no end, and don't make any progress on the solution.
Friends, here's the thing: **just ship something**. Ship it. Ship it. Ship it.
Deploy your code, put it in front of real people, and open your mind and your heart to feedback and criticism. You'll learn more in a week of shipping than you will in a month of research.
There's no right way to do it. There _are_ many ways to do it, and if you ship more often, you'll find a path that works for your project. You'll be able to change more rapidly, and you'll be able to adapt to the needs of your customers.
You'll become a better product builder by shipping products, not by reading about how other people build products.
---
## Send me your project
Here's your call to action for the week: I want to know what you're working on, and I'd love to share your work here in Tiny Improvements. Send me what you're working on, and I'll share it with the community. I'll also give you a shoutout on Threads and LinkedIn.
Hit reply on this email, and send me a link to your project. I can't wait to see what you're working on!
---
## Recommendations from my playlist
- 🎙️ Colin & CJ over at [Build & Learn](https://buildandlearn.dev/) have been podcasting about career growth and building things as software engineers. CJ is a teammate of mine at Craftwork, and Colin works in DevRel at Discord - they're two devs who really know their stuff.
- 📖 I just finished listening to [Oversubscribed](https://www.amazon.com/Oversubscribed-How-People-Lined-Business/dp/B085P1N7LR/ref=sr_1_1?keywords=oversubscribed&qid=1698715330&sr=8-1&_encoding=UTF8&=irreverentm04-20&=ur2&=37e3d32d3a23dee0fda9150b61b2e135&=1789&=9325) on Audible. The book's tagline is "How to Get People Lined Up to Do Business with You" - and it gets right to the point. It's a great read for anyone who is building a product or a business, and it's full of proper advice from real-world experience.
## What I'm working on
- 🎙️ In my latest interview for Software Engineering Daily, I talk to [Tsavo Knott, the CEO of Pieces for Developers](https://softwareengineeringdaily.com/2023/10/25/building-pieces-app-and-the-future-of-developer-productivity-with-tsavo-knott/) about their product, an automated second brain for devs and engineering teams using some insanely cool multi-modal LLMs. If you've ever had that feeling that you read about something _somewhere_ but now you can't find it, Pieces is looking out for you.
- 🧶 I have been posting quite a bit on [Threads (@irreverentmike)](https://www.threads.net/@irreverentmike) lately. These days, the tech community on Threads is feeling a whole lot like the best days of twitter (RIP), and it is really refreshing. If you're active on Threads, hit me with a follow - I'd love to follow you back!
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Chase your interests to build something useful]]>
https://mikebifulco.com/newsletter/build-something-useful-with-ai
https://mikebifulco.com/newsletter/build-something-useful-with-ai
Tue, 17 Oct 2023 00:00:00 GMT
_note: Cover photo for this newsletter by [C D-X](https://unsplash.com/@cdx2?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash) on [Unsplash](https://unsplash.com/photos/PDX_a_82obo?utm_content=creditCopyText&utm_medium=referral&utm_source=unsplash)_
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Your resume sucks. Here's how to fix it.]]>
https://mikebifulco.com/newsletter/your-resume-sucks
https://mikebifulco.com/newsletter/your-resume-sucks
Wed, 04 Oct 2023 00:00:00 GMT
**WHO AM I**
> An impassioned, imperfect, endlessly curious person, fascinated by design and technology, trying to leave the world in better shape than I found it, and amplify the accomplishments of those around me. Admittedly, I cringe just a little bit reading it now - but hopefully you get the idea. It's personal, it's unique, and it's a great way to start a conversation. **Don't use a cover letter template.** I don't know if ChatGPT is to blame for this or what, but I've read several cover letter back-to-back that were nearly _identical_ except for a few specific details. If you're going to write a cover letter, make it personal. Tell me why you're excited about the role and why you think you'd be a good fit. If you're not going to make it personal, don't write one at all. **Lead with something interesting.** This is intentionally vague -- but if your cover letter starts with some variation of "with over 5 years of experience, I..." your cover letter already sounds like 90% of the other cover letters I've read. I know you're more interesting than that! Let your personality and interests shine through. If it all goes well, your cover letter is the start of a conversation - recruiters and hiring managers can read your resume for years of experience (if they really want to). Here's the first few sentences to my most recent cover letter, to give you a sense of what I mean: > My name is Mike Bifulco, and I'm a software designer, engineer, and serial entrepreneur based in Charlotte, NC, USA. I'm submitting my C.V. for consideration for DevRel leadership roles at ████, and I couldn't be more excited to do so. I've spent my career helping others make their dreams come true by building great products on the web. Helping developers tackle new problems and grow their skill sets is an incredible privilege, and being able to do so while working for ████, and growing an incredible team of developer advocates and engineers would be a thrill. **Include your most meaningful personal projects.** If you're applying for a job as a software engineer, I want to see what you've built. If you're applying for a job as a designer, I want to see what you've designed. If you've done some of your best work outside of your job, I would love to see it! **When possible, link to your available work online.** This includes websites, apps in the app store, blog posts, videos, etc. If you've done something cool, I want to see it. ### Found a role you're in love with? Go the extra mile. If you've come across a job opportunity on a team that you're _really_ smitten by, go the extra mile to make your application stand out. Here's a few ideas: **Use your network** to find someone you know with a contact at the company you're applying to, even if it's on a different team. If your connection is good, ask transparently for an introduction, and ask them to put in a good word for you. If you're not sure if your connection is good, ask them to be honest with you. If they're not comfortable making an introduction, don't push it. This is one reason why it's good to be proactively kind to people you work with - you never know when you might need a favor, and if you've only ever _asked_ for favors, you're not going to get very far. Give without the expectation of getting anything in return, and you'll be surprised how often people are willing to help you out when you need it. **Reach out to the hiring manager directly.** If you're applying for a role at a startup, there's a good chance that the hiring manager is the CEO or founder. If you're applying for a role at a larger company, there's a good chance that the hiring manager is a senior leader. Either way, they're probably pretty easy to find online. **Try out the product.** If you're applying for a role at a company that has a product, try it out. If you like it, tell them why. If there are opportunities for improvement, offer constructive criticism. If you're applying to a developer tools company, try out the product and build something with it. Share what you've built with the team, or open a Pull Request to fix a bug or add a feature. This is a great way to show that you're passionate about the product and the company, that you can communicate and work well, and that you're a self-starter. ## Improve the odds to get an interview Everything I've mentioned so far is about making your application stand out, and giving the hiring manager a reason to want to talk to you and schedule that first interview. Yes, it can be a lot of work, and _yes,_ there's definitely challenges with privilege and bias in the hiring process. If you're serious about landing the best possible gig for your next role, you'll see the best results if you put in the work. --- What do you think? Did I get anything really wrong here? Is there something you've done or seen that helps people land an interview? If you have any questions, comments, or feedback, I wanna hear it. Please reach out to me on [BlueSky](https://bsky.app/profile/mikebifulco.com) or [shoot me an email](mailto:hello@mikebifulco.com). ]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Do this with Your Product Waitlist: A Guide for Indiehackers and Startup Founders]]>
https://mikebifulco.com/newsletter/strategies-for-your-product-waitlist
https://mikebifulco.com/newsletter/strategies-for-your-product-waitlist
Mon, 18 Sep 2023 00:00:00 GMT
## If You've Already Started Building the Thing
### Embrace your Early Adopters
Do you already have a working prototype? Amazing! Put it in people's hands. Seriously - get real people using your product ASAP. This can be a scary hurdle to get over, but if you're open to it, you will get tremendous feedback from your earliest users.
Your primary aim should be to create early adopters who not only love your product but also how you're building it. The story of your product can be just as important as the product itself for these early adopters. They'll be your biggest advocates, and will help you spread the word.
With this approach, you're setting the expectation that your product is actively being built (you _are_ building it, right?). This means that you'll need to be responsive to feedback, and you'll need to be transparent about your roadmap. You'll also need to be comfortable with the fact that your product will be changing rapidly, and that you'll be making mistakes along the way. This is a good thing! You'll be able to iterate quickly, and you'll be able to build a product that your customers love.
### Choose an Early Cohort
From your waitlist, select an early cohort of users who you think will be most beneficial for your product. This could be based on their background, their willingness to provide feedback, or their ability to spread the word. You can also use this opportunity to test your pricing strategy. For example, you might offer a lifetime discount to the first 100 users who sign up.
If your waitlist is small, you may choose to let everyone in at once. If you have a large waitlist, you may choose to let people in gradually. This will help you manage the feedback loop from onboarding, and to create a sense of excitement for people who are still waiting to get in.
As you rapidly update your product and release new features, give access to more people from your waitlist. This will help you manage the feedback loop from onboarding, and to create a sense of excitement for people who are still waiting to get in. Open up registrations completely once people are able to onboard without any intervention from you or your team.
### Share What You're Building
Share your progress early and often, through whatever public channels make the most sense for you. This could be a YouTube video, a blog post, or a social media thread.
Use product updates as a way to show your current users that you're listening to their feedback, and that you're actively working to improve the product. This will help you build a community of early adopters who are invested in your success. This will also serve as product marketing for people who haven't yet signed up. Be loud and proud about what you're building, and share updates wherever your voice will be heard.
## The Ultimate Goal: Gain Traction
1. **Stoke the Fire.** In the early days, losing momentum is your biggest enemy. Gaining traction should inspire you to build more and at a faster pace.
2. **Create Inertia**. An engaged audience should feel they have access to something special. Encourage them to talk about your product and be responsive to their feedback. The buzz around your product will help you gain traction.
3. **Get Paid** Don't wait too long to monetize. Even asking for a nominal one-time fee from early adopters can validate your business model and make it easier to scale. Every person using your product knows that you need to make money to keep building it. Every single one of them. Don't be afraid to ask for financial commitments.
### Benefits with this approach
- **Feedback Loop:** Get invaluable feedback from real users, which will force you to keep building
- **Sales Skill:** Sharpen your skills in selling a product by building a muscle for marketing and developer relations. If you can't convince early adopters to use product, you won't be able to sell it to anyone else.
- **Networking:** Even if your product doesn't take off, you'll have grown the network of people who are invested in your success. This can be invaluable for your next project.
### Risks with this approach
- **Time Commitment:** Building software takes time. You'll need to be comfortable with the fact that your product will be changing rapidly, and that you'll be making mistakes along the way.
- **Building too slowly:** If you're not releasing updates, you'll lose momentum with your audience. Even if your product has known bugs, it's better to release early and often than to wait until it's perfect. Your early adopters will be forgiving, and will be excited to see your product improve over time.
## Your waitlist is just the beginning
Having a waitlist is a promising start, but it's what you do next that counts. Whether you're still ideating or have a ready product, these strategies can help you capitalize on your early traction and build a sustainable business. Remember, the ultimate goal is to gain traction, so keep building, engaging with your audience, and don't shy away from asking for financial commitments.
Your waitlist could be the first step in a long and successful journey.
---
## Tools for Building a product with Your Waitlist
- [Ghost](https://ghost.org/) - A fully open source, adaptable platform for building and running a modern online publication. Ghost gives you a blog and a newsletter all at once, and offers a great integration with Stripe for collecting subscription payments.
- [Stigg](https://stigg.io) - A tool for experimenting with pricing strategies. Stigg helps you find the right price for your product by decoupling pricing logic from your product code. This allows you to experiment with different pricing strategies without having to redeploy your product.
- [Reddit](https://reddit.com) is truly handy for doing research on niche communities, embedding yourself with your target market, and asking for feedback. Many product builders use it to find their first customers - there's more than just an infinite stream of memes for you on Reddit.
---
## Resources and reading for this stage
- [30x500 Academy](https://30x500.com/academy/) is a cohort-based class from Amy Hoy and Alex Hillman for building products using an approach similar to what I outlined above. Many of their students have gone on to build successful product businesses, and they have a wealth of resources for indiehackers and startup founders.
- 📖 I've recommended [The Embedded Entrepreneur](https://www.amazon.com/Embedded-Entrepreneur-Build-Audience-Driven-Business/dp/3982195764/ref=tmm_pap_swatch_0?_encoding=UTF8&qid=1695125716&sr=8-1&_encoding=UTF8&=irreverentm04-20&=ur2&=87d35637d191e4c0225f9e8c9b8b2ea2&=1789&=9325) before - it's a fantastic book from Arvid Kahl about building a business around specific and deep interests. I can't recommend it enough.
---
## From me this week
- 🎙️ My interview for [Software Engineering Daily with Charlie Gerard](https://softwareengineeringdaily.com/2023/09/19/catching-up-with-charlie-gerard/) went live this morning! Charlie and I worked together at Stripe. She's an incredible creative technologist, and I had a blast talking to her about her latest projects. If you're in the midst of a career pivot, and looking for inspiration, this one is for you!
- 📰 [The Bun is out of the Oven](https://apisyouwonthate.com/newsletter/the-bun-is-out-of-the-oven/) is our latest newsletter at APIs You Won't Hate. It's all about the new JavaScript runtime that's been all over tech news recently.
_Note: Cover image photo by **Samuel Regan-Asante** (who was formerly) on Unsplash (their account seems to have been deleted)_
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Breaking the cycle: Data-driven product descisions]]>
https://mikebifulco.com/newsletter/data-driven-decisions-product-analytics
https://mikebifulco.com/newsletter/data-driven-decisions-product-analytics
Mon, 04 Sep 2023 00:00:00 GMT
At each point in the timeline, we see two things: the number of people who continue to the next step, and the number of people who drop off.
This helps us understand where people are dropping off -- in other words, where we're losing potential customers. At each of these steps, there's an opportunity to improve conversion rates by iterating on our design.
### One Step at a Time: Hypothesis-Driven Iterations
This gives us data to make informed decisions about the product without getting too wrapped up in what we _feel_ should change. For example, if we see a lot of people dropping off at the step where they select paint colors, we might try a few things:
- Reduce the number of colors to choose from
- Add a "recommended" color
- Remove the color selection step entirely
(Any guesses what we landed on? If you're in Charlotte, NC, you can [try it out](https://craftwork.com/estimate/interior) and see for yourself!
We can then the impact of each change by seeing how the drop-off rate at that step is affected. If we see a significant improvement in drop-off rate, we know we're on the right track.
If not, we can try something else.
This is a simple example, but it illustrates the power of data-driven decision making. Ideally, this is paired with hands-on user research, and learnings from both proactive and reactive customer support. But even with a small team, you can make a big impact by using data to inform your product decisions.
---
## Tools for product analytics
- As mentioned above, we use [PostHog](https://posthog.com/) to track critical user behaviors, and to build funnels for measuring drop-off rates.
- [Highlight](https://www.highlight.io/) pitches itself as a full-stack monitoring platform. It's handy for keeping an eye on errors and performance issues within your app, and is completely self-hostable.
- [Fathom Analytics](https://usefathom.com/ref/DPSSYB) (that's a referral link for $10 off your first invoice) - I've written about [fathom](https://mikebifulco.com/posts/why-fathom-analytics) [several times now](https://mikebifulco.com/posts/seo-tools-for-new-web-projects), and I stand by my recommendation. It's great!
---
## More from my slice of the internet this week
- 🎙️ [Making React 70% faster with Aiden Bai of Million.js](https://softwareengineeringdaily.com/2023/09/05/making-react-70-faster/) - I had a chat with Aiden recently for an episode of the Software Engineering Daily podcast. Aiden is a recent high school grad who's built a React alternative that's 70% faster than React. ...I know, right?!
- 🧸 [Smartbear Acquires Stoplight](https://apisyouwonthate.com/newsletter/smartbear-acquires-stoplight/) - the most recent newsletter from APIs You Won't Hate talks about a recent acquisition in the API devtools world.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Reverse DevRel: The core engineering skill you've been missing]]>
https://mikebifulco.com/newsletter/reverse-devrel-as-core-engineering-skill
https://mikebifulco.com/newsletter/reverse-devrel-as-core-engineering-skill
Tue, 29 Aug 2023 00:00:00 GMT
If you've worked with engineers who are disconnected from your end users, you know how valuable these questions can be. They build empathy and trust between the team and the end users. They help us build better products.
### You got chocolate in my peanut butter! Bringing video into the mix
The use of screencast video is super helpful here, too - it's much easier to digest than a long email or a Slack message. It also creates two important types of empathy:
1. By demonstrating the features we build, we're forced to use them, and feel any UX pain points that might exist as a result of the implementation. This creates a better end product.
2. For those watching demo videos, it's much easier to see the person behind the feature when you can see their face and hear their voice.
### Best of all, you'll level up your teammates
The effectivity of this approach is contagious. As we build out new features, the rest of our team has started to follow the same patterns outlined above. In my experience, this is the type of experience that would be absolutely unheard of for brand new engineers. Connecting _what's being built_ with _who it's being built for_ is invaluable, and not something that can be gleaned from leetcode. It's a skill that's learned through experience.
To quote the world-famous developer advocate Missy Elliot: _take your DevRel, flip it, and reverse it_
---
## Great resources for reverse DevRel
As far as I can tell, nobody has written about reverse devrel, because it's a term I just made up... you can imagine how that complicates things. That aside, here are some great resources to dip your toes into the wild world of engineers who talk to people:
### 📚 The Business Value of Developer Relations
[This book by Mary Thengvall](https://www.amazon.com/Business-Value-Developer-Relations-Communities/dp/1484237471?&_encoding=UTF8&tag=irreverentm04-20&linkCode=ur2&linkId=9442e27bbfa907d124676e93faac5d25&camp=1789&creative=9325) is a great place to start if you're interested in learning more about DevRel.
### 📖 Fanocracy: Turning Fans into Customers and Customers into Fans
[Another great read, by Reiko and David Meerman Scott](https://www.amazon.com/Fanocracy-audiobook/dp/B082349829/ref=sr_1_1?&_encoding=UTF8&tag=irreverentm04-20&linkCode=ur2&linkId=bc920b438d4cf2f5db9b41fa7235b5c7&camp=1789&creative=9325) - while not directly about DevRel, it's a great book about building a community around your product. Building support and momentum for what you're creating is
### 🎥 Dead-simple screencast recordings with Loom
[Loom](https://loom.com) makes it super easy to make quick screencasts. At Craftwork, we use it frequently to record quick videos to share with teammates. It's a great way to get feedback on features as you're building them, and couldn't be easier to use. Their free plan lets you make 25 5-minute videos - which is more than enough to get started.
---
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Continuous self improvement and the morning ritual]]>
https://mikebifulco.com/newsletter/continuous-self-improvement
https://mikebifulco.com/newsletter/continuous-self-improvement
Tue, 15 Aug 2023 00:00:00 GMT
## Morning pages: Journaling for clarity
I mentioned above that I journal every morning. I've been doing this for a few years now, and it's been a game changer for me. My habit is loosely based on [morning pages](https://juliacameronlive.com/basic-tools/morning-pages/), a concept created by Julia Cameron, a writer and artist.
The task is simple: I spend 5 minutes writing down whatever is on my mind. I don't worry about grammar, spelling, or punctuation. I just write. I don't even worry about complete sentences. I just write down whatever is on my mind.
I've found this especially useful in times where I've got a lot on my plate - writing down the first few things that are on my mind can help me unravel the tangled mess of thoughts in my head. It's a great way to clear my mind and start the day with a clean slate.
On days where I'm not particularly stressed, these 5 minutes are often spent reflecting on my goals, and the the people and circumstances in my life that I'm grateful for.
It may seem silly, but it's incredibly powerful. Give it a shot - you might be surprised at what you learn about yourself.
---
## Podcasts for your morning walk
According to my podcast app of choice, I've listened to 161 _days_ worth of podcasts in the last 5 years. Most of what I listen to falls into two categories: comedy (entertainment), and non-fiction, educational shows. I subscribe to a reasonably large spread of shows, so that I can pick and choose what I listen to based on my mood.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[My startup got into Y Combinator]]>
https://mikebifulco.com/newsletter/craftwork-accepted-into-y-combinator
https://mikebifulco.com/newsletter/craftwork-accepted-into-y-combinator
Tue, 01 Aug 2023 00:00:00 GMT
---
## Building a hiring culture we want
Back when I ran the Google Asssitant DevRel team, I had joined a handful of subreddits related to programming and computer science, for a couple reasons:
1. I was hiring developer advocates, and was looking for college graduates who might be a good fit for the job
2. I wanted to give back a bit, and share some of my experience as a seasoned practitioner with budding CS homies.
Perhaps unsurprisingly, remaining in these subreddits for the past few years has been a mixed bag. There are many motivated and passionate students who are learning in public, sharing their struggles, success, and anxiety with the world. _On the other hand_, there's also a deeply toxic and insecure culture around students thinking about the job market. It's wrought with anxiety and elitism.
It's not uncommon to see redditors mentioning that they practice for interviews on a website Leetcode for _hours_ a day, or that they work 12+ hour days at their internships in the hopes of getting a full time job. They make one another feel bad for not being deferential enough to their prospective employers, and stomp on one-another's goals and dreams to feel better about their own paths.
Friends, this is not the kind of world we want to be building. Straight up. Why would anyone want to work in an environment where this is the reality?
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Two truths and a lie: what Meta got right with the Threads launch]]>
https://mikebifulco.com/newsletter/meta-threads-launch-two-truths-and-a-lie
https://mikebifulco.com/newsletter/meta-threads-launch-two-truths-and-a-lie
Tue, 11 Jul 2023 00:00:00 GMT
You may or may not have noticed, but Threads is not available to our friends in the EU - Meta has not yet figured out how to comply with GDPR, Europe's strict regulations around data privacy and information sharing for tech companies.
Meta has paid some _huge_ fines in the past for violating GDPR, and I'm sure they're not eager to do it again. I'm not a lawyer, but I'm willing to bet that supporting ActivityPub will be a huge headache for Meta's legal team. I'm not holding my breath.
### Threads launches on July 6
(Spoiler: **this one** is the lie.)
Meta spent a ton of time and effort telling the world that Threads was launching on July 6th, 2023. They managed press expectations extremely well here circulating images announcing the launch to press sources; they even added features to instagram to generate an image of a "ticket" inviting instagram users to the app at 10am on July 6th (see: cover image at the top of this page).
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Maximize user retention: the cognitive science approach...]]>
https://mikebifulco.com/newsletter/multitasking-and-product-design
https://mikebifulco.com/newsletter/multitasking-and-product-design
Tue, 04 Jul 2023 00:00:00 GMT
_note: cover photo for this newsletter is from [No Revisions](https://unsplash.com/it/@norevisions?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText) on [Unsplash](https://unsplash.com/s/photos/office?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText)_.
If you want to build a great product that people love, making your thing _work_ is not enough.
Truly great products provide value while building trust, loyalty, and enthusiasm. These is often accomplished through many small changes, by researching and observing the real behavior of people who use your apps.
I recently went down a rabbit hole reading about how we understand the **behaviors tied to multitasking** - and lemme tell ya, there is a _ton_ of wisdom that can be derived from what we know about the subject.
Studies in human multitasking indicate that our brains have a very limited capacity to handle more than one task at a time. In fact, we're not really multitasking at all - we're just switching between tasks very quickly. This is called _task switching_. Despite this, many people find it motivating to have a lot of things going on at once. This is called _continuous partial attention_.
There are many pros and cons to this, for example:
- There's a fine line between being motivated and being overwhelmed
- The more tasks we have going on at once, the more likely we are to forget something
- Finishing tasks makes us feel good
Hopefully you can imagine how this would be useful in UX design. It underscores the necessity for simplicity and focus, where each step of the onboarding process should be distinct, self-contained, and not overload the user's cognitive bandwidth.
Moreover, another fascinating aspect of our cognitive psychology is the **Zeigarnik effect**: people remember uncompleted or interrupted tasks _better_ than completed ones. By designing experiences that take advantage of this effect, we can motivate users to return to our products to complete important unfinished tasks.
For instance, we can strategically create breakpoints in the complex processes which leave users eager to come back and finish (i.e. _complete three workouts by Sunday to see your weekly stats breakdown_).
## The bottom line
So, how can we use this information to build better products? Here are some practical tips:
1. **Keep it simple**. Don't overload your users with too much information at once. Break down complex tasks into smaller, more manageable ones. For example: split complex onboarding flows into multiple steps, each with a clear goal, and make it dead easy to come back to when someone inevitably gets interrupted.
2. **Make it easy to come back**. Ever used an app that requires a login _every_ time you come back, even if you check the "remember me" box? I bet you can think of a couple examples off the top of your head. Do _you_ love those services? Of course not.
3. **Celebrate progress**. Reward users for completing tasks by giving them a sense of accomplishment. One of the most well-loved features we built at my last company, smpl, was a celebration screen that popped up when coworking members finished creating their profile for the first time. A little shower of confetti onscreen was a simple, fun way to make people feel good about what they'd accomplished.
By learning to acknowledge and cater to the cognitive intricacies of human multitasking, you can create a user-friendly environment that respects and makes the most out of our attentional capacities.
---
## More reading on multitasking and product design
### Continuous partial attention
The Wikipedia article on multitasking has a section on [continuous partial attention](https://en.wikipedia.org/wiki/Human_multitasking#Continuous_partial_attention), which is a great place to dig in further. It provides a concise overview of the concept, its history, and its implications for product design.
### The Zeigarnik effect
Ever have trouble sleeping because you didn't finish _that one important thing_ you needed to do today? Zeigarnik, baby! There's a great article from the Harvard Business Review on [The Zeigarnik effect](https://hbr.org/2020/10/why-your-brain-dwells-on-unfinished-tasks) that explains the phenomenon in detail. It also provides some practical tips on how it can be used as an advantage.
tl;dr: help your users feel like they're making progress, and break big tasks into smaller ones - they'll feel like they're making progress and be motivated for more.
### Cognitive load theory
As I shared a [couple weeks ago](https://mikebifulco.com/newsletter/cognitive-load-ux-and-why-you-should-care), Cognitive load is a theory that describes how our brains process information. It's a great way to understand how to design products that are easy to use and understand.
---
## For my API building friends in the back
Lots of new goodness from my beloved developer community APIs You Won't Hate this week!
- 🎙️ In the latest episode of the podcast, [Creating world-class API devX with Sagar Batchu from Speakeasy](https://apisyouwonthate.com/podcast/sagar-batchu-from-speakeasy/), I talk to founder Sagar Batchu about how he's building a platform to help API developers create better experiences for their users.
- 🚥 My pal and cofounder Phil Sturgeon wrote a great article called [How to Capture Quite a Lot of API Traffic](https://apisyouwonthate.com/blog/capture-api-traffic-using-optic/), in which he shares a great tactic for capturing API traffic for testing and documentation purposes.
- 📰 Can't get enough newsletters? APIs You Won't Hate's newsletter goes out twice a month, on the 1st and 15th. Check out the latest issue, [Death by Google](https://apisyouwonthate.com/newsletter/death-by-google/).
## Also, it is a holiday
As a side note, happy 4th of July to my American friends. If you're like me, you may be [finding it impossible](https://chicago.suntimes.com/2023/7/4/23779869/supreme-court-lgbtq-rights-segregation-website-designer-letters) to be proud of the [direction our country is headed](https://www.politico.com/news/magazine/2023/06/25/mag-tsai-ziegler-movementjudges-00102758).
Do me a favor, and **stay mad** about it.
[Make sure all your friends vote](https://vote.org), this year and every year.
**We need to do better.** ✊🏽
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Takeaways from VidCon's creator track]]>
https://mikebifulco.com/newsletter/lessons-from-the-creator-track-at-vidcon
https://mikebifulco.com/newsletter/lessons-from-the-creator-track-at-vidcon
Tue, 27 Jun 2023 00:00:00 GMT
) is a helpful tool for brainstorming and structuring a marketing strategy. The acronym stands for Attention, Interest, Desire, and Action: these are the steps which people tend to go through when deciding to make a purchase.
### The indexifembedded keyword
Here's a quick and hyper-specific SEO tip for my all my fellow web-building dudes: the [indexifembedded](https://developers.google.com/search/docs/crawling-indexing/robots-meta-tag#indexifembedded) keyword can be used to tell Google to index a page if it's embedded in another page in an iframe. This is particularly useful if you want to mark a YouTube video as unlisted on your channel, but still have it show up in search results when embedded on your website.
---
This all has me thinking quite a bit about the role video plays in my life - I would love to find more time to share stories and learnings from my startup journey in video format. I'm not sure what that looks like yet, but I'm excited to explore it.
If you want to follow along, you can subscribe to my YouTube channel [@mikebifulco](https://www.youtube.com/@mikebifulco).
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Intellectual humility: how to be wrong productively]]>
https://mikebifulco.com/newsletter/intellectual-humility-and-how-to-be-wrong
https://mikebifulco.com/newsletter/intellectual-humility-and-how-to-be-wrong
Tue, 13 Jun 2023 00:00:00 GMT
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Cognitive load, UX, and why you should care]]>
https://mikebifulco.com/newsletter/cognitive-load-ux-and-why-you-should-care
https://mikebifulco.com/newsletter/cognitive-load-ux-and-why-you-should-care
Tue, 06 Jun 2023 00:00:00 GMT
Germane cognitive load is the processing, construction and automation of schemas.
In other words, germane cognitive load is the amount of effort that your users spend on building a mental model of the thing you're helping them do. Often times, this means relating your thing to something that's already familiar to them. Here, `schema` is a fancy word for "the shape of the problem you're trying to solve".
At [Craftwork](https://craftwork.com), this is something we've been spending a good deal of time on. We found pretty quickly that most people don't have any mental model for what it should cost to repaint a room. Ask two friends what it costs to paint the same room, and you're likely to get two wildly different answers. This is a problem we're trying to solve for by offering transparent pricing for painting services, and by [providing a simple interface](https://craftwork.com/estimate) for people to get an instant quote for their project. You might be surprised to hear that this is a pretty novel concept in the home improvement space.
## What does it all mean?
The sum of theses three types of cognitive load is representative of how much of a pain in the ass it is to use _some thing_ to complete a task. You've experienced all three of these when you use any app or service. As you build your own product, reflect on your own interface designs, and look for areas to improve on cognitive load.
It's tempting to complete a feature, toss it over the fence to be released, and move on to the next thing -- but if you leave it at that, you're leaving a _ton_ of potential value on the table. Spend some time observing peoples' behavior when they use your product, and make it better. There's always room to improve.
---
## Load up your cognits with some brainfodder
Are you ready to dive in? These are some resources that might help you reduce cognitive load for your product:
- 🐗 We recently started using [Posthog](https://posthog.com/blog/using-posthog) at Craftwork. Self-described as "The Product OS", Posthog has a myriad of features that make it easier to see if your product is working, how well it is working, and what paths people are taking through as they navigate your features. It was a breeze to integrate, and has already helped us make some improvements to our product.
- 🫖 Don Norman's [The Design of Everyday Things](https://amzn.to/3Cgn5XG) is a classic tome on designing things that people will enjoy using. He does a great job of explaining design success and failure using basic objects like teapots and lemon squeezers, which makes it easy to understand how to apply his principles to your own designs.
- 🧑🎨 [r/designdesign](https://www.reddit.com/r/designdesign) is a subreddit full of _bad_ design - particularly, design that is over-the-top, just for the _sake_ of design. It's a great place to go if you're looking for examples of extraneous cognitive load.
---
## Noise to signal from me
- 🎙️ I had a chat with [Or Weis from Permit.io](https://apisyouwonthate.com/podcast/permissions-are-the-gift-that-keep-on-giving-with-or-weis-from-permit-io/) about the team his product is building. Often times, permissions, authentication, authorization, and the challenges facing developers building out products for real people.
---
Alright fam, that's all for now - if you've got examples of places where you've noticed cognitive load in your life, I'd love to hear about them -- especially if you've seen interesting ways to improve. Hit reply and let me know!
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Reddit as a tool for learning]]>
https://mikebifulco.com/newsletter/reddit-for-learning
https://mikebifulco.com/newsletter/reddit-for-learning
Tue, 23 May 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Your portfolio is a timeline of your growth]]>
https://mikebifulco.com/newsletter/portfolio-as-timeline
https://mikebifulco.com/newsletter/portfolio-as-timeline
Tue, 16 May 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[We hurled a people into space by building a pool: the case for simplification]]>
https://mikebifulco.com/newsletter/moonshot-design-for-everyone
https://mikebifulco.com/newsletter/moonshot-design-for-everyone
Tue, 09 May 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Tiny Improvements for big changes]]>
https://mikebifulco.com/newsletter/tiny-improvements-for-big-changes
https://mikebifulco.com/newsletter/tiny-improvements-for-big-changes
Tue, 25 Apr 2023 00:00:00 GMT
### Language Learning
For the past 1,000 days, I've been using [Duolingo](https://invite.duolingo.com/BDHTZTB5CWWKSRQUQARVC6SFNU?v=la) to sharpen my Spanish skills and learn Japanese and Mandarin. _A thousand days!_ Do you know what you were doing 1,000 days ago? I had to look it up -- that would be July of 2020.
Doubling down on language learning has proved invaluable as I work on my new business, [Craftwork](https://craftwork.com). Many of my new colleagues speak Spanish as their first language, and although I'm far from fluent, it will certainly help to build relationships and trust with my new teammates.
I've also been learning Japanese and Mandarin -- these are languages I'd love to be able to understand, and although it's been a massive challenge to get started, I'm making progress. I'm not sure if I'll ever be fluent, but I'm enjoying the process of learning something new.
My top tip for practicing a second language is to _get out of your comfort zone_ and try to communicate with native speakers whenever possible. I have never had a bad experience with this - people are generally very kind and appreciative, and it's a great way to learn.
### Writing
Launching [my website](https://mikebifulco.com) and [Tiny Improvements](https://mikebifulco.com/newsletter) has given me a platform to showcase my professional work and share my opinions with others. Writing consistently has not only helped me refine my thoughts and ideas but find likeminided people who appreciate my perspective.
## Taking small steps has made a big difference
These three habits, though seemingly small, have played a significant role in shaping my career, and creating opportunities that I never would have found otherwise. Your own series of Tiny Improvements will surprise you as they accumulate over time, ultimately leading to profound and lasting changes.
---
## Resources for building habits
- [Atomic Habits](https://amzn.to/3n33Ehe) by James Clear is the de facto guide to building habits. James has made an incredible career out of building habits for himself.
- My journaling habit is loosely based on [Morning Pages](https://juliacameronlive.com/basic-tools/morning-pages/), writing technique created by artist Julia Cameron. I love the idea of writing without judgement or expectation, but I rarely have it in me to bash out 3 pages of notes... and I am _definitely_ not hand-writing mine. Do what works for you!
- If you use Roam Research for taking notes, feel free to grab my [Morning Pages Template](https://gist.github.com/mbifulco/1357dde391d866c6a14d492b06414581). It is hyper-minimal by design to avoid overcomplicating my writing process.
## New from me this week
- 🎨 Craftwork is on Instagram! Follow us [@craftworkpaint](https://www.instagram.com/craftworkpaint) to see our latest projects and get inspired for your next paint job.
- 🎙️ Over at APIs You Won't hate (the podcast), my latest interview went live. Check out [Analytics for your API, with Steve McDougall from Treblle](https://apisyouwonthate.com/podcast/analytics-for-your-api-with-steve-mcdougall-from-treblle/) if you're working on a team that is building APIs.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[You are far more influential than you think]]>
https://mikebifulco.com/newsletter/you-are-far-more-influential-than-you-think
https://mikebifulco.com/newsletter/you-are-far-more-influential-than-you-think
Tue, 18 Apr 2023 00:00:00 GMT
## A call to arms: support your friends
I'm not writing this to ask for money, or to ask you to buy anything from me - if you're reading this, I'm already feeling the love. I'm writing this to ask you to support your friends.
Think about your friends who are working hard to build something. Maybe they're building a product, or a service, or a community. Maybe they're working on a side project, or a personal project, or a passion project.
Whatever it is, take 30 seconds out of your day, and share their _thing_ with your network. Let them know that you're a fan. It's small, it's free to do, and I can't tell you how much it means to the people you're supporting.
Small gestures of support can have enormous butterfly effects, too - I've made a good number of serendipitous connections in the past as a result of someone sharing my work with their network, or from times when I've shared and supported someone else's work.
Go, support your friends! You'll be glad you did, and they'll love you for it.
---
## Some friends whose work I admire
- [**Phil Sturgeon**](https://phil.tech) is the tree-planting madman who I work with on [APIs You Won't Hate](https://apisyouwonthate.com/). He's an exceptionally knowledgeable API developer, and has spent the past few years building his charity, [Protect Earth](https://www.protect.earth/). His organization has cleared land and planted tens of thousands of trees all over the UK - an astonishing accomplishment, and he's just getting started. Go follow Phil, he's a wonderful person.
- [**Rizèl Scarlett**](https://twitter.com/blackgirlbytes) is a developer advocate at GitHub. She's been all over the tech conference circuit for the past few years, where I've been lucky to bump into her from time to time. Rizèl is an amazing people connector - I've met and followed so many wonderful people as a result of her work.
- [**Colby Fayock**](https://twitter.com/colbyfayock) works as Director of DevX Engineering at Cloudinary, and is a really talented designer and developer. He's published countless articles, videos, and tech tutorials on his site, [SpaceJelly.dev](https://spacejelly.dev). Colby is genuinely one of the nicest people I've met, and does a great job of elevating the people around him. I'm always impressed by the work he's doing.
- [**Lazar Nikolov**](https://twitter.com/NikolovLazar) is a developer advocate at Sentry, and has started publishing a great newsletter called [Lazar's Tech Musings](https://nikolovlazar.substack.com/) that I've been enjoying. I stumbled across Lazar's work recently, and I'm really glad I did - our work has a ton in common!
## On building a following
📚 [Fanocracy: Turning Fans into Customers and Customers into Fans](https://amzn.to/3GSxOdO) is a book that is always high on my list of recommendations. I come back to my notes on it regularly, and I think it's a great read for anyone, whether you're actively building a following or not.
I've written a bit about nurturing your network before, and I think it's a topic that is worth occasional revisiting. If you're looking for more reading on the topic, you might enjoy these:
- [Imperfection is part of the brand](https://mikebifulco.com/newsletter/today-is-your-day-to-start), and people will love you for it.
- [Today is your day to start](https://mikebifulco.com/newsletter/today-is-your-day-to-start) building and marketing your product, even if you don't have the faintest idea what that is.
## Some of my recent work
- [Building in public growth report: 400 readers](https://mikebifulco.com/posts/building-in-public-growth-report-400-readers) - As I mentioned above, I recently passed the 400 reader milestone. I'm really grateful for the support and I wanted to share some of the things I've learned along the way.
- [Add custom fonts to Next.js sites with Tailwind using next/font](https://mikebifulco.com/posts/custom-fonts-with-next-font-and-tailwind) is a quick tutorial inspired by a post on Reddit. I've been trying to be helpful on /r/nextjs and /r/reactjs lately -- this post is adapted from a response to a question that I thought was worth sharing more widely.
- 🎙️ An interview I did recently for APIs You Won't Hate (the podcast): [Learnin' about webhooks, with Tom Haconen from Svix](https://apisyouwonthate.com/podcast/learning-about-webhooks-with-tom-haconen-from-svix/). If you're building with webhooks, this is a great episode to check out.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The first 90 days as a technical cofounder - building a startup in 2023]]>
https://mikebifulco.com/newsletter/building-a-startup-in-2023-90-day-report
https://mikebifulco.com/newsletter/building-a-startup-in-2023-90-day-report
Thu, 06 Apr 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Wabi-Sabi - embracing imperfection for tech teams]]>
https://mikebifulco.com/newsletter/tech-product-growth-wabi-sabi
https://mikebifulco.com/newsletter/tech-product-growth-wabi-sabi
Tue, 28 Mar 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[An idiot's guide to using ChatGPT to make yourself smarter]]>
https://mikebifulco.com/newsletter/make-yourself-smarter-with-chatgpt
https://mikebifulco.com/newsletter/make-yourself-smarter-with-chatgpt
Tue, 21 Mar 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Why Liquid Death's branding is murderously effective]]>
https://mikebifulco.com/newsletter/naming-your-product-kiki-bouba
https://mikebifulco.com/newsletter/naming-your-product-kiki-bouba
Tue, 07 Mar 2023 00:00:00 GMT
**tl;dr: pointy thing scary, round thing soft.**
Cultural expectations shape our perceptions of what certain things should be branded. For instance, we expect a luxury car brand to have a sophisticated and elegant name, a fast-food chain to have a short and catchy name, and a children's toy brand to have a fun and playful name. These expectations are not absolute, but they provide a useful framework for designing and naming brands that resonate with their target audiences.
## It's not a hard and fast rule
Sometimes, defying these expectations can be a smart strategy for creating a unique and memorable product or brand. Enter Liquid Death, a company that sells one of the most mundane products imaginable, canned water. Where 99% of companies in the world take the same beige market strategy for _canned water_, Liquid Death's approach is anything but dull. The company's name, logo, and packaging are edgy, irreverent (hi), and unexpected, with an unhinged aesthetic that appeals to a young, rebellious audience.
Their slogan is damn memorable, too: **Murder your thirst**.
This brand strategy allows Liquid Death to stand out from other water By challenging the conventions of what bottled water should look and sound like, Liquid Death has become an outright success, with a loyal following and a rapidly growing business.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The productivity tool I use every day to multiply my output]]>
https://mikebifulco.com/newsletter/unlock-productivity-with-networked-note-taking
https://mikebifulco.com/newsletter/unlock-productivity-with-networked-note-taking
Tue, 28 Feb 2023 00:00:00 GMT
As software developers and entrepreneurs, we often find ourselves juggling multiple projects, deadlines, and priorities simultaneously. With so much going on, it's essential to have effective tools and strategies in place to help us stay organized and focused.
This is going to sound completely wild, but the most profound change I made in the way I learn, work, and operate day to day was simple:
## I started taking notes.
Specifically, I adopted a technique called networked note taking (also called _zettelkasten,_ _second-brain,_ and more generally _Personal Knowledge Management_, or _PKM_). Essentially, networked note taking involves creating a web of interconnected notes that link together various ideas, thoughts, and concepts. By using note-taking tools like Obsidian, Roam Research, Notion, or Logseq, you can create a digital archive of your notes that allows you to quickly access and retrieve information when you need it.
So why is networked note taking so useful? For one thing, writing things down helps free up mental energy. Writing things down offloads some of the burden of _just remembering things_ from your brain. Instead of trying to remember everything in your head, you can capture your ideas in real-time and let the tools do the heavy lifting of organization and retrieval.
This gives you more mental space to focus on the things that really matter. You can spend less time worrying about remembering things and more time prioritizing and focusing on what's important now.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The math behind why cafes should have round tables]]>
https://mikebifulco.com/newsletter/design-decisions-cafe-tables
https://mikebifulco.com/newsletter/design-decisions-cafe-tables
Tue, 21 Feb 2023 00:00:00 GMT
This is the shape of a _sublime_ morning - the kind of day that can be easy to... _ah, what the fuck -- is the table unbalanced?_
I **hate** wobbly table.
_tap, tap_ ... _tap, tap_ ... _tap, tap_ ...
Every time you shift your weight, or move your coffee cup, or lean back in your chair, the table wobbles. It's annoying, it's distracting, and some days, it can be enough to ruin an otherwise great morning. It's a flaw that we've all experienced.
## The fix for a wobbly table
As it works out, a wobbly table is not something you _have_ to live with. If you look online, there are countless articles telling you ["how to fix a wobbly table"](https://www.wikihow.com/Brace-a-Wobbly-Table). You can tighten or brace a loose leg, or add shims to make the legs perfectly level, or take the cro-magnon approach and stack some coasters or napkins under one leg.
**However**, there is a solution simpler than all of these. A solution so simple that it feels like it shouldn't work. All you have to do is...
**...rotate the table a bit.**
That's it. Within a quarter turn of rotation, there will be at least one position where the table is perfectly stable.
Seriously - try it yourself the next time you sit down at a wobbly table.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The finicky nature of color in product design]]>
https://mikebifulco.com/newsletter/color-context-and-product-design
https://mikebifulco.com/newsletter/color-context-and-product-design
Tue, 14 Feb 2023 00:00:00 GMT
Designers often face the challenge of unauthorized access to their designs,
leading to intellectual property theft and loss of business. OneGlimpse offers
a comprehensive solution to protect your designs by blocking unauthorized
screenshots and screen recordings. With OneGlimpse, you can have peace of mind
knowing your designs are safe and secure.
Color perception is a very personal experience. A 1995 study published in the scientific journal _Perceptual and motor skills_ called [Blue versus periwinkle: color identification and gender](https://pubmed.ncbi.nlm.nih.gov/7624204/) showed that _"the women identified significantly more elaborate colors than did the men"\*_
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Perception and unexpected tricks of the mind]]>
https://mikebifulco.com/newsletter/unexpected-observations-in-human-cognition
https://mikebifulco.com/newsletter/unexpected-observations-in-human-cognition
Tue, 31 Jan 2023 00:00:00 GMT
This is an effect that I've seen used in visual design as well, although I never had a name for it. As it works out, Entasis is frequently used in the design of typefaces. [Font designers often use entasis](https://graphicdesign.stackexchange.com/questions/111439/is-there-a-font-that-has-the-same-height-for-every-character) to create a subtle optical illusion that makes the font appear more balanced and symmetrical. Somtimes, a character will _appear_ more visually balanced if it is just slightly taller than the others around it, even though that feels like it shouldn't be the case. It's a subtle effect, but it can make a big difference in the way text appears.
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Learn from me: a Dunning-Kruger expert]]>
https://mikebifulco.com/newsletter/learn-from-a-dunning-kruger-expert
https://mikebifulco.com/newsletter/learn-from-a-dunning-kruger-expert
Tue, 24 Jan 2023 00:00:00 GMT
I've got a few ideas, and I've been doing some research, but I'm not an expert in furniture design. I'm not an expert in woodworking. I'm not an expert in small batch manufacturing.
I'm just a dude who is excited about an idea, and I have a lot of questions.
I spent a few hours scouring the web for people smarter than me (spoiler alert: there are _many_ of them). From there I found [/r/hobbycnc](https://www.reddit.com/r/hobbycnc/) and [/r/woodworking](https://www.reddit.com/r/woodworking/), where I can learn from experienced makers and woodworkers. Instructables has an article series on [flat pack furniture](https://www.instructables.com/Flat-Pack-Table-Design/), and there's endless youtube [reviews of home CNC machines on YouTube](https://www.youtube.com/watch?v=_IxPxcvc9Wg).
Now that I've found places where experts are sharing their domain knowledge, I can start to listen, ask questions, take notes, and follow heated conversations. Before long, I may be ready to execute on my idea, or I may decide to pivot and make changes that better suit my expertise and situation.
This is something you can apply to any problem space. The best product builders are those who see the world through their own expertise _and_ the expertise of others, to build something that is greater than the sum of its parts.
It's also important to be prepared for the Dunning-Kruger effect to show up again. As you continue to learn, stay tapped into the community. Be mindful of your perceived level of expertise, and the potential mistakes that come with that knowledge.
Finally, when you do find yourself in the position to share your expertise, do so with humility. It is so powerful to be wrong on the internet, and it's even more powerful to [be wrong and admit it](https://mikebifulco.com/posts/semantic-html-heading-subtitle#-update-i-was-wrong-).
## There are things I think I know
- 💼 **The cat's out of the bag...** at least a little bit. Last week I started listing my new job on my various profiles on line. I'm working on a new company called [Craftwork](https://craftwork.com). I'm working with an outrageously talented team on making it easier for homeowners to get their houses painted... and that's just the tip of the iceberg. If you know any full-stack engineers who love TypeScript and react... I'm [hiring](https://docs.google.com/document/d/1orbRYcbBd2UfSHM5mvgCm_gYSwjOQAeaTh7YqymWAkM/edit?usp=sharing)!
- 🫶 **I'm speaking at the [first ever Charlotte Open Source Meetup](https://www.meetup.com/open-source-charlotte/events/290694423/)** this Thursday (Jan 26) at 6pm. The topic is _Unlocking the Power of Open Source to Launch Your Startup and Career_ - not-at-all hyperbolic. Hope to see you there!
- 🎙️ **A new APIs You Won't Hate podcast** is live! [Funding Open Source, with Dudley Carr from Stack Aid](https://share.transistor.fm/s/9bb11fc4) was a great conversation with a new friend I met at All Things Open last fall in Raleigh. We talked about the importance of funding open source projects, and how Stack Aid is helping to do just that. Check it out!
## ...and the things other people know
- 📚 [**"Thinking, Fast and Slow"**](https://hardcover.app/books/thinking-fast-and-slow) by Daniel Kahneman is a must-read, continuing the pattern of sharing books I love. It explores two modes of thought (fast and intuitive vs slow and reasoned) which appear time and again in decision making and cognitive science.
- 🎥 **[@nolanperk](https://www.tiktok.com/t/ZTRp352dc/) is a skilled designer** and TikTok creator who shares beautifully-made, thoughtful design tips on his account. Ever wonder how to make font sizes feel _just_ right on your app? Look no further.
- 🎙️ [**The Happiness Lab, with Dr. Laurie Santos**](https://www.pushkin.fm/podcasts/the-happiness-lab-with-dr-laurie-santos) is a podcast that explores the science of happiness... that's right, the _science_ of **happiness**. It turns out that personal happiness is something we can study, measure, and quantify. It's an occasional listen for me, and I always learn something.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[These are the books that shaped my career]]>
https://mikebifulco.com/newsletter/books-that-shaped-my-career
https://mikebifulco.com/newsletter/books-that-shaped-my-career
Tue, 17 Jan 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Tools for building a new company]]>
https://mikebifulco.com/newsletter/tools-for-building-a-new-company
https://mikebifulco.com/newsletter/tools-for-building-a-new-company
Tue, 10 Jan 2023 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The case for continued learning, and getting side projects out the door]]>
https://mikebifulco.com/newsletter/side-project-and-a-fresh-start
https://mikebifulco.com/newsletter/side-project-and-a-fresh-start
Tue, 03 Jan 2023 00:00:00 GMT
I'm also really interested in hearing what you're thinking about, and what you're working on. If you're diving into a new project or learning this year, reply to this email with what you're working on. I'd love to hear about it, and to help share it with the world when you're ready.
Happy New Year - let's get building!
## The things holding prime real estate in my brain this week
- 🧮 [Knolling](https://www.youtube.com/watch?v=EJuUhegtlOc) is a the practice of organizing physical things in your workspace at 90 degree angles. It's both visually appealing, and a helpful way to make sure everything is in its right place. It was created by Andrew Kromelow, a janitor working at Frank Gehry's furniture company in the 1980s, where it was used to keep tools organized in their workshop. It's since found footing in the photography world - the [#knolling tag on insta](https://www.instagram.com/explore/tags/knolling/) is full of beautiful examples.
- 🐘 Have you moved to Mastodon yet? I have, and you should too. Find me at [@irreverentmike@hachyderm.io](https://hachyderm.io/@irreverentmike). If you're worried about rebuilding your network from twitter, there are tools like [Fedifinder](https://fedifinder.glitch.me/) which can help you find your friends who have already moved. I've also found Mastodon to be super helpful for SEO -- I've seen a surprisingly high engagement rate in links I've shared, and a distinct uptick in traffic to my site since I started sharing my work there.
- 📚 I recently re-listened to Tony Fadell's book [Build: An Unorthodox Guide to Making Things Worth Making](https://hardcover.app/books/build), and even on a second listen I really enjoyed it. Fadell is the co-founder of Nest, and the inventor of the iPod. He's a fascinating guy, and his book is a great read for anyone who's interested in building things. It's been surprisingly prescient lately - I particularly enjoyed hearing his perspective on wny Southwest Airlines was so successful in their early days, and how they've struggled to adapt to the modern world.
## ABC - always be learning
This week I also thought I'd share some of the resources I've been using while I'm learning new things. I'm a big believer in the idea that you should always be learning, and that you should always be building -- and we damn well ought to be sharing the things that help us out. Here's a few of my favorites recently:
- 📼 [James Q. Quick's YouTube Channel](https://www.youtube.com/@JamesQQuick) has been hitting all the marks for me lately. He shares tutorials and examples on bleeding edge JavaScript frameworks and libraries, and does a great job of making it accessible to folks who might not be super experienced
- 👾 Another recommendation from YouTube, creator CodeBullet has been making in-depth, animated tech videos for quite a while. While they're not step-by-step tutorials, his videos are super engaging and very funny, and they do a great job of breaking down the basics of some seriously complex topics. Check out his recent 2-part series on [Teaching AI to walk in 3D space](https://www.youtube.com/watch?v=qvpXpCvkqbc)
- 🎙️ [Conduit](https://www.relay.fm/conduit) is a podcast from [Kathy Campbell](https://hachyderm.io/@mrssoup@mastodon.social) and [Jay Miller](https://hachyderm.io/@kjaymiller@mastodon.social), which explores "the connection between what we should be doing and what ultimately gets done" - I often feel like my ambitions outrun the time I have to get things done, and Conduit does a great job of exploring why that's okay... and why it's probably a good thing in some cases.
Alright fam, that's it for this week - I'm off to smash my hands into my keyboard and hope something good comes out. Don't forget to send me what you're working on, and in the mean time, be excellent to each other 🤜🏼🤛🏻
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Building your brand in the developer community]]>
https://mikebifulco.com/newsletter/be-intentional-about-building-your-brand
https://mikebifulco.com/newsletter/be-intentional-about-building-your-brand
Tue, 13 Dec 2022 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Customer experience, quality, and the hype cycle]]>
https://mikebifulco.com/newsletter/quality-and-the-hype-cycle
https://mikebifulco.com/newsletter/quality-and-the-hype-cycle
Tue, 06 Dec 2022 00:00:00 GMT
Perhaps unsurprisingly, my experience was different. The website was still beautiful, but the ordering process was clunky. The product was still well-designed and sustainably made, and the packaging was nice. The shoes arrived, and while they looked great, they didn't fit quite right. The return label was missing from the box, and I found myself driving out of my way to one of a few shops in the city that could process my return.
Woof.
I was disappointed, and I felt like I had been misled by my friend's recommendation. But what was happening here? Why did my purchase differ so much from my friend's? At the risk of oversimplifying, I think it comes down to growth.
The company in question saw rapid growth, and as a result, they had to make some trade offs to keep up with demand. They prioritized growth over quality, and their product and experience suffered for a while.
On the other side of the spectrum are companies who make the decision to grow more slowly, and focus on quality as job #1. These companies may not grow as fast, but they tend to have a much higher chance of success in the long run. I find myself more loyal to these companies and experiences, having never been let down by them.
Growth-first companies _can_ bounce back from a dip in quality, and many have done so. I've been impressed lately with [Airbnb's efforts to improve their product](https://twitter.com/bchesky/status/1589541705921212416), and I'm hopeful that they'll get back to providing the unique alue they once did. But I think that the companies who prioritize quality will have a much easier time sustaining growth, and handling issues as they arise.
_(Newsletterman's footnote: I'm intentionally **not** naming Shoe Company™️. The point of this musing is not to shame or call anyone out. I'm just using this as an example to illustrate a point. I've noticed this same pattern in all sorts of companies and services, and I think it's worth thinking about.)_
## Recommendations from all over the hype cycle
Now that I've pointed out that you shouldn't trust recommendations from your friends (lol), here's some things I've found lately that you might enjoy.
- 🐘 [Mastodon (specifically, hachyderm.io)](https://hachyderm.io/@irreverentmike) - You may have seen that I've left Twitter, at least while it's under Elon Musk's control. I've moved to Mastodon, and have an account on Hachyderm.io. If you're on Mastodon, feel free to follow me there! If you're not sure what Mastodon is, check out [joinmastodon.org](https://joinmastodon.org/). If you're still not sure, reply to this email, and I'll find some time put together a quick explainer video.
- 📖 [The Innovation Stack](https://hardcover.app/books/the-innovation-stack) is a book by Jim McKelvey, who co-founded IRL payments company Square (now and its parent company Block). It's hard to imagine how a glass blower became the founder of such an influential company -- his story is fascinating, and the book is a great read.
- 📚 [Hardcover.app](https://hardcover.app/@irreverentmike) (Public beta) is a service for rating, recommending, and discovering books to read. If you've used GoodReads and find its UX lacking for 2022, or you're looking for a service not owned by Amazon, you'll love Hardcover.
## My recent work
- 🏳️ [**Twitter, and the Perils of Obedience**](https://mikebifulco.com/posts/twitter-and-the-perils-of-obedience) I wrote a long-form opinion article on my departure from Twitter, relating it to a famous experiment in behavioral psychology from the 1960s.
- 📹 Quick tech tips on TikTok and YouTube - I've been experimenting with releasing 60s tech tips on TikTok and YouTube. If you're active on either platform, I'd love to hear your feedback! TikTok: [@irreverentmike](https://tiktok.com/@irreverentmike) / YouTube [@mikebifulco](https://youtube.com/@mikebifulco)
- 🎙️ Did you know you can write C++, C#, and Java code that can be used directly on the web? My recent [interview with Matt Butcher from Fermyon](https://softwareengineeringdaily.com/2022/11/25/cloud-native-webassembly/) on the Software Engineering Daily podcast dives into Web Assembly, and was one of my absolute favorite interviews yet.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Put a fork in it - how to know when your work is ready to publish]]>
https://mikebifulco.com/newsletter/how-to-know-when-to-publish-your-work
https://mikebifulco.com/newsletter/how-to-know-when-to-publish-your-work
Tue, 22 Nov 2022 00:00:00 GMT
How do you know when your work is ready to publish?
I feel like this issue is at the heart of _everything_ I create, but it's particularly spicy when it comes to video. I can publish articles all day long, and go back to update them on a whim if the need ever arises.
Video is much more final - at least on YouTube, TikTok, and Instagram, because those platforms don't let you edit your videos after they're published.
After some thought, here's my answer to the question:
**Imperfection is part of the brand.**
Showing some scuffs here and there, and the vulnerability it takes to let those things out into the world helps people connect with you. It also gives you wiggle room to improve over time.
If you're constantly aiming for perfection, you'll never publish anything, and because of that, you'll never get any better.
It's a balance, of course - you don't want to be so imperfect that your work is incoherent or unprofessional. But a few scuffs along the way show that you're a real person, trying your best.
In fact, I think that I grow a much deeper personal attachment with creators who let me see into their process a bit. Things like editing, deciding on a voice, and what to deliver all make the brand feel more real, and more relatable to me.
There's also a subconscious element to it - I feel like I'm getting a peek into the creator's brain.
The secret sauce seems to be leaning into the bumps and bruises, and pointing out from time to time "hey, this isn't perfect, but I see that too".
When things feel _super_ polished all the time, it creates a veneer of false authenticity that just feels like... marketing? I think most people don't want to be sold to; they want to feel like they're a part of something genuine.
So, in short… here's what I think: don't be afraid to put something out there that's not perfect. It'll be more relatable, you'll meet more interesting people, and you'll have more fun with it.
To me, that's something people can get behind.
This dispatch of Tiny Improvements is sponsored by
[Twirp.ai](https://twirp.ai?utm_source=nl_tinyimprov), a tool for A/B testing
your twitter profile. Test different bios, profile pictures, and header images
to see which ones get you more followers.
## What I'm reading
I've had a few connections ask me which newsletters I read regularly, so I thought I'd some of my favorites:
- 🗞️ If you're publishing a newsletter, you have to check out the [Growth Currency newsletter](https://www.growthcurrency.net/?utm_source=MikeBifulcoNewsletter). It's a weekly newsletter by Dylan Redekop providing highly-actionable tips, tactics, and resources to help you grow, improve, and monetize your own newsletter.
- 🏙️ For all my Urbanist / NUMTOT pals - my friend Barry Greene has been sharing his thoughts on Urbanization and public transit in his newsletter [Density Dad](https://cutloose.substack.com/?utm_source=nl_tinyimprovements). His perspective on responsible growth and planning for cities is refreshing, and I always learn something new.
- 🖍️ If you're a parent of an elementary-aged youngster, you should check out [Primary Focus](https://newsletter.primaryfocus.tv/), a newsletter by Miss Natalie, a 10-year veteran of the classroom who also happens to be my best friend and partner. She's been sharing her thoughts on education, parenting, and the future of learning in her newsletter for a while now, and it's a great read.
## Oh and BTW - I've been publishing videos, too
Despite publishing Tiny Improvements weekly, I've taken the last few weeks to recharge my cells a bit. It's a funny time for me - I'd love to be outside enjoying the weather even though it's cold out, but a recurring injury means I really need to take it easy. It's probably a good thing, honestly.
I've been making ~60s tutorials for creators and developers, and publishing them both on [YouTube](https://youtube.com/@mikebifulco) and [TikTok](https://tiktok.com/@irreverentmike).
If you're active on either platform, I'd love it if you checked them out and subscribed.
That's it for now - thanks so much for reading, and if you're in the US, enjoy the holiday.
Until next time,
Mike
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Get started: The trick to publishing online]]>
https://mikebifulco.com/newsletter/today-is-your-day-to-start
https://mikebifulco.com/newsletter/today-is-your-day-to-start
Tue, 15 Nov 2022 00:00:00 GMT
This dispatch of Tiny Improvements is sponsored by
[Taplio](https://taplio.com/?utm_source=nl_tinyimprov), the first AI-powered
personal branding tool for LinkedIn. Increase your impact with your network,
by creating high performing content 10x faster.
## Getting started as a writer
I hear from lots of people who _want_ to start writing online. Many people get in their own way, and never publish anything because of impostor syndrome, or because they don't have an audience yet. The best thing about being a creator is that you can start with _nothing_, and you don't need anyone's permission to get started. The sooner you create something and share it with the world, the sooner you'll get better at it.
Don't get me wrong - I've seen countless people set up a blog for themselves, publish a ["hello world" article](https://mikebifulco.com/posts/it-was-time), and only come back every 6 months to post something like _sorry it's been so long since I've written something here. I'm back for real this time_.
The biggest challenge for online creators is avoiding that pattern.
If you've been on the fence about starting a blog, or a YouTube channel, or a podcast, **this is your call to action:** publish something (_anything!_) and send it to me on twitter [@irreverentmike](https://twitter.com/irreverentmike) or mastodon [@irreverentmike@mastodon.online](https://mastodon.online/@irreverentmike). I'd love to see what you're building, and be a signal boost for your work.
## 2 guiding principles for publishing online
1. [**There is no bar**](https://chriscoyier.net/2022/06/27/there-is-no-bar/). In my absolute favorite blog post of all time, [Chris Coyier](https://twitter.com/chriscoyier) writes about how there is no minimum bar for publishing online. You can start with anything -- and you shouldn't be the one holding yourself back. The only thing you need to do is start.
2. **Writing triples your impact** - during his recent keynote at All Things Open, [Scott Hanselman](https://twitter.com/shanselman) shared a poignant observation. When you teach someone by sharing your knowledge, you've doubled the reach of your brain. If you write it down and even **just one other person** sees that, you've tripled your impact - and it only goes up from there.
When you have something to share -- write it down, and make it available **anywhere** with a public URL. It doesn't need to be any more complicated than that!
## Tools for publishing online
- 🗒️ [Obsidian](https://obsidian.md/) is note-taking tool, and is perfect for creating a second brain and getting things off your mind. If you're used to writing with [Markdown](https://www.markdownguide.org/basic-syntax/), it will feel very familiar. It's free for personal use.
- 🌁 Ever try to upload an image from your phone to your website, only to find it's 30mb and takes forever to download? Enter [Squoosh](https://squoosh.app/), a tool for compressing images. Pull up the URL, drag-and-drop your image, and hit the download button to grab a compressed version. It's that easy.
- 🖼️ Speaking of images, [Unsplash](https://unsplash.com) is a treasure trove of beautiful, high quality images licensed for use online (with attribution). You'll never want to use clip art or a stock photo again.
- 🧇 Waffle -- city -- ice cream cone -- if you've ever had trouble finding an icon for something, you're going to love [The Noun Project](https://thenounproject.com/). Their mission is to provide a library of icons for every _noun_ in the world. Can you imagine such a person, place, or thing?
Alright friends - now go smash some words on a page, and hit publish. I'll be waiting to see what you do!
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[What it's like to get laid off and go viral on the same day]]>
https://mikebifulco.com/newsletter/leaving-stripe-going-viral
https://mikebifulco.com/newsletter/leaving-stripe-going-viral
Thu, 10 Nov 2022 00:00:00 GMT
That was it. I got laid off.
If you're new here, it's likely because you saw my tweet later that same day:
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[What I learned from using AI in my work]]>
https://mikebifulco.com/newsletter/what-i-learned-from-using-ai
https://mikebifulco.com/newsletter/what-i-learned-from-using-ai
Tue, 25 Oct 2022 00:00:00 GMT
## AI tools you should try
These tools all use machine learning and AI to help you get things done. While most of them are not free, they all have some version of a trial or free tier that you can use to get a feel for them. If you haven't tried any of these, I recommend giving at least one a look - AI has come a **very** long way since the days of Goldeneye 64.
### No Code AI tools
📝 [Jasper AI](https://jasper.ai/) is a fantastic aid for people who write - it will help you write better emails, blog posts, and more. It's a great tool for people who want to write better, but get stuck on the details, or suffer from writer's block.
🎙 [Snipd](https://www.snipd.com/) is an incredible tool for people who listen to lots of podcasts. They use AI to automatically create an analyze transcripts of the shows you listen to. You can then use those transcripts to **snip** moments from a podcast, just like you'd bookmark a link to a webpage, or earmark a page in a book. I use it to take notes on podcasts that I listen to, and it's a great way to keep track of the things I want to remember.
🛋 [Interior AI](https://interiorai.com/) is a tool that lets you upload a photo of a room and it will suggest furniture that would fit in the room. It's pretty cool, and has been growing by leaps and bounds. Full disclosure: I happened across the product on twitter recently, and [have been helping its creator](https://twitter.com/irreverentmike/status/1579959127932968960) hone in on their pricing strategy using Stripe's tools. Apart from that, I'm not affiliated with, or paid by them in any way.
### For developers
✍🏼 [Open AI](https://openai.com/) are the creators of GPT-3, a language model that can generate text. It's pretty amazing, and you can try it out for yourself [here](https://beta.openai.com/).
🖼 [Stable Diffusion](https://github.com/CompVis/stable-diffusion) is an AI tool that you can run on your own computer to generate images from text. This one is for my more code savvy friends - it's written in python and not too challenging to use, but it does require some comfort with using a terminal.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Tips for managing burnout and stress]]>
https://mikebifulco.com/newsletter/burnout-and-stress
https://mikebifulco.com/newsletter/burnout-and-stress
Tue, 18 Oct 2022 00:00:00 GMT
The [World Health Organization](https://www.who.int/news/item/28-05-2019-burn-out-an-occupational-phenomenon-international-classification-of-diseases) classifies burnout as a syndrome resulting from chronic workplace stress that has not been successfully managed. It is characterized by three dimensions:
1. Feelings of energy depletion or exhaustion
2. Increased mental distance from one's job, or feelings of negativism or cynicism related to one's job
3. Reduced professional efficacy
...sound familiar?
Thankfully, the WHO is also working with scientists to develop guidelines on identifying and managing burnout. Science is looking out for us again, y'all. While I'm definitely not an expert on the subject, I've found that the following tools have helped me stay ahead of burnout in my job and my relationships.
## The tools I use to stay ahead of burnout
- 🛌 **Sleep better**. I'm intentionally putting this at the very top of the list so that you take it seriously. People always underestimate the effect that sleep has on their life. Don't take my word for it, listen to the experts - [**Why We Sleep: Unlocking the Power of Sleep and Dreams**](https://hardcover.app/books/why-we-sleep) by Matthew Walker is an exploration of our scientific understanding of sleep, and why it is critical to living a good life. Still not convinced? Check out this review from [Bill Gates](https://www.gatesnotes.com/Books/Why-We-Sleep).
- 🖼 **Therapy** is something that we all can benefit from. Especially men -- we are often not equipped with the right tools to deal with and express our emotions. Speaking to a professional can help you understand yourself better, and can help you learn to manage your emotions in a healthy way. Whoever you are, wherever you are, give it a shot. Talk to a _real_ professional (I'm looking at you, evangelicals) and invest in yourself. There are many options available, and [**BetterHelp**](https://www.betterhelp.com/) is a great option if you're looking to try therapy online.
- 📝 **Take notes** - No single habit I've adopted has had an impact on me like note taking. Writing down my thoughts helps me offload tasks from my brain, stay organized, and work more efficiently. I'm a big fan Zettelkasten-style note taking, and I use [**Roam Research**](https://roamresearch.com/) for my notes. It is a paid service - if you're on a budget or just dabbling for now, check out [Obsidian](https://obsidian.md/) and [LogSeq](https://logseq.com/).
- 🧘 **Meditate** - I use [**Headspace**](https://www.headspace.com/referral/z6jb3?slug=cebee0&audio=false) for a few minutes of peaceful meditation when I'm feeling overwhelmed.
- 🧠 This [5-minute video on Burnout from Dr. Sahar Yousef](https://www.youtube.com/watch?v=cFjK5WLpSHE) was actually produced by Headspace, and I found it to be pretty enlightening. Your brain's fear and anxiety center is literally activated by the accumulation of small bits of stress building up for days and weeks on end. The researcher from this video, [Dr. Sahar Yousef](https://www.saharyousef.com/), is working to develop frameworks to help us deal with burnout before it happens.
- 🪐 [The third place](https://mikebifulco.com/posts/remote-work-and-the-third-place) is a term that has been making the rounds on the internet lately. The long and short of it is this: we live a more balanced life when we somewhere to go that is not our home or our workplace. It's a place where we can go to relax, to socialize, to be fulfilled. Check out the linked article for my feelings on the importance of [The Third Place for remote workers](https://mikebifulco.com/posts/remote-work-and-the-third-place).
I'll leave you with this: if there's someone in your life who may be going through a tough time right now, drop them a line and tell them you see them, and you care about them. That little gesture can go a very long way.
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[5 Design rules everyone should know]]>
https://mikebifulco.com/newsletter/design-rules-everyone-should-know
https://mikebifulco.com/newsletter/design-rules-everyone-should-know
Tue, 11 Oct 2022 00:00:00 GMT
In western countries, we tend to read from top to bottom, left to right. It is something we've all been subconsciously trained to do since an early age.
When you're designing something, you can use this pattern to help guide your reader's eye. Assume they will go from looking at the biggest, boldest thing on the page, to the next biggest, and so on. You should therefore make sure that the most important things you want someone to see are the biggest and boldest, and step down from there.
This is called hierarchy. It's a way to help your guide your reader's eyes predictably.
### 2. **Similarity**
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Remember these apps?]]>
https://mikebifulco.com/newsletter/lifecycle-of-a-moonshot-company
https://mikebifulco.com/newsletter/lifecycle-of-a-moonshot-company
Tue, 04 Oct 2022 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The way we talk about our things]]>
https://mikebifulco.com/newsletter/use-of-language-and-intent
https://mikebifulco.com/newsletter/use-of-language-and-intent
Tue, 20 Sep 2022 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[What I've learned from working in public]]>
https://mikebifulco.com/newsletter/building-in-public
https://mikebifulco.com/newsletter/building-in-public
Mon, 12 Sep 2022 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Balance for remote workers]]>
https://mikebifulco.com/newsletter/balance-for-remote-workers
https://mikebifulco.com/newsletter/balance-for-remote-workers
Tue, 06 Sep 2022 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Has it been four years already?]]>
https://mikebifulco.com/newsletter/four-years-already
https://mikebifulco.com/newsletter/four-years-already
Tue, 19 Jan 2021 00:00:00 GMT
Talk soon!
Mike
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[Sip your coffee quietly, act kindly]]>
https://mikebifulco.com/newsletter/sip-coffee-quickly-act-quietly
https://mikebifulco.com/newsletter/sip-coffee-quickly-act-quietly
Tue, 12 Jan 2021 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[The Enthusiast's Hidden Superpower]]>
https://mikebifulco.com/newsletter/enthusiasts-hidden-superpower
https://mikebifulco.com/newsletter/enthusiasts-hidden-superpower
Sun, 03 Jan 2021 00:00:00 GMT
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[On seasonal change, open source, and carbon offsets]]>
https://mikebifulco.com/newsletter/on-seasonal-change-open-source-carbon-offsets
https://mikebifulco.com/newsletter/on-seasonal-change-open-source-carbon-offsets
Tue, 08 Dec 2020 00:00:00 GMT
) is when people are able to draw two distinct conclusions from the same set of data, depending on how it's presented. Forex: I have 200 unread emails in my inbox. Should I panic? Nah, they're marked "To Do" -- I'll get to it later.
## Working in Public (OSS!)
If you're interested in Open Source Software, you should check out the book Working in Public: The Making and Maintenance of Open Source Software, by Nadia Eghbal (link). I just finished reading through it with a book club I was invited to, and I enjoyed the read. I plan on [publishing my book notes to my website soon](https://mikebifulco.com/posts/working-in-public), as well.
## Kicking around in the old domepiece
These are a few of the things I've found on the web lately. I thought you might benefit from them as well:
- 🇪🇸 I've been brushing up on my Spanish. It's a relaxing couple-minute ritual in my day. I enjoy it so much that I've been sprinkling in some Japanese here and there, too! I've been using Duolingo's free plan - my referral link is [here](https://invite.duolingo.com/BDHTZTB5CWWKSRQUQARVC6SFNU) if you want to give it a shot.
- 👨🏫 How much do online courses make? Have you ever taken a course online, or thought about making one yourself as a side hustle? [This is a tool](https://revenue.sixfigureinstructor.com/) that lets you peruse the aggregate statistics of various course topics across Udemy. Did you know that on average, courses on Next.js make $40/day? Pretty wild!
- 🌳 Planting trees can make a difference. In the past, I've mentioned my love for [Ecologi](https://ecologi.com/irreverentmike?r=5d386c6667bad5001010ffae) (that's a referral link), which was previously called offset.earth. I'm excited to share that my good friend Phil Sturgeon has embarked on a carbon offsetting project of his own - he's on a mission to plant a forest of trees on farmland near his home in the UK this winter. Check out his work at [protect.earth](https://www.protect.earth/) , and donate if you're able!
Thanks for reading Tiny Improvements. If you've got any feedback, my inbox is always open: [hello@mikebifulco.com](mailto:hello@mikebifulco.com). If you've found this useful, I would love it if you shared it with a friend!
Be excellent to each other - talk soon.
- Mike
_Disclaimer: Tiny Improvements are my own thoughts an opinions, and not necessarily those of my employer._
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
-
<![CDATA[I swear I wrote that down somewhere 🤦♂️]]>
https://mikebifulco.com/newsletter/swear-i-wrote-that-down-somewhere
https://mikebifulco.com/newsletter/swear-i-wrote-that-down-somewhere
Mon, 11 May 2020 00:00:00 GMT
Thanks for reading Tiny Improvements. If you've got any feedback, my inbox is always open: [hello@mikebifulco.com](mailto:hello@mikebifulco.com)
Be excellent to each other -
Mike
]]>
hello@mikebifulco.com (Mike Bifulco @irreverentmike)
---
## Making a case for doing good things
If you need evidence benevolent behavior is good for business, look at who’s done it before:
- [Ben & Jerry’s](https://www.benjerry.com/values) has built their brand by showing up for people who can’t always speak up for themselves. They've made advocacy part of their product.
- [Notion](https://www.notion.com/product/notion-for-education) gives away tools to students and teachers as part of their mission to help people learn and grow.
- [Fastly](https://www.fastly.com/company)'s devtools platform is accompanied by a strong mission to make the internet a better place.
You don’t need an underground bunker. You just need to be one of the people who gives a damn when things feel uncertain.
This is when it matters most. ✌️
Give 'em hell out there,
- Mike
]]>Product for Engineers is a newsletter on building great products, the best practices of top startups, and lessons learned by PostHog. ## What it means for your product Most people talk about Dunbar's number in terms of 150, but the power lies in close-knit groups of 50. These 50 people are your advocates, your early adopters, your most vocal supporters. For product builders, focusing here first creates a foundation that grows beyond one-time use or sporadic engagement.
> An impassioned, imperfect, endlessly curious person, fascinated by design and technology, trying to leave the world in better shape than I found it, and amplify the accomplishments of those around me. Admittedly, I cringe just a little bit reading it now - but hopefully you get the idea. It's personal, it's unique, and it's a great way to start a conversation. **Don't use a cover letter template.** I don't know if ChatGPT is to blame for this or what, but I've read several cover letter back-to-back that were nearly _identical_ except for a few specific details. If you're going to write a cover letter, make it personal. Tell me why you're excited about the role and why you think you'd be a good fit. If you're not going to make it personal, don't write one at all. **Lead with something interesting.** This is intentionally vague -- but if your cover letter starts with some variation of "with over 5 years of experience, I..." your cover letter already sounds like 90% of the other cover letters I've read. I know you're more interesting than that! Let your personality and interests shine through. If it all goes well, your cover letter is the start of a conversation - recruiters and hiring managers can read your resume for years of experience (if they really want to). Here's the first few sentences to my most recent cover letter, to give you a sense of what I mean: > My name is Mike Bifulco, and I'm a software designer, engineer, and serial entrepreneur based in Charlotte, NC, USA. I'm submitting my C.V. for consideration for DevRel leadership roles at ████, and I couldn't be more excited to do so. I've spent my career helping others make their dreams come true by building great products on the web. Helping developers tackle new problems and grow their skill sets is an incredible privilege, and being able to do so while working for ████, and growing an incredible team of developer advocates and engineers would be a thrill. **Include your most meaningful personal projects.** If you're applying for a job as a software engineer, I want to see what you've built. If you're applying for a job as a designer, I want to see what you've designed. If you've done some of your best work outside of your job, I would love to see it! **When possible, link to your available work online.** This includes websites, apps in the app store, blog posts, videos, etc. If you've done something cool, I want to see it. ### Found a role you're in love with? Go the extra mile. If you've come across a job opportunity on a team that you're _really_ smitten by, go the extra mile to make your application stand out. Here's a few ideas: **Use your network** to find someone you know with a contact at the company you're applying to, even if it's on a different team. If your connection is good, ask transparently for an introduction, and ask them to put in a good word for you. If you're not sure if your connection is good, ask them to be honest with you. If they're not comfortable making an introduction, don't push it. This is one reason why it's good to be proactively kind to people you work with - you never know when you might need a favor, and if you've only ever _asked_ for favors, you're not going to get very far. Give without the expectation of getting anything in return, and you'll be surprised how often people are willing to help you out when you need it. **Reach out to the hiring manager directly.** If you're applying for a role at a startup, there's a good chance that the hiring manager is the CEO or founder. If you're applying for a role at a larger company, there's a good chance that the hiring manager is a senior leader. Either way, they're probably pretty easy to find online. **Try out the product.** If you're applying for a role at a company that has a product, try it out. If you like it, tell them why. If there are opportunities for improvement, offer constructive criticism. If you're applying to a developer tools company, try out the product and build something with it. Share what you've built with the team, or open a Pull Request to fix a bug or add a feature. This is a great way to show that you're passionate about the product and the company, that you can communicate and work well, and that you're a self-starter. ## Improve the odds to get an interview Everything I've mentioned so far is about making your application stand out, and giving the hiring manager a reason to want to talk to you and schedule that first interview. Yes, it can be a lot of work, and _yes,_ there's definitely challenges with privilege and bias in the hiring process. If you're serious about landing the best possible gig for your next role, you'll see the best results if you put in the work. --- What do you think? Did I get anything really wrong here? Is there something you've done or seen that helps people land an interview? If you have any questions, comments, or feedback, I wanna hear it. Please reach out to me on [BlueSky](https://bsky.app/profile/mikebifulco.com) or [shoot me an email](mailto:hello@mikebifulco.com). ]]>
]]>
]]>
### Shaking up the male-dominated sports industry
Only 5% of sports news is on female athletes, and even less on the business of women's sports! The GIST Sports Biz is changing that by delivering major deals, trends, and insights on women's sports, straight to your inbox.
### Hiring developers made easy:
- ✅ Search in 24,000+ remote developer profiles
- ✅ All developers have passed our extensive screening
- ✅ See their salary expectations upfront in their profiles
Do you want to try our Hiring Platform for free?
### Secure Your App Ideas and Make Them Yours: Prove Ownership and Increase Credibility with Our AI-Powered Idea Builder
Take the first step towards app success with our AI-enhanced idea builder. Own and protect your app ideas, and prove ownership with a shareable link. With a track record of progress, you can confidently discuss your ideas. Build with us today!
### Explore Thousands of Creative Classes
Get started with one month free.
As software developers and entrepreneurs, we often find ourselves juggling multiple projects, deadlines, and priorities simultaneously. With so much going on, it's essential to have effective tools and strategies in place to help us stay organized and focused.
This is going to sound completely wild, but the most profound change I made in the way I learn, work, and operate day to day was simple:
## I started taking notes.
Specifically, I adopted a technique called networked note taking (also called _zettelkasten,_ _second-brain,_ and more generally _Personal Knowledge Management_, or _PKM_). Essentially, networked note taking involves creating a web of interconnected notes that link together various ideas, thoughts, and concepts. By using note-taking tools like Obsidian, Roam Research, Notion, or Logseq, you can create a digital archive of your notes that allows you to quickly access and retrieve information when you need it.
So why is networked note taking so useful? For one thing, writing things down helps free up mental energy. Writing things down offloads some of the burden of _just remembering things_ from your brain. Instead of trying to remember everything in your head, you can capture your ideas in real-time and let the tools do the heavy lifting of organization and retrieval.
This gives you more mental space to focus on the things that really matter. You can spend less time worrying about remembering things and more time prioritizing and focusing on what's important now.
That was it. I got laid off.
If you're new here, it's likely because you saw my tweet later that same day:
The timeline above outlines a vast simplification - to give you some idea of what happened in my world last week, here's a few high-level events: - **Monday**: I enjoyed an emergency dentist appointment after a crown come off my tooth during a weekend trip to Philadelphia. - **Tuesday**: Went to [All Things Open](https://allthingsopen.org/) in Raleigh, NC, and gave a talk about [Markdoc](https://markdoc.dev) to 50 devs. - **Wednesday**: Drove home to Charlotte, to pack for the next day's trip to the [Caribbean Developer Conference](https://cdc.dev) in Punta Cana, Dominican Republic. - **Thursday**: Ya boy got fired. lol. In the afternoon, I boarded a jet to Punta Cana with my wife, and shortly after arriving I fired off the tweet above. - **Friday**: With the help of my incredible better half (Natalie 🫶), and steady stream of Piña Coladas, I responded to a trillion messages from people who had seen my tweet. My dudes - it was a wild-ass week. As I write this, it is almost exactly one week later. I've managed to untangle most of my brain by now, and have heard from a _massive_ number of people who reached out to me with love and support. I have probably sent hundreds of replies by now, and I'm extremely grateful for each and every one of you who reached out, RT'd, and subscribed to this newsletter. Seriously -- Tiny Improvements has _doubled_ in subscriber count since last week! ## On moving on & momentum You can't control everything in life, but you can control how you react to it. I am extremely grateful for the experience I had - my team at Stripe was truly unique, and indescribably talented. I'd tell my colleagues that working with them was like having lightning in a bottle. I still feel that way, but it's time to move on. I was pleasantly surprised to see my tweet getting so much attention. It's the most viral thing I've put on the web to date, and I'm trying to use that attention for good. Since getting laid off, many people have reached out to me who are hiring for super interesting jobs. I've been maintaining a list of these jobs, and will continue to keep it up for as long as I can manage. **If you're looking for a job**, or know someone who is, check out [@irreverentmike's job list](https://airtable.com/shrbIYV7uOCfQDeGR) **If you're hiring**, please DM me on twitter [@irreverentmike](https://twitter.com/irreverentmike) or [submit a job directly through this form](https://airtable.com/shraftW1575L6nGED). ## What's next for me I am endlessly thankful for the great network of people I have in my life. Friends, family, former colleagues, and complete strangers have reached out about job openings. I'm thrilled to say that my next job is lined up already. I'm excited to share more about that soon. ### Now back to your regularly scheduled newsletter... As you can imagine, this dispatch of Tiny Improvements is fairly atypical. Generally, this newsletter caters to people building great products - I'm a designer and front-end developer at heart, and a serial SaaS builder. Generally my newsletters include a couple paragraphs diving into a topic like [design for developers](https://mikebifulco.com/newsletter/design-rules-everyone-should-know), or [managing burnout](https://mikebifulco.com/newsletter/burnout-and-stress), a photo or screenshot from my week, and links to a few interesting & helpful tools for getting things done. If that sounds like something you'd enjoy, I'd love it if you stick around. If you know anyone else who might benefit from my writing, please forward this to them, or send them off to [mikebifulco.com/newsletter](https://mikebifulco.com/newsletter) to subscribe. Thank you! Here's hoping this next week is extremely un-interesting. ✌🏾 ]]>🚨 I was laid off from my job at Stripe this morning. I will always look back on my time at Stripe DevRel fondly. Time to unwind and decompress. If you are a newly-former Stripe, DM or email hello@mikebifulco.com. I'll do whatever I can to help you find your next job.
— Mike Bifulco (@irreverentmike){' '} November 3, 2022