Programming analogy as sudoku

As a beardo, I have to say, this makes programming far more complicated than it needs to be.

It is like solving a sudoku, except you get to write the sudoku.

So it is possible to make the sudoku really easy, if you think about what a really easy sudoku consists of and code according to principles of easy sudokus.

It is also possible to make it really difficult if you use java, fortran, or c++.

I was outright laughing by the time I got to "The squares, can't you see, the squares, they're so beautiful".

Because it's so true. It's SO easy to get wrapped up in chaos like that if you aren't truly working as a team. If everyone is off doing their own thing with no code review, it happens just like that.

However, if you add code reviews (or pair programmer, if you are so minded) and good teamwork, it's more like crafting fine art than creating a labyrinth from the inside.

I read the sudoku analogy some time ago on stack overflow, only it was much shorter and concerning the question of time.

How do you explain somebody why it is hard to know when you will have accomplished a certain programming task?

Just ask how long he will need for a sudoku, with a second in precision.

I'd say that teamwork and cooperation within programmers is like a sudoku, programming is more like writing not the sudoku but whatever comes out of that fucked up mind of any of you HN readers!