Even if the meeting itself was instant it would take more than 10 minutes. You would have to stop whatever you're working on, even if you're in the middle of a valuable flow state. Then after the meeting you have to get back into whatever it was, which alone can take you more than 10 minutes depending on the depth of your work.
If that's not bad enough then what you talked about in the meeting can also linger. You'll think of problems others have had and it causes your mind to lose focus, now you have thoughts about your problem mixed with other problems. These meetings also tend to happen during the mornings, smack in the middle of the most productive hours of the day.
No, a daily standup takes much more time than 10 minutes.
FWIW, imagine how a greenhorn might feel working on a team with you. If you feel like giving them some time of your day is a waste or that listening to their problems is a waste they're not going to feel enthused working on your team. Sure, that doesn't necessarily influence your current work item but it might contribute to overwork later if they leave for a team that actually makes them feel like they matter.
One solution I found is to write a quick status in the chat and excuse myself from the stand up.
Sometimes I finish 20 minutes before the stand up and think about what to do next. I usually won’t go into deep work but plan something, write my todo list on paper or review some PR to make use of the amount of time that’s to small to get into flow.
Literally, it's not 10 minutes. Count the time that you have stopped working and people are chatting waiting for the meeting, checking their email when they would not otherwise do so, not working on their main tasks.
20 minutes to half an hour of time not usable for main tasks is a more typical estimate.
We have six people in the stand-up.
If you're so sad about being interrupted then maybe you're taking on too much work?
That is actually a good idea, but it's the first time I heard about it. In most companies, this is not done. Also, it's not just the literal time of the meeting.
It's the time people spend waiting for the meeting, chatting, reading email instead of working on their main task for the day.
It's about the interruption cost and the disruption of what you were doing, not about the literal cost in minutes.
Also, most developers don't have a saying in how much work is assigned to them. Usually, they are over assigned already and the cost of the standup is not accounted for in how long tasks should take.
Add all standups of a week, and you have half a morning of work per week down the drain. That's a lot and again that is literal total time only, and does not account for interruption cost.
If you don't value those things then just be low key in your input, its literally 10 minutes of your day and has the potential to present an avoidable issue. To discard it as "management trash" is IMO a massive amount of disrespect toward your fellow team members. They can help and the stand-up opens opportunities for help. There's design work, review work, product management work, scheduling, triage, retrospectives. There's ample opportunities for efficiency gains in these areas during a stand-up outside of just writing code. If you think your job is just writing code then I can see how you might think they're useless but nobody's job is, we all work in teams.