Live data from Hacker News

GitLab announces workforce reduction and end of their CREDIT values

about.gitlab.com

621–630 of 750 posts

Re: GitLab announces workforce reduction and end of their CREDIT values

#621
post #196

https://www.google.com/search?q=gitlab+stock shows their stock price was ~$52 a year ago and is $26 today, so down 50% in 12 months. It's quite possible this is because they weren't making enough noise about their AI strategy. If investor fears are that AI makes GitLab's business less valuable, including this in their "GitLab Act 2" announcement makes a whole lot of sense: > The agentic era multiplies demand for soft…

Down almost 15% now. Investors hate the CEO's buzzword bingo slop.

Re: GitLab announces workforce reduction and end of their CREDIT values

#622
post #310

> 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 Two big red flags here. First git itself is distributed an…

Git is not designed to handle 1000s of clones and merges to a single repo in minute scale even.

Sure, you are right. Git allows you to keep distributed state and eventually reconcile that.

Customers are trying to do that at absurd human scales right now without AI. Git itself is a bottleneck for large enterprises with large repositories and large CI configurations.

It may be hard to believe but it’s true.

Re: GitLab announces workforce reduction and end of their CREDIT values

#624

GitLab could be the perfect case study on AI-powered efficiency improvements. I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old that was just being shuffled around by managers adding and removing random labels. Surely with all of these ridiculous developer productivity gains enabled by AI, they should finally be able to fix a…

Dunno how it is these days, but that reads like Android roughly 2012-2020. I once found a looooong bug report thread on their issue tracker 7ish years old that had all the usual waves of promises that a fix might make the next release, then silence, then repeat, and the usual challenges to the bug’s status every time a release happened, plus it saw community members correctly diagnose the problem in the first couple…

I no longer care, thankfully, however for several years the Android NDK felt like it was a 20% project from someone on the team.

Re: GitLab announces workforce reduction and end of their CREDIT values

#625

Earlier quoted context omitted.

Whats right with it? Its slow, large, excessively complex and not that resilient to failure. You either want a bunch of NFS machines backed on to ZFS on nvme, with a central jumping off point that allows sharding (this is critical to allow one or more NFS server to fuck up and not kill access to everything else.) Or, pay the money and use GPFS

As someone who's in charge of close to an exabyte on Ceph, I couldn't disagree with you more. Done correctly, Ceph is extremely reliable, resilient, and fast. Once you get over the initial learning curve, dare I say, even a joy to work with.

I concur, even though I have only used it as a hobbyist.

Re: GitLab announces workforce reduction and end of their CREDIT values

#626
post #504

Earlier quoted context omitted.

Not even deterministic autocomplete.

Good job a handful of companies aren’t investing a trillion+ dollars in that. Can you imagine how silly they’d look when everyone realised.

"Everyone is doing it ⇒ it must be right." See also: bloodletting, leaded gasoline and parachute pants.

Re: GitLab announces workforce reduction and end of their CREDIT values

#627
post #280

Earlier quoted context omitted.

Yeah doesn't make sense. My guess is they are doing this to prep for an acquisition. Probably by an AI company or Datadog or similar.

That's exactly what's happening here.

Yeah, didn't see til after I commented, but this CEO ran this same playbook with New Relic. Layoffs and then sold the company 2 months later.

I think Staples is a guy you bring in to sell the company, not run the company.

Re: GitLab announces workforce reduction and end of their CREDIT values

#628

GitLab could be the perfect case study on AI-powered efficiency improvements. I have never interacted with a piece of software that, for every single problem I found, there was an open issue always at least 4-7 years old that was just being shuffled around by managers adding and removing random labels. Surely with all of these ridiculous developer productivity gains enabled by AI, they should finally be able to fix a…

maybe the 'microservices' approach + agentic coding (self directed agents) that have agency to pick up old tickets, open merge requests with maybe a human in the loop will fix all that.

that's the story being sold.

I don't buy it.

Re: GitLab announces workforce reduction and end of their CREDIT values

#629
post #81

Earlier quoted context omitted.

8 layers of management??? At gitlabs team size, that means every manager has 2-3 reports? Yeah, I'd be cutting layers too.

https://handbook.gitlab.com/handbook/company/structure/ > GitLab has at most eight layers in the company structure (Associate/Intermediate/Senior, Manager/Staff, Senior Manager/Principal, Director/Distinguished, Senior Director, VP/Fellow, Executives, Board). > [...] You can skip layers but you generally never have someone reporting to the same layer (Example of a VP reporting to a VP). So they're counting the board…

this is the typical layer at a big tech co.

you can simply cut out so many layers of management & coordination tax & remain with a leaner organization.

Re: GitLab announces workforce reduction and end of their CREDIT values

#630
post #589

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

I actually like GitLab's new UI, but their frontend is far too laggy given its complexity, especially since most of their pages are actually server-side rendered. It doesn't help that they use a weird combination of Vue 2 and jQuery in their codebase. I think that as a corporation promoting the use of AI, they should actually be AI users themselves . They should just rewrite that laggy UI in Svelte, Solid, or even va…

web-components & vanillaJS will solve their slow UI.
Post reply on HN