Hacker News new | ask | show | jobs
by sytse 2883 days ago
We did https://about.gitlab.com/2017/10/11/from-dev-to-devops/ when we where at 50% of our current number of engineers. So far so good.
2 comments

Not trying to be negative. I genuinely would like for GitLab to succeed. My experience (in a totally different industry and scenario, but with product building all the same) was that our decision to pare down to our core competency and focus was the best decision we ever made. We were attempting a full productivity suite, similar in concept but again a different industry. I’m interested in finding an example of a similarly modeled company to compare.
Really no, look at all the comments here (and this is only from techies): you have lost us, we don't know anymore what you are doing, or even trying to do.
We are trying to make a single application that covers the whole DevOps lifecycle, from planning your change up to monitoring its effect.

We're doing it because we believe there are emergent benefits to having the lifecycle in a single application https://about.gitlab.com/handbook/product/single-application...

The idea seems great, but it's not working: there is no single application that can fit all uses, and you are loosing most of the users on the way.

I'm using Gitlab, btw, but only for the self-hosted git and it's user interface (ie. your core). All the other parts (bug tracking, CI, chat, ...) are in different and more appropriate tools for each of our use-cases... because most of yours are not complete enough, or sometimes it's not even clear how they actually could work for us (mattermost for example).