693 karma · joined June 3, 2016
But seriously, IIRC they do 5000 rounds by default, but I've been wondering for a few years how is it that supporting nothing better than SHA512 for the whole /etc/shadow -based system is still ok? How come there's still no support for scrypt or bcrypt?
Edit: oh, someone mentioned this being from 2013. No Redis Streams back then.
At least you can override the default functionality with your own by utilizing the "authorized keys command". It basically allows you to create your own authorization scheme instead of the default "key in file means access granted"
The rationale for it not being a privacy violation, which was a concern that came up a couple of times, was that the machines were company property anyway.
He's a very chill person, but the problem was getting out of hand, so he started pasting users back with just a link to a page explaining why one does not simply do that. Some people took offense, but mostly the situation improved.
It was along the lines of [1], but not sure if it's exactly the same.
Of course even then you need to be active at least to the point of finding the others out there, but I'd still contest it to be the easier way.
Isn't that quite well in accordance of Agile Manifesto's "Responding to change over following a plan"?
Sprints and backlogs and grooming, all those sound they're straight from the Scrum Book. And while I understand that for many Scrum == Agile, actually it's not.
Note that I'm not saying anything about what's the best way to do software. Only that "responding to change" sounds very much agile.
Someone mentioned protobufs, maybe with something like those one could have both?
Automation has already been heavily cutting at the so-called low-skill jobs starting from Industrial Revolution. Or by some definition, from the Agricultural one somewhat earlier.
But the examples of the gardener and cook that were in your citation are actually quite good, I admit.
- "Grass is always greener on the other side"
- "You only fully appreciate great things when you lose them"
- All the people getting anxious or even depressed because social media constantly barrages us with the perfect pictures of perfect peoples' perfect lives, all the while forgetting that on many objective scales the fact that you're even able to get depressed by something like that puts you in the jackpot-winners category in the lottery of life compared to a huge percent of the world's population.
And also TV, as it is still today. Oh, and every other form of advertising basically. If advertising without invading user privacy is so bad (as the perpetrators are rationalizing it), how come all other forms of advertising are still a billion (trillion?) dollar business worldwide? Just makes one wonder.
Nor should they, if they act rationally.
To be honest, I've started thinking that having a lot stronger regulation for punishing companies is the only way to improve the situation. GDPR is a good start in the EU, although it is privacy-focused.
The free-market solution to this is that users (be they consumer or B2B) start shunning the companies and products with the worst security records, but the problem is that security (and privacy, it seems) are so hard to grasp that it's just not happening. Companies exist to make money, and it's sad how many of them won't actually care about anything else. So if that is the only thing that they care about, the only option to make them care about security is to make insecurity a bad road business-wise.
Absolutely not. Force pushing a shared master is probably the worst sin one can commit with git. I guess you already have come upon the 'why' of it.
A "Rebase workflow" works so that devs use rebase to 'move' their work on an updated master after a pull/remote update, resolve potential conflicts locally, and do a fast-forward push to origin/master. This also works on copying work between different feature branches just as well.
I believe in clean, linear history, and strongly prefer rebase-based workflows to merges. That's actually one of the reasons I chose Phabricator for my current place, as it is also very opinionated towards the same way of working.
Edit: oh, and to answer your actual question, the third one.
I often try to reassure people new to git that "if you'll just commit often, there's basically no way you can lose work so that I can't help you get it back. Apart from deleting the whole repo folder. Don't delete the repo folder.".
I also have the habit of preventing non-fast-forward pushes on origin/master, which also helps when I can tell my team that they can't trash the origin even if they try.
It's non-fast-forward pushes that are dangerous. And they're dangerous whether anyone uses rebase or not.
My current company is working with heavy machinery manufacturers, and the industry is years behind consumer automotive. There's a similar kind of explosion in the amount of small intelligent modules waiting to happen.
On the other hand, things like heavy machinery control systems are usually in somewhere in the middle: the machines themselves are burdened by all kinds of regulations, and the machines can kill a dozen people easily by accident if something goes catastrophically wrong, so it would definitely suck to "move fast and break things". Also, like you mentioned, software updates are few and far between.
Then there's medical and aviation and friends, where you have MISRA-C and the like. Very process-y, if you like that.
Basically, work on SW for tangible things, and pick your poison regarding how much requirements and process you want. I'd say that on a very broad average, things do get more strict going farther down the stack, if for no other reason than that if the lowest level code does not work reliably, then nothing else usually won't either.
One of the reasons I love embedded SW development is this right here. I know that it's basically just in my head, but it's so much more satisfying for me to work on a medical device SW or a harvester control system than, I dunno, some random ToDo app.
One could call embedded dev the sweet spot between the real world (as you put it) and the abstract world of pure software.
One of the great things in being a parent is that I can once more forget myself for hours when building snow castles or burrowing tunnels into a snow mountain at the end of the street, and no one bats an eye 'because kids'. Having kids also changes you in a way that you once more remember how awesome that was in the first place.
If you have people under you, or can coach your people to take parts of your responsibilities off you, I think that's a great outcome. If your ICs are so good that they can actually do that, you should give them a raise and be glad you get to focus on other things in the meanwhile.
Of course, if the manager is unable to then broader their own scope, they indeed become disposable.