Writing code is not much different from authoring words. It’s a way to communicate, to the device so it knows how to perform its tasks, but also to current and future developers so they can understand the intent, effectively provide feedback, efficiently make required bug fixes, and eventually expand it as more features are added.
Functional groups within a software solution must have clear API boundaries. One key to success and maintainability is to own those boundaries and carefully reserve the use of third-party technologies as implementation details that can be replaced if need be.
Code exists to solve user problems, and it is most successful when crafted with a minimalist approach. Every line of code you do not write is a line of code you will never have to read, debug or refactor.