That's why I love the Readex Pro font. It also has glyphs for Arabic and a lot more languages in the same file, so I can use one font file for everything.
I'm trying to build a native postman alternative using Rust + Iced. I want it to use .http files as its collections and .env files as its environments. So that data is stored in plain text and easily editable by AI and usable by other apps like VSCode rest client.
Whenever I'm filling a long form on an official website, I feel like I'm racing against an invisible clock because of this session time out thing that happened to me countless times.
I'm surprised nobody mentioned types or type systems as one of the best solutions for eliminating fear. Out of all the systems that worked on, the ones that were changed fearlessly were stuff written in Haskell and Purescript. That was before Rust became so popular. These systems were changed fearlessly and we had very minimal tests. The code reviews were much easier to perform as you don't tend to check if the code might throw exceptions but you just need to think about business logic.
These days I'd argue that Rust is at the same level of Haskell and Purescript in fearlessness.
Some languages that removes certain fears:
- Kotlin: removes the fear of null exceptions
- Go: removes the fear of forgetting about an error that this function throws
- Languages with ADT (Haskell, Rust ... etc): remove the fear of missing a case
I'd claim that this is a logic that comes from rich, first world countries where you don't need to prioritize things in life much, as you can mostly afford everything. Poor people have to think thoroughly about everything they spend money on.
What I noticed too for pushing the for loops down is that more functions start taking list of things instead of one thing. This makes it easier down the path when a requirement change and we need to handle multiple things instead of one thing with the same code logic. It decreases overall change in the codebase.