As a scientist, you are a professional writer: your career is built on successful proposals and papers. Success isn't defined by getting papers into print, but by getting them into the reader's consciousness. Writing Science is built upon the idea that successful science writing tells a story. It uses that insight to discuss how to write more effectively. Integrating lessons from other genres of writing with those from the author's years of experience as author, reviewer, and editor, the book shows scientists and students how to present their research in a way that is clear and that will maximize reader comprehension.
The book takes an integrated approach, using the principles of story structure to discuss every aspect of successful science writing, from the overall structure of a paper or proposal to individual sections, paragraphs, sentences, and words. It begins by building core arguments, analyzing why some stories are engaging and memorable while others are quickly forgotten, and proceeds to the elements of story structure, showing how the structures scientists and researchers use in papers and proposals fit into classical models. The book targets the internal structure of a paper, explaining how to write clear and professional sections, paragraphs, and sentences in a way that is clear and compelling. The ideas within a paper should flow seamlessly, drawing readers along. The final section of the book deals with special challenges, such as how to discuss research limitations and how to write for the public.
Writing Science is a much-needed guide to succeeding in modern science. Its insights and strategies will equip science students, scientists, and professionals across a wide range of scientific and technical fields with the tools needed to communicate effectively.
There's a pattern I’ve realized through reading advice books. The best book on presentation I’ve ever read isn’t about presentation skills. Similarly, the best book on design isn’t about design skills. Now, this is the best book I’ve read on writing, and it isn’t about writing skills either. To be precise, this book does contain a lot of advices on how to write, but these advices secondarily come from a foundation which is much deeper and far greater: the author’s philosophy about writing. The best books transform not only the way we practice a subject, but also the way we think about it. With the right philosophy, even an ordinary person can do extraordinary works.
2020 update: For no book is without shortcomings, no review is complete without pointing out those. Schimel’s philosophy of writing is that of story-telling, of compelling narratives, of suspenses and surprises. I am not saying that this view is wrong. In fact, I believe that this is the correct view if one wants to publish papers that get read and cited. In this sense, the book did just the job it told you it would.
However, the book would be more complete if Schimel discussed whether scientific writing SHOULD be so. Aren’t we supposed to judge a scientific paper on its scientific content alone? Scientists, who are often thought to possess a high degree of "immunity to eloquence”, now seem to succumb to the sensuous pleasure and charm of compelling story-telling.
Super valuable book for beginning scientists. I am now writing my first scientific paper, and this book together with a writing course is helping me loads. Some things you aren't really aware of when you're trying to write down what you've done, so it's nice to get a clear overview of what makes a scientific piece nice to read. I am no native English speaker, so all the extra help is useful. Contains some exercises also, and a list of further books to read. Recommended!
কোন লেখা বিজ্ঞান নিয়ে হোক আর কল্পকাহিনী নিয়ে হোক, সে লেখার একটা গল্প থাকতে হবে, যে গল্পে চরিত্র থাকবে, গতিশীল কাহিনী থাকবে, কিছু টানাপোড়েন আর সবশেষে একটা সমাপ্তি। যত বেশি দিন গল্পটা পাঠকের মনে থাকবে, তত বেশি সার্থকতা। এ ধরনের সার্থক গল্পের কিছু রেসিপি আছে এ বইয়ে।
রেসিপির শুরুটা গল্প বলার ধরন নিয়ে - শুরুতে জেম্স বন্ডের সিনেমার মতো অ্যাকশন দেখিয়ে পরে অতীতে ফিরিয়ে নেয়া হবে, নাকি সাসপেন্সটুকু শেষের জন্য রেখে দেয়া হবে এসব নিয়ে। এরপর ধীরে ধীরে প্রতিটা অংশের গভীরে ঢুকে কার্যকর পরামর্শ দিয়েছেন লেখক — কোন্ অধ্যায় কীভাবে লিখতে হবে, প্রতিটা অনুচ্ছেদের মাধ্যমে কীভাবে গল্পের কাহিনীকে সামনে নিয়ে যাওয়া যায়, কীভাবে কার্যকর বাক্য গঠন করতে হয়, কোন্ ধরনের শব্দ চয়ন করতে হয়। শুধু গাম্ভীর্যপূর্ণ বায়বীয় পরামর্শ নয়, বরং উদাহরণের মাধ্যমে ভাল লেখা আর খারাপ লেখার পার্থক্য হাতে ধরে দেখিয়ে দিয়েছেন। পুরো রেসিপি ঠিকমতো অনুসরণ করতে পারলে লেখা আকর্ষণীয় হতে বাধ্য।
বইটা দ্বিতীয়বারের মতো পড়লাম। প্রথমবার ৪-তারা দিয়েছিলাম — কেন যেন মনে হয়েছিলো উপন্যাসের মতো আকর্ষণীয় হয়নি, তাই ১-তারা কমিয়ে রেখেছিলাম। কিন্তু এ বই থেকে এত কিছু শিখেছি যে ১-তারা কেটে নেয়া অন্যায় মনে হয়েছে। তাই সবগুলো তারাই ফিরিয়ে দিলাম। আর বিজ্ঞান গবেষণার সাথে সংশ্লিষ্ট সকলের জন্য এ বইটি সুপারিশ করছি।
Overall a great book and also in line mostly with my advisor's thinking on the matter. I learned a lot and clarified a lot in my thinking. I'll focus here on some concerns, but overall just make sure to read this book if you need to write science.
Some of the acronyms were hard to keep 100% in mind throughout the book. Also, sometimes my lack of familiarity with particular fields did get in the way. But not too much.
Leaving out the issue of the dynamics of the abstract is a bit odd, I think, since that's really how people get into a paper.
On the little things, one thing I've decided is that saying "not X" is less than ideal. People have a way of overlooking negation. In one example in the book, Schimel left a revised sentence ending in "not conclusive" or something like that. At the end, "not" might be more noticeable, but I'd recommend "inconclusive" even as a longer word. But overall, Schimel has a LOT more down than I do, so take his advice over mine, I guess.
Also, in my discipline (computer science, artificial intelligence, machine learning, robotics), conferences matter a lot, and the paper is only one component of getting citations. Citations might matter a lot more on the presentation (although I don't know statistics), so the small audience of the reviewers is what matters. In this sense, papers become perhaps more like proposals. Seeing an experienced analysis of the dynamics in this world would be nice. Also, how to maximize overall effectiveness where writing is one (still important) component.
Finally, this review (like all my others) is a hack first draft not trying to be formal at all. So don't judge the book by any flaws in my writing here. I definitely expect to review the recommendations of this book in my future writing and editing.
I appreciated this book much more than I thought I would. It not only made me feel better about my more common writing mistakes by noting that I am not alone, it gave me methods to fix them. I knew I had issues with "the big picture" and "telling the story." I had been told as much by past advisors, but it wasn't until this book that I understood what that really meant or how to deal with it. I have already recommended this book to both my advisors and several fellow students, which is probably the best review I can give.
I feel like all the stuff about building appropriate sentences and whatever should be before the section specific structuring. Other than that it's a perfectly fine writing guide.
This is not a fiction book you read before you go to bed. It is one of the "boring" science related books; probably more aimed towards people who just started their career in science as PhD students. However, this book impressed me by its clear messages and very engaging writing style. If you are scientist you don't hear everyday or even at all that science writing is "STORY TELLING". This main message clearly stuck in my head. Author does not just plainly said so, he eloquently "told" his "story" about "story telling" with well chosen examples from published articles and enriched it with his extensive experience in reviewing numerous grant proposal and papers. He didn't stopped with only "story telling"; he represented techniques how to do in the second part of his book. Overall this was probably the best written book on this subject by not only its content, but also its writing style. Therefore I would definitely recommend this book to read.
This book is one of the best I've ever read. It offers awesome writing tools presented in a remarkably clear and engaging way. It covers all aspects of writing, from designing story structure to the usage of specific words, and everything in between. I recommend it even to non-scientists. Although some of its chapters focus specifically on writing in science, most of the book is about writing (and communicating) in general.
I suggest this book to anyone who writes in the sciences. The principles of writing in this book could apply more widely, but the content is geared to science writing. Though Schimel has clear and interesting style, I found it a bit of a chore to read through to the end. There's just a lot to consider when writing. It's totally worth the work though; this is the kind of advice that develops an average paper into an inspiring paper (assuming you've got good science in the first place).
Wow. This was _so_ good! Of course any book on writing has to pass the test that it is well written, and this one is. The message came through loud and clear and it was well structured both across the whole book and at the granular level. I read a lot of books on leadership and the like and what is always a bit frustrating is that the target audience is usually business. It's the same for a lot of large audience books. It's hard to find books like this that specifically target my community: scientists. So this was very well received even if niche, and I've been recommending it to all of my friends who have ever expressed a modicum of interest in effective communication.
Adapting the principles from professional novel writers seemed a little bit of a stretch to me when the author first introduced it. But I as sold after like 10 pages. The author does such an excellent job of that adaptation part. How do the principles of OCAR, SUCCES, LDR, etc apply when you're dealing with scientific papers (that are usually intro, methods, discussion, conclusion) and proposals. And I was especially thankful for the small bits throughout about how the principles applied to proposals (the main focus was on papers). The author's deep experience and interest in this topic, plus being married to a writer, meant that every point made was so thoroughly thought through and backed up by examples. And the examples... it was so useful to see examples of actual scientific text with its problems pointed out and then stepping through the process of improving it. That made every lesson concrete.
The _only_ area I wish had been developed a little more was the application of the writing principles to overall proposal structure. Just as science papers are usually intro/methods/discussion/conclusion and the author did a great job talking about how OCAR etc adapt to that, I would've loved to see the same done for proposals. I don't know structure of proposals is as common across scientific disciplines as it is for papers, but for NASA proposals they are structured as science/technical/management. It's not immediately obvious how to do the adaptation myself, but I will be keeping everything I learned from this book in mind the next time I write a proposal, which is never more than a few months away.
Can't recommend this book highly enough for all of my scientist friends. I did more highlighting on Kindle in this book than I have ever done.
I had to read this book for school. It was useful in what it was trying to teach but hard to read at times. The author also comes off as if they are saying that their was it THE way to write scientific papers which seems a bit arrogant. I did learn more about writing scientific papers well so job well done.
This information puts into focus all my writing mistakes. I am even critical of how I am writing this review! 😅 Turns out most scientific writing is bad: unclear, unapproachable and ultimately unreadable. The author was clear about why it is bad and how to fix it. I hope this will help me with, idk, say the 20 page paper I have to write soon.
This was sooo helpful. There was a lot of stuff in here that intuitively makes sense, but seeing it explicitly stated and fully explained makes it so much more concrete and actionable. I wish I'd been recording useful quotes as I was reading, but on the bright side, each chapter is pretty self-contained so if I feel I could brush up on something I can go back and just read the relevant one instead of the whole thing.
Important takeaways: - Don't make your data say something it's not. A story of a smaller scope done well is much better than trying to force the more expansive, impactful story you maybe initially tried to create but ended up with data to the left of it. - The job of the writer is to make the job of the reader easy. - The scope of the opening of a paper should be no broader or narrower than the conclusions/takeaways. - Define the knowledge gap you are filling. Focus on that. - Writing is mostly rewriting. - Editing for nitpicky things (language, grammar) is always much easier than structural edits, but structure is much more important to get right. - There is no dataset that is so interesting that dull writing couldn't make it boring, and there is no dataset so dull that there is no novel or interesting story to make out of it.
Read for a grant writing class. Useful, especially with its use of examples. Focuses mostly on how to structure your story in scientific writing to make it the must impactful and clear.
It’s been a year since I last read something on writing. This break went well: I regained the curiosity and forgot some bits. I got ready to perceive even some common pieces of advice without impatience and frustration, “I’ve already heard it elsewhere, now where’s the new stuff?”. And I fully appreciated the attempt made by Joshua Schimel to share his writing experience in a thorough and sincere way.
If I had to choose a single word to describe the essence of this book, it would be “story”. Finding a story and telling it is a central idea of what writing is about. Every chapter adds to this idea, and together they form a story, indeed.
I wouldn’t say the book is a practical guide: it goes far beyond such a goal. It brings up controversial issues, discusses the background behind decisions that scientists have to make as writers. On the other hand, these speculations never stay pointless: they do resolve in concrete helpful suggestions. Each chapter is also accompanied by exercises, expanding the opportunities for application. (I must admit that, same as with The Scientist's Guide to Writing: How to Write More Easily and Effectively Throughout Your Scientific Career, I missed the exercises. They are quite demanding, and I’m thinking of dedicating special time to them, maybe with a group of interested peers).
A would recommend this to anyone who is a scientist and hence, as Joshua Schimel puts it, is professional writer.
If you're an experienced writer, a lot of what Schimel says in this book is going to already be quite familiar to you. But the trouble is, a lot of scientists are not particularly well trained as writers, and so this guide might be quite useful to both practicing scientists and graduate (or even undergraduate) students interested in improving their writing.
The author's approach is to unpack the idea of good writing in a highly analytical way. Drawing both from examples of good science writing and from quality fiction, the author describes a method of presenting science narratively that I think will serve almost any writer well.
There is a danger in this approach, however. Because Schimel has distilled what is fundamentally an art (or at least a craft) into a series of formulae and abstractions, there is a danger of following the advice TOO closely and ending up with a finished piece that has no soul. While a soulless formulaic work might be superior to some of the writing I've read in the sciences, it shouldn't be the goal. Nor does Schimel suggest formulaic writing IS the goal; it's just that his method could produce that if the practitioner isn't careful.
Be aware also that this book is intended for scientists to learn about writing, not for writers to learn about how to write science. These are related topics, and the book covers some ground that would be applicable to both groups, but they are not the same things. If you're already a great writer and you're just trying to learn how to apply those skills to science, you'll find this book full of advice with which you already agree, but not much that will serve your particular purpose. This is a book for scientists.
But if you are a practicing scientist and you want your papers to have a little more life and actually attract readers' attention rather than cluttering up the journals without ever getting cited, you could do a lot worse than to read this book.
What is this book about? In a nutshell, it teaches you how to craft better stories, specifically in the context of your research.
Schimel does this by first giving some high level principles to guide your entire introduction, and then diving deep into the nitty gritty. He helps you improve your writing at section level, the paragraph level, the sentence level, and even in word choice. And how does he do this? By giving you examples of bad writing, pointing out exactly why it is bad (in the context of some larger lesson encapsulated by the chapter or section), and then showing how you can fix it.
This book does a great job at giving you guiding principles on how to be a better writer, and then drilling down into exactly how to execute those principles. An absolutely worthwhile read.
Two key takeaways for me: 1. Science writing (for papers and in general) is well received when it is sticky. Use the following principles of SUCCES to improve stickiness: S: Simple U: Unexpected C: Concrete C: Credible E: Emotional S: Stories
2. When thinking about how to structure your writing, from a high level down to sentences, consider using one of the well-established structures: OCAR, ABCDE, LDR, and LD. Thinking about the target audience, and in particular how much patience they have is a good rule-of-thumb to help decide. Most patience to least patience: OCAR -> ABCDE - LDR - LD. O: Opening C: Challenge A: Action R: Resolution
A: Action B: Background C: Climax D: Development E: Ending
Best book on writing for scientists. A must-read for anyone whose careeer is determined by the quality of their research papers and proposals. After reading this book, I found my papers looking like garbage. I realized that for all those years doing and writing science, I had not known how to write a paper.
Schimel argues that writing science is a form of story telling, that the article must convey a coherent story as clearly as possible. From that standpoint, Schimel advocates for the OCAR structure: opening, challenge, action then resolution. The structure and its variations, such as LD (lead - development), should be maintained throughout the article from article-level down to paragraphs and sentences. The book then discusses how to achieve concision and clarity. It wraps up with some thoughts and advices on writing for young scientists.
The writing strategies and advices are persuasive. They fit well with academic writing (papers and proposals). Schimel himself is a renown scientist who learned writing the hard way. That's why he understands the problems in scientific writing so well. His points are illustrated by a large number ofexamples, both good and bad ones. It is instructive and entertaining to see "live editing" when he fixes and polishes bad ones.
The book itself is also an example of good writing! Schimel is clearly an excellent writer. There is just too much to learn from the book that I can't capture in this review. You have to read and enjoy it yourselves.
Probably my favorite book on this topic. Read as needed and skipped around a bit. Some things that stuck with me in the first 2 chapters:
Chapter 1 As a scientist, you are a professional writer.
You dont succeed by getting papers published, but rather by getting them cited - the influence of your work on the field is what matters
it is the author's job to make the reader's job easy
Chapter 2 the further along the path from data to understanding you can take your work and your papers, the more people will be able to assimilate your contributions and use them to motivate their own work and ideas - and that should be your goal.
Rosalind Franklin's photo was good data but it didn't tell the full story of DNA structure and its implications, that's why it's easier to remember Watson and Crick's model
The flow of science, from data to understanding: data -> information -> knowledge -> understanding. If you dont provide understanding your readers will be left searching for it
stories work when the plot arises from the characters, not when characters are contrived to propel a plot - the data are the supporting characters and the overarching questions are the main characters
Let me start this review by making it clear that this book was helpful; it has improved my science writing and specifically helped my in my research internship (where I was lucky enough to hear Dr. Schimel speak on two occasions).
However, this book could have done with another revision. There were several typos, and Schimel often contradicted himself in his writing in a way that wasn't necessary. It could also be even shorter - most of this information he was able to condense into two presentations (that only took an hour each because he tends to ramble a bit when speaking).
I think the examples could also use some more consistency. The most effective examples were broken up into sections to highligh exactly what they did right or wrong. At other times, examples were just thrown onto the page one after the other with only a brief comment, which wasn't entirely helpful.
Finally, I have to point out that quoting Stephen King's advice on revising a draft to make it shorter is definitely a choice, yeah?
An essential read for any technical writer. You may not become a better writer overnight but you will at least avoid the common mistakes and organize your thoughts better on paper. Bottom line: follow the OCAR structure (Opening, Challenge, Action, Resolution) as you tell your story about the data to create understanding and knowledge. That structure is important and the story mindset helps drive your points. Your number one job is to make the reader's job easy. Avoid jargon, use verbs, and aim for clarity. The book breaks down each part by layers: structure, paragraphs, sentences, and words. Discussing how to discuss, provides restrictions and limitations, and resolves the questions on conclusions. Many examples are provided from journal papers - my best one was on the editing process. This should be part of every writer's bookshelf. Now, only if I could convince my students.
"Writing Science" by Joshua Schimel is an indispensable resource for scientists aiming to enhance their writing abilities. Schimel underscores the significance of clear and effective writing within the scientific realm, offering practical guidance to achieve this goal. A key insight from this book is that proficient writing is not only crucial for getting papers published, but also for garnering citations. Schimel's valuable perspectives on the role of storytelling in scientific writing highlight how a captivating narrative can engage readers and facilitate the elucidation and communication of intricate scientific concepts. In summary, "Writing Science" serves as an outstanding guide for scientists seeking to refine their writing skills and make a more substantial impact with their research.
"The more papers we publish and the more they are used, the more successful we are."
Easy to read and full of practical advice for communicating science. Bridges the storytelling with the sometimes dull approach to writing in the scientific community, and strives to find a middle point where scientific rigor meets reader engagement. My only (minor) complaint is having to bear the sometimes patronizing and a little bit boastful tone in the last part of the book; although there are glimpses of humility, in particular the honest intro in the last chapter, the academic nature of the author is there. Finally, for better or worse, reading this book reminded me of a saying: "All business is show business".
One final word of warning: despite the core the message holds today, some of the tools suggested by the author are outdated, mainly because of the AI trend, so, keep this in mind; after all it is a book whose first edition was published in 2011.
If you are a scientist who writes about science and you haven’t read this book, WHAT ARE YOU DOING WITH YOUR LIFE?
I urge mentors to make this a mandatory read for trainees.
The author has collected many otherwise scattered writing lessons (that you may or may not pick up along the course of your career) and presents them here all in one excellent resource.
It gives structure to problems you might have intuitively picked up on in the past, so that now you can concretely identify and fix them more quickly.
Taking Schimel’s guidelines to heart will help you shed any bad and pretentious habits you’ve inherited from ghosts of ‘The Academy’ past.
Schimel has some great tips for the scientific writer, but sometimes seems to contradict himself. He also seems to have very concrete ideas for how a paper should be written, and disapproves of all other styles. If we all wrote like Schimel, papers would be 3 pages long and have nothing but short, powerful sentences. I found a lot of good ideas that I will definitely incorporate in my own writing, but there were also things I think I shall leave to Schimel for his own. Worth a read, but I wouldn't take it as gospel.