DEV Community

loading...
Cover image for My Top 10 Programming Proverbs

My Top 10 Programming Proverbs

antjanus profile image Antonin Januska Originally published at antjanus.com ・Updated on ・1 min read

I cross-posted this post on my personal blog.

A little while back, I started a repo of funny (and insightful!) programming quotes and proverbs. These often take a shape of an existing proverbs (like Rome wasn't built in a day) and get translated to be tech-relevant and hopefully give you a good chuckle (like Facebook wasn't built in a day). Protip: You can put these into Slack as the loading/intro messages. :)

Without further ado, here are my favorites to brighten your day:

When you reach wizened-engineer level, there are at least a hundred wizened engineers above you.


A deployed MVP is worth two prototyped.


Sleep on a force push.


Sometimes you have to cut legacy support to allow the new product to bloom.


Good test coverage + automated workflows = quiet cell phones and better sleep.


There is no test without first a failure


Anger and stubborness make bad allies in code review


With commit and deploy access comes great responsibility


Don't put all your logic in one method basket


A foreach loop avoided is a CPU cycle earned.

Discussion (19)

pic
Editor guide
Collapse
rpalo profile image
Ryan Palo • Edited

I like

Premature optimization is the root of all evil.

Followed by

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.

Collapse
andreasjakof profile image
Andreas Jakof • Edited

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.

Collapse
antjanus profile image
Antonin Januska Author

Go to the quotes repo and open up a PR for that self-quote!

Collapse
jackharner profile image
Jack Harner πŸš€

With commit and deploy access comes great responsibility

My Favorite

Collapse
larsklopstra profile image
Lars Klopstra ⚑

Shouldn't that be merge instead of commit tho?

Collapse
antjanus profile image
Antonin Januska Author

I guess that depends! I was thinking more about not being able to push to master unless you have that permission.

Collapse
amberwilkie profile image
Amber Wilkie

Make it work, make it right, make it fast.

Collapse
andreasjakof profile image
Collapse
gypsydave5 profile image
Collapse
karataev profile image
Collapse
antjanus profile image
Antonin Januska Author

I know! There are tons of these. :)

Collapse
antjanus profile image
Antonin Januska Author

Not listed but one of my other favorites:

What happens in Git stays in Git

Collapse
evild70 profile image
Dennis Lahay

"Working code is better than good looking code."

Collapse
meshcloud3d profile image
Noah Hornberger

If you don't know how to solve the problem, stop typing. It's not funny, but it saves lots of time.

Collapse
drozerah profile image
Drozerah

Get app, stand app, stand app for your app! Get app, stand app, don't give up the fight!

Collapse
antjanus profile image
Antonin Januska Author

Is this Dr. Seuss? πŸ˜‚

Collapse
drozerah profile image
Drozerah

Keep it secret !

Collapse
gdcohen profile image
gdcohen

My favorite: "There are 10 kinds of people. Those who understand binary and those who don't".

Collapse
javaguirre profile image
Javier Aguirre

Leave the camp better than you found it, it applies to programming and almost everything in life 😁