We have very advanced toolsets that target Java, C#, GWT, and flash. These toolsets keep the code clean while we add more and more features. We do this so in the future, it is easy for you to maintain and add new features without high costs. Below is a list of the tools we incorporate into every project. The best part is if you decide not to use us as a vendor anymore, you can keep the toolset intact and keep using it with your next vendor.

Programming Languages

The languages we are experienced with can be found on our Solutions page but please read the rest of the page to find out about our advanced technologies that make your projects of higher quality at faster development speeds. Unlike other offshoring companies, we heavily invest in our toolsets to make sure your projects are developed faster and for less money so I do encourage you to read on.

Design Checking Tools

We have personally built design checking tools. We work with you to write the initial design in xml(takes about one day usually) and this tool guarantees developers don't break your designs. If we run into design problems, we immediately notify you and discuss the problems we are running into and suggest needed design changes. This tool trains our developers to be master designers. All of our products communicate through well defined apis and this tool prevents components from getting around those apis and forces them through the apis. A full article written by our company's founder can be found on devx at http://www.devx.com/opensource/Article/33729

Automated Builds

On every project we use, we setup an automated build system or if you have one already, we integrate with yours. This ensures all the tools we set you up with are run as soon as the developer checks his code in. The tools immediately catch developer mistakes(coding mistakes, design mistakes, etc. etc) and send emails out to the whole team. At your request, these emails can also be sent to you as well. There is also a website indicating the build status of broken or passed. Our developers always try to keep the build passing so our customers can run the build at any time and play with the latest code.

Source Code Checking tools

We set up every project with tools that look for common developer mistakes(Please Contact Us if you disagree with our rules. They are all configurable to your preferences. A few examples of stuff that our tools catch are

  • nasty arrow anti-pattern(many nested if statements).
  • System.out.println statements instead of using a Logger
  • More than 70 lines in a method(methods should never be too long)
  • More than 700 lines in a file
  • A class field that is only used in one method(this field should really be a method variable and not a class field)
  • Many, Many Many more.
  • Don't worry if you have a legacy system. Many of our tools are designed for this as well. First time systems usually result in many many violations of our tools so what we do is configure the tool to allow X violations(where X is your current number). This ensures more violations are not added. Also, at your request, we can also set up the system to reduce the number of violations by Y every 2 weeks. This allows you to still deliver business value while cleaning up your software at the same time.

    Our design checking tools are similarly built to help us refactor bad designs when needed at your request. We prefer to balance delivering business value(ie. Helping you make money) with saving maintenance costs in the future. We will lean towards the one you desire most as every situation is unique.

    Finding Bugs Tools

    Our tools run looking for common bugs like typing hashcode instead of hashCode(a common bug that is very hard to debug once introduced). These tools run to increase the speed of our teams and deliver better quality.

    Code Coverage Tools

    Our code coverage tools report how much of your code base is covered by automated tests. We can also configure the builds to break if a certain threshold is not met. In this way, we could guarantee that X% of your code is covered by tests.

    Simulation Libraries

    We specialize in testing systems and wrote a special library that can simulate large apis. This tool has been tested in many environments and is great for simulating failures and success scenarios. You can also visit the MockObjects Article the founder published on devx. Lastly, feel free to download this mockobject library for free since it is open source

    View Daily Changes LIVE

    We have special tools that deploy software changes after every developer change. You can see your product live every day(bugs and all). This gives you immediate feedback on whether we are meeting your needs or not. You can call us anytime to clarify what you are seeing on the daily deployments. One example is our China customer http://www.teekit.com. (NOTE: The server is in China for Chinese consumers so there may be some delay in accessing the server if you are in the US).

    Q: How much do outsourcing companies spend on technology to speed time to market?

    A: 0% is the normal percentage of revenue spent on those types of tools. Their goal is to grow profit. Helping customers by creating new technologies that speed up development can cut profits since they need to invest in creating the tools. Our company prefers to create a culture of innovation and advanced tools.