Menu

Colin Devroe

Reverse Engineer. Blogger.

Follow: @c2dev2, RSS, JSON, Feedly, Micro.blog.

An interview with Manton Reece of Micro.blog

I have fond memories of the very early days of WordPress (when it had just been forked from b2/cafelog), of Twitter, of Brightkite, of App.net, of Mastodon… just to name a few. The early days of any platform or so important to what they will become. They are the most fun to watch.

The early days of any platform can be frustrating too. Services sometimes go down, features aren’t released as quickly as you’d like, and small bugs can hamper your workflow.

I liken it to watching art be created. It can be a bit messy, it can sometimes confuse you, but when you see the final product you have the privilege of knowing how the platform got to that final state.

Yesterday I volleyed back and forth via email with Manton Reece, the founder and creator of Micro.blog. Micro.blog is in that same relatively early stage where new features are released with regularity, where the community is growing steadily, and where the users have the strongest voice.

He kindly answered a few questions. But here are a few highlights that I plucked from his answers:

  • Micro.blog is both an aggregator of blog posts and a blog/site hosting platform
  • Features on Micro.blog are rolled out slowly on purpose, to be sure they won’t disrupt the principles behind the service. And they often come from what users are already doing on the platform.
  • Native support for audio and podcasts are already part of the plan
  • Many users that use the hosting feature use their Micro.blog-powered site as their primary web site
  • Community support members for curation, help, etc. will be the primary area the team will grow, outweighing engineering

Here is the interview and his responses in their entirety.

First, thank you for making Micro.blog. For me personally it is surfacing some excellent independent microbloggers that I wouldn’t have found otherwise. Now that Micro.blog is open to the public, is there anything that you see happening on the platform, either now or during the beta period, that has surprised or delighted you?

Thanks for being part of the Micro.blog community! I’ve loved how people not only embrace the platform, but in many cases get back to writing at an old blog that they had accidentally neglected, or get inspired to start up a new microblog at their own domain name. So many beautiful photos have been posted, which we like to highlight in the Discover section, and the tone of conversations has remained thoughtful and respectful even as the platform has grown.

I’m also happy to see that many Micro.blog users have warmed up to some of the early decisions we made to not copy every feature from other popular social networks. For example, not showing follower counts or worrying about how many likes a post has received.

People seem to really enjoy the new emoji-based topics we introduced recently, to collect posts about books or music or sports. Little experiments like these are a reaction to what the community is already doing. The best thing we can do is build features that support what people are posting about — to encourage the kind of posts that make Micro.blog a nice place to be — and then see which of those features resonates.

Have you been surprised at all by the number of photos that people are posting? Or, did you always think that Micro.blog would be a great place for people to share photos? And, do you think you’ll see audio or video shared more on Micro.blog in the future?

I’ve always thought photo-blogging would be a perfect fit for Micro.blog, and we’ve tried to build good support for it in the iOS app, such as having built-in photo filters. Many people are frustrated with Twitter and Instagram and want to post photos to their own web site again. But I was still happily surprised to see so many photos. There was also some help from the community, such as Doug Lane running a 7-day photo challenge.

Our plan was to start with photos, with good photo hosting, and then expand to natively support audio and podcasts. After that, video. I think video can quickly become kind of overwhelming and busy when shown in a timeline — especially with auto-playing video, which we don’t want to do. So I’m comfortable expanding this support fairly slowly to make sure we get it right.

I see Micro.blog as two parts: 1. A community of syndicated microblog posts that are populated by people’s independent web sites using RSS or JSON feeds. And, 2. A blogging platform that allows you to create a simple blog (with an emphasis on microblogging). Is this the right way to look at Micro.blog now and into the future? And if so, why tackle both problems rather than simply #1?

That’s the right way to think about it. What I found while developing Micro.blog is that just building a more open social network-like platform wasn’t enough. If we wanted to encourage people to blog more, we needed to make blogging itself much easier. The best way to do that is to also offer to host someone’s blog for them directly on Micro.blog.

Blogs hosted on Micro.blog started with an emphasis on microblogging, but they have improved significantly since we initially launched, and now offer many features competitive with other dedicated blog hosts. There are Micro.blog users who have their full web site hosted by Micro.blog because it’s just more convenient.

This second part of Micro.blog is also very important to grow the service as a business. I want to run Micro.blog for decades to come. The only way to do that — to pay for all the servers and other supporting services — is for Micro.blog to be profitable. Since we never want to show ads, offering paid plans such as blog hosting is a great way to go.

Would you be willing to share any interesting stats? Some that I’d personally be interested in tracking would be the most number of posts in an hour, the greatest number of signups in a day, stats like that.

And as a follow-up: As the platform (meaning the software, hardware, underlying services, backup routines, databases, etc.) become more complex surely you’ll need to expand from being the two-person team Micro.blog is currently. What position do you think the next full or part-time team member of Micro.blog will fill?

I don’t currently have many stats to share. We have been so busy improving the platform that we haven’t built anything to track things like spikes in the number of posts. There is a 500-user limit on new registrations per day. When we opened it up to the public, the limit was just 100 which was reached pretty quickly as people would share a link to their friends.

There are so many areas that we could use a larger team for, like system administration and planning how to scale the platform. As you noted, the first person to join Micro.blog was Jean MacDonald, our community manager. I hope that the community will continue to grow such that we’ll need additional curators to help manage features like the Discover section.

Facebook recently announced they were hiring 10,000 moderators, and I know Twitter has a large staff as well. I expect one mistake that these larger social networks made early on was hiring too many programmers, and not enough curators. For Micro.blog we always want people who can interact with the community and stay ahead of any issues.

Discover has already seen a few iterations. First, it was a simple list of users. Then it expanded to include photos posted by the community. After that, a human-curated list of posts was added. And now, hashtag-like emoji’s allow you to find posts on topics like books, music, and football. Did I miss anything? This must be a fun part of Micro.blog to tweak and see how the community responds. I know I’ve found it to be very fun to have open a few times during the day. Can you share a little about how posts end up in the Discover tab? Who is making those selections and what are the next steps?

I feel like the current iteration of Discover is by far the best yet. There were a couple problems with just featuring a list of users. You can only feature so many users, so we randomly selected users to show from the featured list. Those users would get a lot of attention but unless we continually update the list, it might not be enough people to fill your timeline with interesting posts if you just pick a few people to follow. The list got stale quickly as new people were joining the platform.

