tail -f ~/notes

This morning I was speaking with my co-founder about systems and processes. He indicated that if you go to work for a company, you are forced into a system or process. Otherwise, they really have no reason for keeping you on board. As business owners, we should be diligent about implementing and sticking to these within our own companies. Find something that works for you, build it, implement it, and stick to it.

Sometimes, in the favor of progress, you need to accept that you don’t understand something. Plenty of examples in software engineering. Write it down, come back it to later, but for now, accept that it works for you and not against you.

Migrated this site off Gatsby and onto Astro. The old build had drifted out of date and felt heavier than a personal site should be. Astro ships zero JavaScript by default, which is exactly right for something that’s mostly words.

Kept every article, set up 301s from the old date-prefixed URLs, and added this notes stream so the site can be a living document instead of a thing I touch once every two years.

Astro 5’s content layer lets you point a collection at a folder with the glob() loader and validate frontmatter with a Zod schema. Bad frontmatter fails the build instead of silently rendering wrong — which is how it should be.

const notes = defineCollection({
  loader: glob({ pattern: "**/*.md", base: "./src/content/notes" }),
  schema: z.object({ date: z.coerce.date() }),
});

Reminder to self: a site that’s live and a little rough beats a perfect one that never ships. This stream exists to lower the bar for posting — short notes, no ceremony.