What is the technical hill you are willing to die on in your industry?
Ask Lemmy
41
İleti
17
Yayımlayıcılar
23
Bakış
-
So does the TCP/IP model and that is what systems actually use.
Plenty of things don't fit into the TCP/IP model at all. Infiniband, for starters.
-
Every industry is full of technical hills that people plant their flag on. What is yours?
Is there anybody on Lemmy that isn't a software engineer of some description? No? Anyone?
-
Every industry is full of technical hills that people plant their flag on. What is yours?
If people used a language that actually leverages the strengths of dynamic typing, they wouldn't dislike it so much.
I encourage every programmer to build a Smalltalk program from the ground up while it's running the entire time. It really is a joy
-
Every industry is full of technical hills that people plant their flag on. What is yours?
Not everything needs to be deployed to a cluster of georedundant K8s nodes, not everything needs to be a container, Docker is not always necessary. Just run the damn binary. Just build a .deb package.
(Disclaimer: yes, all those things can have merit and reasons. Doesn't mean you have to shove them into everything.)
-
Weren't there multiple researches concluding that even an EV powered by a coal plant is better for the environment than an ICE vehicle?
If you tell me gasoline yeah probably (diesel generator to power electric motors is done in big ships), caol I highly doubt it.
But apart from pollution per se, an electric car used everyday would require at least 50% of a household power budget to charge (2-3 kW). If every single ICE vehicle would be immediately swapped to electric, I doubt many countries would be able to cope with the increased power consumption. That's why we need more energy infrastructure before a full switch. Or you know, less cars and more public transport.
-
Not everything needs to be deployed to a cluster of georedundant K8s nodes, not everything needs to be a container, Docker is not always necessary. Just run the damn binary. Just build a .deb package.
(Disclaimer: yes, all those things can have merit and reasons. Doesn't mean you have to shove them into everything.)
But then how will I ship my machine seeing as it works for me?
-
If people used a language that actually leverages the strengths of dynamic typing, they wouldn't dislike it so much.
I encourage every programmer to build a Smalltalk program from the ground up while it's running the entire time. It really is a joy
Should also try programming in Rockstar so you can actually say you are a rockstar developer.
Rockstar
Rockstar is an esoteric programming language based on the ‘lyrical conventions of 1980s hard rock songs and power ballads.’. It was created by Dylan Beattie in 2018.
Rockstar (codewithrockstar.com)
-
Is there anybody on Lemmy that isn't a software engineer of some description? No? Anyone?
Yes, me. I am a network engineer with an expired CCNA
-
Plenty of things don't fit into the TCP/IP model at all. Infiniband, for starters.
Does infiniband run IP?
-
If you tell me gasoline yeah probably (diesel generator to power electric motors is done in big ships), caol I highly doubt it.
But apart from pollution per se, an electric car used everyday would require at least 50% of a household power budget to charge (2-3 kW). If every single ICE vehicle would be immediately swapped to electric, I doubt many countries would be able to cope with the increased power consumption. That's why we need more energy infrastructure before a full switch. Or you know, less cars and more public transport.
I do like the idea of less cars, more public transport, and better power infrastructure. Can we have all 3?
-
A dirty hack that exists now is infinitely better than a properly developed tool that has gone through all stages of approval and quality control at some theoretical point in the future.
My shitty report.pl script was heavily frowned upon when I put it on the production servers. Not only was it an undocumented script, but there was going to be a "proper" tool for that soon. Well, the proper tool never arrived and now three years later everyone is using my script because we are all too lazy to compile a list of warnings manually.
Jack it together now but then a Italy run the proper fix. Don't leave dirty hacks in production or test.
-
Does infiniband run IP?
No
-
Every industry is full of technical hills that people plant their flag on. What is yours?
Your favorite AI enabled LLM does a very, very good job of simulating language tests based on previous tests and there's no reason at all not to use it to study and prepare.
-
It doest run CLNS either.
-
Your favorite AI enabled LLM does a very, very good job of simulating language tests based on previous tests and there's no reason at all not to use it to study and prepare.
It can write you a poem, it can't write you a play.
-
But then how will I ship my machine seeing as it works for me?
Damn, I haven't thought of that! Looks like I have to use a subdirectory of your Homedir from now on.
-
Damn, I haven't thought of that! Looks like I have to use a subdirectory of your Homedir from now on.
Just symlink my home folder to your PC and we are good to go.
-
Every industry is full of technical hills that people plant their flag on. What is yours?
IT restrictions should be much more conservatively applied (at least in comparison to what's happening in my neck of the woods). Hear me out.
Of course, if you restrict something in IT, you have a theoretical increase in security. You're reducing the attack surface in some way, shape or form. Usually at the cost of productivity. But also at the cost of the the employees' good will towards the IT department and IT security. Which is an important aspect, since you will never be able to eliminate your attack surface, and employees with good will can be your eyes and ears on the ground.
At my company I've watched restrictions getting tighter and tighter. And yes, it's reduced the attack surface in theory, but holy shit has it ruined my colleagues' attitude towards IT security. "They're constantly finding things to make our job harder." "Honestly, I'm so sick of this shit, let's not bother reporting this, it's not my job anyway." "It will be fine, IT security is taking care of it anyway." "What can go wrong when are computers are so nailed shut?" It didn't used to be this way.
I'm not saying all restrictions are wrong, some definitely do make sense. But many of them have just pissed off my colleagues so much that I worry about their cooperation when shit ends up hitting the fan. "WTF were all these restrictions for that castrated our work then? Fix your shit yourself!"
-
Every industry is full of technical hills that people plant their flag on. What is yours?
Workplace safety is quickly turning from a factual and risk-based field into a vibes-based field, and that's a bad thing for 95% of real-world risks.
To elaborate a bit: the current trend in safety is "Safety Culture", meaning "Getting Betty to tell Alex that they should actually wear that helmet and not just carry it around". And at that level, that's a great thing. On-the-ground compliance is one of the hardest things to actually implement.
But that training is taking the place of actual, risk-based training. It's all well and good that you feel comfortable talking about safety, but if you don't know what you're talking about, you're not actually making things more safe. This is also a form of training that's completely useless at any level above the worksite. You can't make management-level choices based on feeling comfortable, you need to actually know some stuff.
I've run into numerous issues where people feel safe when they're not, and feel at risk when they're safe. Safety Culture is absolutely important, and feeling safe to talk about your problems is a good thing. But that should come AFTER being actually able to spot problems.
-
IT restrictions should be much more conservatively applied (at least in comparison to what's happening in my neck of the woods). Hear me out.
Of course, if you restrict something in IT, you have a theoretical increase in security. You're reducing the attack surface in some way, shape or form. Usually at the cost of productivity. But also at the cost of the the employees' good will towards the IT department and IT security. Which is an important aspect, since you will never be able to eliminate your attack surface, and employees with good will can be your eyes and ears on the ground.
At my company I've watched restrictions getting tighter and tighter. And yes, it's reduced the attack surface in theory, but holy shit has it ruined my colleagues' attitude towards IT security. "They're constantly finding things to make our job harder." "Honestly, I'm so sick of this shit, let's not bother reporting this, it's not my job anyway." "It will be fine, IT security is taking care of it anyway." "What can go wrong when are computers are so nailed shut?" It didn't used to be this way.
I'm not saying all restrictions are wrong, some definitely do make sense. But many of them have just pissed off my colleagues so much that I worry about their cooperation when shit ends up hitting the fan. "WTF were all these restrictions for that castrated our work then? Fix your shit yourself!"
You pay me to admin 400 servers on a couple million dollars worth of hardware. Let me install a fucking app on my own machine without 4 levels of bullshit.
