Earlier quoted context omitted.
What’s a DPA, please?
Data Processing Agreement: https://gdpr.eu/data-processing-agreement/
GitHub’s engineering team has moved to Codespaces
581–590 of 704 posts
Re: GitHub’s engineering team has moved to Codespaces
#582Earlier quoted context omitted.
I did not understand that part. Every heavy Emacs or vim user have its own customizations of editor. How does it work with shared image?
Just use an sshfs mount and a local editor.
Re: GitHub’s engineering team has moved to Codespaces
#583Earlier quoted context omitted.
That's the trick, the git is open, but the metadata is what matters. Issues, PRs, integrations into various code auditing services. That's the whole "extend" bit.
By that logic any proprietary product that provides an interface with an open source tool is guilty. I think accusing MS of EEE in this case is a huge stretch; GitHub is a commercial product that uses a popular open source tool with 100% compatibility (that I'm aware of) and actively participates in the development and features of that tool. When Ms start implementing extensions to git that only work with GitHub, we…
Re: GitHub’s engineering team has moved to Codespaces
#584Earlier quoted context omitted.
That's the trick, the git is open, but the metadata is what matters. Issues, PRs, integrations into various code auditing services. That's the whole "extend" bit.
By that logic any proprietary product that provides an interface with an open source tool is guilty. I think accusing MS of EEE in this case is a huge stretch; GitHub is a commercial product that uses a popular open source tool with 100% compatibility (that I'm aware of) and actively participates in the development and features of that tool. When Ms start implementing extensions to git that only work with GitHub, we…
I don’t know that this is the result of a deliberate strategy by GitHub, but by any metric the extend step is a resounding success.
Re: GitHub’s engineering team has moved to Codespaces
#585Earlier quoted context omitted.
If a business is paying for this product, then THEY (not you) are the customer. And in that context - yes, Microsoft may be asked or build a product for managers to manage their workforce, particularly if remote. This could involve presence tracking, engagement tracking (ie, do you open alerts / read your bug reports) etc. One approach would be to monitor what management considers productive / successful employees an…
> One approach would be to monitor what management considers productive / successful employees and also on employees who have gone on PIP's - then train the AI on that data set. I look forward to the papers on how to slack off on your job while the AI classifies you as "a straight shooter with upper management written all over him". Possible title: "An adversarial approach to the TwoBobs Productivity Classifier" (/s…
I’ve been pitched the TwoBobs Productivity Classifier.
My feedback was anyone who needs it has classified themselves as an unproductive dev manager.
I suggested the concept be made available as being by devs, for devs, purposed as a personal coach, with no uplink to the mothership.
Re: GitHub’s engineering team has moved to Codespaces
#586Serious question: if I were to use this, would Microsoft collect analytics on me (code written, keystrokes, mouse movements, sleep/work schedule, productivity metrics, etc) and monetize that data by using it to build some AI product like Copilot, or build a productivity dashboard so managers can fire people for not being productive enough (like Xsolla did), use it to serve me ads, or do some stupid/irresponsible/unet…
If a business is paying for this product, then THEY (not you) are the customer. And in that context - yes, Microsoft may be asked or build a product for managers to manage their workforce, particularly if remote. This could involve presence tracking, engagement tracking (ie, do you open alerts / read your bug reports) etc. One approach would be to monitor what management considers productive / successful employees an…
Re: GitHub’s engineering team has moved to Codespaces
#587I feel like all of the problems in the blogpost are solvable without moving everyone to this crazy web development environment. To quote one of the proponents: > I do solemnly swear that never again will my CPU have to compile ruby from source. ...yeah, why was that even happening? Why not distribute pre-built artifacts? I feel like the whole docker ecosystem only exists because people forgot how to distribute softwa…
Re: GitHub’s engineering team has moved to Codespaces
#588Earlier quoted context omitted.
> One approach would be to monitor what management considers productive / successful employees and also on employees who have gone on PIP's - then train the AI on that data set. I look forward to the papers on how to slack off on your job while the AI classifies you as "a straight shooter with upper management written all over him". Possible title: "An adversarial approach to the TwoBobs Productivity Classifier" (/s…
Sadly, not /s. I’ve been pitched the TwoBobs Productivity Classifier. My feedback was anyone who needs it has classified themselves as an unproductive dev manager. I suggested the concept be made available as being by devs, for devs, purposed as a personal coach, with no uplink to the mothership.
Ah yes, the classic "foot in the door" approach. Despite all the good intentions behind it, it still would end badly.
Re: GitHub’s engineering team has moved to Codespaces
#589Re: GitHub’s engineering team has moved to Codespaces
#590Github has the best part of 10 critical outages every month. It's a surprise when it doesn't go down.