Now, throughout the day we skim through posts and replies and put them in Discover. This is a better reflection of the activity on the platform. It’s not all posts, but it’s a good snapshot of the kind of things people are posting about. It looks good and isn’t overwhelming. It’s a great way to find new users who just joined Micro.blog, too.

Emoji topics are a little different. Whenever Micro.blog sees a new post, it checks it for emoji and adds it to a collection. If an inappropriate post shows up, we can just remove it from the collection without effecting anything else about that post or user on Micro.blog. There are a limited number of emoji, which keeps everything simple. I don’t think it will get out of control like Twitter hashtag search results often do.

One aspect I’ve always loved about microblogging was that it could be consumed and participated with in realtime. A few examples that come to mind are backchannels for live TV events like awards shows, or for conferences and meetups, etc. Is this something the Micro.blog team thinks about much? Are there any apps, features, or other considerations that would be made specifically to foster realtime interactions for things like this?

I agree this is a natural fit for indie microblogging. Something like live sports might not appeal to everyone, so it would be useful for both tuning into those feeds or filtering them out. Over the weekend, we put the football emoji in the Discover section for people who were posting about the NFL playoffs, as a simple experiment for making current topics more discoverable.

There are myriad other things we could talk about like Pins, third-party applications, indieweb building blocks like Webmention, and the all new Micro.blog logo and app icon. Is there anything you’d wish to highlight? If so, please do. And lastly, what is something you wished I asked but didn’t that maybe you’d like to make sure people reading this interview know (feel free to allow this to be nothing)?

The third-party ecosystem and larger IndieWeb community are both really important. There are several third-party apps for Micro.blog in development now, for iOS and Android. When I was designing the Micro.blog API, I based it on JSON Feed, Micropub, and other common APIs so that third-party Micro.blog apps could also be adapted for other platforms. And likewise, Micro.blog benefits from many existing IndieWeb tools and open source software like WordPress. The more we can push forward the user experience for indie microblogging, making blogging more approachable, the stronger the open web will be.

Thanks Colin! It was great to have a chance to share some of our thoughts behind Micro.blog.

Thanks to Manton for taking the time to write thoughtful responses. If you haven’t yet given Micro.blog a try head on over to there and give it a whirl. You could very well make an impact on the type of place it becomes.

You can follow Manton on Micro.blog at @manton. And I’m @cdevroe.

App icon design, one size does not fit all

Yesterday I reposted Becky Hansmeyer’s vent about having to create multiple icon sizes for her app. I feel her pain. I recently completed an app for both iOS and Android and so I had to create just over 1,000,000 icon sizes. At least it felt like it.

So, like her, I too would like Xcode to create all of the sizes I need from a single larger file.

The issue with this though, which I’m certain Becky knows but she still just wants things to be easier anyway (so do I), is that one size does not fit all in icon design. Each size needs to be considered individually – especially with complex icons.

To quote the venerable Dave Shea from 2007:

One of the more deceptively time-consuming things you’ll do when creating an icon is producing out size variations. If you require a single icon in more than one size, the time you spend designing the first size is only about two thirds of the work you’ll end up doing; the other third lies in tweaking it for different dimensions.

As the size of the icon gets smaller details get lost and so the designer needs to begin removing elements, increasing stroke widths, and the padding around the elements within the icon.

It is why I designed the Summit icon (which I plan to write about in the coming weeks) to be so utterly simple that it will scale without very many tweaks as the icon reduces in size.

As you can see the icon changes very little from large to small. I remove the gradient, tighten one or two things, but that is it. So I’m able to use a Photoshop template that automatically creates every single size from a single Object – and then remove the gradient from the smaller sizes, and then finally increase the spacing at the smallest sizes.

So far this has worked well in my testing on my devices. I still have more I’d like to do with the icon but it will have to do until I get a new beta out. I haven’t shipped a beta in months because I’m rebuilding Summit for both Android and iOS, as well as have a few other irons in the fire.

 

 

Best of 2017 as told by me

To create this list I sat down and wrote from the top of my head the things I could remember being awesome in 2017. The list isn’t exhaustive. It is just what made an impression on me as being “the best” in each category.

Best Blog: fuzzy notepad

Evee consistently writes well-researched, readable, diatribes on topics that could otherwise be boring yet are fascinating and I hang on every word. Here are a few posts from 2017 to get you started:

Best blog redesign: Colin Walker

When I awarded this to Jason Santa Maria so many years ago it was due to his use of color, contrast, typography. But design isn’t limited to how something looks but also how it works. Colin Walker has spend much of 2017 tweaking his blog’s features in subtle ways to work just the way he wants it to. I’m sure he’ll continue to fiddle with it throughout 2018 but I think we can all learn from Colin’s iterative approach. Keep tweaking.

Best new (to me) blog: Brand New

I’ve known about Brand New for a long time and have stumbled across a post or two over the years. But this year I’ve been pushing myself to learn more visual design and one way was to subscribe to more blogs like this. I find these posts, and the community, to be an excellent resource.

Best service: Spotify

This year I’ve used both Apple Music and Google Play Music to see if I could move away from Spotify. Spotify is in a league all its own, the other two don’t even compare well. Spotify’s machine learning robots just do an amazing job at surfacing music that I would like. It is so good it is eery.

Notable mention: Google Photos. I’ve switch from Apple iCloud Photo Library to Google Photos and I’m consistently being surprised by how much better it is.

Best book: Ready Player One by Ernest Cline

This was a tough call. I read some pretty great books this year. But the one that keeps coming up in conversations, the one I’m sharing the most is Ready Player One. I think it is the sci-fi novel that I read this year that most feels like it could happen within a few years.

Notable mention: The Wright Brothers by David McCullough and Annihilation by Jeff VanderMeer.

Best productivity tool: Bullet Journal

Bullet Journaling has made the biggest impact to my productivity and cognitive load than any other app, technique, or method this year. My “version” is slightly different than the default but I’m loving it.

Notable mention: Trello.

Best phone: Google Pixel 2 XL

I’m cobbling together my notes for a “review” of the Pixel 2 XL in the coming weeks but I can say, unequivocally, it is the best phone of the year. For me. I know the Samsung Galaxy Note8 made many people’s list and of course the iPhone X deserves a mention – but for the price, the quality of the hardware, and the software the Pixel 2 XL is an easy winner for me.

