How I grew @prov_pizza 3650% over the last month.

This is me trying to build in public like @thisiskp_ and being transparent like @jackbutcher.

A
visual thread. 👇🍕

1/ The secret towards getting these gains? Start from zero.

The stats after 4 weeks:

0 —> 77.4K Impressions
0 —> 6,130 Profile visits
0 —> 490 Likes
2 —> 73 Followers, sorry for the bait ;)

Here are some of my key learnings. 👇
2/ @jamierusso taught me to remix the content of others.

With only 9 followers I added some pizza sauce to Jamie’s content.

It got me over 4K impressions on a single tweet.
3/ The key to a good remix: add value.

With @prov_pizza I tried to add:

- Another perspective.
- Humor.
- Pizza. This usually does the trick ;
4/ Remixes were a pitfall too.

I was tempted to remix anything from anyone I found interesting, because it seemed to work.

@foundbryan taught me to stick to my niche.
5/ @prov_pizza is about leveraging talent and building better teams.

@foundbryan helped me realize that for the project to work long-term:

1 Genuinely interested follower > 10 vaguely interested followers.
6/ @craigburgess taught me to get doing things.

He’s the living embodiment of ‘putting in the reps’.

By creating pizza visuals everyday, the creative juices started flowing more and more.
7/ @alicellemee taught me to disconnect from my work emotionally.

It’s easy to get caught up in the (lack-off) success of your posts.

Instead of staring at notifications it helped to simply shift my focus towards creating again.
8/ @aadit taught me how to use Twitter the right way.

I went from consuming towards consuming to create.
If you liked these pizza visuals please give @prov_pizza a follow!

We’ll help you to leverage talent and build better teams, with pizza!

It’s a father-son project with @erikvanderkooij. He’s been teaching me for 21 years now.

More from Twitter

1/

Thinking about this tweetstorm, one of the issues I’ve run into as an engineering leader is what to call the software engineering stuff that’s “agile” given that the Agile Community(tm) has killed the brand.


2/

And by & large, I’ve taken to call it “DevOps”, because the DevOps community have taken up much of the mantle @KentBeck & the XP community started with. & Kent has independently focused on safe small changes deployed to production. Which is DevOps.

3/

Much of the art here is making changes safe enough to deploy to production continuously. And to do that, we need to design incrementally, test obsessively, take architecture seriously so we decompose dependencies. & we need to automate everything & do it all the time.

4/

It turns out that this is what Kent & @RonJeffries @GeePawHill & many other folks have been nattering on about & being broadly misunderstood. @KentBeck has some brilliant essays (scattered across FB & his site alas) & @GeePawHill has amazing twitter threads on the topic

5/

When you look at *what it takes* to get to the DORA measures that @nicolefv & team write about in Accelerate, the input metrics for the DORA outputs, it’s making small changes safe.

You May Also Like