News for hackers. Stuff that matters.

rbradford

Re:The Tamagotchi Cemetery on Monday April 26, 2021 @04:44AM (#26940557)
Wikipedia has the details: https://en.wikipedia.org/wiki/Game.com

"Accessing the Internet required the use of an Internet cartridge and a modem, neither of which were included with the console. Email messages could be read and sent on the Game.com using the Internet cartridge, and the Game.com supported text-only web browsing through Internet service providers. Email messages could not be saved to the Game.com's internal memory. In addition to a Game.com-branded 14.4 kbit/s modem, Tiger also offered an Internet service provider through Delphi that was made to work specifically with the Game.com."

Re:Ask HN: Show me your half baked project on Saturday January 09, 2021 @12:08PM (#25702112)
Sounds a bit like woof: https://github.com/simon-budig/woof

Two great things about woof:

1. You can use it as a verb, 2. Woof can woof itself.

Cue shouts in the office, "Hey, can somebody woof me woof?" Followed by a reply of an IP address and lots of puzzled onlookers.

> Do Uber drivers have to pay a license to have the radio on in the car?

In the UK, yes, https://pplprs.co.uk/wp-content/uploads/PRS-for-Music-Tariff...

My first experience of historical fiction was The Gallows Pole by Benjamin Myers. This recounts the story of the Cragg Vale Coiners who clipped coins and used those clippings to mint new coins. Rather than being driven by greed the clippers used the money to help feed the rest of their community. It's a really lovely book and gives a fantastic insight into the lives of the people of that period and area.

https://www.hive.co.uk/Product/Benjamin-Myers/The-Gallows-Po...

Re:Huginn: Create agents that monitor and act on your behalf on Thursday December 12, 2019 @02:28PM (#21775362)
There is a lovely two player board game called Odin's Ravens in which players acting as Muninn and Huginn race against each other by playing landscape cards. [1]

I wasn't aware of the full details of the lore so thank you for bringing that up!

[1] https://boardgamegeek.com/boardgame/192074/odins-ravens-seco...

I just finished "Clearing the Air" by Tim Smedley (https://royalsociety.org/grants-schemes-awards/book-prizes/s...) which was shortlisted for the Royal Society's prize for science books.

The first half of the book covers some of the chemistry of air pollution along with a review of the impact that this can have on health (particularly scary is the discovery that PM0.1 can be found in the blood and may be attributed to cardiovascular disease). Later chapters then talk about how air pollution has been addressed in different places and finally there is some guidance on what you can do reduce your exposure.

I discovered this book from one of the episodes of Inside Science featuring the shortlisted books: it's still up if you want to listen yourself: https://www.bbc.co.uk/programmes/m0008jf1

When my team was learning about Kubernetes we worked through Kelsey Hightower's "Kubernetes the Hard Way": https://github.com/kelseyhightower/kubernetes-the-hard-way

Obviously this much more complicated that using a tool such as kubeadm to deploy Kubernetes however it gives you a really good understanding of how a Kubernetes cluster is put together.

One of my colleagues used the experience from working through this with a set of VMs to create a tool called kubicle: https://ciao-project.github.io/kubicle.html

This allows you to build a Kubernetes cluster on your own physical machines by building it on top of a Ciao cluster if you're not able to use public cloud hosted VMs. For learning you can combine this with Ciao's "singlevm"/ccloudvm mode to run a cluster inside a VM (with nested VMs.)

Full disclosure: I currently work on the Ciao team @ Intel :-)

Re:Readme Driven Development on Monday August 23, 2010 @01:48PM (#1627427)
I recently used this approach to reinvigorate the development of an existing project that has flattened out. Writing out how stuff worked then gave indications of where we needed to improve our API and document our corner cases.

In the end the README didn't represent the status quo but instead became what we were aiming for. For the most part this succeeded, the main challenge I had was persuading my collaborator to actually review what i'd written.