Most of the new, shiny software libraries, designs, and development methodologies are either junk or old ideas. And your project may end up a disaster if you don't understand this.
Wow! That's provocative. Give us a moment. Hear us out.
There are 125ish so-called "web frameworks" listed in Wikipedia. More than one-hundred-and-twenty-five ways to do mostly the same thing. Heck, there are more than 40 frameworks for Java alone! Ask yourself, why was the 2nd or 10th or 25th or 40th framework built? Obviously because all those before did not scratch an itch. But, are there really more than 100 disjoint itches?
Of course not.
Dissatisfaction with current solutions motivates each new solution. But the resulting new golden child doesn't solve the problem because of a failure identify the root cause of the dissatisfaction. Instead it essentially follows the same flawed design of the previous framework (we have written more about this particular problem).
Whatever the cause, clearly, there aren't 125ish ways to solve the same problem optimally. Indeed, many of the frameworks today are just a mess.
Understanding powerful and timeless ideas from the past and seeing through shiny but flawed distractions is critically important because failing to do so results in over-budget, or, worse, outright failed projects.
And it goes without saying that choosing a defective technology, will, by definition and at a minimum, result in increased program construction costs. In the worst case, choosing the wrong technology will result of project failure.
This, then, is the root of our philosophy:
Our principals are university-trained computer scientists, software engineers, and business executives that have decades of experience in software construction and program management.
Through the years, we've built systems of all sizes and types. From medical device software subject to the Federal Drug Administration software development life cycle standards to throw-away prototypes used to sketch new business ideas to investors.
Because projects are different sizes, with difference complexities, and different challenges, we do not force a single development process and system design on all projects. Instead, we work with our clients to select the development process that will ensure project success. Whether back-of-the-napkin informal or the formality required to build software that can be used in systems where failure could result in the loss of human life, we've done it before.
Our principals are former executives who have held C-level appointments in public companies.
This is another key difference in ALTOVISO. We know what it's like to make payroll. We know that this isn't a game or a hobby, but rather a business...a race to produce a product that solves a problem and ultimately helps a business produce a profit for its owners. We have a lot of fun building things. But there is no point to it all unless those things make economic sense to their owners.
We think this real world perspective makes us different and makes us better. We look forward to discussing your next project. Drop us an email at email@example.com