HN user

Others

636 karma

Student @ The George Washington University, studying CS Does undergraduate research on Operating Systems

[ my public key: https://keybase.io/peach; my proof: https://keybase.io/peach/sigs/vvRgNs-IaMSuxB1De1oulrRMYXN7jdyWf764wxbjo3k ]

Posts0
Comments137
View on HN
No posts found.

I appreciate the fact that IMB is trying to present a optimistic view of the future. Not all sci-fi needs to be negative or dystopian, and his remains plausible despite its optimism.

I think if you’d rather read about the downfall of the Culture, then you’ve somewhat profoundly missed the point of Ian’s writing.

1. Exercise good judgment about what projects are “away team-able”. Be okay saying “this needs to be done by our team” even when that’s hard. Otherwise you’ll end up with tricky features implemented by people who don’t understand the full context (this sucks very badly)

2. Make sure the amount of process matches the amount of complexity. If the change is very simple or only a few lines, make it trivial to submit code changes that will pass review. (So have really good automated style checks/test suites.) If the change is complex, make sure you’re doing design reviews before implementation, to ensure the away team doesn’t waste time with bad implementation strategies

How does that work when the thing you want to change is a complex micro-service with a public API? Do you want to spin up your own version of that service and own it forever? Even if you’re okay with that, you’ll not have the clients the older version has

Open-source model works for libraries, or small changes in service code (where the maintenance burden is trivial). But it doesn’t work for complex services with high maintenance burdens

This should never happen on Prime Video. Major breach of customer trust.

If it’s happened to you please call customer service and complain. If they can’t fix it or refund you, please get in touch with me and I will try and get it fixed for you

I feel like this is easier if you’re a non-lever-puller. If you think it’s wrong to pull the lever if it causes anyone’s death who wasn’t dying anyway, then most of these are easy.

Except the “you can’t see the track” one I suppose :P

I think (3b) isn’t true, since the sanctions are effecting every part of Russia’s economy. And while the petroleum industry is like 40% of their exports by revenue, the other 60% is obviously significant. Also from a Russian point of view, the difficulty importing and lack of access to the international banking system may be more painful.

In fact if the west could target everything except oil, they probably would (since that’s the most critical export that Europe needs).

Your overall point still stands though. Your argument is strong. It’s not practical for Russia to simply redirect their flow to maintain “business as usual”.

1. The parent comment is referring to waste in the environmental sense. Nature does not care how expensive the trash was--just the volume/composition 2. It's a big stretch to call AirPods "disposable" I (and many others) keep them for years. In the long run everything is rubbish; an expensive electronic device that lasts for years and years is not "disposable"

I think this comment implicitly assumes that just because people survive on less than 18, it’s livable

That’s not necessarily true, since many people around or below the poverty line rely on government assistance to survive.

Also, the federal minimum is so low and our social safety net is so weak (virtually non existent), many people would be instantly screwed by any sort of drastic/expensive event. (Like unexpected illness or the loss of a job or a car accident.) Is a wage livable if you can’t live through times of trouble?

The issue here is that YouTube (and other platforms) encourage this. It works, in that if you ask people to like comment and subscribe, they like comment and subscribe more. (And that boosts your standing within the system getting you more impressions.)

Plenty of good creators do this (as it works), just to keep up with their peers. It really has nothing to do with the quality of the rest of their content. Don’t blame the player, blame the game IMO

Killing TurboTax 5 years ago

I think this is fundamentally a regressive idea. Currently the very poor pay zero (or effectively zero) income taxes. No matter how you structure the sales tax, you cannot go below zero. (I think negative sales tax is not actually realistic, nor particularly progressive.)

A system that only taxes spending fundamentally has problems in that the richer people can afford to save and invest.

1) People are calling this an “insurrection” because it’s so directly an attack on country leadership. (Whereas the incidents you’re referencing are predominantly riots and attacks on the police.) There may be hypocrisy here, but I don’t think that word is a part of it

2) I think the major difference in the left’s eyes is that those protests were against police brutality and racism, whereas this is an attack on our democracy and an attempt to overrule a free and fair election. Motives matter

3) Invading the capital building wielding deadly weapons is (pretty objectively) more serious than attacking the outside of a single federal courthouse (not to minimize that of course)

I think that squashing commits sometimes make sense. Like is it worth retain two commits if the second one is just fixing the formatting, logs, or metrics from the first one?

Also in open source I think it can be easier to keep track of the history if one commit == one PR.

I agree people kinda just cargo cult it though, good to be thoughtful about the trade offs for your team or project.

Maybe I just misread this article but it really sounds like they don’t own YOLOv5. It’s someone else’s project they think is cool and are amplifying. If that’s right, then I think it’s reasonable to defer naming to whoever actually made the project!

I feel like hashed passwords are somewhere in between “completely okay to publish” and secret.

With good crypto, it should be difficult to make a password hash useful even if it is public. (Although weak passwords can make this worse if salts are also made public.) However as part of a defense in depth strategy, you probably don’t want to release them publicly.

I feel like there are different levels of secrecy at play here. I think the article means things more like ssh keys or api keys specifically.

I love Google's products, and I put up with the fact that they harvest my data. But to have such terrible support for their services is absolutely ludicrous. I've seen too many stories of people losing their content, email addresses, services they rely on, or livelihoods. All because Google is too cheap to provide a reasonable way for customers to talk to a person about their problem.

I understand this is expensive and hard, but to be a company worth 100s of billions, and still neglect this is unacceptable. I think that there is a social responsibility that comes with running such a large and important web service, a responsibility that Google is neglecting.