There's a 'github down' post here every other day.
The ball is right there, bouncing alone in front of the goal, and they just have to position themselves as "we're the stable ones" to score that market when the exodus inevitably happens.
This is what happens, when decision makers are out of touch.
So many things they could be doing, to make people buy into their services. For example they could simply run campaigns about how they promise to never use customer and user repositories for AI training. Or they could show better uptime statistics. Their CI language is better than Github's too.
If anyone gave me a choice between Gitlab and Github, I would go with Gitlab. But if I had additionally the choice to use Codeberg, I would choose that.
Maybe they are just not looking to grow. If they made such a statement, that would actually be a pleasant surprise. No hunger for "infinite exponential growth", just to impress investors? Great! That's a fat plus in my book!
The big thing on their roadmap is rearchitecting for something that can handle the increased load, though. Like, they're clearly paranoid that if they don't move fast, they're going to be just as busted as Github.
TBH the open source nature of gitlab means that any sufficiently large and clued-in hosting company (think: servercentral/deft/summit, whatever it's calling itself these days, or one of its competitors) could put up gitlab instances for people to use and meet more nines of uptime than github. It doesn't have to be the gitlab company itself running servers with the httpd and back-end database.
I understand the meaning, however, in that they're well positioned by having the company name and domain name, same general way that non-technical people will pay wordpress.com to host their blog/small website because it's very easy, rather than DIYing it or paying a 3rd party.
GitLab isn't open-source. It's "open-core". Third parties hosting GitLab instances don't have access to the same range of features that GitLab-the-company does.
GitLab Community Edition (CE) is available freely under the MIT Expat license.
GitLab Enterprise Edition (EE) includes extra features that are more useful for organizations with more than 100 users. To use EE and get official support please become a subscriber.
JiHu Edition (JH) tailored specifically for the Chinese market."
Personal opinion, but I think a great deal of the people who are presently overloading github with one person created vibe coded projects would be just fine with the "CE" feature set.
Having been in some of these values meetings, I really imagine it went like this: someone wanted speed, and someone else wanted quality. Sorry, I mean Speed and Quality. Many people said there is a tradeoff between those two things, and only one thing can be first.
Some brilliant businessman: "I know, we'll combine them. We want Speed _and_ Quality."
If they're asking you to do more for less pay and with fewer coworkers to help, don't feel bad if the company code turns into unmaintainable, unintelligible garbage. They can't really stop you. It's just AI. Something is going to have to give.
Every IC ought to use the present day as the opportunity to build a nimble competitor to their old employer (or whatever industry incumbents they want).
I thought that the GitHub degrading would be an opportunity for them to be an alternative more focused in stability and a customer centric approach .
But it's just more slop
GitHub is already the main platform for random open-source projects, and that's unlikely to change any time soon. GitLab's selling point is essentially "Github, but not by Github". They would do Just Fine offering a highly-restricted free account for the handful of hobbyists who care enough about leaving GH but don't care enough to go to Forgejo & friends and for the people doing evaluations, offering free credits to the few high-profile FLOSS projects who accidentally end up on GL-the-SaaS instead of self-hosted GL, and for the rest just focusing on paid corporate customers.
Every company I've worked at hammers the "ownership" idea and I hate it so much. It's how they drive a culture where employees are expected to invest themselves into "owning" a problem space that can be taken from them at any moment. It's how they trick you into doing extra work that's not in your job description.
Unless you're ACTUALLY an owner, don't be fooled by an "ownership" value.
It's the norm at Big Tech these days. Directors and VPs take all the glory if it goes well while ICs, team leads, and people managers get all of the blame if it doesn't. When the charlatans get exposed, they bounce on to the next company with their charlatan friends. Rinse and repeat while swapping RSUs for index funds, retire with >$10m before 50. If we stopped allowing this to work in our industry, it wouldn't be such a common thing. Unfortunately, with how everything is these days, these people are getting hired on vibes and bravado.
Conversely, you have "full ownership" and have the ability to decide the direction, as long as it's the same direction as your higher-ups have decided.
All the talk about higher-ups taking the big paychecks for "carrying so much responsibility" is in most cases just complete horseradish. When something goes wrong or doesn't run well, suddenly none of the higher-ups are taking the responsibility. Hmmmm it's strange, innit?
"Speed with quality" combined with that says a lot. Sounds to me like it will be the base expectation that their remaining developers slop out features in record time. Any failures will be theirs to "own" personally.
"And that ownership will of course automatically mean that they will work extra hard to ensure quality! Man, what a great idea! Yo, why we didn't think of that before?!"
One must really wonder, if they ever try to hear themselves talking or read their own prose. Maybe they do, but simply don't care at all?
I read this and often think, yes, yes we know, but then I hear juniors at work taking these ideas at face value without considering things like stock splitting and preferred shares.
Owner is the one who gets the added value assigned to. At least according to the Das Kapital. So the check is easy - do you see the added value flowing onto your account or not.
I'm firmly not in Trump's anti-DEI camp but I have seen what can happen when you make it one of your core values. You can end up with a lot of people talking about it a lot, lots of meetings and initiatives rather than doing actual work. And usually those don't go anywhere because the people doing it don't have any power to actually change things. It's unlikely that a company like Gitlab really needs anything changing anyway.
It doesn't make sense for it to be 40% of their values, especially if they're losing money (or very close to it).
Places I've worked that actually seem to have inclusion as a core value are great places to work and seem to have high functioning teams. My impression mostly though is more that it was never really a value for management but they wasted a bunch of time talking about it. In general any mismatch between stated values and actual values has been awful to deal with and is a red flag for places to work.
> Places I've worked that actually seem to have inclusion as a core value
I am not sure if you had implied it but that would align with my experience as well: places that tout diversity were the worst places to work (as someone who is seen as 'diverse') while the ones that treated everyone the same and had the expectation everyone pulls their weight.
I absolutely despise people treating me differently because of who / what I am rather than doing good work. I will take mildly inappropriate good-nature jokes over head pats every day of the week.
I love wildly beyond mild inappropriate jokes as they are a litmus test for a thinking person. The people that take things way too sensitive are a net drag and buzz kill for doing the grinding required. It goes both ways too. I love it when people are agressive with me. So, by freedom of association, cliques form and I have no problem with nepotism because the ultimate currency in life is trust.
That's the thing - you can have it as a lived value, or you can have HR run programs. Very few places have/had both. Given the choice, I'd pick door #1.
(Saying this as a strong advocate for diversity and inclusion, lest there's confusion)
There are two ways to do diversity - the first is to put a brutal skill filter and take everyone that passes it no matter their skin color, body weight, religion or politics. The other is to reduce people to their demographics and push for (in)visible quotas. One of them leads to crappy results.
The meritocratic delusion is that you would be in the "have" pile, rather than sitting in the back of the bus with the rest of the "have nots".
Of course, its statistically most likely that any individual would belong to the much larger latter group but statistically like that only apply to other people, right?
Worse, its a zero step thinkers solution. Step zero is a merit based system, step one is for the people with motels on Boardwalk and Park Place to ensure they can never lose again by rigging the system to ignore merit in favor of capital.
> You can end up with a lot of people talking about it a lot, lots of meetings and initiatives rather than doing actual work. And usually those don't go anywhere because the people doing it don't have any power to actually change things.
Someone I'm close to is going through this right now. They work at a place that officially highly values "inclusion", and their employer's website is dripping with virtue-signaling language related to it. But that someone is disabled, and in fact there's nobody at the organization who owns accessibility issues. Disability accommodations are haphazard, and often not timely. Why? Because no one owns them. They just get punted to an internal employee affinity group of disabled people who don't have a real chain of command, a real budget, or even a real prerogative to do accessibility work, let alone meaningful power— many of its members are routinely chastised by their bosses whenever they dedicate any time to solving access problems within the company. "That's not what we pay your for", "that's not your job", "I need you on this other thing", etc.
Meanwhile the organization receives public accolades from meaningless business press organization as a "great place to work" or even "great place to work for people with disabilities".
I think it's fine for companies to value diversity, and to value it publicly. A little virtue signaling is fine, as a treat; it may actually repel nasty people, encourage good behavior, or make employees feel more welcome sometimes. That stuff is good.
But there's also a real possibility that a company making diversity an explicit value results in lots of energy going into activities that let that company's executives pat themselves on the back about how good they are without actually doing much for inclusion. I wouldn't take any sizeable company's stated values too seriously, including that one.
On the one hand, yeah, you should respect people who are different from you. On the other hand, this is really so obvious that I doubt elevating it to a “core value” makes much of a difference. Are there marginal people who wouldn’t respect diversity unless it was a core value?
Then again I don’t even know what it means for something to be a core value. What is the practical upshot of “collaboration” being a core value of a company? Were people not collaborating before?
I think "inclusion" is fine as a value. "Diversity" is not, because it is an outcome and not an action one pursues. What matters is that all have equal opportunities to participate, and perfectly fair opportunities can create unequal outcomes through no fault of anyone's. Moreover, I think that fixating on the demographics of who joins the company is morally misguided. I want my teammates to be capable and enjoyable to work with, not to check someone's "we must have X number of minorities checkbox". Diversity initiatives always turn into the latter in my experience.
Basically "screw any part about employees working together do what I say fast". What a shame. I love the AI bros who think utopia is coming, 4 day work weeks, etc. more like "get screwed, work more, for less, in worse environments".
The code and product will turn to shit, and the company won't be able to extract itself from the mud.
Employees tasked with doing 10x more work with less help don't even have to feel bad about it happening. It'll also create employment opportunity in disrupting their old employer.
These companies are willingly signing up to become IBM.
There seems to be a massive push against DEI over the last few years in the tech industry globally, despite it being one of the industry's greatest strength.
How well would the tech industry do if they fired all the autistic people for "not being team players"? How many dev teams are there without at least one furry, trans person, or socially awkward geek?
It isn't enough to continue to dominate the upper rungs of the global economic structure, we must go back to actively sabotaging every other group because when you're used to privilege, equality feels like oppression.
Most DEI programs at big companies ended up setting goals based on things like race and sex. Zealots in HR departments then started implementing programs to change hiring and promotion and compensation to implement progressive identity politics at work, under the DEI label. These things happened in secret, because the companies didn’t like to highlight how being the wrong race or sex means your career is worse off.
That’s totally illegal and discriminatory but companies were not facing consequences for it under the Biden administration. The constant injection of DEI politics all over society - at work, in movies, in ads, etc - led to a backlash and personally I think it is one of the things that led to someone like Trump being re-elected. And this administration is very against DEI ideology. That’s one reason corporations quickly abandoned it - they didn’t want to face legal scrutiny now.
Another is that DEI culture produced no positive results, as expected. Companies already had incentives to hire the best employees they can. If you change that with other incentives thrown in, it’ll make things worse. And ten years after DEI began to appear everywhere, it was obvious it produced no benefit at best, and led to worse teams at worst.
Another reason is simply that a lot of the activists pushing this type of ideology grew out of the activist age group. And I think many of them likely don’t hold those beliefs as strongly anymore. But either way, younger people are different. Especially young males who are more conservative.
All of that and other things has led to DEI being removed or at least de emphasized.
Big Tech CEOs having a front-row seat at Trump's 47 inauguration should give you a decent hint: they bribed the right people, so now they get to enjoy the kickbacks. There's no risk of being regulated to death right now, so there's no need to pretend having the same values the Democrats pretend to have.
Corporate DEI was never real. There's no "push against" it, simply because there was never a genuine push for it. Large companies don't have moral values - if they did their CEOs wouldn't be billionaires.
Wow gitlab. Right when everyone was looking to see if you could lead with all the fails at github, you basically said "We're going to throw our source at ChatGPT and see what happens"
Right? I was seriously considering migrating everything in our company from GitHub to GitLab. Now I'm seriously considering self hosting our git instead.
I don't know if that really solves your problem if the main trunk of development for gitlab is being run through several AI slop machines before they push it to what they call stable, then you download that (or use a debian, redhat package for gitlab which originated from it) and self host on your own machine the results of the AI slop fest.
A lot of the conclusions they're drawing in this post about the "agentic era" seem quite misguided and some don't really seem to make sense.
I have no doubt GitLab has too many employees and can benefit from being a more focused company, but it's tiring reading these layoff posts so chock full of buzzwords. I guess they're desperately hoping if they prognosticate about AI enough it will placate the investors.
Let these people keep betting their companies, futures and net competency on text autocomplete. The future is bright for me and everyone else that isn't falling for it.
> planning to reduce the number of countries by up to 30% where we have small teams
One of the really interesting things about GitLab was that not only did they have employees in a large number of countries but they also published their employee handbook which helped show quite how much work it was to support that:
They even used to have a public payroll.md page detailing how payroll worked in multiple countries - they moved that into their private docs a few years ago but the last public version is here: https://gitlab.com/gitlab-com/content-sites/handbook/-/blob/...
With it’s current AI setup GitLab still couldn’t make anything that could be called great in UX so I can’t wait to see what they can do by eliminating the remaining human factor. Can’t personally wait seeing tickets like these [0] open for months with bots telling you that everything will be alright.
>The agentic era affords GitLab the largest opportunity in our history as a company, and we're making the structural and strategic decisions to meet it
>Operationally, we grew into a shape that was right for the last era and isn't right for this one
To meet their largest opportunity ever, they believe they need less resources. I'm not sure I understand how that follows.
>We're rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs to speed us up
Is this also in the list of "we create code twice as fast and the bottleneck is review so YOLO no bottleneck?". I've yet to see a convincing justification for this. If anything, if you're going full throttle all the more reason to watch the steering wheel, no?
That said, 8 layers of management is a lot of management, and every line of the message seems like leadership truly believes they are sinking in bureaucracy. Let's see how unneeded those 3 layers they're cutting were.
Didn't they do that? Staples only came in as CEO at the end of 2024, and I assume he has been working on a plan to restructure the company since then. Because their financials are not great, and they have been losing money every year since 2019.
GitLab never ceases to amaze me in terms of just how bad their product roadmap is. Practical things like CI improvements are put off over UI rebranding on unicorn colours. Yet, good tooling is exactly why people used to pay for GitLab. For better or worse maybe this finally can change and we can get more customer oriented roadmaps again
While hosting internal services for 4 years, Gitlab was the only service that ran hybrid. Wish they could get their act together and focus on actual engineering again.
If anyone at Gitlab management is reading this; getting your microservices to run fully stateless in a Kubernetes cluster should the #1 goal. No disclaimers about potential risk. It's been 5+ years. Get it together. Stop bolting on minor package management features no one is going to end up using anyways.
>removing up to three layers of management in some functions so leaders are closer to the work.
I wish them the best of luck with that plan. Middle management is where the institutional knowledge sits on how to actually get shit done despite challenges & broken processes/systems.
Middle management exists to turn conflicting marching orders from the directors into less conflicting marching orders for the line workers, and to keep any negative feedback on how fucking stupid the directors are from ever reaching them.
They don't cause the broken processes. They are the symptom of a broken executive process. A fish rots from the head down, and the people at the top get exactly the kind of company that they ask for.
Middle managment is also where most of your negative feedback is lost. I think moving fast in general needs tighter feedback loops and this is simply not possible in large organizations.
Negative feedback is not lost, it's filtered. No one at the top is equipped to deal with the actual feedback from ICs, unless your org is 10 people in a bike shed.
Do you really think that upper management wants feedback that the stupid fucking ideas they have are boneheaded? The point of middle management is to absorb it so it doesn't reach the children at the top and make them feel bad
> Middle management is where the institutional knowledge sits on how to actually get shit done despite challenges & broken processes/systems.
Really? In my experience it's the rank-and-file employees who have this knowledge of how to get on with it without ceremony and politics. And the broken processes and politics are created BY the middle managers.
The fact they can't capitalize on the current trainwreck of GitHub speaks volumes. If they had the right product people would be throwing money at them.
GitLab's old values are for now still listed in their handbook:
> GitLab’s six core values are Collaboration, Results for Customers, Efficiency, Diversity, Inclusion & Belonging, Iteration, and Transparency, and together they spell the CREDIT we give each other by assuming good intent. We react to them with values emoji and they are made actionable below.
Since those terms don't speak for themselves individually, it's worth seeing what they're supposed to mean to get a sense of what GitLab is forsaking now. Each section is actually pretty lengthy, so you should go look and skim for yourself.
> 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.
The problem is that such voluntary separation programs tends to disproportionate attract high performers. You're losing the "10x engineer" who has stuck around because they like being here - despite getting attractive offers from the competition.
The mediocre people who dread looking for a new job during a hidden recession aren't going to leave. They can't afford the risk of not being able to find a new place of employment before the severance pay runs out.
If they were thinking far ahead, they wouldn't need to do any firing at all - they would've gradually adjusted their hiring policy in time to avoid it.
if you don't like the new direction you can leave now and get the known now severance package. All in all, I think it is right to offer people voluntary severence with package when you pull the rug out from under them as far as where they thought they were working.
It's defensible to have a voluntary separation program with clear terms. Microsoft, for example, announced on April 23 that a voluntary separation program would launch on May 7. On that day they announced the precise terms of separation, with affected employees given until June 8 to participate. Perfectly reasonable.
What Gitlab is announcing here is that employees need to apply for a separation, at a yet-to-be-determined time under still-unknown terms, without a guarantee of acceptance, in the next 7 calendar days. Much different and just so much worse.
It just struck me. I always thought I had writing software to fall back on, in case my main gig doesn't work out. I don't think it will still be there when I'm ready to return.
Rather striking statements that have me somewhat concerned:
> Agents open merge requests in parallel, trigger pipelines around the clock, and push commits at a rate no human team ever did. Git itself wasn't designed for that load, and bolting AI onto platforms not built for agents is the biggest mistake of this era. We're doing a generational rebuild of the underlying infrastructure to handle agent-rate work as the default. Git itself is being reengineered for machine scale. The monolith is giving way to modern, API-first, composable services. And agent-specific APIs are being built so agents can act as first-class users of the platform, not as bolted-on consumers of human-shaped interfaces
Is there any broader consensus or information on this? Git doesn't scale? is being rebuilt for agents?! Monoliths are out and services are back? Humans are second class citizens now (human shaped interfaces - bad!!)?
What the hell are they planning to do in there at Gitlab?!
> We're rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs to speed us up, and plan to right-size roles across the company to follow suit.
Ah, yes, finally gitlab will have the same uptime leves as GitHub.
I'd hate to be their customer right now. Is this the only "corporate-scale" forge besides Github?
There's a lot of cool things happening between Gitea/Forgejo, Tangled, and Radical, but I doubt the latter two have any significant usage beyond OSS hobby projects. I'm not sure if the former two do, either.
Having used AI to write code, and seen the bs it outputs half the time, any org speed running to a parallel autonomous unreviewed code base is going to get hit with a massive rude awakening when their cluster f of a codebase melts down.
I was finding this really interesting, that maybe a human had written it and it really reflected a vision for how we build software in this new world. I want to know the way, I'm curious!
Until I got to "One platform, three modes." and my brain just pattern matched "AI slop" and the entire post dissolved into meaningless for me.
I don't know if I can stop my mind reaching this conclusion. I'm sure someone at GitLab made some effort to carefully edit the post... But that it wasn't entirely rooted in a human who'd worked out how this stuff goes, but clearly had lots of AI writing it out... Just made my instinct go "this isn't worth paying attention to after all".
Bleh. I was considering moving to GitLab from GitHub for future IaC work given the latter’s issues of late, but this sends me back to the drawing board.
Funny enough it’s not the agentic pivot or AI injection that’s sending me running, though, but the dropping of DEI from their values. Queer folk are still out here fighting tooth and nail for basic opportunities to put roofs over our heads, PoC still out here getting harassed and harmed by cops, disabled folk still struggling for basic accommodations so they can contribute rather than languish. DEI isn’t something you pick up when the popular movement swings towards it as a method of convenience, it’s a value you have to live by especially when times are tough and countries harass you for it.
I recently switched everything from bitbucket to GitHub mostly just because GitHub is more integrated with the AI tools I use. I feel like they’re probably still pretty big in Europe, but they’re losing in some markets more than before.
>Once approved, our new bonus program will give every team member who isn’t on an incentive compensation plan or bonus plan today, the opportunity to earn a cash bonus based on their individual performance, targeting 10% of salary, awarded at their manager’s discretion.
LOL. So basically buckle up and do what you're told and grind. And hope your manager likes you or you'll get nothing.
“Agents open merge requests in parallel, trigger pipelines around the clock, and push commits at a rate no human team ever did. Git itself wasn't designed for that load .... Git itself is being reengineered for machine scale. The monolith is giving way to modern, API-first, composable services.”
Hmm, does the CEO of — checks notes — “GitLab” know what Git is?
GitHub is publicly destroying itself in a desperate attempt to realize Microsoft's AI dreams, and as its main competitor your response is... to do the same?
Rather than going for a "Humans first, robot assistants welcome" approach which promises to deliver things like stability, reliability, trustworthiness, and human connections, they decide to go all-out on firing the humans and letting bots handle things like code review while explicitly shifting the existing human-first company values towards making the remaining humans responsible for the bot's mistakes.
They could've chosen to market themselves as the sane save haven for the GitHub exodus. Instead they choose to go down in history like Google abolishing "Don't be evil". But hey, I bet chanting "AI! AI! AI!" (albeit quite late to the game) will deliver a very solid lukewarm increase in shareholder value!
I'm no big-city product strategist, but this is what kills me about so many of these "we're pivoting to AI" announcements. Everyone else is doing the same thing (or already had a long time ago--like you said, GitLab is late to the game here), so squeezing yourself into an AI-shaped mold does exactly nothing to differentiate yourself from the competition. And if/when the AI hype machine sputters to a halt, the few companies that didn't do this will suddenly find themselves at an advantage, because they'll have real, actual differentiators to brag about.
Like, I know there are actual reasons and incentives here for the ever-present AI pivot. But I think they're stupid and short-sighted incentives.
How these companies act like these changes are for the better good and how "we are different" is just gross.
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.
Not even the balls to do the deed yourself. This reads like Shrek's "Some of you may die,... but that is a sacrifice I am willing to make."
Can't imagine that slop is going to save them. Gitlab is a totally directionless, beyond self-hosting which I think is commendable, shoddily implemented product. I don't hate it, in that it is at least predictable, but the lack of basically any interesting view on how software should be developed or even look is such a waste.
I tried a self-hosted GitLab on a 64 core beast of a machine with Optane drives. Completely empty of content, there were multi-second delays everywhere. Horrified at what must lurk beneath the façade, I switched to Forgejo, Crow CI and YouTrack and couldn’t be happier.
While there are a lot of little knobs that can tweak performance, it shouldn't be slow out of the box, yet it is the number one complaint about GitLab.
When everyone is leaping head-over-heels into AI / agents, you need SOME part of your stack that is NOT that - slow, tested changes you can (mostly) trust, not "break everything quickly - again" stuff.
Imagine if gcc / clang decided to let agents implement new features without a lot of checking..
It's truly amazing that GitLab has 2,500 employees to begin with when I haven't ever encountered a single company or project using their services, besides one or two obscure open-source project once every few years.
Just today we started a new cycle at work to move from GitHub to Forgejo, its such a refreshing tool... So fast, supports everything we need (and more), and no AI slop. Very happy with our decision
>Software has been the force multiplier behind nearly every business transformation of the last two decades. The constraint was the cost and time of producing and managing it. That constraint is collapsing. As the cost of producing software collapses, demand for it will expand. Last year, the developer platform market used to be measured in tens of dollars per user per month, this year it is hundreds/user/month and headed to thousands. Not only is the value of software for builders increasing, but we believe there will be more software and builders than ever, and we will serve an increasing volume of both.
We've seen these tech waves several times - C and COBOL instead os ASM, CAD/4GL, template generation, Visual Basic and the likes (good old Delphi), Java (which allowed to a lot of mid-inept people to write compilable non-immediately-crashing programs), spread of python, and now AI. Every time we have an expansion of the industry, and every time glorious promises which get delivered on modestly. The point here is that they get delivered on.
And with AI i suppose it will be similar, though much better than before. In those previous waves human brain was the limit. This time we throw that limit away from the start - nobody will be able to comprehend the sheer amount of AI-generated code. Yes, that approach will hit some limit down the road of course too...
I have no doubt that AI is making some programmers quite a bit more productive. But if it is even 10% as good as all the marketing claims, we should be seeing an explosion of new tech startups, and a huge increase in feature shipping rate and number of bugs closed. Why isn't this obviously happening? Where's the next Dotcom Boom or Cloud SaaS Explosion?
What I am seeing instead is million-line AI slop pet projects whose sole "user" is its developer, and large companies falling over each other to enshittify their products. If there's no genuine user value being delivered, who's going to pay for those thousand-dollar-per-month developer tools?
>Where's the next Dotcom Boom or Cloud SaaS Explosion?
i see it isn't your first rodeo :) So, in Dotcom the companies needed huge financing for hardware and those money were the main limiter, in Cloud SaaS era small teams with relatively small financing mostly for salaries were able to deliver large - AirBnb, Uber, WhasApp, ... - and the employees, their brain abilities and their ability to work together were the main limiter. Now with AI we don't have these limiters. I'd say the slopped up Claude Code and OpenClaw are the examples of the new wave which is just starting.
>large companies falling over each other to enshittify their products.
Oh, yes, each wave the software is even more sh.tty than before, and this time i think we're really in for a shock to our imagination of how sh.tty it can get. All these datacenters here and later in space would need some slop to churn through :)
My bet is that we'd not have a software as a static set of bits existing for more than one execution. I think we'll have Just-In-Time software. An ephemeral one. It will be generated on the fly for specific task and discarded after. That will keep those datacenters busy at least for some time.
TLDR: 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.
New values: Speed with Quality, Ownership Mindset, Customer Outcomes.
In other words, work harder, not smarter, and no more DEI.
The ball is right there, bouncing alone in front of the goal, and they just have to position themselves as "we're the stable ones" to score that market when the exodus inevitably happens.
Nope, full throttle and stimulants, just because.
So many things they could be doing, to make people buy into their services. For example they could simply run campaigns about how they promise to never use customer and user repositories for AI training. Or they could show better uptime statistics. Their CI language is better than Github's too.
If anyone gave me a choice between Gitlab and Github, I would go with Gitlab. But if I had additionally the choice to use Codeberg, I would choose that.
Maybe they are just not looking to grow. If they made such a statement, that would actually be a pleasant surprise. No hunger for "infinite exponential growth", just to impress investors? Great! That's a fat plus in my book!
I understand the meaning, however, in that they're well positioned by having the company name and domain name, same general way that non-technical people will pay wordpress.com to host their blog/small website because it's very easy, rather than DIYing it or paying a 3rd party.
"Editions There are three editions of GitLab:
GitLab Community Edition (CE) is available freely under the MIT Expat license. GitLab Enterprise Edition (EE) includes extra features that are more useful for organizations with more than 100 users. To use EE and get official support please become a subscriber. JiHu Edition (JH) tailored specifically for the Chinese market."
Personal opinion, but I think a great deal of the people who are presently overloading github with one person created vibe coded projects would be just fine with the "CE" feature set.
Having been in some of these values meetings, I really imagine it went like this: someone wanted speed, and someone else wanted quality. Sorry, I mean Speed and Quality. Many people said there is a tradeoff between those two things, and only one thing can be first.
Some brilliant businessman: "I know, we'll combine them. We want Speed _and_ Quality."
Every IC ought to use the present day as the opportunity to build a nimble competitor to their old employer (or whatever industry incumbents they want).
They're literally setting themselves up for this.
GitHub is already the main platform for random open-source projects, and that's unlikely to change any time soon. GitLab's selling point is essentially "Github, but not by Github". They would do Just Fine offering a highly-restricted free account for the handful of hobbyists who care enough about leaving GH but don't care enough to go to Forgejo & friends and for the people doing evaluations, offering free credits to the few high-profile FLOSS projects who accidentally end up on GL-the-SaaS instead of self-hosted GL, and for the rest just focusing on paid corporate customers.
Every company I've worked at hammers the "ownership" idea and I hate it so much. It's how they drive a culture where employees are expected to invest themselves into "owning" a problem space that can be taken from them at any moment. It's how they trick you into doing extra work that's not in your job description.
Unless you're ACTUALLY an owner, don't be fooled by an "ownership" value.
It's the norm at Big Tech these days. Directors and VPs take all the glory if it goes well while ICs, team leads, and people managers get all of the blame if it doesn't. When the charlatans get exposed, they bounce on to the next company with their charlatan friends. Rinse and repeat while swapping RSUs for index funds, retire with >$10m before 50. If we stopped allowing this to work in our industry, it wouldn't be such a common thing. Unfortunately, with how everything is these days, these people are getting hired on vibes and bravado.
The part I'd missed was that as middle management he didnt have any real authority himself... you live and you learn I guess.
All the responsibility is still yours though.
One must really wonder, if they ever try to hear themselves talking or read their own prose. Maybe they do, but simply don't care at all?
It doesn't make sense for it to be 40% of their values, especially if they're losing money (or very close to it).
I am not sure if you had implied it but that would align with my experience as well: places that tout diversity were the worst places to work (as someone who is seen as 'diverse') while the ones that treated everyone the same and had the expectation everyone pulls their weight.
I absolutely despise people treating me differently because of who / what I am rather than doing good work. I will take mildly inappropriate good-nature jokes over head pats every day of the week.
(Saying this as a strong advocate for diversity and inclusion, lest there's confusion)
Of course, its statistically most likely that any individual would belong to the much larger latter group but statistically like that only apply to other people, right?
Worse, its a zero step thinkers solution. Step zero is a merit based system, step one is for the people with motels on Boardwalk and Park Place to ensure they can never lose again by rigging the system to ignore merit in favor of capital.
Someone I'm close to is going through this right now. They work at a place that officially highly values "inclusion", and their employer's website is dripping with virtue-signaling language related to it. But that someone is disabled, and in fact there's nobody at the organization who owns accessibility issues. Disability accommodations are haphazard, and often not timely. Why? Because no one owns them. They just get punted to an internal employee affinity group of disabled people who don't have a real chain of command, a real budget, or even a real prerogative to do accessibility work, let alone meaningful power— many of its members are routinely chastised by their bosses whenever they dedicate any time to solving access problems within the company. "That's not what we pay your for", "that's not your job", "I need you on this other thing", etc.
Meanwhile the organization receives public accolades from meaningless business press organization as a "great place to work" or even "great place to work for people with disabilities".
I think it's fine for companies to value diversity, and to value it publicly. A little virtue signaling is fine, as a treat; it may actually repel nasty people, encourage good behavior, or make employees feel more welcome sometimes. That stuff is good.
But there's also a real possibility that a company making diversity an explicit value results in lots of energy going into activities that let that company's executives pat themselves on the back about how good they are without actually doing much for inclusion. I wouldn't take any sizeable company's stated values too seriously, including that one.
Then again I don’t even know what it means for something to be a core value. What is the practical upshot of “collaboration” being a core value of a company? Were people not collaborating before?
Employees tasked with doing 10x more work with less help don't even have to feel bad about it happening. It'll also create employment opportunity in disrupting their old employer.
These companies are willingly signing up to become IBM.
Does anyone know what caused this?
Fragile white male ego
It isn't enough to continue to dominate the upper rungs of the global economic structure, we must go back to actively sabotaging every other group because when you're used to privilege, equality feels like oppression.
That’s totally illegal and discriminatory but companies were not facing consequences for it under the Biden administration. The constant injection of DEI politics all over society - at work, in movies, in ads, etc - led to a backlash and personally I think it is one of the things that led to someone like Trump being re-elected. And this administration is very against DEI ideology. That’s one reason corporations quickly abandoned it - they didn’t want to face legal scrutiny now.
Another is that DEI culture produced no positive results, as expected. Companies already had incentives to hire the best employees they can. If you change that with other incentives thrown in, it’ll make things worse. And ten years after DEI began to appear everywhere, it was obvious it produced no benefit at best, and led to worse teams at worst.
Another reason is simply that a lot of the activists pushing this type of ideology grew out of the activist age group. And I think many of them likely don’t hold those beliefs as strongly anymore. But either way, younger people are different. Especially young males who are more conservative.
All of that and other things has led to DEI being removed or at least de emphasized.
Corporate DEI was never real. There's no "push against" it, simply because there was never a genuine push for it. Large companies don't have moral values - if they did their CEOs wouldn't be billionaires.
I have no doubt GitLab has too many employees and can benefit from being a more focused company, but it's tiring reading these layoff posts so chock full of buzzwords. I guess they're desperately hoping if they prognosticate about AI enough it will placate the investors.
One of the really interesting things about GitLab was that not only did they have employees in a large number of countries but they also published their employee handbook which helped show quite how much work it was to support that:
https://handbook.gitlab.com/handbook/people-group/employment... lists 18 countries right now. I guess they're losing 5 of those.
Here's a permalink to the current version of that page https://gitlab.com/gitlab-com/content-sites/handbook/-/blob/... since it mentions that "Diversity, Inclusion & Belonging is one of our core values" and so is likely to be updated pretty soon!
They even used to have a public payroll.md page detailing how payroll worked in multiple countries - they moved that into their private docs a few years ago but the last public version is here: https://gitlab.com/gitlab-com/content-sites/handbook/-/blob/...
[0] https://gitlab.com/gitlab-org/gitlab/-/work_items/588806
>The agentic era affords GitLab the largest opportunity in our history as a company, and we're making the structural and strategic decisions to meet it
>Operationally, we grew into a shape that was right for the last era and isn't right for this one
To meet their largest opportunity ever, they believe they need less resources. I'm not sure I understand how that follows.
>We're rewiring internal processes with AI agents, automating the reviews, approvals, and handoffs to speed us up
Is this also in the list of "we create code twice as fast and the bottleneck is review so YOLO no bottleneck?". I've yet to see a convincing justification for this. If anything, if you're going full throttle all the more reason to watch the steering wheel, no?
That said, 8 layers of management is a lot of management, and every line of the message seems like leadership truly believes they are sinking in bureaucracy. Let's see how unneeded those 3 layers they're cutting were.
Seems like a fair assessment. Maybe they should start by getting rid of the people who put that structure in place?
At gitlabs team size, that means every manager has 2-3 reports? Yeah, I'd be cutting layers too.
If anyone at Gitlab management is reading this; getting your microservices to run fully stateless in a Kubernetes cluster should the #1 goal. No disclaimers about potential risk. It's been 5+ years. Get it together. Stop bolting on minor package management features no one is going to end up using anyways.
I wish them the best of luck with that plan. Middle management is where the institutional knowledge sits on how to actually get shit done despite challenges & broken processes/systems.
It's an even worse plan than eliminating juniors.
They don't cause the broken processes. They are the symptom of a broken executive process. A fish rots from the head down, and the people at the top get exactly the kind of company that they ask for.
Really? In my experience it's the rank-and-file employees who have this knowledge of how to get on with it without ceremony and politics. And the broken processes and politics are created BY the middle managers.
Yes, letting some LLMs "plan, code, review, deploy" will for sure improve quality and depth of innovation you ship.
Yeah, sure. A couple of years ago it was Covid overhiring.
You know the one thing that is never ever going to be given as a reason for layoffs? The growing salary-productivity gap.
Could someone explain it?
If you have a lot of new stuff to build, and if you're not currently losing money, why start a new initiative with a layoff?
> GitLab’s six core values are Collaboration, Results for Customers, Efficiency, Diversity, Inclusion & Belonging, Iteration, and Transparency, and together they spell the CREDIT we give each other by assuming good intent. We react to them with values emoji and they are made actionable below.
Since those terms don't speak for themselves individually, it's worth seeing what they're supposed to mean to get a sense of what GitLab is forsaking now. Each section is actually pretty lengthy, so you should go look and skim for yourself.
Here's the page: https://handbook.gitlab.com/handbook/values/
And here's an archive from yesterday, for when that changes: https://web.archive.org/web/20260510150031/https://handbook....
> 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.
The mediocre people who dread looking for a new job during a hidden recession aren't going to leave. They can't afford the risk of not being able to find a new place of employment before the severance pay runs out.
Neither of these groups are valuing long term expertise
What Gitlab is announcing here is that employees need to apply for a separation, at a yet-to-be-determined time under still-unknown terms, without a guarantee of acceptance, in the next 7 calendar days. Much different and just so much worse.
Plenty of time to whip up a dead man's switch.
https://handbook.gitlab.com/handbook/values/
> Agents open merge requests in parallel, trigger pipelines around the clock, and push commits at a rate no human team ever did. Git itself wasn't designed for that load, and bolting AI onto platforms not built for agents is the biggest mistake of this era. We're doing a generational rebuild of the underlying infrastructure to handle agent-rate work as the default. Git itself is being reengineered for machine scale. The monolith is giving way to modern, API-first, composable services. And agent-specific APIs are being built so agents can act as first-class users of the platform, not as bolted-on consumers of human-shaped interfaces
Is there any broader consensus or information on this? Git doesn't scale? is being rebuilt for agents?! Monoliths are out and services are back? Humans are second class citizens now (human shaped interfaces - bad!!)?
What the hell are they planning to do in there at Gitlab?!
Ah, yes, finally gitlab will have the same uptime leves as GitHub.
There's a lot of cool things happening between Gitea/Forgejo, Tangled, and Radical, but I doubt the latter two have any significant usage beyond OSS hobby projects. I'm not sure if the former two do, either.
Until I got to "One platform, three modes." and my brain just pattern matched "AI slop" and the entire post dissolved into meaningless for me.
I don't know if I can stop my mind reaching this conclusion. I'm sure someone at GitLab made some effort to carefully edit the post... But that it wasn't entirely rooted in a human who'd worked out how this stuff goes, but clearly had lots of AI writing it out... Just made my instinct go "this isn't worth paying attention to after all".
Funny enough it’s not the agentic pivot or AI injection that’s sending me running, though, but the dropping of DEI from their values. Queer folk are still out here fighting tooth and nail for basic opportunities to put roofs over our heads, PoC still out here getting harassed and harmed by cops, disabled folk still struggling for basic accommodations so they can contribute rather than languish. DEI isn’t something you pick up when the popular movement swings towards it as a method of convenience, it’s a value you have to live by especially when times are tough and countries harass you for it.
Fuck you, GitLab.
>Once approved, our new bonus program will give every team member who isn’t on an incentive compensation plan or bonus plan today, the opportunity to earn a cash bonus based on their individual performance, targeting 10% of salary, awarded at their manager’s discretion.
LOL. So basically buckle up and do what you're told and grind. And hope your manager likes you or you'll get nothing.
Aside, none of these announcements even attempt to make sense.
GitLab's TAM is exploding, demand is through the roof, LLM tooling is making each IC more productive, and to capatalize on this moment GitLab is
... "transparently restructuring" by asking employees to quit so they don't have to lay off as many...
Hmm, does the CEO of — checks notes — “GitLab” know what Git is?
GitHub is publicly destroying itself in a desperate attempt to realize Microsoft's AI dreams, and as its main competitor your response is... to do the same?
Rather than going for a "Humans first, robot assistants welcome" approach which promises to deliver things like stability, reliability, trustworthiness, and human connections, they decide to go all-out on firing the humans and letting bots handle things like code review while explicitly shifting the existing human-first company values towards making the remaining humans responsible for the bot's mistakes.
They could've chosen to market themselves as the sane save haven for the GitHub exodus. Instead they choose to go down in history like Google abolishing "Don't be evil". But hey, I bet chanting "AI! AI! AI!" (albeit quite late to the game) will deliver a very solid lukewarm increase in shareholder value!
Like, I know there are actual reasons and incentives here for the ever-present AI pivot. But I think they're stupid and short-sighted incentives.
"Act 2" for crying out loud, get out of town.
If I had any inkling of giving GitLab a try, this killed it.
I think you need to explain it like it’s a bash script else I don’t think you understand it.
(Ironically I don’t think if this article was the prompt, I don’t think an agent would code it up the way you are thinking)
It's Ruby, which is pretty horrific but still I think there was probably something not quite right in your setup because it isn't normally that slow.
Imagine if gcc / clang decided to let agents implement new features without a lot of checking..
almost like a copy of my post :) https://news.ycombinator.com/item?id=47982975
We've seen these tech waves several times - C and COBOL instead os ASM, CAD/4GL, template generation, Visual Basic and the likes (good old Delphi), Java (which allowed to a lot of mid-inept people to write compilable non-immediately-crashing programs), spread of python, and now AI. Every time we have an expansion of the industry, and every time glorious promises which get delivered on modestly. The point here is that they get delivered on.
And with AI i suppose it will be similar, though much better than before. In those previous waves human brain was the limit. This time we throw that limit away from the start - nobody will be able to comprehend the sheer amount of AI-generated code. Yes, that approach will hit some limit down the road of course too...
... so where's the delivery?
I have no doubt that AI is making some programmers quite a bit more productive. But if it is even 10% as good as all the marketing claims, we should be seeing an explosion of new tech startups, and a huge increase in feature shipping rate and number of bugs closed. Why isn't this obviously happening? Where's the next Dotcom Boom or Cloud SaaS Explosion?
What I am seeing instead is million-line AI slop pet projects whose sole "user" is its developer, and large companies falling over each other to enshittify their products. If there's no genuine user value being delivered, who's going to pay for those thousand-dollar-per-month developer tools?
i see it isn't your first rodeo :) So, in Dotcom the companies needed huge financing for hardware and those money were the main limiter, in Cloud SaaS era small teams with relatively small financing mostly for salaries were able to deliver large - AirBnb, Uber, WhasApp, ... - and the employees, their brain abilities and their ability to work together were the main limiter. Now with AI we don't have these limiters. I'd say the slopped up Claude Code and OpenClaw are the examples of the new wave which is just starting.
>large companies falling over each other to enshittify their products.
Oh, yes, each wave the software is even more sh.tty than before, and this time i think we're really in for a shock to our imagination of how sh.tty it can get. All these datacenters here and later in space would need some slop to churn through :)
My bet is that we'd not have a software as a static set of bits existing for more than one execution. I think we'll have Just-In-Time software. An ephemeral one. It will be generated on the fly for specific task and discarded after. That will keep those datacenters busy at least for some time.