HNHacker News
TopNewBestAskShowJobs

jkingsbery

2,170 karma · joined January 19, 2010

submissionscomments
jkingsbery··on Ask HN: How to negotiate continuing to work remotely?
I see a ton of comments on this post that indicate how much power an individual can have. Many people point out negotiating from a position of power, for example by doing good work, or by being prepared to leave for a more remote friendly company. Honest question: Why do you think involving lawyers would improve the situation? Why do you think this is a matter of employment law?

For what it's worth, I worked for a company where most software engineers were unionized. The union accomplished almost nothing on behalf of employees besides taking a chunk of their pay check and otherwise complicating situations that people are able to work out themselves.

jkingsbery··on Hatetris – Tetris which always gives you the worst piece
And here's 7

ฆࡄາໃݣඪජݹಏ૫ຊरಗق༨൪صඨʐএЩටลڝ௨෨ଈݚЩචƙɕࢳ৩ฅڥࢲටະࠇ௨ٴໃɛ௨ٴແߛ௨൞ໃק௧ڠງƷஶكɑݹத෮ແࢭ௧ຂຽஈਢචƚܥ௨ۼถݷಏقܧɒԩঘญகϡࡆϿߟƑؾϿॻ౦ʜວॿޠظܪܦ౻ॸࠋ

jkingsbery··on Hatetris – Tetris which always gives you the worst piece
Got to 6!

హइໃџИටଛڭ௧پಭݪбඩಸݞహࡄȤເ௨ඤʈঅஜѸໃѣۑචʈஆಏ੬ܯཧ૭ටໞݹਓsະࠇஶƣฅяడقແߛ௨ೱٱݸಳ൞ະࢭ௨ඞНݷహइЖݪ௧چະঀ౻ටПݸԫ૫ଠݹ౻ಅໄ൰ళҸཟࢭলฃฅॾవඩಸܭСࡏVپƏοSྌਔ

jkingsbery··on White House eyes subsidies for nuclear plants to help meet climate targets
Whether subsidies are a good idea or not in general for nuclear is an interesting question. The article states that the current plan is to give production tax credits - tax credits for energy produced. Such a subsidy, which does not help mitigate the up front capital costs, would therefore not really address the root problem in the US.

To the more general question though: subsidies are to incentivize people (or companies) to do a thing (or do more of a thing). In the case of nuclear power, the timelines involved in building a power plant are so long, and given the uncertainty of having the same tax credits staying in place for long enough to impact financial plans, it seems unlikely that it would actually have the effect we'd want on nuclear power production.

jkingsbery··on Ask HN: How would you store 10PB of data for your startup today?
Besides what others have asked:

What are your access patterns? You say "no queries need to be performed," but are you accessing via key-value look-ups? Or ranged look-ups?

What do customers do with the pictures? Do customers browse through images and videos?

You mention it's "user generated data" - how many users (order of magnitude)? How often is new data generated? Does the dataset grow, or can you evict older images/videos (so you have a moving window of data through time)?

Besides your immediate needs, what other needs do you anticipate? (Will you need to do ML/Analytics work on the data in the future? Will you want to generate thumbnails from the existing data set?)

What my experience is based on: I was formerly Senior Software Engineer/Principal Engineer for a team that managed reporting tools for internal reporting of Amazon's Retail data. The team I was on provides tools for accessing several years worth of Amazon.com's order/shipment data.

jkingsbery··on The real reason to end the death penalty
Even in the US, "left vs right" on the death penalty is an oversimplification. A pretty good summary can be found here: https://deathpenaltyinfo.org/facts-and-research/religious-st... ... Anecdotally, as a religious person, I'd say that most Catholics I know either oppose the death penalty or would want it to be much more limited than it is now.
jkingsbery··on CSS is no longer a core skill
A few problems with this:

1. I'm not sure "internal" vs. "external" is the right dividing line. I've worked for start-ups where doing something scrappy with our external look-and-feel was fine, and on the other hand my previous project was an "internal" tool that had thousands of internal users, which demanded a higher quality.

