Hian | Building Tintio

Solo founder, 15+ years building software. Now doing it in the open: code, product metrics, and lessons from running social solo.
💬 EN / JP / KR

[Hian | Building Tintio @ohe_dev]

A feature list can't show you how much carrying you'll do between a tool's screens, so I'd suggest counting it yourself the next time you post to all your channels.

Count four things: how often you switch screens, how often you copy and paste, how often you type the same thing twice, and how often you go back to check something. If you copied and pasted even once, those two screens aren't connected and you were the link between them. If you kept going back, what you needed wasn't on the screen you were working in.

Add the four numbers and divide by your number of channels, and you'll see roughly what one more channel would add. When I was designing my own flow, the number I chose to bring to zero was copy and paste.

If you try it, what's the count for one post?

#productivity

[Hian | Building Tintio @ohe_dev]

If you're into tech, let's connect🤝

[Hian | Building Tintio @ohe_dev]

@Sarakhan49309 Keep your brand persona locked in. Tintio makes every draft sound like you from day one—turning multi-channel content creation effortless.

https://t.co/kvuXC35riY

[Hian | Building Tintio @ohe_dev]

For developers working alone, the question that costs the most time months later is often "why did I do it this way?"

Code shows what it does. The reasons behind a decision (the option you tried and dropped, the constraint that forced your hand) disappear unless you write them down. Without them, it's easy to undo a decision without knowing what it was protecting.

Teams often keep decision records for exactly this. When you work alone, a few lines per decision do the same job: what was chosen, what wasn't, and why.

How do you keep track of decisions when there's no team to remember them?

#softwareengineering

[Hian | Building Tintio @ohe_dev]

For developers working alone, the question that costs the most time months later is often "why did I do it this way?"

Code shows what it does. The reasons behind a decision (the option you tried and dropped, the constraint that forced your hand) disappear unless you write them down. Without them, it's easy to undo a decision without knowing what it was protecting.

Teams often keep decision records for exactly this. When you work alone, a few lines per decision do the same job: what was chosen, what wasn't, and why.

How do you keep track of decisions when there's no team to remember them?

#softwareengineering

[Hian | Building Tintio @ohe_dev]

Posting the same idea on X, LinkedIn and Threads sounds like one task. In practice it's three.

X wants the point in the first line. LinkedIn readers expect a little context before you get there. Threads works better when it sounds like you're talking to someone. Paste the same text everywhere and at least one channel will feel off, so you end up rewriting, and each rewrite takes almost as long as the first draft.

It helps to decide which channel the idea fits best, write that version first, and adapt the others from it.

Which channel do you usually write for first?

#contentcreation

[Hian | Building Tintio @ohe_dev]

When you build alone, there's more to do each day than there are hours: product, support, writing, design, the occasional invoice.

The order you do it in matters a lot. If writing comes last, it usually doesn't happen. If code comes first, it tends to eat the whole morning. Which order works varies a lot from one person to the next.

If you build alone, what do you do first when you sit down in the morning?

#indiehackers

[Hian | Building Tintio @ohe_dev]

A small editing habit that helps more than it should: once a post is done, delete the first sentence and reread the post.

First sentences are often warm-up. They set the scene, restate the topic, or ease into the point. Someone scrolling a feed doesn't need that, and the post usually starts at sentence two.

It doesn't work every time. When it does, the post gets shorter and the opening gets sharper at the same time.

What's your last step before you hit publish?

#writingtips

[Hian | Building Tintio @ohe_dev]

@RomanShalabanov Keep your brand persona locked in. Tintio makes every draft sound like you from day one—turning multi-channel content creation effortless.

https://t.co/kvuXC35riY

[Hian | Building Tintio @ohe_dev]

When I set up my own brand profile, I ended up writing two kinds of rules, and they behave differently.

The first kind is words. Words I never want in a post, like "game-changer," go on a list, and any draft that contains one gets caught right away, every time.

The second kind is rules that depend on context, like "say what changed before explaining why it matters." A word match can't judge that, so those rules go to the AI as instructions for how to write.

Keeping them apart made both easier to trust. The word list is exact, and the writing rules shape the draft from the start.

If you had to pick one word you never want to see in your posts, what would it be?

#contentcreation

[Hian | Building Tintio @ohe_dev]

@X_supporttop1 Let's connect! I follow back in seconds!

[Hian | Building Tintio @ohe_dev]

@spacedevin Keep your brand persona locked in. Tintio makes every draft sound like you from day one—turning multi-channel content creation effortless.

https://t.co/kvuXC35riY

[Hian | Building Tintio @ohe_dev]

@syednouman1618 Hey! Glad to connect! 🙌🏼

Tintio is going great! We recently opened our beta and are busy polishing the platform with user feedback. Appreciate you asking—how’s everything going with you?

[Hian | Building Tintio @ohe_dev]

@X_supporttop1 I follow back asap

[Hian | Building Tintio @ohe_dev]

As Sunday comes to an end, another week is about to begin. I’m spending some time tonight thoughtfully planning what kind of content to share on social media this week.

[Hian | Building Tintio @ohe_dev]

As Sunday comes to an end, another week is about to begin. I’m spending some time tonight thoughtfully planning what kind of content to share on social media this week.

[Hian | Building Tintio @ohe_dev]

@MalikAbdul94020 Let's Connect!

[Hian | Building Tintio @ohe_dev]

@Sarakhan49309 Active! Follow back!

[Hian | Building Tintio @ohe_dev]

@chipadodo3002 Yes!