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.

Comments URL: https://news.ycombinator.com/item?id=43560849

Points: 94

# Comments: 41

Comments URL: https://news.ycombinator.com/item?id=43343759

Points: 2

# Comments: 0

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.

We're flattered by the mention & imitation ;-)

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.

1: https://tines.com/community-edition

2: https://www.tines.com/pricing#startup-program

tl;dr – it's a way to build simple-but-slick web apps that are powered by API automation behind the scenes, without writing code.

No code? It's because our traditional users are technical-but-not-engineer types like Security Analysts and IT Managers. So this new way of building front-end experiences follows that lead. But as a more technical maker myself, I've been really surprised at how well this works and scales, and we’re seeing teams like Engineering and DevOps increasingly adopt also. I think maybe it's because us software people most intimately understand the long-term/hidden costs of code… maintaining, bug-fixing, deployment, etc.

Anyway, If you’d like to check it out…

1. there's a usable version of a demo app mid-way down the page above, and then clicking the "How was this built?" button shows you the equivalent of source-code, i.e. the visual automation underpinning everything.

2. we have a forever-free tier, which you can sign up for here and play around for real: https://www.tines.com/sign-up

I’d love to hear any and all feedback! We love a good dose of HN-style tough love, which we certainly received our fair share of last time we surfaced here :-) [2]

- Stephen

---

[1]: Tines – no code automation [2]: https://news.ycombinator.com/item?id=30249518

Comments URL: https://news.ycombinator.com/item?id=34536288

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=30735476

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=23872873

Points: 130

# Comments: 56

Comments URL: https://news.ycombinator.com/item?id=23231181

Points: 14

# Comments: 4

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.

Read a bit more about its origin here: https://medium.com/the-consider-blog/the-next-piece-of-the-p....

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/.

Happy to answer any questions.

Two main things I'd call out.

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.

Comments URL: https://news.ycombinator.com/item?id=19146849

Points: 8

# Comments: 0

- 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

Comments URL: https://news.ycombinator.com/item?id=15222809

Points: 58

# Comments: 17

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.

Email me directly at stephen@intercom.com and let’s chat.

[1] https://intercom.com [2] https://breakoutlist.com/

- Altoid identifies as Ross Ulbricht: https://bitcointalk.org/index.php?topic=47811.msg568744#msg5...

(Looks like the NYT got mixed up about which post was deleted)