Absolutely no fucking way! And anything that touches work is isolated, their opsec sucks so much they didn't even realized they mandate "security solutions" with known backdoors.

[–] SleeplessCityLights@programming.dev 22 points 6 hours ago (1 children)

I think it means they setup new tech on their homelab to learn how everything works and how to break it. Then when a problem arises where one of these solutions is needed at work, you can implement it without any large issues. It makes sense if your hobby is close to or adjacent your day job, and you are on Salary, and your boss treats you right.

[–] marcos@lemmy.world 10 points 6 hours ago (1 children)

Yes, I'm not doing almost any of the things we do at work in my network.

I'm absolutely not running the same software. I'm not organizing the information the same way. I'm not using the same infrastructure abstraction, and even less configuring it in any similar way. I'm not writing the same languages.

The work environment is dictated by consensus between many people, with varying expertise, and weighted by how much work one is willing to put into each aspect of it. Each of those parts lead to bad tech, even though they lead to good people organization.

[–] SleeplessCityLights@programming.dev 2 points 1 hour ago

You are telling me that you can't proof of concept something without a matching tech stack? Or learn exactly how a new tech works? It also sounds like you should never give your work any of your personal time, you won't gain anything except for more work.

[–] IsoKiero@sopuli.xyz 8 points 5 hours ago

Our opsec is pretty well managed, but I try to squeeze anything I'd need at home to work tasks. I get paid to learn the stuff at work and then I can just implement it on my own environment.