The question isn’t who is going to let me;
~ Ayn Rand
It’s who is going to stop me.
slip:4a427.
Who will? →
Sally sells sea shells by the sea shore is simple compared to this →
The Chaos
Dearest creature in creation
Studying English pronunciation,
I will teach you in my verse
Sounds like corpse, corps, horse and worse.I will keep you, Susy, busy,
Make your head with heat grow dizzy;
Tear in eye, your dress you’ll tear;
Queer, fair seer, hear my prayer.Pray, console your loving poet,
~ Gerard Nolst Trenité (1870-1946) from, The Chaos – Wikipedia
Make my coat look new, dear, sew it!
Just compare heart, hear and heard,
Dies and diet, lord and word.
ɕ
Welcome to the surveillance state →
The Internet is a surveillance state. Whether we admit it to ourselves or not, and whether we like it or not, we’re being tracked all the time. Google tracks us, both on its pages and on other pages it has access to. Facebook does the same; it even tracks non-Facebook users. Apple tracks us on our iPhones and iPads. One reporter used a tool called Collusion to track who was tracking him; 105 companies tracked his Internet use during one 36-hour period.
~ Bruce Schneier from, Our Internet Surveillance State – Schneier on Security
slip:4usebo3.
…and he wrote that essay before the Snowden/NSA revelation showed us we’ve gone far beyond it being only an Internet surveillance state. We have collectively delivered ourselves into the power of ideas we do not know we have accepted.
ɕ
SOLID object-oriented design →
Five basic principles of object-oriented design. Not the only five, but five which are, well, SOLID.
Single responsibility – A class should have only a single responsibility.
Open/closed – Open for extension; Closed to modification.
Liskov substitution – Objects can be replaced by instances of their sub-types without breakage or surprise.
Interface segregation – Many, specific interfaces – that is, APIs – are better than fewer, more general-purpose interfaces. (…or “interface” in the worst case.)
Dependency inversion – Depend upon the abstraction. (Not upon the specific concretion.)
ɕ
Cherry tree →
…and then it snowed pink and nearly killed the lawn :*D
ɕ
Courage →
Courage is what it takes to stand up and speak; Courage is also what it takes to sit down and listen.
~ Winston Churchill
slip:4a1.
Training while exhausted →
Is training while you are exhausted beneficial?
…and do you know about the Martial Arts stack exchange?
ɕ
Star Wars machete order →
Should you watch the Star Wars movies in numerical order, or released order? Neither – Use machete order: IV, V, II, III, VI
The Star Wars Saga: Introducing Machete Order » Rod Hilton
There are two obvious options for watching the Star Wars saga.
- Release Order – Watch the films in the order they came out, recreating your experience with the films for someone new to them.
- Episode Order – Watch the films in the order George Lucas intends, starting with Episode I and going straight through to Episode VI
There are two critical flaws with both of these orders, unfortunately, that prevent either from being appropriate.
~ Rod Hilton from, The Star Wars Saga: Introducing Machete Order
slip:4unote1.
Turns out both of those options suck.
Numerical order, (as Lucas’ suggests,) wrecks the greatest movie reveal in history by spending 3 movies explaining it. And release order is also no good because… well… go. read. machete. order.
Seriously. I can’t do Rod’s article justice without quoting the whole thing.
ɕ
Flag day →
ɕ
It is done fast enough when it is done well. →
Getting done right does not mean getting done slow. Getting done right means getting done fast. You will go faster if you do things right. You will go faster if you come down off the “high” generated by the illusion that effort is speed. You will go faster if you calm down, follow your disciplines, and refuse to rush.
~ Bob Martin from, «http://blog.8thlight.com/uncle-bob/2013/03/11/TheFrenziedPanicOfRushing.html»
While he’s talking about software development in general, and test-driven development specifically, this is true for – I think – everything. My experience is that this is true for software development, and other technical work. But it is also true of martial arts practice, parkour, games, building model airplanes… you name it.
The pervasive admonishment should be “do it well,” rather than, “slow down.” Do it well and you’ve – by definition – done it as fast as possible. What’s the point of doing it poorly? What’s the point of rushing to completion; If you didn’t do it well, then it’s not done.
ɕ