759 karma · joined March 24, 2020
The point the author makes is that sometimes you are not in control of those projects. Therefore "letting them fail" seems a false choice constructed by the author.
A better title "You don't know what other people are doing and you don't know why unless it is your job to do so."
IMO, especially when one has snacks fully stocked, it's easy to 'forget' that you ate something.
One big breakthrough for me was reading Arnold S. "encyclopedia of body building". There's a lot of physiological tips and also very practical advice.
I'm sure you can get it from anywhere, but for me this was a big change. Sizing the reps, the workouts, the weights helped a lot in trying to make progress. Additionally endomorphic bodies need different excercise and I was doing too much ineffective cardio for months with few results.
Weights changed my results within a few weeks.
for everyone who says "i've tried etc doesnt work" all i would say is, possibly if you dont have the time due to kids etc.
Otherwise, get to it!
Cranberry's & nut mix - 34g (total) have 8g of protein
1 cup of milk - roughly 8g of protein
This is a pretty light breakfast of 16g of protein. How about a 'big, bold breakfast':
2 eggs - 12 g of protein
4 bacon strips - 12 g of protein
1 cup of hash browns - 3 g of protein
(other carbs pancakes etc going to have < 1g of protein)
So in the 'big, bold breakfast' => 27 g of proteins, I would be 3g behind my daily, average protein intake for the morning.
2 hamburgers for lunch, that's 30g of protein, keeping me close to my daily, average protein intake for lunch.
8 oz steak for dinner, thats 56g of protein.
In total: 27+30+56 = 112g of protein, just 4 g over needed daily, average intake of protein.
Resisting the sarcasm, this is not reasonable.
[1] Perkins https://perkinsmenus.com/hearty-mans-combo/#:~:text=Two%20eg...
"high scores: braised eye-of-round steak 40.62; broiled t-bone steak (porterhouse) 32.11; grilled lean steak 31.0 " numbers are grams per hundred grams or wiki also reports 25% as the average, thus your factor of 2 error in weight (400 instead of 200).
Sincerely,
You-cannot-read-or-convert-units-or-gather-info-correctly
https://en.wikipedia.org/wiki/List_of_foods_by_protein_conte...
1.2g/kg * 90kg (~200lbs-lean) = 108g of protein.
each person, on average, in the US would be eating one 16oz steak or 3-5 hamburgers every day.
1. Listen to what other people say and what they think the problem is, or what the problem "says".
2. Think, ask questions to clarify and repeat step 1. Is the problem actually technical? branch a. otherwise branch b.
a. have you considered the problem is mostly not technical? then proceed to branch b.
b. what miscommunications are keeping the solution from being implemented?
3. Change minds with the words that are convincing to others. Dont be so convinced of your solution that you wouldnt take a better one, return to step 1 unless the problem is "solved"
My blog would be uncompellingly short.
In some ways the technology companies, which such large growth, are their own consumers.
Unless they feel pressure from another growth story or a technical monetary effect, and I emphasize story because its about future returns, its unlikely.
Additionally this has grown so quickly that there is amazing talent being applied to these problems, its hard to imagine every good person has been sufficiently compensated that progress will stall.
It's one of my main arguments against a crash: why would one (1) or a few choose to do that?
I don't know what success looks like but it's probably fair to say they were over-extended by roughly 30-40%.
https://chainstoreage.com/kroger-pay-350-million-automation-...
sometimes volume and total $ are not the same.
Fields up to 1mSv/hr have been detected and signs placed at >0.5mSv/hr locations inside the region[0].
[0] linked article [1] https://www.ans.org/news/article-7429/indonesia-begins-worki...
However having high quality documentation that is easily accessible is always the first step, and if there are information there that are important it is _much_ more likely it will be known.
It is not "a much less of a deal" as you say, it is a pretty big deal for a global product that billions of people touch.
Images produced from SPECT cameras have been around for a while. [2]
This is potentially a 16 pixel "camera" which the "image" is a gaussian blob (Figure 1e and 5e) [1].
This is interesting for a variety of reasons but is way overblown in the "camera" or "image" context. It's demonstration that one can make pixelated devices (4x4) of a specific kind of promising material.
[1]https://www.nature.com/articles/s41467-025-63400-7
[2]https://en.wikipedia.org/wiki/Single-photon_emission_compute...
Fixing the incentives might, however funding comes from very few places and they have their own incentives => lobbied goals or profit-motivated.
One might argue that money is a prioritization method.
I'd argue that having one metric (amount of money) makes you susceptible to single-metric problems: optimization of everything to the point of meaninglessness, critical dependence on the stability of that metric's underlying present & future value.
Defects in the currently implemented financial system (exploitable by evolving technologies) might lead to larger systematic failures and less robustness.
My experience is that incentives within the two are converging: monetization drives all activities.
Higher ed is allowing professors to slump teaching responsibilities - as it has for many years - in favor of high-flying research. What is new is that now: entire departments struggle to find chairs or people to run basic functions at teaching or research levels. Professors are rarely on campus except at the bare minimum and are largely diverting resources (people & research) to their companies.
Synchronous logic does imply some syncing and yielding could be a way to sync - which is what i expect you mean.
Asynchronous logic is concurrent without sync or yield.
Concurrency and asynchronous logic do not exist - in real form - in von Neumann machines
If a publisher was so inclined, I have like 20 or so of these breakdowns that I would like to put into a (<75pg) book. The goal would be 1-3 page distillations of events for broad appeal. 1 page for the introduction and impact of the event, 1-2 pages for summarization and conceptual distillation.
The goal is a somewhat reductive but sharply results-focused perspective on these events.
1. boeing and spirit both work on planes
2. damaged rivets discovered and lots of back and forth to get them repaired. boeing does the doors and spirit does the rivets.
3. rework on rivets needed door plug to be removed, someone at boeing (who is not onsite) sees that the door plug needs to be removed, escalates this request but notes that work must wait for the next week because the only door person who is qualified to remove plugs is on leave.
4. door manager - on the day of the plug removal - de-escalates the door plug removal request. later that day the door manager, door master and three door crew enter area near the fuselage & door plug - correct documentation of removal not generated and none of them were trained to remove door plug. No one knows who removed the plug.
5. a boeing technician moves a stand that has what he believed to be a door plug bolt on top of it. he "strapped it and let it hang" to the fuselage.
6. Spirit indicates plug was removed and reworks rivets
7. No one checks the door plug was reinstalled correctly
best advice i can give is stay razor focused on the goals - and what allows you to achieve them:
1. don't lie to yourself about the utility of the project - nice to haves are not need to haves - almost every idea is bad and few are good and even fewer are good enough to spend 5 years on, and vanishingly small amounts of them are goldmines (see #4)
2. understand what provides true value - treat it with respect and only allow it to be known, if necessary, & carefully present it when necessary so that others understand its value. if _they_ don't understand the value - they wont pay for it and will not care, you have to speak _their_ language and not burn too much time doing it.
3. be kind to yourself & enjoy life while you're chasing the goals - you need close relationships and satisfaction to sustain you and keep you from ruining yourself.
4. look for lucky opportunities & take them.