Category Archives: Snippets

“Recess” and “Good Bones”, or selling the world to my children

There’s more beauty in this world than you can guess

Recently, with the help of someone on Micro.blog and Apple Music, I have turned my family on to the music of Justin Roberts. His band plays children’s music in a power pop style. His music is really catchy, and his lyrics are wry, funny, very kid-friendly (my daughter sings them all the time), and sometimes also play to the parents on emotional level as well.

My favorite Justin Roberts song, by far, is “Recess”. Like the best power pop songs, this song has more hooks and ideas in it than most albums do. The lyrics are cleverly and consistently written from the point of view of a bored kid stuck in a classroom, waiting for the recess bell to ring:

Can’t you hear the blacktop callin’?
Classroom clock is stuck or stallin’
There is nothing that will pass the test
Unless it’s recess

In the second and third pre-chorus endings, the lyrics expand out beyond the tedium of the elementary school classroom to the wonder of the outside world:

One more dotted I
One more crossed T
Then we’ll be runnin’ free
There is more beauty in this world than you can guess

That last line resonates powerfully with me. Seeing the beauty in this world is something children do naturally. I think we forget how to, as we get older, and our knowledge of history and current events expands, and our experience of life evolves from dreaming of what our lives might be to actually living them day-to-day. Our dreams get smaller and more finite as time passes. As we get older still, we relearn to see the beauty, in a different way—with a wonder that is tinged with sadness. As an adult, I see that the splendor and joy of the world is counterbalanced by its disappointments and horrors.

The world is at least fifty percent terrible, and that’s a conservative estimate, though I keep this from my children

The line “There is more beauty in this world than you can guess” always makes me think of the contrasting sentiment expressed in the poem “Good Bones” by Maggie Smith:

Good Bones
BY MAGGIE SMITH

Life is short, though I keep this from my children.
Life is short, and I’ve shortened mine
in a thousand delicious, ill-advised ways,
a thousand deliciously ill-advised ways
I’ll keep from my children. The world is at least
fifty percent terrible, and that’s a conservative
estimate, though I keep this from my children.
For every bird there is a stone thrown at a bird.
For every loved child, a child broken, bagged,
sunk in a lake. Life is short and the world
is at least half terrible, and for every kind
stranger, there is one who would break you,
though I keep this from my children. I am trying
to sell them the world. Any decent realtor,
walking you through a real shithole, chirps on
about good bones: This place could be beautiful,
right? You could make this place beautiful.

This is a profoundly powerful poem that I read in college and have never forgotten. As an adult and a parent, I return to it often. It has always made me feel, in some way, like a teenager who concludes, upon first entering the adult world, that I have been sold a bill of goods: nothing is as nice or easy or fair as my parents and mentors (and, let’s face it, TV and movies) told me it would be. This poem distills all the disappointment and disillusionment that experience and maturity bring into seventeen simple and somewhat humorous lines. I love how it ends on a note that is somehow both cynical and hopeful: “You could make this place beautiful.”

Selling the world to my children

It’s my job, as a parent, to sell the world to my children. I want to tell them the good—now, while they are young—and the bad—later, when they are older. In both times, now and later, I have to remember that Justin Roberts and Maggie Smith are both right about the world. It contains all the beauty that has any meaning. It also contains all the horrors that have ever befell anyone. The most important thing I have to teach my children is that they can make it better—they just have to try, even after the veil of childhood innocence has fallen, and they see the world for what it really is.

The calm before the WWDC storm

WWDC is in a little more than two weeks. As a hobbyist developer, I don’t go to big, expensive conferences 3,000 miles from my home. But I do eagerly await it each year. Last year I was so excited about it that I went as far as calling it “nerd Christmas”. This year, though, I’m not looking forward to the keynote, the new APIs, the betas, and so on.

There have been no substantive leaks about what will be announced, and no one’s predictions so far have been that compelling. That’s in stark contrast to last year, when I practically knew what iOS 11 would bring to the iPad, based on rumors and speculation. This year, the most exciting leak we got is that a cross-platform macOS/iOS development framework will not be announced this year.

As a user and a fan, I basically want Apple to announce a rebuilding year. iOS 12 should be a maintenance release. They can make their software faster and more stable. They can make Siri a lot better. They can fix bugs. Other than that, I don’t want a radical UI overhauls of any of their operating systems (as if the latter would ever happen). On the hardware side, I’d love to see them refresh the MacBook Pro and iPhone SE sometime this year, but my expectations for an announcement at WWDC are very low.

