Honestly, with the AI slop of resumes, I applied to dozens of jobs, and only got a callback to ones I had either a recruiter for or direct connections to, after 20 years of experience. Because I didn't have a big fat "worked at google for 10 years" on my resume. And I'd like to think of myself as someone who can take a very bad situation and make it look smooth.
We once had a cloudflare outage. My CEO asked "mitigate it" I hit him back with, okay, but that'll take me weeks/months potentially, since we're tiny, do you really want to take away that many resources just to mitigate a once every few years half the internet is down issue?
He got it really quickly.
I did mitigate certain issues that were just too common not to, but when it comes to this sort of thing, you gotta ask "is it worth it"
Edit: If you're so small, cloudflare isn't needed, then you don't care if you go down if half the internet does. If you're so big that you need cloudflare, you don't wanna build that sort of feature set. The perfect problem.
> Maybe it's time for a third large phone OS, whether it comes from China getting fed up with the US and Google's shenanigans (Huawei has HarmonyOS but it's not open) or some "GNU/Linux" touch version that has a serious ecosystem. Especially when more and more apps and services are "mobile-first" or "mobile-only" like banking.
This makes me laugh. Not at you, but at the cycle. This was the convo years ago when this was possible, but getting consumers to trust a 3rd party like PalmOS (which was actually pretty darn good compared to android) is practically not possible.
Reminds me of the early days of cloud computing. It was very pricey, but once the tools caught up in 5 or so years, it went from "omg cloud is so expensive" to "omg cloud is only expensive when its worth building your own data center"
Reminds me of the argument of "cars used to be more sturdy than today, where any hit is a total"
Um... Looking at videos of crashing old cars into new cars, the old cars DO NOT hold up to new cars in terms of breaking. The only difference is in old cars the engine would stay intact and the occupants not, while in the new cars its the opposite.
I had a kid at 22, I am now 40 with a kid going to college. I can echo this exact sentiment.
However at 22 I wasn't the experienced person I am today. Nor was I stable, nor could I jump on opportunities like my peers could.
If having a child in your early 20s would mean not losing opportunities in progressing in a career, at least with enough free childcare and food to feed the children, people could be more inclined to have children while they get their life together. Our culture of moving away from home is also a big problem -- having 2 sets of grandparents helping raise a child REALLY helped me at my youth not miss out on youth and still raise my child.
kids between 25-32 is something our society should aim to be as practical and pleasant as possible.
Right up top. The service for alerts no longer works 24/7 so this happened when they were down for their daily window. Therefore the cuts are directly responsible.
I find that postgres query planner is quite satisfactory for very difficult use cases. I was able to get 5 years into a startup that wasn't basically trying to be the next Twitter on a 300 dollar postgres tier with heroku. The reduced complexity was so huge we didn't need a team of 10. The cost savings were yuge and I got really good at debugging slow queries to a point of I could tell when postgres would cough at one.
My point isn't that this will scale. It's that you can get really really far without complexity and then tack on as needed. This is just another bit of complexity removal for early tech. I'd use this in a heart beat.
Tarrifs are a tool that must be applied strategically. You typically announce tarrifs years in advance so business can shift their logistics and build out manufacturing where you want it. However a daily change in tariffs only creates a chaos that the economy cannot simply respond to fast enough.
A new steel mill won't magically appear in the middle of the US within a month.
As someone who set these up, I can tell you, the answer is rather simple:
- spammers have 1 system to set up in order to spam. They get it right.
- company admins have dozens of projects, of which this is a tiny one, with zero ROI to the bottom line (if people don't consider how critical security is). So they delay.
- companies often have dozens of systems integrated, when I set up DMARC/DKIM the first time for my company, a bunch of email tools broke, we had to do a bunch of leg work, took us a month end-to-end. The value was recognized when we almost lost 20k to a "ceo emails you" scam. But until then it wasn't a priority.
- we didn't even have a full IT, i just stepped in because I cared enough.
- my current company has a dedicated security team. These holes are plugged VERY quickly.
- if you use 1password (an example), then you're generating a bunch of random and unique passwords for every site
- questions to verify you as a 2fa tends to be less secure since you tend to make simple answers for those. And they're not convenient to enter into 2fa apps.
- 2fa apps are typically great ways to guarantee one bit of randomness into the process