Halo para Aktivis! (tentunya aktif semua sesuai judul milisnya)

read more

A few days ago MySQL 5.1.42 got released and it is now available with builds for MacOS X 10.6 (Snow Leopard)! The download website doesn’t show it yet, but if you are burning to try, you can get it from the mirror-picking-website.As usual, don’t forget to checkout the changelog before upgrading!If you want to compile it yourself, and need a universal binary, you could try my previous blog entry laquo;Building MySQL universal binaries using MacOS X 10.6 (Snow Leopard)raquo;.

In software development, it?s crucial to track bugs and new features, and to be able to know exactly where a project is at any given moment. Bug tracking is crucial tot his goal; it allows a project manager to know what has been finished and what still must be done, as well as to outline to each developer their goals and responsibilities.

Joel Spolsky does a fabulous job explaining how remembering bugs gets more difficult as time goes on. However, the value of the documentation created by bug tracking is often overlooked. When bugs are filed, and fixed, and time goes on, it?s easy to generate statistics on who creates, who fixes, and what fixes are applied in the code base. New bugs can be linked to old bugs (to see regressions), and all the problems that have ever been solved are in one place.

For this, it is crucial that whatever bug system you use has awesome search capabilities. It?s also important that developers write detailed notes on their solutions, or link to repository commits so that other developers can see the changes made.

Track bugs and features together.
While it?s known as a ?bug database? it should really be an ?issue database? because it should record everything, bugs and features together. Why? Because it makes it easier to know what work is on the table before getting started on a particular project.

Having both bugs and features in the same place means that the project manager as well as the developers can see the tasks on hand, as well as determine what should be pushed into the next release. Often times when considering a new release, project managers only consider new features, because they don?t see the amount of work that must be done to fix the bugs. Having them together will help ensure that this doesn?t happen.

Fix old bugs before starting on new features.
The link to Joel?s post above outlines some of the benefits of starting on bugs before working on new features. I won?t rehash his points; what I will add is this: fixing old bugs first is crucial because developers hate doing it. Developers like working on new code. Developers hate going back and working on old code that they?ve already written, or that other people have written. By forcing developers to fix outstanding bugs before they work on the ?latest and greatest? new features means that the bugs will actually get fixed, rather than being pushed off and pushed off until they?re all that?s left before shipping the product.

I haven’t been posting lately since last year (it’s 2010 now, so HAPPY NEW YEAR for all of you). Slackware-Current hasn’t shown any updates on the Changelog, which means that the team are on vacation or perhaps they are testing something on the background which is not ready for public consumptions.

Some say Arch is more bleeding-edge and it’s suitable for people who are looking for the latest version of packages in their system, while Slackware maintains their stable and secure philosophy since the beginning of the release. It’s all discussed on this article.

About a year ago I wrote about How to get a Singleton right. While nothing has changed my opinion about the Singleton Design Pattern – contrary, I’m even more convinced that it is bad, bad and bad – I still have homework to do. In the comments to this article I was asked about my opinion on the Registry Design Pattern, and I promised it would be worth an own blog entry. Well, I did not anticipate it would take more than a year to write it, but you know, work, and no time, and yada yada yada… so here it is.

When thinking about a Registry one has to consider two points: overall architecture of the application, and implementation of the Registry itself. It’s not that much what you can say about the implementation of a Registry. For PHP, it should just follow one rule to make it testable and to ease testing of classes using the registry: do not make it a Singleton. (You might have guessed that already.) PHP offers the possibility to implement the Registry as a pure static class, where data within the Registry can be stored within a static class variable, and setters as well as getters can also be static methods. There is no value in making it a Singleton, it just more stuff to type where the result is the same: global state. So if you implement it as pure static, the Registry in itself is neither bad or good.

Speaking of global state, it should be common sense by now that global state is a bad idea, at least if this global does not mean the root of the application itself, which leads us to the overall architecture of the application. How is this related to the Registry Design Pattern? The Registry is intended to allow access to configuration data, objects etc. which you don’t want to pass around in your application but require them in different parts (or layers) of your applications. If you have such a need from my point of view this means the application is not fully based on the Dependency Injection principle, it does not separate object creation and business logic as much as it should. If the application is completely based on Dependency Injection, there is no need for a Registry any more.

Did I just say that there is no need for a Registry any more? Well, two exceptions. First, unfortunately in PHP there might be cases where you can not influence the creation of an object instance, and if you want to pass data or other objects to such an instance, you have to take cumbersome actions to pass those. Creation of user land stream wrapper instances is such an example, as those instances are created by PHP itself and there is no possibility to intercept this. Here a Registry might be of help, but it stays what it is: a workaround for a flaw in PHP.

The other exception is the case of using a Dependency Injection framework. You do not need a Registry here – your DI framework already has something like this. It just not called Registry, but it is it’s mechanism where you bind data or objects for example in the case of Stubbles or Google Guice, and in Symfony it is called Service Container. (Please note that this is just a quick thought I had in the last days, I might be wrong on this.)

To conclude, the Registry itself is neither useful or harmful. The more important question is how strong you apply the Dependency Injection principle in your application.

Kali ini kami menguji 3 browser ternama di dunia. Masing masing yang kami uji adalah rilis terbaru mereka untuk gnu/linux.

Komputer yang digunakan untuk menguji Pentium Core 2 Duo 3 Ghz dengan RAM 3 G, koneksi internet direct tanpa proxy. Seluruh browser diinstall fresh dengan posisi cache-history kosong, dan setting default. [...]

Sabtu, (05/12/09) kali ini Kelompok Pengguna Linux Indonesia (KPLI) Solo mendapatkan kesempatan untuk memberikan kuliah umum di Universitas Sahid. Salah satu universitas yang berada di Solo. Kuliah kali ini dhadiri oleh mahasiswa-mahasiswa dan dosen dari USahid Solo. Kuliah umum ini dalam rangka sosialisasi? Open Source dan Linux di daerah Solo pada khususnya. Untuk kuliah umum [...]

London, UK

There’s a campaign started by Monty Widenius to save MySQL from the evil clutches of Oracle. You can read about it here.

Issue #104 of openSUSE Weekly News is now out! TooManyTabs ndash; Saves Your Memory 1.1.0 Alcaro Soliverez/kde.news: First KMyMoney Beta Version Available for KDE 4 Platform Joe Brockmeier: Put some meat on it: Writing release announcements Sharing a /home Directory between Linux and Windows KDE.NEWS/Dario Freddi: KDE Extends Polkit Support to polkit-1 p/p p/p pFor a list of available translations see this page:/p phttp://en.opensuse.org/OpenSUSE_Weekly_News/104/Translations./pRead More…