Workflows

Building in Public Without the Friction

Logging weekly founder updates shouldn't take hours away from coding. How to streamline your updates using minimal, local-first tools.

A
Akhil K Thomas
Published March 2, 2026

The "Build in Public" movement has transformed how independent software is marketed. By sharing revenue numbers, technical hurdles, and behind-the-scenes thoughts, founders can build immense trust and loyalty before their product even launches.

However, many founders abandon the practice after three weeks. Why? Because the act of writing the update becomes a chore.

The Context Switching Penalty

As a developer, your brain is fully loaded with the architecture of your application. When you pause to write an update, you don't just have to think about English prose instead of code; you have to physically change your environment.

You have to log into a web portal, deal with rich-text formatting, upload images to a CMS, and preview the live page. This level of context-switching destroys your technical momentum. A task that should take 5 minutes takes 45 minutes.

The 5-Minute Update System

To consistently log updates without hating the process, you must strip the friction down to zero. The process should mimic opening a terminal window.

  • No Browsers: Never write your updates in a web browser. The temptation to check analytics or Twitter is too high.
  • No Formatting: Write in pure Markdown. Bullet points and bold text should be achieved through keystrokes, not mouse clicks.
  • No Complex Publishing: Don't compile code to publish an update. Use tools that generate static files instantly.

The Developer's Diary: Thooval

We built Thooval to be the ultimate developer's diary. Because it runs natively as a desktop app, opening it takes less than a second. You can have VS Code open on one monitor, and Thooval open on the other.

When you solve a tough bug, you `Cmd+Tab` to Thooval, type a 3-sentence markdown note, hit save (locally), and `Cmd+Tab` right back to your code. At the end of the week, you simply click the built-in Publish button, and your entire dev-log is built into an elegant static web page.

Building in public works, but only if you can actually sustain the habit. Stop fighting heavy CMS tools and start using a local markdown editor that respects your focus.