It’s weird to call a process a perk, but our focus on reusable code is one of my favorite things about working at Table XI. Limiting ourselves to the absolute fewest number of components to build software is a challenge, and it’s one that’s made me a better developer.
Infrastructure is the framework running under your entire business — so it only makes sense that an infrastructure audit would look at the whole picture. If your infrastructure touches your email, applications, timesheets, employee communication and anything else, the audit should as well.
No one puts a system for diversity recruiting in place when they start their business. We all just try to do our best to hire talented people we’ll get along with, and hire them fast. It’s only later that so many companies realize with a shock that all their colleagues look alike.
We always made an effort to include many voices at Table XI so we never had a totally homogenous team. But as we grew, we realized we needed an actual strategy for recruiting diverse candidates, not just good intentions.
Everyone deserves an inclusive workplace. To be seen for who you are and made to feel a part of something is a fundamental courtesy every business should extend to each team member. And most want to — even a business entirely motivated by profit can recognize the statistics that show employees perform better when they buy into a shared sense of mission.
So, why are so many companies terrible at creating an inclusive culture?
Thanks to your reviews, we got quite the honor this week when Clutch released its best of lists for Chicago tech. The company — basically a Yelp for service providers — ranked Table XI the best software development company in Chicago and the best Ruby on Rails development team in Chicago. Our mobile team also made quite the showing, placing fourth for mobile development in Chicago and fifth for iPhone-specific development (though we’re mostly working cross-platform in React Native these days.)
Too many companies realize why they should do user research too late, when they’ve already missed out on opportunities to make product development more effective, deliver high-impact launches and capture market share.
Every industry has a human element, but designing for healthcare means understanding that connection is the heart of medicine. All the new medicines and advancing technologies in healthcare mean nothing without the interactions between doctors and patients. When a person walks in complaining of an ache or pain, it’s the doctor’s job to use their knowledge and intuition to tease out details and offer a diagnosis. That process is intrinsic to the profession, and it’s why the doctor-patient relationship is so sacred.
It’s also the same process we use when building software for healthcare providers.
If you’ve been working in medicine for decades, it can be a bit of a shock when all of the sudden you’re tasked with building software for healthcare providers. It’s an entirely new discipline, with different possibilities, different norms, even a different language.
The truth, though, is that the best hospital software starts with you.
There’s always a learning curve when any industry turns to healthcare software companies, but it’s a particularly deep chasm between tech and medicine. Both sides are highly technical, but that’s where the similarities stop — different cultures, different languages, different expectations about the role of software in healthcare.
One year later, and I would say 60 percent of my time is spent building React Native apps.