Code Bits @codebits67
🦀 Rust Tips + How to write great software Mountain View, California Joined August 2025-
Tweets15
-
Followers0
-
Following5
-
Likes0
In imperative/object oriented languages you change state by mutating variables In functional languages, you change state by transforming variables
- Imperative and object oriented languages => Code has the State - Functional languages => Code is State
Use of bools is usually a code smell. Use enums with two variants for better readability
Every time I get stuck at implementing something complicated, I pause and think about this
1. Make it work 2. Make it work right 3. Make it work fast In this order, always
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
For example it’s impossible in Rust to find all occurrences of Default trait implemented on a type. Therefore, defaults are code smell, shouldn’t use them
Litmus test for if something in code is explicit -> can you find all occurrences of it in your codebase under 10 seconds. If not, it occurs implicitly and outside developer knowledge, leading 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
@keysmashbandit @krishnanrohit That’s only if you know which sensor failed. If camera tells you to take left and LiDAR tells you to take right, which one is failing and which one is not?
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
Good judgment comes from wisdom. Wisdom comes from bad judgement
In beginning, you won’t know what great code is. You have to wait for something to break. Then you will realize how the code should have been from the start to prevent that bug. That is great code.
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
kache @yacineMTB
310K Followers 6K Following reinforcement learning, robots. prev eng @ x, stripe. 6'3 (height) tensorpunk subscribe to read my blog!
Karl-William Nietert @Karl_William
381 Followers 502 Following Look ahead or you won’t get ahead @maticrobots
SpaceX @SpaceX
41.9M Followers 123 Following SpaceX designs, manufactures and launches the world’s most advanced rockets and spacecraft
You might like
