1,030 karma · joined June 3, 2010
In Russian, "tvix" is pronounced, roughly, "tweaks" (but with a German - hard "v" - W sound), which to a Russian probably sounds super clever, given what Tvix is (Nix, tweaked).
In English though, how is it pronounced? I'd like to propose "t-f-icks", because it at least sounds like a candy we think the Lebowski nihilists might well have been ordering at a diner.
The two areas where it's been particularly helpful:
- Tricky Postgres queries - it essentially explains the pretty dry docs to you like you're five
- Partially because I use nvim without intellisense (made the switch after 23 years of vim last year!) - occasional TypeScript type issues
Can’t tell if bugs or clever
Thanks for making it
Excellent writeup!
We tried launching the GitHub repo on Saturday, but it didn't really take off. The GH README is absolutely the right place to start, everything else is confusing.
Our goal is to drive the reader to the "clone repo + start locally" step: once they do that, it all should start making sense.
Regarding your question about swapping out different technologies, take a look here - https://promptswithfriends.com/eject - although it's still a work in progress, and the short answer is "not really, yet".
This might turn into another Clubhouse/Shortcut situation
Stay strong, Threads (.com)
Many years later, I was taking an aerodynamics course at Embry-Riddle Aeronautical University taught by Bob Sweginnis (died in plane crash, while practicing aerobatics), who dedicated an entire class to a paper airplane contest. The winning criteria was “plane that stays in the air the longest wins”.
My plane came in second - I designed it to make an easy curve through the bungalow to maximise air time, and Bob Sweginnis did an excellent job launching it. He stopped the timer when my plane hit the wall of the bungalow, with plenty of altitude to spare.
The winner? A sheet of paper, basically, that pendulumed to the green carpet in a swinging motion, like a leaf, about a second slower than it took my Mona Lisa to commit suicide.
My favorite answer to this question is actually "they would just send an email to their customer success rep" :-)
Some other thoughts: the vendor could group all admins into a separate "customer", with their own set of rooms.
Very similarly, the vendor could also group all users a single "customer" that would function as a community (but where all users are authenticated).
Great question!
(i.e. if I'm an end user and I use Front to get support from my vendor - will my colleagues be able to get involved in sorting through my issue?)
(Pretending that Stripe is using Fogbender for customer support)
The whole reader/writer part is pretty confusing. I made a brief video that explains a possible workflow: https://www.loom.com/share/7f644774c3114e65b779d13d1c6eda18
- Unlimited read access to everyone at your company (because customer support conversations should be accessible to all team members). Say you have 15 people, but only 3 are customer-facing certified - if we charged $15/month, it would be $45/month for 15 people. (This also means unlimited write access in internal rooms - think of it as free Slack;)
- No charge for two customer-facing agents, which would cover most bootstrapped or pre-seed startups;
- Off-the-bat SSO; not a part of enterprise plan.
Here is how I think about it - by doing support through Slack, you're pushing your users to another tool to get support, away from your own product :)
We'd like to make it really easy to fuse a team dashboard (e.g. Twilio Flex) with team support experience, so your users would get the same level of care they get with Slack (possibly better - because instead of a single shared channel, they have what essentially is an entire shared workspace), but without having to also sign into Slack and locate the support channel.
That said, I do wonder how much pushback we'll see because end customers simply love getting support in Slack instead of inside the vendor's product.
We would love for you to beta test! You can kick the tires by signing up and inviting a few colleagues (ping us in support to see what it feels like), or I can walk you through a demo.
To the best of my knowledge, people are using Slack's shared channels plus an integration or two (custom or off-the-shelf).
Interestingly, AWS almost does this, but you have to know (and remember) the identities of those who should be CCd when opening a ticket.