Standard Nintendo behavior.
1,492 karma · joined January 23, 2024
But if it is, then I think you’re trading it for a career of trial and error.
Regularly I watch people at work spend a week trying to solve a problem, but because I learned the fundamentals at some point in my past life, I am able to break down the problem, identify the root cause, and solve it quickly.
Insurance is for losses that will have a major impact on you. It’s putting a price on risk.
Insurance is for you and you should pick it from your own choice of company and you should tailor the policy for your own needs.
Same with financing.
In my case, I get a lot of my insurance from a guy in my town and he has an office that I can walk into if I need help.
I call our vague requirements not because it's part of a certain process or something I read from a book. It's because I want to know what the heck you actually want because I want to double check your plan.
Heck, if a friend comes to me with a plan, my first question will always be "what are you trying to do?" because I don't want you to waste your time.
We built a full wooden camper setup with electrical and plumbing. We sketched and crafted new furniture for our apartment. We designed and built our own hydroponics system.
And we skated a lot and hiked where we could. We did also play a lot of video games.
Someone that goes to work to do the tasks assigned to them (which applies to both managers and those on the line) vs. someone that goes to work because they want something (e.g. maybe a certain product made with certain features) thinks very differently. The latter has a whole plan and the plan has certain sub-requirements that all feed back into the greater goal.
As part of going to Mars, you will likely have to send many supporting missions, which drives the requirement to lower costs. When designing bespoke systems, contracting it out to third party vendors can be expensive. Usually you contract out to third party vendors because they can utilize economies of scale because they have many clients who are asking for the same thing, but there are no economies of scale here because no one has reusable rockets in their catalog.
For me, it's just not worth it. Had iPhones break while on trips and it's just an absolute hassle dealing with replacements, especially when there aren't Apple stores for hours, while I can just put on a protector and done.
(Plus I think a clear case looks really nice and brings a retro Casio vibe.)
Like when I'm listening to a Spotify playlist and I want to like the song or save it to a playlist while driving, it would be amazing if I could just tell Siri to do it for me. As-is, sometimes it tells me it doesn't how to play songs on Spotify.
Or they were showing how you would be able to look for photo by describing it.
But if you are new and are pressed for time, you only look at maybe a fraction of those thousand things, and inevitably you miss some important things.
AWS used to not have sane defaults for S3 buckets.
People arguing about public vs. private are missing the mark entirely. It has nothing to do with that. It's all about how many people have to do a task.
The US govt got to the moon and created a nuclear bomb in a relatively tiny amount of time, all entirely because it was a relatively small number of people focused on the same task. As for people who own routers? Thousands and thousands of them who all have different interests who aren't all focused on the same goal.
Getting a large group of people to do one simple task is 100x harder than getting a small group of people to do a complex task. This is why humanity got to the moon but still are stuck on IPv4.
A lot of interests need a common space.
https://en.wikipedia.org/wiki/Third_place
Most kids have a third place growing up, being an extension of school or another place like the skate park. If you leave school and don't find a new third place, finding new friendships becomes difficult.
You’re supposed to not reuse passwords, but then you don’t remember passwords.
So you use a password manager. Until more recently when phones and computers came with built-in password managers, no normal person was going to download a password manager.
But even when you use a password manager, sometimes it doesn’t recognize the form fields. Or it doesn’t show it because the domain is different. Sometimes it doesn’t save a new login. The website has no direct awareness of the password manager so it’s hit and miss.
So we created passkeys. Except it’s also hit and miss. Some sites only sometimes ask for them. No site explains what they are. Some sites ask for you to login with a passkey, which you wouldn’t have yet, but then don’t ask you to setup the passkey after logging in with a password, so you never set up a passkey.
Overall authentication is a disaster and my very fiery take is overly technical people who are out of touch with normal people design authentication.
But IE devs were unhinged. You could build JS code as a module and attach it to elements using CSS.
Finally we're getting those kind of unhinged features again.
Personally I think you should always be using containerization, because even single node Docker is easy. If you are running something for real, then definitely use Kubernetes.
If you are using containerization, setting up Tailscale is trivial.
Whenever you abstract away something, you can swap out core components like networking willy nilly. Of course, you can always over-abstract, but a healthy amount is wonderful for most non-very high performance use cases.
1. half “you build it yourself”, and
2. half “have someone else build it but you make the plan”
I don’t get who the audience for it is.
You’re supposed to start at the bottom too but the order is kind of all over the place.
Link to the house building one for anyone interested: https://github.com/sjpiper145/MakerSkillTree/blob/main/House...
I did personally get a degree in EE and have worked on low level programming (and funnily enough I do a lot of frontend these days), but there are things that still wow me like people writing game engines. I tried working on game engines briefly and I never got anywhere.
I eventually realized that I just don’t care about game engines or making games for that matter. I wasn’t willing to put in the effort. Watching other people build game engines is more of a spectator sport for me. And that’s fine.
But when I do find something that makes me really happy, it keeps me up thinking all day and night about it.
Now should defenders also make dependency graphs too? Sure, but they should be making lists first before dependency graphs and making sure things are up to date, that they assume limited trust, and that resources are isolated. Then they should make dependency graphs.
“Defenders have to think in list and graphs and manage a billion things. Attackers just have to look at a few things.”
For example, if you are trying to say “run this task at this specific time in Los Angeles time” and you put a specific UTC offset, it just doesn’t make any sense. Los Angeles time consists of two offsets, and yet here you openly put down something wrong. You need to put into your system literally Los Angeles time (like America/Los_Angeles) because that’s what you want. You didn’t want an offset. Dear god why are you putting an offset then?
Or you want to define a specific date but then you put into your system a date with a time like 12/12/2024 00:00. Like you started off with “I want to define a specific date” and here you openly just put a time. You had to make up 00:00. Why are you just doing random things without thinking?
Space engineering is wildly more expensive so development and progress cycles are even longer.
Now my presence is to use this grade A type of implementation because I like very solid software and I’ve done it so many times now that I can bang it out in a coding interview. Or explain it to a team so they can implement it.
But your average app is like a grade D. Even Instagram or Snapchat where I’m never too sure if my stories are going to be in order if my connection fails or even though it lets me cancel an upload, if I do it slightly too late the app fails to cancel because it can’t keep track of its own state through a state transition.
So for 99% of apps, I want them to put a redundant toast. I do not believe they can build solid software with proper state management. At least the redundant toast lets me know it did go through. A lack of toast doesn’t mean it went through because some people barely can implement error handling.
My job has hard problems, chill people, and I care a lot about that we build.
We do have boring work and spaghetti code in places but to be honest, I unload all of that onto junior devs.
For example, in the US, the Supreme Court is able to expand its powers, but it can always be overridden by the legislative branch by design. The executive branch doesn’t even have to follow the Supreme Court’s rulings. And the legislative and executive can be replaced by citizens.
By design, the US Constitution basically has an infinite loop of checks and balances - there is always another institution that can override one institution without breaking any rules.
That said, the buck does stop, but it stops at the people. The problem is that people do need to be well-informed and vigilant to for the this scheme to work out, but to be honest, that is not a problem specifically with democracy — it’s just a general societal problem.
There have been recent Supreme Court rulings that many would say are disagreeable, but we’re not doing anything about it because a lot of citizens either support it or just don’t care. But if citizens did, we could easily undo those decisions using the rules set out by the Constitution. So the problem really lies more with the people than the system.
Now I’m not familiar with the Brazilian political system — who checks the Supreme Court there? I just know the US Constitution had a LOT of people working on it and they covered a lot of bases.
You can negotiate with a bank to get your own rate and then implement your own secure transaction processing. Visa is still required though.
I have worked at companies that bypassed those middlemen. Many companies don’t do it because they are okay with paying higher fees so they don’t have to deal with that extra headache, or because they work at smaller companies that think Stripe, Block, and PayPal invented payment processing when Visa and banks have been around for decades longer.
My risk to my credit number being stolen is honestly low. The risk is the merchant providing a substandard service 99% of the time, and an OAuth style payment flow does nothing for that.
Someone like Amazon who is a trusted merchant already negotiates fees with their banks and they likely already have an extremely low fee rate.
What Stripe, Square and PayPal provide is a service for integrators who don’t want to spend money talking to a bank, negotiating a rate, and then implementing the required security to execute their own transactions.
I uphold a certain quality of work and I expect my peers to do the same. Everyone makes mistakes but even mistakes can be modeled.
But Postgres slowly improved and then got better than MySQL while MySQL stagnated. The most basic bugs persisted, basic features never got added and consistency never seemed to be a point of improvement.