Earlier quoted context omitted.
> you say suck it fascist in response to DEI being removed, Re-read the thread. They made a joke about acronyms.
initial comment - 'gitlab no more dei' secondary comment - 'suck it fascist' third comment - 'fascism and communism would both get rid of dei' whereabouts did the room get misread?
GitLab announces workforce reduction and end of their CREDIT values
531–540 of 750 posts
Re: GitLab announces workforce reduction and end of their CREDIT values
#532Earlier quoted context omitted.
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.
Can you imagine how silly they’d look when everyone realised.
Re: GitLab announces workforce reduction and end of their CREDIT values
#533GitLab 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…
What hope slop-maker-users have then?
Re: GitLab announces workforce reduction and end of their CREDIT values
#534Their old CREDIT values: Collaboration, Results for Customers, Efficiency, Diversity, Inclusion & Belonging, Iteration, and Transparency. New values: Speed with Quality, Ownership Mindset, Customer Outcomes. In other words, work harder, not smarter, and no more DEI.
is there a company that has kept DEI?
Re: GitLab announces workforce reduction and end of their CREDIT values
#535Users want a product that delivers the value they are looking for, VCs are looking for infinite AI scale, these do not meet. So founders need to present two different values and visions, one for customers and one for VCs.
In a small early stage company you can pretty easily hide each side from the other so you can deliver value to your customers while dancing the VC dance, but as you get larger its harder.
I think founders will endure and VCs will calm down at some point, but there is going to be some suffering along the way.
Oh and have you heard that they built Cluade code with only 20 people? (ignore 12 years of AI research expertise head-start and that Anthropic now has thousands of developers)
Re: GitLab announces workforce reduction and end of their CREDIT values
#536Earlier quoted context omitted.
Your comment was also completion.
This retort doesn't make any sense. Take humanity back perhaps 40k years ago and language did not even yet exist. Our token base was 0. Put an LLM in that scenario and it will endlessly cycle on nothing and produce nothing, stuck in a snapshot in time. Put humans in that situation, and soon enough you get us. This is like saying that somebody speaking Chinese is just playing the Chinese Room [1] experiment. The only…
This is not quite accurate. The human lips, throat etc have evolved to be better at producing speech, which indicates that it's not that recent. And that it was a factor in the success of groups who could do it better than others.
It likely started "no later than 150,000 to 200,000 years ago."
sources:
https://en.wikipedia.org/wiki/Origin_of_speech#Evolution_of_...
Re: GitLab announces workforce reduction and end of their CREDIT values
#537Earlier 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. 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 decid…
Trying to portray everyone who ever used a tool as the incompetent cohort is an exercise in self-delusion.
Re: GitLab announces workforce reduction and end of their CREDIT values
#538Uh, if this is what I think it means, I wouldn't trust using a product where their company thinks that approvals for reviews can be automated.
Re: GitLab announces workforce reduction and end of their CREDIT values
#539Earlier 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…
>> 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 of your own making.
Woof, you're sounding mighty aggressive for someone with such a fundamental misunderstanding of the technology you are defending. Have you ever even actually implemented a system around an LLM, or do practice ~~voodoo~~ "prompt engineering"?
> I can point you to ReAct loops and tool-calling and agent-based systems.
Those are all implemented - quite literally - by parsing the *text* that the LLM *autocompletes* from the prompt.
Tool calling? The model emits JSON as it autocompletes the prompt, and the json is then parsed out and transformed into an HTTP call. The response is then appended to the ongoing prompt, and the LLM is called again to *autocomplete* more output.
"ReAct loops" and "agent based systems" are the same goddamn thing. You submit a prompt and parse the output. You can wrap it up in as many layers as you want but autocomplete with some additional parsing on the output is still fucking autocomplete.
If you're going to make such strong assertions, you should understand the technology underneath or you'll come off looking like a idiot.
Re: GitLab announces workforce reduction and end of their CREDIT values
#540GitLab 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…
I'm certain that if they would start doing that, without a proper strategy / workflow when it comes to QA, it will be GitHub reloaded. You'll be able to watch the decline in real-time.
Has any of the companies who went all in on AI gotten better at their job because they went all in on AI?