Header tag

Saturday, 25 January 2020

Review: Star Trek Picard, Episode 1: Remembrance

CONTAINS SPOILERS

Star Trek's latest series, "Star Trek Picard" is an Amazon Prime exclusive - for the UK, this is a long way from the BBC2 once-a-week episode on Thursday evenings (which I eagerly watched) - and shows how far Star Trek has travelled from its syndicated roots.  I watched the first half of this episode on my mobile phone, then finished off the episode on following day at home on TV.

Star Trek Picard is also a considerable distance from its predecessors.  For the first time since Star Trek Voyager, we have a series which is set after the Voyager/TNG/DS9 era - Enterprise and Discovery were both prequels.  This is a real blast of fresh air - this series is not saddled with all the issues of making its continuity fit with already-known events, and having to fit everything in to a huge narrative.  And the best part of this is that STP sets up its own universe very quickly:  the Romulan sun (or, more accurately, star) has gone supernova and there's been a forced relocation of the Romulan population.  Admiral Picard now lives in a chateau in France, with a sizeable vineyard (as suggested in the TNG episode All Good Things), with a Romulan family.  The exact relationship here, and the personal story of how the Romulans came to live with Picard aren't clear - yet.


Much of the backstory is related during a media interview between a journalist and Picard, as he explains how Starfleet abandoned their mission to rescue the Romulans when they were needed most.  Events took a turn for the worse when the Romulan rescue mission was sabotaged - mortally - by synthetics who hacked into the Mars defence network and blew up the colony on Mars.  This has led to a galaxy-wide ban on the development of synthetics, and leads to bad blood between the Romulans and any remaining synths.

There's a parallel plot concerning a young lady called Dahj.  As she learns that her application to the Daystrom institute has been accepted, mysterious ninja assassins beam into her apartment, kill her boyfriend and attempt to either kill or kidnap her.  In a surprise development, she's able to defeat them in hand-to-hand combat (despite having a bag over her head) and realises that she isn't all that she thought.  Further developments follow as she starts having visions of Picard, and determines to track him down when she sees his broadcast interview with the journalist.

Picard is having bad dreams involving Data (who sacrificed himself at the end of Nemesis), and in one interesting dream, sees Data painting a picture - which Picard later realises is a painting that Data completed while he was alive and which now hangs on the walls of Picard's chateau.


The story develops at a measured pace - there are the high-energy phaser fire and hand-to-hand combat scenes, but there are also lengthy dialogue scenes, but these do serve to unpack this new world, and to further the plot in a sensible and plausible way.  Dahj meets Picard, and the two of them attempt to work out how they are actually connected.  There's a bit of the mysterious (which is a new twist for the generally straightforward science-and-logic format of Star Trek), but Picard realises that Dahj is the woman in Data's paintings - and, in a twist that I'm pleased to have spotted - Data painted two identical pictures (one in Chateau Picard, one in the Starfleet Archive).  

As Picard and Dahj start to come to terms with Dahj's true nature - she is a synthetic (android) - Dahj is caught and killed by the Romulan ninja assassins who have been chasing her down.  Picard has a lengthy and revealing conversation with an AI professor at the Daystrom institute, in which he asks about producing an android from flesh and blood, and gets a long but informative 'no'.  Bruce Maddox (TNG Measure of a Man) has been working on this idea, but has not made any progress.  However, it transpires that Dahj was one of a pair - twins - in the same way as there are two identical paintings of her (painted by Data, and titled "Daughter").

