While we know there is much year left, we wanted to recap some of the great blog posts that have been published during 2015 so far. So please, grab a warm beverage, prop your feet up, and enjoy some strait-up, Quick Left nerd wisdom. From our tool kit to yours.
Measuring a team or single developer’s success is tricky. It’s well documented that any kind of performance measuring is ripe for being gamed. So how do you determine if a team is firing on all cylinders? Review some good and bad ideas in this blog post.
Deciding if you want, need, and can afford to hire outside technical help can sometimes be a quick decision fueled by a need to firefight, but there are some strategic choices that can make the experience more successful for both your company and the other party.
Here at Quick Left, we’re big fans of React, and wanted to contribute to the work that community is doing by open-sourcing one of the main features of our product management software, Sprintly.
React is pretty popular here at Quick Left. Most new development on Sprintly is done with React, we recommend it to our clients, and Sam even leads React training courses. As with any new language, sometimes you have to go exploring to find that aha moment. Here is one developers’ study of the difference between Elements and Components in React.
Redis can be a great way to keep in-memory lists. However, what happens when you need to be able to quickly search that list and be able to expire individual items after a given amount of time? None of the Redis classes allow you to do this out of the box, but it can be done. This post will show you how.
Sketching is misunderstood in the Tech Industry. Sketching is something everyone on your team should be doing! You’ll hear it from professionals across the industry, that problem solving starts with sketching ideas. Unfortunately it seems that not many teams are actually taking advantage of this great practice.
When we begin work on an existing codebase, one of the first things done is a CSS Audit. This audit process assesses how organized the project’s CSS is, how up to date the pipeline for evaluating and building it is, and how well structured and disciplined the team is that writes the CSS. Here are the steps you could use to run your own CSS Audit.
Explore some common misconceptions about MVPs (Minimum Viable Products), some different ways to approach building one in software, and how to best use this tool if you’re the CEO or CTO of a startup, a product manager for an established company, or a consultant.
The thought of working with many clients and many technologies in semi-rapid succession is exciting and represents an ideal opportunity to learn a lot, quickly. Here are a few high level learning lessons from one of our developers’ first 30 days in consulting.