This is the last in a three-part series of posts that will explore how we do product development at DevMynd […]
Chief Consultant Sarah Mei made a recent appearance on Table XI’s Tech Done Right podcast. Mei discusses the concept of […]
“Let’s move that to version 2.0. “ Designers are used to hearing this and, although our hearts may break over […]
Small engineering teams who want to diversify have a hard row to hoe. Large organizations can throw money at the […]
Lately I’ve been talking with students at programming bootcamps about their overwhelming fear that they’re not learning quickly and thoroughly enough to find employment afterwards. I think it’s generally produced more by the intensive crunch-time atmosphere of the schools and growing recognition of how big and complex programming is than by an actual deficiency in skills.
Thanks to all the coding bootcamps out there, many tech teams hired their first junior developers last year. Many more are now considering it, and debating how to go about it. Looking at the community chatter on this topic, it's clear that onboarding junior devs into a team of mid- and senior-level folks is not a solved problem. Hell, my company is heading into its sixth cohort of apprentices, and the question of how to structure their time still provokes passionate debate internally.
Here at DevMynd, the two primary things that clients hire us for are product
design/development and developer training. What they don't realize is
that they can also look to us for an objective opinion on their team and its
strengths and weaknesses.
If your organization has customers you must have a customer-centric team in order to succeed. Customer-centricity should permeate every level of the organization, and all the processes that help your teams be productive. At DevMynd we spend most of our time working with customers and over the years have learned how to build a team that's fixated on customer satisfaction and success. Whether building a Ruby-on-Rails web application, a mobile iOS app, or a highly scalable back-end system in Clojure, customers are the constant.
Over a decade of straddling manager and developer roles, I've seen actors on both sides find a way to poke each other with sticks and make projects more difficult (and costly) than they need to be.