by physicsgraph on 7/4/22, 3:14 PM with 61 comments
by rossdavidh on 7/6/22, 1:22 PM
Inevitably, technology changes, and at some point you have to learn a new language, programming paradigm, database, or what-have-you. One feels again that one does not know what to do, at first. It's rather like feeling stupid. I have become able simply to say to myself, 'ah, yes, that feeling again, it shall pass in time', and just keep working at it (whatever 'it' is that year).
If you haven't felt like you don't know what you're doing in many years, your programming career has stalled, and I believe you should seek out a new skill to learn that makes you feel stupid while learning it, pronto. It takes practice to remain calm while having that feeling, and if you haven't had it in years you might let it panic you into thinking you can no longer program.
by bowsamic on 7/6/22, 8:53 AM
For me the more difficult part right now is learning how to become self motivated. Going from having my supervisor coaching me in my PhD to being basically totally unsupervised and free to work on what I want in my postdoc has been very difficult both for my work and my mental health. You have to become almost totally self reliant. You start to value and amplify every bit of motivation you get. Discipline doesn’t cut it, because a lot of academic work is impossible to force. There aren’t many mechanical aspects of it, almost all of my work requires a tonne of diverse creative thinking, even just responding to reviewer comments
Back on stupidity, one of my favourites things has become to ask “stupid questions” as a postdoc. Partly because as a postdoc, people just assume you are very smart, so there is no pressure to “look good” or “not say stupid things”. There’s something weirdly liberating about hearing a bunch of very technical questions from PhD students and then me deciding to ask a very basic conceptual question. That said there are “stupid” questions and then there are ignorant ones, and the line is often blurry
by amelius on 7/6/22, 7:16 AM
Eh, no. The reality is that there is always a pressure to produce more papers with positive results.
by teekert on 7/6/22, 10:33 AM
I have to admit though, it took me until about 35 in age to being able to say to myself: “You know, if you don't understand something, it because it’s hard.” Total game changer for my attitude.
Before that I relied a bit on a certain naïveté, as a biologist among physicists I was sometimes called “Stupid biologist”, I guess it helped seeing it as the joke that it probably was for the most part.
by Vanit on 7/6/22, 6:50 AM
by LetThereBeLight on 7/6/22, 2:40 PM
by throwoutway on 7/6/22, 11:58 AM
by Topolomancer on 7/6/22, 7:51 AM
by YesThatTom2 on 7/8/22, 12:09 PM
“If we knew what we were doing, it wouldn’t be called RESEARCH.”
by tpoacher on 7/6/22, 5:26 PM
by rob_c on 7/6/22, 11:20 AM
Need I mention the reproducibility crisis, poor funding models, retractions from front-page of nature within the single field...
"Naivete" I can agree with. Stupidity is not and should _never_ be encouraged or endorsed. Even if common use of American English tends to push the meaning of the former onto the latter.
Definitions of words are very important when communicating openly and honestly. This is not an attack on commonly used words in American language, it's an observation. British English (and I assume others) are following suit as America leads the way in "english-speaking" culture. Mixing word definitions is entering into a quasi-mixed up state where people don't know the exact definitions of words which makes difficult good-faith conversation difficult.
by seydor on 7/6/22, 7:07 AM