Home » Archives for Chris Minnick

Author: Chris Minnick

Chris Minnick is a prolific published author, blogger, trainer, web developer and co-founder of WatzThis? (www.watzthis.com).

He has authored and co-authored books and articles on a wide range of Internet-related topics. His published books include: React JS Foundations, Adventures in Coding, JavaScript For Kids For Dummies, Coding with JavaScript For Dummies, Beginning HTML5 and CSS3 For Dummies, Webkit For Dummies, CIW eCommerce Certification Bible, and XHTML.

In addition to his role with WatzThis?, Chris is a winemaker, painter, novelist, swimmer, cook, and musician.

Coding All-in-One For Dummies 2nd Edition

My Latest Book: Coding All-in-One For Dummies, 2nd Edition

I’m excited to announce that the latest book I worked on, Coding All-in-One For Dummies (2nd edition), will be available in stores starting this week!

When I was asked to be the lead author for the 2nd Edition of Coding All-in-One For Dummies, I immediately said “YES!” It was thrilling to work together with so many great expert authors to update this important and successful book.

My first goal with writing the book was to make sure it accurately reflected the state of coding today. The first edition of Coding All-in-One For Dummies came out in 2017. Although the foundations of coding taught in the first edition are still the same, much has changed since then.

Important changes include the shift away from mobile web apps and towards cross-platform app development, JavaScript has evolved significantly, Python has been upgraded, cloud computing has become an essential part of coding, responsive web design has gone from being a good idea to a requirement for any web site, and much more.

My second goal with this book was to make it fun and accessible for anyone, regardless of their previous coding experience. There’s a lot of information in this book, but if you take your time and play with it, it will pay off.

My third goal was to stay within the page count limit set by my editors. Oops! I love coding and everything about it. There was so much I wanted to tell you about coding that I ended up going over my page limit by around 400 pages. The resulting manuscript would have been impossible to print in one volume, I was told. So, after some careful pruning, I was able to get down to just 200 pages over the maximum size. I begged for a special exception to the rule and even took out my usual long list of thank yous to my family and third-grade teachers to save a page. Finally, even in this time of skyrocketting paper prices, the wonderful people at For Dummies agreed that this book is perfect, and they’d figure out a way to print it.

I hope you enjoy this book! Thank you for beginning, or continuing, your coding adventure with me.



Backpack Living – Lessons Learned

Prior to the pandemic, I used to travel a lot, and I traveled with a lot of stuff. I’d bring a large suitcase (to check) and a laptop bag and sometimes also a backpack for even a 3-day trip. When I got tired of checking and hauling the suitcase, I switched to using Dufl.com, which was great. The idea was that you sent them the clothes and other items that you travel with. Before you go on a trip, you’d let them know where you were going. They’d FedEx a suitcase with your clothes to your destination. When your trip was done, you’d throw everything into the suitcase, put the provided shipping label on it, and leave it at the front desk. Dufl would wash and store your clothes until the next time you traveled. I’d probably still use Dufl if they hadn’t gone out of business due to the pandemic.

But, alas, the pandemic has brought much change to my life. Earlier this year, I decided to get rid of nearly everything I own and see what that’s like.

I’m almost there. At the end of April 2021, I’m leaving my current home of Astoria, Oregon and I have a one-way ticket to Detroit. I plan to bring nothing but my backpack (an Aer Travel Pack 2 to be specific) and my saxophone (a Yamaha YTS-61, to be specific).

As a test trip, I just finished a 5-day trip to Sacramento. I’ve learned a few important lessons about packing and what to stuff in my backpack. I wanted to jot those down, and thus this post.

What I learned this week:

  1. My over-the-ears headphones are giant and take up a lot of space in my pack. They’re essential (especially when everyone outside is screaming all night long) so I’m thinking I should hang them from my backpack somehow rather than stuffing them inside it.
  2. I’m bad at counting. I brought too many t-shirts, and not nearly enough socks
  3. My laptop (2015 macbook pro) is heavy, and the charger takes up a lot of space that would be better used for socks.
  4. My shoes would be a lot more comfortable if I had brought toe nail clippers.
  5. I need a toiletries bag that’s small and doesn’t leak. Also, floss and a toothbrush cover.
  6. I need a bag that packs very small that I can use to hold dirty clothes so they don’t make my clean clothes dirty.
  7. Bring woolite.
  8. Buy socks that dry faster

