Archive for: February, 2011

Friday Fun: Top 10 truly bizarre programming languages

Feb 18 2011 Published by under computer science, friday fun

Twitter brings us some truly wonderful and, yes, bizarre things. I saw this one a few days ago via Vitor Pamplona and thought it was too good to pass up.

Anyways, here's the story from the original Listverse post, Top 10 truly bizarre programming languages:

This is a list of some of the most bizarre programming languages you will ever see. These types of languages are usually called "Esoteric Programming Languages". An esoteric programming language (sometimes shortened to esolang) is a computer programming language designed either as a test of the boundaries of programming language design, to experiment with weird ideas or simply as a joke, rather than for practical reasons. There is usually no intention of the language being adopted for real-world programming. Such languages are often popular among hackers and hobbyists.

Usability is rarely a high priority for such languages; often quite the opposite. The usual aim is to remove or replace conventional language features while still maintaining a language that is Turing-complete, or even one for which the computational class is unknown.

The list is truly fascinating and hilarious.

My favourite of the bunch was the Chef programming language:

Chef, designed by David Morgan-Mar in 2002, is an esoteric programming language in which programs look like cooking recipes. The variables tend to be named after basic foodstuffs, the stacks are called "mixing bowls" or "baking dishes" and the instructions for manipulating them "mix", "stir", etc. The ingredients in a mixing bowl or baking dish are ordered "like a stack of pancakes".

According to the Chef Home Page, the design principles for Chef are:

- Program recipes should not only generate valid output, but be easy to prepare and delicious.
- Recipes may appeal to cooks with different budgets.
- Recipes will be metric, but may use traditional cooking measures such as cups and tablespoons.

With the following listed as the traditional "hello world" beginner programming example for the language:

Hello World Souffle.

Ingredients.
72 g haricot beans
101 eggs
108 g lard
111 cups oil
32 zucchinis
119 ml water
114 g red salmon
100 g dijon mustard
33 potatoes

Method.
Put potatoes into the mixing bowl.
Put dijon mustard into the mixing bowl.
Put lard into the mixing bowl.
Put red salmon into the mixing bowl.
Put oil into the mixing bowl.
Put water into the mixing bowl.
Put zucchinis into the mixing bowl.
Put oil into the mixing bowl.
Put lard into the mixing bowl.
Put lard into the mixing bowl.
Put eggs into the mixing bowl.
Put haricot beans into the mixing bowl.
Liquefy contents of the mixing bowl.
Pour contents of the mixing bowl into the baking dish.

Serves 1.

Yeah, right. I'd like to see someone reprogram the space shuttle control programs in Chef.

Frankly, I'm not brave enough to test it out using the links to interpreters in the Chef page. Are you?

2 responses so far

Around the Web: Edupunks & edu-factories, The connected organization, The importance of physical space and more

Feb 17 2011 Published by under around the web

No responses yet

Going native with stealthy librarian ninjas

McMaster University colleague Andrew Colgoni (Twitter) has taken my Stealth Librarian Manifesto and tamed it a little bit and come up with his own version, which is here.

I like what Andrew has to say in a post titled, I prefer Ninja Librarianship, myself:

[T]here's much that can be learned from discovering where your faculty are reading/going and finding them there. This can be as simple as finding on-campus conferences that draw a broad faculty audience, and visit that. Here at McMaster, the Centre for Leadership in Learning annually hosts a teaching and learning conference, which draws internal faculty interested in pedagogical research, as well as faculty from other institutions. Typically, librarians have a showing at these kinds of events, which (I hope) reminds faculty that we are invested in student learning as well. I will often attend the Society for Teaching and Learning in Higher Education (STLHE) conference, for similar reasons. At some point, I will definitely attend a science communication oriented conference, too.

...I suspect that finding a (personal) balance between library and faculty 'worlds' is probably best. One can adjust depending on how long you've spent in a career, and on which aspects are more rewarding and challenging.

I'll let you head over to Andrew's blog to discover what's he's done to my manifesto. And I'll note here again that I've released the manifesto under a CC0 license so Andrew and anyone else is perfectly free to take a crack at coming up with their own version. Take up the challenge yourself!

Katie Fraser (Twitter) has also put her thoughts down on bloggy paper on her blog at Chuukaku.com.

I'll let her speak for herself:

The stealth librarian's manifesto had me nodding most of the way through. We should become part of our users' landscape. We should be integrated into research and teaching and we should be collaborative. With all these I agree. However, I baulked slightly at the separation from the information profession the manifesto encouraged in parts: "We must stop going to librarian conferences" and "We must stop joining librarian associations"? Yikes!

