I’m working on OpsOrch(https://www.opsorch.com/), an open-source orchestration layer that provides a single API across incidents, logs, metrics, tickets, messaging, and service metadata.
It sits on top of existing tools like PagerDuty, Jira, Prometheus, Elasticsearch, and Slack, and normalizes them into a shared schema. It doesn’t store operational data, it just brokers requests through pluggable adapters and returns unified structures.
The motivation came from incident response workflows that still require hopping across multiple vendor UIs and APIs with different auth models and query languages. Instead of another “single pane of glass,” this is meant to be a small, transparent glue layer.
On top of the core service, I’m also exposing everything via an MCP server so LLM agents can query incidents, metrics, and logs as typed tools without needing vendor-specific knowledge.
Currently open source, written mostly in Go and TypeScript. Still early, but usable with PagerDuty, Jira, Prometheus, Elasticsearch, Slack, and mock providers. Feedback from SREs and infra folks has been very helpful so far.
Oh, wow! I’d never made that connection. Thanks for pointing it out! You’re right, they do seem really similar, and it makes sense there’d be some cultural exchange around tea and communal brewing traditions.
Currently working on promoting Software Engineering Handbook (https://softwareengineeringhandbook.com/), a book that goes beyond typical technical guides by addressing both the technical and life aspects of being a software engineer.
Marketing it on Amazon, LinkedIn, and Reddit. It's slow but I'm making progress.
We’ve experimented with various approaches to promotion, including HN, KDP, Amazon Ads, and most recently Reddit Ads. It's been interesting to see which strategies resonate with the audience, but we're still figuring out the best way to get it in front of the right people.
Thanks for the questions! I hear you it does sound like a generic book name. Well, we have the domain and we couldn't really name it to something else as we think software engineering has many elements and we wanted to cover them.
Our book isn't just a technical book on software development. Instead, it goes into the life aspects of being a software engineer such as migration and parenting.
Many of us have wished for mentors who could guide us beyond the technicalities, offering insights into personal growth and career navigation. Recognizing this gap, we've created a resource that provides practical wisdom.
By taking a holistic approach to software engineering, we address both personal and professional development in a way that few other books do. This unique blend sets our book apart, offering a clear differentiator that defines our brand.
Any resources you'd recommend to learn marketing (esp. comming from a software background)? Asking for software friend who's having trouble marketing his software business.
I totally understand your frustration. We started writing our book long before(2022) AI became mainstream, and when we finally published it on May 2024, all we hear now is people asking if it's just AI-generated content. It’s sad to see how quickly the conversation shifts away from the human touch in writing.
Thanks for the kind words! We appreciate your suggestion, but we haven’t considered making the ebook public domain. Our goal is to provide real value with the content, and we believe the pricing reflects that.
Our perspective is valuable because we’ve gained extensive experience across both Europe and the U.S., working in startups and renowned companies. I (Yusuf) have worked with Amazon, Workday, and TripAdvisor, while Ender has worked at Microsoft, Meta, and Uber.
Our combined expertise spans multiple industries, leadership roles, and technical challenges, making Software Engineering Handbook a unique blend of insights from both continents. This diversity helps us provide practical, well-rounded advice for engineers looking to excel in their careers.
You can check out buying options on platforms like Google, Amazon, and Apple, all of which provide sample chapters for you to review before purchasing. Thanks for checking it out!
I and Ender have written a Software Engineering Handbook that covers key topics in software development, including best practices, design principles, and leadership advice for engineers. I’m now looking to sell it, but I'm unsure of the best approach to get it in front of the right audience.
I’d love to hear your suggestions on:
=> Marketing strategies for technical books
=> Approaches for building a community or audience around this type of content
=> Pricing models that have worked for you
Any advice or experiences from others who have successfully sold technical content would be much appreciated!
Thank you! This book isn't just a technical one. It's unique because it covers more than just software development, it goes into the life aspects of being a software engineer from migration challenges to balancing work as a parent.
We often lack mentors who guide us beyond the technical matters. In our careers, we wished having such mentors. In this book, we try to offer practical wisdom and answers to questions you may not even know you had.
It’s a holistic approach to software engineering, addressing both personal and professional growth in a way few other books do.
It sits on top of existing tools like PagerDuty, Jira, Prometheus, Elasticsearch, and Slack, and normalizes them into a shared schema. It doesn’t store operational data, it just brokers requests through pluggable adapters and returns unified structures.
The motivation came from incident response workflows that still require hopping across multiple vendor UIs and APIs with different auth models and query languages. Instead of another “single pane of glass,” this is meant to be a small, transparent glue layer.
On top of the core service, I’m also exposing everything via an MCP server so LLM agents can query incidents, metrics, and logs as typed tools without needing vendor-specific knowledge.
Currently open source, written mostly in Go and TypeScript. Still early, but usable with PagerDuty, Jira, Prometheus, Elasticsearch, Slack, and mock providers. Feedback from SREs and infra folks has been very helpful so far.
reply