When I was working in a small agency, years ago, in Germany's warmest city, Freiburg, my boss introduced the team to agile working methods that he had read a book about. We had a whiteboard with some columns on them named To Do, Doing, Done. Some stickies were on these columns. We had a fast-lane which was filled with tasks all the time. I felt I was doing quite some work when fulfilling the tasks and moving a pile of them from one column to the next. Anyway, projects didn't finish on time. The feeling of being productive vanished as soon as we felt we were delivering late. Was there a problem in productivity?
With Heroku you can easily setup deployment and hosting of your application in the cloud. Here are 6 steps how to quickly set up your Node.js application on Heroku.
I've written a transmitter which collects data from Contentful and indexes it in Algolia. It is written in Node.js and really simple.
The application syncs content between Contentful and Algolia. You can configure the service to run with Drafts (Preview API) from Contentful and put it in different indexes in Algolia.
In the past I have written about how I use npm scripts for my build tooling. With this article I want to write about some problems I had and how I solved them. The problems I want to talk about further:
- Concurrency
- Extensive build configuration
- Build environments
When ever I do a front-end review for webpages I start compiling a new checklist of things that I need to take into account for the review. Now I tried to collect some of the most important questions to check for and release them publically.