rice, grains, seeds and potatoes all used to be peasant foods And the kings actually just ate a lot of fresh meat like beef, venison, wild boar, swan, and peacock, and imported fruits and spices like saffron, cinnamon, nutmeg, and pepper A king's diet was high in protein A peasant's diet was low in protein
Fruit Pig are one of the few black pudding producers at scale who use fresh blood - most black pudding these days is made with dried blood imported from Europe.
a cybernetic machine can nail the task and completely miss the job. coding makes this very very easy to see because the tasks are so legible (and verifiable!): write the function, migrate the API, fix the tests.
we've both come to believe that when transformation fails repeatedly, it's time for something different, and one of the tools that leaders need to add to their tool belts (and probably use a lot more frequently than they do today), is starting fresh, creating new entities (agencies and departments, for example) and either endowing them with new authorities or transferring authorities from legacy institutions to the new ones.
I think this is kind of leads to another way that Rust really helps with reliability, which is that if you're refactoring, I think Rust is really good at telling you all the places you need to update. I've done this sometimes where I would refactor something. I change the code. I change the return type or whatever it is, and then I just fix the compiler errors and until the compiler stops shouting. And then once I've done that, I've updated every place I need to update.
I look at um the talent base and I think it is best for us to create opportunity for people to keep on growing with fresh new challenges within the company because if we don't do that they would leave the company
So the question is how do I refactor all the abstractions so that I'm not I have to arrange it once and hit go. The name of the game is how can you get more agents running for longer periods of time without your involvement doing stuff on your behalf?
filmmakers Robert Kenner and Melissa Robledo reunite with investigative authors Michael Pollan and Eric Schlosser to take a fresh look at our efficient yet vulnerable food system.
go fire up your browser. Do it in incognito. Go to your app and do everything with a fresh Gmail address. Try support. See how your support is. Try to contact sales.
I first read it in college and recently, as we approach this milestone, decided to re-read it and was amazed about how fresh and vivid it felt, as well as how nuanced and humane it is.
I started using PHPStorm last year and I love it. I honestly don't know how I managed to live without it. It makes it a breeze to refactor a large codebase or source dive some vendor code.
Legacy code has no test and is not written to be testable. Touching it this sphaghetti code somewhere breaks the system. And to refactor safely, we'd need to have tests first... but where to start? This book gives practical suggestions
A fresh take on navigating the tech the interview process, tailored for frontend engineers. She wrote the book after she found Cracking the Coding Interview to be too Java/backend-focused. The book comes with 1, 2 and 4-week learning plans as well. A great book to start with.
a new relationship is like fresh powder. It is new and shiny and exciting but it will not be a new relationship for long. And then you're still stuck with an old relationship and the question is will your old relationship a year from now be better than your old relationship that you currently have is? And if the answer is yes then yes sunk costs completely apply. But if the answer is no then what you're really doing is shopping for novelty not ignoring sunk costs.
I suspect, considering the process retrospect, a great deal of that pain can be avoided by committing to migrating directly to an SQL system the moment you need an index.
It’s possible it started multiple occasions. There’s two provisos to that. One of them is oxygen makes it impossible really for life to start. So, as soon as we’ve got oxygen in the atmosphere, then life isn’t going to keep starting over.
The Pauls feel as fresh today as the day I put them on, whereas the hydraulics have required much bikeshop tuning over the course of the last eighteen months.
It is a remarkable work, not just of scholarship and research but, above all, of a fresh angle on the way that the inter-reaction between Nazism and Stalinism actually caused such appalling levels of hatred and murder in this particular area.
Wow. A profound little philosophy book from Japan, communicating the psychology of Alfred Adler - a rival of Freud. Told as a conversation between an angry student and a patient teacher. A little book so good that I rushed home from other activities to keep reading it, and finished in a day. A surprisingly fresh perspective on how to live. (The “disliked” part is not the point, so don’t let the…
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.