DEV Community: Celiz Matias

5 tools to be more productive

Celiz Matias — Sun, 04 Apr 2021 07:07:42 +0000

Do you want be more productive?

If you're reading this maybe you just need more rest 😅 , if you think that's true I think maybe the best combination to find your productive moments is your bed and that comfy pillow that goes with it.

It's really important to understand that we as developers first and foremost are human and we need to balance our mind and body to endure long working days.

So here's my top 5 tools to be more productive

Toggl → Is a tool to track your times, this can help you to discover when you are more productive and how many hours you hard work and how rest in your working day.
Remember that is very important take a rest after X amount of time and repeat as many times as you need to in your working day.
Miro → In the absence of physical boards, miro helps us to be more productive in meetings. You can explain a complex problem or flow in simply graphs and collaborate with your team.
Figma → If you work in Frontend you might like this tool, it's really amazing, easy to use and easy to collaborate with de UI/UX team. And if you work in Backend and you have never paid attention to the UX work please start doing it now, this is where the magic begins.
Spark → This is undoubtedly the best email client, It will help you to organice your day, conbine calendars and do tasks from your inbox more quickly.
Notion / Archbee → Notion is very useful for building your own personal documentation, meetings resume. Personally, I keep track of my entire career in Notion, reading lists, AWS docs, react native tricks and technical information to share with the team, etc.

And this is the best part because everything is in markdown so you can copy & paste into Archbee your work documentation related to a specific project.

React Native - Clean Architecture

Celiz Matias — Mon, 16 Nov 2020 01:48:25 +0000

Hi everyone the last time that I worked in a startup with React Native I found a lot of problems with the scalability and encapsulation of different modules and layers.

The problem

React Native is a framework that you can use to development hybrid mobile applications, so as we know we need a API maybe.. and if this is your case and you have the experience working with this framework. I'm sure that you found problems like this:

This is a nightmare in big applications because is really difficult to debug, the only way is find in all the code where is the object property that is (undefined | null | any not compatible with the component or styles).

Or in this other case:

The problem here maybe was a render without the correct data, or some change in the API contract.

The proposed solution

I study how apply something like Clean Architecture to a react native project and started to build a boilerplate to share with the community.

But this apply to different cases.

If you have a stable backend | api maybe you wanna keep the frontend more easier or lightweight I use something like that:

If you wanna get a stable application, with hard safety layers, testeable and easy to scale but a bigger cost in time.

https://github.com/G33N/rn-clean-architecture

For a really big application I recommended separate the app in independiente modules or small applications, like chat, feed, stories... This is more efficient in bigger teams +2 squads or +10 developers. This help to the organization to give more autonomy and as plus more velocity.

Something like that: https://github.com/G33N/rn-mma-app repo in progress Sorry!

Main resources:
https://blog.cleancoder.com/uncle-bob/2012/08/13/the-clean-architecture.html

Thanks for reading! all comments all welcome and help me to build betters things to share with you, so pls leave me your comment!

What do you know about Kaizen?

Celiz Matias — Fri, 11 Sep 2020 23:18:37 +0000

It turns out that the processes we sometimes accept or create unconsciously are not always the best or most efficient and we can fall into the cycle of this process countless times until we realize it. That's why I think that incorporating a kaizen culture in the work teams can be the key factor to achieve being Agile since it implies generating proposals, agreements and activating them.

Start with what you have, make small changes and achieve great impacts!

If it's not easy, it's not Kaizen.

What do you think?

7 reasons to apply storytelling in our posts and jobs

Celiz Matias — Mon, 31 Aug 2020 14:46:52 +0000

Recently I'm studying a lot about how improve my communication skills because is something exclude to be a great leader, get more likes and entertaining to your audience.

The quality of your story is equal to the impact that can generate.
To improve your communication skills and to be heard.
Actually the organisations need more influent leaders and a truly leader need know how tell good stories.
All the scientific texts, the developers' ideas, the presentation, call it what you want, are so boring. Storytelling can help you to be more readable.
Is more easier remember stories than ideas or boring texts.
The power of the influent is so useful and you can apply this into your stories through different methods.
So that your proposals are put into action in the work teams.

Carlos Salas - Storytelling La escritura magica

Why we need the measurements ?

Celiz Matias — Wed, 19 Aug 2020 00:00:52 +0000

How many times our team lead, CTO, CPO or product owner tell us that they wish see metrics, logs or something related a feature?

Once time, A team lead ask me about the coverage of the code I remember that I think "why, if my code works?".

