Getting Ahead of the Curve – Final Update?

Picadilly by the light of the video wall, Canon S120 wide open with both aperture and zoom
Camera: Canon PowerShot S120 | Date: 08-02-2013 17:07 | Resolution: 4824 x 3015 | ISO: 250 | Exp. bias: 0 EV | Exp. Time: 1/100s | Aperture: 1.8 | Focal Length: 5.2mm

When I purchased my Panasonic GX7 on the day of release, I did expect there to be a slight delay in getting software support (see here), but I got frustrated when no fewer than three versions of Capture One came and went without it.

However my patience has finally been rewarded with V7.2.1. This not only delivers full support for the GX7, but has also dramatically upgraded the support for my equally new Canon S120. This produces RAW files which at the wide end of the zoom have very dramatic geometric distortion, so strong it was impossible to correct manually, but in the new version the built-in C1 support corrects them perfectly, with neither geometric nor chromatic aberration evident even at pixel peeping levels.

While I’m still slightly peeved about the time it took (a grand total of 6 months!), I’m very impressed with the results.

View featured image in Album
Posted in Micro Four Thirds, Photography | Leave a comment

Scarily Bad

Reversing the scarily effective performance of Google Now, I just had a dangerous experience with Google Voice Typing. I attempted to make a note in a busy café with a lot of background noise. After I stopped talking it sat and tried to take in some of the other sounds as well, and then tried to parse what it had heard.

The result: one four letter word, a colloquial term for excrement! That’s not what I said…

Posted in Thoughts on the World | Leave a comment

RIP Google Currents

Regular readers may be aware that I became very fond of a Google app called Currents. This took RSS-enabled news feeds, and presented them as attractive “magazines”. For feeds with significant image content (like most of the photography blogs I follow) Currents did a remarkable job.

Beyond making news reading sexy, Currents delivered two other pieces of distinct value: an easy to read default two-column layout on larger tablets, and a “stack” widget which allowed you to quickly swipe through the day’s news, aggregated chronologically, and click through to read the items of most interest.

However, I am writing this in the past tense. Currents is no more. An “update” a couple of weeks ago quietly moved my feed list over to the execrable “Google Play Newsstand” and uninstalled Currents. The replacement is clumsy, with none of Currents’ visual flair. An uninspiring reading experience is exacerbated by a useless widget which removes the brilliant former “flip through” capability.

Unfortunately this is not the first such aberration by Google. It’s less than six months since they killed off both the Reader app (maybe not such a great loss) and the sadly-missed iGoogle (which ironically was killed off allegedly because most users prefer Google’s tablet apps!) Now they are forcing us towards a dreadful replacement for the best of those apps, and I’m not happy…

This also comes on the back of various screw-ups regarding Chrome: the ready plain-text disclosure of stored passwords, the broken scrollbars, menus spaced ridiculously widely on normal PC displays. I could go on, and on, and on…

The arrogance of Google’s developers appears to be exceeded only by their stupidity or blindness to the faults in their “improvements”. When they deign to respond to a torrent of public displeasure, they do so by claiming that it’s our fault for not understanding the brilliance of their ideas, not by listening and responding to customer feedback.

I really don’t understand why Google are behaving this way, but it does seem that having emulated Microsoft’s successes of the 90s, Google are now determined to repeat their mistakes of the noughties, breaking compatibility, destroying things which worked well, and systematically driving customers into the arms of competitors. Apple might get away with treating customers with disdain, but Google have neither their shiny hardware nor the fans’ love for the blessed St. Jobs.

For now I’m sticking with Android and probably Chrome, but I’m genuinely interested in making sure the market starts to develop high quality alternatives, before Google rip their remaining carpets out from under us. If you know of a proper non-Google replacement for Currents please let me know.

Posted in Thoughts on the World | Leave a comment

What Do I Mean by "Agile Architecture"?

A little while back I was approached by EITA Global, a global provider of on-line training, and we have now agreed that I should present for them a webinar entitled "Agile Architects, and Agile Architecture". The current plan is for this run on 8th April. I’ll keep you all posted with any changes.

As part of my preparation, I decided to do a literature scan to see how this topic may have moved on since the last time I did some significant work on it, a couple of years ago. I have to say that based on my initial research I’m not that impressed… I don’t know whether to be flattered or slightly perturbed that AgileArchitect.org comes up squarely at the top of a Google search. There are a few decent web articles around, although most are several years old and I’d seen them before. The Google search also turns up several dead links.

