DEV Community

Cover image for Do You Have a Mantra That Guides You?
dev.to staff for The DEV Team

Posted on

Do You Have a Mantra That Guides You?

Define a personal coding philosophy or mantra you developed in 2023. How does this guiding principle shape your approach to coding and community engagement?


Follow the DEVteam for more discussions and online camaraderie!

Top comments (10)

Collapse
 
thormeier profile image
Pascal Thormeier • Edited

"We always managed to get everything running somehow." - A little bit of a twist on the good old "If there's a will, there's a way." It doesn't work? You managed to get everything else running somehow, so how hard can it be? That one lead to the most insane grinds, the hackiest solutions (not exactly proud of these moments, but alas), motivated people around me and got jobs done.

Collapse
 
wraith profile image
Jake Lundberg

I have 2!

  1. What’s the next action?
  2. Make it work, then make it better.
Collapse
 
anmolbaranwal profile image
Anmol Baranwal

Since childhood, I've always worked hard for my parents.

I've never cheated in my life; I've always put in the effort. Real hard work.

Why? Because I understand the real struggles.

These two sentences are what I've told myself countless times over the years:

"You have to work hard, whether you do it now or later."

"There's always at least one person doing what you're avoiding."

These phrases normally push me further to work harder.

Of course, I've enjoyed my life as much as I can :)

People don't understand that it's damn tough to do your best when you don't have an environment.

Collapse
 
hackape profile image
hackape • Edited

Before delving into a specific problem, always ask yourself:

  • Does this problem even exist?
  • What is the “real problem”?
  • And does addressing the current problem helps solve the real one?
Collapse
 
booleanhunter profile image
Ashwin Hariharan

Here are a few that I follow:

  1. Favor simple code that relies mostly on cross-language paradigms, as opposed to framework-specific abstractions
  2. Don’t just blindly assume past tool choices are sacred
  3. Prefer legibility over succinctness while writing code
Collapse
 
adriens profile image
adriens

That looks fun: let's learn the required stuff and make it happen

Collapse
 
ads-bne profile image
ADS-BNE • Edited

For me:

  • "Be humble". Meaning always be open to learning and constructive criticism (code reviews). For example: I've worked in web for about 15 years and only today learnt that replacing spaces with   prevents word-wrap. Instead of being bothered that I should have known this, I try to be grateful that now I know this.
  • "Iterate, iterate, iterate". Get it working, then improve over and over again.
Collapse
 
ryencode profile image
Ryan Brown

"Always check your assumptions"
As those darn things seem to be what hides bugs and causes errors the most.

Collapse
 
akashdev23 profile image
Akash Dev

"In the journey of programming we can't find one common roadmap. We have to find out our own individual road. There's no predefined path. "

Collapse
 
ksolomon profile image
Keith Solomon

“If you’re not learning, you’re doing it wrong.”

I ignored this for too long…and now I’m in a position where all I’m doing is learning (moving from dev to management).