2. I've seen cases where internal standards slow things down, but I've also seen cases where internal standards speed things up. Yes, if you have to do the same amount of work every time to maintain a high bar, that would slow down CSS work. But we would never say that about bugs in logic, instead we'd say "Use the foo function that so-and-so wrote" and. The problem isn't the standards themselves, it's what corners are cut to achieve them. A "high standard" CSS can help remove friction by helping developers avoid thinking about things that are irrelevant to the task assigned, leading to a more sustainable overall design (see https://www.martinfowler.com/bliki/DesignStaminaHypothesis.h...).

2a. To be more specific about the last point, having a clear design language (we are allowed to use these font sizes and no others; we are allowed to have buttons that look like this one, that one, or the other one; we have to use these colors) forces constraints on developers that can make the overall code base easier to understand and maintain. The constraints remove the possibility of engineers who aren't all that strong in designing user interactions from designing something confusing or buggy.

3. I don't know what this "beforetime" is. I've been working in the industry since 2008. That was three years before Bootstrap's first release which the article mentions as some epochal dividing line. During the entirety of my career, CSS has always been a technology that many developers just don't want to deal with. The only change has been that now a team has 1 person (or maybe 2 people) who are good at writing new CSS definitions on top of a pre-existing CSS framework, whereas before a team had 1 person (or maybe 2 people) who made all the CSS definitions from scratch.

jkingsbery··on Show HN: The game where you test your offside decision-making skills against VAR
Got it, that's helpful! In a lot of the ones I got wrong, however, it looked pretty clearly that the arm was the thing the VAR used to declare a player offsides.
jkingsbery··on Fitted Filtration Efficiency of Double Masking During the COVID-19 Pandemic
Just wait until you've heard my idea for quadrupling the filtering of SARS-CoV2 particles...
jkingsbery··on YouTube CEO Susan Wojcicki Gets 'Freedom Expression' Award Sponsored by YouTube
There was also an episode of The Office (US) about this. Dwight suggests to Jim he starts an employee-of-the-month award, then rigs it so Jim wins so that everyone turns on Jim. Jim at least had the good sense to decline the award.
jkingsbery··on Show HN: The game where you test your offside decision-making skills against VAR
My understanding is that the offside rule is based on where the players' feet are, but based on this VAR is doing it based off of any body part. Do I have the rule right? Or is the VAR bad at distinguishing feet from other body parts?

In any case, well done! In North American sports, there's a push to use a similar sort of system in baseball for calling balls/strikes, I'd be curious to compare my judgement against the computer system they're testing in some minor leagues.

jkingsbery··on Amazon 2020 Letter to Shareholders
The way I've started to look at it is: I don't expect I would be able to make $10 in that hour, but if I could skip doing chore X (cleaning, going to the store, whatever) and instead spend an hour going to the park with my wife and kids, or having lunch with them, or going for a run, that experience would be worth $10 (or probably more) to me. So it's not about trading time for money, it's about paying to trade an unpleasurable experience (e.g. standing in line at the grocery store) for a pleasurable one (drawing or having a hand stand competition with your kids).
jkingsbery··on Write tasks not user stories – Linear Method
> User stories are time-consuming to write and read and can silo engineers into a mechanical role where they code to the issue requirements instead of thinking about the user experience holistically at the product level.

A few problems with this:

1. User Stories, as described by Mike Cohn or in some other textbook description, are supposed to be light weight. They are time consuming to write only in so far it takes time to understand what is the 1-2 sentence summary of the thing to be done.

2. User stories are intentionally ambiguous to avoid "siloing engineers into a mechanical role where they code to the issue requirements." A User story says, "When you're done writing code, here's the thing that needs to happen. Tasks are useful when there isn't much ambiguity, but I've certainly worked with developers who take the approach "I wrote the database table task, I did the Java code task, I did the JavaScript front end task, I'm done" without sanity checking if everything works together.

