I’ve found that whenever I’m bumping heads with a tricky problem, doing something else completely different, is usually what lets me solve it. Sometimes you need “crunch time” but often it’s more productive to take some off time instead. Have you noticed anything similar?
you want to get to a point where you know, your your machine, your org is self-sufficient enough that you know, you just need to occasionally tap the blimp, make sure that things are working. You can course correct if it's not, but that frees you up to then focus on the next important sets of problems that the org needs to, you know, tackle heads on.
what makes the GAWA theory such an interesting example is you have um literally this 100-year segment of like an idea that like flows through many different people's heads before it like settles into something that the math community like agrees is good.
I think the most tricky thing people run into is how should you put together your data structures? I mean for your code you can mostly do the same things as you can in other languages. I mean that's not entirely true but the big thing is really the data structures.
It's more that for myself, the process of writing is the way how I figure things out. And figuring things out is really my goal here. So, I'm I'm trying to figure it out in my own heads, and for that I just have to write it myself.
Um DRAM gets released goes to AI chips who are willing to do longer term contracts, willing to pay higher margins, etc., etc. because at the end of the day, the margin that they extract is much larger from the end user or whatever. Um, and so this this this probably leads to like people hating AI even more, right?
I don’t think executives who take off and work 40-hour weeks should be telling anybody to stay late. I think that’s wrong and immoral. But to me as an individual, as long as I’m not telling other people to do it, my life’s work is my passion and I want to do it as much as possible.
the reason that I think this is kind of tricky is quite subtle. And it's the fact that anytime you use an LLM to assign a reward, those LLMs are giant things with billions of parameters and they're gameable.
the current situation in Iran shows that even if an "IAEA for AI" is necessary for some purposes, it won't be sufficient for resolving the tricky geopolitical issues raised by AI.
Code and data is hard, but ideas is easy. Silicon Valley operates on the way that top employees get bought out by other companies for a pay raise, and a large reason why these companies do this is to bring ideas with them.
"It’s honest in how it covers topics like navigating tricky power dynamics with CEOs, surviving 'peer panic,' dealing with competition within leadership teams, and in its overall breadth and depth."
So what he concluded was that he called remembering an imaginative construction, meaning that we don’t replay the past, we imagine how the past could have been by taking bits and pieces that come up in our heads.
Remember space and time are parts of one unified space-time, the location of the singularity in the black hole is not the middle of space, but our future. It is a moment of time. It is like a big crunch.
While we love GraphQL for many use cases, implementing a secure and performant GraphQL API can be tricky and there is a definite cost to requiring it during early prototyping of your app.
The problem is, when humans went bipedal, our pelvises got smaller, and as humans got smarter, our heads got bigger. So evolution had to get creative. Its solution: all human babies would be premies, born when they were still small enough to pass through a human pelvis.
As the title suggests, this offers a highly pictorial introduction to complex analysis. I would not use this as the only text to learn about complex analysis, but Needham does a marvelous job of conveying the beauty of the subject, with numerous helpful intuitions for otherwise famously tricky ideas.
In any case, I think we need to not only look at the incentives facing scientists, but also those facing department heads, journals, and grant-making agencies.
Podcast. Another classic manifesto from Jason Fried and DHH, challenging the status quo of business today. Properly sparkled with both “fuck”s and wisdom. Fuck 50 or 80-hour work weeks, the always stressed, always anxious way of working, constant crunch. Let’s all calm down. It doesn’t have to be crazy at work.
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.