This paper discusses whether Bitcoin is entering a right- or left-translated cycle as of early March 2025. We argue based on six key macro and market indicators: M2 Global, Core PCE, NASDAQ Composite, ETF Net Flows, Unemployment Rate, and Fed Funds Rate. Both, right-translated (bullish scenario) and left-translated (bearish scenario) cases are considered, alongside key market implications.
Problem to solve: keeping a team of people working on the same project up-to-date in a simple way - overcoming barriers like availability and distribution of team members.
You might be right with your arguments if you see StandupMail as a tool replacing your Scrum standup. However, it's intended to be a tool for every team out there working on the same topic - most teams don't even know what a "SCRUM Standup" is (ask your sales team for example).
I often hear that from smart engineers and like the DIY attitude. However, it's not a no-brainer to build a stable architecture to provide this service. We know, because we build many sw architectures before.
One of the ideas behind is, that we want to provide something using a communication channel people use every day rather than introducing a new one like Slack, Hipchat etc. However, StandupMail is a great addition to teams using those tools already.
Using StandupMail is not about sending in "dones" for every single task accomplished. It's more about a quick recap of what everyone thinks is important for the team to know to stay productive the next day and overlook the big picture of the project.
I'd suggest you look closer at the services that teams are already using and try and add value to those by algorithmically generating what you think is useful for people to know.
I agree simply acknowledging what to-do's people have ticked off in the day isn't that useful (BC can already do this for example) but there is room for intelligent insight here. You could determine people's productivity rate towards a milestone and provide predictions if things are on track for a particular milestone date etc.
I think then you would have a valuable service. Just my 2 cents ;-)
You're free to define when the team is expected to answer. It could be in the morning... during the day. Alle-in-one emails but also one email per task finished fitting into existing workflows.
However, the idea is to send a quick answer back, when your accomplishments are still "fresh" in your mind - Shouldn't take you longer than 5min.
And yes, workers should spend time with their families. I'm doing that right now, too :)
