Didier reminded me to check Nielsen’s last post on Principles of Effective Research. I take a quote out of it…

The foundation is a plan for the development of research strengths. What are you interested in? Given your interests, what are you going to try to learn? The plan needs to be driven by your research goals, but should balance short-term and long-term considerations. Some time should be spent on things that appear very likely to lead to short-term research payoff. Equally well, some time needs to be allocated to the development of strengths that may not have much immediate pay-off, but over the longer-term will have a considerable payoff.

This is a refreshing view.

Looks like Sean has found a good Canadian e-commerce site for computer stuff: NCIX.com.

When I started out as a researcher, as a young Ph.D. student, I thought research was about “having ideas”. Then, it occured to me that it was about “having ideas and ‘selling’ them” because “having ideas” is easy and too many people have too many ideas already. But marketing experts sell ideas all the time… surely, they don’t do “research”. Then, I changed my mind and decided research was about “taking ideas, validating them, putting them in practice, and building tools out of it” where “tools” is to be interpreted in a very wide sense. Turns out it is not a bad definition of what research is. But the part about “taking ideas and validating them” is a networking problem. Where do your ideas come from, how do you know how good they are? Ultimately, “validating” an idea means putting it in front of a community and getting the community to say “this is a good idea”. “Validating” is not the same as selling, though it might be hard to tell what a person is really trying to do.

But to be blunt, I don’t have yet a satisfying definition of what “research” is and I’m not looking very hard… though, networking is a necessary condition for sure. Scientists on desert islands without telecommunication can’t do research. That’s the part that I did not understand until a few years after my Ph.D. Well, maybe I’m hard on myself, maybe I understood it on the surface, but I didn’t internalized until much later.

Michael Nielsen pointed me to an interesting Web page very useful for Ph.D. students and novice researchers: Networking on the Network.

In Networking on the Network, Philip E. Agre accurately describes the world of research as a network. A network isn’t good or bad… so, some nodes will suck energy out of the network, and others will contribute much to it. The network is somewhat self-regulating, but it is possible, nevertheless, for bad leaders to emerge… He has this to say about the relationship between students and supervisor which I find rings very true:

It is good to be powerful, but only in the correct sense of the term. People with the right kind of power, in my view, do not need to manipulate or control others. To the contrary, they are (sic) know that they are well-served when others grow and find their own directions, so they happily support everyone in their growth. They don’t take responsibility for others’ growth, which is a different question. They speak to the healthy part of a person, and they are concerned to draw out and articulate the brilliant ideas and worthy vision that lie beneath the surface of whatever anyone is saying. For example, they don’t try to enroll students as acolytes in their empire-building strategies, but honestly ask what’s best for each student’s own development, confident that their knowledge, vision, and connections will have an important influence on the student’s development in any case.

As you can see, he talks a lot about “Empire building”. Indeed, because research is all about networking, to a large extend, one can build an empire out of thin air, with no substance.

It seems you can either build an empire for the purpose of building an empire, because that’s you definition of success, or else, you can aim to remain “free”. That’s a very powerful idea:

You build networks around the issues you care about, you grow and change through the relationships that result, you articulate the themes that are emerging in the community’s work, and through community-building and leadership you get the resources to do the things that you most care about doing. It’s true that this method will never give you arbitrary power. But the desire for arbitrary power is not freedom — it is a particularly abject form of slavery. If you can let go of preconceived plans then you are free: you can choose whom to associate with, and as you build your network you multiply the further directions that you can choose to go. You also multiply the unexpected opportunities that open up, the places you can turn for assistance with your projects, the flows of useful information that keep you in contact with reality, the surveillance of the horizon that keeps you from getting cornered by unanticipated developments, and the public persona that ensures that people keep coming to you with offers that you can take or leave. That is what freedom is, and it is yours if you will do the work.

I give Agre a lot of credit from bringing in the concept of “freedom” in research. University professors will often talk about “academic freedom”. I think that freedom in research is a stronger form of freedom. You can have “academic freedom” but be a slave to the “publish-or-perish” paradigm for the power it brings you. Or else, you can “do the work”, that is, do your research as a network node, and leverage the strength of the network to make the research you want to do anyhow, much better, much stronger.

At the office, the network is badly configured. Apparently, name resolution is not a priority and it is really slow. So, what I did was to install bind and use my own name server.

Disclaimer: expect bad English or rather, techno-babble to follow.

As I use gentoo, I first had to install bind.

emerge bind bind-tools

Then, you have to

rc-update named default

so that bind is always started when the machine reboots. Start bind with

/etc/init.d/named start

I modified /etc/resolv.conf by adding

nameserver 127.0.0.1

and I made sure that dhcpcd wouldn’t rewrite my /etc/resolv.conf file by adding the line

dhcpcd_eth1=”-R”

to the file /etc/conf.d/net. Finally, restart your network by

/etc/init.d/net.eth0 restart

or

/etc/init.d/net.eth1 restart

like here where for some reason I have eth1 has my network adapter.

I’ve been reading Michael Nielsen’s Principles of Effective Research, he is up to Part IV now.

He makes a very important point about research. When I started out doing research, I thought that research was about sitting in your office thinking up new ideas. God! Was I wrong!

Now, don’t get me wrong, research is not about having meetings with other researchers or spending time chatting, or drawing UML diagrams of what is to be done, or spending weeks on funding proposals. We might do these things, but they don’t make us good researchers. But neither will sitting in your office thinking new ideas. That’s not effective research.

On quasi-desert islands with no telecommunications, you’ll find very few great researchers. The social network doesn’t need to be immediate: I think you can be a great researcher even in a tiny school. And I don’t think your network should be made of students mostly, especially not your own students.

I believe the secret to being a good researcher is to belong to a tightly knitted group of solid researchers. Research is about networking. By tightly knitted, I don’t necessarily mean “military-like”: I mean that you feel peer pressure all the time to do good research. This can be achieved through emails, blogging, phone… whatever the mean…

« Previous PageNext Page »

Powered by WordPress