Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Data Loss at GitLab

blog.2ndquadrant.com

Post reply on HN
Print view View original

231–236 of 236 posts

Re: Data Loss at GitLab

#231

Post by developer2 »

haylem wrote: post #227
briffle wrote: post #195

Earlier quoted context omitted.

Just as an aside, you can hire a remote DBA to help out, until you get a full time person. We have a contracted 3rd party that does secondary monitoring around the clock, and a very, very good pro that we work with on projects. In our case, we have a 'retainer' for 15 hours a month. (and a fixed cost per hour after)

The entire GitLab team is remote, as far as I understand their company model. https://about.gitlab.com/2015/04/08/the-remote-manifesto/ But maybe you meant part-time?

Wow, that explains quite literally everything. Never, ever, trust a company whose cost-cutting measures involves opting to not pay for office space to run a legitimate business. The attempt to tout the lack of a full office as being "modern, hip, and cool" is a blatant lie from management - it's the same concept as open-office floor plans, reimagined and magnified by a thousand. They get to save hundreds of thousands (possibly even a couple of million) dollars a year; meanwhile, you get the exactly the kind of product you'd expect from a bunch of people pretending to be productive from home and working in such a disjointed fashion.

It is always a HUGE red flag when a company opts to have all or a majority of their workforce working remotely. It's a cost-cutting measure, nothing more. Cutting costs equates to cutting corners, and the business - and its customers - suffer the deserved consequences.

This really explains the flippant "it's 11pm and I want to go to bed" reaction in their report. The guy doesn't have an office to go to when shit hits the fan. He's sitting at home, with a bloody ssh terminal open, trying to remotely debug critical engineering problems over a slow vpn connection. Alarmingly huge red warning flags.

Re: Data Loss at GitLab

#232

Post by anonymous_green »

joelx wrote: post #220
anonymous_green wrote: post #207

Earlier quoted context omitted.

Most of their staff is from US/UK, but they just do not want to pay fair wages, which is why I posted the other thread where it was highlighted more.

Is it more fair to pay you $120k or more fair to hire three people in a lower cost area? This argument sounds more selfish than fair to me.

It's unfair to pay low to some and high to the other (as I pointed out earlier most of their employees are in US who are getting paid the average US salary).

A company should follow some rules to neutralise the discrimination between employees, it shouldn't be all pick and choose and take advantage where they can, that's not really the reason one should have a remote distributed team to get cheap labor.

Re: Data Loss at GitLab

#233

Post by anonymous_green »

bartvk wrote: post #226
hobarrera wrote: post #189

Earlier quoted context omitted.

Like I said, they're a remote company, and therefore can hire people in cheaper regions, and don't have to adapt to more expensive markets (like your own). I fail to see how this disproves it, it merely proves that you're not a good choice for them (because you live in a, relatively, expensive region).

> because you live in a, relatively, expensive region If what OP is saying is true, then the company might as well be upfront about it.

> If what OP is saying is true, then the company might as well be upfront about it.

Regardless of that, the average salaries are posted online and they seem to suggest quite the opposite to what they offer people outside of US. It's just an indication of how much of a bully culture they have in negotiations or discriminatory, they might as well just outsource the site and not have a team of their own at all.

Re: Data Loss at GitLab

#234

Post by anonymous_green »

developer2 wrote: post #231
haylem wrote: post #227

Earlier quoted context omitted.

The entire GitLab team is remote, as far as I understand their company model. https://about.gitlab.com/2015/04/08/the-remote-manifesto/ But maybe you meant part-time?

Wow, that explains quite literally everything. Never, ever, trust a company whose cost-cutting measures involves opting to not pay for office space to run a legitimate business. The attempt to tout the lack of a full office as being "modern, hip, and cool" is a blatant lie from management - it's the same concept as open-office floor plans, reimagined and magnified by a thousand. They get to save hundreds of thousands…

Cost-cutting measure don't just end at the office space level, they hire cheap developers too. There's quite a big divide between salaries they pay to their team in US and remote team and they get to do it just because they are "remote".

Re: Data Loss at GitLab

#235

Post by garaetjjte »

rdslw wrote: post #169
aamederen wrote: post #29

With this incident, they once again showed that they are dedicated to transparency, even in the worst days. This increased their popularity on me and I believe among other developers. However, this may not be the case with the business people. I hope they can survive that and also publish a guide for getting better at the "ops" side of the things.

Just to stress one thing, while mentioned in their report, most people don't comprehend: Gitlab was _one_ (last!) final step from complete data loss of everything . One. At that night, there was quite a long moment there had only one copy (and 6 hours old). Every other backup was missing/notworking/deleted. This is scary.

Didn't they had two copies? (staging server and LVM snapshot)

Re: Data Loss at GitLab

#236

Post by yuhong »

developer2 wrote: post #231
haylem wrote: post #227

Earlier quoted context omitted.

The entire GitLab team is remote, as far as I understand their company model. https://about.gitlab.com/2015/04/08/the-remote-manifesto/ But maybe you meant part-time?

Wow, that explains quite literally everything. Never, ever, trust a company whose cost-cutting measures involves opting to not pay for office space to run a legitimate business. The attempt to tout the lack of a full office as being "modern, hip, and cool" is a blatant lie from management - it's the same concept as open-office floor plans, reimagined and magnified by a thousand. They get to save hundreds of thousands…

I think remote is better than open office floor plans in many cases. It just have different problems.
Post reply on HN