Before I get email, know that I have an iPhone X (Eliza’s phone) and I’ve tried the Samsung models. For me it came down to the camera system (which is actually better than the iPhone X in everything but the second lens), the software (Android 8.1 – Samsung is way behind) and the price. The iPhone X will be better next year and, hopefully, iOS 12 will be much, much better than iOS 11. But, as of today, Google is killing it.

One other side note: Google as a personal assistant is so much better than Siri it is jarring. I may have used Siri a few times per month in the past but today I use Google about 10 times per day with nearly zero mistakes.

Notable mention: Samsung Galaxy Note8, iPhone X.

Best podcast: The West Wing Weekly

If you’re not a fan of The West Wing this choice may not land with you at all. So, for you I would suggest Song Exploder. If you haven’t yet listened to TWWW I suggest starting at the beginning and also watching The West Wing along the way.

Notable mention: Song Exploder / Tim Ferriss.

Best platform: Instagram

When I deleted my social media accounts and didn’t even look at them for a few months the one I missed the most was Instagram. The platform continues to be one of the best and they continue to add great new features all the time while somehow keeping the app’s history in tact. The day may come when they add a feature that is terrible but so far they’ve done pretty well.

Side note: The algorithmic timeline almost pushed this one out for me. It is nearly inexcusable that this isn’t optional. I sincerely hope they find a way to allow users this option this year.

Notable mention: Micro.blog.

Best browser: Firefox Quantum

Perhaps this should be “most improved browser”? Quantum is a great name for the strides Mozilla has made with Firefox. They continue to improve the browser.

Oddly, Firefox is not my “daily driver”. I am using Chrome due to my switch to Android. (I’m ecstatic that I now can choose a default browser) I may, though, give Firefox a try across the board again soon.

Notable mention: Safari for turning off auto-play videos and ad tracking by default.

Best app: Apollo for Reddit for iOS

Though I’m now using Android I have to list Apollo as the best app. If you ever kill time by looking at Reddit (which I do a few times per week) I have to suggest you try this app. It is so well made you’ll wish it’s developer made every app you use.

Notable mention: Snapseed and Google PhotoScan (search App Stores).

Best code editor: Visual Studio Code

VS Code has improved a lot over the last year and has now overtaking Atom as my default text editor and code editor for all projects. While I still build native apps in Visual Studio most of my web work and text editing happens in VS Code.

The shared workspaces are the big feature for me this year. I can combine several code repositories into a single workspace and use Spotlight to launch all code related to a particular project in less than a second. It also has git and terminal integrated so I’m usually able to do all of my work in a single window.

Notable mention: Atom, Visual Studio for Mac.

Best YouTube channel: First We Feast

Specifically, Hot Ones. First We Feast has an interview show called Hot Ones that I just discovered this year and I can’t get enough of it.

Notable mention: MKBHD

Those are all of the categories I wanted to feature this year. Again, I simply pull this list together from the top of my head. Just like all years I saw so many amazing things it’d be very hard to create a real list. I suggest following my blog for all of 2018 because whenever I see something worth linking to I do so.

There are, however, some other companies, people, and products that I think deserve a shout-out. Here they are in no particular order: SpaceX, Khalid, Tom Hanks’ lost gloves tweets, The Last Jedi hype, Chris Stapleton, Joe Rogan’s Powerful JRE Podcast, Amazon Kindle and library loans, letgo, Google Maps, OK Google, Logitech MX Master 2S, USB-C, cast iron pans, Amazon Prime.

See you next year.

 

 

SPARK Talks at the NEPA Tech meet up in December 2017

SPARK Talks are, by definition, Short, Provocative, Action-oriented, Realistic, and Knowledgeable talks that are loosely timed, on a specific topic (more or less), and allow many presentations to be given at an event. I had never heard of them prior to this month’s NEPA Tech meet up organized by John George.

SPARK Talks remind me of Lightning Talks or Ignite. I have been to a few Ignite events – some where very early like this one 10 years ago. The thing I appreciate most about this style of presentation is that many in attendance can be part of the program. In fact, at this particular meet up nearly every single attendee was able to take a few minutes and describe themselves, something they’re currently working on, or a topic of their choice.

Photo: Ted giving his presentation on Rust.

In all there were 15 presenters. I quickly jotted them down as they happened. I didn’t get full names or all of their web sites, but at least I captured something. Here are the presenters and their topics:

  1. John – spoke about becoming an independent developer
  2. Jared – discussed his ambitions of working in real estate
  3. George – described use IoT in industrial industries
  4. Ryan – talked of learning more about computers, the web, to better do his job
  5. Kevin – discussed some of the WhatNow! journey
  6. Beth – spoke of her passion for the environment
  7. Colin (me) – spoke about not getting hung up on decision making, just start
  8. Jason – discussed some of the projects Sho Technology Solutions is working on
  9. Ted – talked about the advantages of Rust
  10. Anthonyeducated us on the xAPI
  11. Chris – discussed some of the challenges and next-steps for NEPA Fiber
  12. Danny – showed us a video demo of Kraken Board Sports latest product
  13. Mark – rallied the attendees to contribute to NEPA Tech
  14. Den – discussed his self-taught history of becoming a front-end developer
  15. Gary – discussed eating odd things for his YouTube channel

As you can see the topics were all over the map which helped to keep the evening interesting and the shortness of the presentations moved the event along nicely. I believe NEPA Tech will do events like this again in the future. If so, be sure to contribute. Most of these were fairly unscripted talks so don’t be hesitant.

Thanks to John George for organizing this month’s event. Onto 2018.

Universal Apple apps

Mark Gurman, for Bloomberg:

Starting as early as next year, software developers will be able to design a single application that works with a touchscreen or mouse and trackpad depending on whether it’s running on the iPhone and iPad operating system or on Mac hardware, according to people familiar with the matter.

Remember the many times I’ve written that I wish Apple would combine iOS and macOS into a single operating system that simply adjusts based on the device it is running on? That isn’t what this is, but it is still a great step in the right direction.

Me, a little over a year ago, regarding the Surface Book with Performance Base:

I’ve long written on this blog that I believe Microsoft’s vision of one operating system for both contexts is better than Apple’s two-OS approach. John disagrees with me on this. And I don’t know that there is a right or wrong answer but there certainly is a preference. My preference is to keep my “power user” stuff at my fingertips for when I need them but to hide them when I don’t. The Surface Book does this.

When I was testing a Surface Book for a time I had what I felt is the best of both worlds. I came into my office, docked on a large monitor, and got to work. When I wanted to be mobile and work out of a coffee shop, I could be and everything came with me. Then, when I wanted to read on the couch I could undock the screen and use it like a Surface. Windows 10 would adjust to whichever context I was in. It was either optimized for keyboard / mouse input or for touch.

