Menu

Colin Devroe

Reverse Engineer. Blogger.

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

Microsoft Office now shares a common codebase

Erik Schwiebert:

Mac Office 2016 version 16 is now live! For the first time in over 20 years, Office is again built out of one codebase for all platforms (Windows, Mac, iOS, Android)!

MSFT is dog fooding big time with this latest release of Mac Office. I’ve been enjoying my work within their frameworks and products that allow cross-platform mobile app development.

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.

Nintendo Labo

Nintendo:

Nintendo Labo combines the magic of Nintendo Switch with the fun of DIY creations.

I don’t play any games. I know, I’m boring. But I soaked up countless nights and weekends in my early 20s playing first-person shooters and I can’t get any of that time back. So I choose not to play any games. Which is why I don’t mention games on my blog often. But this set of cardboard extensions for the Switch look absolutely amazing.

The irony is, anyone could have made these for the Switch. And, likely, with this spark, more people will make their own.

The more I see of Switch the more I want to come out of retirement.

Fred Wilson on owning your content

Fred Wilson:

I would never outsource my content to some third party. I blog on my own domain using open source software (WordPress) that I run on a shared server that I can move if I want to. It is a bit of work to set this up but the benefits you get are enormous.

The above quote is coming from someone who was a major investor in, and active user of,  Twitter. You can have both. You can tweet and enjoy using Twitter. You don’t have to boycott it to own your own content.

Over the last few months I’ve found the right balance for myself. I’m not syndicating anywhere* but publishing on my blog. I tweet from time-to-time, I post some photos to Instagram and Facebook from time-to-time, but I do all of that manually. I do so full-well-knowing that any of that content can disappear at any time. And I’d totally fine with it if it did, because everything I want to last is here on cdevroe.com.

* All of my posts do end up on micro.blog but that service is simply ingesting my RSS/JSON feed. I do not have to do anything special for that to work. If Twitter, Facebook, or Instagram did that I’d likely turn that on there too. But I’m tired of trying to keep up with their platform changes to write my own plugins, or even use plugins to do so. So I choose to manually POSSE and keep my sanity.

Wallace.dog

Local friend Jeremy Brown has a cute animated comic that he publishes on Monday, Wednesday, and Friday. It is called Wallace.dog. If you follow him on Instagram you can see behind-the-scenes how much work it is — often starting long before sunrise.

I urge you to check it out.

Seth Godin on Google’s Promotions Inbox

Seth Godin, in an open letter to Google:

Imagine that your mailman takes all the magazines you subscribe to, mixes them in with the junk mail you never asked for, and dumps all of it in a second mailbox, one that you don’t see on your way into the house every day. And when you subscribe to new magazines, they instantly get mixed in as well.

I briefly turned on Google’s separate Inboxes feature a few weeks ago. I found it maddening and turned it off within a few days.

Micro Monday – January 15, 2018: Scott McNulty

My Micro Monday recommendation this week is Scott McNulty.

He’s blogging more, podcasting, sharing his reading reviews, and sharing his weight loss journey. Great inspiration on many levels.

Richard MacManus’s tech predictions

Richard MacManus attempts to predict some things for 2018:

We’ll finally get a killer app for AR in 2018. Maybe hope springs eternal, but I’d love to see an AR app with real utility – not just a game like Pokemon Go.

I suppose it matters how you define “killer app”. For me a killer app would be when “most” people begin to use AR somehow. And, if that is the definition then I would say AR already had multiple killer apps. Pokemon Go, Snapchat, Instagram, Google Maps, all of these are excellent uses of AR and hundreds of millions of people use them.

Mixed reality is tough to segment and define. When I talk about AR I think I’m mainly talking about moving our computing experience away from our screens and into the real world. I would love to have my workspace no longer be tied to my work office. To have any size screen I want, wherever I need it. As I’ve written, I don’t think that will happen for another 9 years. But perhaps that is a different form of AR and AR has already “made it”.

I wonder what MacManus’s definition of “killer app” is?

Android Excellence on Google Play

Kacey Fahey on the Android Developers Blog just sort of gave out some awards:

Every day developers around the world are hard at work creating high quality apps and games on Android. Striving to deliver amazing experiences for an ever growing diverse user base, we’ve seen a significant increase in the level of polish and quality of apps and games on Google Play.

The list is pretty good. I don’t play games so I wish more apps were listed.

Snapthread 1.5 Beta

Becky Hansmeyer:

I’m going to do something I’ve never done before: ask people to beta test my app! If you’re interested in being a part of my very first beta test, please either send an email to feedback@beckyhansmeyer.com or DM me on Twitter (@bhansmeyer). All I need to know is what email address you’d like me to send a TestFlight invite to.

If I were still on iOS I’d want to test this app.

Scott McNulty on making time to read

Scott McNulty gets asked about how he reads so many books every year. His answer?

You just have to make time for it. You know that time you spend doing something other than reading for pleasure? If you spent that time reading instead, you’d read more.

I get asked this same question about building apps, blogging, photographing, etc. Same answer. You will always make time for things you really care about.

Micro Monday – January 8, 2018: Mike Haynes

Micro.blog has a new thing where each Monday you recommend someone to follow and why. Here is Jean MacDonald, Community Manager at M.b:

