swami108

8 ms·

1.
Show HN: I built a weekly sprint planner for individuals(qtr.ai)
3 points by swami108 3y ago|0 comments
2.
by swami108 3y ago
Talent Code by Daniel Coyle. It’s an amazing book about how the best teams and most skilled people in the world learn and get good at their craft. I started learning piano as an adult which is incredibly difficult. Reading this book made a
3.
by swami108 3y ago
Haha, no worries :) My latest failure was Wize, a mobile app that let anyone share their skills. It was a great idea, a bit early for its times (live streaming app before Instagram Live and Tik Tok), and it had a great start--we were in the
4.
by swami108 3y ago
Tells you how many years I’ve been failing
5.
by swami108 3y ago
- chronological and categories. - pin the best ones on top for each category. - have an “all” category, which could be your default.
6.
by swami108 3y ago
I’ve pivoted from full stack to frontend to product. The switch from engineering to product can be challenging. Two tips. - start contributing to product on the side while on your current engineering job, and try to get a PM position with y
7.
by swami108 3y ago
I’ve failed more times than most people. But I’m not a failure.
8.
by swami108 3y ago
Related question: I wonder how many humans (regular people, not copywriters, marketers, and businesses) are actually happy that chatgpt is here.
9.
by swami108 3y ago
MuseScore and Tempo (metronome).
10.
by swami108 3y ago
Quality ideas don’t come up on demand. They come sporadically over time, so it’s best to have a system to capture these ideas. I capture my ideas using Drafts on Apple Watch or phone if I’m not on my computer and eventually move them to Roa
11.
by swami108 3y ago
TDD is the second best method. The first is developing good habits—list out all edge cases and just manually test it out. If you work in a team, the PM, developers, and QA can brainstorm these edge cases together. It’s these simple things t