A recent post on Hacker News sparked debate about corporate software‑engineering roles. The author, a veteran of several FAANG firms, argues that most positions reward performative actions over real delivery. He notes that teams spend time on tasks that impress management while a handful of high‑performers push the project forward for their customers and the company.

The author criticizes the prevalence of one‑to‑one meetings that add little value. He describes them as calendar slots that serve more as status checks than collaborative problem‑solving. This practice, he claims, drains time from coding and hinders progress, leaving developers feeling demoralized by office staff who pretend to be engineers in their daily work and career trajectories in the industry.

These observations highlight a mismatch between corporate incentives and engineering output. When recognition hinges on visible rituals rather than tangible results, teams risk stagnation. The discussion invites leaders to rethink performance metrics and prioritize actual code quality, customer impact, and cross‑functional collaboration over superficial achievements in tech organizations that value innovation and product delivery above status signals and visibility today.