121–130 of 147 posts
When working alone remotely from home, I simulate pair programming with a methodology I call "The Stranger". I sit on one of my hands until it becomes numb and tingly, and then it feels like somebody else is typing and moving the mouse!
I do the same just not for programming.
Not a single screenshot on the homepage? The number zeroth thing I want to see is a picture of the thing. Maybe even a gif or a silent autoplay video. I saw there's a video but it's a guy who's gonna talk. I just want to see the product.
Please watch the video and then tell us what would have been a good screenshot.
I realize that watching a video is maybe how a lot of product companies wish potential customers made decisions, but much like an elevator pitch, if I can't scroll the website and have a glance at what the product looks like, I ain't gunna watch a vidya bud.
Earlier quoted context omitted.
I worked on a team (of nine) which tupled a lot. Using Linux, I, and one other, was therefore not able to participate in a lot of work. Coworkers would pair with others because of familiarity, and because between macos and linux, there was more friction. This caused a severe schisma in an already disfunctional team. Management then disallowed tuple, because it was making things worse. But the practice continued. I qu…
Nobody is forced to use Tuple. If you blame anyone blame that company for allowing anyone to use Tuple in the first place, or the asshat engineers that held it against the Linux people.
My point is that any company that makes a co-operation product, but which excludes a demography from co-operating, should know they are causing harm.
Imagine if slack excludes Android. Or Google Meet excludes Apple devices. That is not only a poor product, it causes minorities to be excluded. Or divides the companies or teams using it. This is what Tuple is doing.
I'm blaming both Tuple for not including Windows and Linux up-front, just as well as management adopting such tech that has these clear limitations.
In this practical case, the Linux (and Windows) users joined later into an "mac-only" team. Tuple, however, was the major cop-op tech: they refused Slack, accidentally used Telegram (!?) and email, and when using Google Meet all engineers refused to turn on webcams. So as a non-Tuple-using person you were really kept out of the loop.
Quoted post unavailable.
Earlier quoted context omitted.
> the audio connection seems to keep going for a few seconds after you close the pairing screen I'm pretty sure this isn't true, but if you can reproduce it, please do let me know and we'll fix asap! ben@tuple.app.
> I'm pretty sure this isn't true Lol I'm not lying to you! I almost always hear an end-of-call sigh from the other person that I'm sure they aren't expecting to broadcast because they think they've ended the call, but nothing embarrassing yet! I'll try to screen-record my next interaction and show you. I think the problem is closing the window shuts down the screen link but not the whole pairing session, but people…
Sorry, didn't mean to imply you were :)
> I think the problem is closing the window shuts down the screen link but not the whole pairing session, but people don't realise they need to separately end the call.
Ah hah! This is totally it. Closing the screen share does not end the call (intentionally). I can decide I don't want to see your screen any more, but still want to talk to you. Definitely a debatable design decision, though. It actually used to work the other way.
Hi folks! I'm one of Tuple's cofounders. Happy to hear any feedback or answer questions :)
Is the work you’re doing for the Linux client also readying Windows support?
I've been using Tuple for the past year and a half or so, IIRC. It's just a really well done Mac app. One of those tools that "just works", is thoughtfully designed, and mostly just stays out of the way and does its job without doing anything annoying. We don't pair program as a regular thing, but we have junior engineers on our team, and often when they need help, or we're working through some bit of architecture, e…
Nice one. One suggestion. While you open the shared URL on the pair's browser automatically, there are still a bunch of steps involved in copying the url, pasting it in the app, and then hitting open, before the URL opens in the pair's browser. Instead, build a chrome/firefox extension that allows 'pushing' a tab into the pair's browser session. I find something good, I right click on the tab and click " Send to Pair…
Earlier quoted context omitted.
I hear you. We're pricey. Just curious – what would a workable price/model been for you?
For private mentoring/tutoring programming learners, $1 per session.
As a junior engineer who started career in 2019, I pretty much owe all my knowledge to Tuple, which I've been using to pair program with senior engineers since pandemic started in early 2020!