Hacker Newsnew | past | comments | ask | show | jobs | submit | motxilo's commentslogin

You allude to the difference between requirements and constraints. What you say is true, but also it's true that the Therac-25 was not designed to not output high power when an operator typed quickly.


This sounds to me like the tech version of QAnon.


Being a Staff Engineer vs just Senior gives you more leeway for negotiation with prospective employers.


"Quiet: The Power of Introverts in a World That Can't Stop Talking" by Susan Cain. This book made me think about my own thinking and social behavior patterns.


In the article, it mentions "In any case, the majority of people are on a spectrum of introversion to extroversion.".


C'mon, don't you guys be so nitpicky... The comment above was made in the context of financial places, and is clearly referring to the "City" of London, as they call the financial hub, not the "City of London" as a whole.


I am only responding because I didn't know what "the City" means because I don't work in the financial sector


Yes, way better and using a humble tone, e.g. "Introverts are not smarter than extroverts. According to IQ scores, the two types are equally intelligent. And on many kinds of tasks, particularly those performed under time or social pressure or involving multitasking, extroverts do better."


Good postmortems should be created for human-induced errors or top-down decision to cut costs. Especially for those.


You don't need a post-mortem when you already know what the problem was.


If you knew what the problem was before the outage happened, and didn't consciously put the effort to prevent it, then oh well, that's professional negligence. Maybe not on you because you may not have the decision power to apply large-scale changes, but definitely somebody within the company. And if you didn't know what caused the outage, and you conducted some type of investigation to get at the heart of the problem, then you need a postmortem.

That's one of the main goals of a postmortem: document what the cause of the problem was, not just for you, but for all interested parties. If some human caused the issue, you need to document what happened and what should be done to prevent it from re-occurring. And fix it, of course.


Can't we all just assume from now on that anything bad that happens is because of some shitty CEO cost-cutting everything to line their pockets? Because 99% of the time that's what's happening.


Same here but s/used book store/amazon/.


I like the browsing atmosphere of the small bookstore. Also I find it hard to get past all the titles that are currently being hyped if I go to amazon. I read more old books than I do new ones. But if I have a title in mind that I want to buy right away, amazon is my first stop


Blindsight (Watts)

Between the World and Me (Coates)

Economics in One Lesson (Hazlitt)

Corporate Confidential: 50 Secrets Your Company Doesn't Want You to Know---and What to Do About Them (Shapiro)

Los últimos españoles de Mauthausen (Hernández de Miguel)

Distributed Systems for Fun and Profit (Takada)

The Knowledge: How to Rebuild Civilization in the Aftermath of a Cataclysm (Dartnell)

Historia mínima de España (Fusi)

Turn the Ship Around!: A True Story of Turning Followers into Leaders (Marquet)

What I Learned Losing A Million Dollars (Moynihan)

Site Reliability Engineering: How Google Runs Production Systems (Google)

Adventures in Human Being: A Grand Tour from the Cranium to the Calcaneum (Francis)

Operating Systems: Three Easy Pieces (Arpaci-Dusseau)


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: