Memel

It happened exactly as I expected. I found a plagiary of my original work on parallel computing at Microsoft's MSDN site . And they even have made a quick-hack implementation for .NET pratform, and aslo exactly in the way as I've proposed in my paper.

When I first published my work one of anonymous commenters asked me whether I had received an offer form Microsoft. I sounded as a joke. And I answered that Microsoft will NEVER contact some unknown small company, especially if it is located in the middle of nowhere...

So far the rethoric question still is: should I ask Microsoft for rewards? Or, at least, for being mentioned in their work?

I've found this in a very interesting and valuable blog by Susthama:

Here is a rough 12 step guide to help you with the problem of life – addiction to self.

...

Step Seven
Accept that I am limited, imperfect, cruel, hurtful, jealous, passionate, and deficient, this is what keeps me humble and modest. I don’t expect to be Amida or perfect.

...

While I agree with the 12 steps in principle, the seventh step confuses me a little. This step assumes that all the people are weak by definition. And what if some person accounts himself as strong enough? This again leads me to my old thoughts that all religions (including even Buddhism) are designed for weak people (or grey masses).

Maybe strength could be accounted for another weakness? Or maybe a strong person is not normal amongst a human world? I doubt it. In my meaning - personal strength is the ability to fine control and to have a good balance between good and evil. Or in other words - to be beneath the good and evil and to supervise them.

Also, does it mean that Buddha was a weak person too? Otherwise - where these rules come from? Rules can come only from strong and supervising person. Am I missing something?

2. When you think you're programming...

And what it really is:

• Tweaking the code to run innermost loops a little faster: this is preparing for competition in the market;
  
• Resolving border conditions, fencepost errors and race conditions: debugging
  
• Rearranging and structuring the code, merging duplicated parts, making functions shorter and clearer: preparing for better product maintenance
  
• Indenting code, providing comments: preparing for presentation
  
• Optimizing the code, rewriting parts of code: consequences of bad initial design
  
• Fighting with tools and frameworks, making workarounds, avoiding known bugs: debugging, testing
  
• Creating sophisticated constructs, such like "one-liners" in Perl: no point at all; overcomplicates further maintenance
  
• Writing the initial code from scratch: yes - this is a part of programming!
  

To be continued...