GitLab announces workforce reduction and end of their CREDIT values

Original Article ↗ Hacker News Discussion ↗

GitLab’s announcement of major layoffs, a shift away from its long‑promoted “CREDIT” values, and a pivot toward AI‑driven “agentic” software development is drawing sharp scrutiny. Commenters see the move as financially motivated and heavy on AI buzzwords, worry that dropping values like Diversity and Transparency signals a retreat from earlier cultural commitments, and question plans to automate code review and internal processes with agents. Many also criticize GitLab’s product direction and performance, arguing the company is missing a chance to differentiate itself from GitHub and are weighing alternatives such as Forgejo, Codeberg or self‑hosting.

Layoffs and “voluntary separation” process

  • Many see the staged process (voluntary separation window, decisions by June 1) as maximizing anxiety instead of “ripping off the band‑aid.”
  • The voluntary program is criticized for unclear terms and lack of guaranteed acceptance; some contrast it unfavorably with clearer programs at other firms.
  • Several argue high performers are most likely to take voluntary packages, leaving risk‑averse or weaker performers behind.
  • Most commenters assume the driver is financial/stock pressure, with AI used as a narrative cover.

AI / “agentic era” strategy

  • The memo’s AI framing (“agents plan, code, review, deploy”) is widely viewed as buzzword‑heavy and investor‑oriented rather than grounded in current reality.
  • Some argue AI tools are useful but fundamentally next‑token predictors akin to “autocomplete,” and unsuited to unreviewed code or process approvals at scale.
  • Others push back, noting tool calling, agents, and real productivity gains in practice, but still see overpromising.
  • Many fear quality and reliability will deteriorate if AI code review and automation replace human oversight.

Shift in values: DEI, transparency, ownership

  • Dropping CREDIT values (especially Diversity, Inclusion & Belonging and Transparency) and replacing them with “Speed with Quality, Ownership Mindset, Customer Outcomes” is interpreted as:
    • Less emphasis on employee well‑being and inclusion.
    • More pressure to work faster with individual “ownership” but little real authority.
  • DEI removal triggers a long debate: some see DEI as performative and bureaucratic; others see it as a proven business strength now being abandoned for political or legal reasons.
  • Loss of “Transparency” is read as a signal that open handbooks and issue discussion may shrink.

Org structure and middle management

  • Cutting up to three layers of management divides opinion:
    • Some say GitLab had excessive layers (up to eight) and too many non‑coding managers.
    • Others argue middle management carries critical institutional knowledge and acts as a buffer against poor top‑level decisions.

Product, infrastructure, and market position

  • Several report GitLab as slow, complex, and overly focused on UI changes and AI features over long‑standing usability and issue backlog.
  • The claim that “Git is being reengineered for machine scale” is seen as vague and concerning; unclear whether this means Git the VCS or only GitLab’s infrastructure.
  • Some think GitLab is squandering a chance to differentiate from a struggling GitHub by also going “all‑in on AI” instead of emphasizing stability and human‑centric workflows.

Alternatives and self‑hosting

  • Many mention moving or planning to move to Forgejo, Codeberg, Gitea, or self‑hosted Git as reactions to both GitHub instability and GitLab’s new direction.