IssueRaiser

I'll be back with a "Show HN" once I get the beta running.

I'll be back with a "Show HN" once I get the beta running. I took several months last year to work on it full-time and got an alpha version working, which taught me a ton of things I didn't know I didn't know about the problem I'm tackling. Now, I'm working on a beta based on lessons learned from the alpha. The product is a way to answer the simple yet awful question, "What changed?" Configuration change is the primary cause of failure in complex software systems. But the part that breaks isn't necessarily the part that changes. For example, a database schema change can break apps that rely on the database. But in large organizations, where the database is administrated by an entirely different team from app development and developers may not even be allowed to look at the production environment, it's a huge pain point. Detecting configuration change and finding the relationships and impact is a really difficult and challenging problem. The biggest takeaway from the alpha for me was that "noise shaping" is a hard problem. For example, Wordpress alters the schema of its MySQL database several times a day. It's a tiny thing (an autoincrement value on a single column), but it makes sorting important changes like upgrades that only happen weekly or monthly or yearly from unimportant changes that happen daily. The trick now is to get a product out of it good enough to make money, so I can afford to quit dayjobbing and live off my own creation, rather than sitting at someone else's desk and counting the number of times a day I wish I had my own product here to help solve the problems I deal with over and over, every damned day.

Posted by beat on Jul 20, 2015, 3:23 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments

ux (SaaS)

I'll be back with a "Show HN" once I get the beta running.

beatJul 20, 2015, 3:23 PM

I'll be back with a "Show HN" once I get the beta running. I took several months last year to work on it full-time and got an alpha version working, which taught me a ton of things I didn't know I didn't know about the problem I'm tackling. Now, I'm working on a beta based on lessons learned from the alpha. The product is a way to answer the simple yet awful question, "What changed?" Configuration change is the primary cause of failure in complex software systems. But the part that breaks isn't necessarily the part that changes. For example, a database schema change can break apps that rely on the database. But in large organizations, where the database is administrated by an entirely different team from app development and developers may not even be allowed to look at the production environment, it's a huge pain point. Detecting configuration change and finding the relationships and impact is a really difficult and challenging problem. The biggest takeaway from the alpha for me was that "noise shaping" is a hard problem. For example, Wordpress alters the schema of its MySQL database several times a day. It's a tiny thing (an autoincrement value on a single column), but it makes sorting important changes like upgrades that only happen weekly or monthly or yearly from unimportant changes that happen daily. The trick now is to get a product out of it good enough to make money, so I can afford to quit dayjobbing and live off my own creation, rather than sitting at someone else's desk and counting the number of times a day I wish I had my own product here to help solve the problems I deal with over and over, every damned day.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue