It’s a tough question, but given my current job, one that anyone with a passing interest will ask me. What does blockchain really mean?
The ideas behind blockchain technology marry several disciplines and ideas together. I think the best approach to answering the question starts with considering what sort of answer your audience will most readily understand.
I’m going to go through several ways to describe what blockchain means.
Paraphrasing the original, but my favourite formulation (self deprecating humour is very British) is:
“Bitcoin is like if leaving your car on idle solved sudokus which can be swapped for heroin”
Despite missing the idea of decentralisation, this is quite accurate! …
Before lockdown, Maya was working full time for a charity sourcing food for the impoverished youth throughout the world.
James’ job was a little less grandiose, and he felt a little more morally bankrupt than she was.
Still, they were pretty happy together. They had even moved in together, though it was out of convenience more than passion. They both felt like there was more to understand about each-other than they knew — sometimes James would toss and turn in the night leaving Maya feigning sleep whilst secretly wandering what she could do to relax him, and James was occasionally concerned for the welfare of his cohabitant human being — the short but drunken nights she sometimes led left him deep in thought, and the following morning her quick laughter and incongruent stories did nothing to sate him. …
I have pair programmed on a daily basis for over two and a half years now, a year and a half of that being in the IBM Cloud Garage.
In this blog I would like to discuss some of the successes and failures of pair programming as part of an approach to software development, and the insights the approach has left me with.
To the uninitiated, pairing may seem a daunting prospect. I’ll go through some common lines of resistance:
“You mean I have to talk to people!? This isn’t what I signed up for…”
A very common assumption to make is that everyone who works in software is an introvert. Introverts generally find social situations draining, and require their own space to recuperate. Thus, as long as software is seen of as a solitary activity, introverts will be drawn to it. …