Ini Lho ITS! 2022

When I first started coding, especially for making websites, about two and a half years ago, I thought everyone wrote their code completely from scratch using plain HTML, CSS, vanilla Javascript, and pure PHP. However, as I spent more time learning and gaining experience, I came to understand that’s not often the way things are typically done.

For many of you, it may seems quite obvious, especially when you think about long-standing tools like WordPress, which has been offering pre-built functionalities and customizable templates ever since. Nowadays, there are even convenience options with no-code (which actually means someone else's code) technologies like Wix, making it easier for us to build websites and applications without any coding knowledge.

Those tools can be handy for creating basic websites, such as blog or company profile sites. Yet, for developers aiming to build more complex websites, it’s crucial to construct projects that are both easy to manage and can adapt. This often involves using a variety of frameworks and libraries—or even boilerplates—created by other developers, that provide more detailed solutions for specific tasks.

I’ve got my hands dirty on some popular frameworks, including but not limited to Laravel, Express, and Next.js. These all come with a bunch of tools and guidelines to follow that help in structuring and organizing the development process. Express, for example, simplifies web servers setup in Node.js without the need to write all the code required to handle HTTP requests, manage routes, and handle responses at a low-level.

I also have made use of packages, such as Spatie, Sanctum, React, JWT, Socket.io, and multiple ORMs (Object Relational Mapping), which offer specific functionalities or parts that I add into my projects. For instance, JWT (JSON Web Token) helps me handle authentication and security within the project by providing a specific tool for generating, verifying, and managing authentication tokens.

Using frameworks and libraries in software development comes with both advantages and disadvantages. Some people prefer to avoid those dependencies altogether, while others do acrobatics with them enthusiastically.

Some developers prefer not to use dependencies due to concerns about unnecessary complexity that could slow down performance or make the project contain a huge amount of extra code that isn’t really needed. They also worry about the potential risk of security issues, especially in older versions of the tools that may be used on their project. Other concerns involve getting stuck using one particular external code that lead to difficulties in maintaining or evolving their projects over time.

On the flip side, since there is no need to reinvent the wheel, many developers find libraries and frameworks to be useful tools that can significantly speed up development time and establish a solid foundation. Additionally, they often come with communities of developers who offer support and advice for their issues. For beginners, utilizing them can be particularly beneficial, as they provide a structured learning environment that helps us understand coding practices better.

Whether or not to leverage someone else’s code to your projects depends on the specific requirements of each development. Whatever works for your needs. 

For those of you who are considering using it and are aiming to minimize its drawbacks, here is a tip from me: taking the time to 

read the documentation thoroughly a.k.a RTFM

, instead of simply just copy-pasting code blindly; can save us from problems later on. There have been times where I spent many hours coding and debugging, only to find out that the solution was clearly outlined in the documentation.

Leverage Someone Else's Code

Table of Contents