Tweet
This whole book will be published using the #BuildInPublic philosophy (thanks, in part, to people like @MeetKevon ) and I'll be keeping Twitter up to date each time I publish a new version.

I'll also be updating my newsletter as I write more!

getrevue.co/profile/valhal…
Of course, there's @csallen , the founder of @IndieHackers . His platform has grown to become one that pushes #BuildInPublic to a massive audience through his newsletter and social media platform. I can honestly say I've learned more about startups from IH than anywhere else.
5 of my favorite developers that #BuildInPublic in no particular order:

@jasonleowsg - Jason develops the outlet for one of my favorite new habits: @golifelog for daily writing. I've written on lifelog every day for the past 10 weeks and it's become an amazing habit.
I need both pieces, the main app and the test framework, to use the same file parsers... so I make the file parsers a submodule of both the main application and the test framework, and voila! #BuildInPublic
The biggest reason I needed submodules though is I've got my work-in-progress main application that depends on a handful of Python libraries I use for file parsing. However, I also have a test framework built out that *also* depends on those same parsers. #BuildInPublic
Git submodules allow you to create parent-child dependencies between multiple different git repos.

For me, I have multiple front-ends (the ComingSoon landing page, a test dashboard front end, a work-in-progress app dashboard, etc.) and multiple backends. #BuildInPublic
One thing that I'm learning fairly quickly as I'm working on @malparse is that so much of working on a complex project with tons of interlacing parts is finding out how to organize a bunch of disparate Git repos.

So today I learned how to use #Git submodules! #BuildInPublic
Working on a video for my channel right now talking about why I love #BuildInPublic and one of the five reasons I chose is that you increase the feedback loop by creating an audience that is constantly giving you constructive (sometimes) criticism and ideas.
This is why I build in public:

- I share what I build
- Someone asks a question what is it
- I answer
- He gives feedback to improve it
- "Why didn't I think of it?!" 🤦‍♂️
- 10s later the new 'feature' is up
- Rinse, repeat

Imagine this over months..Your product UX will 10x twitter.com/therealjayber/…