JB

Link

Restating, underscoring, or even strengthening those scientific results won’t solve that problem. The results already come from multiple fields, are reinforced by multiple lines of evidence, and have been vetted (extremely vetted, you might say) by several extended, multi-layered review processes. Collectively, we don’t know how to “know” anything more confidently than we know this stuff.

If someone chooses to simply reject those scientific institutions, procedures, and results, then piling on more facts is beside the point. It’s not about facts any more, it’s about the authority of the institutions.

I understand why politicians who get their funding from oil companies want to discredit global warming and research into climate change, what I don’t understand is why that willingness to disregard established facts trickles down to everyday republicans.

I’m starting to think that this has more to do with tribalism than actual beliefs. The right-wing tribe believes this set of ideas, given to them by their elected leaders, and nothing will change their mind about that.

Given that we can now safely refute any scientific research (biased), well reported news story (fake news), and even disregard things we’ve seen and heard ourselves (he didn’t really mean that), we have entered a dangerous era where a major section of the population has decided to make up their own reality.

How can we have a meaningful conversation when your loyalty to your tribe means more than facts, reason, or logic?

Link

You will never get any more out of life than you expect

Keep your mind on the things you want and off those you don’t

Things live by moving and gain strength as they go

Be a calm beholder of what is happening around you

Looks like I’ve got a new podcast to check out.

Because the truth of the matter is that, however you go about it, you do need to build your capacity for hard, focused work. That is vital in an age of complexity, where we need to carve out a niche. Most of us aren’t making widgets anymore, and much of that work is being replaced by machines anyways.

Link

I’m not sure if I’m ready to drop $80 on his course quite yet ¹, but I completely agree with what he’s saying here. The ability to concentrate on difficult problems for an extended period of time is only going to become more valuable. Far too many people spend every spare second they have looking at their phone, literally falling down stairs so they don’t miss the latest snapchat alert.

tldr: If you have a Circle device and an Eero mesh network, plug the Circle into the Eero connected to your modem with an ethernet cable.

The router I bought last year just wasn’t cutting it anymore. Several times a day I’d have to turn off wifi and turn it back on again on my Mac, and I’d rarely see speeds over 12 Mbps, even though I’m paying for 100 Mbps from Mediacom. Part of it had to do with the placement of my desk relative to where the router sits, and part of it has to do with running my Mac in clamshell mode through most of the day. Whatever the reason, I was tired of it and splurged for a set of three Eero routers. Now I have one in the basement next to the modem, one in the office, and one in the kitchen, and I consistently get speeds around 70-80 Mbps from fast.com.

I was quite happy with my setup, until random devices on my home network suddenly stopped connecting to the Internet. First it was the Apple TV, then the Fire TV, then my daughters laptop, then my other daughters iPhone, then my iPhone, and when it got to my wife’s iPhone something had to change. Of course, I knew the culprit had to be our Circle from Disney.

The Circle is a little white box that sits on the network on controls access. It blocks content that we’d rather not have, and sets time limits, bed times, and reward systems for the kids. We have all the devices assigned to their owners and what we think are reasonable rules setup. For some reason when we hooked up the new routers I thought it’d be a good idea to move the circle out into the office; I guess I wanted to be able to see it. I sat the Circle next to the office Eero and assumed everything would be fine. It was not.

As I understand it, the Eero works by creating a subnetwork underneath your home network that is dedicated to the routers staying in contact with each other. Eero calls the software that manages the the system “TrueMesh™”, and it lets a device float between routers in the house without slowing down network speeds. The Circle works by using a technique called “ARP poisoning”, where the Circle becomes the default gateway on the network, allowing it to manage the traffic.

So, my theory is that when I set the Circle next to one of the satellite Eero routers, the Circle connected to the closest router and spoofed the default routers ARP address, which caused the router to not be able to communicate with the real default router, breaking the mesh network. Moving the Circle back to the basement and physically connecting¹ it to the primary router solved the problem.

I should mention that the Eero also has parental controls similar to Circle’s built in. I haven’t fully explored them yet, but from what I can tell they don’t quite have the feature set of the Circle. Future software updates might change that, I’ll be keeping an eye on it.

Overall I’m quite happy with both the Eero and the Circle. While expensive, the combination of the two gives me a fast, robust home network with detailed controls over who and what connects, what they have access to, and for how long. ²

It kind of feels like our lives are made up of a countless number of weeks. But there they are—fully countable—staring you in the face.

…

Sometimes life seems really short, and other times it seems impossibly long. But this chart helps to emphasize that it’s most certainly finite. Those are your weeks and they’re all you’ve got.

Link

Reminds me of Robin Williams in Dead Poets Society. “That the powerful play goes on, and you get to contribute a verse. What will your verse be?”

