Most tech #books are frustratingly incapable of predicting the future, and 2006's #Code 2.0 is no exception. But it holds up better than many, and identifies four key #cyberspace themes still relevant today: #regulation - by states, and by code - competing #sovereignty, and latent ambiguity.
Next read is "Concrete Economics" by Stephen S. Cohen and J. Bradford DeLong.
First book from the #NewConsensus reading list.
I finished "The Power" by Naomi Alderman today.
I didn't enjoy the read, but it was thought provoking. The central thesis of the book seemed to be, "our society is based on power, and if women were stronger than men we would see the same oppressive dynamics we see now, reversed."
That's a grim thought.
Next book is The Entrepreneurial State, by Mariana Mazzucato.
I'm going to try not to overdo it with the social notes. It's a library book due back soon, and I'm not sure writing down everything helps me absorb the content.
Still, I'm excited to dive into another #NewConsensus book.
I didn't realize when i bought it that the book was written 2006, but I'm still pretty interested to read "Producing Open Source Software," by Karl Fogel.
I just joined an #opensource software company and I have a lot to learn.
Next read: I've got the audiobook of Margaret Atwood's "The Testaments". Figured I'd intersperse the heavy stuff with *some* fiction.
Just finished the Tombs of Atuan by #UrsulaKLeGuin. The whole thing, cover to cover, on #archiveorg. The Internet rules.
Next book is "City at World's End" by Edmond Hamilton, a 1950s #scifi book hosted on #Librivox.
Thus far, it's classic 1950s fare. A square-jawed team of white man scientists are flung into the far future along with their town. The local government is weak, the women are frail and must be protected.
For all that the premise is interesting - reminds me of "The Night Land" and "The City and the Stars" - post post post apocalypse cities surviving on doomed worlds.
Depending on where you are with understanding the problem and setting direction, you may need to:
• gather new information
• process what you’ve learned
• explore different approaches
• focus on a particular approach
"One of the hardest design problems I ever worked on was for a company that helps IT groups manage risk. Their product focused on open-source components—inexpensive and widely supported by an enormous community, but often vulnerable to security flaws."
Interesting. I thought that #opensource was generally more secure because of all the eyeballs. With notable exceptions, obviously.
@sean ah yeah, the famous Heartbleed.
"Beware the paradox of having too much data and still wanting more. Lots of data may build your confidence in these assertions, but it also leads to spending too much time analyzing the data—analysis paralysis. One of the fatal flaws in our business is that we seem to shortchange analysis, never giving ourselves the time or tools to make sense of what we learn."
#design #UserReaserch