ChatGPT got the snail one wrong over and over, not parsing that on the 16th day there will be no night for the snail to fall back down 4 meters:
Let's analyze the snail's progress:
During the day, the snail climbs 5 meters upwards.
During the night, it slides 4 meters downwards.
So, in a day, the snail effectively moves 5 - 4 = 1 meter upwards.
To calculate the number of days required for the snail to reach the top of the well, we need to determine how many 1-meter increments are necessary to cover the remaining distance of 20 meters.
20 meters / 1 meter = 20 days
Therefore, it will take the snail 20 days to reach the top of the well.
imho software engineers are the most susceptible to the hyperactivity that often leads to these types of maladies - which ultimately flips from “working 100 miles an hour” to “only able to work 2 hours a day”, aka burnout
Byungchul Han is what’s been saving me - almost like philosophical therapy. has helped me to realize the societal origins of a lot of the expectations i inflict on myself
Closing line with the usual FUD around decentralization as a scary thing - even though it was centralization and privileged actors at the center of that centralization that has caused every major CEX collapse.
If we think an occasional CEX collapse is bad, the financial surveillance and political manipulation that would occur under a CBDC scheme is far more damaging to freedom and financial security in the long run.
Be vigilant of articles that slip in advertisements for CBDC - they are quickly becoming a propaganda weapon.
"A more promising approach is through central bank digital currencies that operate within the broader digital monetary system. This is an approach that builds on the trust embedded in central bank money, and could serve public interest in a future monetary system(opens a new window). The technology benefits flow to real world economic activities rather than just other types of crypto. The economic benefits of decentralisation should also be scrutinised more effectively. We are now seeing what happens when an industry rests simply on an article of faith."
- It's typically a journey up and down the stack in terms of frontend, backend, and DevOps, and a journey in and out of solving inherently complex problems (where the seams of your services are, authentication) and incidentally complex problems (frameworks, machine-specific issues, Docker hell etc.)
- 80% what needs to be done today/what fires need putting out, and 20% planning for the future and seeing how the bleeding edge can legitimately help us (e.g. WASM coming soon...). This is part of the general keeping up with advances in industry
- Mentoring, jumping on pair programming calls to unblock other teammates.
most of the problems blockchain attempts to solve are public coordination problems in adversarial environments rather than corporate problems the CTOs/CIOs are likely to have.
People in crypto invent new words rather than building new things all too often. I think it's a carryover practice that emerged from the whitepaper era of 2017-2018, when you had to have a massive pseudo-intellectual theoretical framework supporting your dApp to support a token raise.
The Last Question - Isaac Asimov - Read by Leonard Nimoy
https://www.youtube.com/watch?v=8XOtx4sa9k4&t=544s&ab_channe...