News for hackers. Stuff that matters.
Re:Before Growth by beat on Friday January 15, 2016 @03:11PM (#10911767)
I'm in that "I need to build this so it stops haunting my dreams" category. And I'm a lot older than you. After 20 years in the industry, I kept having the same problem over and over, at job after job. One night, I thought "Man, I wish there was a product for this, but no one makes it." The I thought, "Hey, I could make this! And lots of people have this problem, and it's a really expensive problem, so I could make money at it!"

Three years, a lot of personal cost, false starts, finding co-founders, and other headaches later, and I'm finally getting to where this year, it should start making money. I can't even begin to describe what a difficult experience it's been. Someone once told me the only emotions founders experience are elation and terror. What they didn't tell me is that they are often at the same time, and often for the same reason, and sometimes are indistinguishable from one another.

I'm a founder because I couldn't live with myself if I wasn't. Doesn't mean it's easy, or it's going well all the time.

So that being said... if you want to be a founder, and you're a good software engineer (I'm assuming you're tech, that's why you're here), don't even bother coming up with an idea! Instead, go looking for experienced business people who have a real business idea and the knowledge to pull it off - except for the technical skill. Become their tech co-founder. Because there are so many of them, and so few of us, you can afford to be choosy.

If it's someone who has successfully started businesses before, all the better! There are lots of really smart, driven, reliable business people out there with great ideas, but without the technical skill to implement. Find one, and make something great.

Re:Before Growth by mikepurvis on Friday January 15, 2016 @05:23PM (#10912690)
Matchmaking here seems like a challenge—you're dependent on already having a big network, with the right kinds of people in it.

There are a lot of ways for it to go wrong, eg business competitions, hackathons, etc.

Re:Before Growth by mahyarm on Friday January 15, 2016 @07:45PM (#10913520)
So I looked at your product. How do you deal with the firehose of data issue making it too hard to figure out what happened.
Re:Before Growth by bglazer on Friday January 15, 2016 @05:43PM (#10912822)
Hey, I just wanted to say that I checked out your company, and I think you have a very compelling product. Unfortunately, I'm not in a position to buy it (junior engineer at a massive corp). Instead I just wanted to wish you luck!
Re:Before Growth by beat on Friday January 15, 2016 @06:06PM (#10912958)
I have a very compelling idea, and a very compelling problem. And a product that is not yet sales-ready yet. But we're getting there. It's been in a fundamental rewrite mode since August (what I thought was the beta was actually the alpha), and I've since added two co-founders so I'm not doing it alone anymore - deeply experienced enterprise engineers like me who have felt the pain that we're trying to solve viscerally.

But yes, thanks for the confidence! :)

The best part of it is when I talk to the target users about it and their eyes light up and they get so excited. The problem is huge, and the current solutions are terrible. If we can't make money at this, it's an execution problem, not a market problem.

Re:Before Growth by pm on Friday January 15, 2016 @07:43PM (#10913512)
Had a look, and yes, that's not an easy problem to solve. Good luck with it.
Re:Before Growth by paulmd on Friday January 15, 2016 @09:28PM (#10913927)
How is your product different from etckeeper + flyway + source control?
Re:Before Growth by beat on Friday January 15, 2016 @10:13PM (#10914048)
First and foremost, it monitors the real world, not the version control system. It sees things as they are, not as they're supposed to be. It detects manual, unversioned changes. It detects changes from automation, or from intrusion. It detects things that can't be versioned, like reboots or cert expirations.

Second, it is minimally invasive. You don't have to change your process in order to use it.

Third, it shows relationships between systems. An application isn't just source code. It's compiled binaries, OS patches, user security, databases, firewalls, message queues, apis, and more. Here's a common failure pattern - System A changes, System B breaks. System A might actually be perfectly fine and correct, and B as well, but the relationship between A and B is broken. Change the database schema, and the app can no longer read it. Change the dns, and the UI can no longer find the API. For any decently complex application, the potential sources of failure are in the thousands, and potential interactions effectively infinite. Now scale this up to the enterprise, to organizations so large that your app can be broken by departments you didn't know existed...

Re:Before Growth by subway on Saturday January 16, 2016 @05:44AM (#10914956)
Does it detect when you have a busted marketing site?

https://congruence.io

Re:Before Growth by beat on Saturday January 16, 2016 @10:53AM (#10915574)
Thanks. It's a known problem... we're currently in product work and haven't been dealing with marketing at all. It's just a cert problem - http://congruence.io still works.

And yes, once it's working, it will be able to detect such issues.

Re:Before Growth by beat on Saturday January 16, 2016 @03:08PM (#10916619)
And the certificate is now fixed. Try it, https://congruence.io is working again!