As a developer, I don’t really want to worry about having to support new frameworks or features. Just upgrading from one iOS framework to the next one can sometimes take days of work before all the kinks are worked out. Even upgrading Xcode to a new major version is, as a Swift developer at least, a little scary. New versions of Xcode have not been stable or bug-free for me since Xcode 8 was released. The recently released Xcode 9.3.1 has been working really well for me, though, and I’m loath to give it up anytime soon. I’d love WWDC to be about Apple fixing the numerous, relatively minor, UIKit bugs that I’ve had to work around, but past history leads me to believe that iOS 12 will just have another set of odd bugs to work around.

Premature Optimization

In programming, there has long been a warning in computer science to avoid premature optimization. Donald Knuth called it “the root of all evil”. I find myself thinking about this all the time—not so much while programming, but when I’m thinking of spending money on myself, or telling people how to spend their money on me, as for birthday or Father’s Day gifts.

I’m at an age now where I have everything I would ever want. But…everything I have could still be a little bit better. To wit:

  • I have awesome headphones that I love. I want better ones. And different ones.
  • I have a home server that is underpowered, but quiet and extremely reliable. I would love one with enough power to could run virtual machines, but I don’t really need it.
  • I have a clicky mechanical keyboard that I love. I want a better one—that lights up, unnecessarily, or has colorful keycaps.
  • I have an Apple wireless keyboard for my Mac. I want to replace it with the Apple Magic keyboard, even though I already have an Apple Magic keyboard for my iPad.
  • I have a Series 1 Apple Watch that I love. I would love, even more, a Faster Series 3.
  • Let’s not even talk about iPads and Macs.

These few things are some of my material obsessions. What they have in common, for me, is that they have all been satisfied by things I already own, upgrading to newer or better versions would cost a lot of money (way more than anyone would spend in a gift for me), and the upgrade would be only marginally better than what I have, so I’m not sure if it would even make me happy.

Despite knowing all this, I can’t stop thinking about upgrading what I have to something better. I always want to optimize my experience with the things I enjoy. But, until the things I have break down and are no longer useful, it is too early to upgrade them. Doing so would be indulging in premature optimization, which be wasteful, which is “the root of all evil” to me.

Someday, my headphones will break, my keyboards won’t be compatible with my computers, my server won’t support the OS I want to run, and Apple won’t support my hardware anymore. That’s when I will upgrade these things—after I have extracted every bit of their value. Until then, I will just daydream about, and feel a little guilty about obsessing about, premature optimization.

Strategies to increase diversity on Micro.blog

Jean McDonald, Community Manager of Micro.blog, posted an essay today entitled “Diversity and Inclusion at Micro.blog: Where We Are, Where We Want to Go“.

The question comes up regularly: to what extent is there diversity in the Micro.blog community? We only ask for a name and an email address to register, so we don’t have any demographics on the users in our community. But I do know, based on skimming the names of those who register, that the percentage of users with typically female names is very small. When I look at users whose avatars are photos of themselves, I suspect the percentage of people of color is also very small.

I have been thinking about diversity on the platform since I started using it, the day it opened to the public in December 2017. Jean’s essay inspired me to publish some of my thoughts.

What do we expect?

The Micro.blog service has not been a publicly available for long. At this point, it is understandable that the first wave of users would be primarily composed of fans of its founder, Manton Reece. Manton is an iOS and macOS developer who blogs and podcasts about his development work and the indie web. If you have come across his work online, you are probably very much like him: an iOS or macOS developer, or at least a passionate user; a tech podcast listener; or a passionate blogger or IndieWeb aficionado. This core group is, for reasons related to historical and cultural biases, not a particularly diverse one.

This core group describes me, and certainly does not describe everyone on Micro.blog, but it does describe a lot of the users I found on the service’s Discover page. Manton and Jean have expressed, from the very beginning, an earnest desire to create a safe community of independent micro blogs—”safe” from the abuse that silences disempowered people, women, and minorities on dominant social media platforms. They, along with the users of the platform, have openly discussed how to increase diversity, and the challenges inherent in doing so. I have learned a lot from reading these blog posts and discussions. Like them, I wish for Micro.blog to attract and retain a more diverse user base. The question we all face now is: how?

Here are a few ideas.

Recognize and publicize that community guidelines are intrinsic to the product