3. A User Story literally says what the User Experience should be like. Even if that were the wrong approach, I fail to understand how telling developers "Here's what the User Experience should be like and why they want to do that thing" prevents them from thinking about the user.

Overall, even if there's some truth here, this is a silly article. Stating "User stories evolved over twenty years ago" isn't helpful, because tasks evolved even longer ago. User stories are supposed to be "short and simple" and "describe the task in plain language." I'm really left wondering if the things they call "tasks" and "user stories" are the same thing that I use for those terms.

jkingsbery··on US agencies call for pause in Johnson & Johnson vaccine
I haven't seen any news articles provide a point of comparison of how the number of people receiving the J&J vaccine and experiencing this particular kind of clotting. The first academic-ish article on the subject I could find indicated a typical baseline of 15.7 cases per million (https://www.ahajournals.org/doi/full/10.1161/STROKEAHA.116.0...). If that's true, I don't get it - why would we stop roll out of any vaccine when the baseline (15.7) is higher than the problem that is being claimed (1 per million)?
jkingsbery··on China is betting that the West is in irreversible decline
I just had to refresh and it showed for me.
jkingsbery··on Just Be Rich
> It's less a tutorial or analysis and more a thinly veiled attempt to ease concerns about wealth inequality.

Given in Graham's essay he comes out and discusses the Gini coefficient, it doesn't seem like a "thinly veiled" anything. The point of the essay is to discuss how much inequality itself matters (as opposed to, say poverty, lack of access to health care, or other things other people are raising as legitimate concerns).

> What he fails to mention is that concerns about wealth inequality aren't concerned with how wealth was generated but rather the growing wealth gap that has accelerated in recent decades.

My take away from Graham's article is that, all else being equal, we should care about how wealth was generated, and the gap itself is less important.

> Tech has made startups both cheaper and easier but only for a small percentage of people.

This is probably true, but again I think it misses the point that Graham is making: Creating a new company is overall simpler today than it was in the 1970's and 1980's, and so the "small percentage of people" who can start companies now is larger than it was 40 years ago.

> Paul paints a rosy picture but doesn't mention that incomes for lower and middle-class families have fallen since the 80s.

For a more thorough and balanced analysis of what this author refers to, see Russ Roberts's series on these questions: https://www.youtube.com/playlist?list=PLRZf05zFBLXIKLD3blbnn... . There are several factors that make these long-term trend analyses hard: changing family compositions, changing quality of goods, and challenges with price indexes.

jkingsbery··on Sweden's Pandemic Experiment
I had a similar reaction. The article definitely doesn't follow the Inverted Pyramid approach (https://en.wikipedia.org/wiki/Inverted_pyramid_(journalism) ).
jkingsbery··on Programming is hard
While it is true that there are lot of resources for people getting started and getting into programming, and that "Beginners walk a very fertile ground," I think that misses the point. Something about our industry and trade has been exclusionary. Perhaps unintentionally. The "anyone can program" movement seems to me to be in large about about addressing this - you don't have to be a particular gender or ethnicity to write code (either just for fun, or for a living).

