voxmatt

Same

lol!

LOL

This is lovely. The whole thing.

I may have to revive my own blog now...

Plug for https://www.getclockwise.com/

Cal's writing has been a key source of inspiration for what we build.

I've tried seemingly every mail client on the planet, and Shortwave is the one that stuck. If you have a gmail account — especially a work account — and feel like you're drowning in crap email, Shortwave can move you through it like a knife through warm butter.

Hey HN, we analyzed more than 1.5M meetings, 80k engineers, and 5k companies to create the 2022 Engineering Meeting Benchmark Report. Some good stuff in here about how engineers and eng managers use their time.

This looks super promising. It's impressive how much has been built out already and I'm pumped to see where this goes.

I've been a user of shortwave for a couple months now, and I emphatically recommend giving it a try. I'm a very persnickety software snob and tried almost every email client without it sticking. I'm sure this won't be for everyone, but if you've struggled to get to inbox zero, I recommend giving it a try.

The channels are a cool addition, but most of the value for me is just the ease with which I can process volumes of email.

CEO of Clockwise here, so I'm biased! This game was built by our designers on a Hack Day. So, so fun and such a cool demonstration of how difficult internal scheduling can be.

^^^ this.

As others have pointed out (and some disagreed with), Apple has capital, supply-chain expertise, patience, and a dogmatic focus on the whole experience. In a realm where technology is increasingly a driver of the experience (no pun intended), cars start to make some sense.

But the battery claim... I just can't imagine a universe where Tesla isn't aware of the same hard-science. I'd love to be surprised though.

We built a tool around this essay to help better coordinate across maker and manager time: https://www.getclockwise.com/

At the core, it defragments your calendar, but it also provides a suite of utilities to help you better organize your time (color coding, Slack status, personal calendar sync, auto travel time, etc.). PG's essay has been a consistent point of inspiration for us.

Engineering teams at teams from 5 – 1000 use us. Give it a try and let me know what you think.

Thanks! We built it because we had the problem!

Great article. For the tasks of getting blocks to focus and grouping meeting together, we've created a powerful application that can help automate away some of the drudgery. https://www.getclockwise.com/product

Hello HN!

