I think constants are evil (just joking but….I will explain why).

I am tired of seeing a lot of Java classes filled with the same constants repeated over and over again, instead of collecting them in a common file, which in C Language was called include files (ooooah!).

Read More

In the 1980 comments were used to reduce the “gap” between unstructured code and “rationale” behind the code.

1. C/64 Peek and poke where oscure.
2. Gosub on function pointed by numbers was bad
3. 8-bit systems was tight on command names and so on (think to write a python interpreter in Arduino/bbc:Micro, or look at the memory consumed by the COMMAND STRINGS on C/64 Basic v2)
4. C code was not expressive, but good code required little comment, as you can see here

Today comments are used to:

1. Comment obscure code -> instead of writing it better
2. Comment caching code you will end up to commit breaking production ->instead of having a cache config to disable cache on dev machines
3. Comment not working code will end up in production, producing functional breaks -> because you will forget it and  commit the bad version

When I am sent on a Red Project, the code is often obscure and not commented at all. So I dare to suggest to deprecate comments at all, replacing it with a set of meta annotation like:

@Comment("Documentation of this class/method/function/closure")
@Fixme("Reason")
@Todo("Why",  deadline=20230423)

 

 

Read More

Sometimes you need to remove nasty duplicate on a table, based on a subset of the column. On every big database there is something called “rowid” which can be used to indentify a column in a unique way. On PostgreSQL is called ctid, as we shall see:

Read More

I have used Google in the past 8 years (I know, I am a bit old). Then I was annoyed because of a bad behavior of Google with my AdSense account (shutdown without being able to talk back to someone for explanation).

Read More

Steve is not a normal solution provider.
Steve is the final destination for Project Management troubles.

Let's see how Steve can solve problems

The Ten Steve Rules

1. If you have a customer you can get my attention
2. If your project is run out of time and you need to finish the product yesterday, you will face a disaster. Call me
3. Cannabis programming is too light
4. You cannot offer a Lunch to Steve, unless you have four ticket resturants and at least one more for you
5. Are you saying you need more time to finishing the use case? These are details. If you cannot get it in the required time, I will fire you (Loading a gun): in the real sense.
6. Peace and calm are an useless evil.
7. True Metal Hackerz get the work done in less time then you
8. Linux has a a cold bird as Logo. This is enought to kick it off the project.
9. I prefer Illy over Java, sorry
10. There isn't a tenth rule