Criticism-as-a service: for a fixed fee our team of self-proclaimed experts will criticise your idea/startup/blog post.
— Marc Gear (@marcgear) November 23, 2015
It’s been a few month since I reviewed my podcast subscriptions. Driving over 150 kilometers every working day gives me plenty of time to readjust my tastes and preferences. Just doesn’t leave me too much time to actually do something about it.
Podcasts are easy to subscribe to. Once you find the ones you like. Finding the ones you like takes forever though. Here’s where WP Tavern’s post “Awesome Geek Podcasts: A Curated List of Tech Podcasts” comes in handy. Cause it provides not one, but two lists of podcasts:
And while I’m familiar with many on that list, there’s a tonne of those that I haven’t heard, or heard about.
Any other recommendations?
It’s after bits like this one, I think I should spend more time reading documentation:
Create a new transaction.
This routine should _never_ be called by anything other than RT::Ticket. It should not be called from client code. Ever. Not ever. If you do this, we will hunt you down and break your kneecaps. Then the unpleasant stuff will start.
TODO: Document what gets passed to this
p2pvc – a point to point color terminal video chat. Why? Because we can! Pure geekery …
Over the last six years, I’ve become better at using Git for version control. But my conceptions of the index, the working copy, the object graph and remotes have just grown fuzzier.
Sometimes, I can only understand something by implementing it. So, I wrote Gitlet, my own version of Git. I pored over tutorials. I read articles about internals. I tried to understand how API commands work by reading the docs, then gave up and ran hundreds of experiments on repositories and rummaged throught the
.gitdirectory to figure out the results.
I discovered that, if approached from the inside out, Git is easy to understand. It is the product of simple ideas that, when combined, produce something very deep and beautiful.
Spoken like a true hacker. My hat is off to you, sir.
quine-relay – an uroboros program with 80+ programming languages.
If you didn’t get it, here’s a better description:
This is a Ruby program that generates Scala program that generates Scheme program that generates …(through 80 languages in total)… REXX program that generates the original Ruby code again.
Insanity at its best!
P.S.: Quine (computing) Wikipedia page comes handy:
A quine is a non-empty computer program which takes no input and produces a copy of its own source code as its only output. The standard terms for these programs in the computability theory and computer science literature are “self-replicating programs”, “self-reproducing programs”, and “self-copying programs”.
cool old term – terminal emulator which mimics the old cathode display
You haven’t missed much! :)
Bootstrap/386 – a Twitter bootstrap theme to make webpages look like they are from the 1980s.