Chris Answers Questions About Writing

People often ask writers about their daily schedules, hoping to get some nugget of advice that’s going to help them finally start or finish the novel they’ve been planning. I totally understand where this question is coming from, and I ask the same question of anyone who manages to exercise on a regular basis. Writing can be difficult, and a different perspective or the right advice can sometimes make it easier.

I’m the kind of writer who really likes to tell stories (often conflicting) about the things that I do and don’t do — so I have fun with this question. I never mean to mislead anyone or give out bad advice…I think the things I say make sense…for example: “write without pants on before 6am, edit with pants on after 6pm”. But, take everything I say on this matter with a grain of salt, because I’d be some sort of crazy robot if I actually followed my own advice half the time.

There was an article I read recently where someone tried to actually follow the routines that various authors claimed they followed…but he wasn’t willing to follow through with Hunter S. Thompson’s supposed routine and so the article was sort of lame.

At any rate, I make up stories about how I write, and here’s the latest installment, with some other fun questions and answers too. This is from Nancy Christie’s series of interviews called One on One: Insights Into The Writer’s Life.


I saw the best minds of my generation destroyed by startups,

        weakened caffeinated bloated,

hunching themselves over glowing screens at night looking

        for a syntax error,

filthyheaded coders burning for the algorithmic

        connection to the starry dynamo in the machinery of Steve,

who overworked and malnourished and burned-out and tired stayed up typing

        in the fluorescent wired-ness of south park warehouses sitting

        in the sacks of Herman Miller contemplating Java,

who bared their brains to VCs on Caltrain and saw

        Torvaldsian angels stammering at conference room tables


who eased through universities with curious humor

        improvising Yahoo! and ebay among the

        networks of war,

who dropped out of the academies for startups & committing

        hurried code to be the first to market,

who packed into unadorned rooms in moscone, stuffing their

        totebags with t-shirts and listening to the Guru with

        the laser,

who lost years working for equity marketers in Austin

        with a half-baked idea,

who ate pizza at meetups or drank microbrew at Google

        Numbed, wasted, or killed their minds night after night

with HTML, with CSS, with servers, earbuds and

        endless javascript,

insufferable meetings with clients and lawyers in

        the open workspaces of Brannan & Bryant,

        interrupting all the motionless focus of code between,

Mountain Dew rush of flow, laptop white fruit LCD wakes,

        jolt nerves terminal blinking cursor shell, bourne again

and configuration files in the remote innards of Linux,

        irc rantings and kind opers and faqs,

to recreate the systems and bonds of pre-Internet humans and

        stand before you victorious and heroic and bursting

        with pride yet secretly fretting over the next update

        to the library that binds together his fragile code,

tech and sales scheme in Time, unknown, yet putting down in readme

        what they need to fix post ipo

and rose disillusioned in the elastic pants of freelancing in the makeshift

        home office and uploaded the suffering of crushed dreams

        into another lorum ipsum dolor sit amet consectetur

photoshop mockup that failed to “pop” enough

        and the incessant client change requests inciting their

        own souls to threaten to leave for a thousand years.

* with apologies to Allen Ginsberg’s Howl

A Long Swim in Hell

This summer, I took part in a 5 kilometer open water swim called The Swim to the Moon near the town of Hell, Michigan.

Here’s my account of why I did it, how I trained for it, and what it was like.

Who am I?

I swam competitively as a kid and in high school. Since then (I’m 43 now) I’ve swum on and off, but I haven’t been a serious swimmer at all. In 2011, I swam the Alcatraz Invitational, which is about 2 kilometers. You can read about what that swim did to me here.


