How I See Money Differently

Sam Dogen had another thought-provoking post over at Financial Samurai recently, this time looking at the very interesting difference between the way that Americans and Europeans in particular view money. I encourage you to read the entire thing: How Europeans See Money Differently From Americans. Most interesting out of this entire piece, though, and definitely the most impactful statement for me, was that of his conclusion: “Remember that money is only a means to an end. What is your end?"  

One-Way Ticket to Ride

Worth linking to again, courtesy of Dave Pell’s The Next Draft this time around on the forty-fifth anniversary of Apollo 11’s historic mission: the speech President Nixon plan to give in the event of a moon disaster. Incredible, and remarkable chilling:

“Fate has ordained that the men who went to the moon to explore in peace will stay on the moon to rest in peace."  

The 30 CSS Selectors You Must Memorize

I don’t do this often, but for all the help Tuts+ gave me as I worked to expand the functionality of this design over the past few weeks, I can’t let it slip by without note. When I build a site, I prefer to do everything humanely possible with CSS rather than outsourcing it to JavaScript. Due to this perhaps irrational desire, everything — including device detection — but the ability to enter dark mode and save that preference across multiple sessions is managed strictly using CSS. As I’m sure you web developers out there can understand, this led to some sticky situations in which I almost resorted to a quick and dirty script. Thanks to resources like this one though, I managed to keep my use of JavaScript down to a minimum, and continue to ship a speedy site for you all to read. Next time you import jQuery out of habit, think back to this and ask yourself, “Can I do this with CSS?" Because after seeing tutorials like this, I bet you can.  

Seemed So Sensible

Regardless of your own personal opinions regarding Christianity and religion in general, I think we can all get behind Sid’s overarching sentiment: it is important to remain true to yourself even when doing so means standing alone alongside an unpopular opinion. For in the end, with what will we find ourselves left? It is to these convictions we hold and must hold strongly that we will return; without them, we have nothing.

Stick to your guns. Be yourself. At the end of the day, I promise: you will be glad that you did.  

The Daily Show on Glassholes

Absolutely hilarious video, courtesy of John Gruber — with the choice line taken as an excerpt: “Magellan Was an Explorer. Chuck Yeager Was an Explorer. You Guys Have a Fucking Camera on Your Face.” I was rather bullish on the widespread reaction to Google Glass the other day when I wrote Thoughts on Glass, but I can still appreciate some great humor when I see it. Very well done.  

This Week in Podcasts

Yet another week has come and gone, and here at the end we once again find ourselves with a collection of fantastic podcasts; some new and only just published, while others now have one more chance at enamoring a pair of fresh ears. Some new, some old, and all equally excellent.  

Amazon's Whale Strategy

You cannot — ought not — judge the Fire phone by the traditional standards against which we have come to judge all devices these days, but rather from the perspective of a goods and services company that seeks to facilitate streamlined access to its storefront for its most loyal and devoted customers by offering them a device integrated with its own services to a degree made impossible through third-party integration alone on another device maker’s platform. When considered in this light, the Fire Phone is, inarguably, an interesting proposition that more than merits the considerable number of think-pieces that have been devoted to it since its announcement. This is the point Ben Thompson makes here, and makes so, so very well.  

The Future of Computing

In a style made popular by Benedict Evans in his hallmark Twitter postulations, posit: computers were created for writers. As such, the next iteration of computing devices will cater to the needs of others: creators and designers will have Jarvis-like artificial intelligence systems to converse with and holographic interfaces to involve their entire bodies in the creation process. The current model involves the two tools of the writer’s trade: their hands and their minds. Future implementations will go beyond those unnecessary restrictions that don’t apply in other fields in order to provide a richer, more productive computing experience.  

I'd Drive That

Every so often an article crosses my path wherein the author drools over a custom shop’s awesome modifications to an already awesome vehicle, and then I invariably spend a good long while extricating myself from the inevitable rabbit hole that ensues. As of this writing, nearly four months have passed since I have gone down that path, continuing my trend of leaving roughly three months between each of these articles. Today, I’m back for another round: thanks to the rediscovery of three monsters I squirreled away in my Instapaper queue a number of weeks ago, and only just recently rediscovered, I finally have cause to once again spend time appreciating these mechanical marvels at the intersection of industrial design and raw power.  

First Crack 1.0