I'm a co-founder and CEO of Clockwise, a tool that helps teams find more time for focused work by moving meetings to the best time for everyone, automatically. One of the canonical pieces of writing on this subject is Y-Combinator's very own, Paul Graham. [Maker's Schedule, Manager's Schedule](http://www.paulgraham.com/makersschedule.html) — Clockwise helps broker between these two types of schedules.

Clockwise is completely free while in beta; we'd love for you to give it a try and let us know what you think. Given that this is still a beta release, there are a few requirements:

- Chrome only, for now

- G Suite (business) calendar accounts only, for now

Ha, yes; I've been there many times before!

Rob, I was so sick of this that I started a company around it! We're still early, but what Clockwise does is pretty magical: we rearrange meetings to protect flow state. If you ever want to share feedback or give product ideas, feel free to reach out: matt [] getclockwise.com

https://www.getclockwise.com/product

We'll get there! Had to start somewhere, and Google Cal is a little more common among early-adopters.

We started Clockwise to address this problem, and this PG article was a major point of inspiration. (Looking through the comments, that seems to be a trend!)

We just launched a private beta of Clockwise for Chrome, which helps automatically put more maker time on your team's calendar. It's free and we'd love everyone's thoughts. Feel free to send me an email if you'd like to hop the line: matt@getclockwise.com

https://www.getclockwise.com/product

I couldn't agree more. I'm originally from the Twin Cities and we solved (parts of this) problem years ago with a regional government called the Metropolitan Council. When you have a metropolitan area that spans multiple local governments, coordinating efforts around transportation, development, and environment is critical. And coordination is difficult without some sort of central authority. https://en.wikipedia.org/wiki/Metropolitan_Council

Because I use Typescript! Joking aside though (although, let's be honest, there is some straight-up selfishness: I use TS and if Facebook did, my life would be easier), I think adding types to Javascript is a huge win no matter how its accomplished and it just so happens that TS seems to be gaining more community support than Flow. Flow's support is almost exclusively from the React community because of Facebook. If Facebook would switch to TS, the whole community could coalesce around one standard. That would have huge benefits.

Awesome!

Follow-up (didn't see the updated docs). Looks like there is some support for client-side state through "Client Schema Extensions" — excited to play with this.

I do also hope that this iteration brings with it better docs — that's the one area where I've looked over at Apollo longingly. On many occasions I've discovered unknown patterns in stack overflow answers that aren't documented anywhere (credit where it's due: the answers are often by members of the Relay team).

And one final tangent: the day when Facebook gives up on flow and adopts Typescript will be a glorious, glorious day.

More here: https://facebook.github.io/relay/docs/new-in-relay-modern.ht...

The learning curve for Apollo is a bit shallower for two reasons: (1) they have GraphQL libraries that allow you to implement a Relay-like client on top of an existing GraphQL end point (Relay requires some custom fields); and (2) better documentation.

We went with Relay, however, because it is, in my experience, more robust and more polished. The way that Relay handles fragment composition and defers component rendering, along with data masking, is much nicer and more... holistically considered(again, in my opinion). Using Apollo can feel a bit like patchwork sometimes.

Plus, ultimately, Relay is backed by Facebook and used in Facebook applications, in production, so it's not going anywhere.

Exciting to see! I've been waiting on this since we decided to use Relay for our application about 6 months ago. Relay is amazing but quite an investment (especially mutations).

I'm a bit worried, however, that Relay Modern has focused a bit too much on the internal needs of a massive application like Facebook at the expense of fleshing out some of the rough spots of working with Relay.

Simpler, more explicit mutations is a wonderful improvement, as is more granular control over the cache, but there's no mention of subscriptions or client-side state control (using Redux on top of Relay is... doable, but not as elegant as one might hope for).

That all said, this is an impressive release and congratulations to the team. We're committed to Relay and hope this release grows the community.

The behavior of some of the author's colleagues is incredibly embarrassing, and the behavior of some of the author's managers is just reprehensible. I hope that the more reprehensible behavior is simply an indicator of the problems of unexperienced founders/leaders. I know the nature of these anecdotes is not uncommon, but there does seem to be a clear line between the discomfort associated with office-sponsored drinking events and outright harassment.

The larger discussion has merits, but I do think, for better or worse, startup culture is just a reflection of our alcohol focused social culture (and in full disclosure, I enjoy it). Startups are different in that they often blur the line between professional and social. This can certainly be problematic, but it's also one of the most significant reasons that I enjoy working at startups much, much more than traditional businesses.

The point is well taken, but sitting on my couch in PJs everyday would definitely make me very, very depressed; economic freedom or not. I'm very sincerely happy that this guy found his way, but I can confidently say that this is not for me.

Palo Alto, CA / Bay Area: On-site only.

RelateIQ: http://www.relateiq.com

-------

We're hiring for everything: Engineers (front end, back end, systems, ops, everything), Marketing, Product, Sales

I'm a front end engineer here and I can honestly say that it's the best job I've ever had. Great team, great internal culture, amazing trajectory (we're growing like crazy), and fun.

Our current stack is mostly Java with Cassandra, Mongo, and Postgres. We work a lot with Hadoop, Kafka and Storm. (great post by one of our engineers on Docker/Mesos/Chef: http://blog.relateiq.com/mesos-docker-and-chef/)

Our front end is mostly Angular, and we are heavily invested in Docker for our infrastructure.

-------

We're located in downtown Palo Alto (1 block from CalTrain). We're about 75 people, with about half working in Eng and Product.

EMAIL: alexl@relateiq.com or message me!

I feel a bit bad being so superficial, as the app has real merits, but the design is really painful. The app icon is just awful and, unfortunately, it is only a hint of what's to come upon launching the app. I hope it's successful enough to allow Marco some funds to hire a designer.

There is