5 Lessons I've learned by working on a product with non-technical people
To get started with any work, you need to know what to do. In order to find out what the actual problem the person is facing, you have to ask questions, a lot o
To get started with any work, you need to know what to do. In order to find out what the actual problem the person is facing, you have to ask questions, a lot o
When applying to development jobs, you're often asked to do a coding test to prove that you know what you're doing. I think this is terrible and here are better
During development sprints, you plan work that needs to be completed by the end of the sprint, and you try to leave some extra room for bugs that might occur and need to be fixed. This post describes how I plan to use time more efficiently and to keep developers focused on their task at hand during sprints.
For the past four years I’ve been working on a side project called PunchlistHero, (the new “stable” version will be released in two weeks) and I think it’s still very interesting and it helps me to learn new things about marketing and programming. But how do I find the time to really work on it?
While learning how to use Solr, I’ve come across many things I would’ve like to have known beforehand. So this post is a collection of things that I’ve encountered (and will encounter) that some of you might find helpful to have a solution for as well.
While migrating AngularJS to Angular v6, I’ve come to the point where I start to convert entire pages to Angular. For this to work you can downgrade the entire page to an AngularJS directive and component and inject it into the AngularJS UI Router, or you can use a wonderful package I’ve found. Let’s use that package!
In my previous post, about building a hybrid application with AngularJS and Angular v6, I set up the basics of having a working application. But what happens when some actions in one of the frameworks affect the state in the other? Bring in Redux, the centralized state manager.