November 17th, 2017 / Kat Crawford

![Popcorn]({{ "/assets/imgs/mashup.png" | absolute_url }})

Why adopt a new technology?

The eternal question asked by every business owner, employee, software developer, politician, mathematician… yeah, ok, it's kind of the question, we get it.

There's really only one way to know for sure if a technology is appropriate for your particular project and that is to give it a try. We recognize that is highly inefficient and sometimes completely impractical, so we are going to try help with that headache here.


November 13th, 2017 / Kat Crawford

We’re hiring, which is great. But holy cow, what resumes we have had to wade through.

So, for all of you prospective software developers out there, here is a list of Dos and Don’ts to check off before you send one more underwhelming list of attributes.

person, surrounded by crumpled writing paper, holding up help sign


November 6th, 2017 / Kat Crawford

So lately we've been talking with companies about project ideas. One of the big questions that comes up pretty often and early in the conversation is:

"Do you want a native, hybrid, or web app?"

This isn't a question that people generally put much thought into--or even quite know how to approach it if they aren't developers. To help out, below is an overview and a list of the pros and cons of the three types of apps you might want to have developed.


November 2nd, 2017 / Nicholas Elliott

Whether you realize or not, if you develop software then you have created a Functional Specification. If you don't know what that is, far better writers than I have covered it in detail, but to quote Joel Spolsky:

"A functional specification describes how a product will work entirely from the user’s perspective. It doesn’t care how the thing is implemented. It talks about features. It specifies screens, menus, dialogs, and so on."