Blog

  • Attracting attention of potential customers with the help of articles

    21.05.2010
    Many of those who have read my previous post "Receiving feedback from potential users" think that whatever we do to attract attention of potential customers, there is no result. But it is not so. There is some attention. We have already found one good way of attracting attention of potential users. It is our articles and blogs. But this source remains the only one, and it is this fact that worries us. So we are searching for new ways. Read more

  • Receiving feedback from potential users

    20.05.2010
    It is not very easy to receive feedback from potential customers if you are just a small startup. I believe it is much easier for a large company - you may spend money on marketing research. You may communicate with customers you already have that purchase other yet similar products or services. But when you are a fresh startup, there is no client base and no money either. You face the task of trying to get the maximum possible result from communicating with those who can potentially become your customers and adjust the way of your development if the demand in any way does not fit the supply. In other words, you must find out what you should fix and offer to people to make them most interested in you. Read more

  • "What is it?" – a new option of PVS-Studio code analyzer

    19.05.2010
    While developing, maintaining and selling the PVS-Studio analyzer of C/C++ code, we find it very interesting to communicate with potential users of our software product. The main topic of discussion (besides licensing and pricing policy) is what a particular message generated by the analyzer means. It is not a secret that any code analyzer is a complex tool and messages about errors in a program are not always clear to users. Moreover, it is not always obvious how to correct the code. Read more

  • Developing code testing and verification tools

    18.05.2010
    OOO "Program Verification Systems" develops and maintains the PVS-Studio tool intended for detecting 64-bit and parallel errors in the code of C/C++ applications. The PVS-Studio package is a set of specialized static code analyzers that allow to perform verification of source code at the stage of program designing already and therefore significantly reduce costs on program debugging, testing and maintenance. Read more

  • How to disable IntelliSence in Visual Studio 2010?

    13.05.2010
    The question how to disable IntelliSence in Visual Studio 2005 and Visual Studio 2008 was very popular among programmers some time ago. There was even a huge topic on the MSDN forum where this issue was discussed. Deleting the file feacp.dll appeared to be the right solution. Read more

  • Parallel notes N5 - continuing to study OpenMP constructs

    26.03.2010
    Here is the next post devoted to studying the parallel programming technology OpenMP. Here we will consider two directives: atomic, reduction. Read more

  • Parallel notes N4 - continuing to study OpenMP constructs

    11.03.2010
    In this post we will continue to introduce you into OpenMP technology and tell you about some functions and new directives. Read more

  • Parallel notes N3 - base OpenMP constructs

    02.03.2010
    Now we would like to start introducing you into OpenMP technology and show you the ways of using it. In this post we will discuss some base constructs. Read more

  • In what way can C++0x standard help you eliminate 64-bit errors

    28.02.2010
    Programmers see in C++0x standard an opportunity to use lambda-functions and other entities I do not quite understand :). But personally I see convenient means in it that allow us to get rid of many 64-bit errors. Read more

  • CruiseControl.NET - build automation platform

    26.02.2010
    While developing software products with a complicated structure, you come at some moment to the necessity of automating the processes of building and integrating the projects and distribution kits being developed. Continuous integration is the practice of software development that implies frequent (up to several times during the day) automatic build and testing of the current product version. This approach enables you to reduce the labor intensiveness of the integration as such and detect its defects and conflicts at the very early stages. Note that this methodology implies using a version control system (for example, CVSNT and Subversion) to store the source codes and all the other components needed to build and test the project. Read more