By Elyse Turner
I sat down with Tijana Milovanovic, who was an intern this past summer and has been hired on as a Junior Developer, to talk about development, getting her first post-college job, and the balancing act that any NCAA student-athlete must do.
We're hiring, Android says "Bye bye" to the burger, 10 modern software over-engineering mistakes, and everything else you missed on the Monday Mobile Mashup!
In part three of this series, we talked about smart home usability and the importance of both analog and digital functionality. Today, I’ll share with you my investigation of various smart home platforms and their pros and cons.
We are hiring, designer imposter syndrome, Halloween costume ideas for designers, Android Gradle configurations, and everything else you missed on the Monday Mobile Mashup!
Product design for sustainability, iOS 10 notifications, effective Android architecture, Dan Ward on updating his home to a smart home, and everything else on the Monday Mobile Mashup!
The biggest thing when it comes to smart home usability is that you’re only successful if your smart home works for everybody. A smart home also needs to work 100% of the time, which is why the analog experience is extremely important. The analog experience is just as important as the digital experience, if not more so. When your internet goes down, your WiFi goes down, cell towers go down, zombies eat the electrical grid, or who knows what, these components can still operate.
In Part One of this series, I introduced my adventures in homeownership as I planned to outfit my 1940s-era house with the latest in smart home technology. Today, I’m going to tell you about my installation experience – and the number one challenge to installing any connected home hardware.
Smart home is no longer stuck in a dark corner of the internet, the province of a dedicated group tinkerers. You can go into Best Buy or Home Depot right now and smart home products are on the shelves. I wanted to see for myself if these products are ready from a basic, human aspect – not only how tech-savvy do you need to be to install them, but how savvy do you need to be to use them?
In this series, I’ll share my journey as I answer this basic question and attempt to shine a light on the value that connected home adds to houses old and new. How can it make our lives better without making us completely crazy? Come find out with me.
Working with JSON in Swift, TrueTime for Swift and Android, an updated Joel Test and everything else you missed on the Monday Mobile Mashup!
Xcenv, What we've learned so far from running our Apprentice Program, what two years of Android development have taught me the hard way, and everything else you missed, on the Monday Mobile Mashup!
By Erika Carlson
In 2011, our co-founders had a wild idea to create a company where people would actually want to work. The goals were pretty simple: build high quality software, have the freedom to learn, teach, and explore new technology, and give every team member visibility and a voice in company decisions.
Detroit Labs is a services company. To put it bluntly, that means the entire value of our company walks in the door in the morning and walks right back out at night; our bills aren’t paid by patent fees or monthly subscriptions, but rather from the work our team members do on behalf of our clients. And frankly, using traditional networking and recruiting methods, the supply for new hires did not meet our demand. This led to another wild idea: what if we hire, pay, and teach people, from scratch, the skills we needed. We wondered, “What if we could find people with the skills and the will who aren't yet IT professionals, and welcome them to the world of software development? What would that take?”
“There are companies now making wireless in-ear earbuds that have biometric sensors in them, so it could lead to a big leap in functionality,” said Dan Ward, co-founder of mobile app development firm Detroit Labs. “Apple has focused a lot on health and wellness, so it might open up an entirely new product opportunity.”
Mobile design techniques, the many flavors of commit(), my least favorite thing about Swift, and everything else you missed on the Monday Mobile Mashup!
The correct way to display lists in iOS, lessons from converting an Android app to 100% Kotlin, innovating on Material Design and everything else on the Monday Mobile Mashup!
Exercises for JS beginners, empathy for software developers, the typography for "Stranger Things," and everything else you missed on the Monday Mobile Mashup.
Technical debt costs a team additional development effort. Caused by the decision to write and merge code that is inferior to clean code standards, it may seem easier to implement a quick but short-lived fix at the time, but it has consequences down the road for both your development team and your business.
Last week we dove into how DL organizes agile teams to fully utilize QA. Now let’s focus on tackling QA integration from a team and company philosophy perspective.
HTTP requests, 4 years with Haskell, ideas for making better talks and conferences, and everything else you missed on the Monday Mobile Mashup!
Every company has a different idea of what agile means. With each variety of agile, QA fits in slightly differently, but I hope that you can take away a few ideas from how DL implements QA to improve your agile teams. I’ll cover team organization in today’s blog and team/company philosophy next week.
EmojiTextView, VIM Adventures, how to be a wizard programmer, practical machine learning, and everything else you missed on the Monday Mobile Mashup!