I used to use SyncThing, then Dropbox, then iCloud. But then I just caved and paid for Obsidian Sync and it is the best money spent aside from Claude. I don't have to tinker with weird settings anymore or deal with sync issues, it just works.
> 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.
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.
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.
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.
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.
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.
> 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 do understand capitalism, the point I made was that sometimes I don't have to like it. Scalping included.
I don't need to prove my knowledge to you by pointing out lots of capitalism's flaws. Instead of reading my comment carefully, you decided to teach me about how basic supply and demand operate. Jesus, you are a self-absorbed piece of work.
I grok capitalism and even like it. But there are times where it is difficult to like it. In this case, people rushed to buy this product for the sole purpose of reselling it for 8x. What's wrong with our society that some people can be so morally bankrupt and bereft of good sense.
In the end, I think these scalpers won't sell for 8x because anintendo will just pump out more product. Still, it is sad to see this happen.
Threatstack will do that. Their agent runs on your machine as a kernel mod and will alert you to any libs being used (e.g. openssl, libcurl) whose version matches a known CVE.
This killed one of our main webapps, but since the site was hosted on AWS, I provisioned an ACM certificate (free) in about 5 minutes and manually applied it to the ELB listener. Couldn't have been easier.
Today's weirdness and communication around it has made me trust Globalsign a lot less now.
I use them indirectly like I use design patterns. I'm not thinking "Oh, I'm using 3rd NF" or "I'm using Singleton" at work. Instead, when designing databases I'm thinking about removing duplication (which is the crux of normal forms). However, like proofreading, you can go too far and normalize your database too much, making it hard to work with, so you allow duplication of some fields (hence denormalization).