Besides the title, this might work for their specific case, but I don't see it working in general. From my experience, lots of emails are fake. Either gibberish, or not the user's. You need an actual email to send communications and somewhat reduce spam and abuse. Postponing confirmation doesn't help with that.
The author fails to even mention the actual solution to avoiding email confirmation and reducing onboarding steps: social login.
With social login, users start using the app immediately, and site owners have a validated email (and optionally a lot more). If your app is targeted to developers, use GitHub login. Otherwise Facebook, Google, Twitter or similar, and you'll have a 90% coverage. Some people are paranoid about giving access (although IMO is safer), so also support signing up via email, but at that point it would be the "user's fault" if extra steps are required.