328 karma · joined July 31, 2011
You don't, but it's also not necessary. It's impossible to objectively assess someone's subjective experience, the best we can do is look at groups of people and attempt to find reliable indicators.
The point is that some people will over-emphasize any given trait, and others will under-emphasize it, so on average it evens out.
Think of color perception for a similar conundrum. How can you be sure that the red you see is the same as everybody else is seeing?
We do have this note on all job pages, which maybe should be more prominent:
> Avoid the confidence gap; you do not have to match all the listed requirements exactly to apply.
Some amount of general programming experience is definitely required though, since SREs and DBEs frequently have to dig into our codebase and things like Ansible runbooks. And especially regarding SQL, a lot of it is heavily abstracted not only through the Rails ORM but also our own code.
Found some other jobs that focus less on programming, though we don't have current openings for most of these either:
- https://about.gitlab.com/job-families/engineering/cloud-nati...
- https://about.gitlab.com/job-families/engineering/infrastruc...
- https://about.gitlab.com/job-families/engineering/monitoring...
- https://about.gitlab.com/job-families/engineering/security-e...
- https://about.gitlab.com/job-families/engineering/vulnerabil...
We don't seem to have a good overview of all roles, I found these through https://gitlab.com/gitlab-com/www-gitlab-com/tree/master/sou... :)
But yeah, our response times have been steadily increasing and could definitely be a lot better ;-)
Note that this was always only about excluding certain job roles who have administrative access to production servers, not all jobs in general.
The "Ops" section actually consists of product development teams for features in GitLab itself (the Configure/Monitor "stages"), while the SREs are in the "Infrastructure" department. See https://about.gitlab.com/handbook/engineering/#engineering-d.... But yes, we don't seem to be hiring SREs at the moment, but I assume we'll add more openings in the beginning of next year.
Regarding DBAs, that job you posted is more of a normal Backend Engineer role with a database specialty. We also have dedicated Database Engineer roles:
- https://about.gitlab.com/job-families/engineering/database-e...
- https://about.gitlab.com/job-families/engineering/database-r...
The job description for SREs is here:
- https://about.gitlab.com/job-families/engineering/site-relia...
And yeah for some reason Ctrl+Left/Right to jump around words, Ctrl+Shift+Left/Right to select words, and Ctrl+Backspace to delete a word, are disabled in the console prompt as well (they do seem to work in all the other DevTools input fields I can see). These are pretty ingrained in my muscle memory so I constantly bump into them.
Also I'm on Linux, in case that matters.
But even before that it just seemed like a "guideline" to me rather than a strict "rule" that was actively enforced, and it was introduced years ago before we had a proper Code of Conduct in place.
There's also a dedicated Search team being built at the moment to focus just on this.
- https://gitlab.freedesktop.org/
- https://salsa.debian.org/ (AFAIK this is an ongoing migration)
Others are considering a migration:
- KDE: https://gitlab.com/gitlab-org/gitlab/issues/24900
- GNU Emacs: https://gitlab.com/gitlab-org/gitlab/issues/28152
Maybe someday we'll have federation to work around this: https://gitlab.com/gitlab-org/gitlab/issues/30672 :-)
(found through the <link> tag on the blog)
> The resolver must not retain, sell, or transfer to any third party (except as may be required by law) any personal information, IP addresses or other user identifiers, or user query patterns from the DNS queries sent from the Firefox browser.
> Transparency Report. There must be a transparency report published at least yearly that documents the policy for how the party operating the resolver will handle law enforcement requests for user data and that documents the types and number of requests received and answered, except to the extent such disclosure is prohibited by law.
> The party operating the resolver should not by default block or filter domains unless specifically required by law in the jurisdiction in which the resolver operates.
This doesn't really matter if you live in the US, but most of us don't.
I'm not sure if GitHub Sponsors is already planning this, but since they also track dependencies they could automatically distribute a part of the donations to all the transitive dependencies.
Also, I agree with others that Open Source by itself is not a business model. It's inherently altruistic, so self-sacrifice is a given and if you want to get paid, the best solution IMHO is to support companies who support FOSS by working for them (or founding one yourself). And while of course not everyone has that privilege, we collectively do have a lot of power to influence the job market and donation platforms:
- If you're currently interviewing, make it a point to ask about this.
- If you're currently employed, ask around what your company is sponsoring, or organize an effort to start doing so with a group of like-minded people.
- And lastly, if you're making a shitton of money, donate to the software you use in your private life.
I'd be more than happy to pay good money for each movie/episode, and would regularly pay more than the suggested price to creators I especially enjoy, like you can do on Bandcamp.
I think this was a great way to not only verify coding ability, but also testing team work and communication skills.
- 31K source packages
- which build into 136K binary packages
- consisting of 1.2 billion lines of code
[1] https://sources.debian.org/stats/
[2] https://packages.debian.org/unstable/allpackages?format=txt....
In German we have "sie" which is both third-person singular female, third-person plural, and when written "Sie" also a formal second-person singular/plural. It works just fine.
There's also support for zero-downtime upgrades [1] but I haven't tried it yet.
[1] https://docs.gitlab.com/ee/update/#upgrading-without-downtim...
IMHO it really needs labels as first-class citizens, similar to GMail.