Here are some fragmented reasons as to why I don't like having a couch.
The couch, often positioned facing a television, symbolizes the societal imposition of a predetermined essence onto our living spaces. This arrangement, reminiscent of Sartre's concept of bad faith, dictates the room's function and restricts its potential. It mirrors the limitations we place upon ourselves when we conform to societal expectations, disregarding our authentic selves.
For real.
This writing stems from my experience advising a few startups, particularly smaller ones with plenty of junior software engineers trying to transition into machine learning and related fields. From this work, I've noticed three topics that I want to address. My aim is that, by the end of this article, these younger developers will be equipped with key questions they can ask themselves to improve their ability to make decisions under uncertainty.
Going to American baths is just so weird. I spent my summer in Japan visiting different onsens, and it was both a natural and spiritual experience. Before entering the water, everyone would bathe in the front, and kids would learn from their dads how to bathe. I would often sit on the edges of cliffs, gazing at the water or the sunrise, and it felt like we were monkeys, freely splashing about in nature.
In contrast, the time I spent in LA or New York City at various bathhouses was different. No one looked like an animal; instead, everyone seemed focused on optimization. People barely bathed before entering the water, wearing their dirty little speedos and swim trunks that they had definitely peed in the month before.
Gross.
The goal of this post is basically to share what I have learned about writing a tweet, how to think about writing a hook, and a few comments on how the body and the cta needs to retain and reward the user. Its not much, I've only been on twitter for about 6 month.
This entire piece of writing is dedicated to a recent response on Hacker News. I hope you can see, as a member of reality, that I write this sincerely.
—
Also, I wrote this as a speech-to-text conversion. As I mentioned in my advice post about writing more, my measure for writing more is simply putting more words on a page. If you're wondering how I can be so vulnerable, it's the same as what I mentioned about confidence. If you think this comment hurt me remember that you're just a mirror.
I've also learned that writing is a exorcism of your own thoughts. The more I write, the less these thoughts stick around in my head.
After writing my post advice for young people, a couple of people asked about my learning process. I could discuss overcoming plateaus or developing mastery, learning for the joy of learning. I could also talk about how to avoid feeling overwhelmed by new topics and break them down into smaller pieces. However, I think that has been done before.
Instead, I'm going to explore a new style. I'm just going to go through a chronological telling of my life and what I learned from just trying new things. I'm going to talk about the tactics and strategies and see how this pans out.
If you've followed my work on RAG systems, you'll know I emphasize treating them as recommendation systems at their core. In this post, we'll explore the concept of inverted thinking to tackle the challenge of building an exceptional RAG system.
What is inverted thinking?
Inverted thinking is a problem-solving approach that flips the perspective. Instead of asking, "How can I build a great RAG system?", we ask, "How could I create the worst possible RAG system?" By identifying potential pitfalls, we can more effectively avoid them and build towards excellence.
This approach aligns with our broader discussion on RAG systems, which you can explore further in our RAG flywheel article and our comprehensive guide on Levels of Complexity in RAG Applications.