6 ms·
Mostly skimmed over here, but a key point is that you should be trying to build a cheap version of what you'd use at work. The closer you are to your work envir
by ocdtrekkie 6y ago
Mostly skimmed over here, but a key point is that you should be trying to build a cheap version of what you'd use at work. The closer you are to your work environment, the more you can applicably "try things" at home, and bring them to work with you. And since most of us are pretty busy, it's nice to not have to learn a whole new skill set just for maintaining our home networks.
- fomine3 6y agoI love homelabbing but the ongoing problem for homelabbing to training skill is that more jobs need to use cloud services, rather than on-premises.
- dragonwriter 6y agoSo, why not run open-source cloud software (OpenStack, CloudStack, etc.) in your homelab?
- fomine3 6y agoThat's OK for learning general things and the software but jobs tend to use AWS.
- dragonwriter 6y agoSure, so, you'll want to use some AWS (much of which can be within free tier), some of your homelab with CloudStack, etc., and some Terraform (etc.), and learn heterogenous hybrid cloud. Using a homelab for learning isn't somehow mutually exclusive with having your own AWS account for learning.
- ocdtrekkie 6y agoIf given an option between a job maintaining cloud services and a job maintaining on-premises technologies, I'd take the latter every time. You spend less time fighting support ticket queues and more time doing things.
- Macha 6y agoSadly my last employer used so much internal tooling and IPs that trying to do that would have involved transferring internal packages from the company network to personal infrastructure and probably gotten me fired as that would look pretty indistinguishable from an attempt at contract violating IP theft.
- lallysingh 6y agoI don't get why we'd pay for and maintain the test environment the employer should have. Should I bring my own printer and laptop to the office too?
- mynameisvlad 6y agoI think this misunderstands the point of the parent comment. They're not saying "replicate your work environment so that you can test your things at home", they're saying "replicate your work environment so you can learn best practices and apply your learnings at home when you're at work". There's a stark difference in that the things you host and do with your home setup are your own, but the learnings and technologies can be applied more broadly.
- bregma 6y agoYes, you should subsidize your employer by investing in your own specialized training and your own specialized equipment. With all the cutbacks the government isn't doing that for them any more so it's up to you to deliver solid value to the shareholders and quarter-over-quarter growth.
- mynameisvlad 6y agoEither you're exceptionally dense or you're purposefully ignoring the point. If you're setting up a homelab, you might as well use industry best practices for it.
- ocdtrekkie 6y agoAnd it works vice versa! I don't have to learn to support my home environment... I can actually do research at work for my job and also conveniently apply that to home!
- j45 6y agoIt's less about the employer and some choosing to take an interest in expanding their skills in this way.
- PeterisP 6y agoIt would make sense to build a version of what you're not going to use at this workplace, but what you'd like to use in a hypothetical next one.
- nucleardog 6y agoYeah, if I’m directly testing things for work I’m, at the very least, going to use work resources if not work time for that. We're all Ubuntu on AWS at work. My personal AWS resources are on FreeBSD. My home server is on Windows Server. The few places where I need Linux are at least Debian. Home projects are to scratch a personal itch, try and avoid getting too rusty at the things I don't get to keep up with at work, and/or expand the breadth of my knowledge, not to replicate what I'm doing at work.