Project management tools, tools for managing processes, for managing teams, software for tracking and monitoring tasks, productivity apps for developers, emulators, libraries, modules – all of these are essential in our corporate environments today and certainly crucial for results in organizations that work with technology and software.
I have personally been working in the industry since 2002, and there hasn’t been a company or project where we didn’t need to use this kind of toolkit. In the past, resources were more limited because the internet wasn’t as accessible, and SaaS software was still in its infancy. You had to install applications on your desktop and maintain data on a server. This required someone to manage the system, install, maintain, and back up the information.
Today, everything has become easier and more accessible. It’s all in the cloud, often available for free, even for commercial use. It’s common to use various tools and apps that facilitate smooth workflow. This applies even to our personal lives.
But, not everything is a bed of roses. It happens to me, and I see it happening to others and organizations too, where a specific need arises that isn’t met by “generic” software. In these cases, the first solution that often comes to mind is to adapt to the software. It’s easier! However, it’s by no means the best option.
Have you ever considered the possibility of creating your own resources to meet your needs? Probably, but there’s always that roadblock: I’ll have to maintain this software, and that’s going to be a hassle.
This is where I come in with some of my experiences. There have been several such needs in the organizations I’ve been a part of, and in many of these cases, we discussed and decided to create our own tool. Did it take time? Yes. Did it cost money? Yes. But did it bring benefits? Absolutely!
One of the primary benefits of tools developed directly by the organization that will use them is knowing exactly the requirements and rules, having control over what you want and its purpose. Another advantage is not depending on third parties when dealing with something very specific, as there’s often such involvement in highly targeted projects.
Now, let’s set aside some time from the team to build a tool and get ahead? Not necessarily. This kind of work can be more viable when executed in parallel. It usually starts with a Proof of Concept (POC), perhaps with one or two people involved, and this can even be a development challenge for them. These activities can contribute to individual growth, learning about new technologies, new languages, and getting closer to the involved business rules and the company’s product.
Do I support and participate in the development of these types of tools? I’m certainly part of this movement. After 20 years with this philosophy, I can say that the result is learning in various technologies and various industry segments.
An example of a tool I developed to ease the daily operations in an organization: the company had a phone support system with several people working in the support department to handle calls, but there was no quick way to identify the calling customers. I developed an application that could be used on all workstations, which identified the calls and connected directly to the company’s database to retrieve customer data and log the support.
Another very interesting resource in the field of technology is libraries with ready-made features, especially for developers. I support and participate in another effort that creates libraries and tools for developers to use worldwide, using open-source code, but well, that’s a topic for another article…
See you.