Of course this does not mean that you do not have to have a deep knowledge of programming, having experience supports you to be able to more accurately ponder about when and how to use a particular language or tool. The point is that lines of code endss up becoming a long-term compromise. However, writing lines of code is one of the alternatives for solving customer problems, creating a website via WordPress, using a “Software as a Service” (SaaS), having a framework support, using a fast RAD development tool like Scriptcase, Having a helpdesk system, using a project management application such as Trello, or even good and traditional Excel, are all options that allow you to create less legacy code and, therefore, less maintenance. And delivering that result doesn’t necessarily mean writing lines of code all the time, and of course, doesn’t rule out the need for it. The fact is that your real job is to develop solutions to your company’s business problems. The source code you build is nothing more than a byproduct of your work.
“It’s stressful”, “will require a lot of investment to learn usability”, “not useful for certain tasks”, “won’t work for us”, etc.įor various reasons, this thinking still persists ‘till this day, no matter how much the growing need for speed, practicality and efficiency in delivering results is identified.
It is very common to see people complaining about the use of tools or certain ‘ready-made’ techniques for development. Well, i’m sorry to inform, but you are not paid exclusively for programming! This may seem a little illogical at first, but it does promise to bring a reflection on the reasons for this article. For all those who develop system and softwares every day at work: Have you ever wondered what makes you receive value at the end of the month? In the end, are you paid for your system or code?