All right everyone. CoVID lockdown is ending, back to the office with you all… maybe.
This week for AntipodeanSF in the episode “Angelina” my narration of the story “Nothing unusual happened on the way to the office” by Colin L Howe
Link to the radio show is below. Enjoy!
New month, and a shiny new narration for AntipodeanSF . This week in the episode “Anseka” my narration of the story “Job Search” by David Schole.
Link to the radio show is below, with this story appearing around the 21min mark.
New narration for AntipodeanSF . This week in the episode “Andreseloy” my narration of a story by the late Dr. Shaun A. Saunders, “Mallcity Endgame: The Great Velocity”.
Link to the radio show is below.
Found this paper this morning and was fascinated. The word ‘innovation’ is often overused – don’t get me started on the word ‘strategy’. This is innovative, and clever. To build a functioning satellite for $USDS3,500 by reusing a smart phone and wiring it together with some pre-built componentry is a brilliant concept.
I’m not sure where this initiative went since it was launched (intentional pun) but it appears to have shut down around 2017.
Hyperlink to the paper is HERE and other information is at their website at THIS LINK.
The video below, courtesy of the Brick Experiment Channel, caught my eye as a nifty example of iterative and accumulative design problem solving. This is not constrained to the tangible world. In systems design, a problem with a basic starting point which is responded to with a simple and effective solution often spawn a series of step-up demands and higher complexity problems over time.
There can be a few reasons for this, such as:
By design – an iterative/incremental approach to problem solving beginning with a ‘minimal viable product’ (MVP) which is tested, released, and then informs subsequent design in a conscious, methodical and step-wise fashion
By evolving requirement – the subsequent problems did not present themselves until the initial problem had been resolved due to evolution of the system itself
By naivety of requirement – the clients of the solution did not realise they had additional problems to solve or believed that the initial problem to be solved was the only one
By low capability awareness – the clients of the solution were not aware that the problem was able to be solved and therefore had not applied resources to solve it
By status quo bias – the clients of the solution were emotionally anchored on the current system, despite inadequacies, and so avoided attempts to solve the problem