proomt

Search

Search posts, papers, and topics

All posts

Hacker News front pageBen Stolovitz10 min readintro

Reasons I didn't become an EMT, ranked

Read on stolovitz.comHN 240·114 comments

Summary

The author, a software engineer, finally earned an EMT license after a month‑long, $5k wilderness course, describing the time, cost, cultural, and logistical hurdles that delayed him. He argues the skills and experience are valuable even if you never ride an ambulance, but the path isn’t trivial.

  • A month‑long, $5k EMT course can be taken if your employer offers unlimited vacation and you can afford travel.
  • Volunteer EMS slots are easier to find outside major cities; large metros often have only paid staff.
  • EMS culture can be frat‑like and challenging for women, affecting recruitment and retention.
  • EMT certification gives practical medical skills (CPR, AED, oxygen) useful even without regular ambulance work.

Engineers weighing side‑certifications or volunteer roles need a realistic view of the time, cost, and cultural factors involved.

5/10
careerhealthcarevolunteeringwork life balanceems

Related reading

  1. So You Think You Could Be an Electrician?

    The article argues that the popular narrative that trades now out‑earn college graduates is misleading: college still offers a wage premium, while trades carry higher injury risk and steep entry barriers. It also cautions that AI is unlikely to make trades “AI‑proof” because automation tends to bypass manual dexterity rather than enhance it.

    Hacker News front pageasteriskmag.com11 minHN463425

  2. Teach Yourself Programming in Ten Years

    The essay argues that becoming a competent programmer takes roughly ten years (about 10,000 hours) of deliberate practice, not the quick crash‑course promises. It offers concrete habits—regular coding, peer interaction, diverse language exposure, and real project work—to sustain long‑term growth.

    Hall of Famenorvig.com12 minHN586302

  4. One Month Without AI

    The author spent a month relying on AI code‑generation agents at work, finding that it increased context‑switching, eroded code understanding, and added hidden token costs, ultimately slowing delivery. After quitting AI and returning to TDD, he regained control, code quality, and personal productivity.

    Hacker News front pagebustikiller.com10 minHN187227lobste.rs97

  5. Non Cogito, Ergo Quid Sum?

    The essay argues that LLMs are already outperforming human programmers and rapidly becoming cheaper, which could render software engineers obsolete. It warns of societal consequences and doubts that handcrafted code will retain premium value.

    Yegor Bugayenkoyegor256.com5 min

  6. Why I'm still bearish on LLMs after Navier-Stokes

    The author argues that despite headline successes (e.g., Navier‑Stokes proof, security exploits), current frontier LLMs still require heavy human oversight and rigorous specifications that are costly to produce. Reward‑hacking, narrow generalization, and the need for domain‑expert spec writing limit autonomous deployment to only a few niche domains (high‑failure‑cost work, tightly defined tasks,…

    Hacker News front pagedank.systems5 minHN487644lobste.rs49