I still believe this is the correct approach. And we’re starting to see more of it. Look also at Samsung’s DeX that allows a phone to plug into a display and give you a slightly different interface, drag-and-drop, etc. for getting your work done. There are countless number of professionals where this type of setup would not only work well – but it would be ideal and less expensive or confusing than having disparate devices.

This proposed strategy for Apple, that Gurman says he has insider information on, isn’t the same path that Microsoft is taking. It isn’t one device and it isn’t one operating system either. Gurman isn’t saying that Apple is going to release a single OS for all devices but rather that the app binaries will run on multiple devices and operating systems. It is more akin to Microsoft’s Universal Windows Platform. Many Windows UWP apps and games can run on Surface tablets, PCs, and Xboxes. This is amazing. I’m sure Microsoft users love it. Wouldn’t it be cool if Apple allowed the same app to run on Macs, iPhones, and Apple TVs? Wouldn’t that also allow many great iOS apps to suddenly be useful on macOS? I can think of many iOS-only apps I’d love to have on my Mac.

I welcome this if it happens.

I feel like these approaches are just stops along the road to a unified device that runs a single operating system and can work in many contexts. In some ways, it is the largest advantage that Augmented Reality will bring to the professional workplace. Put on your glasses and work however you’d like. Small window. Huge window. On a 3D object. Or on Mustafar with Tie-fighters flying overhead.

Until then, I’d love an iPhone 7 Plus-sized device that ran a single operating system that “worked like” iOS while on-the-go, and that I could plug into a large monitor and give me full macOS experience. That, for me, would be ideal. Until AR is ready.

No, you cannot simply pay me for a link

Hi. You emailed me. Likely more than once. So I’ve sent you this URL to let you know that no, you cannot pay me for placing a link in an existing article that you somehow found on my site.

It would be totally different if you wanted me to review a product, collaborate on some content, or sponsor some of my other projects like Summit, The Watercolor Gallery, or my upcoming YouTube channel. But, no, you want me to randomly throw a link in an old blog post because it ranks well on Google. And that, to me, seems icky.

Please remove me from any and all of your future lists of unsolicited emails of this nature. Unless, after reading this, you’re going to change your approach and do something much more fun and authentic like the above. In that case, my rates will likely be in the few thousands of dollars to get started.

Thank you,

Colin

Please don’t try to explain Bitcoin at parties (unless you know what you’re talking about)

Unless you’re drinking your flat whites under a rock, you’re likely seeing a lot of news about Bitcoin, it’s current exchange rate against the US Dollar, blockchain and it’s various applications, etc. You might even be getting sick of hearing about it (or, perhaps you’re sitting there earning hundreds or thousands of dollars per day from it). Either way, I must make one request of you, dear reader…

Please do not spread misinformation about blockchain and cryptocurrency. If someone asks you about these things and you don’t know, say so. They won’t think less of you. Explain to them that you too are interested in these things but that you still need to do more research before you’re willing to explain it to them. They’ll even respect you for being honest. Don’t make it up based on a few headlines or tweets you’ve read. If you are going to try to explain these things to people, especially youth, please dive in and get a deep understanding of some of these more complex technologies before you begin explaining them.

I think I’ve caught myself a few times, in recent conversation, going just a little bit further than my own knowledge and regretting it. I feel I have a fair understanding but I’m nowhere near qualified to teach on the subject. Which is why I’m bringing it up here on my blog. Fortunately, most of the conversations I’ve had about these things are with people that are also devouring every bit of information they can about it – and so I don’t think I pointed them in an incorrect direction. But I think we (the nerds among us) can easily misinform others if we begin to describe blockchain and crypto at parties.

So don’t try. Unless you know what you’re talking about.

Attending Venture Idol 2017 at Ben Franklin TechVentures

In 2007 I visited the area where Ben Franklin TechVentures is now. I was there for an interview with the then CEO of Viddler, Rob Sandie, to see about working there full time. At the time, Viddler was housed in Jordan Hall – a one-story building next to the now incredible Ben Franklin TechVentures complex. It wasn’t until many months later we moved Viddler out of the closet-like space in Jordan Hall and into the future-feeling building next door.

That memory pales in comparison to what exists there today.

I make mention of this fact because the feeling one gets when walking into Ben Franklin TechVentures is that the work that goes on in this building is new, exciting, and is the future of technology in our area. I personally want schools, libraries, incubators, and town squares to feel as though they are leading us into the future. Where the work that I do is raised to meet the expectation of the environment. I feel that Ben Franklin TechVentures does that.

In August when I presented at the local meet up I loved seeing the new wing being constructed. This month that wing was completed and this year’s Venture Idol 2017 event was in it.

But building’s aren’t everything. The community is of even more import. And the community is strong.

This year’s Venture Idol was the best attended year yet and, as Fred Beste (the emcee for the event) pointed out, everyone had a chair for the first time. He’s seen BFTV’s growth and he was as excited as I was to see where it is today.

The presentations by the three finalists were great. Mark Keith and I remarked how polished each presentation was. In my mind there were two presentations that were clearly the best; Channel Ape (from Scranton woot woot!) and Give Gab. Both had impressive results, tight presentations, and a roadmap that made sense. At the end of the night Channel Ape took home the victory.

Photo: Mike Averto, CEO Channel Ape, preparing for presentation.

Yes, it is a big of a jaunt from Scranton to Bethlehem. But it has been worth it every single time I’ve done it over the last 10+ years. I’m looking forward to seeing the sort of growth that region has been enjoying happening in our area too. It is only a matter of time.

Speaking at the 2017 tecBRIDGE Entreprenuerial Institute

Photo credit: Mandy Pennington on Twitter.

On Friday I had the privilege to host two sessions at the 2017 tecBRIDGE Entrepreneurial Institute Conference at Marywood University. The event was very well attended (I’d say nearly  200 people, but I don’t know for sure). The speakers and panels were engaging, interesting, and the number of people that remained until the last minute of the event was evidence of that.

My session was titled Social Media Metrics that Matter. I didn’t choose the title but I enjoyed the topic. The audience was mainly students focusing on being future business owners and also local businesses and organizations in our area. I can tell from the feedback that the subject matter was welcome.

The way I laid out my outline was to bring everyone in the room up-to-speed with common metrics that can be tracked on social networks. We spoke about how each of those metrics impacts the business, the content, the page. Then, we used a few example businesses to determine which of the metrics each of them should track and why.