In others similar situation a CPO ask me about the analytics metrics, "how the users adopts the last release?" And in the same way the PO ask me "This screen are slow, we know what happens?"

So life was going well, the team keep working without any metric or productive logs and by surprise the product was aceptable and the users started to growing, and y remember me and my coworkers celebrating.

NICE! We are the best team in the word

So life was going well, right? ;) One day a user found a fat bug and anyone know what happened or how reproduce and we fall through the ladders, I was imagine to Rocky falling for the ladders but I can't found the GIF 😂

We fail, we lost a lot of money and the organisation getting mad with the developers and with a lot of pain we accept that we needed the metrics to monitor the user adoption and behaviours, we needed the logs and traces and why not we needed a performance monitor.

So, getting metrics, logs, testings of your product is part of the quality that the each developer should do and you can trust in me when I tell you that this is hard to start but it's a good investment this will make your job more easier. Because you will more available information to find a solution to your problems or more information to improve flows or complex task in your application.

If you are interested in tutorials about 'how measure a react native application?' leave a comment and I will prepare something more technical.

"Shit happens, but if you are smart maybe you can clean the shit from your shoes and change something that can care your shoes the next time"

NPM package deploy

Celiz Matias — Tue, 18 Aug 2020 21:28:11 +0000

My Workflow

Node.js package deploy

Submission Category: DIY Deployments

Yaml File or Link to Code

G33N / rn-ui-kit

UI library

rn-ui-kit

This repository is part of "Building a scalable APP with multi-module architecture"

What is a library?

Is a piece of business logic code that should be shared

Tree

├── src                            Module code
├── test                           Unit test
├── package.json                   Module dependencies
└── module.ts                      Module entry point

View on GitHub

How works

This workflow run ci and unit test publish a npm package on push or pull request to master branch only if the job build run successful all the steps and pass the coverage requirements.

https://www.npmjs.com/package/@g33n/rn-ui-kit

How I get a senior developer job only with 6 months of experience?

Celiz Matias — Sun, 16 Aug 2020 23:11:27 +0000

Hi everyone! this is my first post... and why not? I'm writing this in english that not is my native lenguaje so be nice and If something is grammatically wrong pls let me a comment :D

So, How I got my senior development job only with 6 months of experience? Really this is not true, I coding from my 18 years as a hobby and I get freelance jobs, remote jobs but nothing professional. In my past I code in PHP, HTML, python, and scripting in linux terminal but I feel that something was wrong and I think if I really want follow this path to be a better developer I need change some things, What I did? at this time nothing relevant just keep studying Angular and others technologies, but what is the most important? that I still hitting the docs of many frameworks without fear to fail or get a bad feedback of my work, let my explain this a little bit more.

When you are in your first steps, the more important thing that you should never do is be self-centred because to learn you need study and hear a lot of opinions and be able to process, so a good practice about this is be a good person, you need ask for feedback all time as possible and make this your routine, code something and ask about how improve your code to your self or your co-workers.

More about feedback culture

Another thing that help me a lot to improve how a learn about something is in first step learn to fail, as developers we need or in others words We should learn to fail, learn about how through the failures we can get more experience for example if the algorithm in your mind is something like that:

senior = successTask + yearsOfExperience

Please you need change this to:

senior = successTask + failuresExperiences + productiveExperience

Where successTask obviously is all things that you feel great to share with others, a library a project, anything, the failuresExperiences is the most valued for me because if you don't have this in your algorithm you are losing the best part of coding, fail in something is great because this tell to others that you don't have fear to fail or unsure of changes and this is great! because this is a really valuable skills to the moderns companies and is a strong boost to new skills.

Also if you understand that the time is relative I'm sure that you understand that the hunters and human resources people always take the same mistake about

"Developer with more than 4 years of experience in {insert skills}"

. We know that this wrong because nothings have in common the years that someone are development in a lenguaje or framework if this person never took the time to investigate about the tool that he/she is using or learn how make a clean code so, this is the why I replace yearsOfExperience by productiveExperience because if you have a developer with 20 years of experiences but he or she just keep in the past and don't invest time in keep learning or keep updated maybe this is not so great.

Finally you work is valued too but you need learn from each others how improve your skills and determinate what is the path in a developer career that make you happy.

I recommend that take a time to do your Ikigai and write yours steps to be the developer, architect, team lead, chief that you want be.

I'm react native developer my short path is maybe be a react architect and for do this I building a multimodule architecture, with unit and e2e tests, CI, and others things. If you wanna be part of this check my repo and leave your comment if this post like you or wanna talk about other topic

Thanks!