The challenge attracted more than one hundred teams from all over the world, including dozens of amateurs. Many designed their cars entirely from scratch, rejecting decades of thinking about what a car should look like.      Jason Fagone follows four of those teams from the build stage to the final race and beyond—into a world in which destiny hangs on a low drag coefficient and a lug nut can be a beautiful talisman. The result is a gripping story of crazy collaboration, absurd risks, colossal hopes, and poignant losses. In an old pole barn in central Illinois, childhood sweethearts hack together an electric-powered dreamboat, using scavenged parts, forging their own steel, and burning through their life savings.  In Virginia, an impassioned entrepreneur and his hand-picked squad of speed freaks pool their imaginations and build a car so light that you can push it across the floor with your thumb. In West Philly, a group of disaffected high school students come into their own as they create a hybrid car with the engine of a Harley motorcycle. And in Southern California, the early favorite—a start-up backed by millions in venture capital—designs a car that looks like an alien egg.      Ingenious is a joyride. Fagone takes us into the garages and the minds of the inventors, capturing the fractious yet beautiful process of engineering a bespoke machine. Suspenseful and bighearted, this is the story of ordinary people risking failure, economic ruin, and ridicule to create something vital that Detroit had never pulled off. As the Illinois team wrote in chalk on the wall of their barn, "SOMEBODY HAS TO DO SOMETHING. THAT SOMEBODY IS US."

    Increasingly, the decisions that affect our lives--where we go to school, whether we can get a job or a loan, how much we pay for health insurance--are being made not by humans, but by machines. In theory, this should lead to greater fairness: Everyone is judged according to the same rules.But as mathematician and data scientist Cathy O'Neil reveals, the mathematical models being used today are unregulated and uncontestable, even when they're wrong. Most troubling, they reinforce discrimination--propping up the lucky, punishing the downtrodden, and undermining our democracy in the process.

    Leadership isn't broken, but how it's currently being practiced certainly is. Everyone has blind spots. The purpose of Hacking Leadership is to equip leaders at every level with an actionable framework to identify blind spots and close leadership gaps. The bulk of the book is based on actionable, topical leadership and management hacks to bridge eleven gaps every business needs to cross in order to create a culture of leadership: leadership, purpose, future, mediocrity, culture, talent, knowledge, innovation, expectation, complexity, and failure. Each chapter:Gives readers specific techniques to identify, understand, and most importantly, implement individual, team and organizational leadership hacks. Addresses blind spots and leverage points most leaders and managers haven't thought about, which left unaddressed, will adversely impact growth, development, and performance. All leaders have blind-spots (gaps), which often go undetected for years or decades, and sadly, even when identified the methods for dealing with them are outdated and ineffective - they need to be hacked. Showcases case studies from the author's consulting practice, serving as a confidant with more than 150 public company CEOs. Some of those corporate clients include: AT&T, Bank of America, Deloitte, EMC, Humana, IBM, JP Morgan Chase, Merrill Lynch, PepsiCo, and other leading global brands. Hacking Leadership offers a fresh perspective that makes it easy for leaders to create a roadmap to identify, refine, develop, and achieve their leadership potential--and to create a more effective business that is financially solvent and professionally desirable.

    And this may sound weirdly obvious, but every single one of those pieces of software was written by a programmer. Programmers are thus among the most quietly influential people on the planet. As we live in a world made of software, they're the architects. The decisions they make guide our behavior. When they make something newly easy to do, we do a lot more of it. If they make it hard or impossible to do something, we do less of it.If we want to understand how today's world works, we ought to understand something about coders. Who exactly are the people that are building today's world? What makes them tick? What type of personality is drawn to writing software? And perhaps most interestingly -- what does it do to them?One of the first pieces of coding a newbie learns is the program to make the computer say "Hello, world!" Like that piece of code, Clive Thompson's book is a delightful place to begin to understand this vocation, which is both a profession and a way of life, and which essentially didn't exist little more than a generation ago, but now is considered just about the only safe bet we can make about what the future holds. Thompson takes us close to some of the great coders of our time, and unpacks the surprising history of the field, beginning with the first great coders, who were women. Ironically, if we're going to traffic in stereotypes, women are arguably "naturally" better at coding than men, but they were written out of the history, and shoved out of the seats, for reasons that are illuminating. Now programming is indeed, if not a pure brotopia, at least an awfully homogenous community, which attracts people from a very narrow band of backgrounds and personality types. As Thompson learns, the consequences of that are significant - not least being a fetish for disruption at scale that doesn't leave much time for pondering larger moral issues of collateral damage. At the same time, coding is a marvelous new art form that has improved the world in innumerable ways, and Thompson reckons deeply, as no one before him has, with what great coding in fact looks like, who creates it, and where they come from. To get as close to his subject has he can, he picks up the thread of his own long-abandoned coding practice, and tries his mightiest to up his game, with some surprising results.More and more, any serious engagement with the world demands an engagement with code and its consequences, and to understand code, we must understand coders. In that regard, Clive Thompson's Hello, World! is a marvelous and delightful master class.

    While there have been attempts to establish one standard or another as the default, there is no common agreement. So beware people telling you there is one right way, they are assuming too much. As a general rule though, netiquette involves the same principles as plain old etiquette -- basic courtesy, respect and ethics. Treat people the way you would want to be treated yourself. By following the principles outlined below, the recipient of your email will be more likely to read and act, if not be favorably impressed by your message:Subject line to summarise the message. Make the Subject line summarise the body of the e-mail. Ask yourself, 'will the recipient(s) know what this e-mail is about'. For example, Instead of Subject: Exam, say Subject: Location of 1508INT Exam, 23 July 2011.Don't assume the recipient knows the background. Include enough contextual information at the beginning of the e-mail for the recipient to know what the matter is about. If in doubt, put background information in. For example, don't say can I have an extension for my assignment?, instead say I refer to the CIT3622 assignment 1 that I handed in late. I was ill and have a doctor's certificate. May I ask for an extension on the basis that I was too ill to do it on time?Keep it concise. Keep messages brief and to the point, but not so brief that it causes the problem outlined in the previous point. This includes deleting any irrelevant text when an email has been back and forth several times. No-one wants to scroll down through pages of text in order to reach the message they want to read. If the sense of the email will be lost by deleting that text, however, leave it in.Reply within 24 hours. Try to reply within 24 hours, less if possible. In fact, get in the habit of replying immediately -- it is the polite thing to do, and the recipient will appreciate a prompt reply. It also makes you look efficient. The longer you leave it to reply, the more likely you will forget or have too big a log-jam of unanswered email.Allow time for a reply. E-mail messages are not usually required to be answered immediately, though it is good practice if you do. Before sending a reminder, allow some time for a response, some times even a few days. Not everyone is online 24 hours a day.Use the BCC field when sending bulk email. If you're sending email to a whole list of people, put their email addresses in the BCC field. That way, the privacy of the recipient is respected, and spammers cannot harvest the email addresses for their dastardly purposes.

    What time is the 3:00 parade? Why does a child need to be 40 inches tall to ride a roller coaster? What happens when the president of France gets lost inside Pirates of the Caribbean? A former employee, or "cast member", at Walt Disney World's Magic Kingdom answers these and other questions while sharing humorous stories about working inside the world's most popular theme park."Stories from a Theme Park Insider" takes you inside the park's famous tunnels and backstage for a look at how theme parks really work, and the funny moments and embarrassments that can happen when your work is someone else's vacation.

    It has emerged from a growing community of designers in various fields who work closely with social movements and community-based organizations around the world.This book explores the theory and practice of design justice, demonstrates how universalist design principles and practices erase certain groups of people—specifically, those who are intersectionally disadvantaged or multiply burdened under the matrix of domination (white supremacist heteropatriarchy, ableism, capitalism, and settler colonialism)—and invites readers to “build a better world, a world where many worlds fit; linked worlds of collective liberation and ecological sustainability.” Along the way, the book documents a multitude of real-world community-led design practices, each grounded in a particular social movement. Design Justice goes beyond recent calls for design for good, user-centered design, and employment diversity in the technology and design professions; it connects design to larger struggles for collective liberation and ecological survival.

    Froeb/McCann's MANAGERIAL ECONOMICS: A PROBLEM SOLVING APPROACH, 2E covers traditional material using a problem-based pedagogy built around common business mistakes. Models are used sparingly, and then only to the extent that they help students figure out why mistakes are made, and how to fix them. This edition's succinct, fast-paced presentation and challenging, interactive applications place students in the role of a decision maker who has to identify mistakes that reduce profits, and propose solutions to bring profits back up. The lively book provides an excellent ongoing reference for students pursuing business careers. New chapters and updates highlight mistakes that precipitated the financial crisis. With MANAGERIAL ECONOMICS, 2E your students are taught to use economics to not only identify profitable decisions, but also how to implement them within an organization.

     So many board members—especially of small nonprofits—want to support a nonprofit and readily accept the invitation to join the board. It’s only then that they discover they are in over their heads, with no idea of their expectations and responsibilities. The Little Book of Boards is here to throw that drowning board member a rope. Told with a conversational style, this book will lead you through the basics of being on a board, how meetings work, and what’s expected between meetings. In addition, at the back of the book are several in-depth resources for understanding Roberts Rules of Order, bylaws, committee structures, board leadership, and much more. Perfect for any new board member—or for an entire board that is feeling lost—this book and its common sense approach will serve you every year you are on the board.

    When it collapsed in February 2014, lawyers across Canada and the business community were stunned. What went wrong? Why did so many lawyers run for the exit? How did it implode? What is it that holds professional partnerships together?This is the story of the rise and fall of a great company by the ultimate insider, Norman Bacal, who served as managing partner until a year before the firm's demise. Breakdown takes readers into the boardroom offices during the heady growth of a legal empire built from the ground up over 40 years. We see how after a change of leadership tensions erupted between the Toronto and Montreal offices, and between the hard-driving lawyers themselves. It is a story about the extraordinary fragility of the legal partnership, but it's also a classic business story, a cautionary tale of the perils of ignoring a firm's culture and vision.Normal0falsefalsefalseEN-USJAX-NONE<!--StartFragment--><!--EndFragment--><!--EndFragment-->

    In Blood, Sweat, and Pixels, Jason Schreier takes readers on a fascinating odyssey behind the scenes of video game development, where the creator may be a team of 600 overworked underdogs or a solitary geek genius. Exploring the artistic challenges, technical impossibilities, marketplace demands, and Donkey Kong-sized monkey wrenches thrown into the works by corporate, Blood, Sweat, and Pixels reveals how bringing any game to completion is more than Sisyphean—it's nothing short of miraculous.Taking some of the most popular, bestselling recent games, Schreier immerses readers in the hellfire of the development process, whether it's RPG studio Bioware's challenge to beat an impossible schedule and overcome countless technical nightmares to build Dragon Age: Inquisition; indie developer Eric Barone's single-handed efforts to grow country-life RPG Stardew Valley from one man's vision into a multi-million-dollar franchise; or Bungie spinning out from their corporate overlords at Microsoft to create Destiny, a brand new universe that they hoped would become as iconic as Star Wars and Lord of the Rings—even as it nearly ripped their studio apart. Documenting the round-the-clock crunches, buggy-eyed burnout, and last-minute saves, Blood, Sweat, and Pixels is a journey through development hell—and ultimately a tribute to the dedicated diehards and unsung heroes who scale mountains of obstacles in their quests to create the best games imaginable.

    You understand the basics of investing and diversifying your portfolio. Now it's time to invest like a pro for greater profits--with investment expert David Stein, host of the popular weekly podcast, "Money for the Rest of Us." He's created a unique ten-question template that makes it easy for individual investors like you to:- Invest more confidently- Feel less overwhelmed- Build a stronger portfolio- Avoid costly mistakes- Plan and save for retirementDespite what many people believe, you don't need to be an expert to be a successful investor. With Stein as your personal money mentor, you'll learn how to make smarter, more informed decisions that can help reduce your risk and increase your gains by following a few simple rules for analyzing any investment. This is how the professionals grow their wealth and how you can, too. This is Money for the Rest of Us.

    

    More and more often, those companies look to technology consultants to fulfill their needs. There are real advantages to being a consultant. You make contacts with a lot of different people; you get exposure to many industries; and most important, unlike a software developer in the IT department for a brick-and-mortar company, as a technology consultant, you are the profit center…so long as you are billing. Consulting can be hugely rewarding—but it’s easy to fail if you are unprepared. To succeed, you need a mentor who knows the lay of the land. Aaron Erickson is your mentor, and this is your guidebook. Erickson has done it all—from Practice Leadership to the lowest level project work. In The Nomadic Developer, he brings together his hardwon insights on becoming successful and achieving success through tough times and relentless change. You’ll find 100% practical advice and real experiences—his own and annotations from those in the trenches. In addition, renowned consultants—such as David Chappell, Bruce Eckel, Deborah Kurata, and Ted Neward—share some of their hard-earned lessons. With this useful guidebook, you can Objectively assess whether the consultant’s life makes sense for you Break into thebusiness and build a career path that works Avoid the Seven Deadly Firms by identifying unscrupulous technology consultancies and avoiding their traps and pitfalls Understand the business models and mechanics that virtually all consulting firms use Master secret consulting success tips that are typically left unstated or overlooked Gain a competitive advantage by adding more value than your competitors Continue your professional development so you stay billable even during bad times Profit from both fixed-bid and time-and-materials projects Build a personal brand that improves your resiliency no matter what happens

    After his death, the contents of his studio, including thousands of glass negatives, were sold off for five dollars. For years the fragile negatives sat forgotten and deteriorating in cardboard boxes in an open carport. How did it happen, then, that the most implausible of events took place? That Disfarmer’s haunting portraits were retrieved from oblivion, that today they sell for upwards of $12,000 each at posh New York art galleries; his photographs proclaimed works of art by prestigious critics and journals and exhibited around the world? The story of Disfarmer’s rise to fame is a colorful, improbable, and ultimately fascinating one that involves an unlikely assortment of individuals. Would any of this have happened if a young New York photographer hadn't been so in love with a pretty model that he was willing to give up his career for her; if a preacher’s son from Arkansas hadn't spent 30 years in the Army Corps of Engineers mapping the U.S. from an airplane; if a magazine editor hadn't felt a strange and powerful connection to the work? The cast of characters includes these, plus a restless and wealthy young Chicago aristocrat and even a grandson of FDR. It’s a compelling story which reveals how these diverse people were part of a chain of events whose far-reaching consequences none of them could have foreseen, least of all the strange and reclusive genius of Heber Springs. Until now, the whole story has not been told.