I'm a Staff Software Engineer at Cisco. I specialize in Python and Go, building functional, practical, and maintainable web systems leveraging Kubernetes and the cloud. Blog opinions are my own.
If you say you donβt like code because it is too slow, I say show me the benchmark that proves the extra complexity is worth it.
And
Think twice about writing code for potential future features. It usually makes your current feature code more complicated, and you double your work if you are wrong about what features are coming.
And slight shameless self-quote:
Write code using methods you wish you had. Then go write those methods.
I like
Followed by
And
And slight shameless self-quote:
Thatβs how I write code. π
First run is usually something like Pseudocode in VS, using methods that not yet exist but lining the rough path.
And then the tedious work.
Next run, the same for each of the not yet existing methods.
And so on... until all methods do, what they are supposed to.
Go to the quotes repo and open up a PR for that self-quote!
My Favorite
Shouldn't that be merge instead of commit tho?
I guess that depends! I was thinking more about not being able to push to
masterunless you have that permission.Make it work, make it right, make it fast.
Amen!
"Working code is better than good looking code."
Antonin - you may enjoy these Perl(i)s of wisdom
There is also The Zen of Python
I know! There are tons of these. :)
Not listed but one of my other favorites:
Get app, stand app, stand app for your app! Get app, stand app, don't give up the fight!
Is this Dr. Seuss? π
Keep it secret !
My favorite: "There are 10 kinds of people. Those who understand binary and those who don't".
Leave the camp better than you found it, it applies to programming and almost everything in life π
If you don't know how to solve the problem, stop typing. It's not funny, but it saves lots of time.