Code Bits
@codebits67
🦀 Rust Tips + How to write great software
Use of bools is usually a code smell. Use enums with two variants for better readability
Everything in your code should be as explicit as possible. Everything that happens should be under developers’ knowledge, anything happening outside will lead to bugs
Default values are silent bugs. If the runtime guesses for me, it guesses wrong. Be explicit: config, timeouts, nullability, perms. Ship intent, not surprises
Money is cheap, Pride is expensive Being proud of what you do is prerequisite for writing great software
When things break, you realize why they break. When you realize why they break, you write things that don’t break
Great Software follows these two principles: 1. Makes it as easy as possible to add features 2. Makes it as hard as possible to add bugs
United States Tendances
- 1. Luka 105K posts
- 2. Talus 16.5K posts
- 3. Blue Jays 84.7K posts
- 4. #GirlsWhoInspire N/A
- 5. #WorldSeries 105K posts
- 6. Halo 171K posts
- 7. #GirlPower N/A
- 8. #INDvsAUS 24.4K posts
- 9. #LakeShow 3,750 posts
- 10. Pharos 6,230 posts
- 11. Flyquest 4,165 posts
- 12. Mavs 14K posts
- 13. Toronto 68.9K posts
- 14. Domain For Sale 8,477 posts
- 15. Snell 14.5K posts
- 16. Marcus Smart 4,020 posts
- 17. Kyshawn George 4,531 posts
- 18. Vando 2,787 posts
- 19. Nico Harrison 2,631 posts
- 20. Kross 2,716 posts
Something went wrong.
Something went wrong.