Jean McDonald:

No one should feel unwelcome here.

This should be one of the public-facing mantras that applies to the entire project, much like “Don’t be evil” was to Google for many years. Jean’s quote should be atop the “Community Guidelines” page, and a link to that page should be near the top of the “help.micro.blog” page.

I think Micro.blog should put a lot more focus on the community guidelines and whatever technology or processes are used to enforce them. It’s a key feature of the platform. People behaving well together is the core of the product for me, and a key differentiator between it and Twitter.

Refine the marketing message

What is Micro.blog, anyway? To IndieWeb people, it’s kind of obvious. To everybody else, maybe not.

If asked, today, to sell it to someone, I might say: “It’s the good parts of Twitter, with none of the bad parts.” I might explain that microblogging is simply sharing something about yourself in public, and that Micro.blog is a safe, respectful place to do so, because it has protections against abuse, and strict community guidelines. If they are unsure why they should share thing in public, I would explain that it is empowering to do so. It is putting your best foot forward online.

Promote on podcasts

Having a simple, concise marketing message is essential, but that message needs to be spread somehow. One of the best ways to market these days is on podcasts.

Manton has a podcast and a microcast, which have brought a lot of people to Micro.blog thus far. I think podcasts are a great opportunity to promote the open, inclusive, but safe nature of Micro.blog. While podcast audiences may, as a whole, skew white, male, and wealthy, there are tons of podcasts out there that are hosted by, feature as panelists, and cater to women and minorities. I’m sure that Manton is adjacent enough to other tech podcasters to get some guest spots on tech podcasts that feature or cater to these groups.

Ask users for help

Micro.blog users are all, at this point, early adopters, and most of us are especially committed to the platform and want it to succeed. Ask us to publicize the service. Give us some ideas how to do that effectively, and in ways that will increase diversity. Provide incentives for us to sign up new people, such as additional badges (which are free to provide) or free months of Micro.blog hosting (which of course incurs a cost). I’m sure something will come of it.

Closing thoughts

My list of suggestions is by no means exhaustive, and Manton and Jean are likely in a better position than I am to understand what they need to do, and what they can do. I do want to express that diversity is important for all of us, even white, male, Americans such as myself. If all people are treated with dignity and are allowed to participate in something (work, society, etc.), outcomes will be better, and life will be richer, for all of us. I have seen that firsthand at a small scale, and wish to see it at a much larger scale. Micro.blog is a good place to start.

Chicken Sausage and Escarole Soup Recipe

Notes

This is a hearty, pasta-free soup, fit for a winter meal. Lots of vegetables, sausage (either chicken or pork sausage can be used), and cooking liquid from cannellini beans (canned or homemade) lead to a chunky, filling soup with a rich mouth feel.

Developing a fond while cooking the sausage will add an important foundation to the soup’s flavor. Deglazing this fond early, before cooking the vegetables in the same pot, will prevent it from burning.

Ideally, the vegetables should be soft but not browned; if they are not softening sufficiently during the sauté, simmer them longer in the broth, rather than extending the sauté.

You can substitute your preferred herbs for the Italian seasoning that I use. If using fresh herbs, add them at the very end, or just before serving.

If you wish to add pasta, ditalini works well. Cook the pasta separately, and add it just before serving, to avoid the pasta absorbing too much of the broth during cooking or storage.

Ingredients

  • 1 12 oz package chicken sausage
  • 1/2 cup water or chicken broth, for deglazing
  • 2 tbsp olive oil
  • 1 cup chopped carrots
  • 1 cup chopped celery
  • 1 cup chopped yellow onion
  • 1 7 oz bag fresh chopped escarole
  • 2 15 oz cans cannellini beans, not rinsed or drained
  • 8 cups low sodium chicken broth
  • 1 tsp Italian seasoning
  • Salt and pepper, to taste
  • (Optional) Fresh squeezed lemon juice, to taste
  • (Garnish) Freshly grated Parmigiano-Reggiano cheese

Directions

In a large pot or Dutch oven, brown the sausage in 1 tbsp of olive oil for 4 minutes per side over medium heat. This will likely not cook it through, which is fine; it will cook through later in the soup. Remove the sausage and set it aside.

Deglaze the pot with 1/2 cup water or chicken broth. Retain this liquid in a cup or bowl; it will be added back to the soup later. If the retained liquid contains any solids, strain it to remove them.

