how to save a lot of time and make fewer mistakes
In this summary, I list some of the things that have helped me in my career. It reads fast, but applying them well can take a lifetime. I have been developing applications for almost 15 years, and still, sometimes, I have to stop and think in the essential parts of this profession.
A few days ago, I had a fascinating conversation with a girl who is visually impaired. When I got home, I spent some time thinking about what would happen if I had those problems or other problems that prevented me from using a keyboard. What would happen if I fell off my bike and broke my arm? Would I still be able to code?
Dictation software has been around for a long time, but it’s usually used purely to transcribe speech. Writing code is different since there are a lot of non-dictionary words and syntax rules.
Nowadays, we can use…
You have an Excel file with many columns and rows, and you need to validate it. How would you do it? The following article will describe a simple way to do it that works fine with both small and big files.
First of all, we need to know which Excel columns we want to validate and what kind of validations to apply. In this example, I will use a file with five rows and five columns, but the method works just as well if it has 30,000 rows and 100 columns.
For simplicity, I will construct it all using only…
I have been working in software development for many years now, and during this time, I have learned to apply a series of steps that help me during the development or planning of a project.
In this article, I have written 19 simple habits to save time when building software and for maintaining a good relationship with my coworkers and clients.
Whether you do things right or wrong, always do them the same way because if something needs to be fixed or refactored, it will be easier if it is the same everywhere.
One of the first things you should…
During my professional career, I have worked with many different types of developers. I have loved working with some of them, but with others, I only hoped to finish the project and not work together again.
In this article, I will list some of these types.
This kind of developer is always promising things to everyone — customers, your bosses, or other developers. But when something really needs to be done, if they can, they jump to another project or try to delegate all the work to other developers. It is very dangerous because it can get you into serious…
In the software world, as in other disciplines, the tricky thing is not to have an idea; the difficult thing is to implement it. In this article, I will list the steps I take to develop an App, from when the client comes to tell me an idea to the final stage of development.
Remember that the ultimate goal of developing an application has to be must provide some benefit to the customer, such as cost reduction through productivity improvements, acquiring new revenue, or improving your relationship with your customers.
When my bosses told me to pick up everything and work from home almost a year ago, I didn’t think it would be a good idea. But I was wrong. A little later, the word “telework” became fashionable and the vast majority of people who could do it went home to work.
At first, I thought the world was coming at me because working with children at home is not easy. The children stopped going to school, and teleworking with a five-year-old at home was a challenge. …
Today my idea was to write a technical article, but it has been a hard day at work, so instead of doing that, I’ve gone for a run in the bush. Running in nature, I started to reflect on what you learn in this profession and what usually happens to us every day; Here, I compile some of them.
A few years ago, I led a project that ended in total disaster. It was not only my fault, but I was in charge, and in the end, I had to tell my bosses that it was better to close the project because we weren’t going to get anywhere, and the hours had skyrocketed.
The project initially had 9600 hours assigned to it at a fixed price, and although it seemed like a lot of hours, no one in my team had estimated them. This was the first big mistake, accepting the responsibility of something without making the previous analysis.
Not long ago, I decided to change jobs. I had a “good job”: well paid, comfortable, and with a free schedule. The decision was not easy because I am no longer twenty years old, but I did it. In this article, I tell how was my last day of work: A mixture of sadness and fear to leave a “good” job and joy to start a new project.
Basically, because I was bored and didn’t want to regret not having done it in the future, doing this is complicated, especially if you have responsibilities and bills to pay. Still, luckily…
Software engineer - software Enthusiast - Sci-Fi writer.