Architecture Chat #35

After a general catch-up on what everyone's doing and introductions from a graduate new comer (Nick Irvine) - we launched in talking about robotics including:

  • Automated Kiwifruit picking robots.
  • Fruit laser bar coding and it's lack of uptake so far.
  • The possibility of per-ordered fruit i.e. you identify how you want your fruit, and it's picked at the precise moment when it fits the consumers needs.
  • The user of heuristic markings for fingerprinting of individual fruit (ie. the Idea that nature, by design, provides unique identifier for each piece of fruit, or that we could mark a fruit for identification that wasn't detectable/displeasing to the human eye.
  • Smart cars, self navigating cars, convoy or drafting applications for self-navigating cars and how these systems would deal with disconnections or extraordinary circumstances.


As an offshoot of self driving cars peter talked a little bit about Scribe (or livescribe - pens that record what you write and say - in unison - and allow playback or online publishing ) - and the future of pen based capture devices and note taking ie. evernote etc.

We talked around Multi-dimensional separation of concerns, and the idea of having both distinct dimensions (that may not be based on a single physical AOP approach) and modules of concerns, and the challenges/opportunities/solutions these "hypermodules" could provide to every day business problems - this also hi lighted the pitfalls of existing AOP approaches which often let you assemble incompatible/incorrect sets of concerns, which modules could help prevent...

I talked briefly around REST and the concept of a generic RESTful application development platform that I've been prototyping lately (like dream, but a little more resource and query oriented, and of course with OAuth support OOTB) rather then re purposing an MVC framework or using WCF (which also feels like a bad fit) or ADO.Net Data Services.

Last of all we talked about Mass Transit just as we were breaking up - Jamie noted he'd been working on a similar project (but for java?) while at Auckland Uni.  Perhaps I'll have a more in-depth report on it next time as I'm currently experimenting with it at the moment when I get time.

Thanks all for coming - write-up's of the previous chats can be found on the wiki.

Read More

2008-10-08 - Upcoming Architecture Chat

Hi All,

The Architecture Chat is Tomorrow - or probably "today" by the time your read this - Thursday 9th October, 11:30am, Garrisons, Sylvia Park.

Some topics that have caught my eye since last time include:


If anyone else has some additional topics they'd like to discuss (or raise in absence) then just leave a comment on this post or send me an email.

See you all tomorrow.  And remember newcomers are always welcome - see the Wiki
for details on location and write-ups from previous sessions.

Read More

Moving to Orcon LLU - bumpy ride so far

As some may have noticed, this blog has been up and down like a
yo-yo for the last two weeks.



The issues are caused by the fact that I host it off the home
office connection - which by and large has been solid as a rock for
the last 2 years, considering the amount of traffic the site gets
is fairly minimal.



I opted to be one of the first guinea pigs to try the LLU (Local
Loop Unbundled) offering from Orcon on the home office - alas it
has not been a pain-free experience.  I think google analytics
tells the story best:







The connection got switched to LLU on around the 21st / 22nd of
September - at which point my connection became a bit erratic -
then it started working well enough - before going wonky again, and
then completely falling over altogether on the following Saturday -
at that point there was no sync.



Around Wednesday sync was restored, then Auth as well on thursday
(so 5 days without any access) - the connection was looking ok at
that point, but then a day or so later I started noticing that it
was disconnecting every 5 to 10 minutes, then taking another 20 or
so seconds to re-establish the connection, that's still happening
as we speak - though they helpdesk has now raised the priority of
the ticket to urgent in the hope that it might be resolved
soon.



So far I've been a pretty disappointed with the alacrity of Orcons
resolution process and the lack of direct contact that can be made
with the LLU team.  Normally with Orcon issues get logged with
the help desk, a ticket is raised, and after a couple of days you
end up dealing directly with corporate support (i.e. people who
know what's wrong) - this process works well, and seems to filter
out those people who actually have problems related to their own
hardware or lack of knowledge.



Not so with LLU, you raise a ticket, but the LLU team can't be
contacted directly, and as happened with me - I had no connectivity
for 5 days, and also nothing done about the issue, it just sat in
the queue - and the helpdesk did not seem to know any more about
the issue then I did - I end up feeling bad having to pester the
helpdesk every day to find out the progress on the issue - and they
keep feeding me the same line of "the LLU tech will call you once
the issue has started being worked on / resolved, I'm sure they'll
do a card reset 1am tomorrow" - So far nobody from Orcon has ever
called me (and I'm not actually sure they ever did do a card reset,
but I suspect that's probably not the issue either).



Now I'm not blogging this out of Venom - I mean all said 'n done I
am guinea pigging the service to some extent and I know if I'd just
stuck with my previous telecom/Orcon mix none of this would have
happened - and the @Orcon folks on twitter have offered to help
push the ticket through quicker which was nice (incidentally ISP
available on twitter == good) - but still I just hope the issue
resolution process becomes a little more robust, and I thought this
might be interesting to anyone else out there considering jumping
on the LLU band wagon.



So my peeves so far are:

  1. Orcon don't actually seem to be doing any follow-up - I had
    to do all the calling (and sitting in the queue) incidentally,
    3pm is the perfect time to call their helpdesk, it's never
    busy.

  2. The LLU team can't be contacted - that bugs me - pestering
    the help desk is counter-productive for days on end, when the
    issue is sitting with the LLU team.  Being able to check the
    ticket status (with notes etc.) on-line would be have been nice
    as well (and saved some phone calls).

  3. The helpdesk doesn't seem to even know when the LLU team will
    look at an issue.  I got the distinct feeling the help desk
    guys knew as little as I did.

  4. No weekend support - I lost connectivity early Saturday, but
    the LLU team doesn't work on the weekend (or so the helpdesk told
    me) - this sucks - telecom have engineers working weekends,
    especially as Orcon are responsible for phone issues as well, I
    could end up with no internet or voice for an entire weekend -
    something I've always found Telecom very quick to respond
    to.  I would hope this only applies to home customers!


Hopefully these (and the technical issues I'm having) are all
just teething problems and will go away as the LLU roll out
continues - in the mean time forgive this blog for being partially
unavailable, and my apathy in not bothering to move the site to
dedicated hosting (which I do plan to do sometime this year,
probably along with a change in blogging software - but I'm too
busy with other things at the moment).
Read More

Arhictecture Chat #34

We talked about a couple of announcments, including the Prism V2 Drop 1, and it's multi-targeting support for Silverlight/WPF (Something we've talked about for a while since WPF & WPF/E first emerged) - we did cover some of the other announcments in
this post as well.

After that we ended up with quite a general discussion on what makes adopting unit testing (and test driven) practices difficult and how mocking/stubbing/AAA etc. fits in.  Interesting side-topics included the idea of teaching test driven development as the very first part of a first-year programming paper at university, behaviour driven development / specs etc.

We had another new comer this week - Guy - who gave us some perspective on how shops still focusing on C/C++ work - as always it's great to have newcomers coming along and contributing to the conversation.

Guy was Albany based, which raised the question again of if we need to have the odd Architecture chat over on the shore - my only concern is that we'd probably loose half of our existing attendees, so unless I got interest for a good 4 or 5 people on the shore It's
probably not worth bothering with - and we'd need a location that's not too noisy (we abandoned our original location in Ellerslie for that very reason).

Apologies for the late post - I have been experiencing a lot of issues since  moving to Orcons LLU (that'll teach me for hosting this blog and wiki on-site :)

Write-ups of previous Architecture Chats can be found on the wiki here.

Read More

Upcoming Architecture Chat - Thursday 25th September 2008 @ 11:30am

Architecture Chat Tomorrow (Thursday) 25th September 2008 at 11:30am, Garrisons, Sylvia Park, Auckland, New Zealand.

Some ideas for topics:


All are welcome - and for new comers directions can be found on the wiki.

If anyone has any other topics please leave a comment on this post or flick me an email, or of course just bring along your questions/topics on the day - otherwise I'll see you all there tomorrow.

Read More