In software engineering, it’s a quite common problem to pick a tool that doesn’t fit properly with a projects’s purpose. Picking a toolset might seem like a small thing at the beginning of a project, but later can end up being an over-engineered or under-engineered one. And refactoring an already developed app to resolve these issues is not easy at all if not almost infeasible considering the time & resource one has to invest. In denkwerk, we always face such challenge as we step into a wide variety of projects from time to time.
There is only one way to tell if a tool or toolset is fit for a project. To try out the tool & understand the pros & cons. No matter how much we read about something or research, it’s always hard to judge a tool or toolset without hands on experience. So, we try our best to do experiments with different tools in denkwerk, especially when we do our in-house projects.
Then we were rebuilding our company website and we thought that for this particular project we have a bit different requirements than our other projects. This website needs good SEO, better rendering time than our previous heavy website with a lot design components, will mostly get and show data with a very limited interaction, will host a blog section as well. So, considering all of these, we picked NuxtJS for the project as it offers a good building block for server-side-rendering which solves a lot of the issues related with SEO and gives us all of the flexibility of VueJS framework. Also, as most of the data for the website are kind of static and hardly changes, we thought it would be wiser to use a service like Contentful to store all our data which removed the need to build a backend api service on our own. This reduces the maintenance cost and effort of the project.
So, to summarise this writing, we can say one thing for sure, at denkwerk, we are open to all kind of ideas and technologies and we emphasize a lot on picking up the right toolset for the right job.