Visiting Us

Original Article ↗ Hacker News Discussion ↗

Technology stack & MUMPS

  • Epic still relies heavily on MUMPS for its core database and backend, with higher-level dialects and frameworks transpiled down to it.
  • Frontends and newer components are largely C#/.NET, TypeScript/React, mobile platforms, plus Python/SQL for analytics.
  • Some commenters who dug into the transpiled MUMPS say modern usage is far removed from the horror stories in older articles, though the language’s skills are still seen as non-transferable outside health IT.

No-acquisition philosophy & company structure

  • A recent podcast episode reignited interest in Epic’s unusual structure: privately held, no IPO, no M&A, and a legal structure designed to prevent sale or reverse takeovers.
  • Supporters argue this enables long-term product focus, avoids integration patchworks like some competitors, and reassures customers they won’t be bounced between owners or squeezed by Wall Street.
  • Critics note this also entrenches a single leader’s power and reduces external accountability.

Product experience & industry role

  • Patients are generally enthusiastic about MyChart, calling it the best portal they’ve used.
  • Many clinicians and nurses in the thread dislike Epic, describing heavy data entry, convoluted UIs, and poor fit for non‑US health systems; Norway and Finland rollouts are cited as scandals.
  • Despite criticism, several say Epic is still better than rival EHRs, and that integration, regulation, and certification requirements make disruption extremely hard.

Work culture, hiring, and training

  • Strong split opinions: some portray Epic as exploitative with long hours (especially in Technical/Implementation Services), aggressive non-competes, anti-remote stance, and burnout; others report 40-hour weeks, solid pay for Madison, and valuable early-career training.
  • Epic is known for hiring many fresh grads from Midwest schools into non-SWE technical roles and investing months in structured training. Many see it as an “early-career transit hub.”

Code quality & internal practices

  • Former devs describe MUMPS codebases with weak ownership, huge complex functions, and defensive accretion of branches.
  • Others praise strong testing, design-doc culture, internal tools (custom code review, PM, time logging on their own DB), and a strong sense of quality and accountability.

Campus, location, and branding

  • The Verona campus is widely described as spectacular, whimsical, and “Disneyland-like,” with cow-themed transport and even live cows.
  • Some love the environment; others find it artificial and note that a nice place to visit doesn’t guarantee a good place to spend years.