Tagide

Cristina (Crista) Videira Lopes started a list of programming or programming-related tasks like this: http://tagide.com/blog/2011/06/things-ics-students-should-do-before-gr… I'm in the same boat. On section 28 of LPTHW. Luckily, I am working with a startup where I hope to cut my teeth helping more with building our product instead of just being a customer guy. I promise to follow up when I get a better answer. Feel free to contact me.

I've mentioned this a bunch already on HN, but I recommend reading "The Structure of Scientific Revolutions" by Thomas Kuhn. The book was published before most people had even heard the phrase "computer science," but I think that computer science still follows some of the patterns he talks about. In Kuhn's view, "normal science" is mostly iterative and incremental. It is so because most people in the discipline agree on most of the big issues, and people are mostly refining those understandings. The periods where people don't agree on the big issues in a discipline is around the time of scientific revolutions: the solutions to such big issues are so different from previous approaches that accepting them requires a complete re-think of what the discipline is. A lot of areas of CS are in the "normal science" part of that cycle, and I think compilers and languages are in there. (The biggest argument against that is concurrency and parallelism.) In the 60s and 70s, programming languages were new, and they changed computer science forever. We were exploring what these things could be. I also recommend Cristina Videira Lopes's blog post, "The Evolution of CS Papers": http://tagide.com/blog/2014/02/the-evolution-of-cs-papers/

Hi all, This blog post/FAQ should clear up the story behind the journal, and its relation to AOSA: http://tagide.com/blog/academia/the-art-science-and-engineering-of-pro… Kind regards, Tim

"I don't understand why the Hacker News community tends to downplay the effect of pure CS research and the programming ability of people in academia." The author of this article, in fact, seems to be a rather accomplished programmer as well as an academic. Here's her "about" page: http://tagide.com/about.html When I was in academia, I had the privilege of meeting some people with really impressive programming talent. And some of the pure CS research I saw had some very interesting applications, such as string matching algorithms that could be applied to DNA sequencing. (Of course, there were people who were extremely talented at bullshit too, but the quality of people varies anywhere you go.)

Nice, but for some reason the link is to a point "below the fold", hiding the headline and the starting paragraph. The proper link is simply http://tagide.com/blog/2014/02/the-evolution-of-cs-papers/.

You might like to check out this blog post by Cristina Videira Lopes (though it's not about Go in particular): http://tagide.com/blog/2012/03/research-in-programming-languages

Some missing context, this post is by Cristina Lopes, one of the co-inventors of Aspect Oriented Programming. For thos that don't know Gregor Kiczales and others worked on the CLOS MOP culminating in their book The Art of MetaObject Protocol. I still think this is the only success story of I'm aware of where multiple incompatible programming language dialects were unified under a protocol malleable enough to express them all. This is William Cook's points about the flexibility of OOP taken to the extreme. When Kiczales and others realized Common Lisp as a community wasn't going anywhere they took their ideas and created AspectJ. Anyways, her blog seems like a lively read in general - I found this blog post pretty entertaining and I agree wholeheartedly - http://tagide.com/blog/2011/05/programming-is-math-apparently/