Once the par-cooked sausage is cool enough, cut it into coins and set it aside, to be added back to the pot later.

Dry out the pot and add 1 tbsp olive oil. Sauté the onion, carrots, and celery over medium heat until they are soft but not browned, about 10 minutes. If the vegetables are not completely soft after the sauté, that is OK; they can be softened after the liquid is added. Add the escarole and Italian seasoning and stir everything to combine.

Add the chicken broth, and add back the retained liquid from deglazing. Raise the temperature to high until the broth starts to boil; then lower the temperature to medium or medium low, to maintain a low simmer. Simmer until the vegetables are soft, which can take 5 to 10 minutes.

Add the cannellini beans, including their cooking liquid, and the sausage. (These ingredients are added later to avoid overcooking them, which would lead to split beans and tough sausage.) Continue to simmer until the sausage is cooked through, which will take only a few minutes.

Season the soup with salt and pepper to taste. If, at this point, the soup tastes dull, add some fresh squeezed lemon juice, little by little, until the broth tastes as bright as you want it to.

Serve topped with finely grated Parmigiano-Reggiano cheese.

Things I wish I could stop doing, but probably can’t

The beginning of the year is a time for setting goals. I have set some goals, and may post them here later. This list, however, represents my anti-goals—my to-don’t list, if you will.

  1. Lamenting failures rather than celebrating successes
  2. Being more interested in process than product
  3. Talking myself out of things
  4. Planning a project, rather than starting it
  5. Drafting blog posts, but never finishing them
  6. Letting important things pile up
  7. Not letting unimportant things go

These are my bad habits and bugbears, the blocks in my mind that frustrate me and prevent me from achieving my full potential.

These are the vampires that I have let in. They are no longer welcome.

Top posts of 2017

I started this blog in the summer, and since then I have published 30 posts, including this one. As far as output goes, I have met my goal, and I am happy with that.

Most popular posts

In the spirit of publishing year-end best-of lists, here are my top five most popular posts from 2017:

  1. Ulysses, a peerless writing tool, a short essay about my favorite writing software. I love good software, and think way too much about what makes productivity software, well, more productive.
  2. Choosing an iPad Pro Keyboard, in which I compare three of the main keyboards iPad users like me might be considering.
  3. Comparing todo.txt and TaskPaper formats, which are two plaintext task list formats. I love plaintext, love productivity software, and love not having lock-in with proprietary software vendors. I have been using both formats for different planning and task management tasks at work all year.
  4. Three ways to create nested projects in todo.txt, which addresses a common problem with the todo.txt format.
  5. Contexts in Getting Things Done, in which I describe the challenges I faced dealing with contexts in the GTD system.

These posts reflect some of my main interests: productivity software and systems, and Apple hardware. I have also written a little bit about Android, the Essential Phone, and parts of the free and open web that interest me.

Thoughts on the writing process

One thing that I have learned this year, from writing regularly again, is how much work it can be to complete a blog post. I have a half-dozen incomplete blog post drafts in my Ulysses library at any given moment. Shaping them into something worth reading is a lot of work—work that I don’t often complete as quickly as I would like. Even a simple 500-word post has to be written and re-written three or four times before I think it is worth publishing.

The writing process is valuable to me, though. Writing is a lot different than analyzing data (my day job) or writing code (my nighttime hobby). Writing, re-writing, and revising help me think and help me focus in ways that my more mathematically-focused activities do not. Plus, it feels good to communicate to the world, and to own all the content I produce and publish it on my own platform, under my own name.

The future

I plan to blog regularly in 2018, both on this site and on mjdescy.micro.blog. I have even set up regularly scheduled reminders (Apple Reminders, naturally) to help keep me on track. Thanks for reading.

Micro Blog

I started a micro blog at mjdescy.micro.blog this week. It is not to replace this blog, but to supplement it with a more frequently updated stream of short comments and asides about my life, or about news items that directly affect my life in some way. I want it to be like Twitter was for me back when I first joined it: a stream of consciousness, and a window into my life. My plan is to keep this blog (my macro-blog?) free of micro blog posts and life blogging, and more focused on longer articles, bigger ideas, and more complete thoughts—as it has been from the very start.

What I want is Twitter that isn’t Twitter

I love Twitter. So much information and commentary is shared there, so quickly, that it is a vital source for “what is going on on the Internet today”. At the same time, I hate Twitter, for all the bad behavior performed on the platform that Twitter, the company, tolerates. I’m not alone. A lot of people I follow feel the same way. I see tweets like this almost every day:

