If it is like 12 characters non dictionary and PW you use only in your homelab - seems like perfectly fine.
If you expose something by mistake still should be fine.
Big problem with PW reuse is using the same for very different systems that have different operators who you cannot trust about not keeping your PW in plaintext or getting hacked.
You know that making CI/CD doesn’t mean you have to pay boatloads of money to a vendor.
Putting up bash script that pulls repo and deploys it is already CI/CD.
Setting up basic Jenkins installation for a technical person should not be taking longer than 2 hours. For person who already is familiar with Jenkins that would be 30mins.
Once you have paying customers I would say there should be max and minimum 2 devs that can fiddle with prod. Others should pass changes via senior people.
A truly lean team (say, <=5 people and limited project scope) should be able to live off their code forge's free CI/CD minutes, or whatever is included in the basic tier they're running. Just run the suite on a schedule against trunk instead of on every PR.
If not, then that's a good signal they should invest more into their CI/CD setup, and like you said it's not necessarily a huge investment, but it can be a barrier depending on skills.
That's a bit harsh, depending on how a person developed or where they worked they may not have had exposure to other facets beyond basic development. Beyond that, it might as well be magic. They'll have to figure out how to provision a VM, ssh into it & lock all the proverbial doors first. Without going into managing it with IaC tools like Terraform, Ansible, Packer, etc.
> That's a bit harsh, depending on how a person developed or where they worked they may not have had exposure to other facets beyond basic development. Beyond that, it might as well be magic.
...so? You sit your ass down and learn. It might take a bit longer if you never touched shell but it's far easier than anything actual programming deals with, especially currently with set of ready or near ready recipes for every environment.
Yes yes. You’re right. I am saying at some places devs don’t own production- there’s an IT/Ops/non-dev person in the loop. Especially common if you’re a consultant in non-tech industries
Lots of stuff breaks only after 5 or 10 years. Because you most likely don’t have people who originally built stuff and knew why it was like that.
Then customers and market changed so you also most likely have different customers.
I had to undo a lot of over-engineering to fix performance issues that was implemented in good faith by people who ultimately left the company and they thought they did a good job future proofing our product.
I am with company from start and now it is 11 years. I knew why they built it like it was so I was able confidently what to fix. But it still took almost a year to undo stuff that was making our current customers miserable.
Good software isn’t always „software that makes money”.
Of course it is important to do stuff that doesn’t make money.
But if your goal is to make money you need software that people will pay for and people will use 20% of features but each one person will use different 20% of the features.
Generalist means something very different for big orgs.
At FANG size companies have people to setup 401k and health insurance, tiny startups need 1 of 3 people to figure that out even if it just means finding a company to outsource such things it still needs to happen. Payroll doesn’t need to be a complex system but taxes must be paid etc.
I would say I look at it from a different angle, big companies can afford specialists. Startups cannot afford specialized employee for database administration or setting up 401k.
But big companies would definitely love to have to pay a single salary for someone who does 401k and when this job is done administrates databases then in between reviews tweets searching for mentions of the company. Exaggerated example but I hope clear.
That already shows up with everything getting „Ops” obviously DevOps but I already have seen DataOps, SalesOps and MarketingOps.
That shows an ability to figure out what needs to be done and do it, regardless of whether it fits the formal job description. That can be an invaluable skill in an organization of any size.
It's the story of foxes and hedgehogs... Both have a time and place. Sometimes you need people who can aggressively put out fires, and sometimes you need people with deep focus for the long haul, who aren't overly distracted by the heat.
It’s a valuable attitude, but not a particularly valuable skill.
Expertise gains value when it can’t be subdivided. A doctor needs to know a who lot of related skills to be a heart surgeon, it doesn’t work to split it into two less demanding roles. However two generalists can sub divide the workload of a generalist with a lot more experience because experienced generalists aren’t particularly skilled at anything.
The horror of picking tech working in it 10 or 15 years and then it suddenly becoming obsolete or irrelevant. Is something a lot of people can relate to.
We're a new industry. So long as we keep iterating on our tools, this will continue to happen. Obsolescence is - in this case - an indicator of progress.
I don’t subscribe to the notion that we are „new industry”.
It already is well past 80 years and we can easily add computation jobs and record keeping that were there before those were digitalized.
„Centuries” of experience in other fields for me feels like it is exactly the case of that guy who has 20 years of experience in his CV in software development but can’t write fizz buzz if you ask for it.
There is so much knowledge lost and new guys don’t study centuries of history to build a house or become a sales person. You might study battles from century ago but they are mostly irrelevant.
If you expose something by mistake still should be fine.
Big problem with PW reuse is using the same for very different systems that have different operators who you cannot trust about not keeping your PW in plaintext or getting hacked.
reply