I wrote an article on passwords, passphrases, entropy, and data breaches for my employer’s blog: https://augustschell.com/passwords-passphrases-complexity-length-crackability-memorability-data-breaches
Recently on one of the podcasts I listen to, I heard an offhanded comment made about how history is taught not in patterns but as facts. For example, “On the 18th of April in ’75, hardly a man is now alive, who remembers that famous day and year”.
Rarely are the “whys” explained – understandably so at early ages, but not understandably as maturation happens.
“Teaching” in so many subjects has become memorization of what really amount to key-value pairs. Like, Columbus: 1492. Norman invasion: 1066. Etc.
Certainly, facts are important. And some things truly are best learned in a rote memorization form – for example, the multiplication table through 12, 15, or 25. But what about states and their capitals? Sure, they’re “pairs” – but are they more?
This is awesome if you’re a trivia nut. But if you’re not, or you truly want to learn the material – not merely pass a test or regurgitate facts – then you need to understand more than just the “facts”.
Outside history classes, it’s especially prevalent in math – very little (if any) time is taken to explain why the quadratic formula works (or even what it is), instead algebra students are expected to just learn and use it.
My late aunt, who did a lot of tutoring in her life, summed-up the problem with algebra (and other math subjects past elementary school) thusly: before algebra, we give a problem like “3 plus box is 9; what goes in the box?” but in algebra, we swap the box for a t or x or g, and we freak out. She would teach the facts, but [almost] never without the whys.
We definitely need more good teachers who want their students to understand not merely enough to pass the class (or the test), but to cultivate the curiosity we’re all born with to become lifelong learners.
First step: stop “teaching” as key-value pairs.
What is EtherPad? It’s an open-source collaborative text editor that works like Google Docs – ie, all editors/viewers can see changes from everyone else in realtime.
- acquire a CentOS server – I used Digital Ocean
- make sure you have enough swap space (if you use the smallest Digital Ocean “droplet”, you really need to give yourself 2-4G swap)
- dd if=/dev/zero of=/swapfile bs=8192 count=524288
- mkswap swapfile
- swapon swapfile
- add this line to the end of your /etc/fstab:
- /swapfile swap swap defaults 0 0
- run the following as root:
- yum -y install gzip git-core curl python openssl-devel && yum groupinstall
- yum -y install screen gcc gcc-c++ make wget curl
- note – it’s not always called “gcc-c++”; make sure you use the correct package name for your platform
- you can find out the correct package name by doing a `yum provides */g++` search
- yum -y upgrade
- bring everything up to date – it’s equivalent to `yum -y update –obsoletes`
- adduser etherpad
- su – etherpad
- git clone git://github.com/ry/node.git
- cd node && ./configure && make && make install
- git clone git://github.com/ether/etherpad-lite.git
- cd etherpad-lite
- screen bin/run.sh
- load http://127.0.0.1:9001 in your browser (substitute the IP/DNS name of your server as appropriate – mine was http://184.108.40.206:9001)
- for maintenance purposes, you should also do a `git pull origin` for EtherPad periodically
Some notes on the above:
- if you already have swap space and/or don’t want to worry about it (though I recommend you do), you can skip it
- I’ve put the `-y` option after every `yum` call presuming you really mean to run it, and you don’t care about dependencies
- if you aren’t using a fresh server (EtherPad certainly doesn’t require it’s own), you may want to be a little more cautious about the `yum` commands 🙂
- you should create a start-up script to ensure EtherPad is running if you need to reboot
- the EtherPad docs have all kinds of further things you can do – this is just a “get it going and start using it” tutorial 🙂
While I am not really in a position to do many of the mini projects given in the book (wrong type of house plus we rent), reading some of the project ideas did give me some inspiration for other activities. One of those is a Buffer-like tool I’m now writing to queue tweets over-and-above what the free level of Buffer will allow (and on a different schedule from my Buffer-fed queue). In conjunction with python-twitter, cron, and simple email messages, I’ve got a system started to which I can email things I would like to be posted, and they will go out when the cron job runs.
The Arduino is an impressive embedded platform – one that has also rekindled another long-time interest I’ve had in robotics. Years back, I recall seeing Sally Struthers advertising for one of those learn-at-home groups, and one of the options was robotics. (By “years back”, I mean 20+ years ago – probably more like 25 years ago, at this point.) I used to own a copy of Robot Builder’s Bonanza – and read it cover-to-cover a couple times. I loved watching Battlebots on TV. I’ve always wanted to buy/use LEGO Mindstorms.
Using robots to automate daily activities (and, of course, for fun) has been a fascination since I first saw Lost In Space and myriad other scifi shows and movies.
Riley does a great job of not demanding you be an expert programmer (or even a programmer at all) with the fully-implemented code examples in the book. He also does a good job of indicating what you’ll likely have to tweak on your own – and what you can probably just leave alone in the examples. Add to this the “extra credit challenges”, and I highly recommend it to anyone interested in home automation, embedded development, robotics, or just general programming/scripting.
There are some other interesting Python snippets throughout the book – that don’t have to be used in the context of an Arduino (like using Google’s SMTP server (via authentication)).
I first came across Why Nations Fail at my local Half Price Books. After seeing it on the shelves a couple times, but still being unsure about whether I really wanted to read it or not, I reserved it at my local library.
Now I wish I had bought it (and likely will) – Daron Acemoglu & James A Robinson, while sometimes slipping into an academic, journalistic tone, present a fantastic historical, economic, cultural, and international view into the similarities, and differences, of “national” failures around the world over the last several centuries.
They spend a great deal of time expounding on the differences of countries that succeed and those that don’t – and offer insights into how failing nations could, potentially, turn themselves around.
Interestingly, the factors that play-into national success and failure are similar throughout history – critical junctures, inclusive/pluralistic political and economic environments vs extractive/exclusive political and economic structures, empowered citizenries, overbearing rulers, literacy, economic incentives (positive and negative), etc.
The Iron Law of Oligarchy:
the overthrow of a regime presiding over extractive institutions heralds the arrival of a new set of masters to exploit the same set of pernicious extractive institutions (p366)
My recommendation? Buy it. Read it. Share it. The background and conclusions this book presents and reaches should be required reading for anyone who wants to see their nation “do better” – politicians, businessmen, citizens, NGOs: all would benefit from applying what is demonstrated in this excellent work.
- Quality of writing: 4/5
- Quality of content: 4.5/5
- Historicity: 5/5
- Educational value 4.5/5
- Overall: 4.5/5
I recently found The Seven Stages of Expertise in Software Engineering.
- Stage 1: Innocent
- barely knowledgeable if at all
- Stage 2: Exposed
- seeking knowledge
- Stage 3: Apprentice
- has read case studies and tries to apply those techniques
- Stage 4: Practitioner
- can actually apply concepts learned in one context to a not-identical context
- Stage 5: Journeyman
- professional understanding and application of the field; can mentor
- Stage 6: Master
- moved from “whats” and “hows” to “whys”; can mentor very effectively
- Stage 7: Researcher
- the teacher, presenter, mentor, speaker, evangelist, writer, authority
Presented firstly in the humorous guise of The Seven Stages of Expertise in Bear Hunting, Meilir Page-Jones makes a highly-compelling case for progressive advancement in [nearly] any field.
Some of the ideas seem similar to what Malcolm Gladwell brings in Outliers (review) or Robert Greene does in Mastery (review). Which seems to only lend more credence to those other works, given that this article is © 1998.
[W]hen you choose a language, you’re also choosing a community. The programmers you’ll be able to hire to work on a Java project won’t be as smart as the ones you could get to work on a project written in Python. And the quality of your hackers probably matters more than the language you choose. Though, frankly, the fact that good hackers prefer Python to Java should tell you something about the relative merits of those languages.
He had a follow-up the next month to expand a little on that thought:
[Y]ou could get smarter programmers to work on a Python project than you could to work on a Java project.
I didn’t mean by this that Java programmers are dumb. I meant that Python programmers are smart. It’s a lot of work to learn a new programming language. And people don’t learn Python because it will get them a job; they learn it because they genuinely like to program and aren’t satisfied with the languages they already know.
Which makes them exactly the kind of programmers companies should want to hire.
I wonder – what is the “new” Python? If Python was what the Cool Kids™ were picking up for fun a decade ago, what is it today? R? Ruby? Or something that isn’t as well known? Ruby is two years newer than Python, but seems to have only become truly popular with the advent of Ruby-on-Rails. R may be too focused (it being designed for statistics programming), though it is also 20 years old now.
If you were a hiring manager, what would strike you as “motivated” or “must be smart” in terms of language(s) on resume?