I can't wait reading the book new SaaS book https://t.co/3p5Ive4vxb
@danmartell@mattverlaque@johnnypage13 and Marcel thanks for your work, I'm excited about what you have created :-)
Meetings are the worst!
They burn people out and nothing gets done.
My tweet on meetings and burn out last week hit a nerve. It resonated with a lot of folks.
These are 7 steps I follow to aggressively reduce meetings.
A short 🧵
✅ You have a Laravel app
✅ You need to monitor your scheduled tasks
✅ Fast install is required
Why is nobody talking about https://t.co/2r7jjzyJNG?
Let's get more awareness about this incredible product. I'll buy a year Pro subscription to a random person who RTs this tweet.
@methodpark @OliverKnittel @github Wer beim Coden etwas Abwechslung braucht, kann beim #fit4christmas Adventskalender mitmachen: https://t.co/t4ViERmhhk ;-)
My new book co-authored with @tjaskula will be published soon and is now available for pre-order for a 45% discount through US Labor Day using this coupon: BACKTOLEARN
https://t.co/Pi9E4rNZIz
What books helped me become a better product manager? Or, in other words, what books should you read if you want to be a PM (or grow as one)?
- “Escaping the build trap” by @lissijean - perfect to learn the basics of being a PM.
- “Inspired” by @cagan -…https://t.co/yWzcvAr5FP
I’ve heard people justify keeping around legacy systems by saying "there’s a lot of domain knowledge in that code that nobody remembers." Frankly, if nobody remembers it, I don’t see the value. 1/2
There are many good questions that you can use in an interview to try to uncover agility. Here are a few. Can you suggest others?
• How long will it take for me to hear back from you?
• Can I meet the team? How about right now? 1/5
Agile projects are finished when the cost of change is greater then the revenue created by those changes. It’s not like a waterfall project, which has a well-defined end, and could go on indefinitely if revenue is increasing because of the changes.
Something to try: Date every item you put on your backlog. If it’s been there >6 months, it will never be implemented. Trash it. If it’s important it will come back.
After that’s had some time to percolate, do the same thing again, but >3 months, then >1 month.
@vitor_q@christianhujer PRs are a red flag, though. If they're in place, then there's definitely room for improvement right there. Lots of good things happen as you figure out how to get rid of them without losing quality.
@allenholub I totally agree that quality is everybody's concern. In my opinion a QA role should care about a common understanding about quality inside the team.