6 ms·

This is good advice for techies, who are usually good at the “do things” and but not the “tell people”. The same principle applies to a startup/side-project. A

This is good advice for techies, who are usually good at the “do things” and but not the “tell people”. The same principle applies to a startup/side-project. At supabase we call this “ship and shout”, which is about as simple as it sounds (Ant wrote about our full “process” here: https://supabase.com/blog/2021/11/26/supabase-how-we-launch https://supabase.com/blog/2021/11/26/supabase-how-we-launch ) The other one that took us some getting-used-to was being repetitive on platforms with a short “half-life”, like Twitter. It made me uncomfortable at the start since the general advice is that “reposting is annoying”. But any given tweet probably reaches only 1% of the audience i thought it would, so not many see the repost. Sometimes we will talk/tweet about something we shipped months ago and we still have developers commenting that they just learned about it from the tweet.

tommiegannert 5y ago
Do you vary (re)posting time of day, or is any repost pattern useful on Twitter?
newaccount74 5y ago
> techies, who are usually good at the “do things” ... But since they don't tell people, they often end up building useless shit. I've experienced this a few times when I spent weeks or even months working on a feature, then showing it to customers, and realising that they don't get it, or that it doesn't fix their problems, etc. I try not to get too attached to my ideas, so if something doesn't work, I throw it away and try a different approach. So I think doing things and telling people after the fact when you are done is not going to lead to success. You need to tell people early, so you can adjust what you're doing to make sure it's actually something interesting.
ozim 5y ago
I just want to add there are a lot of "business people" who are good with coming up with ideas but then those ideas are useless. So it is not only techies. One of company owners for example did not understood market our company is in and mandated that we built in Stripe integration. Well it was useless burning of money and he did not read "do things that don't scale", where our market worked you have high touch sales and send invoices and no one ever signed for payments, I removed the code last year and we are growing with customer base.

tommiegannert 5y ago

Do you vary (re)posting time of day, or is any repost pattern useful on Twitter?

newaccount74 5y ago

> techies, who are usually good at the “do things” ... But since they don't tell people, they often end up building useless shit. I've experienced this a few times when I spent weeks or even months working on a feature, then showing it to customers, and realising that they don't get it, or that it doesn't fix their problems, etc. I try not to get too attached to my ideas, so if something doesn't work, I throw it away and try a different approach. So I think doing things and telling people after the fact when you are done is not going to lead to success. You need to tell people early, so you can adjust what you're doing to make sure it's actually something interesting.

ozim 5y ago

I just want to add there are a lot of "business people" who are good with coming up with ideas but then those ideas are useless. So it is not only techies. One of company owners for example did not understood market our company is in and mandated that we built in Stripe integration. Well it was useless burning of money and he did not read "do things that don't scale", where our market worked you have high touch sales and send invoices and no one ever signed for payments, I removed the code last year and we are growing with customer base.