If you observe people in their daily work, you will see there are many reasons why people do not document things. Time constraints, incentive structures, liability, general trade-offs and ambiguities. This is true not just in software/engineering but in any line of professional work.

There's plenty of grandstanding about the importance of documentation, but not much interest in understanding why people don't document in the first place.

Anyone can pat themselves on the back for pointing to the worlds problems and saying "this could be better!"

> You're in the awkward position of arguing that an expert in a field doesn't understand what she is doing while citing evidence to support yourself that you (by construction) don't have.

No. I'm in the non-awkward position of arguing that non-experts should be careful about interpreting a single case study without context. Especially in a way that implies miracle cancer cures are sitting around in labs with no one paying any attention to them.

I don't think the average HN reader understands just how many wildly different treatments, drugs and therapies are being thrown at different cancers and how quickly medical oncology moves as a field. Cancers are an extremely complex family of diseases. Early results and case studies are correspondingly extremely difficult to interpret due to the variation in individual responses and disease course.

The existence of a "miracle" cancer treatment is almost ruled out from first principles. But if such a miracle treatment is sitting around in a lab, it would be non-trivial to tell it apart from the thousands of other promising candidate therapies that go on to pan out to nothing.

There's no shortage of cancer patients at end-of-life stage undergoing aggressive treatments and/or experimental therapies in clinical trials for minimal to no survival benefit. For almost all of these patients, the best option for them and their loved ones will end up having been a palliative or best supportive care model.

And because her outcome was so unexpected and unusual it got published as a case study. What you don't see are all the cases where the experimental miracle cure treatment did not work. What you also won't see in headlines are all the trials where putative miracle cures and other promising treatments failed to demonstrate survival benefits in larger cohorts than 1.

One of the counterintuitive things about cancer is how badly individual cases and responses to treatment generalize to the broader patient population. If you didn't know any better, you could easily read a story like this and think "wow, this breast cancer cure was just stuck in a lab somewhere!" But to put a story like this into context, you need to understand just how many individual miracle remission stories there are, and how varied individual cancers and responses to treatment are.

There are potential miracle cures almost everywhere, and a large number of them are being aggressively researched, tested on cancer patients at any given time - often as part of combination therapies. Some of these promising technologies do become breakthrough cancer treatments that create durable remissions, such as checkpoint inhibitors. The rest fizzle out.

This isn't a case study about a breast cancer cure. This is a story about a single individual's cancer's response to an experimental treatment. For comparison, there are case studies of spontaneous remission in refractory cancers triggered by seasonal flu.

Virologists aren't sitting around waiting to develop cancer before they decide to roll out the miracle cancer cures. Oncolytic viruses have been researched, studied and tested on cancer patients for almost a century now.

1. The interaction between oncolytic virotherapy and host immunity is complex. Consider that oncolytic viruses are also targeted by the immune system.

2. Oncolytic viruses that directly destroy cancer cells may not depend on a host immune response at all for therapeutic effectiveness.

3. There are many common chemotherapy agents that enhance anti-tumor immunity. For example, 5FU is understood to enhance anti-tumor response and activate the p53 pathway.

4. Immunosuppressive chemotherapies can still enhance anti-tumor immunity by changing the tumor microenvironment. This is one of the principles behind combined chemo-immunotherapy regimes in treatment of solid tumors.

5. Some immune cells promote tumor growth and suppress anti-tumor immunity. Tumor associated myeloid cells are one example of an immune cell suppressed by chemotherapy that promote tumor survival.

This is just scratching the surface of some of the complexities here. In general, cancer and cancer treatment are incredibly complex with massive variation not just between types of cancer but within individual cancers themselves. Oncology does not lend itself to simplistic thinking.

It's more of a "not even wrong" statement. It's the kind of useless and reductive analysis poor leaders trot out from a position of personal frustration after failing to surmount the challenges involved in steering a complex, messy, human institution towards success.

It's incredible how consistently this maladaptive "everyone just work harder!!" mentality crops up among failed leadership in institutions of all kinds and sizes. In this respect, Schmidt is no different to the average frustrated restaurant owner, blaming his business failures on his staff's work ethic, "no one wants to work hard these days" and other copes.

Let's say we go ahead and assume that long grinds and 100% in-office attendance is the only way a successful and highly engaged team can look. Getting to that point would still require leadership to perform the actual hard work of creating the right conditions and incentives for that successful, engaged work to emerge. Shaking your fists at the air and saying "work harder people! we need to win!" doesn't cut it.

If Schmidt allowed himself to look more closely and reflect more deeply, he would realize that Google is and was full of extremely hard workers. But their "hard work" more likely took the form of navigating Google's political structures and chasing up internal promotions and prestige.

I'm not overreacting. There are many people who will read my comment and know exactly what I'm talking about. This is simply a "you get it or you don't" situation where you're currently on the "doesn't get it" side.

Long-term sufferers of RA - and the people in their support networks - know first-hand that RA is a complex and progressive condition that requires some pretty hardcore medical interventions to manage. Like other auto-immune diseases, different people will experience different disease courses. A very small few will be lucky enough that their disease goes into remission for no clear reason. Others will try everything under the sun only to see their disease become worse and worse. The reality for sufferers is that there aren't quick fixes and simple triggers.

It's reasonable to expect that general lifestyle interventions such as healthier diet and the right type of exercise regime may improve symptoms within the margins permitted by the underlying disease process. But promoting content that centers the role of "lifestyle" once RA has already developed only trivializes the disease and widens the empathy gap that sufferers already face.

At this point, I have to assume that being out-of-touch is deliberate branding from OpenAI. Maybe to appeal to equally out-of-touch investors.

IANAL but it's actually not that simple. There are laws and precedents around soundalikes.

I think the cultural defense for this is really lame. Was there really cultural value in evoking "Her"? Because outside of the narcissistic male nerd culture of laughing at your own jokes, and fixating on your own cleverness, there doesn't seem to be. No one outside of this bubble actually thinks it's super cool and culturally valuable for tech companies to attempt reinvent - seemingly without a trace of irony or self-awareness - the cautionary tales and trappings of dystopian sci-fi.

From what I have seen, the demos struck the average person as cringey and left women in particular with a deep sense of revulsion.

Having frameworks that allow more devs to do more things means correspondingly that more people can be hired for those things with less training. In this respect, there is an obvious overlap between employer and developer interests.

Take MongoDB from the article. IME the biggest advocates for MongoDB are not managers (who barely have any idea what it is). It's developers who just want an "easy" way to store data that corresponds closely to the JSON document format they are used to, and doesn't force them to think about "annoying" and "outdated" things like relational modeling, joins and schema migrations.

If fungibility and lowest common denominator hiring drove the popularity of dev tools, then .NET and Angular would be ruling the roost.

None of the ideas here stand up to scrutiny. For example, Angular with its more opinionated design and framework approach was a much better choice for regularizing developer effort and making devs fungible. But by all accounts it lost to React, which is frequently criticized in comparison for allowing too much individual variation in development style.

React itself has become increasingly more complex over the years as it's moved up the S curve and the design direction is driven towards more and more remote parts of the problem space. More than ever, it requires specialized knowledge to use correctly.

Svelte - of which the author is a fan - fits his thesis much more than React. Svelte is billed as simpler and easier to learn and use than React, without requiring developers to wrap their heads around concepts like hooks, reducers and suspense.