On reflection I think this reaction is partly about my background. As an ex-academic (at the PhD student level) and relatively new librarian (I graduated from my librarianship course just over a year ago) I'm very conscious of what I've learnt from the knowledge and expertise of other librarians. I'm wary of the danger of 'going native' - a concept from anthropological ethnographic research, where those studying a culture can come to identify with it so strongly that they become estranged from their own culture. I still think that there's a lot I have to learn from other information professionals, and I don't want to lose sight of the new ways of seeing the world I've learnt as a librarian.

All of which is very relevant. I have to admit that the way librarians feel about the various communities they partake in during different career stages wasn't really something that I considered during the fevered writing of the manifesto. It makes a lot of sense for librarians to be more embedded in librarian networks earlier in their career and then to branch out as they become more familiar with library culture and feel confident enough to infiltrate another culture.

And so, my ideas and opinions evolve and change. Much like librarianship.

What do you think?

One response so far

Interview with the gang at EngineerBlogs.org

Welcome to the long-awaited latest instalment in my occasional series of interviews with people in the library, publishing and scitech worlds. This time around the subjects of my first group interview are the gang at EngineerBlogs.org.

From my welcome-to-the-blogosphere post, here's a condensed bit about them:

  • Cherish The Scientist (EB)

    I am an electrical engineer with an interest in various areas of electromagnetics, including antennas and numerical simulation techniques, as well as IC packaging. I have completed a master's degree in electrical engineering and am currently pursuing a doctorate in geophysics.

  • Chris Gammell's Analog Life

    My name is Chris Gammell and I am an analog electrical engineer from Cleveland, OH. Though I grew up in Buffalo, NY, I first came to Cleveland in late 2001; I earned my bachelor's degree in electrical engineering from Case Western Reserve...This site is dedicated to teaching those who are new to the industry and continuing the conversation with those who work alongside me industry.

  • Flying Flux (EB)

    Who is Fluxor? I'm a worker bee located in the nation's capital, the nation in question being Canada, and employed at FluxCorp for the purposes of building a Flying Flux. And what is a Flying Flux? It's a mixture of analog and digital integrated circuitry designed for mass consumption, although I focus mainly on the analog side.

    So that's what I am -- an analog IC circuit designer ...

  • Design. Build. Play. (EB)

    Just another engineer, formerly of the humanities discipline, writing about cars, aerospace, economics, coffee, design, school and exciting workplace adventures at MegaCorp.

Enjoy!

===============

Q0. First of all, tell me a little about yourself/yourselves -- who you are and how you ended up where you all are, career & blogging-wise.

Cherish. I did my undergrad in physics and masters in electrical engineering, both at NDSU. Currently, I am a PhD candidate in geophysics at University of Minnesota. However, after I finished my coursework, I chose to go back to NDSU and work part-time as a research engineer while working on my dissertation. I started blogging while doing my MS, primarily as a means to keep in touch with friends and family. A couple years later, I found the science blogging community (primarily Science Blogs) and realized there was a lot more to it. I like to write up posts about science, technology, and education, but it's still primarily a place to talk about whatever is on my mind.

FrauTech. This is a second career for me. I went into Mechanical Design because CAD is something I really enjoy and my experience in industry led me to believe this was a discipline I wanted to pursue. So I went back to school for Mechanical Engineering and that was that. I started blogging because I had all these grand plans of things I wanted to build and showcase on a blog. I ended up being too busy between work and school to dig into these as much as I wanted and the blogging instead became a really great outlet for my frustrations, other school related projects, and a way for me to have a conversation about research and industry developments in my field.

Chris Gammell. I still feel like a student on many days of the week. I've only been in industry for 5 years, 3 of those in my current field (which was completely different from the previous field). But once I got into the field and began realizing the potential for analog (and EEs in general) in the blogging space, I jumped in to try and educate people.

Fluxor.. I'm Fluxor, the builder of the Flying Flux at FluxCorp. Someday, I'll get myself some superhero tights to match my superhero monicker. Until then, I'm just an EE that's been working close to a decade and half in analog chip design, having specialized in that area in my master's. My first blog post on flyingflux.com tells why I started blogging.

The impetus was a fairly major layoff at FluxCorp in Jan 2009 which made me go through a quick period of introspection, during which I started blogging and haven't stopped since.

