Earlier quoted context omitted.
There is no basis for that assertion.
This is basic risk management. What matters is error survival, not absence of errors. Moreover, total absence of errors means accumulating dangerous risk. See NN Taleb, for example.
Data Loss at GitLab
181–190 of 236 posts
Re: Data Loss at GitLab
#182With 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.
Transparency? Gitlab is the company that interviews people and rejects them on basis of salary, they've been doing this for awhile, every few months they call a group of people, waste their time and then deny based on the salary. In my case, I've confronted them that USD 100-120k is the market average but they had this stupid startup argument that doesn't make any sense to me.
In the US maybe, but given that they're a remote company with people all over the world, they don't necessarily have to live by US standard (especially when it comes to spending!).
40k USD is a VERY good developer salary in Argentina, and I'd bet that in other countries a lower figure might make the cut too. I can definitely understand why they'd hesitate to pay thrice that amount.
I believe it's over 5 times the average salary.
Re: Data Loss at GitLab
#183Earlier quoted context omitted.
There is no basis for that assertion.
A well known library like curl, has had CVEs. A not known library that also addresses the same circumstances as curl might have none listed. Which would you prefer to use?
Re: Data Loss at GitLab
#184Earlier quoted context omitted.
A well known library like curl, has had CVEs. A not known library that also addresses the same circumstances as curl might have none listed. Which would you prefer to use?
The one with the CVEs because it has had eyes on the source enough to generate them. The devil you know and all that.
The other hasn't had that chance.
Thus, try the first, as it is better tested in the world.
Re: Data Loss at GitLab
#185Earlier quoted context omitted.
> GitLab cost everyone a day GitLab isn't popular because of the stability of its cloud platform. It's popular because you can install your own instance for free practically anywhere with minimal effort. I run GitLab CE on a box in my server closet for projects that involve livelihoods.
I know (because I use it and also host it at home, and like it). The point of my comment was HN's reaction.
Re: Data Loss at GitLab
#186Earlier quoted context omitted.
Transparency? Gitlab is the company that interviews people and rejects them on basis of salary, they've been doing this for awhile, every few months they call a group of people, waste their time and then deny based on the salary. In my case, I've confronted them that USD 100-120k is the market average but they had this stupid startup argument that doesn't make any sense to me.
> USD 100-120k is the market average In the US maybe, but given that they're a remote company with people all over the world, they don't necessarily have to live by US standard (especially when it comes to spending!). 40k USD is a VERY good developer salary in Argentina , and I'd bet that in other countries a lower figure might make the cut too. I can definitely understand why they'd hesitate to pay thrice that amoun…
And its not just me, they've done this in the past as well: https://news.ycombinator.com/item?id=10924957
Also when you work for a remote company, they are cutting cost in terms of office and all which should reflect back in the salaries, the whole idea of working remotely was to mutually benefit both the employeer and employee and not just gitlab using their whole startup argument to cop out when they want on that "truly remote" so-called transparent company.
Re: Data Loss at GitLab
#187With 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.
I am sick of the "They are transparent so it's ok" argument. The fact is this type of thing should not happen anymore.. I get it, stuff fails but it's not acceptable to lose production data at this scale and save face by being transparent. That was ok back in 2003.. Not anymore.
Re: Data Loss at GitLab
#188Earlier quoted context omitted.
Then you end up having deep expertise in a topic that's only important for larger companies. Sometimes this works out well, sometimes it leaves you a little stuck. :)
Meh. Just learn, learn, learn. If it isn't completely applicable to your life that's okay. Sometimes there are pearls of wisdom in best practices in field completely unrelated to your own. Learning something new is always a good thing.
Re: Data Loss at GitLab
#189Earlier quoted context omitted.
> USD 100-120k is the market average In the US maybe, but given that they're a remote company with people all over the world, they don't necessarily have to live by US standard (especially when it comes to spending!). 40k USD is a VERY good developer salary in Argentina , and I'd bet that in other countries a lower figure might make the cut too. I can definitely understand why they'd hesitate to pay thrice that amoun…
Yes, but if you look at the average here its not really outrageous or "5 times the average salary" as you said, here: https://www.indeed.com/salaries/Gitlab-Salaries And its not just me, they've done this in the past as well: https://news.ycombinator.com/item?id=10924957 Also when you work for a remote company, they are cutting cost in terms of office and all which should reflect back in the salaries, the whole idea…
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).
Re: Data Loss at GitLab
#190Earlier quoted context omitted.
I agree. Their catastrophe is not the kind of thing that represents mild hiccups in operations that will be quickly resolved by the same employees who allowed this scenario to occur the first time around. This isn't the result of a single oversight. It screams of a systemic problem with the way the business operates - period. Maybe every project is rushed out with the deadline being the only metric that counts, quali…
I totally agree with needing an experienced DBA, we've had a vacancy open for this for a while https://about.gitlab.com/jobs/specialist/database/
Might wanna revise that today.