"Entrepreneurship is like one of those carnival games where you throw darts or something.
Middle class kids can afford one throw. Most miss. A few hit the target and get a small prize. A very few hit the center bullseye and get a bigger prize. Rags to riches! The American Dream lives on.
Rich kids can afford many throws. If they want to, they can try over and over and over again until they hit something and feel good about themselves. Some keep going until they hit the center bullseye, then they give speeches or write blog posts about "meritocracy" and the salutary effects of hard work.
Poor kids aren't visiting the carnival. They're the ones working it."
MMT is both a description of the current system, a system that is already in place, and a set of policy proposals. So "believing" in MMT may simply mean understanding clearly the process already happening.
I think the argument that MMT is non-normative with respect to inflation is simply false. I'm not an expert, but, like, I've read things other than this article, and in all of them (along with this article) MMT proponents are at pains to point out that "inflation doesn't matter" is a misconception.
As a neutral observer, it feels like if you’re right you could easily show it by literally finding 3 normative judgements on inflation by prominent MMT proponents, and pasting them here, rather than referring to “I’ve read things”
Well, your first would be this article, as I said.
Your second would be the debate between Furman and Kelton on the Ezra Klein podcast, as I said.
I'll dig up a third cite. Like, one of the things in my head is the Kelton vs. Krugman argument, which I read on Krugman's blog, but that's not the best cite, since you're getting Kelton secondhand through Krugman there.
Happy to help. If you'd like to help too, you could cite a source that says MMT'ers feel like inflation doesn't matter.
On the discussion with Kelton and Furman on the Ezra Klein show: I came away frustrated, because I felt that every time Kelton tried to delineate an ideological difference, Furman disagreed that it was in fact a difference. I found it a good discussion on economics, but no clear line-in-the-sand between MMT and orthodox economics.
I have Ctrl-F’d through the article for “inflation” and only see “excessive” inflation as being normatively judged. Which bit do you feel supports your assertion?
> It follows that most of the articles that appear opposed to powerful interests are a) inconsequential, or b) used as a distraction, helping to create the impression that the paper is anything but a powerful conservative force.
It could also be taking on a rival powerful establishment interests, like in Democrats vs Republican type bickering.
Chomsky in his famous Andrew Marr interview addressed Marr's example of Watergate scandal as one part of the establishment defending itself against another part of the establishment, thus allowing the story to be broken. He compared Watergate, which everybody knows about, to a much bigger scandal of the same time, COINTELPRO, which relatively few people have even heard about.
I understand the class of rebuttal you're invoking here, but reversing a string is extremely easy - with or without a library. This is not an academic problem designed to see if a person can study prior to an interview. This is a first pass question designed to see if a person is even acquainted with basic programming. Any such question you could devise would be similarly patronizing or orthogonal to the exact work done on the job.
And yet, despite how easy the question is people still fail it. It's frankly absurd to me that a senior software engineer can fail this question. It's practically a freebie slam dunk for anyone with basic competency. Briefly drop that you can use your language's core function or method to do it. Then declare a new array and iterate through the string backwards, appending each character to the new array. When you're done, collapse the array to a string.
In other words, it's testing if you can write a for loop. How many times in your job do you expect to implement a for loop? I use for loops quite often.
That would be an excellent question to ask during an interview.
If you were interviewing with me, I'd ask you to do the (usually expected) ASCII/array-of-graphemes version first. If you did that, you'd pass, and get a positive shout-out in the feedback session for asking about multibyte chars.
If you, after solving the array-based form, had some ideas or even working code for how to handle multibyte characters directly, without falling back to the standard library of $language's idea of "what is an iterable character-equivalent unit in a string", and demonstrated similar insight in your other interview problems, I'd give a positive shout-out with the addendum that we might be interviewing you for the wrong (too junior) position.
In my experience, most people don't ask about multibyte chars. That's fine, if they solve the problem. It's not a positive or negative. If an interviewer is building questions with hidden "must-ask" gotchas like that, I think they're doing themselves and their candidates a disservice.
Something interesting does happen occasionally when candidates do ask about byte-width (or equivalent less-common but still very important gotchas like pointer/word size, endianness, etc. in relevant problems): some people ask the question, solve the naïve form of the problem, and then offer some thoughts as to how they'd handle the broader multibyte case. But some other people act as if knowing that gotcha means they won't or shouldn't have to continue solving the problem. I've had candidates tell me that they "figured it out" and wanted to go on to the next challenge at that point, without writing a line of code. I've had candidates tell me flat out that writing non-Unicode aware string processing algorithms was unrealistic and a waste of time, and that they wanted a problem that was more real-world or suited to their level of skill. Those things will also get you a shout-out in the interview review session, but not the good kind.
>>Then declare a new array and iterate through the string backwards, appending each character to the new array. When you're done, collapse the array to a string.
a. You can't iterate a 'String' backwards. You need to know the length first. And that requires traversing the string forwards at least once.
b. Once you reach the end you are wasting the effort of revisiting the elements, since you visited them already once.
c. A better option is build a build a double linked list, as you are traversing the list forward.
d. Once you have the double linked list ready, you have pointers to both start and end, and you traverse the way you like.
e. An even better way would be to design a data structure that contains all this meta data at String creation itself.
Class CustomString {
char* headPointer;
char* tailPointer;
int length;
bool isPalindrome;
char* string;
/* Add your interview acrobatic things here */
}
Stuff like this.
Now even though the answer in your comment is correct, they could reject you for not coming up with the answers I gave from point a through e above.
Now imagine some one telling you that, on these grounds, you don't know a semicolon worth programming and are probably a liar.
I hope you understand what's going on here. Every body can be rejected if they don't cut through your cookie cutter.
> a. You can't iterate a 'String' backwards. You need to know the length first. And that requires traversing the string forwards at least once.
That's not at all true in many languages. If a candidate asked "is this string's length known without an O(N) operation on the number of characters in it?" (or knew the answer for the default string constructs in the language they were using for the problem) I'd consider that a positive indicator. If they said what you just said, without consideration for the context, I'd consider that a negative.
This is not a case of someone expecting a given "cookie cutter" solution. Interviewers who do that are doing themselves and their candidates a disservice. This is a case where statements like "I know how strings work because I know how they work in $context" where $context is not what the interview expects you to work in will make a bad impression.
I mean, in languages like Python it can be as simple as `foo[::-1]` or some similar method. Anyone who can give a naive answer like that or
usize len = strlen(foo);
char* bar = malloc(len);
for (int i = 0; i < len; i++) {
bar[i] = foo[len - (i + 1)];
}
and explain why that won't work for unicode strings, I imagine, would pass that particular fizzbuzz test. Bonus points for pointing out the null byte off by one error.
The only competent programmers I can think of that wouldn't be able to come up with that off the top off my head work in embedded or FPGAs where strings are rarely relevant.
Can you traverse an array? Do you know that a string is an array? Do you know how the end or length of a string is represented in your language of choise? Do you know how each character is represented? Do you understand Unicode? Do you understand memory allocation? Is the string being reversed in place or you allocating a new string? What are the space and performance trade-offs between those approaches? I mean, you can fill a whole interview with just this topic. So yes if your answer is string.reverse() then expect some follow-up questions.
There was a period after the collapse of the USSR when there were a lot of private TV channels being set up, which would just show latest Hollywood bootlegs. Some movies which were still in theaters in the US would be shown on TV. That, and random soft porn after children's bed time.
"Entrepreneurship is like one of those carnival games where you throw darts or something.
Middle class kids can afford one throw. Most miss. A few hit the target and get a small prize. A very few hit the center bullseye and get a bigger prize. Rags to riches! The American Dream lives on.
Rich kids can afford many throws. If they want to, they can try over and over and over again until they hit something and feel good about themselves. Some keep going until they hit the center bullseye, then they give speeches or write blog posts about "meritocracy" and the salutary effects of hard work.
Poor kids aren't visiting the carnival. They're the ones working it."