The distinctive cognitive strengths of a discipline are usually not what its practitioners think they are--or so I've argued. If that's right, then we should discount the whole genre of "here's how being an X gives me the tools to give an excellent analysis of Y" articles.
So, caveat lector, because I'm about to discuss how being a software engineer is informing how I quit coffee.
[Edited to add: Turns out a lot of people find it easy to quit coffee. I am not one of those people. When I, e.g., accidentally made decaf instead of regular, I knew it by how sluggish and off I felt.]
First, it made me worry about dependencies a lot more. This mostly came through experience, but reading Dan Luu really crystallized my thoughts about it. There are well-known frames of these habits both as delightful, life-affirming rituals and as draining, costly habits. In thinking-about-dependencies mode, the latter is more salient.
It also informed how I'm approaching this. The following ideas are salient:
So, here was my plan. (This is not medical advice. Please, please consult appropriate sources if you plan to address your dependence on stimulants / other substances.)
I'm at ~40% of my previous daily caffeine intake, with very little hot-beverage consumption.
Many people quit things in many ways; this has been remarkably painless.