GitLab

I have to say, the way you fought your downtime with full transparency in February this year was amazing.

So, this is my question for you. Just like how buildings have mock fire drills, do you think programmers should simulate failures?

Let's face it, downtime is bad and no one wants it. That being said, one should be prepared to handle it. A team of engineers can take the test environment down and another team will try to bring it back up. So, when production actually goes down (god forbid), the engineers will be acclimatized to handling it in a nice way.

Today most open source projects are being hosted on GitHub. What are GitLab's initiative to encourage more developers to use GitLab for their open source projects?

GitLab started using Vue and how is it working out for you now?

Hey, guys, Thanks for the AMA.

GitLab has over 150+ people working remotely. So my question is can you give any tips/advice for working remotely?

Firstly, I must say that I admire your transparency policy in GitLab. It serves as a great source of inspiration for me in my work.

However, now I'm using GitLab on a daily basis, and when I see information about downtimes or some issues, it makes me sad. It's because I know that with high probability my work routine will be affected by those failures.

So here is my question: in your opinion, what is better for a product or a company – be transparent and let people see that nobody's perfect or make an impression of being reliable and trustworthy?

Hi, Dmitriy, Thanks for the AMA.

People might have asked you this question thousands of times previously, but I want to hear your opinion on it.

Why should a developer (not so famous) choose to go with GitLab instead of GitHub in 2017? GitHub has many users today, so the chances of getting more visibility are definitely higher if they opted to go with GitHub.

You are one of the most transparent companies that I have seen. In your opinion how important is it for companies today to be transparent to their users?