lkozloff

It honestly disturbs me how true so many of the predictions from the Idiocracy have been.

Love this - I had a similar idea years ago, specifically for looking at long-text privacy policies and displaying the `diff`... but obviously never built it.

What you've done here is that and so much more. Congrats!

I rolled this out when it was "Facebook at Work" at an education non-profit I was working at in Cambodia. It was generally successful and useful for doing the type on internal storytelling we were trying to do. Particularly because teachers and staff didn't have, need or want Slack.

It was loads better than Google+, which we had tried before.

These days I suspect things like Slack started to take over here, but for that particular time and place it was a great fit.

Interesting - this was actually a feature that got me to convert. I have some slight annoyances with how it handles natural pauses as I collect my thoughts and speak, but overall it's been great.

I've had some interesting discussions and it's helped me structure some thoughts by asking questions and follow-ups, then summarizing our conversation... all while I'm on a walk.

One fun thing I did with my family was have it do an interactive adventure story starring us. We had an adventure, and then used the built in DALL-E to generate images of scenes from our adventure.

I love k9s and use it for most everything... but the unintended result is that I've lost my fluency in kubectl, which is occasionally a hinderance.

But maybe that's what you want from a tool - something so good it essentially replaces the previous way you were doing something?

I've found the act of prioritization to be one of the hardest practices to build. I know I should prioritize. I know it takes time to do it well... but if I spend just 10m doing this one thing I can get a nice dopamine hit for having accomplished... something.

One of the things that has helped me most recently is building out a better set of rules for my inbox that let me segment out unknown priorities from known priorities.

Previously, I'd get so many bids for time the act of even enumerating the tasks TO prioritize was too much and I'd end up in a push-workflow, rather than pulling tasks by their appropriate priority.

So, hopefully this is some encouragement for you to think about what's urgent/important in your inbox, what's unknown and needs triage, and what can be scheduled for later.

So happy to have this small mystery solved. I lived in SE Asia for years where we avoided the local tap water, including for ice at home.

My kids and I observed these ice spikes every morning when I took out the trays to for iced coffees, and I always wondered why I'd never seen them anywhere else in the world.

It's almost a nice retroactive confirmation that the water delivery service we relied on was selling distilled water as advertised!

Support Manager (and person who wrote that line) - it's certainly not meant to be dismissive or tongue in cheek. If you've got some suggested wording to help take away that feeling, I'm happy to submit (or merge) and MR to the blog post to make it feel less that way.

We actually do want (and care) about your feedback and wanted to provide a clear way to give that. In the past we've gotten support requests, tweets, comments on GitLab issues and a myriad of other creative ways of voicing thoughts, opinions and ideas.

My hope was to streamline feedback into a single place that GitLab support and our community teams are actively monitoring. There's been some helpful discussion there (and here) already.

I don't think you're wrong here. Remote itself does unlock advantages that aren't accessible to colocated companies (e.g. hiring anywhere), but one of the primary things that remote-practices unlock are surrounding communication.

Organizations approaching remote have a helpful speedbump that encourages them to take an intentional look at the way they disseminate information. Being fully remote is an accountability structure that helps ensure that everyone is following those practices.

There's nothing that would prevent a well-run colocated company from capturing those particular advantages, but such a company would probably slowly drift remote as companies like Buffer (and GitLab!) have as they grow and look for new talent.