In Nineteen Ninety-One, I was a freshman in high school, living in a tiny house in small town Montana. Just me and my mom. My family, like so many at the time, had fallen apart. We had moved around a lot, I felt odd and out of place. I was angry, full of teenage angst, and generally pissed off at the world for the hand it dealt me.

Somehow I had talked my mom into letting me have a TV in my room, and I used to stay up late at night to watch MTV broadcast the videos they deemed too weird for the standard days fare. It was one of those nights I saw and heard something new, something fresh and raw,Nirvana’s Smells Like Teen Spirit. It blew me away. Apparently I wasn’t the only one either, because soon after I first saw it the rest of the world discovered Nirvana as well.

It’s hard to overstate the impact Nirvana had. They really were something different, at least to me. A melding of punk and pure rock-n-roll, three guys in a garage belting their rage into the abyss. To me, the kid that I was, Nirvana was the complete opposite of the popular butt-rock of the time. I mean seriously, look at these guys.

I remember offroading in the backwoods of Montana, my friend driving way too fast in his S10 pickup, playing Lithium as loud as it would go, and the both of us howling with delight as we launched the pickup over another hill.

Nirvana led me to Pearl Jam, Soundgarden, Screaming Trees, Smashing Pumpkins, Blind Melon and so many more. They opened up the world of music to me by channeling what they felt through what they created, and I got it, because I felt that way too. Of course the lyrics of Smells Like Teen Spirit didn’t make any sense, but they didn’t have to, the world we were awakening to didn’t make any sense either. All we could to do was rage, rage, rage.

But not all the time. There were times of reflective introspection, easy, hopeful times of mindless joy, quiet times with the best of friends. A few years later, after the candle had burned so brightly, the light was put out.

Nirvana spoke to me in a way that nothing else did at the time. Nowadays I never listen to grunge, I mostly prefer jazz and classical. I also can’t say that the bands message is something I believe in now. I’ve moved on.

I’ve been thinking more about my defense of the Mac as a long-term computing platform, and I’m slowly coming around to understanding that at the base of my ideas is a type of willful ignorance that I should know better than to indulge in. The world is changing, computers are changing, and how we work and interact with them is changing drastically. To get to the root of this, let’s follow the five “whys” of why I need a Mac to work.

I need a Mac to get my work done. Why?

Because the Mac is a Unix based computer that includes the standard set of tools I use day to day, and it’s solid and reliable enough for me to depend on to work well when I need it.

Why do I need a Unix computer to work?

Because I’m a devops engineer, or automation engineer, or advanced sysadmin, whatever you’d care to call this job at the moment. I work primarily with AWS, and the best tools for building the automation systems for deploying our applications use the command line. Not to mention I often need to ssh into a server to troubleshoot it.

Why does the AWS environment use the command line?

Well, technically the command line is just one of the tools available, the awscli tools talk back to the AWS API, and AWS has SDKs available for popular languages. I could, and often do, write python code to accomplish what I need done. I suppose the real answer to this question is that there is currently no better interface for doing what I do.

Why is there no better interface for doing what you need to do?

Because designing human interfaces that make sense is difficult, especially with complex concepts. We need to be able to express logically that one bit of code needs to pull data from another bit of code which is pulling data from a database, all the while ensuring that the customer is getting the information they need quickly and easily.

Why are the systems you work with so complicated?

That’s a good question. Maybe they don’t need to be, or maybe in the near future they won’t be anymore. My work involves manipulating data, building websites that allow people access to upload and download data, and ensuring that the infrastructure these systems run on remains fast and available. How much of this is now being built into platforms like AWS, Azure, and Google Cloud Platform? How much of what I do each day could soon be accomplished by machine learning?

What if you could ask your phone to generate a graph of Apple’s annual profit and loss, and be sure that the visuals it returned were accurate and reliable? What if I could tell an iPad to build a highly available, auto-scaling infrastructure for hosting the Python code in my git repository, and the iPad would just go out and build everything I needed? How far are we from AI being able to tell from looking at a git repo the details of the infrastructure it needs? In that scenario, what use is “devops” when the engineer is AWS? For that matter, how far away are we from telling the computer the logic of what we need and having it develop the code for us?

Possibly not far. A recent article in Wiredexplores this very possibility:

Traditional coding won’t disappear completely—indeed, O’Reilly predicts that we’ll still need coders for a long time yet—but there will likely be less of it, and it will become a meta skill, a way of creating what Oren Etzioni, CEO of the Allen Institute for Artificial Intelligence, calls the “scaffolding” within which machine learning can operate.

That scaffolding is where I’ve been aiming my career for quite a while now, but, it may not be enough.

In the long run, Thrun says, machine learning will have a democratizing influence. In the same way that you don’t need to know HTML to build a website these days, you eventually won’t need a PhD to tap into the insane power of deep learning. Programming won’t be the sole domain of trained coders who have learned a series of arcane languages. It’ll be accessible to anyone who has ever taught a dog to roll over. “For me, it’s the coolest thing ever in programming,” Thrun says, “because now anyone can program.”

