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 Trends
- 1. #UFC321 16.5K posts
- 2. #OctHealingStreamsDay2 N/A
- 3. Maksum N/A
- 4. Good Saturday 30.9K posts
- 5. Mizuki 16.1K posts
- 6. Raposo N/A
- 7. #Caturday 4,087 posts
- 8. Sunderland 36.5K posts
- 9. #SaturdayVibes 4,630 posts
- 10. #CollegeGameDay N/A
- 11. Garnacho 23.7K posts
- 12. Amorim 23.6K posts
- 13. Armorion Smith N/A
- 14. Joao Pedro 8,102 posts
- 15. Kenny Chesney N/A
- 16. Prime Rib N/A
- 17. Patrick Star 11.1K posts
- 18. Your Pete 3,364 posts
- 19. TAEHYUNG GOES TO HOLLYWOOD 68.5K posts
- 20. Neto 15.9K posts
Something went wrong.
Something went wrong.