SomeBeans http://www.ianhopkinson.org.uk ...the makings of a small casserole Wed, 04 Sep 2019 14:55:56 +0000 en-US hourly 1 27293786 Book review: Superior by Angela Saini http://www.ianhopkinson.org.uk/2019/09/book-review-superior-by-angela-saini/ Wed, 04 Sep 2019 14:52:12 +0000 http://www.ianhopkinson.org.uk/?p=3018

Continue reading »]]> superiorNext I turn to Superior: the return of race science by Angela Saini, having recently read Inferior by the same author. Inferior discusses how men of science have been obsessed with finding differences in all manner of human abilities on the basis of gender. Superior does the same for race.

In both cases largely male, white scientists spend inordinate amounts of time and effort trying to demonstrate the superiority of white males. There is a still pervasive view amongst scientists that what they do is objective and somehow beyond the reach of society. However, there is a a choice to be made in what is studied which goes beyond the bounds of science. Unlike Inferior, Superior reveals explicit funding and political support for racist ideas which stretch to the present day.

For Saini this is somewhat personal since she is of Indian origin, and considered a “Black member” by the NUJ. This highlights one of the core issues with race. The limited palette of races introduced in the 18th century ignored the huge variations across Africa and Indian to render the world down to White, Black, Indian, Chinese.

Furthermore the genetic variations within races, are bigger than those between races. Race was a construct invented long before we knew anything about genes, and it was a construct assembled for specific geopolitical purposes. The fundamental problem with race science is that it is literally skin deep, you might as well try to establish the superiority or otherwise of people having brown eyes, or red hair. The variations in genes amongst red-heads are as large as those between red-heads and blondes.

The account is historical, starting with the first “research” into race, when Britain, France and other countries where building empires by colonisation and the slave trade was burgeoning. It became important to rationalise the mistreatment of people from other countries, and race was the way to do it. White scientists neatly delineated races, and asserted that the white race was at the top of the pile, and thus had the right to take the land of other races, who were not using it correctly, and subjugate them as slaves.

Darwin’s work on evolution in the 19th century gave race science new impetus, white superiority could be explained in terms of survival of the fittest – a natural law. These ideas grew into the science of eugenics which had the idea of improving human stock through breeding. This wasn’t a science practiced in the margins, still renowned figures at the heart of statistics and biology were eugenicists.

Eugenics increased in importance prior to the Second World War but the behaviour of Hitler and the Nazis meant it fell out of favour thereafter. This is not to say race science disappeared. In 1961 a number of academics set up the journal Mankind Quarterly, funded by Wickliffe Draper’s Pioneer Fund. This had the appearance of a respectable academic journal but was in fact an echo chamber for what was essentially white supremacists. Similar echo chambers were set up by the tobacco and oil industries on for smoking and climate change. They look sufficiently like academic science to fool outsiders, and for politicians to cite them in times of need but the rest of their parent fields look on in horror. Mankind Quarterly is still published to this day, in fact within the last couple of years Toby Young was forced to resign as director of the Office for Students having attended meetings at University College London organised by Mankind Quarterly. University College London has a troubled relationship with race science.          

This isn’t to say that all race science is maliciously racist. The human genome project led to plans to establish the diversity of the human species by sequencing the DNA of “isolated” groups, this typically meant indigenous people. Those promoting this diversity work were largely liberal, well-meaning if not somewhat paternalistic but their work was riven by ethical concerns and the natural concerns of indigenous people who they sought to sample.

Touching on origins Saini observes, once Neanderthal DNA was found in white Western Europeans the species experienced something of revival in reputation. Once a by-word for well, being Neanderthal, they are now seen as rather more sophisticated. It turns out the 10,000 year old Cheddar man was surprisingly dark-skinned certainly to Britons wishing to maintain their ancestry was white. The key revelation for me in this section was the realisation that large scale migration in prehistoric times was on on-going affair, not a one off. Waves of people moved around the continents, replacing and merging with their predecessors. 

It has been observed that some races are prone to particular medical conditions (at least if they are living in certain countries, which should be a clue) therefore we seek a genetic explanation for these differences. This approach is backed by the FDAs approval of a drug combination specifically marketed to African Americans for hypertension. Essentially this was a marketing ploy. African Americans experience significant environmental challenges which are risk factors for hypertension, hypertension is a complex condition for which there is no simple genetic explanation.

Even for sickle cell anaemia, for which there is a strong genetic basis, using race as a proxy is far from ideal – the rate of the sickle cell anaemia gene varies a great deal across Africa and is also common in Saudi Arabia and India. A former colleague of mine from Northern Italy had the condition.

For a middle-aged white Western European male scientist Superior is salutatory reading. As for Inferior people men like me have repeatedly asked “What makes us so special?”, it is long past time to stop. 

]]> 3018
Book review: Gods and Robots by Adrienne Mayor http://www.ianhopkinson.org.uk/2019/08/book-review-gods-and-robots-by-adrienne-mayor/ Thu, 08 Aug 2019 05:46:31 +0000 http://www.ianhopkinson.org.uk/?p=3012

Continue reading »]]> gods_and_robotsThis is a review of Gods and Robots:Myths, Machines, and Ancient Dreams of Technology by Adrienne Mayor. The book is about myths from mainly ancient Greece, and how they relate to modern technology. Material from the Etruscans, and to a lesser extent Indians, Chinese and Romans play a part.  

The central characters in the book are Talos, Medea, Daedalus, Hephaestus, Pandora, Prometheus with a small part for Pygmalion.

Talos was an animated bronze statue, made by Hephaestus – the god of the forge, to guard the island of Crete. He appears in a number of stories but most notably in that of Jason and the Argonauts. He is killed by Medea, who promises him eternal life but instead kills him by removing a bolt from his ankle which releases the vital fluid that fills his body. Talos appears in mythology in the 5th century BC. Medea is a witch who offers Pelias eternal life but instead tricks his children into killing him.

Prometheus was one of the mythical Titans, and was responsible for creating humans, and giving them fire – for which he was punished by Zeus. Depictions of his act of creation vary, with earlier representations showing him manufacturing humans in the way one might assemble an automata whereas later representations show him animating human figures.

On my first reading Daedalus appeared to be a semi-mythical character, that’s to say a historical figure whose actions were extended in the telling. However reading more widely it seems he was mythical. His actions, designing the labyrinth for King Minos, making wings for himself and Icarus to escape the King and making highly realistic statues are on the boundaries of the possible.

Pandora was constructed by Hephaestus at Zeus’s direction to bring evil to the world. Again she is a constructed being, and representations of her show her as being different from other figures with something of an “uncanny valley” look to her. Pygmalion carved a statue of a beautiful woman which Aphrodite brought to life. I was intrigued to discover that the self-propelled mops and buckets in Disney’s Fantasia have antecedents in Goethe in the late 18th century and Lucian of Samosata in 150AD.

Bronze statuary seem to be a recurring theme in the book, for the period when these myths arose bronze was seen as an almost magical metal. Artisans had learnt the lost wax process for casting which enabled them to create hyper-realistic statues of people and animals. In myth these bronze statues were associated with heat, Talos kills his victims by crushing them in a burning embrace, Hephaestus’s Colchis bulls were made from bronze and had burning skin.

Another theme of the book is immortality, something that mortals seek to gain from the gods. Reflected today in modern life extension research.

The Greek mythology I know I believe I learnt as a fairly young child from films like Jason and the Argonauts (cited in this book), and I think the book of the Clash of the Titans film amongst other modern reproductions of these tales. What is missing from this education is an appreciation that the characters in these stories are not singular, in the historical record there are multiple versions of each character stretching back over many hundreds of years.

As someone with no classical training I am very curious as to how the stories in this book reach us. As I understand the earliest original writing on paper is something like 1500 years old which leaves a thousand or so years back to some of the stories in this book. Mary Beard’s book SPQR touches on this briefly. Gods and Robots does not explicitly address this question, it shows us pictures of ancient vases and talks about works that have been lost but are recorded by later writers but does not join the dots.

What do these antecedents to robots in ancient myths mean to us today? Perhaps the striking thing is that the robots we see in cinema dating from the early 20th century, and being realised now, have precursors dating back thousands of years. We have been imagining robots for a very long time similarly we have been imagining life extension for a very long time. However, machines for computation and factories do not figure in this book. The Antikythera mechanism makes a brief appearance – it dates from something like 100BC – but it is more an illustration of how sophisticated Greek artisans had become. In some ways the striking thing about the Antikythera mechanism is its uniqueness, it is the only device of its type from this period and we don’t even see simpler devices as far as I am aware. 

The book finishes with some instances of mythological devices appearing in real (ancient) life. It has to be said that a number of these are of a gruesome nature, more than one tyrant took pleasure in forcing people to jump from great heights with Daedalus-like wings leading to their death. Phalaris used a bronze bull to roast people alive.

This is a fairly short book, I think the main thing it leaves me with is a desire to know more about the myths of the ancient world have reached us rather than the central topic of the book.    

]]> 3012
Book review: Designing Data-Intensive Applications by Martin Kleppmann http://www.ianhopkinson.org.uk/2019/07/book-review-designing-data-intensive-applications-by-martin-kleppmann/ Wed, 24 Jul 2019 09:21:10 +0000 http://www.ianhopkinson.org.uk/?p=2989

Continue reading »]]>

Designing Data-Intensive Applications by Martin Kleppmann does pretty much what it says in the title. The book provides a lot of detail on how various types of databases and database functionality work, and how these can be plumbed together to build applications. It is reminiscent of Seven Databases in Seven Weeks by Eric Redmond and Jim R. Wilson, in the sense that it provides a broad overview of a range of different data systems which are specialised for different applications. It is authoritative and well-written. Seven Databases is more concerned with the specifics of particular NoSQL databases whilst Designing Data-Intensive Applications is concerned about data applications rather than just the underlying database.

The book is divided into three broad sections covering foundations of data systems, distributed data and derived data. Each chapter starts with a cartoon map of the territory, which I thought would be a bit gimmicky but it serves as a nice summary of what the chapter covers particularly in terms of the software available.

The section on data systems talks about reliability, scaleability and maintainability before going on to discuss types of database (i.e. relational, graph and so forth) and some of the low-level implementation of data storage systems such as hash indexes and B-trees.

Reliability is about a system returning responses in a timely fashion, Amazon have observed sales drop by 1% for every 100ms of delay, other have reported a drop in consumer satisfaction of 16% with 1 second slowdown. The old academic in me twitches at providing these statistics without citing the reference. However, Designing Data-Intensive Applications is heavily referenced.

There is some interesting historical detail, including the IMS database which IBM built for the Apollo space program in the late 1960s (which is still available today), and the CODASYL database model for graph-like databases from a little later. Its interesting to see how some of these models have been revisited recently in light of the advent of fast, large memory in place of slow disk or even tape drives.

I was introduced to databases rather late in my career, they are not really a core part of the scientific computing background I have. Learning the distinction between OLAP (analytics) and OLTP (transactions) databases was useful. Briefly, transactional databases are optimised to work on single rows and provide fairly strong guarantees on transactional integrity. The access pattern for analytics databases is different, typically analytical workflows want to take the contents of an entire column and carry out aggregations and calculations over the whole column. Transactions are not so important on such databases but consistency is important, a query may take a long time to run but it should provide results as if it ran on the database at a single point in time. These workflows are better serviced by so-called column-stores such as Vertica.

The section on distributed data systems covers replication, partitioning, transactions and consensus. The problem with distributed systems is that you never know things have failed for ever, and its difficult to know what order things have happened in. This reminds me a bit of teaching special relativity to physics undergraduates long ago.

It is hard to even be able to rely on timekeeping on servers. I found this a bit surprising, when we put our minds to measuring time we can be incredibly accurate. GPS time signals have an accuracy significantly better than microseconds, yet servers synced well using NTP (Network Time Protocol) achieve something like 100 milliseconds – a factor of thousands poorer. And this accuracy is only achieved if everything is configured correctly. This is important because we therefore cannot rely on timestamps to provide a unique order for events across multiple servers, nor can we even rely on timestamps synced with NTP to be always increasing!

The two big themes in terms of databases are transactions and consensus. These are the concepts that provide the best assurance on the integrity of operations and their success over distributed systems. I used the word “assurance” rather than “guarantee” deliberately because reading Designing Data-Intensive Applications it becomes clear that perfection is hard to achieve and there are always trade-offs. It also highlights the problems of the language used to describe features. Some terms are used in different ways in different contexts.

The derived data sections starts with praise for the Unix way of piping data between simple command line scripts, Data Science at the Commandline covers this area in much more detail. It then goes on to discuss the MapReduce ecosystem and the differences between batch and stream processing. This feels like a section I will be returning to.

The book finishes with some speculation as to the future of the field, the two thoughts that stuck with me are the idea of federated databases, systems which use a common query language to interface with multiple different datastores. The second idea is that of unbundling functionality so that, for example, data may be stored in a standard SQL database for unique ID based queries and in Elasticsearch for full-text search queries – in some ways these are simply different facets of the same idea.

Designing Data-Intensive Applications is a big book with no padding, it is packed with detail including many references, but remains readable. Across a fair number of titles this is definitely one of the better technology books I have read.

]]> 2989
Book review: Sprint by Jake Knapp http://www.ianhopkinson.org.uk/2019/06/book-review-sprint-by-jake-knapp/ Sun, 02 Jun 2019 14:58:04 +0000 http://www.ianhopkinson.org.uk/?p=2983

Continue reading »]]> sprintSprint: How to Solve Big Problems and Test New Ideas in Just Five Days by Jake Knapp with John Zeratsky and Braden Kowitz is another book in my business oriented stream of reading.

The sprint is a 5 day programme for planning and running a consumer test of a prototype, starting on Monday with the consumer test on Friday. The programme is laid out in huge detail, even lunch times and break times, with suggested menus are proposed and a maximum size for the sprint team of 7. It is something of the spirit of a “sprint” in the Agile sense but not the same thing.

The book arises from the authors’ experiences at Google Ventures, a venture capital firm, and their work with startups for the most part. I suspect this has a bearing of the cited success of the process, startups are typically compact organisations and typically at the beginning they really need to get something in front of customers. This looks like a great way of doing that, I can see it being more challenging in a mature organisation. Knapp does provide some examples from more mature organisations as well, and mentions at the end that college lecturers have adapted it for courses.

Knapp sets up the sprint as being in contrast to a conventional brainstorming session where everyone has an equal say and no idea is too stupid. The drawback of the brainstorming method is that typically a huge number of ideas are generated in the session, many of questionable quality and then nothing happens afterwards.

Sprint is strong on the idea of a Decider, someone that will make the ultimate decision at points through the programme. The Decider is typically someone like the CEO but if the CEO can’t be available all week then they can delegate to someone else. The Decider can be influenced by spot-votes of other participants but they have the casting vote. Spot-voting is when participants indicate preferences by places sticky spots on items. The higher level implication of the Decider is that there is someone committed to the sprint who has the power to make things happen after the sprint has happened.

The five days of the Sprint are as follows:

  • Monday – defining the challenge and coming up with a target;
  • Tuesday – come up with solutions;
  • Wednesday – plan out the prototype;
  • Thursday – build the prototype;
  • Friday – Run the consumer test; 

My experience of brainstorming is that typically the challenge / target stage is done elsewhere, and the main action is in the “come up with solutions” stage. In this programme the “come up with solutions” part is more of an individual exercise than a group one.

The prototype is planned out as a storyboard of around 15 frames which represent the screens someone might see on a website or app as they conducted the core task. The key initial frame might be a fake news article linking to the prototype website.

The prototype is typically implemented as a facade, it is a fake of a website or app built largely in Keynote (Apple’s presentation software). Initially I bristled at this since my special skill is building fairly functional prototypes in short-order but even I would struggle to do that in one working day. Knapp provides a few of examples where the prototype is something else, they worked with a health clinic in the US which tried out a family friendly clinic arrangement in one of their existing clinics, a pump manufacturer who made the a sales brochure for a new pump rather than a model pump and a robotics company who had the majority of a prototype hotel delivery robot already built.

The commitment of time is large, attendees are expected 10am-5pm all five days, actually 9am-5pm on Friday. There is some scope to allow the Decider to make appearances intermittently, and Monday includes an “Ask the experts” session where outsiders can be brought in for 30 minutes or so. I can see in a larger company that it would be hard to carve out the required time. Also in a larger company it is unlikely you would get a genuine Decider on board, the output of the sprint process would go into competition with other priorities.

The book finishes with a summary of the 5 day programme, a shopping list – indicating the exact number of packs of Post-It notes you should provide and same questions and answers. To a degree I like this, these are my type of people but I can imagine for many the level of detail, control will be oppressive.