It was a good exercise, even for me, and I hope those that attended each of my two sessions got something out of it.

A technology predication time capsule

Readers of my blog will know that I occasionally attempt to predict when certain technologies that I write about will hit the mainstream. While I’m very passionate about a few technologies, I try to temper that excitement with the experiences I’ve had, the wisdom that comes with age, and other factors. Usually, things take a little longer to happen than we’d like for the things we want to see most. And sometimes, sometimes, the things we want most never materialize at all.

For the purposes of this post, mainstream doesn’t mean critical mass but rather mass market adoption. With 7B+ people on the planet reaching critical mass is far easier than reaching mass market saturation. In other words, a company, product, or technology can reach sustainability and never truly hit the mass market. Examples: Tesla can succeed, be profitable, and have happy customers without the world moving on from fossil fuels. A company focusing on AI can make great livings, do compelling and challenging work, without every family having their own personal C-3PO.

Here are some stake-in-the-ground predictions on some of the most talked about technologies of our day. We’ll see in the next few decades if I was even close.

  • Legal, fully autonomous driving with no human assistance: Mid-summer 2026 – Even 9 years out there will still only be a few select vehicles that will fit into this category. There will still be humans driving on the road. And, only the most expensive cars will have all of these features. But, it will exist, be available to anyone, and be legal in the US. And I also believe there will be small fleets running in select cities for Lyft, Uber, and I believe Tesla will have a ride-share platform by this point. Also, don’t be surprised if Apple does too.
  • Bitcoin, or some crypto-currency, being widely transacted at small retail stores in the US: 2027 – If Square, or some other platform with high market saturation, turns on crypto for retail SMBs then we can say they accept this form of tender. But, I believe it will be 10 years before we see a decent number of daily transactions by consumers. I know, “decent” is relative so I’ll give it a number: $100,000,000 US dollar equivalent in a single month. This is roughly 25% of US monthly retail revenue as of September 2017. Side note: By this time we’ll see talk of the US dollar being converted to an all digital currency and, perhaps, transacted on its own blockchain.
  • Mixed Reality experiences used in everyday work environments: 2027 – Today we share links to web sites, documents on Google Drive, and flat or animated graphics to design and develop both soft and physical products. By 2025 many of these every day things will be accessible and even better experience within MR. I believe most businesses with digital assets will have multiple pairs of “glasses” or “goggles” that will allow team members to view or collaborate on these types of data. In other words, by 2030 rather than sending a child a link to Wikipedia to learn about our Solar System I believe we’ll be sending them MR experiences that they will consume using an augmented reality experience on a device other than a flat panel display. This happens today. But no where near mass market. And this industry has a long way to go. Even further than I previously thought.
  • Wireless internet takes over all cable based internet: 2029 – Most people in the US will connect to the Internet via wireless across all devices. And there will be no limitation on bandwidth usage.
  • Fully autonomous fleets replace individual car ownership: 2037 – Today US cities are plagued by traffic jams comprised of single occupant vehicles. Mass transit softens this but doesn’t solve the issue due to the convenience of a car. Ride sharing services have softened this even more and car ownership in urban areas is on the decline. By 2037 we’ll see massive reduction in individual car ownership in cities but also in the hinterlands as fleets of fully autonomous vehicles, combined with better mass transit, can care for the majority of transportation needs. I believe, however, families with at least 2 children will still have a single family-owned vehicle of some sort. Again, I’d like to put a number on this. So I’d say 15-25% less car ownership/use for individuals and commuters nationwide.
  • Mixed Reality replacing many conventional meat space locations/activities: 2050 – By 2050 the majority of children in the US will have the option to attend school in VR ala Ready Player One. Virtual classrooms will no longer be limited by federal budgets but will be designed to appear like cathedrals of learning.
  • (Because, why not?) An off-planet human civilization: 2175 – Humans will walk on Mars in the 2020s. And, perhaps, a small moon or Mars base will exist in similar fashion to today’s ISS in the 2030s. But a civilization, where people live, work, play, have children, and die peacefully etc. won’t exist on any other planet or moon (likely the Moon will have an established civilization prior to Mars). The reason I put this far-reaching prediction on this list is because I believe the excitement around a human footprint on Mars will lead to speculation about off-planet civilizations. But, we must all remember, we put a footprint on the Moon many, many decades ago and then just never went back. I do think that we’ll be mining objects near Earth much, much sooner. Even the Moon. But we’ll do that with robots and minimal human intervention.
  • Tweet editing – Never.

Check back in a few decades to see if I was even close.

Creating Summit: The current summit view

This post is the first in a series of posts about my experience building and designing Summit. This post focuses on just one view within the application; the current summit view.

The idea for Summit came nearly 4 years ago as far as I can tell. I’ve hunted around for scraps of paper, digital notes, code snippets to see if I can come up with an exact date but I’ve been unable to. And it has been fits and starts for several years.

When Kyle Ruane and I started on the idea we first thought the UI would be a bit more game-like. I envisioned a 3D model of the current mountain you were hiking that would progress the person up the summit in first-person towards each goal. This was altogether too much work, and far too difficult given my unfamiliarity with the platform. Kyle’s suggestion – again, many years ago – was to use a low poly look. He would craft a low poly representation of the summit and we could allow the user to move around in it, perhaps even spin it around, zoom in-and-out, etc.

I pulled that thread for a very short time before giving up. Remember, we started toying with the idea of Summit before Swift was released. So I was trying to draw this UI with Obj-C. Something I’m even more terrible at than Swift.

Here is what one attempt at drawing progress lines using Obj-C looked like back 4 years ago or so. I took this screenshot in June 2014 and was already labeling it “historical junk” in my files.

The red triangles were goals to meet, the blue line was your path, and the white line was your progress so far. My goal was to overlay this on top of the low poly art that Kyle drew. This was inspired by maps like this. (copied here for archival purposes)

This worked but was not that easy to pull of, introduced more complexity than we needed, and so we quickly shelved the idea until we got more familiar with the platform.

In tandem I began constructing a simple web UI to start cataloging steps from a phone. This was purely to get used to writing code that would track user’s steps, show stats, work on our step algorithm (the code that determines how far up Mount Everest a single step walking in a downtown city parking lot gets you), etc.

It went this way for a few years. I would open up a code editor and begin working on the pieces of Summit; the progress UI, the algorithm, the code to read from a user’s step count or HealthKit or Apple Watch.

