HNHacker News
TopNewBestAskShowJobs

peterwwillis

1 karma · joined March 4, 2021

submissionscomments
peterwwillis··on Teacher's low-tech laptop hack to display handwritten notes for online class
Because people shouldn't have to increase their risk of death significantly just to have the privilege of having housing and food. The comparison is ridiculous. It's like saying, you already have a low risk of death by colon cancer, so why not eat things that dramatically increase your risk of cancer. Do you want them to die?
peterwwillis··on AWS IAM is having issues again
So, just to clarify: if a "customer" who happens to employ tens of thousands of people also employs non-US citizens (such as the DoD's foreign national IT contractors), then non-US citizens would have access to GovCloud.
peterwwillis··on This electrical transmission tower has a problem
It would be great if the author had just made a blog post and tweeted it. This sort of seems like useful information, which will suck to lose when this tweet inevitably disappears and isn't updated later with new information.

Tweets make excellent momentary entertainment. Let's stop using them for anything else.

peterwwillis··on Teacher's low-tech laptop hack to display handwritten notes for online class
The point you've just tried to make is that it's fine to force teachers to risk death in a classroom, because they might also get hit by a car driving into work? You need to work on your rhetoric.
peterwwillis··on Ask HN: How do people become experts?
How do you become an expert? Pick a thing and focus on it intensely. Keep coming up with questions. The harder it is to find an answer, the closer you come to being an expert. At the end of your journey, you will still have questions. When you are one of the few people who can find the answers, you're the expert.

> It seems like the important stuff that differentiates the expert from someone with casual knowledge isn't documented.

Experience is the biggest driver of expertise, and most people just don't document the things they find out unless they have to. But often the information does exist, if it's been around for a while. Ask yourself how the expert became an expert. What other fields might they have studied? What jobs might they have had? What similar subjects might reveal some of the details?

> Sometimes its not, but the knowledge seems to be locked in the brains of a few individuals or organizations and can only be unlocked if your'e lucky enough for them to take you in

Yep. Working with others is an important part of building expertise. Building relationships opens up new pathways to find information.

> On the other hand, a minority of the experts I know are nearly completely self taught and I'm struggling to figure out how to manage.

Relax. Expertise is not something you can force, it comes with time. Some things are easier than others, but if you continue to slowly work at it, you'll get better.

> Generally as a hobbysit Like I said every time I've tried to deep dive I reach a point where I'm not sure what I'm missing, where to find it.

Not every fish can be found by diving deep. Searching for knowledge is a normal part of building expertise; don't stress if you're not immediately sure where to look. If you get stuck, start again from the basics and question your assumptions. Try thinking about it from both a low-level and high-level view. Try to change your perspective. You will invariably come up with new places to search.

As you search, write down questions. If you get stuck on one, start looking into another. Remember to take breaks and get enough sleep, exercise, good diet. We learn best when we are stress-free, healthy and happy.

peterwwillis··on Teacher's low-tech laptop hack to display handwritten notes for online class
The teachers will work themselves into an early grave just to help the kids. Nobody's doing that for teachers. Teachers are more at risk of actually dying when in-person learning is forced on them as some school districts have done. And they have their livelihood to think about (many live a little more than paycheck to paycheck).

Comparatively, the kids aren't dying, they don't have bills to pay, they don't work overtime. Their parents may even be able to pull them from school, or homeschool. Worst case they might be held back a year.

The students will survive this, but the teachers literally might not.

peterwwillis··on Teacher's low-tech laptop hack to display handwritten notes for online class
This is what I think of when I think "innovation": a different perspective. Not lost in the weeds of details, but a thousand miles above them.
peterwwillis··on The Spite Software License
If I had a dime for every time a big company I've worked at has investigated the licenses of the software it uses, I'd have fifty cents.

People tend to forget that big companies are really just collections of normal people who are not lawyers and don't even think about licenses. If 5 levels of managers haven't all been explicitly instructed to read random software licenses or they're fired, the engineer's not gonna do it unless they feel like it, and most don't feel like it. It mostly only comes up when legal goes out of their way to make a stink about it, and they're not just continuously demanding license information.

peterwwillis··on Why do so many people want us back in the office?
> We can do so much better, for ourselves, our customers and society if we stop being so frightened or so certain of the future.

That would require removing emotion from our biology. Maybe shoot for something smaller.

peterwwillis··on Happy 1600M epoch second
Knowing Splunk, I'm surprised it was a regex and not a bunch of strchr()s
peterwwillis··on C’s Biggest Mistake (2009)
Agreed - in that I write it in Perl if I need it to just work right now. Perl is still, to me, the most useful programming language for completing a generic program in the smallest amount of time. (Part of that is due to CPAN, and part to the gazillion built-in features of Perl 5)
peterwwillis··on Security by obscurity is underrated
Risk is not just a formula. Risk is also "formulaic": when you get people used to an idea, they become blind to things outside of that idea, and there in lies the danger.

If your corporate IT group regularly asks users to send in their passwords via e-mail in order to perform some remote maintenance, then the users will be habituated to sending their password to a familiar e-mail address. If someone from outside their company asked them for their password, they would immediately say no. But an e-mail with the right "From: " address, they would quickly fall for. So it becomes easy to trick the users into sending their password to an attacker in some circumstances, because of the assumptions they make.

Security by obscurity is just another form of this: a practice which isn't really secure, but people may think is secure, because it seems to avoid the simplest, most stupid attacks. But literally any action you take could prevent the simplest, most stupid attacks. That doesn't mean that any action you take makes you "more secure".

Hiding a key under a door mat or in a sun visor isn't "more secure" than leaving it in plain view. Anyone who's not a total moron will find it, and if that's your whole security posture, you're screwed.

peterwwillis··on How Do Routers Work, Really?
I think the simplest way for people familiar with PCs to visualize it are the FirePOWER devices. Network cards plugged into some slot have embedded chips which can be programmed to, say, filter specific kinds of traffic, or pass it onto the host CPU for more advanced logic. While the machine's central CPU runs a web interface, manages local databases, downloads updates, manages clusters, records metrics, etc. And either can even be hot-pluggable, interchangeable blades in a larger machine chassis.

Protocol-wise, isn't it common now for the NP on higher end stuff to handle L4 and higher protocols? Or are those still largely managed by the CPU?

peterwwillis··on The Fed now owns nearly 1/3 of all U.S. mortgages
So.... Is it a stupid time to get a mortgage and buy a house, or a fantastic time?
peterwwillis··on A curated list of falsehoods programmers believe
I didn't see a falsehoods list from the perspective of a sysadmin. Time to start writing a blog post....
peterwwillis··on Desolate English path has killed more than 100 people (2017)
This reads like Lovecraft!
peterwwillis··on Does storing bread in the fridge make it last longer? (2019)
I actually had a bread box at one point, and the bread got moldy after two days. Maybe it just needed to be cleaned, or maybe it trapped moisture and heat?
peterwwillis··on How to take back control of /etc/resolv.conf on Linux (2018)
I'm lazy, and I've been doing this on my own computers for over a decade. I wouldn't do it on a box that anyone else uses. And I've had to do the normal fixes for some VPN software when the network blackholes any DNS traffic not going to their server IPs. Otherwise it's worked out fine for me
peterwwillis··on Show HN: A proactive way of securing your Linux server
A dynamic IP filtering list is still reactive because you haven't actually secured the box or its services. You've just made it slightly inconvenient to brute force. You might as well use port knocking, because even with a fancy schmancy authentication system (and the attack surface of a custom web app...) I can MITM your active connections just fine either way, or spoof your whitelisted IP.

I know everybody likes Fail2ban, but these two iptables rules (or something just like them) actually work better and don't fill up your logs:

  iptables -t mangle -A PREROUTING -p tcp --dport ssh -m conntrack --ctstate NEW -m recent --set
  iptables -t mangle -A PREROUTING -p tcp --dport ssh -m conntrack --ctstate NEW -m recent --update --seconds 60 --hitcount 4 -j DROP
To actually protect the network layer, use some kind of VPN with MFA.
peterwwillis··on Police-issued "courtesy cards" help friends and family out of minor infractions
We have tons of preferential treatment in our justice system, it's not really a secret. For example, economic preferential treatment. If you have lots of money, you can get out on bail easily. If you're poor, you may lose your job, maybe your kid (social services), etc, if you can't afford bail. If you get arrested on some minor charge and you have $80 cash in your wallet, you can be released immediately rather than wait overnight for a judge to arraign you in the morning. Did you know foreign nationals can buy residency in U.S.? Not citizenship, but residency; I think it's ~$300,000.

Unlike Lady Justice, cops are not blind at all - they can pick and choose when to enforce the law. I forget what it's called, but the police are literally given the option for some laws to just not enforce the law if they don't want to. If the cop is in a good mood, they can decide to just let it slide. If they're in a bad mood (or they don't like the color of your skin) they might prefer to enforce it.

peterwwillis··on Bottlerocket, an open source Linux distribution built to run containers
I haven't dug into the engineering behind this yet, but my main concern with any custom Linux distribution is it often ends up as a waste of engineering.

It's pretty easy to write your own Distro and pair it down to the essentials, and pairing it down that way allows you to strip out complexity, making it easier and more reliable to patch it. But that then means you are now maintaining this custom thing forever. If you're Amazon, that might be fine, but I suspect that this will be dropped when it is no longer profitable or a competing project supplants it - meaning in 5 years this thing might be gone. (A common theme of custom Linux distributions)

And then there's troubleshooting. With a stripped-down distro, you will eventually need more tools to debug the thing, meaning you have to build and maintain packages to do that. Bottlerocket's answer to this is "run them in containers and use our API!", but I'm not sold on this. Have you ever tried to do debugging between host and container, or container to container? There's a lot of b.s. you have to hop through, and most Unix tools were not written with it in mind. I highly doubt that it will magically work for everything. If that's the case, then this "don't worry, because magic" idea is not really saving you work over maintaining a traditional OS.

Moreover, you don't need a custom distro to do live patching. There are simple tricks you can use to juggle files and processes during a live patch, to say nothing of "checkpoint process && 'mv old_file new_file' && thaw process", etc. Kernels support live patching too. So if the argument is "well it's easier to patch", i'm not sure you're not trading away "easy" in one place for "pain in the ass" in another (see above). All of this also argues that it's just as effective to treat live-patched systems as you treat immutable infrastructure, and I'm not convinced of that argument either. The former is just more complex, and complexity attracts failures.

