Can't recommend Zero enough. It's a really thoughtful piece of software with great abstractions. As well as the obvious performance benefits arising from having data synced and available in the client, I've been blown away by how much it simplifies React code. With a sync engine in place, most client-side state seems to evaporate, you get to think synchronously in most component code, etc.
Hey, OP here. I’ve really enjoyed your work on AI agent definitions. So thank you for reading!
I don’t actually claim that ours is necessarily the correct answer for everyone – it’s our own. But I believe it is at least _an_ objective definition. Other definitions I’ve seen have been murky and subject to interpretation.
Ah, thanks for pointing that out! We've updated the docs to avoid referencing that deprecated repository.
FYI self-hosted is usually something that customers in highly regulated industries opt for – the vast majority of our customers are on our managed cloud.
But seriously, congrats on shipping, and for bringing some new ideas into the fold.
One point of clarification: Tines is certainly not only for the Fortune 10. We have a forever free, generous Community Edition [1] with tens of thousands of happy users, as well as a massively-discounted startup program [2] for early stage companies. Reliable workflow automation matters for teams of all sizes, and we're proud to welcome them all.
We hear this a lot, and it's something I'm personally interested in. There are also a few tradeoffs and downsides involved in building it… but it's something we’re actively considering.
We just shipped Groups. I'd love to hear what you think. We've been using it in our company for several months, and it's greatly improved our communication culture.
Finally, if you're hearing about Consider for the first time – it's also an email client you can adopt just for yourself (although it works even better when multiple folks on a team use together!). Overall, we've tried to design for focus and flow throughout, and almost all features apply to your own private mail just as much as shared/team-level stuff. See more at https://consider.co/.
First, it's easy to find history. With a Consider group, you can see all of the history of all groups you're in, right there in the email client. So – a new engineer, say, on their first day in the company, can browse engineering@. (And they can see all the conversations the team have pinned there, almost like a super lightweight wiki.)
Second, it's easy to browse groups you're _not_ a member of. So, that engineer can stop by design@, and take a sneak peak of what the design team are working on now and then, without having their inbox fill up with stuff they're not interested in.
Some companies (notably Stripe) have built cool internal tools to approximate these benefits on top of Gmail and Google Groups. With Consider + Groups, you get everything combined in one place by default.
Yes. Rails has by now certainly crossed into boring software territory – arguably a [positive thing](http://mcfunley.com/choose-boring-technology) anyway – but it remains an excellent choice coming into 2018:
- Out of the box, Rails has close to unbeatable developer ergonomics, tooling, stability, and ease of use
- Lots of high quality, large companies use it (GitHub, Shopify, Airbnb, Square, Twitch) and have by now figured out how to scale it, often sharing and open sourcing their efforts, e.g. https://github.com/Shopify/identity_cache
- If your product front end is simple, Turbolinks can be an excellent choice (find me a faster, more bug free product than Basecamp)
- If you prefer to use a more modern JavaScript solution on the front end like Ember or React, Rails API is a perfect fit
- The Ruby ecosystem and community are both very high quality
Intercom ● Onsite ● San Francisco ● Product Engineers
I’m looking for great software engineers who are highly opinionated about the products they work on.
Intercom [1] is growing exceptionally quickly [2], as we build out the customer communication platform. At the highest level, we’re trying to make Internet business authentic and personal for everyboddy.
I quoted Apple's Retina claim on the site: ‘The Retina display’s pixel density is so high, your eye is unable to distinguish individual pixels’. (They have many variations on this).
So for me a real retina display would make a single white pixel on black background invisible at normal viewing distances to a normal eye.
I love my retina displays, but Apple's marketing annoys me as I can still see pixellation at times. This is a quick game to see if you can dispute the marketing claim.
This doesn't seem to be about feminism specifically (although your classification of an equality movement as an infection would certainly demand extraordinary evidence).
It seems to be more about gender, and gender roles. There's a really big question here that I find interesting as a hacker: how much of what we call gender is biologically constructed, and how much is socially constructed? Obviously, say, having a penis is a direct function of biology, but what about something like girls' supposed preference for pink? This is almost certainly a social construct, and one that only arose in the early twentieth century [0]. And yet dressing little girls in pink has certainly influenced generations of us - do you know many guys who would be comfortable using a pink wallet?
The big question becomes important when we look at an issue like girls being the minority in engineering/technology/business leadership/etc: how much of this is due to some inherent biology, and how much is due to a lack of role models or social expectation for young girls to show interest in these areas?