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 103K posts
- 2. Sauce 76.4K posts
- 3. Sauce 76.4K posts
- 4. Garrett Wilson 4,286 posts
- 5. Breece 12.1K posts
- 6. Cheney 212K posts
- 7. AD Mitchell 5,962 posts
- 8. Shaheed 15.3K posts
- 9. Mazi Smith 4,347 posts
- 10. Jerry 53.9K posts
- 11. Jermaine Johnson 2,825 posts
- 12. Merino 29.4K posts
- 13. #JetUp 1,496 posts
- 14. Aaron Glenn N/A
- 15. Indy 16.7K posts
- 16. #NFLtradedeadline N/A
- 17. Minkah 5,139 posts
- 18. Veach 3,982 posts
- 19. Micah 9,796 posts
- 20. Mougey 1,560 posts
Something went wrong.
Something went wrong.