Q1. How did you decide to start up EngineerBlogs.org? Were you inspired by the turmoils in the science blogging world over the last year or so, starting with Pepsigate and continuing with the mushroom-like sprouting of a whole bunch of new independent and commercial networks?

Cherish. I suggested the idea to Chris, who had tried starting an EE blogging community a couple years ago. The four of us who started EB were already actively reading and discussing each other's blogs, so I thought it would be fun to do something as a group. I was particularly hoping that it would make it easier to find blogs related to engineering.

I think that while many of us knew about Pepsi-gate, that didn't really play into our decision to start the group. Aside from the fact that it's hard to find engineering bloggers, it's also easy to get lost as a blogger with the millions of blogs that are already out there. As a
reader, it's difficult to avoid information overload. People may not find or visit our individual blogs, but I think we're making an effort to do some of our best, most relevant writing for EB, which is providing us with a good reader base. I think we all would like for our writing to be useful and interesting to people, and EB seems to be helping make some of our writing on engineering and engineering culture more visible.

Chris Gammell. I have absolutely no idea what Pepsigate is...so no, I wasn't inspired by it. I jumped at the chance as Cherish says because I HATE when people sit around talking about starting a website. It's so easy these days and it's better to start a site first and ask questions later. I like ScienceBlogs but I prefer reading about engineering type issues. And most of all, I have had a hard time finding other engineering blogs...so when I found a group, I latched on!

Fluxor. What Cherish said. Plus, I love being elitist. And I love Americans. So when they asked me to become part of this exclusive club, how can I refuse?

Q2. You have kind of a unique model, both aggregating existing blogs and getting
your bloggers to add content directly to the site. Could you explain what that's all about and what the rationale was for doing it that way?

Cherish. We talked this over a bit. All of us are pretty happy with our individual blogs and feel we've invested a lot of time and effort into them. Most of us write very regularly (and Chris has his radio show, The Amp Hour, along with other projects), so we were reluctant to try to fit all of our writing into some sort of formal engineering group context. We considered making EB a blog aggregator but felt it would be of more interest to offer some original content instead. The decision was that each of us would commit to providing a certain amount of content or support to EB. This allows us to contribute without a bunch of pressure to produce content and allows us to use our own blogs for whatever we want. Personally, I don't think I'd enjoy writing about engineering all the time. If I were to move my blog to EB, I would feel a lot of pressure to do that, and I think that would take a lot of the fun out of blogging.

FrauTech. I agree with Cherish, I enjoy blogging about engineering but I like having a blog where I can talk about my cat or whatever else. So I think our personal blogs are pictures of us as whole people and engineer blogs just filters that down to who we are as engineers for readers who are looking for that key ingredient.

Chris Gammell. I listened to the others.

Fluxor. We don't really aggregate posts in real time. We do repost our favourite posts from the past once-in-a-while. But there's a limited supply of those posts.

Q3. Blogging has really taken off in the science world but somehow not so much among engineers. What do you think the reason is for that?

Cherish
. Personally, I think scientists want to talk about their interests, and for many of them, their chosen outlet is blogging. It allows them to discuss their interests in depth, sometimes getting into the subtleties and nuances of their field, talking about what they've learned. Engineers who are really interested in their field tend to do things like participate in HAM radio or similar groups. There are a lot of very active discussion boards where people are swapping ideas, but I think engineers would rather be building things rather than talking about building them.

FrauTech. I think also most science bloggers work in academia or in science journalism and so have free reign to discuss their work specifically and either a secure academic or government funded job to where they don't have to worry about what they say online putting them out of a job. If an engineer is working in private industry he or she doesn't have the same flexibility and might be able to talk about hobbies but anything remotely like what they work on at the job could be seen as harmful or violating proprietary regulations. I think this kind of business atmosphere extends even to engineers working in academia with just a general tendency to be more secretive, careful and private.

Chris Gammell. I think the academic environment that most scientists work in really has a beneficial effect on the blogging community. Engineers obviously battle stigma and stereotypical lack of writing skills. More recently the spectrum of engineering disciplines has popped out a few engineers who enjoy writing and we're hoping to meet them all!

Fluxor. *shrug*

Q4. Related to that I guess, why do you blog?

Cherish. Personally, I blog to talk about things that I find interesting and to meet other people who share those interests. It's both an outlet and way of socializing.