Basic economics says that scarcity creates value, in a world where anyone can program the skill currently required would be drastically devalued. This predicts a move from “infrastructure as code” to “infrastructure as algorithmically determined”.

I need a Mac for what I do now, but if current trends continue I might not need a Mac for much longer to do my job. In fact, as the tech industry continues to evolve, it’s entirely possible that it will evolve to the point where it no longer needs me. When that happens, maybe I’ll finally open up that coffee shop I’ve been dreaming about for decades.

Link

Sal Soghoian, writing for MacStories:

Here’s a thought experiment. Let’s imagine that Apple decided to combine their engineering resources to form app teams that delivered both iOS and macOS versions of applications.

In such a scenario it may seem logical to retain application features common to both platforms and to remove those that were perceived to require extra resources. Certainly Automation would be something examined in that regard, and the idea might be posited that: “App Extensions are equivalent to, or could be a replacement for, User Automation in macOS.” And by User Automation, I’m referring to Apple Event scripting, Automator, Services, the UNIX command line utilities, etc.

I’ve said many times that one of the main reasons I came to OS X is the underlying Unix utilities. I literally can’t do my job without the command line. It’s always in my dock, it’s always open, and I’ve got it customized just the way I like it. There is no replacement for the terminal, and no App Extension can provide a way for me to string together the tools I use to get done what needs to get done.

In such a world like Sal is imagining, I would have to find an SSH app like Prompt and setup my entire development environment on a Linux server somewhere. While possible, it’s not economical and it’s certainly not how I’ve become accustomed to working. I don’t think I’m alone in this either, anyone who does web development relies on command line versions of Python, Ruby, PHP, or Perl, along with a host of other small utilities to do things like syntax checking or unit tests.

I think it’s possible that Apple could remove the Terminal from OS X, along with the Unix utilities, similar to what they’ve done with iOS, but I don’t think they will. Apple uses OS X to develop their own software, so they know what the developers need to be efficient and productive. However I could see a world where you had to install Xcode and enable “developer mode” to get to the Unix utilities. We may not be far away from a day when OS X no longer ships with Terminal.app, but I think we’ll always have a way to install it when there’s real work that needs done.

I think Apple may be heading in the wrong direction, and it’s sad to see Sal be let go, but I’m glad to see him carrying on fighting for the users.

Despite aspirations of expanding my fields of interest and adopting new hobbies outside of technology, my day-to-day work gets done on a Mac. I’ve got a vested interest in the Macs continued survival, I’m one of those “truck drivers” that uses their machine for all it’s worth, and would have a difficult time transitioning to anything else. In my job I need to run shell scripts and build Docker containers, I need to ssh to Linux servers and RDP into Windows instances. I need to write, edit, and run Python code that connects to a database through a ssh tunnel. I need to do things that are either difficult or simply impossible with iOS, but are dead simple¹ with a Mac.

That’s why I switched to a Mac in the first place, someone had finally put a useable interface on top of a solid Unix core. The Mac community, especially the third-party developers, is why I stay on the Mac. I could get my work done on Linux, but my Lord, why would I want to? My degree is in human-computer interaction, I’d spend half my time ranting about the thousands of paper cuts in the user interface until I abandoned the GUI and ran everything from the command line, or a stripped down paneling interface. I’ve been there before. The Mac is a comfortable work environment that doesn’t skimp on capability like iOS does. Look deep enough into any of the iOS only workflows and nearly all of them are relying on outside computing devices of some type to get around what iOS can’t do.

But today we are once again hearing the death knell being rung for the Mac. This time it’s not because of an outside source taking over, but Apple itself who might simply decide that the Mac isn’t worth keeping around anymore. This is despite it being a profitable business, and being the sole source of development for iOS apps, and despite it being an industry leader in features and design, the tech media have decided that Apple is only a breath away from blowing out the Mac candle forever.

Well, we’ve been here before, right? It was before my time as an Apple user, but it’s my understanding that in the late ‘90s you couldn’t swing a dead cat without hitting on an industry “think piece” about the death of the Mac. Yet, here we are at the dawn of 2017 and the Mac is still here.

That’s not to say that it isn’t entirely possible that Apple might kill off the Mac Pro, or the Mac Mini. I wouldn’t be too surprised if neither of those products existed by the end of the year. But a new macOS-running computer of some sort is something I expect to be able to buy for the next three years, at least.²

Assuming the current Mac I’m typing this on lasts for the next three years, which it should unless I break it somehow, my next Mac should last for another estimated three to five years. Let’s just say I draw this out as far as I can and say five, that means I’ve got at least eight years of Mac use easily planned for the future. Which of us can look that far into the future and see what the computing industry or our lives will look like by then? Perhaps the iPad and iOS will finally have matured enough to make Macs truly obsolete, or perhaps my work requirements will have changed sufficiently to make adopting iOS full-time relatively painless. Who knows?

