(LINK) Exclusive: Automattic CEO Matt Mullenweg on what’s next for Tumblr – The Verge

I can’t think of a better home for Tumblr. Automattic has the cash, the network and clearly Matt knows what he is doing.

Yahoo should not have bought but that is all history at this point.

I never used it and always prefer proper blogging like WordPress but I think it is a useful platform. But mostly porn to some extent.

Exclusive: Automattic CEO Matt Mullenweg on what’s next for Tumblr – The Verge

Advertisements

(LINK) Principles of Shaping | SHAPE UP

Been reading the Basecamp SHAPE UP site in bits and pieces.

I love this section:

https://basecamp.com/shapeup/1.1-chapter-02#wireframes-are-too-concrete:

Wireframes are too concrete

When design leaders go straight to wireframes or high-fidelity mockups, they define too much detail too early. This leaves designers no room for creativity. One friend put it this way:

I’ll give a wireframe to my designer, and then I’m saying to her: “I know you’re looking at this, but that’s not what I want you to design. I want you to re-think it!” It’s hard to do that when you’re giving them this concrete thing.

Over-specifying the design also leads to estimation errors. Counterintuitive as it may seem, the more specific the work is, the harder it can be to estimate. That’s because making the interface just so can require solving hidden complexities and implementation details that weren’t visible in the mockup. When the scope isn’t variable, the team can’t reconsider a design decision that is turning out to cost more than it’s worth.

(LINK) “Prefer” Postmortem: 6 Lessons Learned From A Network Of Independent Professionals

“Prefer” Postmortem: 6 Lessons Learned From A Network Of Independent Professionals

Great post about a product that didn’t make it. Lots to grok in here.

Love this part:

You can’t obsess enough about the top-of-the-funnel.

The more time the Prefer team spent with different Soloists and Clients, the more we realized how many different value propositions there were for first-time users. We learned that some clients just wanted the ability to discover services, some Soloists only cared about referrals while others only sought a better way to serve existing clients, while other pairs of Soloists and Clients just valued things like easy billing and automatic notifications for appointments. With such variance of preferences, the “first mile” of the customer experience either didn’t evolve fast enough or failed to serve a broad enough set of users. This experience emboldened my observation that most product teams only spend the final mile of their experience building the product thinking about (and testing) the first mile of the customer’s experience using the product. It should often be the opposite.

Speaking of Scott – his book is a great read!

(LINK) Dark emerges from stealth with unique ‘deployless’ software model | TechCrunch

There is always the promise of a new way of building stuff.

I am always dubious of a new way that requires a new language.

I also wonder how tweakable it all is once launched – can the devops person adjust it at the GCP level or is a roundtrip needed to go from editor to launch?

Interesting times.

Dark emerges from stealth with unique ‘deployless’ software model | TechCrunch