>Any tips on how to be "Maintenance focused more than feature focused" Honestly this is more "how do I keep from having to perform maintenance" but just spitba

>Any tips on how to be "Maintenance focused more than feature focused" Honestly this is more "how do I keep from having to perform maintenance" but just spitballing... Do you have defined Service Level Objectives (SLOs) for your APIs? Do you have unit tests so you can both prove changes do what's needed and that nothing else broke (regression testing). Do you have good error handling and readable error messages or is that all #todo? Are your processes idempotent? Is there a documented and automated recovery procedure if not? Add all the features you want, but if you build them to have a high uptime and resilient up front you're really combining a view into maintenance (or more importantly - not needing it) while still delivering features. And if those things aren't true then I guess making them true first before adding features is sort of what the original poster meant?