December 7, 2022 –

10 recommendations for clean code and a successful life

Table of Contents

We feel fortunate to know and work with many talented developers that create wonderful things, shaping the future of technology and pushing the boundaries of innovation. But what’s behind it all? We have sat with one of our outstanding developers, Keylin Wu, to discuss the essential things for a balance of life and work.

What you need to know

about Keylin

  • Is our Senior Mobile Developer.
  • Speaks Mandarin, English, and Spanish.
  • She loves traveling and meeting new people.
  • iOS and Flutter(Dart) passionate developer.
  • Is our first guest in the DNAMIC Insights video series (coming really soon).

She wakes up and starts the day with a cup of coffee, a stretch, and a list of things to do that keep her mind sharp and focused. By setting goals for the day in a notebook where she creates a path filled with checks and small victories at the end of the day. 

Keylin's 10 recommendations

for developers

As a developer, focusing on your goals throughout the day is crucial. This can be difficult when faced with distractions, as we usually are when working from home, but you can stay on track if you keep your goals clear and concise. Working from home leads to motivation and excellence if you create a space and routine you love waking up to!

 

Keep your goals in mind but don’t forget about breaks too! Developers spend a lot of time on desks and looking at screens, so be conscious of how rest can impulse your work afterward. Recharge and come back to your work with fresh energy!

 

(If you aren’t a developer, you should go directly to the last two).

 

  •  Stay alert! Fixing one bug can create additional bugs!
  • Code is fragile; treat it as such! Code can be rigid, inextensible, and even not testable!
  • Features work most of the time, but sometimes they don’t, and that’s okay. Keep working on it.
  • Don’t be afraid to make changes just because it might cause a code crash. 
  • Build more efficient and maintainable code by eliminating bad design.
  • Avoid or minimize the need to refactor code.
  • Eliminate rigidity, fragility, immobility, and strong cohesion. 
  • Create code easier to understand, maintain, and test. For you and for others.
  • Believe in what you are doing. Do work that matters! 
  • Stay passionate!
We talked to her about her every day and how she puts these recommendations into action, and this is what she told us:

Success is all about communication

“I keep transparency and communication as priorities because I’ve learned with time that you need to speak up if you really want to be heard. As a woman, it took me a while because we are often accustomed to being silent or mansplained in this industry, but now I say what I need to say, and I ask for help when I need to. It has served me well in my life.”

At work, she swears by Slack as one of her main tools because of how accessible and multi-team communication it can be. She has mastered emails and is not shy regarding video chatting because she holds high regard when team communication flows.

“I make sure to say hi to the teams before I begin my tasks because this way, we start on a good note.”

Being transparent has helped her grow, but it has also helped her work more quickly and efficiently, individually and in a team.

Try to learn from everything

“Ego can be a very common feature in this industry, but you must go past that to evolve as a person and part of a team.”

With SOLID principles, she learned them as a guide to making code just as she likes: Well done and well structured. But she wasn’t given them as a topic in her education; instead, she put them into practice when encountering what she calls a spaghetti code in a project way passed her graduation.

“What makes a spaghetti code is that it has a fragile foundation and the efficiency lacks and it’s difficult to escalate. As the name says, it looks like spaghetti.”

The experience brought her a new appreciation for design software principles like SOLID and their work. How they make good patterns, clean code possible, order, well-done interfaces-etc.  Learning these added to her career big time and made her appreciate her craft even more.

“It’s worth mentioning that these principles are not absolute truth but rather a proven guide that will lead us down a more enjoyable path when programming. Not only for me but any programmer who will use your code.”

Work smarter, not harder

“How you know and see code can be the difference between a headache code and a power source.”

People need to be open about learning, adapting, and adopting elements to their lives. In a developer’s case, these principles like SOLID can assure quality and efficiency, plus minimizes repetitive code. 

What would have happened if she decided she already knew everything she needed and worked that spaghetti code like that? 

She’d probably be working on it still!

SOLID taught her what a good foundation and a firm structure could avoid her in the future and present. Yet, these are not the only ones she recommends you look at as a software developer.

KISS, SOLID and DRY

Like SOLID, many principles can help developers in cases needing a type of guide while making a “solid” foundation, structure, and overall excellent and organic code.

KISS is an acronym for the phrase "Keep it simple, Stupid!"

It seems a little aggressive, but this reminds us that any system will work better if kept simple, even in complex situations. KISS stands for simplicity as a development goal and shoves unnecessary complexity in any process.

DRY stands for "Don't Repeat Yourself"

This refers to making changes in any part of a program’s functionality, excluding changes in features that lack a logical relationship to the changed functionality. Essentially it reminds developers to avoid duplicating code to simplify maintenance ahead.

SOLID

SOLID’s object-oriented development principles make development easier to maintain and extend over time when applied together.

Keep your goals clear

and your code clean!

To be a developer requires organization, patience, consistency, bravery, empathy, and a little bit of craziness- the good kind. Because good code is like a garden; it’s beautiful and well-organized. But bad code can be compared to weeds – they’re everywhere! The differences might not seem significant at first glance, but you’ll notice how they can affect your work over time. If you notice it too late, it can seriously affect your projects. 

 

 Developers must be careful and conscious to ensure that code is as consistent and uniform as possible. For future development and to facilitate work for other teammates or developers who might go into this code later.

DNAMIC's addition

When you love what you do, you can excel at it. 

There are many keys to happiness in development. But when you can focus on your goals and keep your code clean and consistent, you can work better and become better.

 Keylin’s recommendations and way of working are a great examples of doing what you love in a place you enjoy and can motivate you to become the best.

 

If you’re interested in learning more about SOLID principles or staying up-to-date on the latest software trends and technology, check out our blog or INSIGHTS video series!

Learn more about our services!

Or contact us directly! Ask away!

And we will have the perfect role for out-of-the-box thinking developers ready to change the game and enhance your business to new heights.

Share content

Facebook
Twitter
LinkedIn