In June 2017, when I picked up this project on my own to take on since Kyle had moved away, I decided I needed a simpler approach to the UI. In part because Kyle is the design genius but also in part because I wanted to get as quickly to shipping an app as I possibly could. I prefer to iterate on ideas with user feedback than to work on something in a silo for years. I wanted a way to show the summit, or some visual from the summit, but yet also show one’s progress. And I also still needed multiple goals per summit.

Here are a few drawings from this summer.

See, I’m not an artist. Admittedly, though, this wasn’t an attempt to draw anything beautiful but rather to get a general idea for all of the views I needed to pull off the layout. I needed some labels, some buttons, navigation, etc.

The long goal buttons was really “a punt” on my part. I gave up trying to get Xcode’s Storyboard feature to properly align a changing number of goal buttons (since each summit has a different number of goals) in a way that worked with each device size. It was very frustrating. So I began to go down this path of having them just be full-width, flat buttons.

But then I ran into Brian Voong on YouTube. In most of his video tutorials he suggests forgoing the Storyboard feature and using code to create the UI. Though I didn’t want to lose the progress I had made, I’m so glad that I took his advice. Writing UI directly in Swift is far, far easier (for me)  and seemingly more powerful than using Storyboards.

This revelation allowed me to go back to a drawing I did a month earlier. This one:

On the left, the elements needed, on the right, a rough sketch of a much more minimal and airy design of the current summit view. The goal buttons have varying distances between them relative to how far apart they are in real life (I’m still working on getting this right in the app).

Using Swift I was able to make this happen much easier than Storyboards.

The above is one of the very first swings at this view. It had all of the elements I wanted. And I’ve been iterating on this specific design ever since. I wish I had the hundreds of iterations saved but I don’t.

Here is what the most recent iteration looks like with goal buttons that are easier to determine your progress and other tweaks to make the UI more consistent.

This is the design for this view I’ve settled with for now. I have plans to iterate on this current design for some time before, perhaps, taking a whole new swing at it. Perhaps my skills will grow to the point that I feel confident going back to Kyle’s low poly idea. But, I’m pleased with how it has come along so far.

Attending October’s NEPA.js meet up

On Tuesday, October 10 I attended October’s NEPA.js meet up. John George of NEPA Web Solutions was this month’s presenter and his topic was Bitcoin and the Blockchain: Democratizing How We Exchange Value.

I believe all members of NEPA.js would agree, John’s presentation was arguably the best presentation the meet up group has had to-date. Though the Blockchain can seem a complex topic, John did an excellent job describing how it worked, where it is currently being used, and its future potential. Though the meet up was relatively well attended, I left wishing that so many more people had heard his presentation.

To further the lesson beyond the walls of the Scranton Enterprise Center, John also gave each attendee a gift in the form of a wallet containing a single bit of BTC. He also incentivized attendees to claim that bit for themselves by awarding the first few that did so with $50USD in BTC. Those that did it were rewarded indeed since the value of BTC has jumped to new record highs this month. Those that didn’t claim their bit may be kicking themselves for dragging their feet.

John will likely do this presentation again, in some form, under the NEPA Tech banner. Meet up’s like October’s are what is spurring the group to expand the group into a more general direction. This particular presentation had nothing to do with JavaScript – as the name NEPA.js would have you believe – and so we want to make sure each meet up is approachable by all that would be interested. You may remember me saying this over the last few months, and even in January I spelled it out specifically, but now there has been positive steps towards this happening. We’ll have more to announce in the near future.

Thanks to John for the amazing presentation, and for the bitcoin, and to the attendees for the active discussion.

Side note: My apologies for a terrible pano photo. I’ll try to do better next time.

Developers, Let me tell you about Microsoft (audio)

I’ve been writing about Microsoft’s moves for the last three years. This week everything has come together and I’ve been writing my first multi-platform application using C# and Visual Studio. In this long rant I go on and on about how Microsoft needs to spread the word about what they are up to.

Links for this bit:

Download.

My tips for new iOS 11 upgraders

I’ve been using the iOS 11 public betas on my iPhone and iPad for several releases and I think it is one of the most important updates to iOS. It brings lifesaving features to the iPhone and powerful features to the iPad.

Tomorrow iOs 11 is being released to the public, I thought I’d jot down a few things that I believe people should do on the day they upgrade, so that they don’t just move on with their busy lives and forget.

  • Turn on automatic Driving Mode detection. This setting could save your life and those of others. You have no excuse good enough to justify being able to text while you drive. iOS 11 does a good job of detecting when you are driving and turns off all notifications. Almost immediately when you exit your vehicle at your destination your messages are waiting for you. I love this setting. Settings > Do Not Disturb > Do Not Disturb While Driving.
  • Set up Driving Mode auto-replies. Optionally, you can set iOS 11 to automatically reply to certain people with messages that you’re driving. Or, you can keep this feature off and people will simply believe you have a life and cannot respond to every text message within 15 seconds of receiving one. Settings > Do Not Disturb > Auto-Reply To.
  • Customize Control Center. The control center (the screen you get when you flick up from the button of the screen, or from the top-right on the iPhone X) is very different than iOS 10. You can now add or remove buttons from it, and even customize their position on the screen. I’ve chosen to have Camera, Notes, and Voice Memos easily accessible in the bottom-right of the Control Center. I love it. Settings > Control Center > Customize Controls.
  • Identify faces in group photos. For those of you without a Mac, you’ve never had facial detection and naming capabilities for your photos. Now you can put a name to a face in iOS 11 and when your device is locked and plugged in it will rummage through your photos for you and find the vast majority of the other photos with that person in them. I’ve found that using large group photos is the quickest way to finding the most people. So, start off finding a few dozen group photos, naming everyone in them, and then let iOS 11 go to work at night. It is surprisingly good and getting better with every release. Photos > Find a Group Photo > Swipe Up > Click on person under People > Tap “Add Name” (repeat for all people in the photo).
  • On iPad: Customize your Dock. You can have up to 15 apps in your Dock on iPad. You can also add more by adding folders of apps. There is also an area on the right side of the dock that can show recent apps. Turn on Recent Apps in Settings > General. Otherwise, drag your favorite apps into the Dock.
  • On iPad: Practice multi-tasking, split-screen, and drag-and-drop gestures. iOS 10 has had split-screen features for iPad since it was released and I still see many iPad users that do not take advantage of them. iOS 11 makes these features even more powerful. Unless you make these part of your muscle memory by practicing them, you might be under-utilizing the power of your device. Watch this video on YouTube to see how best to open multiple apps, drag-and-drop files, and more.
  • Try out Notes’ new features. Notes has some new features that you will definitely find useful but you need to know they are there. Try some of the following:
    • If you have an iPad Pro with Apple Pencil, try tapping your Pencil on the lock screen. This results in a new note. Pretty slick.
    • Try the document scanner. iOS 11’s ARKit features allow for a pretty practical use of this technology in scanning a document and being able to sign it with ease. It is remarkably good. Put a document on a table, open Notes, in a new Note hit the + symbol, select Scan Documents. Prepare to be wowed. I wish this feature were part of the camera somehow or its own mode from Control Center. Again, here is a good video showing how this works.

