Fair point! In many libraries, you can go to the library and check out DVDs as well.
That could be a way to make videos available for free but inconvenient enough that people would pay for a more convenient way, just as they do with books.
> There's no real room to evade tariffs outside of misclassifying or misrepresenting imports
There’s an entire field of “tariff engineering” that’s experienced an understandable boom in demand in the last 12 months. That’s technically about avoiding or reducing tariffs rather than evading them, but tomato/tomato…
> I haven't seen one in 15 years across 5+ different companies.
Were you a solo founder of 5 companies? I literally cannot fathom that you worked at 5 even very modest-sized tech companies and never experienced a colleague with some level of what we’d call neurodivergent.
I can’t validate that the rate is 38%, but I find it hard to believe it’s under 5% and if it’s 5%, you’d be hard-pressed to avoid crossing paths across 5 companies and 15 years.
There's neurodivergant and there's neurodivergant. I've definitely worked with oddballs and nerds and various atypical folks. But there's a massive gulf between them and someone with legit no questions about it autism.
What’s the alternative that’s better? Having a 5/1 or 1/1 ARM just means that your current house’s mortgage would also be more expensive because your 3% mortgage would have adjusted upward by now.
If you’re willing to have your current mortgage be more expensive to avoid the “downside of being locked into a low payment, you could just pretend your mortgage had adjusted and go buy a house that suits your needs better.
Aren't most people who are "locked into house" a seller that's removed from the market, but also a buyer that's removed from the market?
I can see how someone who decides to keep their current house to use as a rental and buy a new owner-occupied property would tend to increase house purchase prices slightly (but also increase rental availability and lower rent prices slightly), but also think that’s a tiny minority of current homeowners.
Thanks, that is helpful. I can see from it there's lots of plane traffic flying just south of the river, from East to West, into Heathrow airport, from 5am onwards.
If everyone costs the system $10, and the five people pay $8, $9, $10, $11, and $12, respectively, I think it’s a mistake to say only the last two net-positive taxpayers are paying for the system.
It’s also what critical thinkers do when evaluating “what percentage full of shit do I think this author is?”
If a glaring innumeracy or terrible estimate is in the article, why did the author include that? What was their angle? Does that make me trust the rest of the article more or less?
I agree that some random leetcode-hard problem is not a good indicator, but if you can’t write fizzbuzz or can’t sum an array of integers, you’ve given me important data about your skills as a programmer on that day.
I’ve never had an interview question that asked me to do something straightforward. If I did get a question like that, I would be immediately suspicious about what the catch was.
For campus, we ask very straightforward questions to try to weed out the very lowest of coding fluency at that early stage. (Basically to try to guard against late track changers who haven’t actually coded but know that the SWE market is better than whatever their original interest was.)
If I ask that of a senior candidate, it’s because I got a whiff of “this candidate might not be able to code at all, and I’d like to save us both some time and frustration.”
We ask of every candidate. At least half the time, I wish I'd done so before getting invested in the "experience" portion, when that ends up not actually translating to ability (and believe me, I am trying to help them to succeed)
The beauty is, even a simple exercise answered quickly like "sum of integers" provides ample opportunity to learn a lot about how they think.
Start digging in to testability, requirement changes, etc. Change it to a rolling sum (producing a sequence instead of a single value). Do they use an array or an iterator? Do they output straight to the console, or produce an actual function? Could the numbers come from other sources (database, queue, etc)? What might the tradeoffs be? If there's something they are unfamiliar with, are they quick on the uptake if you explain it? And so on.
I don’t know, I still think 22 year old me might still flub even a simple on the fly question (granting that I do my first internship with IBM writing lots of code when I was 20).
If they flub half of the time and go on seven such interviews, they have over a 99% chance to pass at least one of them.
And that’s for someone with only a 50/50 success rate at summing an array of integers. Do you want to hire someone for a software role who is an underdog to be able to sum an array of ints?
Interviews are learning experiences, you get better at it the more often you do them. My first comment in this thread was that this guy was just a learning experience for these students. Summing integers is easy, understanding someone’s rushed description of what they want done along with rushing to code or write a solution on a whiteboard is the hard part.
How do you make good or bad resolvable? Is a piece of code being used by Tyson Foods okay? A vegetarian software engineer who contributed to the package might say “no, that use contributes to the killing of animals for food, which is bad.”
If you need to evaluate all the context to know whether a license is usable, it makes it extremely hard for “good guys” to use code under that license. (It’s generally very easy for “bad guys” to just use it quietly.)
It is not a computer program, but a an ethics problem. We can solve it by thinking of the context and the ethics of it.
I realize it is the topic of this thread, but OP did not mention anything in relation to licenses, and was just talking about good and bad not existing objectively (without context).
I think, if we came with a specific situation, most people with similar values might reach the same good/bad verdict, and a small minority might reach a different one.
I believe the Tyson Foods example is overly simplistic and still too abstract, because one can be vegetarian for many reasons, and these would affect the "verdict". In the real world, if we were working on that piece of software the question would be: Does the implementation of this specific hr SAP module for Tyson foods by me, a vegetarian against animals suffering unnecessarily, etc. as opposed as the abstract idea of any piece of code and any vegetarian. If a friend called you: I have this situation at work, they are asking me to write software to do x and I feel bad about it, etc. etc. I bet it would not be difficult to know what is right and wrong. Another aspect of it is, we could agree something is wrong (bad) and you might still do it. That does not mean there is no objective reality, just that you might not have options or that your values might not be the ones you think (or say) they are, for example.
But in a typical FOSS scenario, your decision to open source the code and Tyson Foods decision to use it are decoupled. You don't know who all the potential users are when you open source it, so you can't consider all the concrete cases and make sure that the license reflects them. In the same way Tyson Foods isn't going to contact all the creators of libraries they want to use and ask if their concrete use case is in line with the creator's ethics.
Agreed. This would be a logistical nightmare on both ends. Especially if the licenses can be revoked if and when Tyson Foods decides to change some of their policies and/or the author decides to change their political views.
I believe that this would effectively make sure that nobody uses these licenses.
> I think, if we came with a specific situation, most people with similar values might reach the same good/bad verdict, and a small minority might reach a different one.
All you doing is agreeing how the context of the situation is determining if the action is "good" or "bad" (which was my point)
reply