Sprint is a quick and easy read, it is chatty in style and is littered with little stories from sprints Knapp and his team have taken part in. I’m probably not in a position where I’d be able to implement the sprint programme in its entirety but provides a lot of food for thought, little ways of changing things.

]]> 2983
Book review: Matthew Boulton: Selling What All the World Desires by Shena Mason http://www.ianhopkinson.org.uk/2019/05/book-review-matthew-boulton-selling-what-all-the-world-desires-by-shena-mason/ http://www.ianhopkinson.org.uk/2019/05/book-review-matthew-boulton-selling-what-all-the-world-desires-by-shena-mason/#comments Mon, 27 May 2019 08:45:43 +0000 http://www.ianhopkinson.org.uk/?p=2978

Continue reading »]]> matthew_boultonMatthew Boulton: Selling what all the World Desires by Shena Mason is a rather sumptuous book featuring a collection of articles and a catalogue of objects relating to Matthew Boulton, organised by Birmingham City Council on the bicentenary of his death in 2009.

Boulton was famous for his Soho Manufactory built a couple of miles from the centre of modern Birmingham. There he started making “toys”, following in the footsteps of his father. At the time “toys” were small metal objects such as buttons, buckles, watch chains and the like for which Birmingham was famous. Over time he brought a high degree of mechanisation and productionisation to the process.

But “toys” were only the start of his business interests, he soon moved into making higher value objects such as vases, candle holders and tableware made from silver, Sheffield plate (silver plated tin) and ormolu (gold gilded bronze or brass), aiming to supply a growing middle class clientele by producing objects at scale with a high degree of mechanisation to reduce cost. For this he cultivated connections in well-to-do society, and employed the best designers.

I was interested to read the article on Picturing Soho by Val Loggie which talks about how the architected design of the factory was essentially part of Boulton’s marketing strategy. The Soho site drew many visitors, it was a feature of the late Enlightenment that facilities such as these attracted visitors from across Europe and America. Boulton even installed tea rooms and a show room to furnish their needs. Although a continuing concern was the risk of industrial espionage which led ultimately to the curtailment of such visits in the early years of the 19th century.

As part of his silver work he campaigned for Birmingham to have its own Assay Office to hallmark silver goods. Previously silver items needed to go to Chester to be assayed and receive a hallmark which was a lengthy journey, costing money and risking damage to items. Gaining an assay office required an act of parliament for which Boulton lobbied in the face of opposition from London silver and goldsmiths. The London case was damaged when a “secret shopper” investigation showed that most silverware passing through the London assay office was below standard, and furthermore they were caught trying to bribe Boulton’s former employees to speak against him. An assay office was granted to Sheffield in the same act.

Boulton also built a mint at Soho, pretty much fully mechanising the process of producing coinage, trade tokens and decorative medals. This work seems to have been one of his more profitable enterprises. Towards the end of the 18th century the government had not minted new copper coinage for quite some time which caused problems because it was often pennies and tuppences that workers needed to buy essentials. Ultimately Boulton was given the contract to mint a large quantity of copper coinage, and was selling minting machinery around the world.

Finally, there was his work on steam engines with James Watt. Watt invented an improvement to the Newcomen steam engine in use at the time which made it much more efficient, in terms of the amount of coal required to produce the same power. Watt also developed engines that produced reliable rotary motion, essentially for driving factory machinery rather than just pumping water out of mines. In the first instance Watt and Boulton acted as consultants, designing engines for specific customers and buying in parts from various suppliers to construct them. They charged a fraction of the cost saving from reduced coal use, which sounds like it was rather difficult to administer. The engine business, they maintained their income by lobbying parliament to extend their patent. Later they built a foundry at Soho which made all of the parts of the engine.

Actually, there was one more thing, Watt and Boulton produced a system for mechanical reproduction of letters and paintings.

Boulton’s businesses were continued after his death by his son, and the son of the James Watt. The silver plate company and foundry lasted longest but by the end of the 19th century they were gone. The Soho Manufactory made it to the dawn of photography but was demolished in 1863. Boulton’s Soho House remains on the site but the rest of the works, and parkland in which they sat have been overtaken by housing. 

In some ways he was the metalworking equivalent of Josiah Wedgewood with whom he was well-acquainted through there membership of The Lunar Society, you can read more about them in Jenny Uglow’s The Lunar Men. He was also interested in the science of the time.

Many of Boulton’s ventures seem to have been of limited commercial value, they often required significant investment which he raised via loans, and revenue typically fell below expectations.

This is a beautiful book, the articles cover the key parts of Boulton’s work at Soho but it is not a biography. The catalogue, which makes up half the book is worth reading too – the photographs are gorgeous and there are descriptive text boxes which explain the wider context of the objects.

]]> http://www.ianhopkinson.org.uk/2019/05/book-review-matthew-boulton-selling-what-all-the-world-desires-by-shena-mason/feed/ 1 2978
Book review: Lost in Math by Sabine Hossenfelder http://www.ianhopkinson.org.uk/2019/05/book-review-lost-in-math-by-sabine-hossenfelder/ Sun, 12 May 2019 07:07:26 +0000 http://www.ianhopkinson.org.uk/?p=2973

Continue reading »]]> lost_in_mathIt is physics for my next read, although my background is in physics and chemistry I don’t read much physics. Lost in Math by Sabine Hossenfelder is a journey through modern fundamental physics and how it has lost its way over the last few years in a quest for beauty rather than relevance.

My background is actually in a different part of physics, the physics of squishy things like plastics, proteins and plants. I stopped being an academic physicist nearly twenty years ago but even at that time there was a definite feeling that some area of physics felt themselves superior to others. Experimental soft matter physicists, like myself, were at the bottom of the pile.

This background does mean that I’ve talked to actually string theorists about string theory, and been intrigued that when you asked them where the extra (20 or so) dimensions the theory requires were the fall back answer was always “curled up very small” – they were unable to express it differently. 