There are some overtones of Blade Runner here (I've never seen it), especially as we discover that Dahj's twin is living and working on a Romulan colony which - in the episode's final reveal - is built inside the remnants of a Borg cube.  The final scene, starting with two dangerous-looking spacecraft (the latest version of the Romulan warbird) moving through a cloaking field and entering a large, dark space station is filled with tension and the slow, steady reveal of the cube is shot in the style of the opening of First Contact, with a musical score that is very reminiscent of the Borg theme.  It's a dramatic conclusion to a great opening episode, and I'm looking forward to the rest of the series.

For those who were expecting to see more of the characters from previous Star Trek series - Seven of Nine, for example - you'll be disappointed.  This is very much the start of a long series (Star Trek has had mixed form with series-long arcs) and the trailer is for the whole series, not for episode one.  There's plenty in this first episode, though, and there is much to be hopeful about.

Season 1 Episode List


Episode 1: Remembrance
Episode 2: Maps and Legends
Episode 3: The End is the Beginning
Episode 4: Absolute Candour
Episode 5: Stardust City Rag
Episode 6: The Impossible Box
Episode 7: Nepenthe
Episode 8: Broken Pieces




Friday, 24 January 2020

Project Management: A Trip To The Moon

Scene: meeting room, some people dialling in remotely. The plan is to launch a manned rocket to the moon, and the project manager (PM) is kicking off the project.
PM "Right, team, let's plan this space journey to the moon. What kind of fuel will we use in our rocket?"
Designer 'Before I answer that, we want to discuss the colour of the nose cone. The design is to paint it blue.'
PM "Okay, blue is fine. Have you had any thoughts about the engine?"
Designer 'No, but we actually think a red nosecone might be better.'
PM "Noted. Let's move on from that, and come back to it nearer the launch time."
Marketing: We thought blue. Now, how we will we choose the pilots? PM "I was thinking that we would have a rigorous selection process."
Marketing: "We can do that. But we'd like to address the name of the spaceship. Our subsidiary want to call it the USSS Pegasus. We want to refer to it as the US Pegasus - the 'SS' was a suggestion from our previous owner. As this is a combined program, we're going to go with the US Pegasus."
PM "Noted. The US Pegasus. Now, about the pilots..."
Designer "And the name of the ship must be in blue text."
PM [making notes] "...blue text..."
Designer "To match the nose cone." PM "Now, circling back to the question of the pilots."
Stakeholder: "Oh, you can't say that. Circling back suggests that the ship isn't going to land on the moon." PM "Sure. So let's go on to the pilots?"
Stakeholder; "Yes, we can sort that out." PM "Thanks. Now - timelines. Do you have a target date for landing on the moon?" Stakeholder; "Yes, we want to land on 28 July, 2020. When do you need to launch?"
PM "How long will the flight take?" Stakeholder "That depends on the fuel." PM "Doesn't it depend on the engine?" Marketing "Possibly. But it's important that we land on 28 July." Stakeholder "Yes. 28 July. We've set that date with our president. It's his birthday"
PM "So who can give me the launch date?"
Stakeholder "Well, we expected you to provide that." PM "Okay, let's assume it takes four days to reach the moon. Can you have everything built and fuelled by then?" Stakeholder "And we'll want to check everything works." PM "Like a test launch?" Marketing "Oh no, we can't have a test launch. We can't have our competitors knowing what we're doing."
PM "No test launch?" Marketing "No." PM "And the pilots?" Stakeholder "I'm working on it." PM "And the fuel?" Stakeholder "I'll find somebody. Somebody somewhere must know something about it."
Marketing "And we'll need hourly readouts on speed. Preferably minute by minute. And oxygen levels; distance from the earth; internal and external temperatures. All those things." PM "Are you interested in the size of the engine?"
Stakeholder "We've been planning this for six months already. We know it'll need an engine." Engineer; "Sorry I'm late, I've just joined." PM "Thanks for joining. We're just discussing the rocket engine. Do you know what size it will be?" Engineer: "Big." PM "Big enough?" Engineer: "Yes. 1000 cubic units. Big enough." PM: "Great. Thanks. Let's move on." Stakeholder: "Wait, let's just check on that detail. Are you sure?"

Engineer; "Yes. I've done the calculations. It's big enough." Stakeholder: "To get to the moon?" Engineer: "Yes." Stakeholder: "And back?" Engineer: "Yes." Designer: "Even if we have blue text instead of red?"

Engineer: "Yes."
Marketing; "What about if we have red text."
Engineer; "The colour of the text isn't going to affect the engine performance." Stakeholder "Are you sure?"
Engineer: "We're not burning the paint as fuel. We're not painting the engine. We're good." PM: "Thank you. Now; how much fuel do you need?"
Engineer: "That depends. How quickly do you want to get there?" PM: "We need to land on the moon on 28 July 2020. I've estimated a four-day flight time." Engineer; "I'd make it five days, to be on the safe side, and I would calculate 6000 units of class-one fuel, approximately." PM: "Okay, that sounds reasonable. Will the number of pilots affect the fuel calculation?" Engineer: "Yes, but it won't significantly change the 6000 units estimate. When you know the number and mass of the pilots, we can calculate the fuel tank size we'll need."
Stakeholder; "But we won't know that until launch." PM: "Until launch?" Stakeholder: "Yes. We don't know how many people we want to send to the moon until the day of the launch." PM: "And the colour of the text? And the nose cone? And the actual text."
Stakeholder: "Will all depend on people we send."
PM: "No test launch?" Marketing; "No. We need this to be secret so that our competitors don't know what we're doing." PM: "So we're launching an undetermined number of people, in an untested rocket of unknown name and size, to the moon, with an approximate flight time and fuel load, at some point in the future."
Marketing: "But it must land on 28 July." PM: "2020, yes. Ok, We've run out of time for today, but let's catch up tomorrow with progress. Between now and then, let's work to decide some of the smaller details like the fuel and the engine, and tomorrow we can cover the main areas, such as the size of the rocket and where it's going. Thank you, everybody. Goodbye for now."

Tuesday, 31 December 2019

Looking Back Over My Shoulder

The start of a new year (or the end of the previous one) is a time for looking forward, setting goals making resolutions and planning for the future. There's a general view that looking back isn't healthy and focusing on the past doesn't create a healthy mindset.  This is often the case if the previous year has been difficult, challenging or simply awful.

I disagree.


Looking back at the past can help us identify our strengths, our victories and how we can build on them.

The shepherd boy David took on the giant Goliath. He volunteered, based on his previous experience and his previous victories with God.  He knew his God; he knew his place and he knew his own history.

1 Samuel 17:
34But David said to Saul, “Your servant has been keeping his father’s sheep. When a lion or a bear came and carried off a sheep from the flock, 35I went after it, struck it and rescued the sheep from its mouth. When it turned on me, I seized it by its hair, struck it and killed it. 36Your servant has killed both the lion and the bear; this uncircumcised Philistine will be like one of them, because he has defied the armies of the living God. 37The Lord who rescued me from the paw of the lion and the paw of the bear will rescue me from the hand of this Philistine.”

David had learned from his experiences with God, conquering lions and bears in previous years, and he used this experience with 'small things' in preparation for his next challenge.

So, look back over your shoulder, take stock and review your victories, your experience and the positives. Carry them with you (like a sling and a staff) and go take on your giants!

This post is one of a series of New Year's Resolutions/Year in Review posts - here are the others in the series:

The Lists of Firsts

A first time for everything: 2018
2019 in reflection
Looking Back Over My Shoulder at 2019
First times in 2021 list
First times of 2022
First times in 2023
Things I did for the first time in 2024

Saturday, 28 December 2019

Just: Not Good Enough

I don't make many New Year's Resolutions.  Truth is, I'm still working through my resolutions from a few years ago: to give more than I receive; to repair not replace and so on.

This year, I have one resolution that I've already started on.  Simply put, Just: Not Good Enough.

"Daddy, come and play with me!'
'I'm just washing the dishes.'
'Just give me a second, I'm just tidying the floor.'
'I'm just sending an email.'
'I'm just checking Facebook'.

And so on.

So this year, I'm going to stop saying "just". If I'm washing my hands, my face, the dishes or whatever, then that's what I'm doing. Saying "just" makes it less important, and makes your request to play or set up your game or whatever even less important. "Just" is not a good enough word to use.

And if you ever catch me saying "just" in my prayers, tell me. I don't usually use "just" but you never know.  Imagine:

"Mighty Father God, maker of the universe, please would you just lift my headache for half an hour."
'30 minutes? Are you sure?'
"Yes, and i pray that you would just bless the meeting at church this morning."
'And this afternoon? When you all go back home?'
"Just this morning is fine, thanks."
'Are you sure??'
"Yeah, and we just pray... that you would just..."

So, I'm going to lift the lid on what I pray for. I don't say "just" verbally when I pray, but I mentally contain God in what I ask for. I've been getting better at asking for the Moon (so to speak) and expanding what I pray for, and asking for bigger things, and this is my main aim for 2020.

Just: Not Good Enough.

2019 in reflection

At the end of 2018 I wrote a summary reflection of the year, and the theme I identified was "first times". 2019 seems to have been similar, with a surprising number of first times. However, the other main theme for the year has been change (I suppose if you do something for the first time it's either the cause or consequence of change).

My three children now all go to the same school, with our youngest moving from pre-school nursery to primary school nursery. It's a subtle distinction, but it now means that Daddy's Taxi only has to make one drop in the morning. 2020 will see our oldest child start high school, which will mean more significant changes ahead.

Planning further ahead into the future, we had a conservatory built onto the back of our house in 2019, and that led to significant change (I still don't think of it as part of our house, and it's been finished for three months now).  It's given us more living space, and in time will become my office during the daytime, as we move things around in the future.

While I was on a work experience placement from high school, the desk I was borrowing had a desk calendar with a daily motto, and one that I saw (and kept) was "Unless we know what we want ), we stand a poor chance of getting it." Over the years, that motto has helped me identify what I actually want, and to work towards it.  This year, I have taken that a step further and extended it to, "And if we don't ask for it, we really won't get it."  What do I want to drink? What would I like for dinner? What do I want to do this weekend? What do I want for Christmas? I've started changing what I say - and how I think - so that if you ask me what I want,  I'm more likely to tell you. And sometimes, it's actually up to me to say what I want to do. I'm lifting the lid on what I think I can do, or what I'm supposed to do, or what I think I'm allowed to do (usually inside my own head) and instead of discounting my own ideas myself (I could never do that), I'm at least going to say what I want first!

So, 2019 has been a year of change - internal and external - and is likely to lead to more change next year.

Happy New Year, and may you ask for what you want.

The Lists of Firsts

A first time for everything: 2018
2019 in reflection
First times in 2021 list
First times of 2022
First times in 2023
Things I did for the first time in 2024



Monday, 18 November 2019

Web Analytics: Requirements Gathering

Everybody knows why your company has a website, and everybody tracks the site's KPIs.

Except that this a modern retelling of the story of three blind men who tried to describe an elephant by touch alone, and everyone has a limited and specific view of your website.  Are you tracking orders? Are you tracking revenue? Are you tracking traffic? Organic? Paid? Banner? Affiliate? Or, dare I ask, are you just tracking hits?

This siloed approach can actually work, with each person - or more likely, each team - working towards a larger common goal which can be connected to one of the site's actual KPIs.  After all, more traffic should lead to more orders, in theory.  The real problem arises when people from one team start talking to another about the success of a joint project.  Suddenly, we have an unexpected culture clash and two teams, working within the same business, are speaking virtually different languages.  The words are the same, but the definitions are different, and while everybody is using the same words, they're actually discussing very different concepts.

At this stage, it becomes essential to take a step back and take time to understand what everyone means when they use phrases like,  "KPIs","success metrics", or even "conversion". I mean, everyone knows there's one agreed definition of conversion, right? No?  Add to cart; complete order; complete a quote, or a lead-generation activity - I have seen and heard all of these called 'conversion'.

When it comes to testing, this situation can become amplified, as recipes are typically being proposed or supported by different teams with different aims.  One team's KPIs may be very different from another's.  As the testing lead, it's your responsibility to determine what the aims of the test are, and from them - and nothing else - what the KPIs are.  Yes, you can have more than one KPI, but you must then determine which KPI is actually the most important (or dare I say, "key"), and negotiate these with your stakeholders.

A range of my previous pieces of advice on testing become more critical here, as you'll need to ensure that your test recipes really do test your hypothesis, and that the metrics will test the hypothesis.  And, to avoid any doubt, make sure you actually define your success criteria in terms of basic metrics (visits, visitors, orders, revenue, page views, file downloads), so that everybody is on the same page (literally and metaphorically).


Keep everybody updated on your plans, and keep asking the obvious questions - assume as little as possible and make sure you gather all your stakeholders' ideas and requirements.  What do you want to test? Why? What do you want to measure? Why?

Yes, you might sound like an insistent three-year-old, but it will be worth it in the end!


Monday, 21 October 2019

How to Solve Edge Matching Cards Puzzles - Practical Advice

While I was at high school, around 25 years ago, I was first introduced to an edge-matching puzzle.  This is made up of 16 square card pieces, with a colour on each edge, that have to be arranged into a 4x4 square so that all the colours of the edges on each piece matches their adjacent neighbour.

It all sounds so easy.

I recently acquired two versions of this edge-matching puzzle - one based on cogs, and one based on footballers - with a view to finally solving it.  I didn't solve the puzzle while I was at school, and I've not revisited it much since, except to conclude that it was impossible, or was going to take longer to solve than I wanted to invest in it.  Well, things have changed, and as it's clearly been pestering me for 20+ years, so I figure it's time to rise to the challenge - especially since the Special Educational Needs Co-ordinator at my high school took delight in telling me that one of the 'weaker' children in our year group had successfully solved it.  Challenge accepted, Mrs Kirkham!

Here, for reference, are the 16 cards in the "Mechanical Mayhem Puzzle":



My first few attempts at the puzzle were not at all successful.  I very quickly connected a few pieces, but never made significant progress, and never really got past about 75% complete  before the pieces refused to go together any more.  I therefore decided it was time to get some hints and help, from that reliable source of all knowledge - the internet.

The most helpful information I found was from a research paper into edge-matching puzzles - apparently, these puzzles are not trivial, in fact they are N-difficult.  The advice was to find matching pairs, and then try to connect pairs to form fours, sixes and eights.  The pairs didn't always form squares, but at least I was now working systematically.  Here are a few candidate pairs, as examples, shown as vertical pairs:

And then some candidate squares:


As I became more familiar with the cards, I quickly identified patterns that would not work - for example there are only two squares which contain the bronze-coloured cog shown on the right.  Therefore they must form a pair, since the likelihood of them both being on the outside edge of the 4x4 square seemed low to me.  I didn't count each kind of cog and work out which were the most and least frequent, but I soon noticed that the large golden cog was very common, as was the yellow daisy-style cog.  The very small silvery cog was quite rare, so I was more careful with how I placed any cards that contained it.

And, with a little trial and error, this approach worked for me (with some adjustments, intuition and observation). Yes, I conquered the edge-matching puzzle (and it only took me 20+ years).



Other recent maths puzzle articles I've written that you may be interested in:

Snakes and Ladders (Collatz Conjecture)
Crafty Calculator Calculations (numerical anagrams, five digits)
More Multiplications (numerical anagrams, four digits)
Over and Out (reduce large numbers to zero in as few steps as possible)