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 الاتجاهات
- 1. Jets 82.1K posts
- 2. Bengals 49.2K posts
- 3. Eagles 112K posts
- 4. Giants 93.6K posts
- 5. Falcons 38.3K posts
- 6. Caleb 36.9K posts
- 7. Zac Taylor 4,963 posts
- 8. Browns 46.7K posts
- 9. Bears 65.6K posts
- 10. Myles Garrett 8,251 posts
- 11. Ravens 50.2K posts
- 12. Dolphins 27.9K posts
- 13. Drake Maye 16.3K posts
- 14. 49ers 30.8K posts
- 15. Skattebo 43.3K posts
- 16. Andy Dalton 9,034 posts
- 17. Justin Fields 7,814 posts
- 18. Anthony Nelson 1,256 posts
- 19. Dylan Harper 4,569 posts
- 20. Dillon Gabriel 5,680 posts
Something went wrong.
Something went wrong.