Warning, this post is polemic, but it has content that MUST be discussed.
Have you ever had to give maintenance to legacy code? Do you also want to cry when you see “that kind” of code? :D On today’s post we’ll talk about the art of over engineering.
When we talk about legacy code people usually get scared, and many times with reason.
Whenever I have to maintain some legacy project, the first thing I look at are the tests. Automated tests are usually a documentation of the written code, so looking at the tests we can have an idea on what a class does, even better if we have BDD tests, because we’ll have the scenarios very well described which makes it easier to understand whats going on. But in reality, how many times did you look at a code and it was not covered by tests? …
How many times you, as a developer, felt overwhelmed by having many tasks and responsibilities on the company you work on?
On today’s post we’ll discuss about being overwhelmed, the power of saying “No” and how to keep your mind sane.
Bringing responsibilities to yourself is a good thing for a developer. By doing this you will stand out and the opportunities will start to pop up for you.
It’s normal that, once you are evolving as a developer/it professional in general, new opportunities appear for you and I really encourage you to take these opportunities to grow in your career. …
Are you sure you’re a senior professional? Which developer or professional of any other area never asked yourself “Am I a senior professional”?
We never know which level of seniority we are. But, what is seniority? On this post I’ll talk a bit more about this subject and tell a bit how I think a senior professional must be.
I’ve participated on many projects and on these I could see many situations where I questioned why some people are considered senior. Is it because of the time of experience? Is it because of the knowledge?
Some people say it is about “experience”, however I strongly disagree. Seniority is not just about experience, because a person can have 10 years of experience however cannot deal with a lot of important things that we need to succeed on professional life. Usually a senior developer, talking about developers, is that person who is already very experienced and the market sees him/her as a person that can aggregate in many aspects on their companies. …
Covid-19 is the hot topic in 2020. I’ve been reading about the impacts on the economy and on the companies. As we know, there are a lot of bad things about covid-19 — deaths, unemployment, economy collapse, people lonely, depression, etc.
But we need to see the good part of this pandemic. I know it’s hard to see a good side, however there are good lessons we’re learning. Today we’ll discuss a bit about the lessons companies learned from covid-19.
Many times we think that only certain sectors of the economy can work with digital products, but during this pandemic it’s proving wrong. Many small, medium businesses, and even autonomous professionals are innovating with digital services/products. …
There are a few things that could help the life of the ones that are starting their IT career.
Note that I said help, not make it easier. There is no easy path to succeed on this field, you need to study, share knowledge, study more, exercise soft skills and many other things
Below are 5 tips that will guide you to the success path.
Probably you are working closely to very good people, but also with people that is not very helpful. You need to identify the ones that can really help you.
Choose your mentor and stay close to this person. Listen what he/she says, try to get lists of things to study, pay attention on his/her actions, discuss about the things you are studying, be a good listener. …
Now at the beginning of 2020 the home office became even more popular with the pandemic of covid-19.
I’ve spoken with a lot of friends that also work on IT and they’re having some trouble with home office, then I decided to write this post to talk about these problems and to suggest things.
In the past 13 years, I’ve worked a lot of time in home office mode. So I’ve been through all these problems and this post have some answers for developers and team leaders.
Whenever you work from the office, you usually “work” 8~9 hours a day. But let’s be honest to ourselves, who produces 8 hours in a row? …
Some time ago I presented a talk about API Design and its basics. As it was presented to small group of people, I decided to write a post about it.
Why should I care?
First of all, your API is the front door of your company. If you expose your API externally, it should be safe, have a well designed contract and all the points that will be better explained below. Even if you don’t expose it externally, you probably have internal applications that must consume it, if things are not ok, you’re gonna run into problems.
Companies earn money with APIs charging for the requests that are made to the API. This point explains itself, with a bad design, you may need to version it more often, more chances to break, etc. If you run into problems, nobody will call it and you get no money. …
In the past few years I’ve been working and studying RESTful APIs, and I have seen some common mistakes in different projects and forums, then I decided to write this post based on some experiences and on stuff I read.
Here are some anti-patterns, their explanation and examples.
Your URI does not explain whats going on, simple like that.
RESTful APIs are about resources, when we’re building our URIs, we need to tell a story about that resource, looking at the URI the consumer must understand all about the given resource, where it came from, which is its identifier, which options it has. …
Learning is always a challenge, even if you are already experienced. Today we’ll talk a bit more about the learning process.
I have already helped some developers to learn and grow their careers, in other hand, I had help from good developers/architects to learn a lot and get in a good position.
Which one is more important, practice or theory? There are lots of people whose brains only learn by practicing, is that true? Yes … and no :)
Different people learn in different ways. Some are visual, others need practice, others prefer to watch a video, others need to draw on a note book to understand. …
Have you ever worked in a team with many developers and there was that one who just wanted to build walls? In this post I’ll talk about that kind of developer, who just wants to do the very basic and don’t care about the rest.
But, what does “build walls” mean?
I just want to put the bricks there and that’s my job.
Participating on a project is more than just “delivering” user stories. I have had a lot of different experiences with developers that just wanted to deliver user stories: deliver deliver deliver.
But looking at the big picture is very important, just delivering is not enough. Sometimes it’s good to look at the product and question yourself — how this user story impacts the business/product. Some times it’s good to ask yourself some of these questions before…