Amazon turned up a couple of loosely-related books, and the most obvious candidate appeared to be "Lean Architecture: for Agile Software Development" by James O. Coplien and Gertrud Bj�rnvig. I’ve now read a couple of chapters, but my first impression is not very favourable. I may be rushing to judgement, in which case I’ll apologise later, but the book seems to somehow equate "architecture" with "code structure" with "project structure", which isn’t right at all, missing a number of the most important dimensions of any true architecture.

This led me to ask myself a very basic question. "What do I mean by ‘Agile Architecture’?". In Coplien and Bj�rnvig’s book they seem to answer "an architecture which facilitates agile development". That may be one definition, but it isn’t mine.

I think the confusion arises from the difference between "agile" applied to a process (e.g. software development), and applied to a product. In the former case, the Agile Manifesto undoubtedly applies. In the latter, I’m not so sure. I think that for a product, and especially its architecture, the primary meaning of "agile" must be "able to respond to change". The larger the change which can be handled quickly and cheaply, the more agile the architecture. An architecture which has been built in a beautifully run agile project but which needs new code the first time a business rule changes is fragile, not agile. The system which can absorb major changes in the business rules without a single line of code is genuinely agile. The integration architecture which allows multi-million pound system A to be upgraded with no impact on adjacent multi-million pound system B, or which allows the company to be restructured just by re-configuring its services, is the most agile of all.

I’m slightly worried that "agile" may have become a "reserved word", and this "architecture in the large" definition may run counter to accepted practice. Is that right, or am I reading too much into a few examples?

Posted in Agile & Architecture, Thoughts on the World | 4 Comments

That Was Quick…

The Beech Avenue near Kingston Lacy - Mono version
Camera: Canon EOS 7D | Lens: EF70-300mm f/4-5.6 IS USM | Date: 28-02-2014 14:55 | Resolution: 5184 x 3456 | ISO: 400 | Exp. bias: 0 EV | Exp. Time: 1/30s | Aperture: 10.0 | Focal Length: 180.0mm (~291.6mm) | See map | Lens: Canon EF 70-300mm f/4-5.6 IS USM

OK, here’s the black and white version. A couple of interesting challenges here. To get enough contrast I had to take the yellow component in the mix right down to zero, and also go for a much “darker” look overall (as otherwise the white patches of lichen on the trees were overwhelming). What do you think?

View featured image in Album
Posted in Photography | Leave a comment

Remember When There Was Something Called Dark and You Couldn’t Make Photographs?

Detail from the side of Salisbury Cathedral
Camera: Panasonic DMC-GX7 | Date: 28-02-2014 18:28 | Resolution: 3214 x 4286 | ISO: 3200 | Exp. bias: -33/100 EV | Exp. Time: 1/13s | Aperture: 4.5 | Focal Length: 25.0mm | See map | Lens: LUMIX G VARIO 12-35/F2.8

Sadly, this isn’t my own quote, but it is very apposite. I decided to break my journey back from Kingston Lacy in Salisbury, and took a quick walk before dinner down from my hotel (apparently the longest continuously operating hostelry in the world!) to the cathedral. I popped the Panasonic GX7 with its new 12-35mm lens over my shoulder, and I’m glad I did. The cathedral is floodlit, although not to excess, and I caught it when there was just a hint of blue left in the rapidly darkening night sky.

In the past a photo like the above could only have been created with a tripod and patience. No more. The GX7 produces fine quality at ISO 3200,and the stabilisation of the lens allows it to be hand-held down to about 1/10. I didn’t even have to exploit the f/2.8 aperture, which would have given me another stop. Essentially we have now reached the point where if I can see something, my newer cameras can photograph it.

Next time, photography through the lens cap! 🙂

View featured image in Album
Posted in Photography | Leave a comment

Ansel Would Be Proud?

The Beech Avenue near Kingston Lacy
Camera: Canon EOS 7D | Lens: EF70-300mm f/4-5.6 IS USM | Date: 28-02-2014 14:55 | Resolution: 5184 x 3456 | ISO: 400 | Exp. bias: 0 EV | Exp. Time: 1/30s | Aperture: 10.0 | Focal Length: 180.0mm (~291.6mm) | See map | Lens: Canon EF 70-300mm f/4-5.6 IS USM

I had a day off today from work, chasing contracts and Android development, to focus on photography and writing. The core was a workshop with the famous and venerable landscape photographer Charlie Waite, at the even more famous and venerable Beech Avenue near Kingston Lacy.