The problem in fundamental physics is that theory is running well ahead of what can be experimentally confirmed. The Higgs boson found at CERN in 2012 was predicted in the early sixties, some 50 years previously. Gravitational waves, first observed in 2016, were predicted by Einstein 100 years previously. Theories today are generating hypotheses which may never be experimentally accessible, on current technology they require accelerators the size of galaxies and and Jupiter sized detectors.

With theory running so far ahead of experiment, how does one decide whether a theory is correct, an accurate model of the universe? The answer of choice for a number of years has been beauty, and naturalness. Distinctly unphysical concepts. Defining beauty is a difficult business, in physics as well as elsewhere. For physicists it means beautiful maths. I wonder whether there is a a link with music here, the Westerners have trained their ears to find particular note combinations harmonious or beautiful but in other traditions different combinations are considered beautiful. Naturalness is a related idea, which has a technical meaning, naturalness abhors taking one very large number from another very large number to leave a number of just the right size. What are the chances of that happening?

Hossenfelder embarks on a world tour to address these issues, talking to scientists across the US and Europe. The style of her writing is journalistic and confessional. This is refreshing to see in a book about physics.

An interesting point raised is that the point of a Kuhnian revolution is as much that our perception of beauty shifts when there is a paradigm shift, as anything else.

The pain for particle physicists is that there is this zoo of 25 particles from which all the matter we can see is constructed but they seem so arbitrary, there is no rhyme or reason to their masses or deep reason for their number. Really, particle physicists want an equation from which these features simply appear rather than find themselves in the position of having to set the values of masses and so forth. This is why physicists are physicists and not biologists or chemists. Chemists revel in mess, biologists are even worse.

The hope was that the LHC at CERN would reveal new particles after the Higgs boson, which would confirm that there was something beyond the Standard Model, this would provide some meat for them to gnaw at and the prospect of planning the next big facility to find out more. But so far there has been nothing, leaving particle physics at a loss.

Cosmology is suffering from a similar problem, although the problem in cosmology is linking up general relativity which explains black holes and the like with quantum mechanics. No one really knows what quantum mechanics means, just that it allows you to explain the values measured in certain experiments really well for reasons best not inspected too closely.

It is sometimes thought that scientists collect loads of data and then come up with a theory that explains it all, this hasn’t been the case in physics for a long time. For the best part of the last 400 years physics has been about coming up with plausible theories and checking to see if they are correct.

Hossenfelder finishes with some thoughts on other types of cognitive and social bias, and even provides an appendix of remedies to address them.

Lost in Math has the air of a disenchanted author making a final tour of the topic she loves before leaving for a job in industry, so it is heartening to find Hossenfelder still in fundamental physics. It seems to me that this level of introspection and the personal touch is something that is needed in academic research.

Fortunately for British readers the phrase “lost in math” is scarcely used in the text.

]]> 2973
Book review: The Culture Map by Erin Meyer http://www.ianhopkinson.org.uk/2019/04/book-review-the-culture-map-by-erin-meyer/ Tue, 16 Apr 2019 09:01:32 +0000 http://www.ianhopkinson.org.uk/?p=2951

Continue reading »]]> More work-related reading for this post with The Culture Map by Erin Meyer, it has the lengthy subtitle “Decoding how people think, lead, and get things done across cultures”.

The Culture Map
The Culture Map

Meyer’s thesis is that there are national cultures which can be described by a countries location on a set of eight axes, and managing fruitful international collaborations requires recognition of this fact and an appreciation of where the team members lie on this scale.

The book is divided into eight chapters, each concerning one of the axes. Typically a chapter will start with what one might term an anecdote or case study which introduces an incident which illustrates the wider point of the chapter. These are all very personal and individual, there are names of people and companies, and specific meetings and scenarios. This is followed by a summary table which lists out where different countries fall on this particular axis and then goes on to suggest some strategies to address potential issues in multicultural teams.

The eight axes are:

  • Communicating – is communication high-context (i.e. implicit) or low-context;
  • Evaluating – is negative feedback provided directly or indirectly;
  • Persuading – principles-first or applications-first? To convince someone do you describe a concrete instance (application) or recommendation or start with a theoretical model (principles)?
  • Leading – hierarchical or egalitarian;
  • Deciding – are decisions made consensually or top-down?
  • Trusting – is trust based on tasks (i.e. work successfully completed) or relationships (sharing meals and drinks);
  • Disagreeing – is disagreement confrontational or non-confrontational;
  • Scheduling – is scheduling linear-time (i.e. on time) or flexible-time?

In most cases the themes are considered in isolation but in a couple of cases there are interactions. For example, between communication styles (high and low context) and negative feedback styles (direct and indirect). The US, and to some degree UK and Canada, are unusual in that they favour low-context, explicit communication but indirect negative feedback. The second case is in the disagreeing style (confrontational or non-confrontational) where a ninth axes is slipped in: emotional expressiveness.

As someone with a background in the physical sciences this type of of book can be a bit challenging. Physical scientists expect theoretical models, such as the one presented here, to represent an underlying physical truth. The model is therefore, crudely, right or wrong. Outside the physical sciences a model can be something else: a framework for exploration and discussion. That’s to say the important thing is not the “correctness” of a model but the opportunity it presents in framing discussions. I suspect this makes us principles-first on the persuading axis.

In this case the physical scientist in my wants to argue about whether there really are 8 axes or should it be fewer (or more) and how well-established is the evidence for each of these axes. For some axes Meyer cites academic work in support. She also provides some rationalisation for where countries fall on an axes on the basis of history or prevalent religion.

The book presents itself as a manual for working between cultures but I wondered from the start whether it was more generally applicable. Individual styles vary within a national culture, if I look at my approach to timekeeping then I fall on the positively Germanic end of the scale, whilst other English people I work with have a much more Italian view of timekeeping. Arguably software developers as a group are on the “low context” end of the communication scale, computers are pretty much the definition of low context communicators – everything is absolutely explicit.