Brad DeLong: “I wish there was a network like twitter, but not, you know, actually Twitter”

 

The thing is, practically since Twitter’s inception, alternatives did exist. I know. I used them: Identi.ca, StatusNet (the successor to Identi.ca), Pump.io (the successor to StatusNet), and App.net (a for-fee Twitter that got a lot of press but not so many users). And, I abandoned them and went back to Twitter, despite its flaws. So did everybody else.

Why is Twitter so sticky, and nothing else is?

What makes Twitter is valuable not what it does—microblogging is relatively easy to implement these days—but who is on it: Famous people! Intellectuals! Politicians! Journalists! These people and many more are not only publishing there, but reading there, too. Communication with, and between, influential people there can be two-way, and is usually in public, which is fascinating to read and unlike any other communications platform that had come before it. Twitter can amplify the voice of the non-famous and non-published people, too—the under-represented—which is often great.

Why is Twitter described as a cesspool?

Sometimes, though, amplifying under-represented voices is not great. Some voices are under-represented because they are malicious: Racists! Nazis! Liars! Sexist doxxers! Spammers! Russian bots! Malicious people have unique incentives to exploit and abuse a communications platform like Twitter. First, simply having a medium and a platform to spread their message is unique to them, because these people have been barred or banned elsewhere from spreading their message. Second, access to this new platform may be fleeting, because they could be banned there, too, for the same reasons they have been banned elsewhere. Third, people who want to spread malice are not the type of people who are concerned with preserving the health of the platform’s community, or the platform’s reputation in the wider world. Therefore, they can destroy the platform in the process of spreading their message.

Why can’t Twitter fix this?

The world is too complex to separate people, or Twitter users, into good and bad actors. What is unpopular or under-represented today may be celebrated tomorrow; it may be true and worth spreading today. Understandably, Twitter doesn’t want to choose who gets to speak on their platform. Therefore, they tolerate hate speech on their platform to a degree that makes some of their users angry. It puts the company in a difficult position when hate speech is broadcast (retweeted) by the President of the United States, as it was this week.

I understand Twitter’s problems as a company. It needs eyeballs on it to sell ads. Controversy on the platform, and the sheer number of active users (whether they are real people or bots), lead to greater traffic, greater revenue, and greater return on investment for their investors—at least in the short run. In the long run, however, poisonous speech on the platform poisons the platform.

What to do about it, as a Twitter user?

Basically, it is hard to see how, as users, we can improve Twitter. Twitter, the company, owns the platform. Consequently, it has the sole power to fix its flaws. Improvements to blocking and reporting abuse that Twitter has implemented have not satisfied the users who need them the most.

Moving away from Twitter entirely, onto another, similar platform, can work for small communities who primarily wish to communicate amongst themselves. It is unlikely, however, that a critical mass of influential users—the celebrities, journalists, etc., who make the platform valuable—will move to a different platform at this point. Without those users, another platform, however superior from a technical or community management standpoint, would not have as much value.

As a Twitter user, you really have two choices now: live with the abusive users, and report and block them as well as you can; or, if Twitter abuse is bothering you enough (or worse, threatening to your safety), stop using Twitter entirely. That is a sad conclusion to make, but I think it is realistic. Twitter’s ad-based model, need to generate both traffic and return on investment to satisfy its shareholders are, in the short run, at odds with its stated goal to improve safety, and therefore community, on its platform.

Fortunately, there are other ways to write content on the internet for free, such as WordPress. The problem is, you may never achieve the same reach with these other platforms as you would with Twitter. That is why I am sticking with Twitter myself. From a moralistic point of view, I would love to ditch it for something else. Despite that feeling, I get enough value from Twitter to keep using it, despite the sick-to-my-stomach feeling the Twitterverse gives me some days.

Back to RSS and the Indie Web

At the end of last year, I quit using RSS. It was a big step for me. I had been using RSS practically since it first became available. My first RSS reader was the Sage plugin for FireFox, which I started using in 2004. I subscribed to Slate, LifeHacker, a couple other professional publications, and a fairly large number of personal blogs, covering topics ranging from technology, economics, and personal finance to cooking and television shows. I was obsessive about skimming my feed many times a day, reading every headline, and often every article, of Slate and my favorite blogs.

