YAGNI. Seriously. That pretty much describes the main problem with Java - "maybe we'll need this coffee maker to also do julienne fries in the future!"
... and, it will be eventually closed. Maybe. Definitely before the program quits. Not sure that it'll be closed before you run out of file handles, though.
My current employer, when hiring me, said "Have you ever looked at the Firefox codebase? No? Good. Here, take this Firefox bug. Fix it by Monday, or at least analyze the root cause, and let's talk about it during the interview".
Needless to say, they had no interest in Firefox per se. It was just a cool open-source project, and a good way to give me "actual work" while making it plainly obvious that it wasn't for their own benefit/ they weren't looking for "free code via tech interviews"
That's still 1.6-5.3 times more than they used to be, according to the original claim. Seems less dramatic than 5-10x but for an apartment that already feels tiny, it's a lot.
> That chicken is a confit [...] plus cost of employees to serve
Is that really a thing in the US? Honest question, I'm confused. The justification for requiring 20% tips (and considering you "nasty" if you leave any less) is that the waiters in the US are not even paid minimum wage, they rely on the customer tips to make a living. So, which one is it? If they rely on the tips, surely they don't cost the restaurant owners any significant amount of $$, do they?
I think what many Americans fail to appreciate is that all the safety guarantees that come with deniability + lax security have a (pretty big) cost, one that YOU are paying in the end.
Like - US for a very long while didn't use chip & PIN - but it was simple to deny the transactions and as a consumer you were somewhat well protected, despite lax security. But this generates large costs, and perversely, the cost/uncertainty affects the small businesses the most.
Yes, when I use 3DSecure for an online transaction, the bank shifts the burden of proof to me (a correctly-authorized 2-factor transaction cannot be simply challenged with a complaint at the bank, I have to prove that it wasn't me). Still, it's hard to argue that 2-factor for online transactions is consumer-unfriendly, even if the consumer loses the deniability
On our ops dashboard we see stuff like number of ID syncs, number of events processed (by type), etc. - I'd argue that is something is truly "broken" you see it.
If you're using funnel analytics to decide that the product is broken - i'd say you probably do something wrong.
it's not silly, it's infuriating. I can't pay at the pump with my card, because I don't have a US ZIP (I do have a perfectly secret PIN that I can use everywhere in Europe, but US doesn't seem to care about that)
What if I play it on blackjack? It may be incredibly poor judgement on my part, by what if I totally intended to win & pay it back, with interest?
My point is that if I didn't actually do anything to deceive you into giving me money (like, I didn't claim that I have a millionaire father who's going to give you the money in case I lose at blackjack) - then it's not really deception on my part; it's just error and/or poor judgement on your part for handing me the money.
His advice flies in the face of every negotiation course/book. Yes, you must know the range they are willing to pay; but once you know... you don't wait for them to make an offer, you ask something at the high end of what they're willing to offer, possibly above (but close enough to) the higher margin(* ).
The one who first names the price forms the baseline of negotiation. Say their range is 100-140k. If you say, "tell me what you would pay" and they say 100K, you're screwed, no way you can say "150k" from there and still be taken seriously. If OTOH you say 150k at the start and are lucky enough to get the answer "no way we can give you more than 140k", from there it's a simple job of asking for an extra concession that you know they can make ("Hmm... ok, say I could accept 140k, but only if the company allows me to WFH when I need to")
( *) Of course, not from the start. He's right about that. They need to be invested in the hiring - if they already spent a lot of effort trying to assess your skill before making an offer, you're in a much better position to ask a lot. Presuming that they like you, of course.
> I'm arguing that "unfamiliar" does not necessarily mean "hard to find".
Yes it does, it literally means "not having knowledge or experience of" and thus it is hard(er) on people. Familiar does not necessarily mean "all websites do it the same", familiar literally means "well known from long or close association". It may be association with something else, not even software (see apple's skeuomorphic design with the original iOS).
It may be worthwhile to make something unfamiliar (i.e. "harder") - but you should have good reason to do so. "Hur dur I creative designer" is not good reason.
> Sadly, you can't set the value of an index in an array like that in the top level in C, only inside functions.
This is not exactly true. An assignment is a value, you can do e.g.
int a = b[x] = 0;
(which implies that you can do your array-index assignments at the global level by creating nonsensical/unused variables and initializing them).