We are inaugurating Micro Monday January 8. Inspired by Follow Friday, we want to encourage helpful recommendations rather than lists of accounts to follow. We suggest you make just one recommendation per week. Include a link to the account micro.blog/username to make it easy for people to click and follow, whether they see your recommendation on the Micro.blog timeline or on your blog. We highly recommend you give a short description of the reason for your recommendation. (Include the phrase Micro Monday and you’ll earn a special pin!)

Sounds like fun. Though I don’t like that we feel we have to link to the micro.blog URL*.

This week I’ll recommend Mike Haynes. Mike is active on M.b and is working on an Android client that I’m eager to try out. Here is his web site too.

* I don’t particularly like Micro Monday’s rule of sharing the micro.blog URL (instead of the user’s domain) since I think the entire purpose of Micro.blog is to promote the use of independent platforms. But I’ll follow the rules. I hope the rule shifts in the future to sharing each other’s domain name.

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.

 

 

Repost: Becky Hansmeyer re: app icons

👉 Becky Hansmeyer:

Xcode should, by default, generate app icons for all sizes from a single artwork file. That would eliminate such an obvious pain point for app developers and designers.

Repost: Stephen Pieper re: Indieweb plugins

👉 Stephen Pieper:

I went a bit crazy with Indieweb plugins and services to begin with. The fervour of the new follower. I’m cutting out the stuff I don’t need now or the the things that just don’t work the way I want them to. Manual seems best for some things.

Colin Walker’s tech predictions

Colin Walker answered the call. Interesting list. Here is just one:

Mark Zuckerberg reveals he has political ambitions after all. Not wanting to be criticised he “does a Trump” and supposedly signs over all control of Facebook while making a run for the White House.

I don’t think Zuckerberg will ever leave Facebook. Not even to be President.

But that’s the point of these lists. Let’s see what happens!

Noah Read’s tech predictions

Prompted somewhat by my technology prediction time capsule, Noah Read takes a stab at what he thinks we’ll see (or, won’t see) in 2018.

He has some interesting takes. Most of which I agree with.

I do not think I agree with this take, though:

AR will be a passing craze, while at the same time making certain niche use cases much better than they’ve ever been. I just hope those use cases are more useful than funny animated masks on social networks.

AR may indeed be a passing craze but I don’t think that will be determined within 2018. It will take much longer to know that. And I don’t think the use cases for AR will be niche. For instance, I do believe my future workspace will be “in AR” rather than VR. (Or, perhaps this is my own wishful thinking). And I think there are enough people like me that would want this to say it is larger than just a niche use.

Of course, maybe I’m wrong and Ready Player One will be the reality.

Regarding self-driving technology, though, Read says:

Problems of infrastructure, distance, regulation, public opinion, and human nature will infuriate utopians who would like a Jetson’s future today, but these are real issues that will slow adoption in the real world. It’s coming, but current estimates seem optimistic.

This I agree with. Obviously.

Many of us underestimate how long change happens. The change we want we want immediately.  Personally, I want self-driving to become mainstream yesterday. But I feel we’ve still got nearly a decade of manual cars and drivers to deal with before things take off.

More people should write down their predictions. And not just for 2018 but for the next 20 years. It is a fun mental exercise and I’m certain it will be fun to look back upon every few years.

To that end I randomly challenge Colin Walker, Matt MullenwegManton Reece, and Mike Haynes to jot down at least 5 predictions for the next 20 years.

The new Technorati

Glenn Rice:

My first impression is that micro.blog could be the new, simpler Technorati for the rising IndieWeb tide – a nice centralised way for people to discover each other’s posts and sites without losing the decentralised, own-your-data nature of the indieweb.

I have very fond memories of Technorati so I do not mind this comparison. Technorati helped expose people to the power of the indieweb at the time because it was a jumping off point to find some of the best content all over the web. It wasn’t a platform so much as a service. As Micro.blog grows, particularly out of the small blogger audience it currently has, it could fill this role very nicely – while at the same time being a solution for many to publish their own blogs.

/via Jonathan Lacour.

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.

 

 

Choosing without deciding

Seth Godin:

We can save a lot of time and effort by making our meaningless choices effortless. Pick the first one, or the one in alphabetical order or flip a coin. Merely have a rule and make the choice.

This point made by a recent post by the inimitable Seth Godin strikes the same chord as my SPARK Talk at this month’s NEPA Tech meet up.

I advise several companies and speak to dozens of entrepreneurs. Many of them make the same mistake – they give too much weight to some of their very early decisions and never getting started because they can’t decide.

I see it all the time. In many facets of business. Another way to phrase this situation is paralysis by analysis.

The example I used in my SPARk Talk was that of programmers that become dogmatic in their language or framework choice, or can’t decide at all which to use, or always want to jump to the latest buzz worthy trending language or framework for very early versions of their product. The result is that they never ship anything.

Choosing a language or framework is an important decision. But, not at the cost of starting. Just get started.

While we’re on this subject, let me be clear about how I would advise a company to make this choice. In many cases is doesn’t matter whatsoever what programming language or framework you decide to use for your app. At least not for the first few iterations of the product. In general, the customer will never know or care what you used to write the app. So, in this respect it doesn’t matter. However, if you’re going to maintain the code longterm, use a language or framework that makes you happy to type. If you’re going to hire a large team, use a language or framework that has the largest pool of talent to pull from. But please start!