Skip to content

Update cs-fde-super-day.mdx#2806

Open
leonardwolters wants to merge 1 commit intomainfrom
leonardwolters-patch-4
Open

Update cs-fde-super-day.mdx#2806
leonardwolters wants to merge 1 commit intomainfrom
leonardwolters-patch-4

Conversation

@leonardwolters
Copy link
Copy Markdown
Collaborator

No description provided.

@vercel
Copy link
Copy Markdown

vercel Bot commented Apr 14, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
langfuse-docs Ready Ready Preview, Comment Apr 14, 2026 5:59pm

Request Review

@dosubot dosubot Bot added the size:XS This PR changes 0-9 lines, ignoring generated files. label Apr 14, 2026
@github-actions
Copy link
Copy Markdown

@claude review

Comment on lines 1 to 11
---
title: CS and FDE Super Day
description: CS and FDE Super Day interview process at Langfuse.
title: Forward Deployed Engineering Super Day
description: FDE Super Day interview process at Langfuse.
---

import { Badge } from "@/components/ui/badge";

# CS and Forward Deployed Engineering Super Day
# Forward Deployed Engineering Super Day

The Super Day is a full onsite day in our office where we work together with you on real problems you might tackle in your future role at Langfuse. The goal is to simulate working together for a day—a trial run for both sides to determine whether we enjoy collaborating, coding, and problem-solving together. Here is an overview on [how we work](/handbook/how-we-work/principles) as a team.

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 The PR removes "CS and" from the title and H1 heading, but the document body still contains two stale CS references: the preparation sub-heading still reads "CS and Forward Deployed Engineers:" and the afternoon session still says "We discuss Langfuse's CS/FDE strategy". These should be updated (or removed) to match the new FDE-only framing of the page title.

Extended reasoning...

What the bug is: The PR performs a partial rename — the frontmatter title, frontmatter description, and H1 heading were all updated to remove "CS and", but two occurrences in the document body were overlooked.

Specific locations:

  1. In the Preparation section, the role-specific bullet sub-heading still reads "CS and Forward Deployed Engineers:" (visible in the file around line 26 of the rendered document).
  2. In the Afternoon Session section, the description reads: "We discuss Langfuse's CS/FDE strategy" — retaining the "CS/" prefix that was removed everywhere else.

Why existing content doesn't prevent it: The edits were straightforward find-and-replace style changes in the frontmatter and H1, but the body content uses slightly different wording ("CS and Forward Deployed Engineers" vs. the title's "CS and FDE") and was not caught in the same pass.

Impact: An FDE candidate navigating to the "Forward Deployed Engineering Super Day" page will encounter a preparation checklist explicitly addressed to "CS and Forward Deployed Engineers" and an afternoon session framed around "CS/FDE strategy". This is confusing and suggests CS and FDE are combined audiences, contradicting the new FDE-only page title. If the intent is a clean split (CS gets its own page), readers will be misled.

How to fix: Update the preparation sub-heading from "CS and Forward Deployed Engineers:" to "Forward Deployed Engineers:" (or just remove the role-specific qualifier if it applies to everyone). Update the afternoon session text from "We discuss Langfuse's CS/FDE strategy" to "We discuss Langfuse's FDE strategy" (or equivalent FDE-only phrasing).

Step-by-step proof:

  1. Before this PR, the title was "CS and FDE Super Day" — consistent with body content referencing CS roles.
  2. This PR changes the title to "Forward Deployed Engineering Super Day", signaling a CS-free document.
  3. A reader clicks the new FDE-only link and lands on the page.
  4. Under "Preparation", they see "CS and Forward Deployed Engineers:" — they wonder if this page is actually for both roles.
  5. Under "Afternoon Session", they read about "CS/FDE strategy" — again suggesting this is a combined CS+FDE document.
  6. The inconsistency leaves the document's audience ambiguous despite the title's clear FDE-only intent.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs size:XS This PR changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant