I’m following the Software Security course at Coursera.

In this course, they explain how an adversary can take advantage of code defects and how to defend from them. I’ve looking for some like this for long time.

At the end of one of the videos there is a kind of poetry I liked. But I didn’t found it in Internet. So I’ve copied it here. It gathers all kind of code defects we should avoid because an adversary can try to use them.

So here you are: “Gashlycode Tinies” by Andrew Myers, inspired by the “Gashlycrumb Tinies” (1963) by Edward Gorey

After writting the article Why Java rocks, I have no other option than writting why Python rocks.

Before starting, I might advise you that Python is my favourite language. And this is like search your best friends defects.

Some days ago I browsed a Kinisoftware slideshow and he said that “Java rules”. He couldn’t explain why Java rules at the end, so I decided to do it in his place.

But at the end I will explain why Java does not rule.

I hope that Kinisoftware can read this and criticate it with all his soul. Kini: This is for you!

This week I realized about the difference between an ugly constructor and a pretty one. It is curious how easy doing it well is and how cheap it is, so I am going to share my point with you, waiting your comments.

Since I began to work, I have done lots of ugly things, so do not face me up if you find something mine done in a different way :D The real goal is to improve yourself day after day!

Today I have discovered lots of things about this great unknown assert.

It happens that I had a very strong debugging tool too close from myself and I hadn’t used it.

Trying to fix this problem, I write this article, but I am not going to write anything that is not already written at Java Assert Documentation or Python Documentation.