1/ I don't care about clean code or tech stack anymore. Literally once you stop tinkering about what tech stack is best, you double your shipping speed.

2/ I moved from writing HTML/CSS to Tailwindcss and DaisyUI. DaisyUI mainly for building my landing pages and Tailwindcss for building the frontends of apps.

3/ The only environment I have is production aka master. I ditched the separation of environments. Prior to that I had at least 1 dev and 1 prod environment.

4/ I moved from React to Svelte. I feel Svelte is more intuitive and very easy to learn. Finally I don't need to learn some opinionated stuff.

5/ All of my backends are built on top of @AWSAmplify . I basically describe the stuff I want in schema.graphql and the backend gets auto-magically created for me.

@AWSAmplify 6/ I write no tests, I absolutely don't care about programming patterns and if my code works I leave it as it is. The main goal is to ship a working and not a beautiful code

@AWSAmplify 7/ I spent 3 months to learn the rules of a good design. My goal is not to build the best UIs, but to build professional looking UIs. I would say learning the rules of design provides the highest leverage effect for devs.

@AWSAmplify 8/ I finally started with marketing on Twitter. Most of the revenue comes from Twitter. Prior to that I tried to be active on all platforms, but it never worked. Once I picked a single platform for focusing, it started to work for me.

@AWSAmplify 9/ Shipping half-backed products is better than not shipping anything. At least people from Twitter are okay with bugs, I constantly get bug reports in my DMs. Every time I fix something, I see my MRR going up.

@AWSAmplify If you enjoyed this thread: 1. Follow me @tarasowski for more 2. RT the tweet below to share this thread with your audience

@tarasowski Great thread Dimi! 💪 I followed a path very similar to yours. I'm curious about the schema.graphql of Amplify. I understand that you get a GraphQL API (which is cool). You just need to implement the backend logic then. Are you using it with NextJS?

@ikoichi Hey Luca! You don't need to implement the logic. @AWSAmplify generates the tables, queries, mutations and subscriptions for you. Basically what you get are JS/TS functions that you can call. That's it. The codegen module does that for you!

@tarasowski Loved the thread! Just what I needed. After years of being a developer and obsessing about doing things the “right way”, I need to get out of that mindset and learn to ship faster! Tough to also do with a full time job where quality is also expected 😅

@glenp01 I would say the most underrating skill is context switching. I absolutely agree when you work with a team you need to follow a set of rules. But if you work alone, skip them. "If the only tool you have is a hammer, it is tempting to treat everything as if it were a nail."

@tarasowski Would love to know how much each of this projects are making 😁

@nilansaha Currently around $500 a month (with 100% growth month over month in revenue). With one exception, one of the projects made $20,000 from a single sale.

@tarasowski Nice work @tarasowski ! Would love to feature your growth story in the @SaaS_Weekly newsletter.

@ian__ito @SaaS_Weekly Take it 😄 let me know if you need anything else.

@tarasowski Awesome thread Dimi! This is so me, except I use Firebase instead of Amplify. I'm learning aws rn. Do you use cognito with amplify for authentication?

@0xshrini Yes Cognito!