It was a good group, and we had an excellent day of discussion about photography, how we do it, why we do it, and what we need to improve. Unfortunately as for so many others this Winter the weather let us down, and we managed a grand total of about one hour on location, getting buffeted by strong winds, pelted by rain and battling a combination of ambient temperature and wind chill which together netted out the wrong side of freezing. I ended up using the same gear and clothing as I was using at the top of Kerlingfjotll (“Bitch Mountain”) in Iceland – not what I was expecting from the Dorset Beech Avenue.

I went prepared for intensive activity, with a total of about 48GB storage across two cameras, or enough for well over 1500 shots. I took…  34, including about half a dozen “technical test shots”. Ansel Adams used to complain that 35mm film photography was in danger of leading to an excess of quantity over quality of photography. Had he survived to see digital, while he would undoubtedly have mastered the technology quickly and effectively himself, his concerns about quality vs quantity would have multiplied manifold! At least today I kept the quantity down.

Quality did suffer a bit. I had hoped after Charlie’s pep talk to go out with camera tripod mounted and take a slow, considered approach to photographing the avenue. Instead i took a series of fairly hurried “grap shots” mopping everything down between shots. Inevitably the rain has also reduced contrast and clarity of the trees in the distance.

However I’m not unhappy with this shot. The composition is exactly what I wanted, I like the tonal range (although ironically I’ve actually toned down the saturation!), and clarity is OK, if not perfect. I might try a black and white version as well…

View featured image in Album
Posted in Photography, Thoughts on the World | Leave a comment

Developing for Android

Regular readers will realise that I’ve been rather quiet recently. The reason is that over the last couple of weeks I’ve bitten the bullet and started seriously developing an “app” for Android. As always when I have a programming project in progress other uses of my “project” time tend to take very much a back seat, so apologies if you’ve been watching for photos or words of wisdom… 🙂

I don’t want to say too much about the application itself until I have something ready to put on the market place. Suffice to say I think I’ve spotted an odd gap in the market where the weaknesses of iOS force a number of good solutions to one problem of information management, whereas Android’s more flexible architecture ironically mean the problem goes unsolved. Watch this space.

I was initially a bit worried that the learning curve for Android development might be very steep, especially when I started working through the standard Java-based examples in the official Google development toolkit. Like all Java development that approach seems to require a vast amount of “scaffolding” code, which must be constructed with very little environmental help, to achieve very simple results. This didn’t look good.

Then, thankfully, I discovered Basic4android. This is a remarkable toolkit developed by a small group in Israel which allows the development of Android software using a powerful but very accessible language and IDE based on Visual Basic. Behind the scenes, this is compiled into standard Android Java code, so ongoing delivery of applications is standard, but the coding and design process is close to “pure VB”.

The development environment has all the features you could reasonably ask for, including code completion, syntax highlighting, background compilation and the like. Remote debugging extends to devices connected over the Internet as well as via cable or local networks, and has a cunning feature where you can “hot swap” the code behind a running application allowing a range of changes to a running test application without restarting it. These are very impressive abilities for a product from a relatively small company.

Just as with the original VB, Basic4android has a model which allows developers to supplement the platform capabilities with shareable components, libraries and code snippets, and a very active community has rapidly built a library of “donationware” which provides easy access to the majority of Android features. I’ve had to be a bit ingenious in a few cases, but even as a newbie on my first project I haven’t yet found a requirement which can’t be met with a few lines of code.

On a slightly more negative note, Basic4android doesn’t seem to provide a good solution to the problem of supporting multiple screen sizes and orientations, except by writing multiple hard-coded scripts for the various options. This problem has been solved for websites with the concept of the “responsive grid”, and it ought to be possible to arrange the UI of an Android app with similar logic (e.g. “arrange these two controls side by side with the label taking 75% of the width, unless the screen is narrower than X, in which case arrange them vertically”). If this can be done in Basic4android I haven’t yet worked out how.

Debugging on a physical device connected directly to the PC is very straightforward, but of course limited to the devices you own, and a bit clumsy if you fancy doing a spot of work when travelling. While the Android development kit includes an emulator for the PC, it runs so slowly as to be completely unusable, even on a high-spec machine like my AlienWare M17x. I may have discovered a better compromise, in Android-x86, a port of Android which runs happily in a VMWare virtual machine. Installation was easy, but there are a few foibles I haven’t yet conquered. Again, watch this space.

Overall my adventure into Android development is shaping up well. More news later.

Posted in Android, Code & Development, Galaxy Note, VMWare | Leave a comment

Scarily Good

My new phone (I upgraded to a Galaxy Note 2 as I was running up against memory limitations on the Note 1) has a potentially useful but also quite scary feature. There’s a service running on it called “Google Now”. This has no direct user interface, but just pops occasional reminders into the notification bar.

