GitLab announces workforce reduction and end of their CREDIT values
1–10 of 750 posts
Re: GitLab announces workforce reduction and end of their CREDIT values
#2Oh and it won't be done until June 1st, so the employees can have some anxiety until then. As a treat.
Re: GitLab announces workforce reduction and end of their CREDIT values
#3[dead]
Re: GitLab announces workforce reduction and end of their CREDIT values
#4Oh and it won't be done until June 1st, so the employees can have some anxiety until then. As a treat.
At least they are honest about it:
> The planning is happening openly, including a voluntary separation window. That creates real uncertainty for our team over the next few weeks, but we believe the outcome will be better for it.
No good way to execute lay-offs, my preference would be to do it like a band-aid. What use is it to do it in open unless they plan on having gladiatorial matches to keep your job. Otherwise it's just like a painful game of Duck Duck Goose.
Re: GitLab announces workforce reduction and end of their CREDIT values
#5Oh and it won't be done until June 1st, so the employees can have some anxiety until then. As a treat.
At least they are honest about it: > The planning is happening openly, including a voluntary separation window. That creates real uncertainty for our team over the next few weeks, but we believe the outcome will be better for it. No good way to execute lay-offs, my preference would be to do it like a band-aid. What use is it to do it in open unless they plan on having gladiatorial matches to keep your job. Otherwise…
the people who would leave after a layoff can do so preemptively, perhaps saving headcount for someone else?
Re: GitLab announces workforce reduction and end of their CREDIT values
#6Earlier quoted context omitted.
At least they are honest about it: > The planning is happening openly, including a voluntary separation window. That creates real uncertainty for our team over the next few weeks, but we believe the outcome will be better for it. No good way to execute lay-offs, my preference would be to do it like a band-aid. What use is it to do it in open unless they plan on having gladiatorial matches to keep your job. Otherwise…
the people who would leave after a layoff can do so preemptively, perhaps saving headcount for someone else?
[flagged]
Re: GitLab announces workforce reduction and end of their CREDIT values
#7Time to tell everybody about Forgejo, again.
Re: GitLab announces workforce reduction and end of their CREDIT values
#8TLDR: Because of AI the future belongs to the engineers, so we took the noble decision to stop hoarding them on our payroll and make sure there are enough to go around for the other companies.
Re: GitLab announces workforce reduction and end of their CREDIT values
#9[deleted]
Re: GitLab announces workforce reduction and end of their CREDIT values
#10Here's their soon to be updated(?) handbook with the CREDIT values: