Tag: Beta Readers

Errors in Writing

This is an update of a post that originally appeared on March 18, 2011.

I get upwards of 65 e-mails about my books on most days. Some of the conversations I have with readers are amazing and many readers have continued to write me for years. It’s gratifying to know that my books are helping people—it’s the reason I continue writing. Although I make a living from writing, I could easily make more money doing just about anything else. The thought that I might help someone do something special is why I stay in this business. When I actually hear about some bit of information that has really helped someone, it makes my day. I just can’t get the smile off my face afterward.

Of course, I’m constantly striving to improve my writing and I do everything I can to help the editors that work with me do a better job too. Good editors are the author’s friend and keep the author from looking like an idiot to the reading public. In fact, it’s the search for better ways to accomplish tasks that led me to create the beta reader program so many years ago. Essentially, a beta reader is someone who reads my books as I write them and provides feedback. The extra pair of eyes can make a big difference. Beta readers receive my thanks in the book’s Acknowledgments. Sometimes I provide other perks, such as a free copy of the book, depending on the level of beta reader input. (If you’d like to be a beta reader, please contact me at [email protected] for additional details.)

A typical book has five beta readers, but sometimes there are more or less of them. They provide all sorts of input that ranges from finding grammatical, spelling, and technical errors, to providing advice on how to approach a particular topic for readers from other nations or those with disabilities. Some of my beta readers are critical thinkers and play devil’s advocate, others are great at pointing out inconsistencies, especially in my artwork. So, there is no typical beta reader; they have a very wide range of experiences and provide me with a wide range of insights.

You’d think that with all the pairs of eyes looking at my books, they’d come out error free. After all, it isn’t just me looking at the book, but several editors and the beta readers as well. Unfortunate as it might seem, my books still come out with an error or two in them. The more technical the topic, the greater the opportunity for errors to creep in. Naturally, the errors are amazingly easy for just about everyone else to pick up! (I must admit to asking myself how I could have missed something so utterly obvious.) When there is an error found in the book, I’ll provide the information to the publisher so it’s fixed in the next printing. The error will also appear on the book’s errata page on the publisher’s site. If the error is significant enough, I’ll blog about it as well. In short, I want you to have a good reading experience so I’ll do everything I can to hunt the errors down and correct them.

However, not every seeming error is actually an error. There are times where an apparent error is simply a difference of opinion or possibly a configuration difference between my system and the reader’s system. I’ll still try to figure these errors out, but I can’t always guarantee that I’ll fix things in your favor. After all, another reader has probably found still other results or has yet another opinion on how I should present material in the book.

The long and short of things is that despite my best efforts, you’ll probably encounter an error or two in my books and I apologize for them in advance. We’ll also continue have differences of opinion and that’s usually the source for new ideas and new ways of viewing things. I’m honest enough to admit that I do need your help in creating better books, so I’ll always listen to you and think about what you have to say. I hope that you’ll continue to read my books and do amazing things with the information you find therein. The results of your researches are truly the reason I remain in this business and I realize that we’re in this together. Thanks for your continued support!

Beta Readers Needed for Amazon Web Services for Admins for Dummies

I still remember Amazon Web Services (AWS) when it was simply a method for getting information about Amazon products, making sales, and getting product status. The original web service didn’t do much, but people absolutely loved it, so it continued to evolve. Amazon has put a lot of work into AWS since that humble beginning and now you can perform all sorts of tasks that have nothing to do with buying or selling anything. You can create an entire IT structure for your organization that doesn’t involve any of the micromanagement, hardware purchases, software purchases, and other issues that kept IT from doing what it was supposed to do in the past-serving user needs in the most efficient manner possible.

There are a number of AWS books either published or currently in the process of being published, but these books don’t really answer the one question that everyone appears to be asking in the forums online, “How do I get started?” However, in recent years this has changed with more blogs talking about the subject. You can even check out this great AWS blog for more information. As for books, most of the titles out there right now answer questions for a specific group after that group has installed the product and gotten started with it. AWS is immense and is naturally intimidating. Unfortunately, the getting started documentation from Amazon is incomplete, outdated, and hard to understand. Amazon Web Services for Admins for Dummies helps administrators (the focus group) and others (such as DevOps and developers) get started so that they can actually make use of that next level up book. Here are the sorts of things you see covered in the book:

  • Part I: Uncovering the AWS Landscape
    • Chapter 1: Starting Your AWS Adventure
    • Chapter 2: Obtaining Free Amazon Services
    • Chapter 3: Determining Which Services to Use
  • Part II: Configuring a Virtual Server
    • Chapter 4: Creating a Virtual Server Using EC2
    • Chapter 5: Managing Web Apps Using Elastic Beanstalk
    • Chapter 6: Responding to Events with Lambda
  • Part III: Working with Storage
    • Chapter 7: Working with Cloud Storage Using S3
    • Chapter 8: Managing Files Using Elastic File System
    • Chapter 9: Archiving Data Using Glacier
  • Part IV: Performing Basic Database Management
    • Chapter 10: Getting Basic DBMS Using RDS
    • Chapter 11: Moving Data Using Database Migration Service
    • Chapter 12: Gaining NoSQL Access Using DynamoDB
  • Part V: Interacting with Networks
    • Chapter 13: Isolating Cloud Resources Using Virtual Private Cloud
    • Chapter 14: Connecting Directly to AWS with Direct Connect
  • Part VI: Getting Free Software
    • Chapter 15: Using the Infrastructure Software
    • Chapter 16: Supporting Users with Business Software
  • Part VII: The Part of Tens
    • Chapter 17: Ten Ways to Deploy AWS Quickly
    • Chapter 18: Ten Must Have AWS Software Packages

As you can see, this book is going to give you a good start in working with AWS by helping you with the basics. Because of the subject matter, I really want to avoid making any errors in this book, which is where you come into play. I’m looking for beta readers who want to use AWS to perform basic administration tasks, even when those tasks are related to a home office. In fact, I have a strong interest in trying to meet the needs of the small-to-medium sized business (SMB) because many of the other books out there cover the enterprise to the exclusion of these smaller entities. As a beta reader, you get to see the material as I write it. Your comments will help me improve the text and make it easier to use.

As you can see from the outline, Amazon Web Services (AWS) is actually a huge array of services that can affect consumers, Small to Medium Sized Business (SMB), and enterprises. Using AWS, you can do everything from back up your personal hard drive to creating a full-fledged IT department in the cloud. The installed base is immense. You can find case studies of companies like Adobe and Netflix that use AWS at https://aws.amazon.com/solutions/case-studies/. AWS use isn’t just for private companies either-even the government is involved. That’s why Amazon Web Services for Admins for Dummies has a somewhat narrowly focused audience and emphasizes a specific set of tasks that it will help you perform. Otherwise, a single book couldn’t even begin to cover the topic.

In consideration of your time and effort, your name will appear in the Acknowledgements (unless you specifically request that we not provide it). You also get to read the book free of charge. Being a beta reader is both fun and educational. If you have any interest in reviewing this book, please contact me at [email protected] and will fill in all the details for you.

 

Facing the Blank Page

Most writers face writer’s block at some point. You have a blank page that’s waiting for you to fill it and you have a vague notion of what you want to say, but the text simply doesn’t come out right. So, you write, and write some more, and write still more, and hours later you still have a blank page. Yes, you’ve written many words during that time—all of them good words—just not the right words.

Every piece of writing I do starts with an outline. Even my articles start with an outline. Creating outlines help you focus your thoughts. More importantly, they help you to see how your thoughts will flow from one idea to the next. Sometimes, if you’re honest with yourself, you’ll discover that you really don’t have anything more than a vague idea that will never become an article, white paper, book, or some other piece of writing. Of course, that’s really the reason for this exercise—to see if you have enough information to even begin writing. If you don’t have enough information, then you need to research your topic more. Research can take all sorts of forms that include everyone from reading other texts on the topic, to doing interviews, to playing. That’s right, even playing is an essential part of the writer’s toolbox, but this is a kind of practical play that has specific goals.

Once you do have an outline and you’re certain that the outline will work, you need to mark it up. My outlines often contain links to resources that I want to emphasize while I write (or at least use as sources of inspiration). A lot of writers take this approach because again, it helps focus your thoughts. However, an outline should also contain other kinds of information. For example, if a particular section is supposed to elicit a particular emotion, then make sure you document it. You should also include information from your proposal (book goals) and your reader profile (who will read a particular section) in the outline. Your marked up outline will help you understand just what it is that you really want to write. In reading your outline, you can start to see holes in the coverage, logic errors, and ideas that simply don’t fit.

Moving your outline entries to the blank page will help you start the writing process. Convert the entries to headings and subheadings. Ensure that the presentation of the headings and subheadings is consistent with the piece as a whole. Unfortunately, you can still end up with writer’s block. Yes, now you have some good words on the page, but no real content. An outline is simply a synopsis of your ideas in a formalized presentation after all.

Write the introduction and the summary to the piece next. The introduction is an advertisement designed to entice the reader into moving forward. However, it also acts as a starting point. The summary doesn’t just summarize the material in the piece—it provides the reader with direction on what to do next. People should view a good summary as a call to action. By creating the introduction and the summary, you create the starting and ending points for your piece—the content starts to become a matter of drawing a line between the two from a writing perspective.

At this point, you have enough material that you could possibly ask for help. Try reading your piece to someone else. Reading material aloud uses a different part of the brain than reading the same material silently. Discussing the material with someone else places a different emphasis on the material. The other party can sometimes provide good suggestions. You may not use the suggestions directly, but listening carefully can often present you with creative ideas that you wouldn’t have considered otherwise.

It’s important not to overwork the piece. Sometimes you need to do something else for a while. Yes, you always want to spend time in research and thinking your piece through, some writing is often done in the subconscious. Fill your head up with as many creative ideas, fascinating thoughts, and facts that you can, and then do something that actually will take your conscious mind off the topic. You might watch a television show or movie, go for a while. have coffee with a friend, take a nap, or do any of a number of other things. The important thing is to forget about the book for a while. Often, you’ll find that the now semi-blank page doesn’t present a problem when you return. Let me hear about your ideas for dealing with the blank page at [email protected].

 

Beta Readers Needed for Python for Data Science for Dummies

According to just understanding data, a data science consultancy, “data science lies at the intersection between statistics, programming and hacking.” And many businesses can take advantage of data science because it can help them identify patterns that you can use to improve your business’s operations. But, what exactly is it?

Data science is the act of extracting knowledge from data. This may seem like a foreign concept at first, but you use data science all the time in your daily life. When you see a pattern a sequence of numbers, your mind has actually used data science to perform the task. What data science does is quantify what you do normally and make it possible to apply the knowledge to all sorts of different technologies. For example, robots use data science to discover objects in their surroundings.

Of course, data science is used for all sorts of applications. For example, data science is used with big data to perform tasks such as data mining or to predict trends based on various data sources. The fact that your browser predicts what you might buy based on previous purchases rests on data science. Even your doctor relies on data science to predict the outcome of a certain series of medications on an illness you might have.

Even though data science first appears easy to categorize, it’s actually huge and quite difficult to pin down. It relies on the inputs of three disciplines: computer science, mathematics, and statistics. There are all sorts of sub-disciplines used as well. Because of the depth and width of knowledge required, a data scientist often works as part of a team to tease out the meanings behind the data provided to solve a problem.

Python for Data Science for Dummies provides you with a beginning view of data science through the computer science discipline using a specific language, Python. The capabilities of Python as a language make it a perfect choice for this book. While reading this book, you’ll see these topics explained:

  • Part I: Getting Started with Data Science & Python
    • Chapter 1: Discovering the Match between Data Science and Python
    • Chapter 2: Introducing Python Capabilities and Wonders
    • Chapter 3: Setting Up Python for Data Science
    • Chapter 4: Reviewing Basic Python
  • Part II: Getting Your Hands Dirty with Data
    • Chapter 5: Working with Real Data
    • Chapter 6: Getting Your Data in Shape
    • Chapter 7: Shaping Data
    • Chapter 8: Putting What You Know in Action
  • Part III: Visualizing the Invisible (2 Pages)
    • Chapter 9: Getting a Crash Course in MatPlotLib
    • Chapter 10: Visualizing the Data
    • Chapter 11: Understanding Interactive Graphical and Computing Practice
  • Part IV: Wrangling Data
    • Chapter 12: Stretching Python’s Capabilities
    • Chapter 13: Exploring Data Analysis
    • Chapter 14: Reducing Dimensionality
    • Chapter 15: Clustering
    • Chapter 16: Detecting Outliers in Data
  • Part V: Learning from Data
    • Chapter 17: Exploring Four Simple and Effective Algorithms
    • Chapter 18: Performing Cross Validation, Selection and Optimization
    • Chapter 19: Increasing Complexity with Linear and Non-linear Tricks
    • Chapter 20: Understanding the Power of the Many
  • Part VI: Parts of Ten
    • Chapter 21: Ten Essential Data Resources
    • Chapter 22: Ten Data Challenges You Should Take

As you can see, this book is going to give you a good start in working with data science. Because of the subject matter, I really want to avoid making any errors in book, which is where you come into play. I’m looking for beta readers who use math, statistics, or computer science as part of their profession and think they might be able to benefit from the techniques that data science provides. As a beta reader, you get to see the material as Luca and I write it. Your comments will help us improve the text and make it easier to use.

In consideration of your time and effort, your name will appear in the Acknowledgements (unless you specifically request that we not provide it). You also get to read the book free of charge. Being a beta reader is both fun and educational. If you have any interest in reviewing this book, please contact me at [email protected] and will fill in all the details for you.

 

Expressions of Gratitude

As this year ends, I realize just how much has happened and how much I’ve grown as a person. The turmoil actually began when my wife became ill over six years ago, but intensified when she died in April. Since that time I’ve had to answer a lot of questions about my life and how it would change without Rebecca in it. Some answers are coming, some are still unknown, and a few have been satisfied. The most important question I had is whether my friends would be there to support me during this trying time and they’ve been more than up to the challenge. It’s good to have people you can rely upon to help keep the blog posts written, the books and articles in process, and the new fields of endeavor in progress. It would be impossible for me to name everything my friends have done for me and I wouldn’t even try. All I can do is express my extreme gratitude for them and hope they know how much they mean to me.

I’ve talked many times about how self-sufficiency is more about trying to do things on your own in as much as possible, but then realizing that no one can make it completely alone. Self-sufficiency can and does go wrong when people think that it means living like a hermit away from all human contact. Yes, I’m self-sufficient in many ways, but I’m also smart enough to know that I depend on others for help when needed. Getting that help is one thing—ensuring they know how much their help means is quite another. Expressing gratitude, even for the seemingly simple things, is an essential part of the self-sufficiency experience. It’s not possible to go wrong when you’re grateful for the help you receive.

As this year ends, I hope that you’re truly grateful for all of the small ways in which people have helped you this last year and every year to come. More importantly, I hope that you’ll actually take the time to thank your helpers in person, through a phone call, or by sending them a card (or possibly all three). The people you can count on, those few true friends in your life, are more important than anything else here on earth.

With this in mind, I also want to take time in this post to thank all my readers.  Every purchase you’ve made has helped keep me in business so that I can continue helping others. Every question you’ve asked has helped me produce better materials. The gracious contributions of my beta readers have been appreciated most of all. Goodbye to the old year; happy new year one and all!

 

Developing the Reader Profile

A lot of people have written to ask me about writing books—about the techniques I use to develop a useful book. So far, all of my books are technical in nature. Not all of them are computer-related, but the majority are. The sorts of books that I write is changing and you’ll likely see me write books in other areas in the future. Whether I ever write fiction remains to be seen, but I do plan to branch out into other areas. No matter what I end up writing, I expect that I’ll use many of the same techniques when writing future books as I use to write my current books. Mainly, I need to find a way to communicate the ideas that I understand in a form that the reader can understand. It doesn’t matter what those ideas are—they exist in my head and I need to get them out of my head and into the reader’s head.

When I’m putting an outline together, I try to put myself in my reader’s shoes. Sometimes that means actually doing a little play acting and trying out things to see how I’d feel if I were the reader. Yes, conveying technology, or any other topic for that matter, means understanding the reader and how the reader feels. It means respecting the reader as a person and understanding that the reader has specific needs, as well as specific skills. Sometimes I’ll talk to the beta readers who are reading my books about issues or bounce ideas off the technical editor for my book. I’ll review materials online and see what people are discussing online. In short, I develop a profile of my reader and roll it around in my head until I can start to see a technology from the viewpoint of my reader. It’s not an easy thing to do, but it’s a necessary skill to develop.

In a way, I’m creating a relationship with what I think my reader will be. Beta readers do offer the opportunity to interact with actual readers, but my reading audience is relatively large, so it really does come down to creating a rapport with an idealized reader—one who encompasses everything I expect that my reader will be. The relationship takes form in a profile that I write down and review relatively often as I write the book. As I come across additional insights during the writing process, I develop the profile of my reader more fully. I keep constantly asking myself how I would talk about the subject at hand if I were sitting in a coffee shop (or some other relaxing environment) with the reader.

To a certain extent, I need to consider the reader’s need for self help. I can’t provide any reader with a specific answer for most problems the reader will encounter. To do so, I’d need to write immense books that no one would want to read because they’d be too bulky. I can provide the reader with knowledge and insights, but I can’t provide the reader with a precise response to any given problem because at the time I write my book, the problem is undefined. So the communication takes the form of ideas, rather than a specific procedure, in most cases.

Authors are hindered by a number of factors. The most important of these issues is the inability to communicate with the reader in real time. It’s the reason that I try to make myself so accessible through e-mail and by writing this blog. Even with these additional levels of communication, however, there are still barriers to communication. For example, I can’t easily read your body language to determine whether my response is actually helpful—I must make my best guess. When writing a book, I have to anticipate your needs and hope that my guesses are good ones because they are, in fact, guesses.

The reader profile doesn’t have to take a specific form, but it does need to provide you with a complete picture of the reader. Even if you define a few reader aspects incorrectly, having a reader profile will help you remain focused throughout the writing process on a particular reader. Here are the sorts of questions I ask myself when creating a reader profile:

 

  • What is the reader’s education level?
  • Will this reader understand these specific concepts?
  • When will the reader be reading my book?
  • How will the reader react to certain types of information?
  • Are there social biases I need to consider when communicating with this reader?
  • How does the reader view the subject at hand?
  • Is the reader likely to have language issues or special needs?
  • Will the reader be alone or part of a team?
  • How does the reader view me?


Most of my books require that I ask other questions, but this a good sampling of the sorts of questions that I ask myself. You’d think that with all of this effort spent considering my reader that I’d communicate quite well. However, there have been books where I ended up missing the reader completely with my profile. I directed the book at one audience, but another audience actually found the book more helpful and purchased more copies of it. When that happens, I get a lot of e-mail from a lot of disgruntled readers (and the online reviews are also less favorable). These failures require that I go back and review the premises on which I based my book and make corrections. I maintain statistics for the book, and if I get the chance to write an update, I tweak the reader profile accordingly to better meet the needs of the audience that purchased my book.

Anyone writing anything can benefit by creating a reader profile. If you currently write documentation, but don’t create a reader profile, I encourage you to do so because you’ll end up with a far better document as a result. As the years have passed, my profiles have gotten better, but I’m under no delusions that I’ll ever write the perfect profile. Even so, I’d never consider writing a book now without creating a reader profile first. Let me know your thoughts about using reader profiles at [email protected].

 

Not Mere Words

A number of readers and editors have asked me about the pains I take in choosing words for my books and articles. Let’s say that it was a revelation that has prompted me to work so hard to create the right word combinations. It came to me one day while I was looking at samples in a paint store. I was looking at paint chips for just the right sort of white. The store must have had twenty or more versions of white—everything from antique white to Arizona white. The winter white intrigued me because it almost looked a bit blue in the store’s light. The idea is that each name is supposed to express the nuance of color—to create a picture in the viewer’s mind.

Many people see words as text. However, text is an abstraction of a word—the presentation of that word on paper or on screen. Words are expressions of ideas. A word creates a picture of an idea or object in the viewer’s or hearer’s mind. Using the right word transfers an idea precisely from your mind to the mind of someone you want to share an idea with. Consequently, like the paint samples in the store, the nuance of words you choose is important if you want to maintain the clarity of the idea. Winter white isn’t the same as antique white, much as submitting to someone’s authority isn’t the same as acquiescing to someone’s authority. You’ll find both words on the same page in a thesaurus, but they’re different. There is a nuance of difference in the meaning.

There is another important lesson you can learn from paint chips. When you place a winter white chip next to a blue chip, the blue in winter white stands out clearly. However, place the same winter white chip next to a red chip and suddenly winter white looks more white than blue. The context of the paint chip has changed. Likewise, the subtle meaning of a word changes in relation to the words around it. You must consider the context of the word in order to understand its true meaning. In fact, most dictionaries include multiple meanings for a word in order to convey this sense of context.

However, a word is an expression of an idea and not the idea itself. Both the writer and the reader must understand the word in order for the transference of an idea to take place. When the writer and reader have the same understanding of the word, the transference is clear, but it become less clear as the understanding of the two diverge. When a reader doesn’t understand a word, there isn’t any transference at all. Consequently, a well-read author could use terms that a reader doesn’t understand, with the result that reader is confused, not educated or entertained. So, better authors define unusual terms in context, to help readers understand the term and still derive the nuance of meaning the author originally intended.

Technical writing is perhaps one of the more difficult mediums when it comes to word choice. An author needs to convey ideas precisely, which means that a significant range of word choice is both warranted and necessary. However, in order to educate the broadest range of readers, the author is necessarily limited by the need to simplify the text, so as many people as possible can understand it. This dichotomy presents the author with a serious dilemma that editors can sometimes make worse by insisting only on accuracy or only on simplicity, without considering the art behind the writing. (A good editor supplies alternative terms that the author can choose from in order to retain clarity without increasing complexity.) The need to convey ideas clearly in a form the reader can understand is one of the reasons I use beta readers to help refine the content of my books. Beta readers act as a sanity check by helping the author determine which words truly are beyond the average reader’s understanding.

All this leads to a practice that I’ve had since the day of my vision in the paint store. I learn a new word each day. In fact, I use two sources: A.Word.A.Day and Dictionary.com. Both sources send a new word to my e-mail each morning and I choose the word I want to learn that day from them. I may not use all of these words in a book, but the words do expose me to new ideas that will appear at some time in my books. Words are expressions of ideas—the more you learn, the more ideas you possess. What is one of your favorite words? Have you ever found yourself unable to convey an idea because you lack the appropriate word? Let me know at [email protected].