FrauTech. I enjoy reading STEM related blogs and feel like having my own blog is like being a part of a larger community of like minded people who care about a lot of the same things I care about. It's also a way for me to keep working on my writing as well as force myself to keep learning new things. A blog writer to be effective I think has to be able to change and grow with time and writing about engineering helps me realize what topics I'd like to learn more about or where I can grow and improve as an engineer in a way my job is too narrow to make obvious. I think in the end it will make me a better engineer.

Chris Gammell. I blog for personal development, not monetary. Pushing myself into situations such as writing, especially about topics that I'm not completely familiar with, really forces me to learn about subjects enough to not sound like an idiot. I like the connection, especially given my former statement about feeling like a student...whereas
engineering in school is very social, engineering in the workplace is less so. I think writing and interacting with others online really helps keep connected and meet new people.

Fluxor. It's an outlet. And getting to know other bloggers online has made it more rewarding. Plus, I once entered a writing contest on a whim and won. Even got to read it on CBC radio 1. That was a surprise because I really hated English in high school and barely passed the English proficiency essay requirement in undergrad. My perception of my own writing abilities took a turn for the better after that event.

Q5. Is there a difference between science and engineering blogs?

Cherish. There can be. I think that those of us blogging at EB tend to be more like science blogs: we have a lot of interests and cover different ground. A lot of other engineering blogs I've come across, however, tend to be sponsored by magazines and focus on things like tech trends and offering information on specific technologies or advice for certain fields.

Fluxor. Don't read enough science blogs to know.

Q6. You have a good balance of bloggers so far, men vs. women, Canadians vs. Americans, different career stages. Was that planned or did it just happen?

Cherish. We're even somewhat diverse racially. The diversity just happened, but probably this is due to the fact that we started reading each others blogs because we like getting perspectives that are different than our own. We've discussed how we'd like to preserve this aspect of the group, although we've acknowledged that it's already hard to find engineering bloggers, so we're not sure how feasible that will be.

Fluxor. Serendipity. And I would drop the plural on "Canadians".

Q7. What are your plans for the future?

Cherish. We would really like to add a few more bloggers. Primarily, we feel like we're too heavy on electrical engineering and would like to find established bloggers who might be in other fields like mechanical, chemical, civil, or industrial engineering. We're playing around with ideas like themes and wondering what we can do as a community that we might not be able to do as individual bloggers.

Fluxor. Cherish said it all.

No responses yet

Yes, the interviews are back

Way back when, I used to post fairly frequent interviews with publishers, bloggers, librarians and scientists who I thought were interesting people to hear from. Mostly I wanted to hear about what they thought about changes in the scholarly publishing environment.

I've got links to a bunch of them below, mostly to the old blog. (I'll start moving the rest over here when I'm done with the book reviews.)

The last significant interview I did was with Dorothea Salo, way back in October 2008.

What happened?

Well, I decided I wanted my next interview to be with someone involved with publishing at a scholarly society. I actually identified a couple of candidates who looked like they might have some really interesting things to say. For whatever reason, I just ended up getting radio silence when I tried to contact them or get their agreement to be interviewed.

In the end, it was such a frustrating experience that I just gave up. Probably unwisely, but I guess there's never a shortage of things to blog about, only a shortage of time to actually devote to blogging. Especially once I moved here to ScienceBlogs, I guess lower-hanging blogging fruit became more of a priority.

The only interviews I've posted since October 2008 were a couple of relatively short ones with CISTI and a sort-of interview with Kevin Marvel of the American Astronomical Society. While those were good, solid interviews, they weren't quite what I was hoping for.

In any case, two things.

One: Coming a few minutes after this post is a group interview with the gang at EngineerBlogs.org.

Two: I'm going to try and start doing these more regularly, perhaps back to around two per school term. Here's where I need your help. I'd like to make my next interview subject someone in the scholarly society world again, to answer similar question to the ones Kevin Marvel did. Please volunteer at jdupuis at yorku dot ca if you're that person. Or if you know of someone who might be willing, please let me know.

I'll update here when the interview post is actually published.

As promised, some of the older set of interviews:

One response so far

From the Archives: Gawande, Shermer & Angier group review

I have a whole pile of science-y book reviews on two of my older blogs, here and here. Both of those blogs have now been largely superseded by or merged into this one. So I'm going to be slowly moving the relevant reviews over here. I'll mostly be doing the posts one or two per weekend and I'll occasionally be merging two or more shorter reviews into one post here.

This group review is from October 12, 2008.

=======

A few books that I've read in 2008 that haven't quite made it into their own reviews:

Gawande, Atul. Complications: A Surgeon's Notes on an Imperfect Science. New York: Picador, 2003. 288pp.

This is a very fine book that I recommend without hesitation. Gawande has to be one of the absolute best popular writers about medicine of all time. This book is a collection of essays that were published in other places, mostly The New Yorker. The theme of the first section of the book is the fallibility of doctors, how they need to learn about their craft by basically practicing on us, and the ethical and practical dilemmas that all of us face because of this simple facts. We all want to be operated on by the most experienced surgeons, of course. But how did those surgeons get experienced in the first place? The rest of the book more or less picks up on those themes as it covers some medical mysteries and some things that the medical profession doesn't really understand yet.

This is a must-have for any academic or public library and I can imagine medical libraries building whole exhibits and and other collection focus activities around the work of Atul Gawande.

Shermer, Michael. Why Darwin Matters: The Case Against Intelligent Design. New York: Holt, 2007. 199pp.

Another very fine book. Noted sceptic Michael Shermer basically demolishes the Intelligent Design and creationist paradigms from start to finish, but he also does it in a rather ecumenical way, taking care not to burn bridges or overly offend. You can get an idea of what he covers from the chapter titles: The Facts of Evolution, Why People Do Not Accept Evolution, In Search of the Designer, Debating Intelligent Design, Science Under Attack, The Real Agenda, Why Science Cannot Contradict Religion, Why Christians and Conservatives Should Accept Evolution and The Real Unsolved Problems in Evolution.

Shermer also weaves in his own personal story about how he evolved from being a Christian creationist himself to his current position supporting evolution, as well as his experiences at the Dover trial.

A solid, informative book, even if it's occasionally marred by Shermer's own descents into theistic gobblydegook, such as on page 43, "If we think of God as a thing, a being that exists in space and time, it constrains God to our world, a world of other things and other beings that are also constrained by the laws of nature and the contingencies of chance. But if God is the maker of all things and all beings visible and invisible in heaven and earth, God must be above such constraints: that is, above the laws of nature and contingencies of chance." A good rationalization for believers, I guess, but it does undermine some of his other arguments.

Overall, I'd recommend this book to most public libraries and any academic library that collects popular science.

I would like to close with another quote, from page 161.

Darwin Matters because evolution matters. Evolution matters because science matters. Science matters because it is the preeminent story of our age, an epic saga about who we are, where we came from and where we are going.

Angier, Natalie. The Canon: A Whirligig Tour of the Beautiful Basics of Science. New York: Mariner, 2008. 293pp.

Natalie Angier is a well-known science writer for the New York Times and in this book has produced a very fine explanation of what science is all about. She also covers an awful lot of territory giving an overview of the current state of the art in various of the scientific fields.

But the most important contribution of the book is the first few chapters where she basically gives an layperson's introduction to the philosophy of science. She talks about the scientific method, the role of probability in science and the role of measurement, all very important topics in understanding what science is. I think it's important to mention that her approach is in sharp contrast to Bill Bryson's A Short History of Nearly Everything, which tended to use a more historical narrative, concentrating on the eccentricities of the various scientists he profiled to give colour. Bryson really didn't discuss any philosophy or have any extensive discussion of the scientific method, to the book's great detriment I believe. Angier seems to have learned from Bryson's mistakes, both in giving that philosophical and mathematical underpinning as well as not portraying scientists as freaks and weirdos.

The rest of the book is given over to a quick overview of physics, chemistry, evolutionary and molecular biology, geology and astronomy. It's quite dense and perhaps potentially a bit dry, but she mostly avoids that with a lively sense of humour sprinkled with quite a bit of flashy wordplay. This aspect of the book came under a fair bit of criticism from other reviewers, but I think it works quite well. Granted, she does goes overboard on occasion -- sometimes it seems that every paragraph needs to end with a little zinger.

Did I learn anything? Yes, I did. Quite a bit really. On the frivolous front, it seems that Angier and I share the same passion for collecting bookmarks. Who knew?

I would recommend this book to any academic or public library. Even high school or middle school libraries would be able to find readers for this book.

No responses yet

Around the Web: Tips for smarter social networking, Contemporary student life and more

Feb 12 2011 Published by under around the web

No responses yet

Friday Fun: Library Of Congress Adds 3 Titles To List Of Films That Should Be Destroyed Forever

Feb 11 2011 Published by under friday fun

Sometimes we collect stuff that we think no one else wants. Sometimes, maybe we should be anti-librarians and erase from all human memory things that should never have existed.

