What you need to know
- 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
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!
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.”
“I make sure to say hi to the teams before I begin my tasks because this way, we start on a good note.”
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.”
“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
KISS is an acronym for the phrase "Keep it simple, Stupid!"
DRY stands for "Don't Repeat Yourself"
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.
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.