I often find that developers with an interest in product development and the business side can make huge contribution by suggesting alternative solutions to writing more code.

With some gentle pushback on requirements they can help clarify what the real issue is. Of course, this has to be done carefully or it will quickly get very annoying.

Another useful skill is to have a feeling for when problems get too hard and it's time to backtrack. At least in my work, most of it is basic CRUD of different varieties. If I find myself inventing new things or not finding any answers Googling my problem, it's likely that I'm on the wrong track and there is a simpler path I missed.

Managed services. S3 instead of building a process to store and replicate files on a file system that you manage. DynamoDB or RDS instead of managing your own DB.

Libraries instead of cutting your own code for everything.

Effective searching for projects who have already done the thing you’re about to do.

Sometimes: it’s as simple as taking a day or few days to think the problem through to ensure you really understand it.

Finding a way to deliver the needed functionality in Excel/Sheets instead of a custom application.

Removing complexity and making the solution super simple can easily make you 10x or 100x more productive.

Don’t check hn, reddit, facebook, twitter or any other socials during work hours.

CI/CD and more broadly building abstraction layers and automation.