My reason for doing the Swim to the Moon was the same as my reason for doing the Alcatraz swim: my sister, Beth. Beth is a very good swimmer, and, unlike me, continues to swim competitively on a regular basis. She asked me (or dared me) to swim from Alcatraz with her, and it was such a good experience that we decided to find new swims to do together — but, in warmer water than San Francisco Bay. Along with Beth’s friend, Brendan, we formed a team and called ourselves “Das Shark”.

How I trained for a 5K swim

I had about 8 months from when I signed up until the date of the swim. I started training right away. At the beginning of my training, I hadn’t seriously exercised since I trained for the Alcatraz swim (4 years ago). I was also smoking and drinking pretty heavily.

I started an intense workout regimen, I lost 30 pounds, I quit smoking, I cut way back on beer, and I was swimming between 1 and 5 kilometers a day, 5 days a week.

I didn’t do any of these things at the same time, however. By the day of the swim, I had gained back much of the weight I had lost (swimming makes me hungry), and I was drinking a lot of beer. But, I was a much stronger swimmer.

The swim turned out to be a great opportunity for a family reunion. We rented a house near the race for the week prior to the swim, and the whole family came out and cooked, swam, fished, and partied. The area around Hell has numerous small lakes, and the house where we stayed was on a particularly small one.

On the first day at the house, Beth and I jumped into the lake for a practice swim. It was warm, shallow, and still — perfect breeding grounds, it turns out, for the dreaded sea lice. I must have stirred them up and they proceeded to attack me. For the next three weeks, my legs were a bumpy and itchy mess. No one else was affected in this way, and so I think I may have just been unlucky or particularly sensitive. Note: I’m not 100% sure it was Sea Lice, so if you happen to be a Sea Lice expert, let me know and I’ll send you a picture!

What was it like?

On the day of the race, we woke up at 5:00AM and drove to the lake, where we got on a school bus that took us to the starting line. At the starting line, there were 200 swimmers and 2 porta potties. All agreed that this was an area where the race organizers could have done better.

We made up a cheer for Das Shark:

“2, 4, 6, 8! Team Das Shark will decimate! Chomp chomp chomp! You! Chomp chomp chomp! Today! Chomp chomp chomp! At 8:40 am! Chomp chomp chomp! For approximately 1 and a half to 2 hours! Chomp chomp chomp! Then we’ll have lunch! Chomp chomp chomp!”

Brendan drew a sweet logo that included a Shark wearing Lederhosen.


The course for the race started in one lake, then went through a narrow channel and into another lake. The finish line was at the opposite end of the 2nd lake. Buoys in the lakes marked the course, and special buoys marked each kilometer of the course.

The water was warm — 79 degrees — which is nice, but probably too warm for most serious swimmers. That early in the morning, there was steam coming off it, which you can see in our team picture below.


At the starting line, swimmers were started in 3 groups according to their self-reported swimming abilities. When the starting buzzer went off, there was a mad dash for position, with 50 or so swimmers in our group trying to get out ahead. The water was murky and shallow, and I kicked other swimmers and was kicked several times during the first 5 minutes.

Once everyone spread out a bit, I got into a groove.

Every long distance swimmer sings to themselves in order to stave off boredom. For most of the swim, I was singing the songs we listened to on the way to the lake that morning. I think it was this album (opens in a new window for your listening pleasure while you read the rest of the article).

But, I was also making up stories about how I would become lifelong friends with the 3 or 4 people I was swimming close to for most of the race. We’d help each other out, encourage each other to stick to our swimming, sign up for other races together, and have awesome barbecues. We were just about equal in swimming abilities and we had all been looking for other people to swim with. Maybe we’d even start a band. Note: None of those things actually happened.

The channel between the lakes was the most unpleasant part of the race. It was narrow and shallow. If I wasn’t right in the center of the channel, my hands would drag through the muck at the bottom. Everyone was trying to stay in the middle of the channel, and so collisions with other swimmers were much more likely.

There were a couple bridges that passed over the channel, and spectators stood on these and cheered us on.

After the channel came the much larger lake, Half Moon Lake. There was a dramatic temperature change (from cool to much warmer) upon exiting the channel and entering Half Moon Lake. At first, I thought the person in front of me had peed.

By the time I got to the last 2 kilometers of the race, I could feel chafing under my right arm, so I tried to favor my left arm and change my stroke in order to not make the chafing worse. Other than that, I was feeling good, but I was eager to be done. When I reached the last buoy and knew that there was only 1 kilometer to go, I pushed myself to go faster.

The lake got very shallow about 50 yards before the beach. When my hands started dragging on the bottom, I stood up and started running. I crossed the finish line totally exhausted, and then tripped and fell on my face in the sand. The announcer made a joke about me stumbling but he misread the numbers on my arm and said someone else’s name: “Joe from Kalamazoo is looking dazed and confused!”

chrisandbethchampsI finished the race in 1 hour, 34 minutes (107th overall, out of 217 swimmers) and took 5th for men in my age group (out of 10). My sister finished 2nd in her age group (32nd overall) with a time of 1 hour, 18 minutes.

A few days later, as we were driving to Chicago, Beth and I discovered Jim “The Shark” Dreyer, who has done many incredible long distance swims and holds records for such insane things as being the only person to swim across every one of the Great Lakes. His latest feats include swimming long distances while pulling heavy things (like cars).

Inspired by Jim “The Shark”, Beth and I are now starting to make plans for our next big swim.

What writing death notices taught me about writing

smallnoticeI’ve been a professional writer for 22 years. The first time my writing was published was in 1993, when I was the circulation manager for a small weekly newspaper in Detroit. The full-time reporters considered the job of writing death notices to be beneath them, and shoved it off onto me.

I loved it. Each week, the death notice forms would come in from the funeral homes, along with the remembrance ads from the spouses and loved ones of the recently, or not so recently, departed. Some notices stuck to just the facts: Mr. Volchuck died March 18 at Holy Cross Hospital. He’s survived by his daughter, Anna, and his son, Leon.

Other notices would feature bible verses. Occasionally there would be a line or two of bad poetry or some clip art selected from a binder that was kept at the front desk.

Some death notices would give a bit more information about the person than just the names of their spouses, children, and grandchildren. For example, Jan Kowalski played football for University of Detroit and worked at GM for 30 years.

My job was to put each death notice into a standard format, get the facts and spelling right, and have it all ready to go to paste up (the paper was pasted up when I first started working there) in time for the Tuesday night press run.


The structure of death notice had been the same for the entire 75+ year history of the paper: Last name, first name, middle initial, location, date of death, survived by wife (nee maiden name), children, grandchildren, location and date / time of services.

Although the policy was to stick to the standard format and keep it as dry as possible, I would routinely include as much information into each death notice as I could. A death notice is a very different thing, with a very different purpose, from an obituary. But, I treated each notice as an opportunity to try to fit an obituary into around 50 words.

The challenge of squeezing human details or touching words into whatever small amount of space was left after listing the grandchildren was one that I was particularly fond of and good at.

The readership skewed towards elderly Polish-Americans. They were notorious gossips and wanted to know everything about everyone else’s troubles, illnesses, and ultimate undoing. The paper, however, had a policy of not printing the cause of death.

I was a 22-year old on a break of indeterminate length from college. Full of unearned self-assuredness, I argued with the editor-in-chief and publisher — who had a collective 40+ years of newspaper experience between them — that the cause of death should be listed in death notices whenever it’s included on the form.

Death notices were one of the most-read parts of the paper in this community. Listing the cause of death, I argued, would make the notices even more popular. The publisher considered it tacky to mention the cause of death, and pointed out that doing so would require additional research and permissions from survivors. I eventually saw that the trouble of printing the cause of death wasn’t worth the effort, and my crusade for openness ended there.

From this first experience with being published and having my writing distributed I learned to be concise, to always be thinking about the audience, and to do quality work while balancing the effort and rewards. These are vital skills for any writer to have, and I would encourage anyone who is just getting started as a writer to spend some time practicing the art of writing death notices.