Here's a description of the "Automata Processor", a phrase I hadn't heard before [1]:
> Micron’s new Automata Processor (AP) architecture exploits the very high and natural level of parallelism found in DRAM technologies to achieve native-hardware implementation of nondeterministic
finite automata (NFAs). The use of DRAM technology to implement the NFA states provides high capacity and therefore provide extraordinary parallelism for pattern recognition. In this paper, we give an overview of AP's architecture, programming and applications.
Sitting here, in your chair, you can definitely do this no problem, right? So find a group of people who will simulate the interview environment for you.
Also, there are strategies for managing the time problem. 20 minutes is a bit fast for understand => ask questions => implement => test on this problem. But you can organize the code so that if you run out of time it's still clear you knew how to solve the problem and can code your way out of a wet paper bag. E.g., I would pass an answer that got everything correct but didn't get around to implementing isPalindrome() or isSoCS() before the 20 minutes was up, especially if the candidate could give a ~1 minute description of how to implement those functions. (I would also give more than 20 minutes.)
I interviewed at a place that started by having me do a HackerRank test online, and complimented me on my code and comments. Then the in person interview ended with a coding test involving a much simpler problem which I assume I failed, from my perspective due to the pressure of limited time and people talking at me. It's hard for me to figure out what was going on, unless they basically thought they were testing to see if I cheated on the first test.
However, I haven't experienced repeated failure of a consistent type, so I'm not particularly motivated to worry about this sort of thing. I do know that different companies have radically different processes, so if someone tells you "you're not a good fit" it may be completely true and not a negative judgement at all (even if that's how they mean it).
It so happens that I got my undergraduate degree about ten years later than is typical, and thus I can pass for someone that much younger than me, at present. So in an interview, it is tempting for me to give away my age by reminiscing about computing in the 80s, and that could have caused me to be rejected a couple times but I will never know for sure...
How do you know how often someone smokes or drinks? How do you determine what level of smoking/drinking is harmful enough to merit higher premiums? How do you dispute the insurance provider's claim that your cancer is really your fault because you chose to live in a city with bad air?
You're missing the entire thesis of the article. The thesis is that Finland (et al)'s education and healthcare systems are more efficient because they are socialized. Given one binary comparison between condition A and condition B (Finland vs. US), some causal speculation is justified. Given dozens of such comparisons, all coming out to the same result, your case becomes anti-empirical.
soru's comment on this thread provides one nice rational model that tries to explain why. But the much more important point is that our rationalizations are slaves to the empirical data. Not the other way around.
> Given dozens of such comparisons, all coming out to the same result, your case becomes anti-empirical.
As others in this thread have pointed out, Finland vs. US is not a good comparison, Europe vs the US would be. We can socialize medicine in individual states with good results (see: MA) but US-wide? With 332+ million people? With all the differences in costs of living in different parts of the country?
When the EU rolls out a single-payer system for the entire Eurozone then we'll have something to compare against but the entire nation of Finland has less people (5.7 million) than New York City (8 million) and is a monoculture, to boot.
Given that the mishmash of european systems has much wider variance probably than US internal schemes do, I find the argument 'but US is too" complex not entirely convincing.
Given how much of the current scientific and technological context of our civilization comes from the US, and there are lot of single payer schemes working in other countries, I would find the "we don't want to" argument more convincing than "it's too complex for us".
Anyway, I don't know the nuts and bolts of any of the health care systems but generally when political will manifests itself people are capable of all sorts of things if they are within the realm of the laws of physics.
It's not like health care was rocket science. The best bang for buck comes from providing just the cheapest things modern medicine has come with within the reach of all. It's not surgeries and MRI machines and all that capital intensive stuff. A nurse with a basic kit could achieve all sorts of improved health outcomes in his/her patients.
The point of this report is that the empirical evidence contradicts your hypothesis. These sorts of broad-strokes, ultra-rationalist arguments should be set aside whenever data is available.
Data is available on rapid price inflation that coincides with central planning initiatives in the US. Data also exists showing the systemic risks to nations created by these systems, such as the looming global demographic crisis created by the combination of social welfare systems and the baby boom.
We aren't talking about those abstract ideas, we are talking about health care and it's associated access and cost. As such, the data shows us the United States fares worse than similar countries on the measures of access and cost (both to the individual and the state)[1]. The United States also has the most "free market-like" system of comparable countries. How can it be that costs are so high and outcomes are no better if we are closer to a free market than others?
Causes of price inflation and the looming demographic crisis are not "abstract ideas."
For literally decades the US did not open a single medical school due to lobbying from the medical industry. Even though we've tried to reverse the trend since the 90s, there are still fewer medical schools today than there were 100 years ago. When the government decides how many doctors there will be, it may get the number right or it may get the number wrong. But that's nothing akin to "free market-like." And it's a major part of the explanation why US doctors make 2x+ what their counterparts in countries like Germany make.
During the New Deal era regulations wage caps were put on workers in the hopes of staving off inflation. Employers, wanting to entice good employees to work for them sought to get around these wage caps by offering health insurance. This then spread like wildfire, coincides with the time healthcare inflation separated from general inflation, and began the trend towards a lack of price transparency.
Most of the differences in outcomes between us and other wealthy nations amount to lifestyle/culture much more-so than affordability and availability. Americans are very obese. Not having to pay a copay to visit the doctor is not going to change that. But obesity means we'll have more problems with newborns, lower life expectancy, etc.
> there are still fewer medical schools today than there were 100 years ago... it may get the number right or it may get the number wrong... And it's a major part of the explanation why US doctors make 2x+ what their counterparts in countries like Germany make.
> Most of the differences in outcomes between us and other wealthy nations amount to lifestyle/culture much more-so than affordability and availability. Americans are very obese. Not having to pay a copay to visit the doctor is not going to change that. But obesity means we'll have more problems with newborns, lower life expectancy, etc.
> During the New Deal era regulations wage caps were put on workers in the hopes of staving off inflation. Employers, wanting to entice good employees to work for them sought to get around these wage caps by offering health insurance. This then spread like wildfire, coincides with the time healthcare inflation separated from general inflation, and began the trend towards a lack of price transparency.
Except, of course, in the countries where it didn't spread like wildfire. Why all this crazy post-hoc history-building when you can just... empirically observe how the natural experiment played out?
Your modus operandi in this thread is the start with an ideology and then derive conclusions that are often wholly inconsistent with observed reality. There's nothing wrong with premises or theory-building, but when the data flatly contradict your conclusions... well, that's the difference between reality and fantasy.
By your link we're 52nd in doctors per capita. That's not great. Plus I'd already noted that we've made a concerted effort to undo the damage since the 90s. Are you suggesting that supply and demand has no impact whatsoever on the wages doctors are capable of demanding? Do you believe that artificially restricting the supply for decades has had no impact on wages whatsoever?
Higher adolescent pregnancy rates, higher rates of HIV, etc.
=== Most experts estimate that modern medical care delivered to individual patients—such as physician and hospital treatments covered by health insurance—has only been responsible for between ten and twenty-five percent of the improvements in life expectancy over the last century. The rest has come from changes in the social determinants of health, particularly in early childhood.===
So best case scenario access and affordability to healthcare accounts for about 25% of improvements in life expectancy. Except the majority of people already have access to healthcare in the US. It's not as available and affordable as we'd like, and we're talking about how best to improve availability and affordability, but it's a tiny fraction of the problem of why US health outcomes are so bad.
It's clear you still don't understand my critique.
> By your link we're 52nd in doctors per capita. That's not great.
I think this sort of argument is innumerate. Statistical sciences provide us with many ways of testing the correlation between "value of care per dollar spent" and "average doctor salary".
None-the-less, I am tempted to point out that Cuba is #2 on this metric ;-)
Regarding the rest of your post, consider actually reading that New Yorker piece. The things you think it says, it DEFINITELY does actually not say.
== And it's a major part of the explanation why US doctors make 2x+ what their counterparts in countries like Germany make.==
That is a nice thought, fortunately NPR has done the actual reporting on this. It seems like the answer is government interference [1]:
"But the biggest reason German health costs are so much lower, experts say, is that doctors are paid less. This largely reflects Germany's concerted efforts to keep costs down over the past two decades."
On administrative costs it seems like government mandates on benefits and payment rates keep those costs 50% lower. Also, they have an employer-based system:
"On top of that, administrative costs are almost 50 percent lower. That's not because the German health system is simple and streamlined. With its employer-based system, multiple insurers and ever-changing rules, German health care is as complicated in many ways as the U.S. system. But administration is much simpler because nearly everybody gets the same benefits, payment rates are uniform and virtually everybody is covered."
==Most of the differences in outcomes between us and other wealthy nations amount to lifestyle/culture much more-so than affordability and availability.==
You have provided no evidence to back up this claim. What makes you so certain that it's true?
==Not having to pay a copay to visit the doctor is not going to change that.==
Might this encourage more people to visit health providers more frequently? This might lead to earlier detection/treatment and lower long-term costs. Why have you dismissed this potential outcome?
>"But the biggest reason German health costs are so much lower, experts say, is that doctors are paid less. This largely reflects Germany's concerted efforts to keep costs down over the past two decades."
Yes, this supports my statement. I said the medical lobby has artificially constricted the supply of doctors. Limited supply means higher wages. I'm not familiar with the German system, they may have done other things such as price fixing to keep wages lower. Personally, I'd prefer having "too many" doctors. This would give me more personal choice to choose the one I like the most while simultaneously keeping prices reasonable.
>You have provided no evidence to back up this claim. What makes you so certain that it's true?
===Most experts estimate that modern medical care delivered to individual patients—such as physician and hospital treatments covered by health insurance—has only been responsible for between ten and twenty-five percent of the improvements in life expectancy over the last century. The rest has come from changes in the social determinants of health, particularly in early childhood.====
>Why have you dismissed this potential outcome?
As noted above the majority of improved health outcomes are not the result of access to healthcare at all. Let's be generous and use the highest percentage in the stat provided above: 25%. So now we're only at 25% of healthcare gains at all, and the fraction of that that isn't actually affordable either by the individual themselves, through their insurance coverage, or provided by charity. We're talking a really tiny fraction of gains here.
== I said the medical lobby has artificially constricted the supply of doctors.==
In the free market, money equals influence. As long as AMA determines who is/isn't a doctor, they have an incentive to make it as hard as possible to become a doctor.
==The rest has come from changes in the social determinants of health, particularly in early childhood.==
Now you have to prove that free and easily accessible access to health care won't have a positive impact on the social determinants of health. It stands to reason that part of America's reluctance to visit doctors is rooted in the historical costs associated with visiting doctors. If we can remove that stigma through cheaper and more accessible care, it stands to reason that we can improve the social determinants of health over the long term.
Here's an example: In Canada, one can visit a dietician as part of their health insurance, this could have a positive impact on obesity, which would lead to healthier population.
> Here's the first article that came up when I googled the subject... [cites article laying down the case for increased social welfare funding, which doesn't even justify the stated claim]
Oy... talk about (not quite) winning a battle but losing the war.
Also, this whole methodology toward argumentation just reinforces the top-level critique. The important word in "start with the data" is not "data", it's "START". I.e., begin by understanding the problem. Then solve the problem. Don't walk around with a hammer trying to bash things.
When the factory closes, whose car do you repair? When the factory closes, whose plumbing do you fix? When the factory closes, whose house to you build?
As all of these cities aptly demonstrate, plumbing and auto mechanic jobs aren't a panacea for disappearing factory jobs.
Aside from the "nuh uh; uh huh" nature of this exchange, I really don't understand what your position.
> I didn't say you don't own the photo, I said you don't have control over it. Those are two very different things.
I'm not sure what youre definition of "control" is, but based upon the arguments you've made about "control" above, I assume you mean it in some absolute sense.
Ownership definitely implies control. He can use DMCA to compel a third party to stop publishing his photo, for example. How is that not "control"?
Your definition of control seems to be somehow about capability or power, rather than normative ethics or legal right. Which is a rather absurd way of talking about this issue.
In that sense of control, I don't even control my own body. Someone who is stronger than me can hurt me; can rape me; can even kill me. I have no control.
Of course, for normative reasons, we make laws against other people controlling me in certain ways even though they have the power to do so.
Data privacy is no different. The discussion is not about what degree of control a party is physically capable of exerting. The discussion is about what degree of control the government should grant to each party.
The fact that someone somewhere is capable of hoarding my data, does not imply that this outcome is just or optimal. Your position is a textbook example of the naturalistic fallacy.
That seems to me a bold claim to me - don't actually teach anything, just demand stuff! And behold, by pure magic (and LOTS of selection) we get a handful of successful students who manage to pass, validating this "teaching" style. Is that really what you have in mind?
I'm actually someone who did and does not have a problem with that style. It suits me very well. At university I mostly learned from non-university sources (e.g. using outside text books and ignoring lectures, and doing my own independent research and work on the side). I also finished over 60 edX and Coursera courses during the last five years (some easy, like history of architecture, many hard STEM and medical subjects) - so I like learning by myself. Still, when I go somewhere to be taught and all they tell me is "this is what we want you to be able to do at the end, but you have to go teach yourself" it makes me pretty mad. I had a few such edX courses - you know, if I have to use Youtube and Google I sure can get the necessary knowledge, but then why did I sign up for the course??
There always is plenty of opportunity to let people act independently. Refusing to teach as a way to teach is just lazy and incompetent.
> don't actually teach anything, just demand stuff!
That is not all that bad pedagogy assuming you have reasonable demands that escalate over time. It is to extreme if you never explain anything, but if your teaching style consist primary of forcing students to learn by themselves and explaining only minimum necessary, then I strongly approve.
Giving students everything directly is more incompetent, because it imo results in weaker learning. The goal is not to show how hard-working teacher is, the goal is to produce as many as much capable as possible graduates.
The strawman that makes your argument so brittle is that there are only two positions on the spectrum. The school of technology at Purdue has some of the brightest people I've ever encountered. What makes them extra luminous is their ability to spot common pitfalls novices run into. They learned this by being engineers in industry. Thus, those educators are supremely positioned to find the struggling adulthood novices that are good at fundamental academic skills, and keep them on the path.
Just like Ford Motors tried to convince everyone that they were the best, they eventually believed their own ad copy, and got entrenched in making cars the way that had always made them. And then all of Ford's competitors reverse engineered his logistics, and said "if your time to you is worth saving, then you better start swimming or you'll sink like a stone, for the times, they are a changing".
It worked for Bob Dylan pretty well too, when popular music was dominated by Elvis Presley.
1. learning to struggle successfully is far more important than mastering the chain rule.
2. If you start with excellent students, then you can set those students up to struggle on much harder and deeper questions.
My point, really, is that a curriculum that manages to not "lose" anyone will also fail to strike a good balance between "struggle" and "hand-hold" if 90% of your students start off as "Excellent".
The hardest part about designing a course is figuring out when students should struggle, and when to hold their hands. The answer will vary depending upon the quality of the students. Excellent teaching aimed at excellent students looks very different from excellent teaching aimed at mediocre students. Differentiating instruction is Teaching 101, and differentiation in universities often happens at the institutional or program level.
E.g., are Khan Academy's descriptions of the product rule better than Chicago's Math 160? For certain students, yes. For others, emphatically not! Neither option is "better" in an absolute sense, but each is definitely "better" for any given student.
There is nothing wrong with a course of study that's designed for the top 1% of high school graduates. And admissions mistakes do not equal bad teaching. On the contrary, torpedo'ing the entire curriculum to make sure that every student makes it through would be grossly irresponsible.
I recently had to write a scheduling algorithm for our home-grown operating system. I was running into some very difficult to debug issues, so I asked my TA for help. They had no clue and told me to consult the professor. The professor wouldn't help. Our textbook offered no guidance. We're not allowed to discuss projects whatsoever with other students. So after north of 5 hours spread over a few days of trying to figure out my issue, I gave up. How was this a beneficial experience?
Not being able to discuss your project with other students in an operating systems class is insane. You need to get input for the subtle bugs that are going to occur.
There is a reason why operating systems and compiler classes are notorious.
However, if 5 hours debugging is too much, I'd get out of the field now. Try debugging something for MONTHS while your bosses are all hanging over your shoulder.
In addition, 5 hours spread out is a problem. Subtle bugs require intense focus and you should be doing 5 hours per session. You have to inload and control a lot of details, most of which are irrelevant, in order to find the thing that really matters.
I really wish I could teach a "debugging class" where I hand groups real code with frustrating bugs. Unfortunately, no CS department would ever let me teach it as it would destroy enrollment.
I agree - 5 hours really isn't that much. I've spent much more time than that on single issues in the past, and it's by no means something that's scaring me out of the field. I should've spent more time in a single session hunting down the issue, but I didn't quite have the time (or motivation after seemingly making no progress) when it was only one of a few things I had to work on that week. One of my issues with that class in general was the complete lack of guidance on how we should go about debugging our operating systems' issues. The only method mentioned by my TA was to print more variables, which isn't incredibly useful if the kernel won't boot or if the print function isn't working. And the issues would compound as the projects were often dependent on previous projects. One of the tasks was to implement asynchronous signal handling through registered callback functions, which is quite difficult to do if you didn't get the scheduling algorithm working properly in the previous project. It felt like the class was designed to be difficult and not designed for me to learn. I was pretty excited to take an Operating Systems class, despite what I'd heard, and it was the class that left me feeling let down, not the content.
I would personally love a debugging class to get some more varied ideas on how to approach difficult problems. Seeing someone's thought process when debugging something like a kernel would've been really useful.
> Seeing someone's thought process when debugging something like a kernel would've been really useful.
The first thing when doing a kernel is don't be clever. Suboptimal isn't just good--it's preferred. Linear searches are fine. Shell sorts are fine. Arrays are fine even if you have to recopy them a lot. Hashes are too complicated. Trees are too complicated. Randomizing things is too complicated. Until your kernel needs to scale, the "suboptimal" ways are more understandable, and, as a bonus, they sometimes are more optimal as they require less up front overhead.
The second thing is "replace pieces". Because you weren't clever, you can rip out and change chunks with relative ease. It's not "proper", but, if you're on a deadline, sometimes swapping some component and having the bug go away is good enough. Just realize that, if a bug goes away randomly rather than because you understood it and killed it, you have planted a time bomb likely to blow up in your face at the worst moment. :{
The third thing is "hypothesize and THEN test". This drives me crazy with junior folks. If I had a nickel for every time I got the response "I dunno" in reply to "Okay, why did you think doing X would fix things?" I would be a rich man. This is the piece that makes debugging a kernel hard. You have multiple layers of abstraction, and the bug is probably 3 layers away from the thing that triggers it.
Something which I tend to use more for things like kernels than "normal" programming (whatever that means) is that I religiously check and assert on my data structures even at great performance penalty. Having a data structure blow up immediately is far better than soldiering on and getting the malfunction after everything is scrambled.
Something which I am becoming increasingly religious about is that time is an input to my functions that operate on "external" inputs (button presses, RF events, USB events, network packets, etc.). It's a pain sometimes, but when you need to debug something subtle, it is really nice to be able to replay things exactly.
And, a final piece of advice, learn your tools. GDB, for example, is amazingly powerful. Unfortunately, I only seem to learn more about it after the fact. :( I do something really stupid and someone asks "Why didn't you just do <mumble foo mumble> in gdb?" and my response is always "Because I didn't know about it."
I feel like there's always a little crotchetyness in older engineers. I remember being in school right when companies were putting all of their literature online. For electronics, that was such a huge leap forward from having to buy entire books of data sheets for integrated circuits. People on the other side of that divide had the same complaint about a different subject.
"You only looked through the data sheet for 4 hours? Back in my day it might take 4 hours to get the thing to even turn on!"
Stack Overflow. The key to debugging is to not be so arrogant as to assume you are working on a problem for the first time. In fact, this is the underlying premise of rubber duck debugging. You tell an inanimate object what you did to get where you are now, and as you enumerate and elucidate, your faulty assumption is often laid bare.
I've seen something similar at other institutions.
The School of Engineering, in this case, is trying to teach something more than just domain knowledge about engineering disciplines. The goal is to take those "18 year-old polyglots" and turn them into world-class problem solvers.
You see this is every elite educational program. Mathematics at Chicago. Computer Science at Carnegie Mellon. Engineering at MIT. Their programs have a difference in kind, and are very intentionally not built for "the average college student".
It's good that there's an alternative path within the same institution for those students who need to focus their efforts on baseline competence. But it's also good that strong programs expect more out of their students.
You've simply recited the fallacy. You've framed the very debate in terminology that assumes you are correct.
But that's what all entrenched interests do.
Schools of technology are not simply teaching baseline competence. They teach the theory of the same subjects, with a more hands on approach emphasized.
They are showing up to civil war reenactments with tanks and planes. The old timers are in a huff about it, but what else is new?
> You've simply recited the fallacy. You've framed the very debate in terminology that assumes you are correct.
I'm not sure what this means.
My claim is that educational programs designed for the top 1% of students are not well-suited to educating the next 10%. And vice-versa. (E.g.: A Chicago math student is often not well-served by the sort of "calculus for engineers" courses you'll find at state college branch campuses. Also, a college senior struggling through their Calculus requirement is not at all well-served by Chicago's honors mathematics program. Neither approach is better in an absolute sense; but in each case, one is clearly better relative to the particular student.)
This is not some sort of tautology. It's a serious pedagogical hypothesis with decades of empirical research probing its truth value.
> They are showing up to civil war reenactments with tanks and planes.
I can't speak to Purdue specifically. In the cases I know about, the very explicit purpose of these alternative degree programs is to build a department by admitting students that the name-brand program rejects, or who fail out of the weeder courses. The "old timers" aren't in a huff about it, because they had no interest in admititng those students to their existing programs in the first place.
I suppose I would argue that in the evolutionary sense, a university accumulates it's marketable value in units of accomplishment by it's people. To the extent that any one person can unequivocally demonstrate exceptional value through their own accomplishments, by inventing and commercializing valuable goods and services that improve the overall well being of humanity, the particular buildings those people occupied 30 years prior, and the particular people that educated them for those few months, are of no particular interest to the university. The university wants prestige because it attacts more prestige, which they can monetize.
I can agree that in the sense that the people best positioned to become the most educated should be paired with the best equipped to effect that teaching. However, at some point we're arguing over what is the best position to be in, which is not in anyway objective.
I would say, to firm that up even more, every school can point to their accomplishments, and the graduates/professors that worked on them, as to why they are in rarified air. You can look through Wikipedia at all of these renowned scientists, and who their advisors were, and who their students were. So you can say they stood on the shoulders of giants, and also stood tall for others to perch even higher.
But not a single one of those heroes of science should rightly be remembered primarily or even secondarily because of where they studied.
The underlying fallacy is that you can only learn the best skills from the best people in a short window if time in your early adulthood.
> Micron’s new Automata Processor (AP) architecture exploits the very high and natural level of parallelism found in DRAM technologies to achieve native-hardware implementation of nondeterministic finite automata (NFAs). The use of DRAM technology to implement the NFA states provides high capacity and therefore provide extraordinary parallelism for pattern recognition. In this paper, we give an overview of AP's architecture, programming and applications.
[1] https://www.cs.virginia.edu/~skadron/Papers/wang_APoverview_...