Architecture and technology advise
When a specific problem is to be solved, it is natural to ask:
- What technology should be used ?
- Will it be scalable ?
- Where will it be hosted ?
- Is it maintainable ?
- Is it future secure ?
We advise on the choice of technology, including for example the use of third-party components. Too often we see companies that unnecessarily consumes resources on developing parts of the systems – which they could usefully be purchased from component suppliers.
Standards
If you put two men to accomplish the same tasks (not necessarily IT related), the end result probably the same, but the way we have come to what would typically be far different. Within For software development can be a real nightmare. There is nothing that is black / white, some developers solve problems in one way other in a completely different. Over time, developers of the same groups, hopefully have rectified their standards. It does not change that for example new employees do not know these esoteric / ingrown standards. Otherwise mundane tasks such as: code sharing among developers, can be difficult, if not agreed on the concrete standards. Standards can often develop decidedly religious wars in the development groups.
Codereview
When software applications are developed, the focus easily on the business aspects. When the application meets the requirements specification and error-free operation – one may be inclined to say that the application is complete.
It is often forgotten that most applications have a relatively long life. The probability that users want changes / additions in functionality is increasingly seen over time. One should always make demands on software developers that maintain a quality to the daily and future maintenance ensured.
This quality should ideally be made at the outset of a project and secured the way. The quality should be internally secured using reviews as the application of reviewed at a technical level. It requires: a broad, long and deep technical experience to conduct these reviews. In the development groups, this can be a “painful” process. We offer therefore, on the basis of our many years of experience to undertake these reviews as a neutral external partner.
A review is considered by most as a negative process where weaknesses are identified. Our reviews will also highlight the positive areas, which will thus form the basis for how future development should be carried out.
For various reasons, the quality of the source code regularly made. It is important that the error is identified as early as possible in the process that the code remains the future, as well as creating a uniform / understandable source code that can be maintained.
