Please Stop Using Booleans.
Related videos
This is bad...
Theo - t3․gg
104.3k views
Stop letting your agents write Markdown.
Theo - t3․gg
91.0k views
OpenAI is lying
Theo - t3․gg
81.9k views
Open source is dying
Theo - t3․gg
97.8k views
So I stopped using Ghostty...
Theo - t3․gg
165.4k views
Anthropic is lying to us.
Theo - t3․gg
122.7k views
I was wrong
Theo - t3․gg
69.3k views
"please stop calling us slop" - Microslop
The PrimeTime
180.9k views
2025: The year I stopped writing code
Theo - t3․gg
51.9k views
If you write code, please watch this.
Theo - t3․gg
78.0k views
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Unlock all features
FREE: Get instant access to 10 AI summaries, chats, or transcripts per day.
Related videos
This is bad...
Theo - t3․gg
104.3k views
Stop letting your agents write Markdown.
Theo - t3․gg
91.0k views
OpenAI is lying
Theo - t3․gg
81.9k views
Open source is dying
Theo - t3․gg
97.8k views
So I stopped using Ghostty...
Theo - t3․gg
165.4k views
Anthropic is lying to us.
Theo - t3․gg
122.7k views
I was wrong
Theo - t3․gg
69.3k views
"please stop calling us slop" - Microslop
The PrimeTime
180.9k views
2025: The year I stopped writing code
Theo - t3․gg
51.9k views
If you write code, please watch this.
Theo - t3․gg
78.0k views
Top Comments (10)
tomorrow a new video with title: "I was wrong, booleans are the gods"
"You either die a complex type or live long enough to see yourself become a Boolean."
There's no in-between when it comes to booleans.
So tl;dw: Don't store booleans. If the boolean can be derived off some logical explaination, it shouldn't be stored.
I once saw someone store age, despite having the users birth date, so yeah.
crazy refresh pull
From the standpoint of enterprise development, this makes sense. From the standpoint of embedded development, we often use booleans because it is the data type. I want to read a pin and store the state. It would be nice to have everything timestamped too, but when the specification of your device is measured in kilobytes of memory it's a luxury that often cannot be afforded. In this case, creating structures that pack 8 booleans into one uint8 would be the reason to argue against booleans.
Bro getting paid by Big String now too?????
Came here exclusively for the comments. Next up. Please stop using strings.
"Yes or no? I personally find myself a little in between" ah yes the irony
Unlock the Data Inside
Turn Videos into Knowledge
- Get FREE 10/day: transcripts, summaries, chats
- Chat with videos, export text & PDF
- $1 free API credit for RAG, chatbots & research
Free forever plan • All features unlocked
Top Comments (10)
tomorrow a new video with title: "I was wrong, booleans are the gods"
"You either die a complex type or live long enough to see yourself become a Boolean."
There's no in-between when it comes to booleans.
So tl;dw: Don't store booleans. If the boolean can be derived off some logical explaination, it shouldn't be stored.
I once saw someone store age, despite having the users birth date, so yeah.
crazy refresh pull
From the standpoint of enterprise development, this makes sense. From the standpoint of embedded development, we often use booleans because it is the data type. I want to read a pin and store the state. It would be nice to have everything timestamped too, but when the specification of your device is measured in kilobytes of memory it's a luxury that often cannot be afforded. In this case, creating structures that pack 8 booleans into one uint8 would be the reason to argue against booleans.
Bro getting paid by Big String now too?????
Came here exclusively for the comments. Next up. Please stop using strings.
"Yes or no? I personally find myself a little in between" ah yes the irony