This afternoon I had an appointment, which I had recorded in Outlook simply as “Sally” with the location “Strada Cobham”. At about 2.40 a reminder popped up which said not just “you have an appointment at 3”, but “leave by 2.54 to be on time” , quite an accurate estimate of the required driving and parking time!

I’m impressed, but also slightly concerned. What other information is Google mining from tiny bits of data of mine?

Posted in Thoughts on the World | Leave a comment

Getting Ahead of the Curve – Update

Birmingham Bull Ring and St. Martin's Church - ISO 3200
Camera: Panasonic DMC-GX7 | Date: 10-12-2013 21:25 | Resolution: 4523 x 3016 | ISO: 3200 | Exp. bias: -1 EV | Exp. Time: 1/20s | Aperture: 5.0 | Focal Length: 14.0mm | Lens: LUMIX G VARIO PZ 14-42/F3.5-5.6

When I bought the Panasonic GX7 on the day of release I realised there might be a short delay before it was fully supported by third party software. A few weeks on and there was support from Adobe and some unexpected sources, but no sign from Phase One. Fortunately the in-camera JPEGs are absolutely excellent and I cheerfully blazed away in Morocco while waiting patiently.

Come December my patience was wearing thinner, with three months’ RAW files ready and others stacking up. I took to checking daily for new Capture One updates, and was finally rewarded on Monday by the release of v7.1.6. That was the first good news.

To my frustration, the release notes stated that the GX7 support was “provisional”, although Phase One had managed to deliver full support for pretty much every other recent new camera. The primary limitation seems to be the lack of any lens correction, even manual, which is a rather substantial issue for a micro four thirds camera. Any shots taken with the wide ends of my zooms will have to wait… That’s the bad news.

</moan>

There is, however, some really good news. The image quality is simply superb, much better than I have been able to achieve with Adobe Camera Raw, and a dramatic improvement on all my other cameras at high ISO. Images are essentially noise-free at ISO 1600, and not much worse at ISO 3200, suggesting I was unnecessarily pessimistic limiting myself to 1600 in Morocco. At ISO 6400 there’s a bit of noise, but essentially correctable. I would probably choose to use a lower sensitivity for something critical, but for general use it’s absolutely fine, as long as I don’t try to pull the shadow exposure too far. I might even be brave enough to use 12800 in a pinch.

So my Christmas present from Phase One may be arriving in instalments, but it’s looking really good for the latest compact system cameras.

The above shot gives you an idea of what can be achieved, and is also suitably seasonal. My very best wishes to all my readers, and hope that we all have a successful and satisfying 2014.

View featured image in Album
Posted in Photography, Thoughts on the World | Leave a comment

Morocco – Did I Need Two Camera Systems?

Blacksmith at work, Marrakech
Camera: Panasonic DMC-GX7 | Date: 11-11-2013 15:29 | Resolution: 4592 x 3064 | ISO: 1600 | Exp. bias: -1 EV | Exp. Time: 1/40s | Aperture: 8.0 | Focal Length: 35.0mm (~72.0mm) | Lens: LUMIX G VARIO PZ 14-42/F3.5-5.6

Here’s the list of the main kit I took to Morocco:

  • Canon 7D body
  • Canon 550D body
  • Canon lenses: 15-85mm,  17-85mm, 70-300mm, 10-22mm (The 550D and 17-85 were basically “spares”, although both got a small amount of use.)
  • Panasonic GX7 body
  • Panasonic lenses:14-42mm (power zoom), 14-42mm (kit lens, spare),  45-175mm, 100-300mm
  • Olympus lenses: 12mm f/2, 9-18mm
  • Gitzo GT1540 tripod with Gitzo ball head
  • Around 96GB each of SD cards and CF cards
  • Three battery chargers and one or two spare batteries for each camera
  • Polarising filters in each of the following sizes, and protective UV filters in almost all: 37mm, 46mm, 52mm, 58mm, 67mm, 72mm, 77mm
  • Lens hoods for most, but not all of the lenses
  • Remotes for both systems, including an intervalometer for the Canons (ironically the GX7 has one built in) and an adapter cable because the Canons have different connectors
  • Shoulder bag for around town and tiny bag for GX7 as well as my large backpack for travelling and the desert trip

While I liked the flexibility of this selection, I would be the first to admit that it meant carrying more than ideal in terms of both weight and value. It’s also almost in danger of becoming my standard kit for any trip, which is vaguely ridiculous. However it’s not obvious how or even whether I should pare it down for a future similar trip.

