13 ms·
Academics, we need to talk
- PaulHoule 11y agoI know you Silicon Valley people think that farmers are a bunch of hicks and an easy target to be disrupted. No f-ing way. Cornell University has many departments that are good, but when I look at the agriculture and vet school they are beyond anybody else. Ag schools do research which is relevant to the technological and business problems of their industry. They do plenty of work on genetic engineering, chemistry and work closely with the likes of Monsanto. They are doing a lot for big ag. They also do research to help small farmers beat pests without pesticides, produce and market (delicious!) Halal meat, even help householders same money and have a better lawn. "Organic" and "Alternative" innovations diffuse into the mainstream. Pesticides are expensive to buy and to apply; if there is a cultural tweak that's cheaper, they'll do it in a flash. When corn prices got high, Cornell promoted dairy farmers to plant cabbages and other crops as an alternative forage. They are always beta testing new crops in our area; Cornell and UNH are finding variants of plants that perform well in the cold Northeast climate, have expanded Wine production and are commercializing new fruits such as the Paw Paw. Their research is relevant, and it is also communicated directly to the public and industry. Cornell Agricultural Extension has an office in every county of the state that you can walk up to and call and get questions answered, go to an event, etc. They work with trade publications, local government. And it is not just New York, they do research on tropical agriculture and run a program to get access to agricultural literature to anyone in poor countries that need it. I would point to that as being a much more real "technology transfer" than the people who are concerned about copyrights and patents.
- skywhopper 11y agoI'm having trouble figuring out how this relates to the article.
- boxy310 11y agoAgricultural engineering has a significantly better interrelationship between academia and industry. Or in other words, ag engineering closes the loop on the R-to-D stage of R&D. As a result, developing practical solutions leads to more research questions, and it forms a tighter virtuous cycle. As a result, it provides a better example than what the initial article implies between tech academia and industry.
- PaulHoule 11y agoIt's a model for emulation.
- willis77 11y agoCornell? It's pronounced "colonel" and it's the highest rank in the military.
- mdwelsh 11y agoI'm not based in Silicon Valley, and I went to Cornell for my undergrad degree.
- verisimilidude 11y agoAn ag researcher usually needs to go out into the surrounding community to get good data or info or otherwise complete his research. They often get their hands dirty on real farms, so naturally they'll be more rooted in the real problems of the industry. I grew up on a cherry orchard near UC Davis, and some group of random students would show up every other year looking for help. This is all much different from a software researcher who can just work from his/her lab (or even bedroom) at all times. It's easy to lose sight of the greater industry when you don't need its (direct) help to complete your research.
- dang 11y ago> I know you Silicon Valley people think that farmers are a bunch of hicks and an easy target to be disrupted. No f-ing way. Please don't make unsubstantive, divisive generalizations like this in HN comments. They make the threads worse, including your otherwise fine comment.
- PaulHoule 11y agoHonestly it is a joke. It drives me nuts though to see how HN people don't get it that better rural broadband would mean they make more money.
- revscat 11y agoStop. There are no "HN people". There are people who post to HN, but the opinions are for the most part surprisingly varied. You are shooting yourself in the foot by making over-generalized comments like this.
- skywhopper 11y ago> I know this sounds like a waste of time because you probably won't get a paper out of it It's unfortunate that a "lessons learned" paper summarizing a sabbatical in industry doing customer-facing work would not be publishable. Surely it's far more useful to other academics than most papers. It'd definitely be more broadly relevant. My wife is a professor in a practical field and I'm always sad to hear what counts as a "good" paper or a publishable article. The big journals in these fields drive the notion of what is and isn't legitimate research. That's the point where what constitutes career-advancing "academic output" has to be changed. But I'm not enough of an insider to have any idea of how to go about doing that.
- boxy310 11y agoI'm sad that journal reputation often trumps practicality of not exactly "breakthrough" articles that are nonetheless extremely interesting. One could argue that blog-reading should form an important part of being well-read in the literature, but again there's the concern over quality of research & insights that leads us to journals in the first place.
- TeMPOraL 11y agoMore and more researchers are also blogging. I think we're seeing a move in this direction.
- mdwelsh 11y agoThe issue is that when doing a sabbatical/internship at a company, it's often not possible to write a paper - either because there's not time, or the company may not want to publish the work (which could be confidential). I wouldn't go to a company expecting to be able to publish about the project.
- NotOscarWilde 11y agoBut if a company wanted to make sabbaticals or science-focused internships more interesting for people on the academic career tracks, it probably could ease their confidential policies and design such internships so that said academics can publish, right? You have mentioned elsewhere that you are looking into how Google can help the academic world focus more on the right industrial questions, and you personally recommend such sabbaticals/internships -- so this seems like a natural step.
- samth 11y agoAcademic research that unknowingly (or sometimes even knowingly) duplicates secret industry work is much more valuable than this discussion indicates. Sure, it's not valuable _to Google_ for someone to publish things they already know. But everyone else benefits. If people at Google want their research to stop being duplicated, they should publish it. Of course, if your goal is that Google adopt your new system in their data centers, then you need to know what they already do. But the problem with that model of research is the initial goal, not the way it's currently executed.
- mdwelsh 11y agoI'm not so worried about duplication by academics -- that does not happen often -- but rather about academic research that's just wrong: makes bad assumptions, uses a flawed methodology, fails to address the general case.
- kenjackson 11y agoIf industry could provide better platforms (up to date, not hand me downs or neutered versions of their real product) then I think you might see better forms of this research. For example, I'd love to improve search relevance, but w/o having access to Google's search engine to build on, it's pretty hard. That's my suggestion. :-)
- mdwelsh 11y agoWhile I agree in general that opening up opportunities for academic-industry collaboration is good, I don't think it's practical for academics to work on problems at true industry scale. Academics don't have access to the resources, personnel, or funding required to do that kind of work. An academic lab can do many things of relevance to industry -- but not everything. Google recently open sourced its TensorFlow plstform specifically to enable researchers (and others) to build upon and improve it -- trying to avoid the problem with MapReduce (where a bunch of clones came out that were, at least initially, inferior to the original).
- sail 11y agoWhat stood out for me: My PhD advisor never seemed to care particularly about publishing papers; rather, he wanted to move the needle for the field, and he did (multiple times). Racking up publications is fine, but if you want to have impact on the real world, there's a lot more you can do.
- forgottenpass 11y agoNow, I don't think all academic research has to be relevant to industry. I'm getting kind of sick of this tactic, where this fake concession is made before going on about how academia isn't designed well enough to deliver to industry. If authors of articles like this didn't care about the efficiency of academia to deliver them research, what's the big deal if there are a bunch of people somewhere running around in circles? Hey, at least the CS academics occasionally produce something useful to industry, which is more than I can say about other groups running in circles. Sure it could be about burning through money, or a real desire to improve the state of CS academia. But if that was the case I'd expect these articles to have categorically different discussion and calls to action. Or - at the very least - address goals of acedemia other than performing research for industry. I've never been an academic, and never want to be, but even I gave up reading after the "(I know, crazy, right?)" line. At that point, I knew for 100% sure, that the target audience of this article is not academics. Nobody is that much of a condescending prick to the person they're trying to persuade. This is not a "we need to talk" conversation this is a "I need to talk at you, so I can show off to other people."
- mdwelsh 11y ago(I'm the author of the original blog post.) Ad hominem attacks aside, I do think it's a big deal if a bunch of academics are spending time working on the wrong things, if for no better reason than maximizing efficiency: Don't forget that most academic research is funded by the government. Since I also happen to help decide which research proposals Google funds, I also care that academics are well-aligned with the problems we care about. Clearly we also need to invest in long term bets. But there is a big difference between doing long-term, potentially-groundbreaking research and bad industry-focused research.
- deleted 11y ago[deleted]
- cushychicken 11y ago>it's a big deal if a bunch of academics are spending time working on the wrong things At the risk of sounding a little prickly with my comment - isn't it a little presumptuous to write off a certain amount of research as "wrong"? There are plenty of examples of research that didn't have a clear purpose leading to breakthroughs - safety glass, microwave ovens, and Teflon all spring to mind. Also, focusing on efficiency doesn't really align with academia's purpose, which (to my mind) has more to do with fundamental research. This article about Xerox PARC springs to mind: http://www.fastcodesign.com/3046437/5-steps-to-recreate-xerox-parcs-design-magic-from-the-guy-who-helped-make-it http://www.fastcodesign.com/3046437/5-steps-to-recreate-xero...
- tensor 11y ago> Industry is far more collaborative and credit is widely shared. This couldn't be farther from the truth. Your idea's are generally credited to the company, which in turn is credited to the CEO or some other high up. On collaboration, it's only more collaborative within a given company, and not always even then. Between companies it's outright hostile to collaboration by definition.
- _delirium 11y agoIt's often not even collaborative within the company, but only within a specific fiefdom within the company.
- accountatwork 11y agoSomething I've seen at every large tech company I've worked at (which includes the author's company), is that some people do the work for something cool. The next step for them will be to prepare a slide deck so that some big name can give a talk at a conference. That doesn't always happen, but it's common. Depending on the managers and team leads involved, that kind of thing can also happen when promotions come around. At every place I've worked, a common complaint is that the TL for the project got promoted despite not doing much because they were TL. Of course that's not supposed to happen, but it happens all the time. The post seems to compare the worst case in academia vs. the best case in industry. You could just as easily flip things around and make industry sound bad.
- accountatwork 11y agoIn case it wasn't clear in the original comment, the big name is usually someone who was only tangentially involved in the project, if at all. Sometimes it's the head of the org the project took place in. They may have approved the budget for the project, but it's rare that the big name did any of the work. This is like when Tim Bray mentioned that Amazon is great because he hasn't experienced the same problems that have gotten a lot of press lately. Of course he's treated well! He's Tim Bray! Matt Welsh is exactly the kind of big name that isn't going to lose credit on something. Of course he gets credit! He's Matt Welsh!
- draw_down 11y agoTranslation: Universities should continue on the path to becoming the research arm of industry. Academics should alter what they do and how they think, in order to better suit industry. Academic research does not have value or merit of its own, outside of its usefulness to industry. Impact on the world happens only in an industrial context.
- jsolson 11y agoActually reading the article, explicitly none of those things. Alternatively: if you are doing work that attempts to have industry relevance you should have some idea of what problems are actually relevant to industry. In particular, just because you think something is an interesting and challenging problem that just has to be affecting industry players does not mean it actually is. It may have been solved already, or you may have made some poor assumptions on conceiving the problem which, if corrected, make the problem disappear entirely (perhaps replaced by a different one that would've been a more valuable research target). If you're trying to do forward-looking invent things that aren't even a twinkle in industry's eye yet, that's absolutely fine too, and the author explicitly calls out that the only important thing here is to recognize when your work isn't likely to be applicable in the near term. Nowhere does Matt state that this makes this sort of research less valuable, and honestly in many cases academia is the only place it can reasonably happen due to funding incentives.
- wfo 11y agoIt's already happened with CS education for undergrads, why not have industry dominate the research arm of CS departments as well? If we don't bend over backwards pandering to industry and completely restructure academic thought to pander to profit-driven corporations then how will our bright grad students get jobs at Google? God forbid if we don't obey every command of the software industry one day someone might say they're a CS major at a party and have someone ask "CS? Why? What are you going to do with that?"
- Fede_V 11y agoI think he is largely correct in identifying the flaws of 'academic research', but he does not spend enough time discussing the whys. Academics are in an insanely competitive environment, where what is rewarded is bringing in grants/high impact publications. There are a very select few academics that are so brilliant and have such sterling reputations they can afford to not play this game (like Matt Welsh's former advisor) but most young researchers don't have this luxury. For example, Peter Higgs, the Nobel prize winner who postulated the existence of his namesake Boson, flat out said that: "I wouldn't be productive enough for today's academic system" (http://www.theguardian.com/science/2013/dec/06/peter-higgs-boson-academic-system http://www.theguardian.com/science/2013/dec/06/peter-higgs-b...). He spent several years of quiet research without publishing anything to develop his theory - a young professor doing the same now is unthinkable. The most highly successful young scientists I know now are incredibly career driven and optimize ruthlessly for the kind of output that tenure committees are looking for. Basically, if you want researchers to incorporate best practices (tests, version control, well commented code, etc) and to actually attempt ambitious longterm research programmes, make sure that's what you reward, and remember you cannot just reward success. By definition, something ambitious has a high possibility of failure - if failing means that your career is destroyed, then people won't do it.
- nickpsecurity 11y agoThis is very important. Writers like Matt might do well to factor in the "academic" constraints much like he encourages them to do for industry. I ran into this in a discussion with Anti on prior art for Rump Kernels. Learned a bit in that discussion but his troubles getting approval stood out: https://news.ycombinator.com/item?id=10141736 https://news.ycombinator.com/item?id=10141736 I had heard about BS in academia where only paper output, grants, citations, and so on count. That Anti had to fight to get them to care about his work being implemented speaks wonders about how this works out in practice. Had he only cared about academic success, he could've dropped some light technical details and graphs in the paper then been done with it while the idea collected dust. Many benefited from him fighting the tide on it to produce good papers and an implementation. I'm not in academic circles but I bet many face the same battle. With the pressure, it might be impossible for them to produce the desired output on their own within their constraints. Or so difficult many give up. Perhaps we should encourage them to have one good line of research they string out over years for quality and ensuring delivery while doing lots of nice papers in between to keep institutions happy. Think that might work?
- swehner 11y agoWhen you're telling other people what they should do, you're already lost. I also don't feel academia is obliged to any particular promise of delivery, but that's kind of independent.
- jsolson 11y agoThat's not really what the article is doing, though... Instead it's saying roughly: much of the work coming out of academia attempts solve problems applicable to industry, but in actuality industry is not actually suffering from the problems solved (either because underlying assumptions are wrong and industry is plagued by a different problem or because the problem has already be adequately solved by existing work).
- swehner 11y agoSome quotes from the article: "My first piece of advice: do a sabbatical or internship in industry." "you have to work on a real product team" "hold yourself to a higher standard" "keep an open mind" Kind of painful to reread it, actually.
- selimthegrim 11y agoWith all due respect, munin's point upstream about commoditized research areas doesn't apply to quantum information yet, Prof. Wehner, but if I were you I'd be afraid about Google poaching talent, even from Singapore.
- jsolson 11y agoAll of those quotes are conditioned on the premise that you're doing research which purports to be relevant to industry. In that context I agree with Matt. > Now, I don't think all academic research has to be relevant to industry. In some sense, the best research (albeit the riskiest and often hardest to fund) is stuff going way beyond where industry is focused today. Many academics kind of kid themselves about how forward-thinking their work is, though. Working on biomolecular computation? That's far out. Working on building a faster version of MapReduce? Not so much. I'd argue most academics work on the latter kind of problem -- and that's fine! -- but don't pretend you're immune from industry relevance just because you're in a university. This paragraph makes this point abundantly clear: there's plenty of research that is focussed on expanding the field and is discovering problems that will exist once industry catches up. Fantastic. It's risky to try and find the future, but someone has to do it, and I think (based on this and his other writing that I've encountered) Matt would agree that time spent in industry is of dubious utility to those folks[0]. For research that is attempting to tackle extant problems encountered by industry, though, the researcher would be well served by ensuring that the problem they're attempting to solve is actually extant and that the assumptions they're making in trying to solve it don't simply sound reasonable but actually reasonably embody assumptions underlying real (aka industry) deployments. Otherwise they may get a lovely paper which solves a problem that nobody actually has or presents a solution that is impractical because it assumes things which are, in real deployments, incorrect. [0]: On one hand, it might give them a better feel for in which direction a tractable future lies, but by the same token it might prevent them from exploring potentially fruitful avenues by constraining their thinking.
- yarrel 11y agoClickbaity title aside, this is sound advice for academics who wish to be relevant to industry from someone who has experience in both camps. Other academics, for example those doing "stuff going way beyond where industry is focused today" as the author explicitly states, can safely ignore it.
- irremediable 11y agoI agree with some of this, but I wonder... > It drives me insane to see papers that claim that some problem is "unsolved" when most of the industry players have already solved it, but they didn't happen to write an NSDI or SIGCOMM paper about it. I've seen many examples of industry "solutions" that aren't documented, aren't published, and aren't even validated. There's a place for papers like these. I'm not quite your typical CS researcher (I do applied math and software for medical imaging), so YMMV, but I think this criticism is too harsh.
- mdwelsh 11y agoThat's a fair point. The issue is that many of these papers don't seem to acknowledge that industry has (unpublished) solutions, and are somewhat naive as a result.
- irremediable 11y agoFair. This happens less in my field, but a lot of that could be because, for medical applications, people are far less willing to certify without published validation.
- knughit 11y agoAnother way to look at it: avoid the open/academic community stop doing xrypto research because NSA mathematicians are (secretly) way ahead of them? "Open" is a different league from proprietary. It doesn't matter that they are behind proprietary. but it matters when they are working on the wrong problems.
- mcguire 11y agoIt's unfortunate that, in science, if it isn't written down, it doesn't exist. Having been bitten by the 'but we already know how to do that' comments, I find this particular aspect of industry to be very irritating. There are 3 possibilities: The unpublished solution is brilliant. The solution fits for very limited constraints applicable only to that situation. The solution is a half-assed hack that only looks like it works. In only one of those situations is the 'naive' comment valid.
- munin 11y agoToday, in academia, it's considered risky to do research in computer vision, machine learning, or speech processing, for example, because it's likely that you will get "out-Googled". Google probably has an entire team of 20 working on what your one graduate student is doing. They'll have petabytes of real data to test against, hundreds of thousands of computers to run their jobs on, and decades of institutional experience. Your graduate student has a macbook air, six months of experience from an internship at Microsoft, and a BS in computer science. If you're lucky. They're going to lose. They should just go to work at Google. Over time, fields of study become industrialized. There was a time when doing research in computer vision, machine learning, and speech processing was risky because the field was new, difficult to enter, and the prospects for commercialization were slim. That time has passed. Those 20 people working at Google are the people that helped that time pass. One could argue that the place for this work is now in industry - the motivations are all right and the resources and data are aligned to carry the work forward at a rapid pace. This happens in other fields. For example, there's some word on the street that DARPA is going to stop funding so much basic research into applied robotics. Industry, they say, has got this covered. You can argue that they're right. The commercial sector is starting to get real thirsty for robots. Amazon talks about automated drone delivery. Everyone talks about self driving cars. The military wants to buy automated planes as a purchase, not as a research project. The time for basic research, it seems, is over. As far as I can tell, this happened with systems about fifteen years ago, so the academic activity you see in systems is what is left over after all of the researchers that could do things moved into applying their research in industry. You no longer need to have weird hair and be buried in a basement to think about 20 computers talking to each other in parallel - you can go work at any technology company and think about two million computers talking to each other in parallel, and get paid two orders of magnitude more money. So the people doing systems research in academia are the people that cannot take their systems research into industry. If they could get internships, they would, and then they would get jobs. They haven't.
- anonymousDan 11y agoSuch nonsense. I know plenty of people doing great systems research that just doesn't align with the goals of current technology companies. Just look at the proceedings of the top systems conferences and there are plenty of good papers and ideas out there.
- KKKKkkkk1 11y agoRe collaboration. I work in a government research lab which prides itself on being a collaborative environment. The result is that we publish 10-author papers in which one author is doing all of the work and the other 9 are cheering from the sidelines. I don't think this is particular to my lab -- the typical scenario is that 90% of the work on any given project is done by 10% of the people. So when people praise their work environment for being collaborative, I'm sceptical. I'd much rather be in a situation where everyone gets the credit they deserve for the work they have actually done.
- jff 11y ago> Coming from academia, I was trained to fiercely defend my intellectual territory, pissing all over anything that seemed remotely close to my area of interest. Anyone who has ever been through a conference/journal submission process knows this pain. You can usually tell from the comments which of the reviewers is working in your field and wants to shut you out.
- wfo 11y agoIf you're doing industry-relevant research and you're in academia, leave. Your work can be supported by corporate profits because it is in essence for corporate profit. Get a job in industry, make more money, and make room for academics who want to do honest-to-god academics and work on theory or fundamental research. Or who want to do research relevant to improving society, not improving profit margins. There aren't that many professor jobs out there. It's unbelievably greedy to be taking one up to do industry's dirty work. You can always take an afternoon off a semester here and there to be an adjunct and teach a SE class or give a guest lecture.
- mdwelsh 11y agoI don't agree with this at all. The partnership between industry and academia is long-standing and has proven to be extremely valuable -- much of the Internet came about because of it.
- wfo 11y agoAt this point it's not a 'partnership' -- industry has co-opted and taken over academia to a startling and troubling extent. Universities are expected to pump out software engineers trained in industry best practice, not thinkers and theorists, and woe betide any school that doesn't toe the line. Research is pushed towards corporate interests as requested in this article here and people just give up. As public research is defunded corporate money has to fill in, which forces academics to make some noises about "applications" or "industry" when they write their papers in hopes of more funding. In any paper, no matter how theoretical, you can make it sound like it has "applications". If someone published the halting problem today, the first half of the abstract would be "as industry deals with more and more complex programs and terabytes of data that are distributed as services in the cloud, we need to understand if there are limits to what we can compute. We present an argument that there are limits, and describe some practical applications". Many capitulate altogether, trying to do industry work from their academic position. It is these last people who should get out. The creation of the internet worked wonderfully. It was invented by academics based on government grants when it was basic research, and then refined and turned into something practical and workable and, most importantly, profitable, by industry. Exactly as it's supposed to be.
- pklausler 11y agoProgram committees and the conferences they serve may be part of the problem, and hence part of the solution as well. Instead of picking the best N papers so as to fill out a conference schedule, pick the good papers and shorten the conference schedule if the number of good papers is <N. And then raise the standards to meet your expectations of reproducibility, code reviews, unit tests, etc. If a big conference like ISCA were to be shortened by one day by omitting the least worthy papers, you'd see much better work arriving the next year.
- AngrySkillzz 11y ago> "Coming from academia, I was trained to fiercely defend my intellectual territory, pissing all over anything that seemed remotely close to my area of interest." Apparently the author was unable to break that habit.
- woah 11y agoMatt, I was intrigued by your throwaway "not another multi hop routing protocol" comment. As far as I can tell, the field is very slow-moving. The state of the art, Babel, is at least 5 years old and is an incremental improvement on protocols that are at least 20 years old. Some very promising research was done into DHT-based routing with Scalable Source Routing, but this work is now from more than 10 years ago, and interest seems to have dropped off completely. Are there a bunch of protocols that I don't know about? Are you maybe referring also to centralized path finding algorithms? This would explain the comment.
- mdwelsh 11y agoNobody needs multihop routing protocols. Show me one instance in which they have been useful, despite 20+ years of academic work in the area.
- nijiko 11y agoI think we should talk about the constraints rather than relevancy.
- Fomite 11y ago"Second: don't get hung up on who invents what. Coming from academia, I was trained to fiercely defend my intellectual territory, pissing all over anything that seemed remotely close to my area of interest. Industry is far more collaborative and credit is widely shared." In my experience, this is only true until there is money to be made. Or more specifically, that industry was more than willing to share credit, but ownership was theirs.
- nitinics 11y agoI think Industry Research is mostly driven by some constraints that applies to their architecture, their business use-cases and how much the company is willing to spend $$$ on research that adds value to their products or services. Academics on the other hand thinks beyond the box and researches and gives clues to upcoming industries on where the problem might be and how it could be solved, therefore eventually helping Industry grow with validation from the researches and allowing them to put them into "products" and "services". Therefore, I don't think Academics should stop doing what they do (i.e. wander around) and have a laser focus on Industry's product-based researches.
- deleted 11y ago[deleted]
- deleted 11y ago[deleted]
- hnur 11y agoRelevant: http://www.smbc-comics.com/?id=2088 http://www.smbc-comics.com/?id=2088
- jonsterling 11y agoWho gives a damn if academic research is relevant to industry? Almost anything that could possibly be relevant to industry is highly uninteresting. Imagine being someone who thinks that Capital could decide what is a good problem to work on...
- mdwelsh 11y agoThis is so completely wrong. The most exciting work happening in systems, networking, programming languages, crypto, computer architecture, mobile, and many other subfields of computer science is highly relevant to industry and very interesting academically.
- jonsterling 11y agoI do pure type theory, semantics, proof theory & intuitionistic mathematics. Very little of this will find a home in industry (at least, not for several decades). Industry has historically been incredibly resistant to 100% of the things I'm interested in, and I don't blame them! But it's not just the hard & expensive stuff that they are resistant to. Even the "easy" stuff (like adopting a programming language designed by the professionals instead of the amateurs) they won't do. I build interactive proof assistants. But I'm not pushing their applicability to industry, and I don't expect them to be relevant to industry (for a long time at least). Why? Because it's too expensive. Formal verification in type theory MAKES NO ECONOMIC SENSE; ask anyone who's actually ever done any industrial verification, and you will find out what tools they are using, and it has nothing at all to do with the area of research I'm involved in. This is because there are inherent trade-offs in every technique, and industrial use-cases tend to prefer a certain set of trade-offs, and I prefer a different one. But it's a fascinating topic, and something that I'm preparing to devote the next several years of my life to. And I can safely say that a meteorite will more likely destroy Manhattan than will any of my computer science research be of widespread relevance to industry. So, no, I totally disagree with everything you have said.
- alberte 11y ago#insert standard weekly hackernews attack academia article response here
- lpw25 11y ago> I still serve on program committees and review articles for journals and the like. Judging academia from your experience on program committees is like judging the entertainment industry from watching Britain's Got Talent.