The Engineering Manager

Controlling for age would bias the sample. A random sample is a random sample. Gravidity is calculated over the woman's entire history. Age is irrelevant except for the fact here that we know the older women had lower gravidity which means they were pregnant fewer times over their whole life. [1]

The simple fact is the women with more time to get pregnant, who had the injections, were pregnant less than women who did not get the injections who had less time to get pregnant. Halving pregnancy rate over the life time is some major birth control via 15 minute medical appointment.

Additionally, the amount of sex had by younger people has been on the decline. While that is not mentioned, it would be one more parameter working against the injections.

Here's an article on the mental model called inversion, which is about avoiding stupidity. [2] [3]

"If going down route a in the dark in the rain is correlated with traffic accidents, take route b, regardless of the fact that one's super tires or eagle eyesight might supposedly negate causation."

The same reality holds up at scale, and not just at the one clinic, but they retracted it for political reasons. [4]

1. https://nurseslabs.com/gtpal-guide-to-gravidity-and-parity-in-obstetrics/

2. https://fs.blog/inversion/

3. https://www.theengineeringmanager.com/growth/invert-always-invert/

4. https://pubmed.ncbi.nlm.nih.gov/29889622/

Some random thoughts:

1)

Depending on where you live, there will be hundreds/thousands of new CS graduates every year, but a smaller number of available jobs for juniors.

So, you need to differentiate yourself from the rest.

Starting from there, there are two paths you can follow to increase your chances of finding a good job (not mutually exclusive):

- Do what everyone does, but better.

- Do different things then everyone

2)

First principles thinking.

It has been an invaluable thinking method for me to improve myself, in all areas of life.

Some random links:

https://jamesclear.com/first-principles

https://www.theengineeringmanager.com/growth/first-principles-and-asking-why/

Some examples on how you can apply it to software development:

- You will be using various languages/frameworks/libraries when creating software, with various level of abstractions. At the beginning, you won't have the necessary experience to understand how everything works underneath. Whenever you find time, try to dig through the abstractions to discover why they were built the way they built, how they work together. This understanding will make you a better engineer.

- When working with non-technical clients/project shareholders, what they say they want and what they really want will usually be different. Often, you will have to dig through their requests to find out how you should continue.

>I am of course talking from a moralist and empathical perspective.

Speaking from a business and engineering perspective, I'd be surprised if (even in an ideal world with no environmental externalities or exploited third-world labourers) the cost of the raw resources, shipping and e-waste processing were a significant part of that $1.

We're literally talking about something 1/16 the size of a postage stamp that gets stamped into a similarly tiny plastic shell.

From my admittedly "peak mount stupid"[1] position as an engineer that uses these things, I'd suspect that the biggest contributors to that $1 figure come from the expert labour required to both R&D the chips as well as run the machines that manufacture them.

[1] http://theengineeringmanager.com/wp-content/uploads/2017/12/20111228.gif

Newsletters
http://levelup.thekua.com/
https://softwareleadweekly.com/
http://www.techmanagerweekly.com/
https://wherewithall.com/

Blogs
https://randsinrepose.com/
https://blog.pragmaticengineer.com/
https://www.theengineeringmanager.com/
https://www.askamanager.org/
https://increment.com/
https://devtomanager.com/

Conference
https://theleaddeveloper.com/

Other Resources
http://lenareinhard.com/engineering-management-reads/
https://github.com/LappleApple/awesome-leading-and-managing

Previously: Best book / resources on leadership, especially for tech teams?
https://news.ycombinator.com/item?id=21712194