I'm opening my Pivotal Tracker project from 2011... and I'm surprised at how good the UX is/was!!! Visually it looks old, but the UX I think is great:

Simplicity is reinforced with a great information density: lots, but not overwhelming. Current design trends make information density super low, forcing you to scroll a lot and spending much more energy/time just to be able to look at things.

When you need to "open" an item, you remain in the same screen (no modal, no context change): metadata, description, conversation. Nothing more!

In Linear I'm totally lost with projects, cycles, views, projects...

I'm stuck with Github Issues/Projects, but I miss Pivotal simplicity!!

I've just exported a 10MB Pivotal CSV...

When providing infraestructure for clients, we ended up writing the Ansible, and then docs describing what we had done. We created this tool to generate documentation automatically from magic comments we include in Ansible. This way, we automate things and be sure everything is up to date, saving lots of time of writing.

Any major differences related to SQLPro Studio? https://www.sqlprostudio.com (apart from access to some systems, and price, but since I consume it via Setapp...).

And so: Plans to make it available on Setapp?

I run SQLPro Studio at work. Just downloaded TablePlus to play around. The big difference is GUI performance. With a 100k row sample set SQLPro Studio UI gets laggy. TablePlus runs it smooth.

TP also has more data display options.

How much have you spend on Mixpanel??? ;)

How did you get to insights/assumptions like "If people don’t do [action] during their first 7 minutes in their first session, they will not come back"?

Thanks for the question furilo.

We run behavioral cohorts. We do cohorts over everything, every action people do, every screen they visit, every piece of value they receive. We also know when those actions take place (first 5 minutes, first hour, day, etc).

With the above, we've learnt what actions have the strongest retention. Now we need to look at the duration of the first session, which we have. We know that if we dont convert people during their first session, they is no coming back - no push or email or anything, will bring them back.

Once we know what the lever of retention is/are, and much time we have to convert, we run user tests with different types of users (converted, non-converted, people who've abandoned the app, people who dont know the app), and observe how they discover the lever, how they describe it, how they use it. This is gold, and helps us iterate.

Which action has the strongest retention in a fashion app like yours?

The Social|Promotions|Notifications|Forums tabs (and its automatic classification) is something I can't seem to live without. There is a way to replicate that (automatically in Mailspring). I think this is my main and only blocker to think on a permanent move! Congratulations on the work.

At least they are Irish...

A great explanation of a fairly complex issue. Amazing tha EU authorities are imposing such a burden for small companies when what they are supposed to do is fight tax evasion by multinational gigantic entities.

Thanks, Furilo! Yes, this is a big mess for small businesses. And it affects not only to European companies but to any business in the world that sells to European consumers.

Yes, in the same way other hundreds of factors will determine the outcome of a startup

Propose your favourite datasets!

What you will be going through?

I haven't put it all together yet, but I have given a number of workshops so will draw a lot of material from things I done in the past. I will probably cover the basics of mapping online, creating your first points map, styling points, creating multiple layer maps, and maybe a bit of temporal mapping. Nothing final yet!