ADSD with AOA and Udi – Day 4

It has been four days since I slept.

I am hallucinating Authorities (aka Services), Bounded Contexts, or is that Business Components? Up is down, down is up. Everything is abstract. Everything is physical but different. Or not.

Today we moved at a much steadier clip through our materials. I was more alert by necessity, and there were fewer tangents, although still enough. There’ve been a few cases of not-really-questions-more-comments-to-try-and-impress, but far more frequent are in-depth tangents that feel like individuals trying to get some free consultin’ out of Udi.

It is of course hard not to bring your real-world scenarios into the learning experience, but there is a difference in the feel of a question motivated by not-quite-understanding and a question that is looking for a solution.

Today was actually surprisingly more concrete and nuts-and-bolts. Still provocative and even surprising in places though, but I wouldn’t have *that* any other way. Why yes, yes, let’s connect the javascript client straight to the database; and the case he made was surprisingly compelling all things considered.

I cannot quite tell how he felt about CQRS; the tone and body-language was somewhat dismissive, but he explained it with a level of nuance and determination at odds with that posture. He was definitely dismissive of Event Sourcing though. And we’re not allowed to use Udi Says for justification, but it was hard not to sympathize with his assessment of the limitations on its value.

He still reveals some things with a larger sense of mystery and caginess than I think is warranted, but at this point I’ve decided the showmanship is just getting the best of him.

And… I was so hopeful.

We got to 200 pages out of 250 around 4pm. I thought today was going to be an “early” one (i.e. 5:30pm for example), since I knew he had a further speaking gig in the evening, and surely he eats?

In the end he raced through to page 237 by about 7pm. I’d have said that bodes well for an early mark tomorrow, but I really have no idea what to believe anymore. I’m doing my best to stay focused and absorb everything throughout the day, but it is … so … hard.

One more day.

I can do this.

And then, hopefully, a more in-depth summary of what I got out of the experience.

The Answer Might Surprise You.

ADSD with SOAAOA and Udi – Day 3

Dear diary, today is day 12 of my 5-Day Training Course.

I would complain about the energy drain if not for the appreciation that Udi is investing so much of his time. Every day starts at 8:30, and goes well past 6 pm with very limited breaks. It’s a … marathon? (I hope?) We’re now 30 hours in with at least 20 more to go that I can tell, excluding further homework tomorrow.

I am a bit mystified why Udi uses the word “Service” so much when he clearly has a distaste for its nebulous definition and general appropriation. “Authority Oriented Architecture” sounds like a much better descriptor overall, even if Authority isn’t ideally unambiguous either.

IT managed to go through all the good words by the end of last century, re-defining them all into meaninglessness.

The pattern in Udi’s style is abundantly clear by now; cleverly selected examples without singular answers, and a well-honed skill at arguing, together make for a lot of head-scratching around the room. I am enjoying thinking around the provocative propositions he throws out there, but I cannot help but feel there’s a level of empty calories about the exercise.

There will be no technology advice anywhere along the way. That’s an implementation-detail that is case-specific and therefore not something he can (or will) give us. I think some in the class are still hoping/thinking we may end up there, but that’s not the direction this course is following.

There will also be no scientific underpinnings for the theories. De-composing architecture along the lines of his advice is a good thing, because. And by squinting just right I am convinced overall that’s true, but I wish I had something more concrete to hang that on. Case studies. Empirical evidence. A rigid mathematical proof (I can dream…), but that’s also not where this is heading.

It’s a very valuable exercise at stretching the mind, and learning new ways to approach architectural and design decisions though, and that’s not to be sneezed at.

Still no silver bullets, sadly.

ADSD with SOA and Udi – Day 2

So,…

Apparently I am back in school now; after a long day (8:30am – 6:30pm) I have a homework assignment for tomorrow. I had hoped to get some extra sleep tonight, but no luck.

UsingĀ Thing-Oriented-Architecture, I am modelling the service boundaries for a hotel booking system tonight. I probably will save some for on the train tomorrow morning, because I could barely keep awake today and if I don’t sleep well, tomorrow will be worse still.

