So basically they are saying: do not code here because we are letting machines code... nice.
GitLab announces workforce reduction and end of their CREDIT values
501–510 of 750 posts
Re: GitLab announces workforce reduction and end of their CREDIT values
#502Earlier quoted context omitted.
> To believe that first you would have to ignore tool calling, ReAct loops, and the whole agent feature. That would be silly. How? It all still functions with text prediction
> It all still functions with text prediction Wilful ignorance can't be fixed. As the saying goes, you can lead a horse to water but you can't make it drink. I can point you to ReAct loops and tool-calling and agent-based systems. If after being pointed those you still choose to be stuck on the "it's just text prediction" then that's a problem you are creating for yourself, and only you can get unstuck on a problem o…
> I can point you to ReAct loops and tool-calling and agent-based systems.
Those literally work with text prediction.
If you take the text prediction out of it, nothing happens.
You stick a harness around a text predictor which then triggers the text predictor.
If you think I am missing something then please do point it out.
Re: GitLab announces workforce reduction and end of their CREDIT values
#503Earlier quoted context omitted.
“But they’ve added RL so…!!!” You are obviously right and I see examples of it everywhere. E.g I asked Claude opus 4.7 (the latest/greatest) the other day “is a Rimworld year 60 days?”. The reply (paraphrased) “No, a Rimworld year is 4 seasons each of 15 days which is 60 days total”. Equally, it gets confused about what is a mod or vanilla since it is just predicting based on what it read on forums, which are clearly…
Maybe there was more in the context before that question? I just copy-pasted that question into Opus 4.7 and it replied: Yes. A RimWorld year is 60 days, split into four 15-day quadrums (Aprimay, Jugust, Septober, Decembary), each corresponding to a season.
[deleted]
Re: GitLab announces workforce reduction and end of their CREDIT values
#504Earlier quoted context omitted.
Maybe there was more in the context before that question? I just copy-pasted that question into Opus 4.7 and it replied: Yes. A RimWorld year is 60 days, split into four 15-day quadrums (Aprimay, Jugust, Septober, Decembary), each corresponding to a season.
And that is the reason why it is only autocomplete. You probably had less context than the poster before, so it could not mix stuff up. The poster before either had more memory or the search searched through more topics. And btw it’s really hard to only give access to some things.
Not even deterministic autocomplete.
Re: GitLab announces workforce reduction and end of their CREDIT values
#505Earlier quoted context omitted.
They have 2800 employees with 5-10 reports per manager.
Mathematically that would work out to a lot less than 8 layers of management. I wonder if they have 5-10 employees per manager at the bottom of the org chart, but a lot of middle managers and manager-like titles mixed through the middle.
[deleted]
Re: GitLab announces workforce reduction and end of their CREDIT values
#506Lots of interesting information here: >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 re…
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 of directors as a layer above the CEO.
I'm speculating, but they probably also have an unbalanced tree - you'll often see the IT security chief reporting directly to the CEO (because it's important to keep on top of, and they need authority to do their job) but only having 50 people below them in the org chart.
In some corporations you also sometimes get almost-nonexistent ranks created to smooth over a reorganisation. If a level 5 bureaucrat decides to merge the departments of two of their level 4 bureaucrats, they could demote one of them. Or they could make one into a level 4.5 bureaucrat.
Re: GitLab announces workforce reduction and end of their CREDIT values
#507Earlier quoted context omitted.
Yeah they all want to fire the guys who can make sense of the mess the vibe coders are doing and try to stop it. It will be interesting in the next few years. Assuming we won't be in the 3rd world war thanks to the USA and will have much bigger concerns.
> Yeah they all want to fire the guys who can make sense of the mess the vibe coders are doing and try to stop it. You're grossly inflating the level of contribution from your average software developer. Are we supposed to believe that the same people who generated the high volume of mess that plagues legacy systems are now somehow suddenly exemplary craftsmen? Also, it takes a huge volume of wilful ignorance and sel…
I've seen which developers became vibecoders. They were the people I'd have wished to get rid of.
The ones who never acknowledge a mistake even if the process is crashing; the ones who put "return true" in a test so that the test doesn't execute and will insist that you broke their code if you remove the return true and when the test actually runs it fails; the ones who read a blog post about some new thing and decide we need to do like that; the ones who will write code that fails and then be nowhere to be seen when there is customer support to do.
Re: GitLab announces workforce reduction and end of their CREDIT values
#508Wow 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 just look at the pricing and really start thinking about is it really multi hundred euro a year per seat product... Frankly as consumer those pricing levels just seems like distanced from reality.
Re: GitLab announces workforce reduction and end of their CREDIT values
#509Earlier quoted context omitted.
I couldn't disagree more. "predictions made about one's neighbour scale downwards in accuracy relative to increased cultural diversity"? I feel like this is just a fancy way of saying that you're uncomfortable with people being different from you. The social tension you're describing is in your own head. Even the article you're citing doesn't even agree with what you're saying.
your post is an ad hominem without substance to back the personal accusations within. i said there were arguments both in favor of and against diversity. the article i posted showed arguments both in favor of and against diversity. obviously some contradictions will present when looking at both sides. diverse, millenia old, genetically encoded behavioural structures exist in our shared reality. id love to discuss thi…
Human populations dont share enough genes when they do share culture for this argument to make sense, people identifying as X culture but with Y genetics don't magically act like Y - saying "genetically encoded behavioral structures" is usually just code for "black people are dumber than white people" so you should understand why people are assuming bad faith.
Re: GitLab announces workforce reduction and end of their CREDIT values
#510Earlier quoted context omitted.
> To believe that first you would have to ignore tool calling, ReAct loops, and the whole agent feature. That would be silly. How? It all still functions with text prediction
> It all still functions with text prediction Wilful ignorance can't be fixed. As the saying goes, you can lead a horse to water but you can't make it drink. I can point you to ReAct loops and tool-calling and agent-based systems. If after being pointed those you still choose to be stuck on the "it's just text prediction" then that's a problem you are creating for yourself, and only you can get unstuck on a problem o…
[deleted]