Firstly, apart from the spare Micro Four Thirds normal zoom, each lens and all three bodies saw real use (although I could realistically have substituted either of the others for the only outing of the 550D and 17-85mm lens). However following my experiences in Cuba and Iceland I wouldn’t forego carrying a spare body for the “main” camera and a spare mid-range zoom, although by carrying two different “systems” I doubled up both elements on this trip.

I don’t think there’s a single shot I took with either Canon I couldn’t have taken with the GX7, but that might not have been true if there was more fast action, and I might have got one or two shots I missed if I had had the 7D with its fast performance and 6X standard zoom ready in my hand. The Canon lenses are definitely a bit more resistant to flare, but in most cases I didn’t find that an insuperable problem with the MFT kit. Whether the Panasonic batteries would have lasted the desert trip and frozen night shoots is an unknown, but the third party batteries for the Canon weren’t great either.

Conversely I definitely got several shots on the GX7 which exploited the GX7’s unobtrusive nature, silent operation, the wide aperture of the Olympus f/2 lens or the remarkable reach of my new 100-300mm lens. These I might not have got with the Canon.

As I’ve said before, the Panasonic GX7 is the ideal camera for wandering around in towns, or exploring cramped interiors like those of the older buildings in Morocco. I’ve read other reviews which liken it to a smaller Leica rangefinder, and if that’s true then I finally “get” the rangefinder aesthetic. Where it scores over other such cameras is that it is not limited to one mode, but moves seamlessly from point and shoot (composing on the rear display), or “twin lens reflex” (using the same panel tilted), through rangefinder and on to a high performance shooting mode best described as “mini DSLR”. I find myself increasingly using all those modes, whereas with my previous cameras live view has been only for situations where I genuinely can’t reach the viewfinder.

I also find myself using the multiple aspect ratios as a positive composition aid, and the live preview as a visual exposure guide in a way I have not done before.

The sheer physical size has an impact on subjects. In our financial argument with the snake charmers one of them went through our group saying “you have big camera, you have big camera…”. He got to me, raised his finger, and stopped dead. Something similar happened a couple of times.

Could I have managed with just the Canon kit? Probably, but I would have had to work harder, both physically and to get what I wanted from some of the subjects.

Could I have managed with just the Panasonic (with my GH2 as “spare body”)? Yes, but I would have been a lot more nervous about the desert trip. I happily sat on camel back with the 7D bouncing in the saddle. At one point I dropped the 7D in the sand from several feet up, but just dusted it off and carried on. That might have been a more serious incident with the smaller cameras.

The solution might be to extend my micro four thirds kit with a weatherproof lens and body, such as the Panasonic GH3 and 12-35mm lens. Morocco wasn’t that hard on kit, although I didn’t know this beforehand, and that pairing would have managed fine in the desert.

Unfortunately the harshness of a location is something which is hard to predict on a first visit: Iceland was much harder on equipment and even some of my heavyweight Canon gear did not survive – the wear on smaller cameras would probably have been unacceptable.

The alternative view (although it’s from Kirk Tuck, a man who changes his cameras almost as often as I change my socks) is that we just accept that the cost of smaller, lighter kit is that we wear it out more quickly, and that this fits with the gradual obsolescence due to technical advances. While I partly buy this argument, I’m not keen to completely wreck and write off equipment, and it brings the risk of a trip where both the primary and spare equipment die before the end. That would be a real disaster.

So for now I have moved one step closer to travelling light (or at least light-er). For trips to “easy” destinations I may be prepared to go MFT-only. For more physically challenging locations, if there will be a lot of fast action, or if I need the visual impact of a “big” camera I take the Canons. For trips with a mix of both, I remain a beast of burden.

View featured image in Album
Posted in Micro Four Thirds, Morocco Travel Blog, Photography, Travel | Leave a comment

Camera History

Andrew's camera "fleet", December 2013
Camera: Panasonic DMC-GX7 | Date: 03-12-2013 13:43 | Resolution: 11493 x 1881 | ISO: 200 | Exp. bias: 1 EV | Exp. Time: 1.0s | Aperture: 16.0 | Focal Length: 45.0mm (~93.0mm)

While my memory works tolerably well, and as I suspect I’m about to enter one of my periodic phases of camera replacement, I thought it would be interesting to write up a list of the cameras I have owned and how my photographic capabilities (but not necessarily my skills) have evolved with them. Read the article here.

Read the full articleView featured image in Album
Posted in Micro Four Thirds, Photography | 1 Comment