It is true, as the article points out, that programming is hard. But we teach lots of things in school that are hard that no one will do professionally. Calculus is hard too, but more people take AP Calculus in the US (based on https://secure-media.collegeboard.org/digitalServices/pdf/re..., around 400k) than take AP Computer Science (based on same, around 188k). I don't think Calculus is that much more valuable, nor is Computer Science that much harder, to justify such a large gap. The point is, even among STEM subject, there's a taboo around computer science and programming.

But it is equally true that it's not helpful to tell people that programming is a walk in the park, and the article does a good job explaining that. Perhaps better than saying "programming is hard," or "programming is easy," we say "programming is worth it" and leave it there.

jkingsbery··on Janet Yellen to call for global minimum corporate tax rate of 21%
I'd be curious to know more details about the proposals. It seems hard to look at corporate taxes in isolation from other things corporations do and the other taxes that people pay. Some countries choose to provide fewer government services, or are able to provide government services for less money. It seems only fair that these countries would have lower corporate tax rates. Corporate tax rates also seem like they would be affected by what the capital gains tax is: the government can get money out of a group of people by either taxing the company they own or by taxing the capital gains they realize when their company does well. It also does matter what kind of other taxes a company will need to pay (payroll taxes), or what other taxes citizens pay (whether or not they pay VAT).

It's hard to imagine a global minimum corporate tax rate not being exploited by special interests. Just because companies avoid taxes today by switching countries, won't mean that they won't find other loop holes tomorrow. It's easy to imagine countries saying "sure, our nominal corporate tax rate is 21%, but <special protected industry X> has to have a different rate because of <cultural and historical specific reasons to that country>.

jkingsbery··on Yes, experts will lie to you sometimes
Agreed... but who is "you" in the sentence?

Unfortunately, it seems to me experts increasingly think that their domain is the only one that matters, so they (as experts) should make decisions without consulting on whether someone in a different field that might have more, better information.

Also, the "least-lethal way to fail" argument assumes that there aren't other lethal trade-offs coming from down stream impact in areas outside an expert's vision.

jkingsbery··on Google’s copying of the Java SE API was fair use [pdf]
Yes, a good point, it does. Breyer's opinion does say the court is arguing that the API is copy-righted, but used under fair use (as opposed to not copy-righted, in which case fair use doesn't make sense). But my point about what seems to be the main distinction making it copy-right-but-fair-use is the declaration vs. implementation concern, a distinction that logically exists (so I think the outcome is correct!), but does not seem to legally exist.
jkingsbery··on Google’s copying of the Java SE API was fair use [pdf]
I 100% agree that this is the right outcome. Any other outcome would be a nightmare for software developers and would inhibit the development of products.

But the dissent raises an interesting point. I think it shows how the crafting of legislation by people who are wholly ignorant of technology can create problems. While programmers recognize the difference between an API and it's implementation, Thomas makes the interesting point that the relevant legislation does not (page 4 of the dissent):

> Copyright law generally protects works of authorship. Patent law generally protects inventions or discoveries. A library of code straddles these two categories. It is highly functional like an invention; yet as a writing, it is also a work of authorship. Faced with something that could fit in either space, Congress chose copyright, and it included declaring code in that protection.

> The Copyright Act expressly protects computer code. It recognizes that a “computer program” is protected by copyright. See 17 U. S. C. §§109(b), 117, 506(a). And it defines “‘computer program’” as “a set of statements or instructions to be used directly or indirectly in a computer in order to bring about a certain result.” §101. That definition clearly covers declaring code—sets of statements that indirectly perform computer functions by triggering prewritten implementing code.

While it clearly is in the Court's prerogative to interpret law, there seems to be a pretty good case that the court didn't provide an interpretation for a gap in the law, it instead fixed a law that didn't make sense.

jkingsbery··on We Killed Expertise (And why we need it back.) (2017)
> Trustworthy journalists wouldn't print something without multiple sources.

There are unfortunately too many recent examples of media organizations that do just this, publishing articles with a single source that turn out to be biased or unreliable.

jkingsbery··on We Killed Expertise (And why we need it back.) (2017)
I agree with a lot in this article, but the author touched, in passing, on an interesting (and lower stakes) example: baseball.

The experts in baseball for a long time thought baseball should be played a certain way. Bill James starting proposing radically different approaches that were later put into practice by Billy Beane (described in Moneyball) and later by Theo Epstein (who led the front office for the Red Sox and Cubs organizations when they won the World Series the article mentions). The story of baseball over the past 10-15 years has been about ignoring one set of experts as the industry has developed a new set of experts.

Another problem with experts I would have like to see this article address is when experts overstep their area of expertise. Experts can tell us facts from their area of expertise, but when we have complicated problems that involve trade-offs from areas outside the expert's area, that can lead to bad decisions.

