Guess which book, as yet unreleased, is pre-selling at #1 in Amazon’s “Corruption & Misconduct in Politics” category?
P.S., I possibly may earn a few helpful cents as an Amazon affiliate bookseller if you follow this link to the book. But only if you actually buy it or something else. Otherwise, bupkis. No soup for me. Thanks for considering.
I confess. I haven’t read all of John Bolton’s book, The Room Where It Happened. And I likely won’t read all of it, to be honest. I’d rather page through John Milton before I’ve had my morning caffeine than wade through John Bolton.
However, until just a few minutes ago as I write this, I was sloshing around in The Room Where It Happened and stopping to read occasional paragraphs. I also was looking at news headlines saying the Trump Administration wants to block the book’s publication on grounds it contains classified information.
Then, suddenly, my screen went dark and a message popped up:
We’re sorry. You can’t access this item because it is in violation of our Terms of Service.
Likely, many others saw that message at about the same.
Until then, I had been thinking: if I see anything in this book that appears to be classified, I will close my eyes tightly and quickly page forward. Scout’s honor. Of course, I also was wondering if the Top Secret clearance I held while in the Vietnam War is still valid, just in case I accidentally glanced at something Trump’s lawyers didn’t want me to see?
To mis-summarize the ruling of Judge Royce C. Lamberth of the Federal District Court of Columbia regarding the publication of this work, Bolton’s book–the “horse” (or “horse manure,” depending on your political persuasion)–already is out of the proverbial barn. Indeed, it was available just about anywhere on the planet for a while if you had the right web links or other book review connections. And it’s scheduled to be released June 23, 2020, according to Amazon. It was difficult to see how or why the Trump Administration was still expecting the bolted horse to be rounded up and led back to its barn.
I magically had received access to an ebook copy of The Room Where It Happened. I honestly cannot tell you from whom I got it, because I don’t know. Things like this occasionally happen when people review books online or in print. For books to sell, they must be publicized. Names make news, the old saying goes. And news headlines can help a book hit best-sellers lists even before it’s released. I had requested a review copy from Simon & Schuster and got zero response. Then, suddenly, a stray horse fleeing its barn bolted past and dropped something where I could find it (without stepping in it).
I did get to read quite a few pages before the link went dark. Bolton, in the book, says he held some strong sympathies and hopes for Donald Trump’s now-bedraggled presidency in its early days. But an “axis of adults” surged into the Oval Office and surrounded Trump right after the inauguration. They mostly impeded him and did what they could to help themselves, rather than help shape and promote his political agenda.
“They didn’t do nearly enough,” Bolton charges, “to establish order, and what they did do was so transparently self-serving and so publicly dismissive of many of Trump’s very clear goals (whether worthy or unworthy) that they fed Trump’s already-suspicious mind-set, making it harder for those who came later to have legitimate policy exchanges
with the President.”
Of course, Trump himself receives plenty of criticism, too, in the book. Ambassador Bolton says that when he joined the Trump Administration, he had long believed “that the role of the National Security Advisor was to ensure that a President understood what options were open to him for any given decision he needed to make, and then to ensure that this decision was carried out by the pertinent bureaucracies. The National Security Council process was certain to be different for different Presidents, but these were the critical objectives the process should achieve.”
But the “axis of adults” (not all specifically named in the portions I read) kept getting in the way. And Trump’s own personality kept tripping him up, as well, Bolton states.
“Because…the axis of adults had served Trump so poorly, he second-guessed people’s motives, saw conspiracies behind rocks, and remained stunningly uninformed on how to run the White House, let alone the huge federal government,” he writes. “The axis of adults is not entirely responsible for this mind-set. Trump is Trump. I came to understand that he believed he could run the Executive Branch and establish national-security policies on instinct, relying on personal relationships with foreign leaders, and with made-for-television showmanship always top of mind.”
Many on social media previously objected to the publication of this book and vowed to not help Bolton profit from it. But many also are now referring to it and quoting from it as they express their outrage toward the Trump White House. After watching the Trump impeachment hearings gavel to gavel and wishing John Bolton had been a brave patriot who showed up voluntarily to testify, I have understood the misgivings. Nonetheless, historians, presidential scholars, Trump biographers (there will be Trump biographers), screenwriters, numerous pundits, and others will have a field day digging through this book and harvesting eye-opening nuggets of ineptitude, opportunism, favoritism, and more.
As a book reviewer, I have to give The Room Where It Happened some credit for being useful to readers in those categories. I also can see it serving as one of the textbooks in a graduate-level course on how not to run an American presidency.
Bottom line, we’ve known things definitely have been bad inside the White House between January 2017 and now. Bolton’s White House memoir shows how some things actually have been worse than many of us imagined. Even a cursory look, a quick bolt through Bolton’s book, is enough to make anyone who cares for two-party democracy in America, and the rule of law, wince and wish tomorrow was Election Day.
Now more than ever, with some 40 million Americans unemployed, the nation’s economy stalled by protests and a deadly pandemic, and federal leadership failing, we need to review and draw again from hard lessons learned during major events in our nation’s labor history.
Mike Stout’s well-written new memoir, Homestead Steel Mill: The Final Ten Years, should be a must-read for labor leaders, labor activists, labor academics, labor lawyers, and labor specialists at all levels of local, state, and federal government. It deserves attention as well from libraries and general readers interested in American labor history, how unions operate, and what roles unions will play in the nation’s difficult economic recovery.
The author has walked the walk of a Pittsburgh area blue-collar steelworker and union leader. Stout’s credits are too numerous to summarize here, but include writing for and editing an influential union newspaper, helping found one of the first and largest union food banks, and organizing several community coalitions aimed at trying to help save steel mill jobs. He also is known internationally as a labor and social activist, as well as singer-songwriter.
The Homestead steelworks already had earned a prominent and disturbing place in American labor history when Mike Stout began working there for U.S. Steel in 1978 as a utility crane operator. Indeed, as one of his well-researched book’s sources, Brett Reigh, has noted in a master’s thesis: “In its 106 years of operation, the Homestead Works [had] witnessed some of the greatest battles ever waged between labor and capital in the United States.”
In 1892, for example, disputes between the Amalgamated Association of Iron and Steel Workers and the Carnegie Steel Company exploded into a lockout and then the infamous “Homestead Massacre” that claimed at numerous lives. In an attempt to break the union, Carnegie’s leaders had brought in some 300 Pinkerton guards to try to overwhelm the strikers. A violent battle ensued, and some strikers and Pinkerton guards died. The Pinkertons eventually surrendered, but the strike ended after 6,000 troops from Pennsylvania’s state militia arrived, sided with the mill’s management, and stood guard while strikebreakers were brought in to replace union workers.
Working at Homestead
Mike Stout was one of some 7,000 employees at Homestead and believed he had found a job for life in one of America’s most essential industries. His area also had several other U.S. Steel mills and a total of about 30,000 steelworkers.
In a chapter titled “Homestead–Forge of the Universe, Heart of Industrial Unionism,” Stout recounts some of the Homestead mill’s historical significance:
“Homestead, Pennsylvania, has been synonymous with steelmaking since 1880. For over one hundred years, the Homestead mill, seven miles southeast of downtown Pittsburgh on the south side of the Monongahela River, made the steel that helped shape the Industrial Revolution in America, producing armor plate during America’s involvement in both world wars, as well as the Korean and Vietnam Wars. It made structural beams for skyscrapers, including the St. Louis Arch, the Home Life Insurance Building in Chicago, the Pan Am, Empire State, Rockefeller Center, and United Nations Buildings in New York City, and the shafting for the power plant at the Hoover Dam. It made the steel for every major bridge and waterway back in the day, from the Panama Canal through the Golden Gate and Oakland Bay Bridges in San Francisco out west to the George Washington and Verrazano-Narrows Bridges back east.”
During Stout’s times at Homestead, however, steel mill owners were refusing to modernize and increasingly sending jobs and steel investments to cheaper sites overseas. Many workers, including Stout, were laid off repeatedly and not all were called back to work. As Homestead’s workforce shrank, union leaders and union members continued battling to maintain jobs and benefits and to keep employees as safe as possible in dangerous working conditions.
How dangerous? According to Stout:
“Working in a steel mill was dangerous beyond description. You worked in extreme temperatures. Heavy equipment and machinery were flying all about you. You could be working in front of rolling red hot steel where the temperature in the front of your body was 2,300 degrees, but your back would be freezing. You worked a different time shift every week, working 8:00 a.m. to 4:00 p.m., then 4:00 p.m. to midnight the following week, then midnight to 8:00 a.m. the third week. Also, every week your two days off would change; you’d be off Sunday and Monday, then the next week Monday and Tuesday, etc. Your entire life outside of work was determined by your life in the mill. There wasn’t much time or energy for anything else.”
Union members and leaders also fought among themselves over what was the right balance of “union democracy,” how trade unions are governed–an important focus in Stout’s new book. A key concern of the rank and file (the union members) was that union executives would accurately represent the members’ interests when dealing with, and negotiating with, mills’ executives. Much of Stout’s memoir is devoted to his time navigating and leading some of the inner workings of union activities, politics, and activism. Many readers who have no experience with unions may find these chapters both eye-opening and surprisingly engrossing.
After the plant was shut down in 1987, a shopping mall was built on its site. In a review of Stout’s book, written by a former steelworker at a nearby mill, Mark Fallon recalls: “The union at the Homestead mill, United Steelworkers (USW) Local 1397 and its Rank and File Caucus, was an ‘insurgent’ local that often took vigorous issue with the policies not only of U.S. Steel, but those of its parent United Steelworkers of America International union.”
Fallon adds that while Stout served as the union’s “Grievance Chair for the entire mill between 1981-1987,” he won a significant victory for more than 3,000 former workers: more than $12 million in back pay, severance pay, pensions, and unemployment benefits. “He was the last union official out the door when the mill closed and stayed on for another four years fighting for workers’ pay and rights without receiving a dime from the union.”
After Homestead, What Lies Ahead?
The future of work in America is frighteningly uncertain as this review is being written. In the ongoing pandemic, millions have lost their jobs, businesses, and even careers, while millions of others are now working from home with no certainty that they will have workplaces, positions, or employers to return to in the future.
As Charles McCollester emphasizes in the foreword to Stout’s book: “The coming generation of workers faces a radically changing world of artificial intelligence, robots, drones, pervasive surveillance, genetic engineering, insidious pollution, and accelerating climate change. Mike’s account of a grassroots democratic labor insurgency fighting for economic survival remains relevant, even as the nature of work changes.” (McCollester is former chief steward, UE Local 610, Switch and Signal plant and former professor of Labor Relations at Indiana University of Pennsylvania.)
Stout hopes to see a future where disparate groups unite and create a larger and more powerful social and political force. He urges: “There is commonality in all movements out there—be it Black Lives Matter, the #MeToo women’s movement, health care, immigration rights, worker rights, the environmental movement, or the movements against the many unjust wars our government is waging. Everyone needs a decent job, reasonable benefits, a democratic voice, a healthy environment, equal treatment, dignity, and a peaceful life. Until organized labor joins in a sustained coalition with these movements as one voice, as well as with our elected representatives, we will remain isolated, picked off one by one.”
How to Get the Book
To purchase the book, contact: PM Press, Oakland, CA. www.pmpress.org $24.95 (paperback), $60 (hard cover), $8.95 (ebook) + shipping & handling. For a signed, First Edition copy at a discount price, contact the author at: email@example.com $25 (soft cover) including shipping and handling $40 (hard cover) including shipping and handling.
“The Book Artist,” the eighth book in Mark Pryor’s Hugo Marston mystery series, is entertaining, absorbing–and paced a bit slower than some detective/police procedurals. That’s because it offers readers a nice mixture of Paris atmosphere and American diplomats and others living, working and partying in Paris.
The novel’s law-enforcement angles also require some slower pacing. The main character, Hugo Marston, chief of the security for the U.S. Embassy in Paris, must work within a narrow legal framework (that he sometimes oversteps) while interacting with Paris police and other French agencies.
In “The Book Artist,” a sculptor is murdered, and French police arrest an American suspect who has close connections to Hugo. He is convinced she isn’t the killer. But her DNA has been found on the victim’s body, and the Paris police say they have other evidence that can bring a murder conviction.
Marston must unmask the real killer before his American friend disappears into the French legal system’s labyrinth.
In this fifth novel in Susan Spann’s Hiro Hattori series, danger starts on page one and doesn’t let up until almost the very end.
Set in 16th-century Japan, the series focuses on Hiro Hattori, a master ninja from the Iga province who once refused a commander’s orders and is now serving what is supposed to be a long, humiliating punishment. Hiro is tasked with protecting a Portuguese Jesuit priest named Father Mateo, who, at first, speaks insufficient Japanese and doesn’t understand how easily he could be hurt or killed for inadvertently blundering over an important local custom or taboo.
During the four previous books of the series, Hiro grudgingly has been helping Father Mateo get a better grip on feudal Japan, its rulers, its warlords and its strict and unforgiving social order. Along the way, the ninja and the priest also have been thrust into situations where they have had to work together to solve some murders.
In Betrayal at Iga, Father Mateo now is more knowledgeable and comfortable with being in Japan, speaking its language and reaching a few Christian converts. And Hiro has recognized that the foreign priest is an honorable man in his own way. Hiro now admits that he and Father Mateo have become friends. But it is a time of trouble, so he and the Portuguese Jesuit have had to take refuge among Hiro’s clan. And, in their “safety,” they soon discover they are sheltering in a village where many people are trained assassins.
Indeed, when an ambassador from a neighboring clan appears and tries to negotiate a peace agreement with Iga, he is poisoned during a welcoming dinner and dies right in front of Hiro and Father Mateo.
If the killer is not found soon, war may break out between the ninjas of each clan. Or Hiro and Father Mateo themselves may be killed. No pressure at all on the two investigators!
The author, Susan Spann, has a degree in Asian history and has maintained a lifelong fascination with Japanese history and culture. She has an excellent eye for detail and creates believable settings and scenes without bogging down her smooth writing. She also has her characters speak with straightforward, accessible dialogue.
Betrayal at Iga is fine escapism: a 16th-century ninja detective procedural. The story also offers subtle and absorbing lessons in Japanese history, geography, customs, warfare, love, honor and friendship.
It’s five-star reading and definitely recommended if you are looking for something well beyond an ordinary detective thriller.
Considerable planning, effort and care have gone into writing Go in Practice, a new Golang programming book from Manning and also available from Amazon.
The book’s structure and approach are both geared toward helping Go newbies move beyond the basics. The writing is clear, and the code examples are focused and not overly long.
Go in Practice opens with a concise refresher on the history, advantages and key features of Go. From there, the 11-chapter book moves into areas that include:
An interface for your applications
Taking your applications to the cloud
In each of these major sections, the authors present some 70 useful and practical techniques, such as:
Avoiding CLI boilerplate code
Using multiple channels
Incrementally saving a file
Custom HTTP error passing
Using protocol buffers
These and the other practical techniques are presented in Problem, Solution and Discussion format. And code examples illustrate (and allow you to try out) what is supposed to happen.
If you are still learning the Golang basics, make this one your next book. Stick with Go in Action or some other starter book, for now. But if you know the basics and are now eager to get more serious about learning and applying this versatile programming language, definitely check out Go in Practice.
If you already are using Go as a development language, it can’t hurt you to take a look at this how-to guide, as well. You may pick up some new and useful techniques.
The two authors, by the way, have been described as”key contributors in the Go ecosystem for years.”
The three authors of this book note that “[d]ata science is a very wide field, so wide indeed that a book ten times the size of this one wouldn’t be able to cover it all. For each chapter, we picked a different aspect we find interesting. Some hard decisions had to be made to keep this book from collapsing your bookshelf!”
In their decisions and selections, they have made some good choices. Introducing Data Science is well written and generally well-organized (unless you are overly impatient to get to hands-on tasks).
The book appears to be aimed primarily at individual computer users and persons contemplating possible careers in data science–not those already working in, or heading, big data centers. The book also could be good for managers and others trying to wrap their heads around some data science techniques that could help them cope with swelling mountains of business data.
With this book in hand, you may be impatient to open it to the first chapter and dive headfirst into slicing, dicing, and graphing data. Try to curb your enthusiasm for a little while. Books from Manning generally avoid the “jump in now, swim later” approach. Instead, you get some overviews, explanations and theory first. Then you start getting to the heart of the matter. Some like this approach, while others get impatient with it.
In Introducing Data Science, your “First steps in big data” start happening in chapter five, after you’ve first delved into the data science process: 1. Setting the research goal; 2. Retrieving data; 3. Data preparation, 4. Data exploration; 5. Data modeling; and 6. Presentation and automation.
The “First steps” chapter also is preceded by chapters on machine learning and how to handle large data files on a single computer.
Once you get to Chapter 5, however, your “First steps” start moving pretty quickly. You are shown how to work (at the sandbox level) with two big data applications, Hadoop and Spark. And you get examples of how even Python can be used to write big data jobs.
From there, you march on to (1) the use of NoSQL databases and graph databases, (2) text mining and text analytics, and (3) data visualization and creating a small data science application.
It should be noted and emphasized, however, that the concluding pages of chapter 1 do present “An introductory working example of Hadoop.” The authors explain how to run “a small [Hadoop] application in a big data context,” using a Hortonworks Sandbox image inside a VirtualBox.
It’s not grand, but it is a start in a book that otherwise would take four chapters to get to the first hands-on part.
Near the beginning of their book, the authors also include a worthy quote from Morpheus in “The Matrix”: “I can only show you the door. You’re the one that has to walk through it.”
This book can be a good entry door to the huge and rapidly changing field of data science, if you are willing to go through it and do the work it presents.
Spear of Light is the second book in The Glittering Edge duology. And it has been my introduction to Brenda Cooper’s science-fiction writing.
For the most part, I am impressed. While I missed Edge of Dark, the duology’s first book, I am pleased at how smoothly I was drawn into Spear of Light, a complex but engrossing tale of humans, post-humans, and robots on the “re-wilded” planet, Nym. This second book in the duology stands nicely on its own.
The general flow of the novel is summarized on other sites, such as Amazon and Pyr, so I won’t rehash it here. But a lone ranger, Charlie Windar, wants desperately to save his rebuilt planet and is caught in the middle of an approaching war between the post-humans (the Next) and the Shining Revolution, a group of humans who want to attack the Next, no matter if it means Nym will be wrecked (again) in the process.
Meanwhile, the Next, who previously were banished from Nym’s solar system and later returned in force, are now quickly building a massive new city on Nym. And the humans caught between the Next and the Shining Revolution cannot figure out why the Next seem driven, this time, to uncover something mysterious within Nym’s ancient history.
Writers often are advised to “Write what you know.” Author Robin Yocum clearly has heeded that advice. This is a well-written mystery that also is a coming-of-age story, plus a fine portrait of simpler times in the American heartland during the mid-1960s.
A Brilliant Death is set in a real-life but now unincorporated village, Brilliant, Ohio. Brilliant is a settlement on the Ohio River near the West Virginia border, in an area where steel mills, coal mines and a glass factory once held sway and Polish and other immigrant names are common.
Yocum’s novel focuses on two teenage friends, Mitch Malone and Travis Baron, as they near adulthood in Brilliant and start trying to uncover the truth behind the death of Travis Baron’s mother when he was still an infant. Along the way, the two youths, both promising athletes, continue growing up, getting into typical teenage scrapes, and nearing the time when they will go off to college or off to the Vietnam War.
They do manage to discover the terrible truth behind Travis’s mother’s death. And what they learn puts both of their lives immediately into danger. Now they must make difficult choices from options they hoped they would never have to consider.
If you have worked with the decade-old Spring framework, you know well that it has a long history of providing configuration headaches for developers. The new Spring Boot framework, on the other hand, literally brings much-needed simplification and automation to the process of using Spring. And it can put some refreshing fun back into application development.
“Spring Boot,” Craig Walls states in his new book, “is an exciting new way to develop Spring applications with minimal friction from the framework itself. Auto-configuration eliminates much of the boilerplate configuration that infests traditional Spring applications. Spring Boot starters enable you to specify build dependencies by what they offer rather than use explicit library names and version. The Spring Boot CLI takes Spring Boot’s frictionless development model to a whole new level by enabling quick and easy development with Groovy from the command line. And the [Spring Boot] Actuator lets you look inside your running application to see what and how Spring Boot has done.”
You do not need a lot of Spring experience to benefit from this book. You do need some Java background, and it is helpful to have used Groovy, Gradle and Maven a few times. But the book’s text is written smoothly, and it is well illustrated, with numerous code examples and a few screen shoots. So Java developers who are fairly new likely can use it and pick up new skills.
While going through the book, you develop a reading-list application using Spring Initializr, Spring Boot, Spring Tool Suite, and other tools. In the project, you “use Spring MVC to handle web requests, Thymeleaf to define web views, and Spring Data JPA to persist the reading selections to a database,” Craig Walls explains. Initially, at least, “an embedded H2 database” is employed during development.
Walls’s book is divided into eight chapters:
1. Bootstarting Spring 2. Developing your first Spring Boot Application 3. Customizing configuration 4. Testing with Spring Boot 5. Getting Groovy with the Spring Boot CLI 6. Applying Grails in Spring Boot 7. Taking a peek inside the Actuator 8. Deploying Spring Boot applications
Four appendices also are presented: Spring Boot developer tools, Spring Boot starters, Configuration properties, and Spring Boot dependencies.
Bottom line: with Spring Boot providing much of the heavy lifting, you likely will gain better feelings about the venerable Spring framework. You may even wind up with a healthy new respect for it. And Spring Boot certainly should add more years to Spring’s usefulness and viability in the marketplace.