Meyer does touch on this idea briefly at the beginning of the book, talking about how the national scores on a scale represent the average across the distribution of individuals’ scores for a nation but doesn’t really pick it up as an idea.

Some themes arise in these solutions, the first of which is that recognising difference is half the battle. The second is about being explicit about how you will handle areas of potential misunderstanding. Finally, there is a warning about not trying too much to ape characteristics that are not your own. For example, if you come from a culture where criticism is typically indirect, don’t go all out to be direct in your criticism because it really is possible to go too far and you won’t be a good judge of what “too far” is.

I’ve noted when reading books on marketing that the style they use has a distinct marketing air, and I wonder whether the same is true for this book. Are the anecdotes about dinner to appeal to our relationship-trust side, and the summary tables our task-based trust side?

This is really a book which I wish I’d read long ago, in part because I’ve worked in international teams as an academic and commercially in both small and large companies. But also because I see in this book as a guide to working with people more generally, even those in the same culture.

]]> 2951
Book review: Empires of Knowledge by Paula Findlen http://www.ianhopkinson.org.uk/2019/04/book-review-empires-of-knowledge-by-paula-findlen/ Mon, 08 Apr 2019 17:46:26 +0000 http://www.ianhopkinson.org.uk/?p=2948

Continue reading »]]> empires_of_knowledgeMy next review is on Empires of Knowledge: Scientific Networks in the Early Modern World edited by Paula Findlen. Here I find myself venturing a little further into academic history of science than I am entirely comfortable with!

Empires of Knowledge is a collection of essays. Its focus is on networks, and it was stimulated by Stanford’s project on mapping the Republic of Letters. The introduction cites Francis Bacon’s New Atlantis, inspiration for the Royal Society but Findlen focuses on the network which brings the knowledge of the world to Bensalem (the location of this fictional Atlantis).

The first chapter is by Robert Morrison, entitled A scholarly intermediary between the Ottoman Empire and Renaissance Europe. It concerns Copernicus and how he potentially was exposed to Arab astronomers whilst at Padua University. More widely it talks about diffusion mechanisms from the Ottoman Empire through Jewish intermediaries to Europe. I felt it could have done with some lists of actors, and network diagrams. I suspect this is why I’m not a historian.

The second chapter is by Findlen and concerns the Jesuits and their network starting in about mid-16th century. The Jesuits saw scientific knowledge as a supplement to their missionary work. This worked two ways, sharing knowledge from Western Europe to the far flung places they visited was a benefit in their missionary work but they also saw collecting new scientific knowledge and bringing back to Rome as important too. The chapter also talks about some of the travails of trying to coordinate observations across large distances with sometimes inexpert collaborators. The simple passage of a letter from Japan to Europe could take 3 or 4 years. “Scientists” outside the Jesuits saw the potential of this organisation for gathering knowledge. It struck me that the Jesuits rose before New Atlantis was written and before the Royal Society and the Academie des Science in France were founded, these could be seen as secular equivalents.

The third chapter continues the Jesuit theme discussing the Ignatian Tree by Marcelo Aranda, an illustration in Athanasius Kircher’s book “The Great Art of Light and Shadow” which showed the 466 missions of the Jesuit church in 1646 as a tree. Also included were sundials which showed their location as determined by lunar eclipse measurements – a method for finding the longitude but only relevant for fixed locations. Determining the date of Easter was an astronomical problem which had been partly resolved by reform of the calendar but in the 17th century there was some risk of celebrating on the wrong day due to the effect of time zones.

Next up is a chapter by Carol Pal on Samuel Hartlib, called The Early Modern Information Factory: How Samuel Hartlib turned correspondence into knowledge. Hartlib was active in the years just before the Royal Society was founded and kept an expansive correspondence network. He republished within that network but also made work available in print (sometimes to the ire of his correspondents). He left approximately 5000 letters in his archive currently at the University of Sheffield and it is likely that amount is doubled if letters from him in other archives are considered. This seems to be typical of the size of the correspondence of such actors. In a time before scientific journals were published his imprimatur was seen as a sign of quality. The chapter also discusses how such men usually employed scribes to keep up with the level of correspondence, in the absence of photocopiers or word processors.

There’s a certain repetitiveness in my paragraphs, this next one is on the chapter by Iordan Avramov on “Letters and questionnaires: The correspondence of Henry Oldenburg and the early Royal Society of London’s Inquiries for Natural History”! Inquiries for Natural History were essentially surveys containing questions on all manner of topics sent out to correspondents. These were used to elicit information, their consistency allowed for information to be verified and monitored over time, and their very existence provided correspondents with a framework in which to reply – they were not faced with a blank page. The Inquiries also had the function of expanding Oldenburg’s network. He could send out a questionnaire to one of his existing correspondents and ask that they forward it on to someone else if they could not reply.

Ingenuous investigators by Ivano Dal Prete, a vignette on the activities of Antonio Vallisneri (1661-1730) who was a member of the Republic of Letters but corresponded mainly with local contacts in Northern Italy. The point Dal Prete is making here is that although distant lands get the headlines, the Republic of Letters was fractal, what was visible on a global scale was also visible locally. In the late 17th century even Europe was to some degree terra incognita. Del Prate reports that Vallisneri never visited a local (17 miles away) fossil location, the travel was hard in the mountainous area and the natives were hostile.

Corresponding in war and peace by Elise Lipkowitz covers the communications of Joseph Banks and Charles Blagdon during the Peace of Amiens in 1812/13, a brief period in which France and England were not fully at war. This includes some numerical work the volume of transactions. The Peace was fairly tense and the character of the correspondence is cagey compared to earlier periods. Much of the correspondence is between Banks and Blagdon, who was in Paris for the whole of the Peace.

