If every uh software engineer knew to watch out for false serial dependency chains, things where they were creating series of dependent operations that could not be optimized away or other sorts of architectural problems like that that cannot be easily fixed, then the world would look more like just wait and optimize the hotspot, right?
When you look at these investigations, the reason this happens is, you know, these are very responsible, very intelligent parents who will, you know, put their child in the car and then get in the car and then you just get in this mode of I'm going to work. I'm going to do my job and you're in this routine.
it’s also true that their impact on our output was never as tremendous or as clear-cut as that of prior innovations, such as the steam engine or the power loom, and that integrating them effectively into the workforce took a long time
Overall, I'm loving the M4 Max so far, and I've noticed that it does handle certain tasks such as running Pest PHP tests about twice as fast sometimes as the M1 Pro did, which is nice.
Excessive manufacturing requirements are a pervasive problem, especially in the field of cell and gene therapy and they are killing countless of promising medicines before they ever reach patients.
Yeah, I think the biggest bottleneck is compute and for that the longest lead time supply chains are not power or data centers. They're actually the semiconductor supply chain themselves, right? It switches back from being power and data center uh as a major bottleneck to chips.
I think computing supply chains are much easier to monitor than nuclear ones - there is only one TSMC and one ASML, but there are nine and maybe soon ten nuclear powers
But my point is that this is still not the reason (or is only a very small reason) why these goods from China are cheaper than elsewhere. The main driver of lower labour costs has been automation; not having a human worker at all.
And the trick here is not to act too much on the feedback that the very disappointed people are giving you because they already love your product. Also, not to act at all really on the feedback that the not disappointed people are giving you because they're so far from loving your product that they are essentially a lost cause. but to focus on the segment of the somewhat disappointed people.
What I’m saying is that art requires making choices at every scale; the countless small-scale choices made during implementation are just as important to the final product as the few large-scale choices made during the conception.
And for a long time, I thought that's what had worked. That this was why Ruby on Rails took off, became one of the most popular full-stack web frameworks of all time, inspired countless clones, and created hundreds of billions in enterprise value for companies built on it. But I was wrong. It wasn't the crusade that did it.
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.