By doing the above you may just save a life. But, also you’ll get far more use out of the device you already own and take full advantage of this monumental release of iOS.

If you have any others, feel free to leave them in the comment section below.

Attending September’s NEPA.js meetup

On September 12th, NEPA.js held its September meetup. Anthony Altieri presented on beacons – the typically small Bluetooth devices that “chirp” some very basic information multiple times per second allowing app developers to understand the proximity of a user. This allows for things like understanding where a shopper is in a retail space.

His overview of the devices, the spec, some of the software, and the differences between iOS and Android, and iBeacon and Eddystone – was a really nice introduction into the space. He did a great job.

I learned a lot during his presentation. Thanks to him for putting it together.

If you haven’t yet been to a NEPA.js and you live in our area – I implore you to check one out. It is consistently attended, always fun, and isn’t always focused solely on JavaScript. But even if it was, it is worth your time.

A unique color for every address in the world

A recent, yet-to-be-announced client project had me designing a mobile app interface that dealt a lot with showing locations and events that are happening at certain locations (how is that for vague? sorry).

While I utilized the brand’s colors to represent certain sections of the app I wanted the app to have tons of colors in order to portray a sense of fun throughout the app. But how could I incorporate pinks and yellows and bright greens without the overall brand disappearing?

After toying with a few design ideas I had an idea to create a unique color for every address in the world. This would result in two benefits; first, each location was then branded as a color, and second, every user would see that location as the same color. If I were a user of the app here in the US and I flew to Spain and looked at a location for an event  there, I would see the same exact colors representing that address as the person that lived in Spain and created that event.

Since I wasn’t to be the developer of the mobile application I wanted to avoid the possible pushback this idea might receive from that team. I didn’t want to add burden to the other people on the project by showing a design mockup and a set of requirements and then walking away. I wanted it to have zero overhead for the developers.

One of the solutions I discarded was generating a random color each time an event location was added to the service and then store the color for that address in a database. While this solution is relatively simple to implement it was no good. It adds more work for the developers and they have to maintain the datastore indefinitely. Several other ideas with the same caveats came to mind and I quickly tossed them into the bin.

Once I eliminated all of the ways I didn’t want to solve this problem – the solution came pretty quickly.

Since every address is already unique, I just needed to find a way to represent an address that could be turned into a color. In other words, I wanted the address itself to represent a unique color. And I wanted to do it in realtime as the application’s UI loaded.

So I jumped into JavaScript and began working it out. Here is what I settled on:

This solution allows for just over 16.5 million colors. Far more than this app will likely require during its lifespan.

Here is a demo of the process and if you view the source you can see the code at work. It is fairly simple to follow.

Oh, there was an issue that I ran into with this solution that was fun to solve. If the background color that was generated was too dark the text became hard to read. So digging around I found a way to determine the luminosity of the background color and thus change the text to something a bit lighter in those instances. That too is shown in the demo.

I was then able to repurpose this demo code and give production-ready code to the developer that is going to ship in the app. When that ships I’ll write more about it.

Colin Walker: “Should replies be posts?”

Colin Walker, in a post on whether or not replies to other posts (or, comments) should be their own posts:

There has to be a line, a point where a comment is just that and not a reply. It’s a question of semantics but not everyone’s answer to “what is a comment and where does it belong?” will be the same.

I struggle with this a lot.

It is likely the point I should have made in my post regarding Micro.blog becoming a commenting service (and the fact that I don’t like that). I don’t want to reply on my blog to every reply to my posts on M.b because then I would have dozens and dozens of posts on my blog that would be very tough for readers to follow contextually. I believe the commenting mechanism that has been around for decades, even un-threaded, is far more useful than dozens of desperate posts stitched together loosely with a link that says “in reply to”.

Webmention attempts to bridge that gap between post and reply but that also is tough to follow along if the thread gets unwieldy.

However, I also don’t want to reply to every reply on my posts directly on M.b either (though, I do from time-to-time) as that isn’t much better than using any other silo like Twitter or Facebook. Should M.b go away, all of those conversations would be lost.

This isn’t a new issue nor is it exclusive to M.b. If I replied on my own blog to other people’s posts on their own blogs (like I am in this post to Colin Walker’s blog) then one side of the conversation could disappear at any time. I can only control my side of the equation. But at least if I have my own blog I have control of that one side.

I think it is good that these topics are being discussed again. The same debates have been swirling since blogging began, they swelled again when the indieweb movement began to take shape, and I think they are happening again as a result of M.b’s growing community. I do not believe there is one single answer to many them. You have to do what is right and sustainable for you.

For now, here are my personal rules for replying to posts. These will most definitely change over time.

  • If I want to say a quick “congrats” or “excellent post” or something of that nature I will leave a reply directly on their blog. If they do not have commenting turned on I will attempt to email. If they do not have email publicly available I’ll say nothing at all.
  • If I have something substantive to add to the conversation, or if I would like my “followers” to see the post I will quote the post on my blog with my additions to the conversation. Like this post.
  • If I simply want to direct people to the content I will use my new repost tag that I’ve been experimenting with. I’ve seen others use the “a post I liked” type post. That could work too.
  • If people reply using M.b, Twitter, or Facebook I will not reply on those services*. But I may reply on my own blog.
  • If I would like to keep my reply private I will attempt to email.

As an aside: I know some of you do not want to leave a public comment. I love getting reader emails. I get a fair number of them. And some of them have been excellent conversations. So please don’t hesitate.