Giant bones and the Taunton stone by Lydia Barnett is about the reception in London by the Royal Society of communications from Cotton Mather in 1712 regarding fossil bones, now believed to be of mastadons, found in New York state and the “Taunton Stone” an inscribed stone discovered in Massachusetts. Mather spent much space in his reports analysing the fossils to a cool reception by the Royal Society – they were much more interested in getting hold of the specimens for their own inspection and interpretation. The Taunton Stone, on which Mather had written much less, raised much more interest. Illustrations (although poor) allowed them to make their own interpretations, and gave access to a history of North America. This was to be used to rationalise the colonization of the area, and the persecution of the native Americans.

The tarot of Yu the great by Alexander Statman reports on investigations into China as the source of all ancient knowledge following an appreciation of the length of its recorded history.

Spaces of circulation and empires of knowledge by Kapil Raj talks about the importance of local knowledge, and local experts in India. Both in William Jones work on comparative linguistics and also James Rennell’s mapping of India. Raj prefers to talk about “spaces of circulation” rather than networks. This seems to be based on an assumption that links in a network must either exist or not exist, my more mathematical view of networks is that links can have weights which may indicate distance or frequency of contact, or any number of attributes.

Recentering centres of calculation by Matthew Sargent continues this theme with a discussion of Van Rheede’s Hortus Malabaricus, a volume on the plants of the Far East. It highlights the varied loci of activity, the book was written mainly in the Far East but published in Amsterdam. Plant samples, and drawings of plants could circulate, travelling the networks of knowledge, without carrying with them the context in which they were collected or the native uses of a plant.

The Atlantic World Medical Complex by Londa Schiebinger traces the path of “bois fer” in a treatment for yaws, a tropical infection. The story brings together medicine as practised in Europe, Africa and the Americas and the difficulties in tracing the contributions made by slaves and native Americans given their position. It also highlights how difficult it can be to be sure of the identity of plants such as “bois fer” at such great separation in time – particularly when the participants at the time were not clear.  

The final chapter is Semedo’s Sixteen Secrets by Benjamin Breen, this refers to the medical works of João Curvo Semedo (1635-1719), a Portuguese physician. He collected the elements of medical preparations from around the world in particular those areas which had been under Portuguese writings. The interesting side to his writing is that although much of the material he recommended was fro outside Europe, the authorities he cited for their use were Western European.  

The book finishes with epilogues by three different authors who do something similar to what I have done here. The format of the book, a set of 20 page chapters, helped me along. Each presents a single thesis, and if I didn’t get along with the author’s style the next chapter came up soon enough. I’m glad I read it but I’m going for something a bit easier next!

]]> 2948
Book review: justinguitar.com Intermediate Method by Justin Sandercoe http://www.ianhopkinson.org.uk/2019/03/book-review-justinguitar-com-intermediate-method-by-justin-sandercoe/ Fri, 29 Mar 2019 10:40:50 +0000 http://www.ianhopkinson.org.uk/?p=2941

Continue reading »]]> intermediate_courseIt is possibly inevitable that my guitar playing has leaked into my book reviewing, or that time I should have spent practicing has gone into reading books, or buying gadgets. So far I have been well-behaved on the guitar buying front, my guitar count is still at one.

However, I have bought a Boss Katana 50 amplifier which counts as saving money since it simulates other amplifiers! As well as 5 amplifier models it allows for 3 effects to be chained together to such as reverb, chorus and overdrive. Justinguitar.com has a whole section on the amplifier (link), this includes downloadable settings which if you’re playing correctly will give you the same tone as Justin and the original track. Any differences in sound will be down to your skill.

But back to the next book, justinguitar.com Intermediate Method by Justin Sandercoe is the follow up to the Beginner’s Course I reviewed previously. I reviewed the Beginner’s Method when I’d worked most of my way through it, this one I’m reviewing after just reading it and trying out a few of the new things.

The Intermediate Course contains five stages in contrast to the nine in the beginners stage, it finishes with a section on different improvisation styles including jazz and fingerstyle playing. The stages tend to develop ideas in previous stages rather than each stage representing a new area. Four months after I started playing it is probably a bit soon for me to be working seriously on this course, although I have a good memory for chord shapes and the minor pentatonic scale my playing is really slow which I think will only be fixed by practice. I could do with learning some more songs too. Justin pitches this very much as an optional course, the Beginner’ Course should leave you competent to play a wide range of tunes.

Barre chords were introduced towards the end of the Beginner’s Course, in this course they are expanded and developed further — indeed barre chords are the main chord work of the book. The beginner’s course just looked at the Major E-shape barre-chord, here we meet the variants of the E-shape (minor, dominant 7th and minor 7th), as well as other shapes (the A-shape and the diminished/half-diminished). One of my achievements playing guitar is a fairly good barre –gained by practicing bits of Creep by Radiohead excessively – it isn’t yet entirely useful since I can’t change very quickly.There are still some of the one minute chord change exercises which I found really useful in the beginner course.  

A new feature of this course is an introduction to standard musical notation. TAB notation works very well for guitarists since it tells you where to put your fingers but it doesn’t provide a visible sign of the rise and fall of a melody also other musicians don’t speak TAB.

The beginner’s course introduced the minor pentatonic scale, here we learn the major scale, the blues scale and a hybrid scale. The importance of scales is that they provide a basis for improvisation.

The intermediate course also covers some more advanced techniques including note bending and hammer on/flick off. This is handy because any cursory glance at guitar tutorials on YouTube will show tutors using these techniques fairly casually. As for the beginners book, Intermediate Course works best in combination with the video tutorials on the justinguitar.com website (which are free). I read the Blues material but the website pulls it together more clearly than the book and certain technical skills are very hard to learn off a page. nI particular the online course talks very clearly about using licks (short runs of individual notes) as “words” in a Blues language.

