Obtaining hardware from terminated remote employee
-
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
-
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I've seen, but never tried myself, a remote option in VSCode. I just saw it in an article the other day. Interested to try it out.
-
@stacksofplates said in Obtaining hardware from terminated remote employee:
I haven't really seen anyone do this other than CAD work.
We actually do it some for development.
-
@StorageNinja said in Obtaining hardware from terminated remote employee:
@scottalanmiller said in Obtaining hardware from terminated remote employee:
Can't do that legally for US employees though, in most cases.
I worked a place that kept your first week's wages as a deposit against hardware (yes, this is weirdly legal at least in Texas).
Eventually, it got silly as more and more of the office switched to BOYD (The rule dated back to when they issued $600 smart phones and laptops that cost 2K).
This was technically in the signed work contract but many people angrily found out about it after their first paycheck was kinda "light".Might be legal in Texas, but AFAIK violates federal law. Texas can't change federal law and that sounds like a disaster just waiting for someone to get a better lawyer.
-
@scottalanmiller said in Obtaining hardware from terminated remote employee:
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I've seen, but never tried myself, a remote option in VSCode. I just saw it in an article the other day. Interested to try it out.
It works really well, at least for the Go projects I work on. Everyone having the same extensions and environments is really nice.
-
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I believe you and find it very interesting. Wov. If that's how most people work, I'm just blown away. I assumed everyone was remote and had full on development and test environments at their disposal.
-
@Pete-S said in Obtaining hardware from terminated remote employee:
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I believe you and find it very interesting. Wov. If that's how most people work, I'm just blown away. I assumed everyone was remote and had full on development and test environments at their disposal.
Mirrors what I've seen. What little bit I've seen it seems that development remains more often local than remote.
ChromeOS seems to encourage away from that, but not many devs using that.
-
@scottalanmiller said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I believe you and find it very interesting. Wov. If that's how most people work, I'm just blown away. I assumed everyone was remote and had full on development and test environments at their disposal.
Mirrors what I've seen. What little bit I've seen it seems that development remains more often local than remote.
ChromeOS seems to encourage away from that, but not many devs using that.
it's like the LANLess idea, great idea, rarely implemented
-
@Dashrender said in Obtaining hardware from terminated remote employee:
@scottalanmiller said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I believe you and find it very interesting. Wov. If that's how most people work, I'm just blown away. I assumed everyone was remote and had full on development and test environments at their disposal.
Mirrors what I've seen. What little bit I've seen it seems that development remains more often local than remote.
ChromeOS seems to encourage away from that, but not many devs using that.
it's like the LANLess idea, great idea, rarely implemented
If by LANless you mean a Zero Trust Architecture, then it's more than an idea.... it's widely implemented, and proven as one of the most effective methods of security. There are large global enterprises everywhere who have already adopted and implemented it. There are many others who are currently implementing it, and there are many planning to.
It's the only true path forward. Those who don't adopt Zero Trust Architecture, will surely end up wishing they had.
-
@Dashrender said in Obtaining hardware from terminated remote employee:
@scottalanmiller said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I believe you and find it very interesting. Wov. If that's how most people work, I'm just blown away. I assumed everyone was remote and had full on development and test environments at their disposal.
Mirrors what I've seen. What little bit I've seen it seems that development remains more often local than remote.
ChromeOS seems to encourage away from that, but not many devs using that.
it's like the LANLess idea, great idea, rarely implemented
It's implemented commonly in big and advanced companies. You are used to small firms and communities like SW where things are years behind typically. LANless is, and has been, a major market force for forever.
-
@Pete-S said in Obtaining hardware from terminated remote employee:
@stacksofplates said in Obtaining hardware from terminated remote employee:
@Pete-S said in Obtaining hardware from terminated remote employee:
@StorageNinja said in Obtaining hardware from terminated remote employee:
@JaredBusch said in Obtaining hardware from terminated remote employee:
Hardware is not worth the fucking time to get back.
If the company thinks wasting man hours on that is a good idea the company is insane
While I largely agree, our R&D laptops are ~2-3K a pop. (fully max spec' MPB or XPS with onsite repair agreements).
I did hear we have started on the Mac's using DEP, so the device will auto-enroll in MDM even if the device is wiped.
https://support.apple.com/en-us/HT204142Makes no sense developing on a laptop IMHO - unless you're talking about another kind of R&D in another field.
On our team we remote into development servers and all development and testing is run there. Which means the computer you're actually sitting in front of just needs to be able to run a browser, rdp, ssh etc. So any machine suitable for general office work would get the job done. So no 2-3K laptops needed for development, even if that is not the primary reason. I kind of assumed everyone worked that way but haven't actually given it much thought until now.
I haven't really seen anyone do this other than CAD work. Everywhere I've been it's local development, possibly using Eclipse Che or Coder or something for a remote IDE but still local.
VSCode and JetBrains tools allow you to include your development environment in a container. So when you open the project it will open inside of a container with all of the dependencies included. That's the best workflow ive seen so far.
I believe you and find it very interesting. Wov. If that's how most people work, I'm just blown away. I assumed everyone was remote and had full on development and test environments at their disposal.
They usually do have full dev/test environments but it's all containerized. So it's trivial to run that locally. Then when you are satisfied with local results push to your branch and have it auto build/deploy against the actual dev/test environments with something like Flux/Argo. This is still remote, GitOps is all about remote workflows.