I eventually dropped Sage for Google Reader, and used it, and later Feedly, as a back-end to whatever smartphone RSS reader I was using. For years I checked my feeds a dozen times a day, read a ton of articles (though not all of them, as I used to), and generally felt pretty happy with the experience.

Why I quit using RSS

I stuck with RSS long after I became a habitual Twitter user, long after I started to see articles linked to from Twitter before they hit my RSS reader, and long after most technology writers and podcasters started disparaging RSS as some antiquated technology that, like dial-up internet service, was hopelessly out of date.

Eventually, though, I quit using RSS—not because it was uncool, but because it was no longer making me happy. Like those writers and podcasters said, the basic need RSS fulfilled for me—keeping current, and entertained with fresh reading material—was being fulfilled by other services. Twitter did so more timely, and with more commentary from the writers. News aggregators, such as Apple News, did so with a slicker visual style. (I am emphatically not a regular Facebook user, so I miss out on whatever is going on there.)

I thought these services were more hip, modern, and fun than RSS. Most importantly, I thought they were keeping me more current. After all, for a long time, my RSS reader (the wonderful Reeder app for iOS) fed me the same articles that I had already seen on Twitter. Worse, it fed me five or six different publications’ takes on the same subject every day, which was interesting a few days of the year (such as when reviews of new Apple devices hit the streets), but was otherwise completely redundant.

What I missed without RSS

After a year RSS-free, I started to think something was missing. I was literally missing articles that I would like to read, especially those from bloggers I liked, such as Erica Sadun and John Gruber, because they would pass by in the timeline before I would see them. I was missing bloggers’ voices in general, because most of my Twitter list (like everybody’s, I’m sure) is heavily news related. I could keep up with what the New York Times and Washington Post are publishing each day pretty well; but what about what Manton Reece and Tyler Cowlin are publishing? Their voices were being buried in my Twitter feed by the daily (hourly?) news cycle.

Without RSS, I missed the spirit of the independent web: all those individuals and small publications who are sharing knowledge and expressing opinions that don’t fit into 140 characters, or even 280.

Back to RSS (and Atom, and JSON Feed)

After many months away from it, I realized that RSS wasn’t the problem—I was. I wasn’t using RSS in a way that made me happy. Worse, I supplanted it with Twitter, which both sucked up all my attention every day, and reduced my attention span for content to 140 characters (a length perfect for snipes and jabs and headlines, but insufficient for most cogent thoughts). Fortunately, RSS has not died since the rise of Twitter and Facebook. It has quietly remained a fundamental internet technology, undergirding nearly every online publishing platform. Many, many sites support it without advertising it the way they used to ten years ago. Luckily, any good client can find feeds using just the site URL.

Not only RSS is still there: my longstanding RSS software is still there, too. Like in 2013, I am using Reeder on iOS as a front end, and Feedly as a back end. Reeder has been around almost as long as the App Store. It is rarely updated, but it just works. It’s simplicity, elegance, and stability make it one of the finest apps on the platform. Feedly, the back end service that actually checks my feeds, is a free service that I basically never look at. I don’t use their website. I don’t use their app. I don’t really know or care how they make money off of me. It, like Reeder, is solid, stable, and just works.

Using RSS with a different perspective

After returning to my RSS reader after such a long break, I had thousands of unread items and dozens of subscriptions. I decided to start over, so I unsubscribed to all my feeds, and started thinking about what I really wanted to get out of RSS, and, in general, out of the Internet.

I decided to use RSS differently now. I no longer need it to drink the content firehose and keep current with the minute-by-minute news cycle; Twitter is available for that, for good or ill. Instead, RSS enables me to follow a few interesting voices on the Internet, read their actual, in-depth thoughts, and not miss anything they have to say.

To these ends, I no longer follow big media sites. Primarily, I follow blogs: real blogs, written by actual people, rather than published by massive organizations. I’m mostly following Apple-focused tech bloggers and Swift programmers, which reflects my favorite hobbies—but that’s just what I’m doing for now. Lastly, I’m not checking my RSS feeds a hundred times per day. I am checking only a one or two times per day, and often I don’t have any updates. Instead of adding more feeds, I just accept it now. Sometimes there’s nothing new to read, and that’s OK.

I’m happy with RSS again. All it took was figuring out what I really needed to get out of it, and taking control of how I used it. It’s a really great technology, no matter how passé or uncool it seems to be.