Every few months, while pulling out of a parking spot, my car will just SLAM on the breaks violently, sometimes when I'm in reverse and sometimes when I'm inching forward. Even at low speeds it's super unsettling.
1,251 karma · joined March 23, 2009
Former: New Relic, BrowserMob, Selenium, Java open source.
Every few months, while pulling out of a parking spot, my car will just SLAM on the breaks violently, sometimes when I'm in reverse and sometimes when I'm inching forward. Even at low speeds it's super unsettling.
In their case, they went with a "pageToken" variable which is basically a cursor.
The API has been around for years.
My own personal experience: I have a calendar assistant startup (http://reclaim.ai if you're curious) that does a bunch of awesome things. And we designed it to work where you already are -- namely in Google Calendar.
But a lot of potential investors, for example, question our definition of "active user" when we tell them we consider the customer getting value if we blocked out and defended time for their lunch as their schedule filled up.
Conventional wisdom is that the user isn't getting value unless they are coming back to your UI and getting your notifications etc. But that's just not the case for us: we helped our customer manage their time better without ever requiring them to come back into our app.
Isn't that like... the best possible thing? Solving a problem with the least amount of friction? It's working for us and fortunately we found investors who agree, but there are a lot of people out there that think about "engagement" in fairly simplistic terms that I think holds back our industry and also hurts the customers.
I wouldn't put them in the Dropbox bucket.
Also, I think the value Tailscale provides is fairly unique and far from obviously a platform feature like file storage and perhaps even password management.
Fun little thing we did with it: nobody can access the prod network without requesting access via a Slack bot (powered by https://indent.com/). So somebody requests access, another authorized person approves it, and the Tailscale ACLs are updated for X minutes and then reset.
Access to secure environments is super low friction but more secure (with fantastic audit trails) than ever.
Funny enough: quite a few Zapier employees use us to do calendar automation.
IMO, the opportunity is "and" not "or". Zapier is great (I use it too!) for so many use cases, but sometimes the use case is complex enough and the opportunity large enough that dedicated solutions emerge.
So while some value may strip away from Zapier via dedicated solutions like Reclaim, I think Zapier will also continue to add value by educating more of the world, improving their UX, and connecting with more services.
For the folks looking for coding-style solutions, I'm also big fan of https://pipedream.com/. Check it out!
I wish someone did an article on that sound too!
Reclaim.ai (https://reclaim.ai) is an intelligent operating system for the calendar, helping to automate and defend the schedules of busy product leaders, engineers, managers and their teams. Thousands of busy professionals rely on Reclaim every day to manage their calendars.
We offer full health, dental, and vision benefits to all employees as well as a competitive salary, a generous equity package, and a 401k program. Flexible hours, remote-first, awesome (and scrappy) team.
Reclaim is backed by some of the top venture firms in the US, and you’ll be on the ground floor of a fast-growing company with a big mission.
Full-Stack Engineer: https://reclaim.ai/careers/full-stack-engineer
I truly can’t tell what this is. I also had never heard of Deno before so that context didn’t help.
At first glance it seemed to be a next gen way to build interactive UIs in the Slack app, compared to the callback nature we built our app with.
But digging a bit deeper, it seems to be more narrowly focused on their “workflows” feature, which is one of the few things in their platform we haven’t used.
I’d love to learn more, but also if anyone from Slack is reading: your platform is pretty complex and announcements like this don’t help folks like me.
https://developers.google.com/calendar/api/v3/reference/even...
But often a problem is that people in one organization can really only check the free/busy time for one of your calendars (the primary calendar associated with that org), and thus end up booking you when you're busy on one of those other calendars.
I'm guessing this is the root problem you're getting at with your comment.
Until the platforms themselves (ie: Office and Google) offer up a native way to indicate that multiple calendars represent your busy time, you're kinda stuck with this problem without employing a third party service.
The good news is there is a solution to this problem -- my own startup[1] has a feature[2] that watches source calendars and creates blocks of time on a target calendar. It offers several different privacy options, such as making the block simply say "Personal Commitment" or "busy" or having it carry through all the event details (but not attendees because that would create a mess).
[1] https://reclaim.ai/ [2] https://reclaim.ai/features/calendar-sync
One way we (somewhat) solve for your desire today is that we schedule out all the stuff but then make it fairly easy to decide what to do just-in-time without wrecking the whole schedule. It’s not perfect but it’s been working for some of us.
It’s something that has frustrated me, as a manager, when fellow managers said it to me. I feel like it gives permission to managers to detach themselves from the reality of their organization.
The trick is to know WHEN to dive deep, because you are right that managers also have to maintain a broad perspective.
But being able to sniff out problems and then dive into them has always been the hallmark of a great manager/executive, at least in my own experiences.
https://twitter.com/sadbangs/status/1304685594430377985?s=21
> Leaders operate at all levels, stay connected to the details, audit frequently, and are skeptical when metrics and anecdote differ. No task is beneath them.
IMO this particular trait correlates well with a need for less process / project management software. I really believe if more people did this companies would be better off.
Note: this isn’t the same thing as micromanaging but I understand why some people think it is.