I’ve created a small scala-script to extract messages from SOAPUI. Writing this was surprisingly easy, and certainly faster and more pleasant then processing the SOAPUI manually.
If you have to access persisted data, of course, you do not have to necessarely use SQL. But in case you do, knowing something about SQL-performance helps.
I just did a this 3-minute test on SQL performance (for Oracle), with 4/5 score. Pretty fine.
The answer I failed was about multi-colomn indices. When you have a index containing multiple columns, if you use one of those columns in a where clause, the index is used. However, the index can only be used efficient if you use at first column.
De organisatie waarvoor je werkt besluit Agile te worden. Dat klinkt eng! Ongetwijfeld betekent dat een reorganisatie en dus dat mensen ontslagen worden. In deze tijden van economische tegenspoed zou het jammer zijn als mensen zonder baan komen te zitten, dus laten we eens kijken wat mensen in de softwarewereld, die gewend zijn aan Waterfall, PRINCE2, TMAP of CMMI zouden kunnen doen als hun organisatie besluit Agile te worden.
Lees meer ›
Lots of SF movies and futerist though that the future interface of the computer would be voice: talking to your computer like it was a human. Nothing less is true: the future are gestures to the computer? Why, now that people have smartphones, they could communicate with each other using video-calls – the videophone of the past. Rather than that, many people just post text messages to each other. People prefer to text to other people, why would they even use voice to talk to a computer?
Of course the best interface, next to typing commands to a computer, would be using gestures: just subtle move your hands in front of your screen to get things done.
A few start-ups already have the technology available: Meet the Nimble-Fingered Interface of the Future
Quite a while, my top posting was about waste at the government. Now something more positive on waste, and other lean subjects: I recently read the book ‘Een lean overheid‘. The book is in Dutch, and gives a nice introduction on using Lean in government organizations.
Unlike other lean books, translated to Dutch or not, it’s written specifically for the Dutch government. I guess most of this information is relevant for Dutch speaking readers, for those that speak English only: I am very fond of using lean at the government. Some people at the UK government seems to be getting it, as well as the US government. Hopefully the government in the Netherlands catches up soon!
Inspired by an OS that went in oblivion some years ago (BeOS) operating systems as Windows, Linux and MacOS all have ways to monitor directories for changes built into the filesystem: meaning if a directory is changed because a file or directory is added, removed or changed you can get an event. There’s need for running a program that periodically monitors the directory (nor does the OS do that, it’s build into the filesystem). Software like Dropbox and other filesyncing products use this, so whenever you change or update a file it’s immediately updated to the ‘cloud’.
The name of the API’s for the listed OS’s are:
There are a number of open source libraries that allow you to use that API in Java, not all cross-platform. Fortunately, since Java 7 watching directories is now part of the default java.nio.file API.
The (Dutch) website Computable has a interesting article on how awful it is the government wastes enormous amounts of money on it-projects. With that regard a report by System Error on the UK government who are (were?) equally awful is still a good read: Fixing the flaws in government IT
SSD disk are becoming increasingly popular. As they read faster, you might consider running databases such as Oracle DBMS, MySQL or non-sql databases. However, interestingly, originally databases are optimized for tradition hard drives with spinning disks: most importantly: data is read in small chunks, and sequential reads are faster than random reads. I can’t remember everything anymore, but I do remember doing calculations on various reading/writing algorithms during my university days.
For SSD’s this model doesn’t hold anymore: this blog posting shortly explains why: Why theory fails for SSDs There’s no difference, if I understand correctly between random reads and sequential reads. However writes are much slower. Also SSD’s have to calculate the physical address for every different read or write access. Meaning if you read a different part of the disk continuously, this will be slower then reading in the same pattern again and again.
Of course the theory doesn’t fail, but it just doesn’t apply to SSD :-).