As much as yesterday felt like the set-up for some grand unified theory on distributed design, after today it feels like there aren’t going to be any answers, just increasingly vague questions. And a lot of my own opinions. So maybe more than anything this is a course to help me figure out what I believe myself? With some rules-of-thumb thrown in?

So far the single most useful piece has been a helpful question to determine whether services are sitting in the right context together (or not). I can tell it’s going to get a big work-out in time.

And I’m looking forward to the suggested approach to pull information back together into a cohesive interface. I can kinda see where Udi’s leading, but it is still a little bewildering. This may be exacerbated by the fact that heĀ is clearly purposely constructing worst-case examples to push boundaries.

I’m hoping tomorrow brings more answers than new questions.

I’ll hold off on holding my breath.

Day 143 – Baking Trial

I’m on a tight deadline, so this weekend will have to involve primary construction of my architecture project. I picked a recipe from Taste.com.au, and made it in full measure assuming I’d have to do a second larger batch to complete all the surfaces.

Ready to Measure
Ready to Measure

Apparently dimensions can be deceiving.
Reading “7 cups of flour” should have given me a clue.

To Flour Mountain
To Flour Mountain

In any case, I decided to proceed making all the dough, but only constructing a single roof segment tonight. Because it’s the largest and trickiest single piece to make with the oven at my disposal, and it will give me enough indication if the rest of my plans are workable with what I have.

D'ough
D’ough

I hope to have the rudimentary undecorated house standing before the end of the weekend.

Piece of Finished Architecture
Piece of Finished Architecture

Then there’ll be a few more evenings for embellishments on the exterior, before it’s time to eat my creation. I’m having a lot of fun already.

I just wish I could taste a bit… but I need it for the finished product. And I forgot to bake a spare piece!

Day 138 – Planning a Build

Today, a first attempt at video production. It’s a bit primitive; no audio. My goal was to find out the recording quality and whether I could get it through my available tools into a shape that would work on YouTube.

I’m going to build a gingerbread house based on a design for an actual house. So my first step was to print out the floor plan and exterior image so I can work out all the required baking.

The video below deconstructs the floor plan into a set of surfaces I will need. My next step will be to calculate all the dimensions for the various surfaces before cutting them out of cardboard as a template for the baking process.

As you can see, I’ve numbered all the surfaces as well. I don’t want to get my walls mixed up during construction.

Day 57 – The Oddest Hotel

I had enough light this morning to get some good shots of the room that I am in. Some culling was necessary because I had of course not considered all the various mirrors and reflective surfaces in the room, and I doubt anyone out there is waiting for needless shirtless-Jerry pictures.

I think I have mentioned before how this may not be the most modern hotel, but it has an unmistakably interesting atmosphere. It suits me perfectly.

Upon arrival it isn’t entirely clear what you could expect from the hotel. The fountain at the front, and the look of the building try to breathe luxury and atmosphere. The international flags over the entrance scream out tacky and cheesy.

Once inside it luckily leans more towards classy, but in a slightly different era. From the rich red carpets running everywhere, through the solid furniture to the lighting in the hallways could all come out of an Agatha Christie novel if you ask me. Even the occasional sound of screeching trams curving through their iron tracks adds to the illusion.

But then you enter the rooms. And they have clearly been re-purposed from an earlier high-ceilinged life into new hotel-room duties. From the entrance there is a single step down to where the breakfast nook and kitchen are.

But straight ahead there are also four steps up to an intermediate level where the work desk, the coffee table and some comfortable seats are.

And once ready for bed, I need to avail myself of a whole other set of stairs leading to the bedroom/bathroom loft.

Yes, my room has 2 sets of internal stairs.

And then once you fall onto that bed, tired from a hard day worked, you’ll find yourself wondering who decided on the scalloped corrugated iron ceiling pattern. There is a floor right above, and it cannot possibly serve an actual purpose. But it’s the oddest architectural highlight to add to a room.

Still, it all adds to an odd kind of charm.

And a room that is needlessly luxurious for a single traveller.