This blog has moved to a new place!
Wednesday, September 9, 2009
Sunday, December 7, 2008
The company I work for was recently distinguished as one of the top ten companies to work in Argentina (145 companies participated in the survey). This is more amazing if you take into account:
a) we all take the survey (does not matter if you are a functional analyst or manager or junior developer).
b) we are among giants in the top ten.
I am probably not the most involved guy in this (greetz go to Julio, HR, Diego, Juan, etc) but anyway it is nice to see the company being awarded again.
You can see the list here.
Today I set myself to start learning Smalltalk. For unknown reasons (availability, laziness, incompetence, who knows?) all of my OO teaching in university was using the venerable and powerful C++.
Years later I see that C++ while powerful on its own was probably not the right language to start with objects, it drags a big weight because of its C familiarity, so OO concepts might be a bit obscured by the language itself.
Being in Houston alone and without a car (Houston is amazingly not "walk friendly") I decided to see for myself what I missed in the past by learning some Smalltalk now. Probably it is not going to be the same experience, years of using other languages and platforms are probably an obstacle while trying to learn something new, previous experience clouds and blurs your ideas (like C++ clouded my vision of objects). Anyway I am willing to give it a try. According to Smalltalk gurus and followers my mind should be blown away and a whole new vision of objects may appear in front of me. I want to believe these people are not under the effects of any psychotropic (this guy's writing doesn't help the cause).
In any case, I am about to try two different environments.
Squeak (free and open source)
VisualWorks (free for non commercial use)
I know there's a Smalltalk implementation over the Net stack, including wrappers over the library to present it as standard Smalltalk library. I will try that later since I do not want to be diverted by other familiar stuff.
Right know I am in the hunting for good learning material ...
If my mind is blown away ... surely I will be writing about that.
Tuesday, October 28, 2008
I have found the following articles from Jimmy Bogard about SOC. IMHO they are very good. I just thought about sharing the links to them.
I hope you like them as much as I do.
Sunday, October 26, 2008
I have a Canon 570IS camera. A simple point and shoot model. It has the ability to save video that you can later download like you download the rest of the pictures.
The problem with these avi files is that they use a codec that is not installed into Average Joe's computer. The codec is called something like Picvideo MJpg, apparently a very fast encode/decode codec used by many photo cameras. The audio is encoded with standard PCM encoding. Full data for the avi file:
Video: MJPG 480x640 30.00fps [Stream 00]
Audio: PCM 22050Hz mono 352Kbps [Stream 01]
Now. I needed to send a video to someone who doesn't have the mjpg codec and doesn't know anything about computers. I do know that he (my brother) has a codec pack installed including xvid, one of my favorite codecs. Also, files using mjpg are not exactly light. One of my little videos of 35 seconds used 22.8MB so if I wanted to send the videos, I'd like to make them smaller. So the idea is to:
- Get smaller files
- Get files using a more friendly codec
One more thing. If you used the camera rotated to shoot the video, you can "straighten" it from the ZoomBrowser Ex (cool piece of software bundled with Canon cameras) or later, in this case I will do it later with Virtual Dub and one of its filters.
So I fire up Virtualdub and open the video file:
You see the image of my brother rotated. This is the first thing I want to fix. I select Video - Filters - Add and from the list of filters I select rotate2
(why not rotate alone? just because 2 sounded more advanced and says it is optimized ;) ). After clicking OK, a configuration dialog appears. At first I decided to go with 90 degrees of rotation and clicked on Preview, didn't work, my brother ended up head down like Spiderman. So I did -90 degrees and he was on his feet again ... but with an annoying black border. Clicking on Expand frame to fit took care of the problem. As for the Filtering mode I selected Bicubic 4x4, it is heavier on your CPU but you get better results (or so they say, I am not an expert). Image below
With my brother oriented the way God intended to, I have to take care of compression. As I said I will use Xvid. Go to Video, ensure that Full processing mode is selected and click on Compression, a list of available codecs will appear.
Select Xvid Mpeg-4 Codec and click Configure. On the Profile @ Level dropdown select Portable, this will turn off some of the advanced stuff that we really don't need and keep everything compatible. You can check about profiles here. Select Two pass - 1st pass as the encoding option. The idea is that Xvid will collect information that will make the final result better by having pre-crunched information before the second pass. The negative side of this is that it will take longer to complete the whole process.
The information that the pass is going to collect is stored in a file. One issue I found is that, by default Xvid shows something like \stats.pass when you click on the more button next to Encoding Type. This does not work, probably because of Vista's security feature, in any case, I prefer to have control of where the files are going to be created so I set the file path to the same folder where my end avi file is going to reside.
Now click OK on everything and get to the main menu bar. Click File - Run video analysis pass. Depending on the CPU horse power this can take a while. Notice that the "pass" file storing the first pass info should be created where you selected it to be.
Now Xvid has information on what we want to compress. So go back to Video - Compression - Configure. The Xvid options should be visible again. Select Twopass - 2nd pass leave the Target size as it is. Now go to the File - Save AS AVI select the file name and folder and click on Save. Depending on your power this can take a while but you will get your AVI with Xvid file. In my case not only the Xvid compression is taking place, but also the rotation.
Check out the size :)
And if you mind about quality (you should not ... you are recording with a photo camera!!) check the following picture (click to enlarge)
Original - Xvid compressed
This was all done with default options. You can also tweak the Target size if you want to get a smaller file, and also resize the video on the fly with a resize filter in Virtualdub.
Tuesday, October 21, 2008
A couple of weeks ago I had to use the XmlSerializer. I used it before almost for the same reason. To exchange information between some systems. In my particular case I was using very simple DTOs. In case you don't know it, the XmlSerializer is known for being slow. When you ask for an instance of the serializer using the DTO type in the constructor, there is some process going on behind the scene. All of this happens the first time you ask for the instance.
- The serializer checks to see if it is a known serializer (it maintains an internal cache). Being the first time you ask for this type it won't find anything.
- The type you sent gets reflected to death inside the System.Xml.Serialization namespace. Information is gathered from your classes (public properties, fields, attributes to modify the schema, etc). All of this is stored in mapping information.
- With all the mapping information. The serializer proceeds to create code (yep to create it) using the facilities provided by a CodeDomProvider, in this particular case, the CSharpCodeProvider.
- The new code which include functionality to serialize and deserialize is compiled (all of this because you instantiated a serializer...) and the result is a temporal assembly usually named [your type].XmlSerializers. The name might be followed by some number under some circumstances but usually you won't see nothing there. Remember this is the name of the assembly not the name of the dll file. If you use some tool like Process Monitor you will be able to see csc (the C# compiler) launching when you instantiate your serializer. In my case I see something like:
"C:\Windows\Microsoft.NET\Framework\v2.0.50727\csc.exe" /noconfig /fullpaths
This is of course a completely temporal path and name.
So as you see the problem here (if you decide there is one) is that creating an XmlSerializer for a given type is very resource consuming. It won't probably bring down your machine but since there is an easy way to improve you might want to give it a try.
You see, the steps I numbered first are not complete. Before trying to create new code, the XmlSerializer is smart enough to try to see if there is any pre-created serializer/deserializer assembly for the given type. You must provide this assembly, and you do it by using the sgen tool. You will find this tool in the bin folder of your SDK.
The sgen tool basically makes use of stuff already present in the framework. It does not create code by its own but uses the static call to XmlSerializer.GenerateSerializer static method. As an example, this is a command line:
C:\Users\Flaker\Spikes\TestSerializers\TestSerializers\bin\Debug>sgen /a: MyDtos.dll /k
The reason I added the /k is because I am curious and this flag will keep the temporary files that are otherwise deleted. You can see the output of the command line:
and the list of files. Including the temporary files (in this case they start with "fdyxy6-l.0").
The important result there is the file MyDtos.XmlSerializers.dll. That files includes the methods to serialize and deserialize your types. Just by including it the instantiation process of XmlSerializer won't create a new one.
In fact, if you want to, instead of using the regular XmlSerializer you can use the new class inside the new assembly. So your code
So just with a simple command line call or post build script (if you need that) I get a lot more speed without effort.
Wednesday, October 15, 2008
Yesterday I listened to a very interesting podcast by Scott Hanselman. It included a nice talk about a research work at Microsoft. One of the results of that research is a bot for Messenger that you can use to:
- Get translations
- Talk (well ... write) to other contacts in your contact list in their native language using the bot as a middle man translator.
Test it, you just have to add mtbot@hotmail as a contact. Check the window capture below to see a sample.
UPDATE: type "tbot ?" inside the window to get some help (without the quotes ... obviously)