Steve Streeting, a programmer, writes about developer workflow, game tooling, open source licenses, home automation, and version control setups.
Commenters mostly cite 'The Interruptible Programmer' as advice for coping with interruptions, and also point to his move from Unity to Unreal.
It's not exactly hard to find people discussing different best practices and their own individual workflows in Mercurial, either[1].
The existence of these articles doesn't tell us anything negative about Mercurial, or Git, it merely tells us that these tools are powerful enough to be used for Real Work in Real Workflows, and that there are few things people love more than talking about their workflows.
[1]: Random examples:
http://stackoverflow.com/questions/448567/best-practices-in-mercurial-branch-vs-clone-and-partial-merges
http://mercurial.selenic.com/wiki/WorkingPractices
http://stevelosh.com/blog/2010/08/a-git-users-guide-to-mercurial-queues/
https://blogs.oracle.com/kto/entry/mercurial_best_practices
http://mercurial.808500.n3.nabble.com/Best-practices-for-merging-td2989382.html
http://www.stevestreeting.com/2010/04/22/mercurial-queues-just-clicked/
I semi-regularly refer colleagues to this article I read some years back "The Interruptible Programmer" - it argues that it's hard to stay in the zone, so instead accept that you're going to be interrupted and embrace it.
https://www.stevestreeting.com/2010/09/04/work-2-0/
Good point. This recent HN item speaks to that. http://www.stevestreeting.com/2010/09/04/work-2-0/
The interruptible programmer
He's using Unreal for his latest game: https://www.stevestreeting.com/2020/05/07/from-unity-to-ue4---part-1/