I was reading the description of an upcoming project for our marketing team which started with this phrase...
Usual campaign stuff -- templates, banner, sidebar
This may seem innocuous, but everything we're now describing as "the usual stuff" used to be highly specialized hardcoded hacks that used to take entire engineering cycles to work on. Now it's just part of the product and can be lumped in as the baseline work. These days it is a task our marketing team can pull off. A year ago it was a big last-minute software project every time.
Since you're on DEV, you should have some familiarity with what we're talking about. DEV is built on Forem (which was extracted from DEV) and includes functionality for running "campaigns" which is a highly flexible utilization of the site to launch specialized functionality without having to write new code into the core codebase. We use this for contests and partnerships. It's functionality we use consistently, but not too long ago this was a productivity pipe dream.
This xkcd comic makes reference to the presumed futility of efforts to automate a certain type of task. It is so often the case that hard software projects not to result in actual value creation that it is worth celebrating when it does.
The work to "generalize" this functionality, make it re-usable for us and everyone who runs Forem, is an effort in longterm value creation that is easy to talk about abstractly, but seeing it in action as though taken for granted within our own team is still special. It's not necessarily easy to derive actual productivity gains from the software we write. There are always tradeoffs. I've worked on a lot of projects which presume to offer actual business value or productivity wins but fail to provide that in practice. It's satisfying to take notice of the times when it does work out.
A year ago this was a big project with unknown payoff. Now it's just the "usual stuff".