jkingsbery··on Move Slow and Make Things
I had a similar reaction. It's a nice April fool's joke, but I hoped for an actual counter-balance to "move fast and break things." The book that taught me the value of moving slow in programming was Test Driven Development by Kent Beck, who ironically spent several years at Facebook.
jkingsbery··on How to Manage a Dark Ages Estate
At the risk of stating something obvious, Wikipedia's article on the Carolingian Renaissance is a good place to start: https://en.wikipedia.org/wiki/Carolingian_Renaissance

The term I've seen in books I've read lately is "Early Middle Ages" (see https://en.wikipedia.org/wiki/Middle_Ages#Early_Middle_Ages).

"Dark Ages" is arguably applicable to the time around 500-800, although the other problem is that there's also another commonly referred-to time period known as the Dark Ages, the Greek Dark Ages, from around 1100 BC - 750 BC.

jkingsbery··on Gallup: U.S. church membership dips below 50% for first time
That was the premise that an investigative journalist had in mind when he started an investigation to demonstrate precisely what you said to the rest of the world. Rather than starting with his assumptions and arguing against a strawman, he went to verify every fact he could and went to talk to experts. Instead of proving Christianity is a sham, he ended up converting to Christianity and writing a book about it: https://www.amazon.com/Case-Christ-Journalists-Personal-Inve... .

TL;DR: Christians wouldn't say that we base our beliefs on a collection of stories. We base our beliefs in the historical fact of the Resurrection. Perhaps we'll find out we're wrong some day, but having considered the best evidence we have (and the book I linked to walks through why that evidence is compelling), Christianity is a reasonable position to hold.

jkingsbery··on The WHO-China search for the origins of the coronavirus
> Accidents happen. Even if it was a lab accident, it's not a reason to be outraged with the Chinese government.

Agreed! Whatever did cause COVID-19, the outbreak was made worse by a lack of transparency by the CCP. It seems like no matter what, the WHO report is unlikely to discuss that much. Which is a shame, because with more transparency into what happened we would be better able to stop the next COVID-19 from happening.

jkingsbery··on Yes, experts will lie to you sometimes
> You’re probably not being punked; you’re being babied. So if and when you go fact-checking the experts’ recommendations, remember that they probably do have their assessment of your own best interests in mind. Think of them as an overprotective parent, not as an enemy.

But... we're not babies. I get that many experts have good intentions. But treating adults like babies is a good way to come across as an enemy.

> When experts make guesses about whether the public can handle the truth, they aren’t acting as experts; they’re acting as amateurs. They’re winging it.

This is a start, but it's bigger than this. Experts are amateurs at understanding all the nuances of anyone's daily lives beyond their own. It's not just that they say "I'll lie here, because it will be good for people," and they misjudge how people handle lies. It's that very often experts have revealed that they don't understand what it means for something to be "good for people" beyond their narrow expertise.

jkingsbery··on The WHO-China search for the origins of the coronavirus
So, to summarize-the-summary: there are four possible theories:

1. Direct-jump from bat population

2. Started in bats, came to humans through intermediate animal

3. Came from frozen food outside of China

4. Lab accident.

I used to think the lab accident theory was crazy, because it sounds like a science fiction movie. Not an impossible theory, just a crazy one.

But according to this article, despite a year of investigation, (1) is unlikely because we haven't found anyone that interacted with the nearest bat population hundred of miles away that didn't work in the virus lab in Wuhan and that caught the virus, (2) is unlikely because we would have found the intermediate animal by now, (3) is unlikely because the first case found was in China (and not somewhere else... if frozen food had the virus, the food would have had it before it was frozen, and someone else would have had it), and (4) is unlikely because a government famous for blocking information and is paranoid about how it is perceived domestically and internationally says "No, trust us on this one."

At some point, crazy theories become the most likely. Hopefully I'm wrong though, and they find an explanation that isn't "lab accident." It seems like we should be studying viruses and sharing that information with each other, and accidents like this will make it more likely that such research doesn't happen.

← PreviousPage 7 of 21Next →