|
(can't wait to make a Beef Wellington for Christmas)
Things I enjoyed reading
It's very easy to forget that behind any success story there are hundreds of failures, usually by some other people. Most stories written are not about failures, as people tend to avoid sharing them.
The author is doing quite the opposite, and this is great: not every side project brings millions, not every startup becomes a unicorn, but sometimes lessons learn are worthy of it anyway.
First of all, when deciding about the next project, I need to choose the smallest idea possible that can be developed by one person. Cut the scope as much as possible.
Estimate the time needed for the MVP. It shouldn’t take more than 3 weeks, assuming having a day job and working on the project only in my free time. If the estimation is higher, try to find out the quickest way to develop the MVP. There are many no-code tools that might speed up the development.
This is a great advice too: trying to polish everything to perfection means you just chase windmills, while instead you could actually get some product into the wild and learn from users' feedback instead of making assumptions.
This isn't the first article about cinnamon I am linking to, but probably the most detailed out the ones I've read on the peculiarities of actually peeling the bark and then grading it based on the thickness of quills.
For harvesting, farmers cut down the branches of cinnamon trees at an angle, which allows cinnamon bushes to regrow, Lakshith says. Young and tender twigs are thrown away. Once branches are soaked in water and are moist enough, peelers remove the outermost layer of the cinnamon bark. To produce thin cinnamon quills, they spend hours stripping off the inner bark of the cinnamon branch in sheets.
I am slightly disappointed no one published a similar paper before, but here we go: the authors watched all James Bond movies and comment on his exposure to harmful behaviour, activities, chemicals and so on, trying to understand if there is anything particularly interesting we could learn from one of the greatest spies.
An often-overlooked health concern for Bond is his level of hydration. Alcoholic beverages, shaken or stirred, do not prevent dehydration, which is a major concern given the extremes of physical activity he goes to, often in warm climates. On only three occasions was Bond observed drinking non-alcoholic drinks: orange juice [4], coffee [3], and salt water [9], of which the latter is particularly unhelpful in maintaining fluid balance.
Check out the full paper for more thoughts on jabs he misses before traveling, dressing attire unsuitable for the level of sun exposure he gets, and many more. Kind of made me consider watching the first twenty movies (which I've never seen thinking the only decent things from that century are stored in wine barrels).
Out of many things I have to say about software development, here is one of the most important ones:
In short, don’t start the work unless, and until all the variables are known…as much as possible. Look at it this way: how would you feel working on a 1,000 pieces Lego or puzzle, and just when you’re about done, you realize that there’s one piece missing. Or maybe two. Or three. Would you say that the Lego or puzzle is complete? I wouldn’t. I’d be frustrated. It means that I wasted time and energy that I could’ve directed somewhere else. Sure, you might say “Well, it’s 98% done”. But I don’t want a 98% done Millennium Falcon Lego. I want the whole thing. Why? Because it’s supposed to be whole. It’s that simple.
A good engineer solves problems, but most of the time the problem is not communicated properly: it is scattered across specifications, designs, documentation, OKRs, charts, and statistics. Any single discussion touches some of the sides to the problem, but almost never covers them all, so all parties involved are missing out on the opportunity to align their perspectives.
Solving a problem is not always about writing code – code is just a tool – it's about changing the perspective in such a way everyone gets to see the whole picture, and then removing obstacles if someone (not necessarily the user) is still missing out.
And that starts with the communication and asking questions.
The title might be relatable albeit misleading, but I honestly enjoyed taking a break from news and stories and research papers and just spend a few minutes reading about tomatoes (literally):
I’ve been reading a whole lot about tomatoes, particularly how they are transported from the North to the South of Nigeria. You see, tomatoes are quite subject to decay, only staying good for a couple of days outside of cold chain storage. As many transporters can not afford that they take a huge loss from the amount that is loaded unto the trailers to the amount that gets delivered to markets in the South.
This is actually one of the main reasons behind my weekly newsletter: taking a break from what I do for the rest of the week is not only refreshing but also is a great chance to sum up thoughts and ideas.
I grew up with lots of Cola copycats, but that didn't reduce the amount of myths and conspiracies about the drink (quite the opposite!). I won't be spoiling neither the two of them mentioned in the post nor the author's clear explanation of why they're not true – check it out. This point is quite interesting though:
Also, remember that all cola (including diet) is bad for your teeth, due to the acidity. If you drink it, try to do so with meals, try to use a straw, and try to drink some water after. Also, don’t brush your teeth immediately after drinking cola. The enamel on your teeth is vulnerable due to the acidity. You should wait 30-60 minutes for your saliva to repair the enamel before brushing.
The hight acidity is no surprise to me, although honestly as it doesn't taste sour I never thought of it from that perspective.
If you're reading this newsletter for any substantial amount of time, you've probably noticed that I am a huge than of all things linguistics. I don't speak many languages (yet?) but reading about their differences or others' journeys towards mastering them is fascinating on its own.
The matter of "discipline" comes in this way. Even when you make up your mind to do your Latin every day, life has a way of intruding so that you will be tempted to miss days. There will be crises and upsets and intrusions and excitements, and your feeling will be that "missing just one day can't hurt."
It does hurt. You've got to do your Latin every day, through death and disease and accidents and heartbreak, when you're travelling and when you're at home, when you're in school and when you're on vacation.
The best way to do this is: do your Latin first thing every morning, before you do anything else. Then, no matter what happens for the rest of day, they can't take your Latin lesson away from you.
This advice works for pretty much any other language too: perseverance does wonders when it comes to learning, and sadly there are no silver bullets here.
Solving a problem is not always enough. Sometimes solving it elegantly is what matters, even if the problem sounds oddly specific, like how many Thursdays are in any given month.
But it nagged at me. This blog has a long history of showing calendrical calculations, and I had written a post on a similar problem (finding months with five Fridays, Saturdays, and Sundays) eleven years ago. The scripts in that post had some brute force aspects, but they also took advantage of how months are structured to filter the loops. I wanted to do something similar for the “how many Thursdays” problem.
As the result, instead of just looping through days of the month, there is a beautiful mathematical solution (which is way harder to understand than a bruteforce approach, but it doesn't really matter).
I could probably share the link for the sake of the title's irony, but it's actually very insightful.
Instead, I’ve somewhat effortlessly and unconsciously downshifted from the self-imposed drive that was part of building a career. With retirement, that level of professional engagement has wound down and I can relax today, free of self-inflicted urgency about what’s next. Notices and messages commanding my attention still arrive at my email inbox, only now I have the unguilty pleasure, if I wish, of swiping them away.
At the same time I think that in a few decades the concept of retirement and its boundaries will be blurred by remote work, flexible schedules and many other things. There will be less and less point in appointing a date after which the option of swiping things away will turn into an "unguilty pleasure".
Judging by the article, retirement is an ultimate stage of being independent, from both society and other people, and this is what we actually manage to move closer and closer without becoming older or richer.
There is undoubtly a rise of attention to decent Russian writers (a few years ago the interest was only towards the indecent ones), and thus more and more modern authors are trying to decipher their motives.
They are doing it pretty good for rookies, and start with looking into writers' past:
His biography is a sequence of events for which only the adjective Dostoyevskian will really do. The Geist seems to pursue him; the Hegelian world-spirit seems to have a cruel, experimental interest in him. His mother dies of tuberculosis when he is 15. Two years later, his father perishes mysteriously, probably murdered by restive serfs. Eking out a literary career in smelly St. Petersburg, the young Dostoyevsky falls into debt and personal squalor. Also into reformist politics, which are bubbling up all over ancien-régime Russia: secret meetings, ardent manifestos.
The funny thing about Dostoyevsky is, his past never defined his writing and that's where I would challenge the author of the article. The key to understanding Dostoevsky is to realise that his writing is driven by his lack of future, which he never envisioned for himself.
Angst and misery of his characters is not his troubled past, it's his undefined future. And that stands true for most Russians.
Things I didn't know last Tuesday
I refuse to believe I was the only one lied to by parents and teachers, who'd claim that if you touch a baby bird dropped out of a nest, it'd be abandoned by its parents.
I think I even had nightmares of touching one by accident.
In fact, contrary to what our parents may have told us, most bird parents are unlikely to abandon their chicks over a little human fiddling. "Usually, birds are quite devoted to their young and not easily deterred from taking care of them," Chu said.
Judging by the source, birds don't even have such elaborated smell receptors to distinguish a short human touch.
Designing cities is hard, and numbering streets is not an easy feast, but Florence, WTF?
A double sequence of street numbering exists in Florence. Shops and businesses are identified by the letter 'R' after the number. This signifies 'red'. Private residences are numbered in black. Thus a street may have two number 18's, at times at considerable distance one from the other; 18R (as in the addresses given here) is a shop or business, while 18 is a private house.
Luckily, modern buildings don't rely on that rule anymore.
Sadly, seems like it's not only in Florence, but in other Italian cities too.
First I learnt that British pupils don't really drink pumpkin juice, now I am learning that Brits didn't even bother carving pumpkins, because they had turnips. And radishes.
For protection from Stingy Jack and other apparitions, people in the British Isles began carving faces into pieces of produce—particularly turnips, but in some cases potatoes, radishes and beets. Celebrants placed lit candles inside the cavities, similar to the pumpkin jack-o’-lanterns of modern Halloween. They believed leaving the spooky carvings outside their homes or carrying them as lanterns would protect them from harm’s way while offering a flicker of light that could cut through their dark surroundings.
| 