* I no longer have a Twitter or Facebook account. I do have a M.b account but I’m beginning to wonder if I need one as I have my own fully functional weblog. If I didn’t and I wanted a microblog and didn’t want to use Twitter, I could see having an account. If I wanted a more fully featured blog I still believe WordPress is the best tool for that. Also, I’m sure as the M.b community grows it could mean that my content would be discovered by more people. I think M.b may end up being a thriving, well run, community and service. It is why I backed Manton’s efforts via Kickstarter. But, if I have my own blog, and if I really don’t care much about my content being discovered, then I see little reason to syndicate to it. For the time being I’m still going to as I want to see how the service matures.

Presenting at the August 2017 Lehigh Valley Tech Meetup

The Lehigh Valley Tech Meetup is an excellent community in the Lehigh Valley that meets monthly at the Ben Franklin Technology Partners incubator within the Lehigh University Mountaintop campus. The community around the meetup is excellent and the building is amazing*.

While the tail-end of my presentation walked through my experience building my first iOS app Summit, the majority of my presentation was focused on helping early stage companies think about their go to market strategies.

I’m currently advising several companies, a few of which are businesses built around mobile apps, and have heard about 11 other start-up pitches this year so far. And during that time I’ve noticed a trend. Entrepreneurs that are attempting to build a business around an app sometimes underestimate the amount of thought that should go into the marketing and sales strategy for the app. It is as if some feel that apps are less thought and work than products that you can touch. So during my presentation at LVTech I hoped to convey that the same “boring” (yet, tried and true) business practices that apply to products also apply to software.

A few questions I urged those thinking about building a business around an app were:

  • Does your idea service a large enough segment of the market? We hear the “scratch your own itch” mantra a lot. However, it won’t always lead to finding hundreds, thousands, or tens of thousands of customers.
  • How will you reach those customers?
  • Are there ways to expand your idea into other products or services that can be sold to the same segment?
  • How will you sell or package your idea?
  • What will the price be? (free, one-time payment, subscription, service contracts)
  • What channels can you leverage to sell your idea? (App Store, retail, online, conferences, distributorships, via a sales force)

By considering these, and may other questions, you can determine if your idea has enough layers to support an entire business or if you just have an app idea**.

I also briefly discussed three misconceptions I’ve been seeing over the last year dealing with very early stage start-ups. These misconceptions were:

  • Press-based launch strategies: some thing that by being covered by press will be enough to get them to profitability. They have no other strategy. On the contrary, getting press coverage early on will give you very muddy analytics which will make decision marking very difficult. Very seldom are the tech audience your real customers.
  • How long until profitablilty: More and more entrepreneurs begin with the plan of losing money for 3 or more years. I believe this stems from press coverage of other companies getting large rounds of funding. Most businesses should strive for profitability within the first quarter or year of business.
  • ”I’m not technical, I need a technical co-founder”: Don’t be this person. Anyone can learn to code. Geeks are not smarter than you. They’re just interested and relentless. Be the same.

We then did about 10 minutes or so of questions and answers. The questions I got were really great and I appreciate all those in attendance helping me with the answers to the questions I didn’t have much experience in.

Thanks to Tim Lytle for the invitation to speak and to Ben Franklin Technology Partners for the continued support.

* I worked in this same building for years while at Viddler. But when I worked there the back half of the building didn’t exist. In fact, Viddler started in Jordan Hall – the building just beside the new building. And now, they are extending it even further. The building is an amazing place to work and have a meetup of this kind. I’m jealous that our incubator in Scranton feels so dated when compared to this building. Especially comparing the meeting spaces.

** It it totally fine to “just have an app idea”. I do. And I’m loving working on it. But it is also good to have the proper perspective about your app idea.

Summit – The Adventurous Step Counter

This evening, at a presentation at the Lehigh Valley Tech Meetup, I’m opening up public beta access to my new iOS app, Summit – The Adventurous Step Counter.

I’ve stitched together a temporary web site for the app as well as a mailing list that will allow you to get access to the final few beta builds prior to public release. If you have an iPhone please consider signing up and giving it a spin. I’d be very grateful for your feedback.

Thanks to the 13 private beta testers who have already tested the app and provided feedback. You can expect a brand-new build of the app coming in September.

What is Summit?

Summit is a free, iOS-only app that uses your step count to virtually hike up tall peaks like Mount Everest in Nepal, learn about amazing landmarks like Diamond Head in Oahu, and even take a leisurely stroll down famous streets like Lombard Street in San Francisco. As you make progress on your journey you’re provided new information at each goal.

At the time of public release there will be 5 summits and new summits will be added each month thereafter.

Here are some screenshots of the app as it is currently:

When I started on Summit I did not know how to develop an iOS app. It has been really fun to learn Swift, Xcode, iTunes Connect and Test Flight, and the myriad other things I was able to learn in order to get this app as far as I have.

I still have a bit of work to do, but I’d love your feedback along the way as I finish the app up for release.

My personal blogging tips

I’ve been writing things down on my own blog for a few decades. I wish more people did too. If you’d like to have a personal blog but struggle finding things to write about, here are a few tips that may help.

  • Don’t post about what you will do, post about what you’ve already done – In other words, I try to avoid the “I should blog more” posts and just get on with blogging more. Also, I like posting photos and status messages sometime after they’ve happened.
  • Find a theme – Niche blogs do extremely well. So stay on topic. Personal blogs do less well but they should still have a theme and that theme should be you.
  • Create reasons to post – My What I saw series and observations series give me a reason to write. Should I feel writer’s block I can fall back to one of the series.
  • Have a schedule – I try to post one or two posts per day prior to 9am. Some are scheduled in advance some aren’t. Everything else that happens is completely random.
  • Be totally fine with missing the schedule – Sometimes I don’t blog for a few days or weeks due to time off away from the computer or just being focused on something else. And I’m totally ok with that.
  • Don’t post test posts – Create a staging or a local development environment to test your site’s features. It is really easy to do.
  • Try not to care about stats – Stats are useful for a number of reasons but obsessing over them won’t help you at all. Check them once a month to see how you’re doing.
  • Create an inspiration list – In your notebook or notes app write down some topics you’d like to write about someday. Make it long. Like, 50 items. Don’t worry too much about what should be on it just start writing the list down. When you can’t think of anything to write about look at that list and simply pick any one at all and check it off.
  • Subscribe to a bunch of blogs that interest you – More than likely the conversations started by others will give you more than enough to write about.
  • Perfect is the enemy of good – Just hit publish.
  • Have fun! – I’ve thoroughly enjoyed blogging all these years and I don’t imagine I’ll be stopping any time soon.

If you have a neglected blog or are just starting one – jump in! Oh, and don’t forget to email me the URL.