My Android phone died on me last week.
More accurately, it has been randomly deciding that the battery must be discharged by now and turning itself off. Having played around with the settings a bit, and even resorting to a factory reset, I have come to conclusion that the problem is probably a faulty battery.
Since I have a new phone on order, I am not particularly inclined to rush out and replace the battery for the current phone. So, as a stopgap, I have dug out my old Nokia N72.
Not having used a Symbian phone for a while, it took me a few moments to find where everything was but it was surprisingly easy to get used to the interface again. Part of this may be related to the that I moved some of the applications around to better fit my quirks when I was last using this phone. Configurability is good as good, though, and it’s also rather nice to find that I have a file manager by default rather than having to go and look for one.
The form-factor has also proved to be remarkably resilient. The N72 is a candy-bar phone with a sliding cover to protect the camera. Four years ago, this cover struck me as being a bit flimsy but, compared to the not-quite-tablet experience that the typical Android phone gives you, the N72 does feel remarkably well constructed. It’s not heavy, but it is solid, compact and lets you know that this is a phone that can take a bit of a battering without too much trouble.
And then there’s the battery life. I have been playing around with this phone for the best part of a week and am still nowhere near needing to plug it back into a charger. Not only is it quite relaxing to not have to be constantly monitoring the battery status but this also brings home just how much of a resource hog Android can be.
I have no plans to permanently abandon Android, but I will certainly be keeping this phone around in case of emergency. Having a phone that you can charge up after completely ignoring it for almost half a decade, and rely on it just working is really rather reassuring.
In their time, Nokia made some very good phones. Symbian is not perfect but I can’t help but feel that if the company’s management had put more resources into developing phones and less effort into Dilbertesque organisational silliness the smartphone landscape today would be both very different and a lot healthier.
I’m not a huge fan of UltraEdit, but we have to work with what we are given. And what I have been given is a test editor that keeps on creating backup files every time I hit the save button. This may be useful to some people but, for me, it is just annoying.
However, it’s also pretty easy to switch off. Go to
Advanced > Configuration > File Handling > Backup and select No Backup.
And now your folder is decrapified.
I had a Victor Meldrew moment this weekend while looking at a Toy catalogue with Macsen. It turns out that you can now buy a scoop to pick up snow, a mould to form it into a snowball and a launcher to fire the snowball at someone. The catalogue in question was on paper, and the associated webite was unlinkably awful, but the same toys can be found on Amazon.
What’s wrong with picking up a handful of snow and lobbing it?
Psychologist Oliver James, author of the parenting book Love Bombing, believes children don’t “need” a vast panoply of toys.
“Most children need a transition object,” said James, “their first teddy bear that they take everywhere. But everything else is a socially generated want.”
This strikes me as very true. Certainly, my own kids have no shortage of toys and most of these end up left in boxes – ignored and then forgotten. They do each have their favourite toys and it is this limited subset of the available options that they keep returning to.
And, truth be told, more fun for all can be achieved by handing them a tool (be it a broom, a rake or whatever else happens to be seasonally appropriate) and making sure that they are able to help with whatever I happen to be doing.
Obviously there is a balance to be struck here and I am not about to embark on some sort of anti-toy crusade. Equally, though, if you have considered buying some over-priced replacement for an over-arm throw, one that is only going to be usable for about one week in 52, then your kids have too many toys.
Project Euler problem 99 is as follows:
Comparing two numbers written in index form like 211 and 37 is not difficult, as any calculator would confirm that 211 = 2048 < 37 = 2187.
However, confirming that 632382518061 < 519432525806 would be much more difficult, as both numbers contain over three million digits.
Using base_exp.txt, a 22K text file containing one thousand lines with a base/exponent pair on each line, determine which line number has the greatest numerical value.
This had me stumped for a while because, as far as I could find, there is simply no realistic way of calculating the large exponentials in the list. And then I learned something:
log(xy) = ylog(x)
And once you know that, finding the solution is very easy indeed.
It’s rare that you need to sort a database file (or table), but I have encountered a circumstance in which a sorted file had to be delivered. Being naturally lazy, I started looking around for the least-work method of achieving this and ended up looking at the RGZPFM command. This is a command I have used quite often to compress a physical file (it removes the deleted records), but this time around it was the reorganise part of Reorganise Physical File Member that I was interested in.
From the help text:
If a keyed file is identified in the Key file (KEYFILE) parameter, the system reorganizes the member by changing the physical sequence of the records in storage to either match the keyed sequence of the physical file member’s access path, or to match the access path of a logical file member that is defined over the physical file.
The important thing here is that any keyed file can be specified. So if I have an appropriately keyed logical file, I can very easily sort the physical.
Some names have been changed, but if I have a physical file called ITEMLIST and I want it sorted by field BARCODE, I need to first create an index:
create index ITEMLIST01 on ITEMLIST (BARCODE); label on index ITEMLIST01 is 'Logical on ITEMLIST (Keyed: BARCODE)';
Then I can easily reorder the physical file ITEMLIST into BARCODE sequence with the command:
RGZPFM FILE(ITEMLIST) KEYFILE(ITEMLIST01 ITEMLIST01)
There is nothing more cowardly and corrupt than a lawbreaking political leader who threatens the free press when they call him to account.
- Cory Doctorow on David Cameron’s threat to seek a court order against The Guardian if the paper doesn’t stop revealing the extent to which crimes have been carried out with the knowledge and approval of the highest levels of the US and UK government.