The Marici Difference
Software runs a lot of the world, and because of this, most developers want to be good.
he field rewards this. You can be good at best practices, you can be good in specific technologies, you can be good in a vertical, you can be good at testing, you can be good at keeping up with all the latest technologies. You can be broad and shallow, and you can be narrow and deep.
The great impedance mismatch typically occurs in the region between knowing the business and knowing technology. Even the business of technology is different from the implementation of technology. The broad and deep software engineer is rarer than a unicorn. What mostly happens is a whole bunch of developers who want to be good. In the desire to be good, developers tend to have to choose between knowing your business and knowing technology deeply. We don’t think this is fair.
So We've Specialized
We’ve learned patterns over the years and projects and we find that we are 100% successful by specializing in the 80%. We have project execution methodologies that fit most variants of specific verticals. We do test automation, tech refresh, specific software components for any point in the cycle, clean room/due diligence, and of course, entire software projects. Many activities that can result in ‘burn teams’ are the very activities we get excited about.
This allows us to really focus on the specific components that occur in every project. Doing this also lets us continuously improve on the execution of these components.
The output to all this is of course, better software. Code is fully unit tested, Acceptance tests are written in plain language, dev teams are no longer divided along ‘enterprise application teams’ and ‘product teams’. And the impedance mismatch between ‘the business’ and ‘software/IT’ becomes that much smaller.
There are of course, things that we think all organizations should do well. Like communication. Having an origin as unique as ours, we figured the best ways to communicate very quickly. Not just using Jira, GoToMeeting, etc. (Though we do use those), but even when doing face to face communication. We know what it’s like to coordinate a team across 4 time zones, and we know better than to be dogmatic about agile. We also know that that disagreement we’re having with that UX designer is the last 2% we need to make your application ‘pop’.
We fully believe that if you're excited about your project, we' ll be excited about your project. And at the end of it, there's just that much more good software in the world.
Here are few things we're proud of
Tell your idea to us, We are all ears
Here is how you can get in touch with us