I attended the third RWDevCon March 30 – April 1 in Alexandria, VA. (Yes I know that was 10 days ago, but I had a lot of notes.) It was the third time RWDevCon was held, thus I was one of a reported 12 faithful attendees who have attended all three conferences. I even dragged a colleague from one of my customers to attend this year.
Why do I return for the joy of back to back eight hour days of seminars (this year with a third all day workshop for added pleasure)?
It would be great to see RWDevCon grow into something much larger, so that those that put in the hard work could realize that success. But it is also excellent at the size that it currently is. Ray, Vickie and the team have a hard balancing act to do.
Bottom line: I cannot recommend this conference more highly to any and all iOS developers. Most of these sessions provided me with enough information that I could use what I learned immediately. Some are difficult enough that I’ll need to review the data before knowing enough to be dangerous. But the amount of tools and education gained in these three days provides a high ROI on time and money spent.
It was a tough choice between the Debug workshop versus this one, but need won out. I’d recently completed a cycle count and inventory Swift application in a very tight timeline, and I KNEW I had broken many app architecture rules in haste….so I went to task to re-learn and hopefully be amazed by some new ideas as well. Had I known attendees would be getting a copy of Derek’s (who was leading the other workshop) Advanced Apple Debugging and Reverse Engineering book at the conference close, I would have had more incentive to choose this session…until Josh and René put out an app architecture book.
After meeting one of my three favorite nephews for brews and dinner at the Trademark downstairs the night before, I was primed and ready (obligatory local beer picture included) for the next morning’s 8 hours session.
What I learned:
After the workshop, with a full brain, sore butt from sitting, an hour to spare until the opening reception and the threat of bad running weather in the ensuing days, I headed out to run down King Street, a very cool old set of blocks that runs towards the river, right into more running trails (obligatory running scenery picture included – session details after the photo).
There were three tracks of sessions. There are the ones I selected to attend. There are several others that I either worked through the demo material or plan on doing so…as, so far, one cannot be in two places at once.
Machine Learning on iOS (Alexis Gallagher)
Why I attended: I want to employ machine learning with two of our products (Secure Workflow and Clinical Decision Support).
What I learned:
iOS Concurrency (Audrey Tam)
Why I attended: We have an old objective-C app that is getting converted to Swift, and it needs some concurrency help at one customer as their network is slower. I’d like to put parts of the data refresh in the background while updating the animations of the workflow tasks and notes. Plus Audrey is my wife’s name, so there you go.
What I learned:
Building Reusable Frameworks (Eric Cerney)
Why I attended: The old objective-C app I mentioned earlier has frameworks, and they need to be updated.
What I learned:
Why I attended: Reactive programming. Buzz words. Got a taste during the app architecture workshop. And I sensed a book was coming (obligatory signed book page picture included, only found Marin and Ash though…there’s a lot of authors!)
What I learned:
Practical Unit Testing I (Jack Wu)
Why I attended: Code is never tested enough. Especially mine.
What I learned:
Swift Playgrounds in Depth (Jawwad Ahmad)
Why I attended: I didn’t get to use playgrounds enough as a kid. It was a tough choice between this one and Practical Unit Testing II.
What I learned:
Advanced iOS Design Patterns (Joshua Greene)
Why I attended: The description talks about authentication, auto re-login, data and thread safety designs.
What I learned:
Swift Error Handling (Mike Katz)
Why I attended: My error handling looks like the if-then-else statement from hell.
What I learned:
Post-conference bottle share
Why I attended: I brought two great beers from local Houston breweries and they needed to be tasted. (obligatory Houston beer picture included, especially since several people asked about them. They were mighty tasty)
What I learned:
One could make a case that this wasn’t really part of the conference. But it was. We traded beer stories, travel stories, family stories, tried to kill a monster in a dungeon while bluffing (more card games), and generally had a great time. All were invited.
With the amount of pre-conference setup, conference materials and notes gathered from this (and the previous two) RWDevCon, the investment here will continue to pay off as they are used and referenced. Next comes incorporating these into release plans for the apps we already have deployed, and those we will deploy in the future.
Some additional photos included here at the end.
Notes on the 2017 SXSW Health Tech sessions I attended (some with photos, some with photos of slides from the presenters) in order of relevancy to current projects. The sessions (and links to each if you want to jump down) are:
To see notes from other SXSW2017 sessions:
This was an excellently balanced and informative presentation where Dr. Duncan presented the technical perspective and Dr. Pevnick presented the data analytics and research perspective. I took pictures of most of their slides, the pertinent ones are included here.
Cedars Sinai starting allowing patients the option through their patient portal (voluntary) to link wearable devices and their readings, and integrated those readings into their EPIC EMR system. With little advertising they got up to 2800 patients (out of 130,000 portal users) sending in readings.
An interesting session title, especially given that two of the panelists with devices also had apps that were critical to their devices. The incongruity was somewhat rectified by the discussion that the focus was on the device, as opposed to YAAS (Yet Another App Syndrome, my acronym).
Panel: Lu Zhang (NewGen Capital, VC), Stuart Blitz (SeventhSense Biosystems), Janica Alvarez (Naya), Jeff Dachis (OneDrop)
I could have elected to wait in the two lines for Joe Biden (one for wrist bands, one to get in) and his cancer moonshot discussion. And, as I found out later, I also could have fanboyed out and found the Game of Thrones session (which I wasn’t aware of) which was right new door to Biden (apparently).
But the statistics and perspectives presented in this SXSW Health Tech session were a reminder of the size of the problems of diabetes and pre-diabetes.
Panel: Dr. Baker Harrell (It’s Time Texas), Michael Mackert (UT Austin), Nish Parekh (IBM Watson), Stephen Pont (Dell Medical Children’s)
This was a Texas focused session, which featured using technology to reach all Texans. Statistics were presented about smartphone penetration (e.g., there almost everywhere) and the app called “Choose Healthier“, a collaboration between It’s Time Texas and the Dell Children’s Medical Center was introduced. It initially contained events and location information for in and around Austin at the time of the presentation.
The slide below shows stats from a PEW on smartphone penetration from 2016. The point of the panel was that apps could be delivered to all people regardless of income level or demographic factors.
This is the session where I got stuck in an elevator on the way up to the Austin Chamber of Commerce. Lovely! Apparently this is the only way to get up to the chamber of commerce. We weren’t in there for longer than ten minutes, and since it was raining out it wasn’t too steamy…just another bit of excitement at SXSW.
Panel – Brian Baum, Charles Huang, Karen DeSalvo, Sukanya Soderland
This panel had an interesting mix of local and national perspectives, all of whom agreed that data collection is hard but data integration is harder. One of the best slides was one I got a mostly crappy photo of (if you get stuck in an elevator you don’t have the best choice of seats, or so I found out). But it talks about the amount of money that is invested in segments of healthcare that create or utilize data…versus integrating or sharing it. That slide is below.
Karen DeSalvo, the former director of the ONC, shared the goals of data and system integration between the public and private sector. Little discussion on what would happen with these goals with the new administration.
At this panel, Brian Baum introduced Connected Health Austin, a local initiative. There was discussion on defined data communities within Austin, and all they “solve the same problem differently everywhere” followed by discussion on how Connected-Health Austin would be different in this regard. I heard of several of these type initiatives in Austin during SXSW, hopefully they will all inter-connect.
Panel – Abhas Gupta, Andrew Rosenthal, Carine Carmy and Matt Klitus
The focus here was on providing advice for starting a company in the health tech sector.
Presenters: Slava Rubin (one of the founders of IndieGogo), Bill Clark (CEO of Microventures)
First Democracy VC is their joint venture that focuses on Equity Crowdfunding that was made possible by Reg CF, Title III. Slava and Bill said all of their ventures thus far has reached their funding goals. A slide they shared (at the end of these notes) shows that as March 2017 about 230 Reg CF offerings have been filed with the SEC (this is since it ‘went live’ in May 2016).
Slava shared a brief timeline leading up to the availability of equity crowdfunding.
A slide the gents shared on current equity crowdfunding statistics is shown below.
The long wait for the return to Osten Ard is almost over. I was grateful to be given an opportunity by Tad Williams and his wife Deborah Beale to read an advanced copy of The Heart of What Was Lost (available at the beginning of January). Returning there was indeed the sweet breath of cold fresh icy Nakkiga mountain air that Memory, Sorrow and Thorn (MSantT) fans have been waiting for. And, since it made me want more, luckily the three books in the new series, The Last King of Osten Ard, are not far behind.
Full disclosure: this is based on an advanced copy. Slight spoilers may be below. If you don’t want to read further, the TL;DR of this review is…it sure as hell was worth the wait…but makes the months until The Witchwood Crown seem like an eternity.
I normally include snippets from the book in my notes to emphasize certain thoughts, but in deference to the author and readers of this unreleased book, I will forego that practice here.
After wars there is hatred. If you’ve ever talked to an American veteran of World War 2 who experienced the Pacific battles, many of them had an undying hatred of the Japanese. And that hatred was reciprocated. It may heal over time, but directly after the conflict it is fierce.
Tad Williams captures this (and other points) scarily well in this novel that takes place shortly after the battle at the Hayholt at the end of To Green Angel Tower. Duke Isgrimnur, whose son Isorn was killed by Pryrates and Norns in that battle, leads an army of Rimmersmen and others to chase the Norns as they retreat north, all the way back to Nakkiga. The Duke’s men’s increasingly fervent goal is genocide, to completely exterminate the Norns. Though tired of war, they are propelled by a hatred and an “it’s us or them” mentality (as it was the Norn’s intention to end the human race with The Storm King and Utuk’ku’s plans).
The Norns return the harsh sentiment. In MSandT the reader saw little of the Norn viewpoint, save for small vignettes from Utuk’ku. In The Heart of What Was Lost, as hoped for, the curtain is pulled back to reveal a very complex and developed Norn society, as one would expect from a people who had been around for many human lifetimes. The Norns believe, rightly so, that they are fighting for their very existence. With their Queen Utuk’ku in a deep sleep of recovery after her part in the battle, they are on their own. And their is “court intrigue” as those leaders who would normally bow to Utuk’ku vie for leadership roles and influence in what remains of the Norm kingdom.
There are dark parts of this novel, parts that remind me of Williams’ writing in Happy Hour in Hell (reviewed here on the archived and Hugo-award winning SFSignal) from his Bobby Dollar series (a series I highly recommend, and hope Williams continues to write…AFTER he’s finished The Last King of Osten Ard, of course). There is a viciousness to the battle scenes and tactics not seen in MSandT but appropriate for the enmity of these two armies. In MSandT, when a long-lived Sitha was killed, there was an almost palpable sorrow in the writing…that one who had lived so long and had so long yet to live would perish. In this novel, perhaps because there is so much death for the Norns, that sentiment is different; it is the blasphemy of genocide that permeates each Norn death.
There is not much character development in the humans (we’ve known the Duke and Sludig through thousands of pages, so not much is needed), other than the view of a Pedruin named Porto who gives the common soldier’s perspective. This is well played, as in any war the common soldier normally wants nothing more than to survive and return home, and desires the same for his brothers-in-arms. Porto portrays this well, as the hatred of the Norns is left mostly for others (save when the Norn violence hits close to him), and Porto stays, committed to his fellow men but constantly pining for distant, warmer places…and survival.
I admit that after the mysteriousness of the Norns in MSanT (which fed their mystique), as a reader I was apprehensive about seeing them as real characters, and losing that veil of unknowing. But that apprehension faded the as the story moved. The Norns are paraded out for all to see, with their family histories and specialities: Singers, Builders, Sacrifices. Simply put – Singers work with magic, Builders build and Sacrifices are soldiers – an interesting but appropriate name for the riskiest job of a long-lived people. Family histories are hinted at and in some cases revealed. The Norns have human slaves as well, unlike the Sithi. One wonders if this was another of the reasons for the split between the two (Sithi and Norn), or if the Sithi learned to survive without the Dwarrows (the other part of the Gardenborn who were used mostly as slaves) better than the Norns. It would be interesting (and perhaps will be revealed?) to learn if the Norn builders learned from the dwarrows how to do their craft of bending stone to will. And, though hinted at here (no spoilers), it will be interesting to see how the Norns and their slaves change in the The Last King of Osten Ard. There are several great new characters to follow into the forthcoming series.
There is a building suspense in the question of whether the Norns would survive, fed by notes interspersed amongst the novel from a Chronicler of the Norns (Lady Miga). With The Last King of Osten Ard series looming, and the Norns set to play a roll in those tomes, there is little room for such suspense of whether the Norns would be wiped out. But there is uncertainty on which of the long-lived Norns will survive and how the Norns will be changed; and how, if at all, the humans like the Duke will be changed from this last ordeal. One assumes this book would be the Duke’s last hurrah, as the Last King series is said to be set 30-40 years after these events. The Duke is already an old man, and one would assume he would not make an appearance. From my standpoint, he will certainly be missed; his characterization was outstanding throughout the entire MSanT series, as well as in this addition to the canon.
With MSandT there were some glimpses of the Garden, of the time before the Gardenborn (Norns, Sitha and Dwarrows) were driven out by “Unbeing.” And there is a bit more of that in The Heart of What Was Lost. As we are shown a more complete vision of the Norns world in this novel, I hope we see more of the history of the “Garden” and what really drove them out in the next series..
One note on the setting, the descriptions of which show the effort Williams puts into such things: much of the latter half of MSandT took place in the cold, in winter-like conditions, and this book has more of the same. As the locale moves further north, the weather grows colder. It is amazing how Cali-based Williams can write the cold so much that the reader knows, even feels, how much the characters abhor it.
This is a novel that requires an extensive background in Osten Ard (or at least of the events of To Green Angel Tower), but given Mr. Williams’ tendencies in all of his series, this book will be prefaced by a “What had gone before” section to catch up old and new readers. This practice should be the norm among writers on long works and series, other than expecting readers to re-read or catch-up via Internet scraps. There are already (as of December 1) photos around the InterWebs of some spectacular maps that will be included in the book. Hopefully this will be accompanied by “previous events in the series” blurb for new readers…and there should be a lot of new readers. This series influenced the legion of great fantasy writers that are being published today (for more background on this, see this SFSignal article).
It’s been more than two decades since To Green Angel Tower, the last book in MSandT, was released. The 1990s were a different world, or so they seem. But Tad’s books have remained timeless. I, like many, have so been looking forward to this continuation, so much that I hope, in typical Tad fashion, he turns The Last King of Osten Ard “trilogy” into a 4 or 5 book set! (or at least a record setting length for the books).
About a 45 minute drive from where we are in Tomball north toward Montgomery is the Saint Francis Wolf Sanctuary. We did not know about it at all until this past Saturday when they held their open house. It is a fascinating place, housing thirteen wolves (at least when we were there) in a variety of enclosures. They are a 501(c)(3) non-profit, and the annual open house is their big yearly fund raiser.
There are a number of ways to visit the sanctuary, almost all (except the open house) are by appointment only (link here). I highly recommend visiting by an arranged appointment vs. the open house…there were tons of people at the open house, and the road to get to the Sanctuary had cars backed up quite a ways and parked on the side of the road for a long way.
The sanctuary consists for about seven enclosures which have two wolves each. There are two “ambassador” wolves (Tala and Meeko, who is jet black) that were out for pictures as part of the open house. The wolves were, for the most part, lounging (except for Romulus, pictured above, who shared enclosure #7 with snow white Rafiki who never left the house). When they brought Meeko back from his photo ops and took Tala out, most of the wolves got up and paced.
That’s Rajah and Lapua (enclosure #5) greeting their neighbor Meeko, who shares enclosure #6 with Tala who was taking her turn with the photos. The video below is the wolf being taken out.
I’m not sure why all the wolves get excited when one of their number comes back or gets taken out, other than the obvious concepts of greeting, wanting to be let out, or some other pack-like emotion.
The highlight of the open house was Romulus, who stayed close to the fence in spite of (or perhaps because of) the large number of people…including young kids howling, hoping to elicit a response. For the most part, he just sat there, but he did get up and pace. One of the volunteers who was talking to visitors said that the younger wolves were kept toward the end where Romulus and the ambassador wolves were kept, so it makes some sense that the younger ones would be more active.
Below is a picture of enclosure #4, home of Echo and Achilles. You can barely see one of them close to the hut, but the picture gives you a good idea of what the wolves enclosure look like.
The Sanctuary has an on-going fund raiser to move to a new sanctuary location, which plans for a much larger enclosure. The relocation fund and the plans for the enclosure and new location can be found here.
For those of you driving from Houston, I suggest using Waze (someone has added the location and it took us right to it) or following the directions on the Saint Francis Wolf Sanctuary’s web page.
McKinney Falls State Park is about 6 miles from downtown Austin and 3 miles from my son’s apartment. We hiked there on a sunny September Sunday. (For links to our other State Park hikes, see Brazos Bend and Huntsville).
Like many of the State Parks in Texas, McKinney Falls has a long history. Thomas F. McKinney was one of Stephen F. Austin’s original colonists, and the remains of his house are still in the park. There is an excellent book from the Texas State Historical Association on McKinney Falls (link here) that gives a great view of its history.
It is $6 per person to get into the park. We hiked the Homestead Trail (the longest listed trail in the park at 3.1 miles) and portions of Rock Shelter Trail (to the point where it was blocked) and Picnic Trail, and spent time around both the Upper and Lower Falls.
After entering the park and taking the first right, there are three parking lots at the trailhead to Homestead Trail. It is a short walk over part trail, part rock formation to get to the Lower Falls. Though there at not been much rain lately (as usual) the falls was still flowing and there were quite a few swimmers at the lower falls.
Just past the waterfall (either a short rock to rock jump or a wade through the water) the trail continues. We found a sign that pointed toward the Homestead one way and the Gristmill the other; we chose to head toward the Homestead.
The Homestead is from the late 1840s and was (according the the sign) occupied by the McKinney’s until Thomas McKinney’s death in the house in 1873. Several families lived in it until it burned in the 1940s.
Homestead Trail is pretty overgrown; I do not know if this is normal or just from the time of year when we were there. The ground was pretty dry and cracked in places, so given the dry conditions it wasn’t recent rains that had it overgrown. There were certain places where we had to duck under the overhanging brush.
There were some open parts and a little bit of elevation change, but not much. And there were places where you would walk out of the brush and see office buildings or a golf course – one of the “features” of being in a state park this close to a major city.
There were a lot of dogs in the park. Some, like this one, seemed to know the trail quite well, as he was taking his owners on a walk.
There were a couple of places where we could have taken additional trails (Flint Rock Loop Trail, which intersects with Williamson Creek Overlook trail – combining these would provide for an almost six mile hike), but we stayed on Homestead Trail. We finally got back around the the remains of Thomas McKinney’s grist mill, which was interesting (there must have been more water there at that time, but it was bone dry there now) but there wasn’t much left of it.
And then we came back to the lower falls from the other side.
As we walked back toward the trailhead, you can see the large limestone covering that you walk over to get to the falls. It was still before noon but it was already getting warm on those rocks. I’d imagine in the hot Texas summer afternoon sun it would not be a place to be…unless you were heading for a dip in the water.
We then intended to hike along Picnic Trail (the picnic tables gave the name away) and Rock Shelter Trail to get to the Upper Falls. We made it to the Rock Shelter, which we read had been in use as a shelter by people for nearly 4,000 years. There were also some trails that you could scramble down to get a look at Onion Creek.
But the trail was closed right where “Old Baldy” (a large tree) was. We weren’t informed of this at the ranger station, but it wasn’t a long trail so turning around was not difficult. In the picture below you can see “Old Baldy” in the middle. It looks like the rails on the wooden walkway were down and the bridge had other damage.
With no hiking options, we drove to Upper Falls, which had more swimmers and divers that the Lower Falls did.
Here’s a short video to show the extent of Upper Falls.
Overall, it was a very convenient park with some short trails and a couple of really nice waterfall swimming holes.
Back in the day, my son collected Pokemon cards, played Pokemon on Gameboy, and taught me about Pikachu, Snorlaxes, and other interesting creatures…as I’m sure the kids of many others my age did. As my son grew older, he gave his Pokemon card collection to someone much younger who had more enthusiasm (a very generous move, one he semi-regretted when he saw the prices for some of those cards on eBay!) and moved on to other things. Now in his mid-twenties, my son and I are playing Pokemon Go, semi-together from 200 miles away.
Despite the articles about “nerd herd” and getting the geeks out from behind their computers (which is a pretty good thing, IMHO), in addition to the afore mentioned family camaraderie (and I loudly applaud those friends of mine that are actively playing with their kids), there are other obvious reasons certain people should become familiar with this app/game:
Pokemon Go is the top Free app (with in-app purchases) on the Apple App Store and Google Play Store in the US, the UK and multiple other countries, and has been there since it’s release. It is the fastest app to reach 10 million downloads worldwide, reaching that mark in seven days (source). It also currently leads all apps in daily usage time (i.e., how long do users actually have the app opened). (source).
It did have a bit of a head start in both content and database:
There are some characteristics of the game that are familiar, especially to those familiar with previous pokemon games. But the basics are similar to anyone who has used any count/goal based program: collect everything and level up. This is a common development model, whether it is for a beer drinking app like Untappd (see my breakdown of the Untappd app here), a healthcare/shopping app like Walgreens or game apps. There are badges for most everything (similar to programs like Untappd) though I seem to rarely look at them, other than for counts.
These are holes that will be filled, either in future releases or by independent developers. There are already examples of an entire ecosystem springing up around the game; Chat apps (see this developer’s app blog) as an example, I assume to be used to tell people when a rare pokemon is near. There are also several hacks, such as maps that use the app protocols to determine locations of pokemon, pokestops, etc. (most of these can be found in the pokemondev sub on reddit). Some of these are getting shutdown; one even mentioned a “cease and desist” order.
The “augmented reality” piece, where you can use your device’s camera to see pokemon on the background of the real world, is interesting but unnecessary in this game. It is such a battery sucker that I do not know of any players that have not yet turned it off. It is being used primarily as a novelty (I found a pokemon at a landmark) or by businesses to lure pokemon hunters in.
The estimates of how much the game has made the various parties varies. One estimate says that Apple, purely on the percentage that they receive from in-app purchases through the app, will make $3 BILLION in revenue over the next couple of years (source). Since Apple gets 30% of in-app purchases, that would imply an estimate of $7 BILLION in revenue for Niantic (one would assume this gets shared with Nintendo for licensing).
There is, of course, no need to spend money in the game if you choose not to (full disclosure: I do not). Sensor Tower is estimating $1.6 million per day in the US spent. And the app has not yet been launched in Japan where the average spend per mobile user is higher, and the Pokemon craze is even more rabid.
Nintendo’s stock price doubled following the release of the app (chart here) though it has retreated a bit from those highs.
Local businesses are taking advantage as well. Yelp now lets users filter based on pokestop locations. Many shopping areas and downtowns will have multiple pokestops near them. In the game, there are items known as “Lures” which do what the name implies (they lure pokemon to a pokestop for 30 minutes). When this happens, the pokestop lights up on the map, shooting purple pieces up like flares. Small businesses near pokestops are dropping these lures to lure people in while they hunt.
Pokemon Go is almost as well-known these first few weeks for server crashes as it is for having more users than most other applications. Since Niantic spun out of Google, one would assume that they have Google infrastructure. They don’t have Amazon Web Services (AWS), as the Amazon CTO has humorously repeatedly offered health over twitter whenever the servers are down.
As the game added multiple countries over this past weekend (July 16), the servers supporting the game crashed repeatedly, causing the game to be in operable most of that Saturday morning.
The image on the right is all that the players see. There is no notice that the game is having server issues. So users either continue to press “retry” (which comes up after a few minutes of this screen) or kill the app and start over…both of which cause more login attempts and impact on the servers.
From a capacity planning standpoint, one would assume that there would be a trending analysis done on the initial implementation based in the United States before adding in the multiple additional countries. Either this was not done or it was done incorrectly, causing capacity to crash the servers.
This is tolerated somewhat humorously (check out the Pokemon Go reddit forums for examples) for now. But if there are tours, events and other plans made around the app ( as there were that Saturday), this will not be acceptable by the user community for long.
Interestingly as of this writing, Niantic is advertising for a Software Engineer – Server Infrastructure...probably a much needed position just now!
My fellow joggers: we have an enormous advantage in this game of Pokemon Go. And this infuriates my son…and is the only reason I can even begin to keep up with him in this game (and with the many teenagers that are on summer break and do not have to work). That advantage is that mileage matters in several different facets of the program:
It may be obvious, but the downsides to running with the game are:
I have an old Google Glass from an earlier development project. Glass would be a great accessory for this game, and for all games that combine real-world with augmented reality. The ability to see landmarks and have heads-up display facts and stats was one of the benefits of Glass. Unfortunately, the issues it had, particularly with battery life, would have to be fixed. And it had a sweat problem (i.e., sweat be bad for Glass). But image just running along and speaking commands to Glass about throwing Pokeballs…those that make claims of “nerd herd” would have a field day with that one!
My current collection is below. Have fun!