From a Backend Developer to DevOps - THE FORCE AWAKENS by Mey Beisaron

Focus on understanding users (developers) needs before building tools - conduct discovery sessions and get early buy-in

Create simple, clear documentation with “how-to guides” and screenshots rather than complex technical docs - if something is too hard to document, simplify the tool instead

Set up regular collaboration sessions and office hours for developers to get help, but don’t force scheduled meetings

Join developer communities and Slack channels to learn from others facing similar challenges - no company is a unique snowflake

Build communication channels with users and maintain a documentation feedback loop to continuously improve tools and processes

Think like a developer but remember you’re building tools FOR developers - if they won’t use it, it doesn’t matter how technically impressive it is

Start with understanding existing architecture and workflows before suggesting new tools or changes

Create opportunities for developers to provide feedback early in the design process

When learning new tools/technologies, take time to ask lots of questions and understand the “why” behind choices

Remember that user requests and adoption are just as critical as performance and technical considerations when making architecture decisions