81–90 of 147 posts
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" or similar.
Hi folks! I'm one of Tuple's cofounders. Happy to hear any feedback or answer questions :)
The best improvement was the clunky 'observer'-party that wasn't easily able to become the 'driver'. I think I actually received a reply on that one, plainly stating that it's a well-known issue that's being actively worked on, and not long after it began working seamlessly. I was about to ask about shortcuts, as moving the mouse to the menubar to temp-mute (or hang-up at end of call) can be a bit awkward if your screen is the one being shared--I just looked and there are Hotkey settings, just no defaults. Great stuff.
There used to be some issues where leaving Tuple running for days/weeks(?) sometimes could have it consuming CPU while idling. I don't recall the OS-version specifics, but I've got into the habit of exiting and restarting it every day or so. The problems may have been fixed but I haven't tried leaving it running to find out. If there's a way of submitting diagnostics specifically for these sorts of issues, I'd like to know.
It all it's as close to a perfect product as I use on a daily basis. Even with one team member's internet that can get slow at times, dropping to 1080p makes the text a bit chunky but still readable and able to follow along.
Quoted post unavailable.
Build a native app and you get complaints about cross platform. Build an electron (or other cross platform toolkit) app and you get complaints about resource usage and non native ui. Seems to me that they know their target market (large tech shops with lots of devs on macos) and preferred to optimize for resource usage and user experience by going native. For another company, this could very well be the wrong choice,…
This. I am currently making a productivity app and I had to actively unbias myself from the hackernews/prosumer mentality that I must write independent apps for at least 3 operating systems/GUI systems, and 2 more if I want to go mobile.
It's a shame that interoperability has been an anti-priority from the OS providers (mainly MS, Apple and Google - if there was any standard Linux would follow). Even more sad is that the popular opinion is blaming developers for the situation.
Earlier quoted context omitted.
In places I've worked in, there's very little pair programming culture. If a dev needs help, maybe the reaction is "push your code to a special branch and I'll take a look later" or if it's really urgent "use screen sharing" instead. A lot of that comes down to different environments: some use Emacs, others use Vim, yet others use VSCode, and remote control isn't really effective because of all the different shortcut…
I can tell you how Pivotal solves this problem (or used to; my time was years ago): Standardize the configuration. If some special tool is making you more productive, share it with the team and get everyone on board. Don't try to be a special snowflake. IMO this is the right way to do pair programming. It tends to bring everyone up to speed with the latest tools, and it keeps eccentrics out of the weeds. It's not to…
Wow, what a really great idea. I love the code snippet sharing box, that's perfect.
Earlier quoted context omitted.
In places I've worked in, there's very little pair programming culture. If a dev needs help, maybe the reaction is "push your code to a special branch and I'll take a look later" or if it's really urgent "use screen sharing" instead. A lot of that comes down to different environments: some use Emacs, others use Vim, yet others use VSCode, and remote control isn't really effective because of all the different shortcut…
I can tell you how Pivotal solves this problem (or used to; my time was years ago): Standardize the configuration. If some special tool is making you more productive, share it with the team and get everyone on board. Don't try to be a special snowflake. IMO this is the right way to do pair programming. It tends to bring everyone up to speed with the latest tools, and it keeps eccentrics out of the weeds. It's not to…
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.
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.
As far as a screenshot for product? Not sure, it really stays out of the way which I like but that makes it difficult to convey visually. Which you seem to have realized :)
Earlier quoted context omitted.
Have you practiced it extensively though? You said you haven't professionally, so that leaves just personal experience. I would say it's not entirely critical, but I'd be very skeptical about a company's engineering if they didn't pair program. It would make me look closely at their other practices or lack of
I very much get a cargo-cult vibe from this statement. In a 30-year career, I’ve pair-programmed under 100 times. Usually to get someone up to speed on a confusing part of the code base. In fact, I’d go as far as to say that if pair programming is a recurrent need, you need one or more of better engineers, better documentation, or better code reviews.
I don't see it as only as a need to unblock someone. It's a great way learn and share from in a junior:senior dynamic, and also speaking strictly remotely, a nice way to socialize