> People are kinda stupid when it comes to eating meat. The current scale of meat consumption [1] is just mind boggling. Yet even this comment has to be a throwaway because people can't handle someone telling them they shouldn't eat meat 2x a day.
I'm sensing a lack of empathy in this comment.
Calling people stupid or attaching any label to them will only hinder your attempt to sway their minds.
Portraying black and white thinking (splitting), when we know the world is shades of grey, also hinders your ability to change minds.
It's great that you found benefits to moving to a non-meat diet. This helps others see what they could benefit from. Continue from here.
This is the same issue as an abolitionist speaking to a slaveholder. The moral problem is so overwhelming for the abolitionist that it is exceedingly frustrating, difficult and ineffective trying to persuade the slaveholder.
> I'm sensing a lack of empathy in this comment
That is what is frustrating- to have to show more empathy for the feelings of the slaveholder than the slaveholder has for their slaves.
Have you been to commercial meat operations? I am not talking about millions of non human lives held in captivity, raped and slaughtered..but the condition of the labour in meat processing and meat packing industry.
It’s not a cowboy who brings your steak to the table, but probably some undocumented immigrant paid slave wages and living in a shed.
> comparing meat eating to slavery makes you seen even more unreasonable
I think that is an attitude that our culture will be ashamed of in the near future, just like we are ashamed of slavery now. The agricultural practices are almost identical (different mammal). The major difference is that we consume the flesh of one, and the produce of another.
The only reason for saying that the enslavement of other animals is ok, while the enslavement of humans is not, is if we can come up with a reason that makes us special and those other animals not. There is only shaky ground for any of those possible reasons, and believing them puts blinders on what we can know. I.e., we will not recognize things that do not fit our conceptions, which has big implications for our biological science, psychology and philosophy.
The fact is that meat eating, like slavery, is not reasonable. It is just something we grew up doing (individually and as a species). Any argument advocating it is as superficial and misleading as antebellum racial theorists. That is an uncomfortable truth.
Nonsense. Try telling the lion it is being cruel to the Antelope, or the wolf it is being cruel to the deer. All life (minus plants and Cyanobacteria) get their energy from eating other living things. That’s just the way it works.
Sometimes we compare dissimilar things and in the process discover new truths. We don't compare them to see which is worse, we don't compare to rank them, but to discern similarities and differences and, in doing so, gain a better understanding of both our subjects; even, why not, of ourselves.
It's only unreasonable to compare factory farming to human slavery if one believes that the rights of animals compared to humans is similar or worse than slaveholders believed the rights of their slaves to be compared to thme.
For the record I eat meat, but I'm under no illusions regarding the cruelty of the process. I support all laws that would increase farm animal welfare, even if it means my steak gets more expensive, it's simple enough to make good veggie dishes once in a while.
If — and I recognise that it is an "if" given the current lack of any sufficient testable definition of subjective consciousness awareness of self — if farm animals are self-aware, then slavery would be several steps up from their current existence.
We only stopped feeding cows to other cows because of a fear humans might get prion diseases.
Coming at it from the other direction, "what if humans were food?" is a horror trope, be it vampires, zombies, werewolves, or psychopath cannibals.
"Empathy" is not "sympathy" ("in-" vs "with-"). You try to understand the position of the other (it's a projection), not necessarily sharing the feelings.
The poster clearly expressed that "if they do not see it, insulting will probably create a counterproductive reaction of closure - it's not helping them to see it".
Its an arbitrary line, holding slaves at least follows from the golden principle. What principle says don't raise animals in poor conditions or eat them? Are you extending the golden principle to apply to all animals? Why? Do you think these principles come from anything but a higher-order self-serving? Rather naive to make up a principle for no other reason than a poorly identified (non)-symmetry. I could see applying the golden principle to a dolphin but its probably some back of the mind idea that maybe one day my grandchilds grandchilds grandchild will be half dolphin and I should hedge for that eventuality.
I'm not trying to sway any minds, the majority of people aren't going to change their meat consumption habits at all and honestly I'm fine with that. I never said in my comment that everyone should be vegetarian. Being vegetarian requires a lot of thoughtfulness, especially if you're at all athletic (I train muay thai and ashtanga yoga), and most people don't have the time for it (or think they don't).
People become exceedingly defensive when they're asked to confront the reality of their habits, and honestly I think it's probably too much for people to even begin to consider. I have deep empathy for that as a fellow human as I've been through it too and have experienced both sides of it multiple times (meat eating -> veg -> meat eating -> and now back to veg for good).
And their timeframe is pre-COVID and the worst possible time during COVID, when people were just trying to figure out how to work and live and not catch some deadly virus. 2020 was a hectic time and such an abnormality that I wouldn't base any long-term human behaviour on it.
As a non-judgemental sidekick. It helps with flesh out a random thought, it helps me understand a random coding problem, it helps me see why a vuln exists in a particularly difficult-to-read piece of code, and building outlines for reports and presentations that I'm too lazy to deal with. It is also starting to replace the random Google searches I used to do.
To boil it down, it's my "10-minute task" time saver.
And my use of it really picked up when I started using GPT4. It's head and shoulders above GPT3.5 in terms of quality and clarity of output.
Security is mutli-faceted, so it's hard to know where to start. I like to help people begin by getting them to learn the fundamentals. A lot of security training is changing your mindset (perspective) on situations.
Two books I like to start this process:
* Threat modeling by Adam Shostack
* CISSP all in one handbook by Shon Harris
You don't need to get a CISSP cert, but the resources and education are generally applicable in most situations.
If you're looking for something more practically related to securing the code you write, the OWASP Top 10 (and OWASP in general) is probably the best place to start. Many modern frameworks like Spring have lots of nice security features baked in, but I've still seen plenty of low hanging Top 10 vulnerabilities in Spring apps -- most often caused by simply failing to use allowlist (formerly known as whitelist) validation on key inputs.
It is astonishing how often people neglect basic programming best practices (input validation, error handling, logging, access control) which in turn leads to security vulnerabilities. My theory is this is caused moreso by Agile Management forcing developers to cut corners, rather than just developers being ignorant/lazy.
Threat modeling can be a good practice to learn, because it gets you into the habit of thinking about how you could hack each new thing you're developing.
I dont think the CISSP is a good recommendation for this person's case, unless they plan on becoming a cyber security manager.
That's not my point suggesting CISSP. The book I recommended takes the reader through the different OSI layers for networking and security, a basic intro to threat modeling, and other stuff that is fundamental to security. One can always skip the managerial stuff, but it doesn't mean the CISSP book is not a good recommendation.
Also, having a developer understand the value and need for code security from the perspective of a security person is important to the overall success of an infosec program. Otherwise both engineering and infosec are going to be grating on each other.
40 is a great time. In fact, I went down a similar path.
Now that you've done your share of sysadmins, SRE and software developer, you can see how things can fail. That's the heart of security. As tptacek advises, choose an area of security to focus on and go down that path for awhile. You'll find you will want to go further or jump to another path, but security is a great thing. The world is going to need more security-aware people and you can be at the forefront of it.
My current security focus is holistic defence of data flowing from customer to company. The whole SDLC lifecycle. It's fun but super challenging because it focuses on changing human mindsets and behaviour, but my Dev and ops skills are essential to my technical success.
And certs are useless on their own. Don't do certs unless you can specifically get something out of it. Your work experience is much more valuable than a cert at this point.
If you don't mind, I would love to know how "changing human mindsets and behaviour" and "Dev and ops skills ... technical success" go together for you!
Is your goal creating a development process that leads to a secure system, or securing a system made by an existing process? How much code do you write? Maybe some tasks you've enjoyed or a typical day would be great.
I say this because, while I've never had or wanted a title that included security, as a dev I often find myself looking at "holistic defense of data flowing" and attempting to improve the situation. A role based on that concept is interesting.
Given the inputs you stated, I am full CF because I don't want to manage state files, and I want some more advanced things like Deletion policies and automatic tagging of resources with the stack info. We use these tags in a lot of lookup scripts when operating on the infrastructure.
> I still can't really figure out what a container is.
If you mean this in a general sense...
One use case at Unbounce (where I worked in infrastructure) was to encapsulate the runtime dependencies for different services that were on a machine.
Our monolith required Ruby 2.1 and a bunch of gems. Then we were using Scout for centralized monitoring, which required 1.8 with a separate set of gems. We only noticed the problem when our monolith moved from Ruby 1.8 to 2.1.
To fix this problem of dual-Ruby runtimes, we encapsulated the Ruby 1.8 + gems into a Docker image for Scout, then ran the Scout container on the machine. It works perfectly and never conflicts with the monolith's Ruby runtime.
Does it allow to do "nested" logins? E.g., first login from machine A to machine B, then login from machine B to machine C, while the security token is on machine A?
> you'll get paid more than you need to survive - so don't be an idiot with your money.
Adding to this is something to consider:
You will be paid more than you need to survive, but you will most likely survive longer than you will be paid. Make sure you save money for those times.
I'm sensing a lack of empathy in this comment.
Calling people stupid or attaching any label to them will only hinder your attempt to sway their minds.
Portraying black and white thinking (splitting), when we know the world is shades of grey, also hinders your ability to change minds.
It's great that you found benefits to moving to a non-meat diet. This helps others see what they could benefit from. Continue from here.