Kind of like that scene in The Ten Commandments where The Pharaoh orders all mention of Moses be obliterated from monuments and records.

I kind of like The Onion's take on it, Library of Congress Adds 3 Titles To List Of Films That Should Be Destroyed Forever:

The Library of Congress announced this year's selections for the National Film Incineration Project on Tuesday, naming three titles it had chosen to permanently eradicate for the sake of future generations. ... NFIP president Lawrence Feldman said as workers shoveled every known copy of Hollow Man 2, Nights In Rodanthe, and Rock Star into a furnace burning at 6,000 degrees Fahrenheit. "I'd like to thank our librarians for their painstaking work combing thrift stores for VHS tapes and personally deleting every known digital version of these unremarkable films."

What would you add to the list? Or more precisely, what would you subtract from human memory?

I'll vote for The Phantom Menace.

14 responses so far

Around the Web: Personal data ecosystems, Learning to say, "I don't know" and more

Feb 11 2011 Published by under around the web

No responses yet

A stealth librarianship manifesto

Stealth librarianship is a way of being.

This particular edition of the manifesto applies to academic libraries. The principles of stealth librarianship apply to all branches of the profession, each in particular ways. Other manifestos could exist for, say, public or corporate librarians.

However the core is the same: to thrive and survive in a challenging environment, we must subtly and not-so-subtly insinuate ourselves into the lives of our patrons. We must concentrate on becoming part of their world, part of their landscape.

Our two core patron communities as academic librarians are faculty and students. This manifesto concerns faculty. A later manifesto may address infiltrating student communities with stealth librarians. Or, you can write that one yourself. Go for it.

The jobs of faculty comprise research, teaching and service. We must stealthfully insinuate ourselves in those areas. We must make our laser-like core focus our patrons.

  • We must stop going to librarian conferences and instead attend conferences where our patrons will be present.
  • We must stop presenting only to our fellow librarians. That's what Twitter is for. We must make our case to our patrons on their turf, not make our case to ourselves on our own turf.
  • Where possible, we must collaborate with faculty in presentations.
  • We must stop reading the formal library literature. That's what librar* blogs are for. We must familiarize ourselves with the literature and scholarly communications ecosystems of our patron communities.
  • We must stop writing the formal library literature. That's what librar* blogs are for. We must make our case for the usefulness of what we do in the literature of our patron communities.
  • We must stop joining librarian associations. That's what Friendfeed and Facebook are for. (Go LSW!) We must instead join associations that revolve around our patron communities.
  • We must not segregate ourselves within "library divisions" in those organizations but must partake fully in those associations. As above, this includes conferences and society publications.
  • In terms of engaging faculty at conferences and in the literature, we must engage both their teaching and research roles.
  • We must stop serving on so damn many library committees and make time to sit on committees at all levels of our institutions' governance structure. It may take time and considerable effort to stealthily insinuate ourselves into all the places we belong.
  • We must invite ourselves to and actively participate in departmental meetings, faculty councils, senates and whatever other bodies make sense.
  • We must integrate ourselves as fully into the teaching mission and classroom environment of our faculty as staffing levels allow. We have much of value to teach their students and can help faculty fulfill their curricular goals.
  • We must fully engage our faculty in the social networking spaces where they live. As well as all the library people we engage, we must also follow and interact with our patrons on Twitter, Facebooks and other sites, where appropriate.
  • Add your manifesto element here.
============

A couple of final points.

As with all manifestos, this one is subject to the failings of hyperbole and oversimplification. Think of it as a series of provocative statements not a realistic plan of action. For example, I don't really think we should all abandon our professional associations.

This is based on hope and promise, not despair.

Similarly, it is incomplete and flawed. Please feel free to add to it in the comments as well as suggesting modifications and deletions. Certainly the education part could be expanded.

And the student one. Let's start building that one together in the comments.

And yes, I did really start thinking about this at Science Online 2011, with some ideas here and here. I also started germinating some of these thoughts after seeing how the library sessions at Science Online 2010 worked out, see here and here, noting how the session on Reference Managers was better attended and didn't have "library" in the title. And looking further back, it's a fairly common theme for my blogging, for example here and here.

What does this all mean? I'm not sure. But it's worth thinking about.

Finally, this document is released under the CC0 license. Have at it.

Update 2011.02.23: Some futher links and reaction to this manifesto:

28 responses so far

« Newer posts Older posts »