Since starting this website nearly two years ago, I have written specifically about the engine that runs it exactly four times: in Introducing First Crack, I detailed my long journey to the realization that I needed to build something completely my own, from the ground up; later, I talked about some of my creation’s niceties in First Crack in Practice, before outlining the changes an innocuous redesign brought about in First Crack’s Complete Overhaul. Finally, some eleven months later, I returned to once again briefly run down my latest updates in Changes to First Crack. Since then, however, for the last six months, I have not said a peep. Today, that changes with the release of First Crack 1.0 to the public.  

Disrupting Disruption Theory

Very interesting take on the recent flare up around Disruption Theory, and how Lepore was not necessarily wrong to criticize Christenson and his theory, but that she did point to the wrong permutation of it: it is not necessarily the base theory that is flawed, but rather the watered-down version we find in use so often today. John Kirk then proceeded to delve further into the theory in a great follow up to Ben Thompson’s recent piece, Critiquing Disruption Theory.  

Critiquing Disruption Theory

I linked to this piece by Ben Thompson in the title only because it is his most recent on the topic of disruption theory; I strongly encourage you to start with his earlier piece from last year titled "What Clayton Christenson Got Wrong", where he more fully explains the theory and further expands upon some of its flaws. Especially if you — like me until now — only know of Disruption Theory in the abstract as explained in passing here and there, these two articles from Ben are a fantastic place to start.  

This Week in Podcasts

I am considering using a boilerplate for the introduction to this article, and keeping the actual noteworthy content the dynamic aspect going forward. So, let’s give it a try with last week’s opening: “Another week, another set of great podcasts for your listening pleasure. Enjoy.”  

Like a Pendulum

From the Woman Suffrage movement of the late nineteenth century to the early 1920s, to the Civil Rights movement during the ‘50s and ‘60s, American history in particular has suffered many bruises at the hands of remarkable injustices. Even going back further to the 1700s, at the dawn of the Revolutionary War, the Founding Fathers laid the foundation for this nation as the result of an affront they and their constituents considered intolerable. Since then, we as a people have proven unable to shake our masochistic obsession-bordering-on-fascination with this approach to social governance. Quite unfortunately, I might add, for despite a brief respite of fifty-odd years since the last major social movement, increasing civil unrest has brought us to the doorstep of yet another, albeit hopefully less violent, confrontation between social norms and its ever-changing landscape.  

Losing Apple

Yes; fantastic piece from Sid O’Neill. I myself have begun to wonder the same things lately, questioning how I became so pedantic and obsessed with things of such little real importance that I would wax on endlessly about a simple ad, of all things. Yet, unlike Sid, I have been able to suppress those uncomfortable questions until very recently. As time marches on, however, and the amount of time I devote to this hobby only grows, this is a very real reality that I must confront. And as for what I will ultimately answer? Time will only tell; were I forced to make a prediction now, though, I would wager I end up on the same side of this issue as Sid.  

Bitter Medicine

I never had a problem with the aesthetics of iOS 7, and continue to have no troubles whatsoever with it running atop my iPhone 4S: my phone never restarts, and my battery works just fine — especially for a device rapidly approaching its third birthday. Nevertheless, I can appreciate that many have had numerous and insurmountable problems in these areas as well as in many others, and that these issues have made iOS 7 a very difficult release with which to reckon their faith in Apple. And when framed in this light, I can understand why some would characterize their experience with iOS 7 as “bitter”. However, no significant, meaningful change comes without at least some modicum of pain: one does not become fit without straining at the gym, and becoming a big-time fancy-pants blogger takes more than one sleepless night along with a fair amount of effort. It’s important to keep in mind, then, the difference between necessary and unnecessary pain. This, I believe, was the former, and — at least for me — a relatively painless evolution at that.  

Precluding Success

Quite some time ago, I started this draft with a simple premise: precluding success is failure of at least one effort in a given area. Put differently, those who have yet to fail in their chosen profession can never attain greatness in that field. Along with this supposition, I included one more stipulation as an addendum to the previous statement: one can, however, substitute knowledge, to a degree, for failure. Regardless of the knowledge amassed relating to a particular skill set or field of study though, the best one can hope for is mediocrity without the essential, formative impact even one failure invariably brings with it. Thus, from these somewhat humble beginnings, I began to craft this article.  

This URL shortener situation is officially out of control

This situation really is crazy. Part of the problem, though, at least where Twitter is concerned, is that Twitter does not use the t.co shortener until after a tweet is posted, which means after it imposes the 140 character limit. Especially for me where every link to one of my own articles that I post starts with “zacjszewczyk.com/Structure”, this makes not using my own shortener — in this case, Bitly — completely impractical. Even then though, there is no real justification for even this many redirects, and especially not as many as Scott found here. Insane.  

More Articles