Alongside the course books there are also Songbooks, I have the Beginners Songbook and the Rock Songbook. These complete the online videos well, provided a record of chords and TABs for what can be complex songs.

I should probably review my “learning journey” at this point, I think the way forward here is to pick a few songs and learn them properly, maybe making a recording. Ideally these should focus on improving particular skills. So far I’ve learned riffs from a few songs – Seven Nation Army, Smoke on the Water, Teenage Kicks, Creep but not really the whole thing. The only exceptions to this are Link Wray’s Rumble, which is pretty simple and I’ve been practicing a 12-bar blues which varies from the version Justin teaches with an intro and an “outro”.

Although I’m not ready to work through this book systematically I’m glad I got it now.

]]> 2941
Book review: JavaScript Patterns by Stoyan Stefanov http://www.ianhopkinson.org.uk/2019/03/book-review-javascript-patterns-by-stoyan-stefanov/ Wed, 20 Mar 2019 17:15:16 +0000 http://www.ianhopkinson.org.uk/?p=2927

Continue reading »]]>

More technology related reviewing next, JavaScript Patterns by Stoyan Stefanov. This is part of my continuing effort to learn JavaScript.

For me this isn’t a question of learning the nuts and bolts of a language but rather one of learning to use it fluently and idiomatically.

I thought this book might be in the spirit of the original “Gang of four” design patterns, but although it mentions these design patterns it is more generally about good style in JavaScript. The book is divided into eight chapters including an introduction.

The first substantive chapter on “essentials” talks mainly about variable declarations and some odds and ends. The most interesting one of these was the behaviour of parseInt which converts a string into an integer. Except if the string starts with a zero, as ISO8601 days and months would, then parseInt assumes it is a number in base 8 (octal)!! I can foresee many long hours trying to debug this problem without this forewarning. This chapter also discusses the importance of coding style conventions.

The second chapter talks about literals and constructors. It strikes me that much of this is about unwinding the behaviour of developers more used to statically-typed languages. The JavaScript way is to create objects by example, rather than take a class definition and derive from that. Although in the permissive manner of many languages it will let you do it either way. Since this book was written JavaScript has gained a “class” keyword which allows you to construct classes as you might in Java or C#.

Next up are functions, JavaScript shares Python’s view of functions as objects, allowing them to be passed as arguments. This is particularly important in JavaScript to provide “callback” functionality which is very useful when doing asynchronous programming. I learn here that the “currying” of function is named after Haskell Curry, who also has a whole language named for him. I always feel when passing functions as arguments that I am fiddling with the underpinnings of reality – it can make debugger difficult too.

I found the idea of functions that redefine themselves on first run interesting, it sounds useful and dangerous at the same time.

The chapter on object creation patterns is all about introducing module like behaviour and namespacing to JavaScript which at the time the book was written were not part of the language. Also covered are making private properties by hiding them in function closures.

The code reuse chapter is largely about patterns for achieving inheritance-like behaviour. This introduces a range of patterns which build up to almost exactly replicate class-based inheritance.

Finally we meet some of the classic Gang of Four design patterns. Some of these patterns, such as the iterator pattern, have been absorbed entirely into the core of languages like Python and more recently, JavaScript. The Observer patterns is implemented in web browsers as events, which are ubiquitous. Perhaps the lesson of this chapter is that some of the Gang of Four patterns have been absorbed into the core of languages, we use them almost without thinking. The Strategy Pattern, which determines algorithms at runtime, fits well with the chapter on functions and JavaScript’s view of functions as objects.

The book finishes with a chapter on patterns for the Document Object Model, or rather JavaScript in the browser. It includes well-known advice such as not testing for browser type but rather testing for functionality. It also has advice on optimising JavaScript for deployment.

There is minimal mention of specific tools or libraries in this regard, although Yahoo’s YUI library is mentioned a few times – Stefanov has worked on this library so this is unsurprising, and not unreasonable.

This book had more of the air of Douglas Crockfords’ JavaScript: The Good Parts than a book on patterns which was what I was expecting. Alternatively perhaps “JavaScript for users of statically-typed languages”, as such it probably works pretty well for Python programmers too although modules have always been built-in to Python and there is a “class” keyword for specifying classes.

JavaScript Patterns is readable though, I’m glad I picked it up.

]]> 2927
http://www.ianhopkinson.org.uk/feed/
www.ianhopkinson.org.uk
crawl=CC-MAIN-2019-39
75545
application/http; msgtype=response
sha1:KEWK6247JFMT5ICALUGOQSTD2V54BKCP
<urn:uuid:38842b50-a0a6-4cbe-94f4-fc51748892bc>
2019-09-18T17:53:28Z
185.11.240.187
application/rss+xml
sha1:ICUU4HIPUJ7KKLLYK75SBNAUJWL25PHL
<urn:uuid:8db11d92-84f0-44df-a02d-15f41fb491b9>
http://www.ianhopkinson.org.uk/feed/
response
<urn:uuid:7e986e6c-734a-4018-9cf8-b53406ccf59a>
isPartOf: CC-MAIN-2019-39
publisher: Common Crawl
description: Wide crawl of the web for September 2019
operator: Common Crawl Admin (info@commoncrawl.org)
hostname: ip-10-67-67-52.ec2.internal
software: Apache Nutch 1.15 (modified, https://github.com/commoncrawl/nutch/)
robots: checked via crawler-commons 1.1-SNAPSHOT (https://github.com/crawler-commons/crawler-commons)
format: WARC File Format 1.1
conformsTo: http://iipc.github.io/warc-specifications/specifications/warc-format/warc-1.1/