Ultimately I think what you'll find is Bottlerocket will get a niche following, but also some people will get annoyed by it and go back to regular distros which already have well defined methods.

peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
You absolutely should not ship updates by pulling from an unversioned tag; it's bad for a number of reasons. There's some simple ways to avoid it:

  # In your CI pipeline, something like this:
  $ cat Dockerfile  
  ARG release_tag
  FROM baseimg:${release_tag}
  # etc; i think the container metadata keeps the base version, or you can store it in the container with a RUN line
  
  $ base_version_tag=$(./get-latest-versioned-tag.sh some-docker-repo:my_prefix/my_image:stable)
  $ new_container_version=$(./make-new-version.sh)
  $ docker build -t my_img:${new_container_version} --build-arg release_tag=${base_version_tag}
Then you run your tests on the new image, maybe do a gradual deployment, and can quickly roll back to the last base image or skip broken versions. Your own container version is always rolling-forward, and you can revert the base image version at any time.

If you do this with a specific stable tree (like debian:8-stable or something) you should only get security updates, but if you use :latest, that's a total nightmare.

peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
I've been a regular Python user for a decade and every Python app I've ever used has worked on stock Python. And vendor builds often ship with patches that make it work better on the OS in question. But I can see how devs often want bleeding edge releases.

From a stability, reliability, and CI/CD performance standpoint, I would discourage building your own Python. Things break more the more often your base version changes.

peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
Correct, you have to do both.
peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
I can't edit my old comment, but it's extremely disturbing that I got downvoted so much. What I described is literally the best practice.

If you don't use Docker containers, use some other form of Immutable Infrastructure like Packer VM images. But those are huge and clunky, so you should really get used to Docker containers. You could instead make Linux packages, but they don't make for as Immutable a system as the OS state constantly changes, and packaging is more work in general.

peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
Literally any change in your system can break. It matters what you do once it breaks, and what I describe makes the whole thing much more repeatable and easier to recover from.

Docker containers builds are extremely repeatable. You run some software called Artifactory, which keeps the built versions of your artifacts, including base image tags. You store your applications in there, as well as the Docker containers that you built. If you need to go back a version, you pull it out of Artifactory. This is industry standard at this point.

peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
Uh, no, you don't ever overwrite a release. You build new versions, test them, deploy them, and if you find a bug along the way, you roll back. You can pin versions of base images and update them when they have security patches, or you can rebuild a base yourself and patch it yourself.

This isn't containerization best practice, this is just plain old Ops best practice that we've been doing for decades. The new part is doing it with containers and building immutable images rather than continuously muting state.

peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
Use your OS to install the stock Python and the stock setuptools, wheel, and virtualenv Python packages. Then make a virtualenv for every single Python application (virtualenv ./some app/). Then make a requirements.txt file with the pip packages you need and their version numbers and install with ./someapp/bin/pip install -r requirements.txt. If you do something bad, rm -r ./someapp/ and start over.
peterwwillis··on Python setuptools v50 breaks pip installation on Debian/Ubuntu
Immutable Infrastructure as Code. Docker containers are the modern gold standard. You can get fairly far on a stock OS with a combination of vendored binaries/libraries and virtualenv/pip, but containers are much simpler.
peterwwillis··on Why Doctors Hate Their Computers (2018)
For the medical professionals here who hate their EHR systems: send the CEO, CTO, President, VP, etc of the company some mail describing your problems, how many people hate it, how much time it drains, one or two ideas on how to make it better, and ask them to forward your mail to the product owners. One of them will hopefully forward it down the chain and in a year maybe one of those things will be less painful.

Also, a bunch of the people reading HN work for different vendors, so light up the comments about specific problems with specific products and we can take them directly to the people who can fix it.

← PreviousPage 5 of 34Next →