The point is, all this handwringing over the future of the Mac is overblown. We have years of macOS ahead of us. Apple is selling some fantastic Macs right now³, and I expect they will continue to do so for the foreseeable future. Until iOS actually is better than the Mac, there’s no reason to think that any of us will have to adopt our toolset to another platform. The Mac is here, has been here, and from what I can see, will continue to be here for many years to come.

Part of what’s been great about using Apple products is the feeling of living just a little bit in the future. The Mac, iPod, iPhone, and iPad paved a way towards a far less complicated future, where technology was seamlessly integrated into our lives, and enhanced our day to day interactions with our work and with each other. Apple, better than anyone, understands that technology is at it’s best when it’s nearly invisible. But, living in the future comes at a price, namely a sacrifice of stability and accepted norms of what works.

Yesterday we were driving to see family who lives three hours away. About a half hour into the trip I got a Skype message from a friend asking for some technical help. After he explained the problem I knew how to fix his issue, but I needed to SSH into a server to do it. Unfortunately, I left my Mac at home, and had nothing but my iPhone. Undaunted¹, I setup a VPN and downloaded Prompt by Panic. This is where I ran into a problem. To SSH into the server I needed to get my private key². Prompt would use the key if I could get it copied into my clipboard, but getting it there turned out to be more of a hurdle than I could overcome.

I tried to get the key from BackBlaze, but the iOS client wouldn’t let me view the text of the key or to export it with a share sheet, it only told me the type of file it was, which was no help. I also thought that I might have a copy of the key³ in a zip file in my Archive folder under my Documents folder, and I recently turned on iCloud sync for my entire Desktop and Documents folders, so I thought I should have been able to get to the key from there. In what was probably the most frustrating technical failure of the night, the iCloud app refused to download any file, and any other app I had installed that also had access to iCloud also refused to download files or would simply freeze up and crash.

The point of moving documents into the cloud was to have them when I needed them, but when I did need them the system failed. To add insult to injury, when I wanted to look up something frivolous this morning the app worked fine. I’ve since turned that feature off. If I can’t rely on it, it’s not worth it having it turned on. I wanted to live in the future where I never had to think about having access to my data, where it’s just always there when I need it, but in this case, the future simply isn’t ready quite yet.

This fiasco caused me to think a bit more about what has and has not worked in technology in 2016. A lot of virtual ink has been spilled about virtual reality and self-driving cars, but neither of them are quite ready for the real world yet, not that I’ve seen anyway. Social media has allowed trolls to run rampant, sucked our attention reserves dry, and helped elect the single most unqualified president in history to the highest office in the land. Twitter and Facebook have had great years in the past, but 2016 was not one of them. I’ve withdrawn almost completely from both of them, but I’m looking forward to Manton finally unveiling micro.blog. Yahoo announced that they let over a billion accounts get hacked, the DNC got hacked, and the Internet of Things got hacked. Overall, not a good year for online security either. A great year to be a 1Password customer though.

2016 was a not-too-subtle reminder to be critical of the organizations and devices which play a role in our lives. A reminder that trust is easily lost and not easily regained. That the promises people make are not always the ones they keep.

So, what has worked? On a personal level, while I’ve been critical of my need for the application in the past, my experience with DEVONthink and DEVONthink to Go has always been exactly what the developers said it would be. I’ve never lost data, the new sync works reliably and securely, and the company continues to be active and responsive with their customers. I’ve left DEVONthink in the past, 2017 is the year I commit to it wholeheartedly.

My Mac, iPhone, and Apple TV continue to work well. I almost never have an issue with any device. The one issue I had with my iPhone was recognized by Apple as being widespread and they fixed it for me at no cost. My particular recipe for apps on my Mac continues to work well, although I removed Byword shortly after writing it to consolidate all writing in Ulysses. Speaking of which, Ulysses deserves a special mention as being rock solid, beautiful, and reliable. It’s my favorite writing application, probably ever. Likewise, Day One continues to be fantastic, and receives my highest recommendation for consistent, intentional journalling. There’s more that’s worked over the past year, things silently working along in the background, but these are the things that stand out to me.

I work in the technology industry. I’ve spent sixteen years (so far) studying where and how it fails, what works, what doesn’t, and how to get the most out of our investment. This year my optimism took a hit, and more things than I expected failed. In 2017, I’m looking forward to finding new ways for this tech to not only become more invisible, but more trustworthy as well. 2017 is not just about personal benefit, it’s about security and social conscience as well. It’s about choosing technology that works best for yourself, and for everyone involved. I’m looking forward to exploring exactly what that means as we sail into the uncharted waters of a new year.