1,048 karma · joined February 28, 2012
It would be a much better case for regulating if there were some external payer.
Source? This would be worrisome.
I mean, nitpick I guess? but cheap energy isn't a positive externality of the energy industry, it's the product.
"The Python interpreter has a number of functions and types built into it that are always available." [1]
"Long option values can be split across multiple lines simply by indenting the continuation lines." [2]
Agree with your teacher in that the first one seems fine. [1] https://docs.python.org/3/library/functions.html
https://www.walesonline.co.uk/news/uk-news/uk-twitchers-floc...
>- Why wasn't the degree granted?"
According to [1]
"in 1968, he defended his PhD thesis on "Computational Complexity and Program Structure" at Harvard under the supervision of Patrick C. Fischer. However, Ritchie never officially received his PhD degree as he did not submit a bound copy of his dissertation to the Harvard library, a requirement for the degree."
So he had bigger and better things to do than mere filing. Plausible!
[1] https://en.m.wikipedia.org/wiki/Dennis_Ritchie#:~:text=Howev....
Settings > Accessibility > Force Enable Zoom
overrides this (h/t someone HN when I complained about this too).
Research: https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2769645
And yet somehow we continue to hire and manage software developers, evaluating their performance holistically.
What is it about teaching that supposedly makes skill so uniquely opaque to administrators that it's (teach to the test) XOR (pay by seniority).
Why?
The higher cognitive function that leads you to read books about quitting could be exactly the mechanism the GP describes.
If books can help you quit, less bookish people will quit less, all else equal.
Well said, though presumably if your work was _BBC Tokyo correspondent_, that would be a weird argument.
I feel like self-contained, self-describing, potentially self-validating data types like in the parent comment would tend to be complexity-reducing as long as they don't mix in control flow or deep deep inheritance hierarchies, though.
If your experience is limited to academic projects, grinding leetcode, even competitive programming, you've done things where first one is nearly always optimal.
Once you are on a team optimizing for continued feature delivery over time, the cognitive load of picking up and understanding old code full of raw maps and strings starts to justify the overhead of a bit more semantic scaffolding in places.
IMO the necessary judgment has to be learned even by smart, academically talented people.
https://www.history.com/.amp/topics/christmas/santa-claus#si...
US GDP in 2021 was $23 trillion. US GNI (national income) im 2021: was $23.3 trillion.
"monetary flows"
You're right, remittances and foreign aid are income but not GDP.
Please explain where income comes from if not from the sum of goods and services produced?
If we accept that service providers are going to price discriminate, then we accept that they are going to price discriminate on _some_ imperfect heuristic.
It seems to me that you have to argue
(A) Businesses should not price discriminate
Or
(B) price discrimination based on marginal features is okay but this particular feature (needing SSO) isn't very predictive
Or
(C) This particular feature might be predictive, but security is too important to be part of a willingness-to-pay heuristic, so it's unethical to use this particular feature in this way.
C seems like the argument a lot of people here are obliquely making.