Welcome to The Deep Blue C++

-
Waves at Getaria/Guéthary, Aquitaine, France


During my years as a software engineer, I have learnt quite a lot of things - and I keep learning every day. I learn from practice, discussions with workmates, reading... I especially learn from mistakes: code that doesn't do what I expect, code that doesn't do anything at all, code that does it but with some occasional crash or two... If you're a programmer, you know what I'm talking about.

What I've learnt has substantially changed the way I write code. In my first years as a programmer I tried to avoid mistakes, but I hadn't made enough of them yet to discover the best ways to prevent them. Now I know better. I know there are some things that bring you into trouble very quickly. Other things will silently wait for the worst moment - maybe months or years later, to come to the surface in the form of even more original problems. Disorganized code, uninitialized variables, pointer arithmetics, implicit casts, syntactic overloading, inheritance in which functions hide other functions, too complex expressions, unclear function or class semantics... the list of things which you'd better avoid in the first place has become rather long during the years.

I decided to start a blog where I'll organize and share my experiences and ideas, so that I won't forget them. As a plus, you'll be able to read them and give me your feedback. I will appreciate any comments you leave in this place. I'm sure I can learn a lot from them!

There are already many C++ blogs, often written by people who know much more about software and C++ than I'll ever do. I hope my contribution will add some practical aspects which I feel may be useful, especially for novice programmers.

Software programs have two kinds of audience. They are written for a computer to execute them, but also for people to read and hopefully understand them in the future. The best programs are those which work well in both ways – the machine does its job, and humans can make that work evolve into something which suits new needs.

We write software to change the world, because programs are run to change something. Their lines will be spelled tomorrow with effects that we cannot fully foresee. We rise waves which will go a long way until they reach a far away shore - one which our eyes may never see.

Let’s take a dive. Welcome to The Deep Blue C++!

Comments

  1. Anonymous11 March 2014 at 08:57

    Thank you for your two cents worth! (or your "Little grain of sand") :P
    I'm sure you can help Indian Politicians, too! See this link below:
    http://www.theunrealtimes.com/2014/02/04/indian-politicians-write-c-programs-to-compare-2-strings-part-1/

    Cheers.

    Uri

    ReplyDelete
    Replies
    1. Daniel Daranas12 March 2014 at 10:42

      Thank you Oriol for the very first comment in The Deep Blue C++! It all began in Carrer de Figueres, you know :-) Every politician should be able to compare two strings in C++, that's the bare minimum! :P

      Delete
  2. varun16 April 2014 at 12:06

    Hi Daniel! Looking at your blog, I was wondering if you can help me in writing code for Text Clipping in Computer Graphics in c++? I don't know how to start and I can't seem to google anything on writing its logic.
    P. S. I need it ASAP. Can you help?

    ReplyDelete
    Replies
    1. Daniel Daranas16 April 2014 at 19:36

      Hi varun, sorry, actually I can't help you because I don't have any experience in the subject you mention. I'm sure there must be somewhere (libraries, book shops) where you can find good learning material. Good luck!

      Delete

Post a Comment

Popular posts from this blog

#2. Make all type conversions explicit

-
Assignments, function calls and expressions in general should not contain implicit type conversions. All type conversions should be explicit. Type conversions should be isolated in their own line, which should consist only of the assignment of the result of the type conversion to a variable of the target type. A statement should not mix type conversion with other operations. For example, if you need to convert an object to one of another type to pass it as a function parameter, do not do it in the function call itself; instead, do it in a separate instruction in the previous line. Type conversion occurs when an entity of type A is, well, converted to an entity of type B. This may occur in function calls, expressions using operators, or assignments. An explicit type conversion is one which you can read in the code. An implicit type conversion is one which does not appear in the source code, but is done automatically when the software is executed. Making all type conversi
Read more

#13. Organize your code in classes

-
The minimal unit of code is a statement . The minimal unit of code which can be tested and reused is a function . Functions are rarely practical all by themselves; they are usually organized in modules which offer a set of operations which make as a whole. The class is the main semantical unit in object oriented programming. A class is an abstract data type with an associated implementation. As Bertrand Meyer puts it in Object Oriented Software Construction, 2nd Edition : Classes should be the only modules. These concepts will not be obvious in the integrated development environment you use to create your code. Usually, these IDEs let you create projects, and inside them, they let you add units or files. You know, of course, the C++ syntax; you know there are two keywords, class and struct , that let you define a type with its associated data members (fields) and operations (functions). You are probably aware of the difference between class and struct : the default visibili
Read more