Efficient but not necessarily better. When I'm solo developing I go back later and I made some questionable decisions a team member would have identified.
My bank sometimes requires me to "fax" documents to them using a phone number. I download their electronic documents, upload them to my esigning programing, esign them, then e-fax them using the esigning program to their fax "number". I'm sure on their end, they download the electronic "fax" and put it directly into their document system. There is no paper at any point in this process.
I think one thing that's missing from this article is what engineers at higher levels of IC status (up to VP) do. When a Sr. Engineer is choosing between a Manager and a "Principal Engineer" type role, I have to remind them that PEs also don't do much depth coding. They write proposals, discuss architecture, sit in meetings. Ultimately, the same mechanisms that Managers use.
There's certainly SOME PEs that go deep in some areas but the majority I've worked with are broad owners of technology in large organizations. The difference between the two roles often has to do with what balance of time you want to spend influencing others for broad goals vs. building up jr. folks to accomplish your team's goal.
In either case your authority is derived from whether people "under" you want to work with you. People who can't get a set of people to go a certain direction won't last long in either role.
Fire TV also has cross-service search which I find good. Roku has a more streamlined clickthrough interface but Fire TV generally shows me where something is available even if it takes a few more clicks to get there.