Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
peterwwillis
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
16 ms
·
91.
▲
by
peterwwillis
6y ago
Another way to think of a distributed system is as a threaded application on a multi-core CPU. Break down the interactions within the application by all the logical boundaries and you have a basic distributed system. Typically the input and
92.
▲
by
peterwwillis
6y ago
> Capitalism is a system that runs on human misery, The last two capitalistic organizations I've worked for, all my co-workers were cheery, friendly, helpful, and enjoyed their jobs. The people frustrated were the ones that did thei
93.
▲
by
peterwwillis
6y ago
Serverless is the most overhyped cron job runner in history.
94.
▲
by
peterwwillis
6y ago
You were unfairly downvoted. This is an important question. Sometimes NFS is your only option. When you have legacy applications which nobody is going to rewrite, and you need to scale some operations on a set of files over many nodes, NFS
95.
▲
by
peterwwillis
6y ago
Sure, but it has nothing to do with Capitalism (other than Capitalism giving us two days off a week rather than 0). I'm sure the good people of the Communist Party of the Soviet Union didn't enjoy going to work again after a few d
96.
▲
by
peterwwillis
6y ago
Is there a term for Techie FOMO? Fear Of Not Capitalizing? FONC
97.
▲
by
peterwwillis
6y ago
#9 should be "distributed systems are superior to centralized systems", but the people who made the list must have found it too obvious to include.
98.
▲
by
peterwwillis
6y ago
It always struck me as odd how papers like this make it all make sense, and then you go and run one of these things, and realize that an available system doesn't mean a system that runs well. It just means a system which is capable of
99.
▲
by
peterwwillis
6y ago
It's fantastic for simple tasks, which is why so many people use it. It also turns out that many complex tasks can be reduced to a collection of simple tasks, otherwise known as "a bunch of crappy scripts". I encourage all my
100.
▲
by
peterwwillis
6y ago
Read the ash or dash man pages and just use what they give you. That's pretty much Bourne shell which is pretty much POSIX.
101.
▲
by
peterwwillis
6y ago
I like this write-up! This could be easily turned into a guide for internal teams on ways to look at your own infrastructure and apps and secure them, as no security team is going to do it all for you.
102.
▲
by
peterwwillis
6y ago
I mean, in an ideal world, it should be a low/no-code target. In the sense that you should be able to manipulate K8s as a dumb user to make it do what you need to do, when you need it, without somebody in your way. A company called Q
103.
▲
by
peterwwillis
6y ago
No offense intended, but a generic marketing elevator pitch for a technical product makes me grumpy. I want to see the technical details, but I'm not signing up for your website just to dig for them. So this creates a missed opportunit
104.
▲
by
peterwwillis
6y ago
Please google "affordable housing crisis united states". The first 40 or so stories paint a decent enough picture so I won't link them here. > Housing prices are high because so many people want to live in highly desirable
105.
▲
by
peterwwillis
6y ago
Progress. It's hard to build a society when the people in it don't have anywhere to sleep, or keep their consumer products.
106.
▲
by
peterwwillis
6y ago
How they're built has nothing to do with the immense complexity of building them, it has to do with the land. Everything about a house is tied to the land it sits on. The regulations, the building codes, the architecture, its particula
107.
▲
by
peterwwillis
6y ago
A slightly different take: do things in such a way that scaling isn't a consideration. Figure out if you want to scale or not, and make a thing that either scales, or doesn't. Don't make a thing and then get surprised later
108.
▲
by
peterwwillis
6y ago
Buy this book. It's amazing . It might be my favorite book. It's entirely utilitarian in simplicity and proportions, yet also provides really interesting history and knowledge, and looks nice on a shelf. Anyone who drinks should
109.
▲
by
peterwwillis
6y ago
Not to be that guy that always says "what do you want to do that for?", but it's possible you're looking for the wrong solution. If you buy ingredients and set aside time for specific kinds of recipes, you don't n
110.
▲
by
peterwwillis
6y ago
Replace "Promoted" with "Elected" and you have the US political system.
111.
▲
by
peterwwillis
6y ago
No, you have not locked yourself into anything, you can always grow. Comfort can breed complacency, so my initial advice is to quit your job and try to get a new one that's more demanding. It forces you to kick your own butt into learn
112.
▲
by
peterwwillis
6y ago
Preach!! And this should extend throughout the organization. If Architecture or Security or any other group is making your life miserable, they too should be DevOps'ing, working closely with you, caring about your frustrations that o
113.
▲
by
peterwwillis
6y ago
Yep. It's more of a concept of cooperation than anything else. Which, since it's not a concrete thing, makes it harder for people to understand. But then there's specific practices that arose out of trying to drive best pract
114.
▲
by
peterwwillis
6y ago
I'd cut them a little slack time-wise to track down where they have your address. In a large organization it's common for many products to have their own sets of PII records (and mailing system) and no way to query them all, so if
115.
▲
by
peterwwillis
6y ago
Seems universal in the industry. We also have #yolodevops and #fomodevops. #yolodevops: "We're not going to fix that broken cluster, it's going to be replaced next year with The Cool New Thing.", or, "We don't
116.
▲
by
peterwwillis
6y ago
I haven't; there are definitely some protocol scanning differences. But off the top of my head, you could try 1) do a reverse lookup on a v4 address and then query the name for a v6 address, 2) do DNS probing for a domain you're i
117.
▲
by
peterwwillis
6y ago
> The big drawback for putting complex code in notebooks is that you can't debug it in your IDE. I mean, that's one of the many drawbacks. Executing random independent snippets of code in different stages based on multiple vari
118.
▲
by
peterwwillis
6y ago
DevOps isn't a person or a role. People who are called a 'DevOps Engineer' simply have a bad title. Our industry is very stupid. But yes, they are often Ops, and in general they shouldn't be troubleshooting the applicati
119.
▲
by
peterwwillis
6y ago
Say a plumber installs a new sink in a house. A year later, a weak joint fails and springs a leak, and the plumber is called to fix it. They could ignore the error, charge the person for the repair, and go on with their day. Or they could a
120.
▲
by
peterwwillis
6y ago
This attitude almost always turns into the following: On-call: "Hey devs, I'm being woken up at 3AM because your app sucks. Please fix it." Devs: "Sure, no problem." 4 months go by On-call: "These alerts are st
More ›