21–30 of 56 posts
Earlier quoted context omitted.
Was? Are you saying you don't hold that opinion anymore, or do you just not use it?
Signups have been closed for 2.5 years since they were acquired by Slack. http://blog.screenhero.com/post/109337923751/screenhero-join...
What about a shared whiteboard, though? That's the one thing I'm missing at the moment. Using one of those with a couple of nice graphics tablets would be great.
I have lamented the lack of a good online whiteboard experience for decades now. I think the real problem is that for a proper whiteboard, we need obscenely large and high-resolution displays. Analog is much better than digital in this particular.
I used to think there was a lot of value in the concept of pair programming but I think the Pull Request and Code Review model is simply superior. It allows for a lot of the benefits of pair programming but with lower costs. I've always found that even looking over someone's shoulder to help debug something slows to a crawl. It takes more discipline than most engineers have to keep it truly paired.
So much of the work I do as a programmer does not go into the repository.
Yeah, that's not ideal, but so much of the work I do is in the technique. In the keyboard shortcut, the ~/.bashrc, the discipline of red-green-refactor, of pomodoro.
None of that stuff goes into the pull request, and yet all of it is something my programming pair can experience and learn from. And when I enter an area that's bizarre to me — when I am picking up a new language, a new tool or paradigm — a partner is 1000x more productive than my incessant slacking of code snippets when her explanations easily become demonstrations, and not least of all because it means that helping me is not an interruption to your KPIs.
None of that comes across in a pull request.
Maybe if your work exists entirely within code, within languages that you know, with build toolchains that are done changing, and you're entirely satisfied with your development environment, habits, and methods. In that case, yeah, CI and a little PR review are probably all you need.
Meanwhile, pair programming actually decreases the discipline you need to be a good engineer.
Real-time collaborative editing with text editors and IDEs.
Supports Sublime Text, Atom, Neovim, Emacs and IntelliJ IDEA (which includes the family of editors, e.g. PhpStorm WebStorm PyCharm RubyMine, etc)
It can be pretty interesting to watch two people code in one of the public workspaces..
What about a shared whiteboard, though? That's the one thing I'm missing at the moment. Using one of those with a couple of nice graphics tablets would be great.
I have lamented the lack of a good online whiteboard experience for decades now. I think the real problem is that for a proper whiteboard, we need obscenely large and high-resolution displays. Analog is much better than digital in this particular.
I've used a shared tmux session over ssh in the past, which worked quite nicely without installing any extra software (besides tmux obviously)
Is Wemux ( https://github.com/zolrath/wemux ) still relevant?