Clojurians Log v2

If you do remote pair/mob programming what format and tools/platform(s) do you use? We want to improve knowledge sharing in our team and decided to try regular "mob programming" sessions - e.g. UI-focused devs introducing our ui library and concepts behind it and then trying to implement a small, but real, feature together. Our devs use a variety of tools - Emacs, IntelliJ, VSCode, ... I did some pair programming in the past but never remotely and I'm afraid it's gonna be very challenging to make it a good experience.

tmate works if you can accept the security implications and all parties are comfortable with the tmux UI https://tmate.io/

it doesn't work for a non tty frontend though

at my last job we would use zoom screen sharing and git mob to sign multiple authors onto commits. its not great for mid work handoffs but is good for pairing if its more driver/passenger style

I know @stefan.van.den.oord is using a combination of video sharing and VS Code Live Share. Where I work I’m the only one using VS Code so it’s Zoom only for when pair programming. Which works pretty nicely, but, as @dpsutton says, a bit more of spectator sport. Switch drivers often somewhat compensates.

@jumar I've been using http://screen.so for pairing - and it is mostly great. Both users get a cursor and can type and/or mark up a shared screen.

My company is moving away from Clojure and I'm very sad. I was discussing with another developer, and he mentioned Clojure wasn't on the 2020 stackoverflow survey, but it did pretty well in the 2019. Does anyone have any insight into that?

they removed it, not sure why

for various reasons (like this Slack), Clojure is not particularly active on SO, so presumably that's a reason

I see, thanks Alex!

really off topic here but looking for ideas. Problem: I am writing a client which will run specific tests on the users computer (they clone the code and run it in docker). Once the user runs the test, the client needs to publish the results to the server (this happens in the background without the user being concerned about it. but the user know this is happening). The user needs to be authenticated to publish anything to the server. Also, the users I am dealing with do not want to be prompted to enter their credentials, they are just concerned with running their tests. I am told storing their own credentials in a file on their computer is also a no go. A solution: 1. Ask the users to authenticate once with the server and get back an access token. 2. Store the access token on the file system (at some specific location) 3. (Steps 1 and 2 will happen only the first time or if the user looses the token) 4. The token will be stored in a DB so even if the app restarts, it will be saved without the hassle of re-creating it. 5. The user will run the tests and once the tests are finished, the client will use the token to authenticate with the server and publish their results. This solution seems a bit fragile. I have searched the web and I see things like API keys and auth tokens (i think what I am doing here is using auth token as an API key). Do you guys have an idea how I should approach this. A pointer in the right direction will be very helpful. Thanks.

your solution seems reasonable. seems very similar to how google handles auth with their apis: https://developers.google.com/gmail/api/quickstart/python

when the local credentials don't exist or aren't valid/expired, it goes through an oauth flow with something like: • print a link to open in a browser • the user logs in using their browser • an oauth token is presented to the user • the user copy and pastes the oauth token into the command line