12 ms·
What are those issues?
by moggie 13y ago
What are those issues?
- eli_gottlieb 13y agoLargely a focus on maximizing short-term and near-term "productivity" - as we understand it here and now - rather than allowing the leisure for both basic sanity and for larger thoughts.
- weland 13y agoI was about to write a longer post, but this is so incredulously complicated, and I am so biased, that I changed my mind halfway through. I'm honestly too biased about some of its points to provide anything marginally better than flamebait if I start going into details, but I can offer some hints. 1. The funding for research is increasingly scarce, and the ones who decide how big they are and to whom they should go are increasingly clueless. This means that ideas are funded less and less based on their scientific merit, and that more and more funds are handed over based on personal relations than on true selection. This is an incredibly important problem. The retards running it are (like most retards) too arrogant to realize that we, as a race, suck at making predictions about what we can do. Both in terms of being too optimistic (remember thirty years ago when people thought we'd write these posts from a base on the Moon?) and in terms of missing obvious things, like electricity, which was intensely studied for several decades before it got any reasonable application. There are many ways to avoid handing money over to crackpots. The focus should be on those, not on trying to judge the merit an idea might have in practice. We're too stupid to do that yet. 2. The bulk of the work is carried out by underpaid people, in bad working conditions. This makes smart people bitter, kills their productivity (in the short term) and their lives (in the long term). I distinctly remember my first workplace after I dropped out: it was a start-up where we were routinely pulling 60-hour weeks before we managed to hire enough people. This felt like a lot of free time to me. 60 hours is a free week for a PhD working on something worth a fuck. 120 hour stints are rare because of the physical strain they put on you, but you end up doing one every two months or so. Don't get me started on what that does to your life. This may work if you have a bunch of Steve Jobs wannabe pretending they're scientists, researching how to sell things. Turns out, it's disastrous when trying to do real work. A lot of the jokes we played in the office revolved around that. They stopped being funny when we pondered how many drowsy PhDs were simply too tired to realize they could do <this thing> and bring us five years closer to treating cancer. 3. A lot of the undergraduate classes are becoming less and less fundamentals-focused, because academia is increasingly becoming the place where you're trained to work in the industry. Consequently, as people finish their senior years, they are increasingly less adept at research -- though, sadly, increasingly proud about their can-do attitude and so happy they have a Computer Science degree to prove that they can design websites, as if you actually had to fucking go to college for that. Turns out these people are good enough for the wonderful world of startups. They're just as clueless about the real world as the people who pay them, their self-esteem is bad enough, and they are so utterly inept at learning anything mildly complex that they are easily sucked into the industry vortex. This isn't true only about CS and CompEng, it's happening in fields like EE and Mechanical Engineering, but the proportion of mission-critical applications in those fields is slightly higher, so most of the hipsters get cured after their first months on the job. Turns out this system, while being almost satisfactory for the industry, breeds very bad researchers. Turns out it's hard to do research into web communication if 90% of your graduates have mad CSS skillz but still have trouble explaining what O(log n) means. #1 and #3 above may be subjective, and there are a lot more points that I didn't want to bring in so as to maximize the chances of keeping the discussion civil. #2, on the other hand, while also being something I am quite subjective about (actually, it's the one I'm rather heartbroken about) is the one that escapes the scrutiny of people who are otherwise quick to cry out against the likes of Walmart. Part of my dropping out of academia (see below for disclosure) is that I'm really not that smart. I'm good, but not scholarly material; I'm good at bringing together various technologies and finding atypical solutions to practical problems, but I suck at pounding on the same important issue for years and years at a time. I also suck at math. My brain isn't wired correctly for that. So, even if the working conditions hadn't been the way they were, I'd have left academia at some point, simply due to my sheer incompetence. However, I had a lot of colleagues who were incredibly smart. People who could think of a problems in way I could never have possibly thought, and who were genuinely better at what they studied (electromagnetism) than I'd ever have been (I ended up doing research in EE by sheer chance anyway; I got into EE because I thought it would make be a better programmer -- which it did). You wouldn't believe the way they changed in five or six years of working 10-12 hours a day, not only weekdays, but weekends too. I've heard more stories of wrecked relationships than I can think about, and too many of them are struggling with depression. Most of them don't regret it at all. They're happy with what they discovered and genuinely feel they made the world a better place, but having been there, I honestly can't help wondering if it was worth it. I never bring it up with them, for obvious reasons, but it's very sad, especially since I can relate with that. (Almost) full disclosure: I am an academia dropout. I dropped out during my MSc studies, despite being on a fairly good track (several articles, in several important journals (important as in "people who aren't scientists have heard of them") with my name on it, prior to me earning my BSc).
- foobarqux 13y agoYou seem to, maybe fairly, denigrate startups and industry in general as well as academia. What should an intelligent person do? What did you settle on? What advice would you give to young people?
- weland 13y ago> You seem to, maybe fairly, denigrate startups and industry in general as well as academia. Yeah, this is exactly why I changed my mind halfway through that long post :-). I honestly love the startup environment. I'd much rather work in start-up than a large company. What I do denigrate is starting up for the sake of starting up. Finding an (often otherwise legitimate) need, pounding at it for six months while it's still hot, and coming up with a technologically half-assed product to sell for a reasonable price. This is, in my opinion, destructive both intellectually and technologically. It teaches bad habits and gives little time to learn both adequate technologies and the fundamentals of their trade to programmers. I'd be a very rich man if I had a penny every time I told a colleague who was enthusiastic about a new technology he'd discovered on kickstarter or here on HN that <this operating system from the 70s/80s/90s> or <this thing from the 70s/80s/90s> had this. You know something is wrong when so many new things are so similar to old things -- so similar to the point that they repeat the mistakes. As for academia, I still keep in touch with some of the people I worked with there. It's the most intellectually stimulating place I've ever worked in, and contrary to popular belief, one of the most refreshing feelings a professional can have is walk into a roomfull of people and realize they're the dumbest in there. I miss being the dumbest man in the room. > What should an intelligent person do? I honestly have no idea. > What did you settle on? I didn't settle yet, but if I were to look back, I'd say what I'm doing now is better than what I had back then. Now I'm working for a large-ish company. Their business is entirely software, but they want to start doing hardware and they brought me in to help. They pay me well and I can come in the office at 10 AM, which is good (I have some sleep issues). The work itself is shit; there's a long ladder of managers who are increasingly clueless about what embedded development means, but each of them has to deliver results (no matter how irrelevant) because they made promises. Consequently, most of what I do is pointless, but not entirely uninteresting. In the last month or so, I dabbled in a USB driver in the Linux kernel, hacked on an HTTP proxy, helped a colleague build a PCB... it's useless, but not entirely devoid of fun. I intend to leave as soon as someplace where they actually need me to build stuff, not massage egos, shows up, but until then, I can bear it. That being said, it also leaves me enough free time to do some hacking of my own, enough time for my hobbies, enough time for family and friends. I have enough time to brew beer with my girlfriend, read whatever books I want, learn Go and post crap on Hackernews. I'm far more unhappy with what I do than I was in university, but overall, I'm a happy person.