'Programming The World Wide Web', written by bestselling author, Robert Sebesta, provides a comprehensive introduction to the programming tools and skills required for building and maintaining server sites on the Web.

    There she saw first-hand how deeply intertwined Silicon Valley was with the federal government, and always had been, and how shallow the common understanding of the secrets of the Valley's success actually was. Now, after almost five years of pioneering research, O'Mara has produced the definitive history of Silicon Valley for our time, the story of mavericks and visionaries, but also of powerful institutions creating the framework for innovation, from the Pentagon to Stanford University. It is also a story of a community that started off remarkably homogeneous and elitist and stayed that way, and whose belief in its own mythology has deepened into a collective hubris that has led to astonishing triumphs as well as devastating second-order effects.Deploying a wonderfully rich and diverse cast of protagonists, from the justly famous to the unjustly obscure, across four generations of explosive growth in the Valley, from the Forties to the present, O'Mara has wrestled into magnificent narrative form one of the most fateful developments in modern American history. She is on the ground with all of the key tech companies, and chronicles the evolution in their offerings through each successive era, and she has a profound fingertip feel for the politics of the sector, and its relation to the larger cultural narrative about tech as it has evolved over the years. Perhaps most impressively, O'Mara has penetrated the inner kingdom of tech venture capital firms, the insular and still remarkably old-boy world that became the cockpit of American capitalism and the crucible for bringing technological innovation to market, or not. The transformation of big tech into the engine room of the American economy and the nexus of so many of our hopes and dreams--and increasingly nightmares--can be understood, in Margaret O'Mara's masterful hands, as the story of one California valley. As her majestic history makes clear, its fate is the fate of us all.

    Busted as a teenager for hacking into Pac Bell phone networks, Kevin Poulsen would find his punishment was a job with a Silicon Valley defense contractor. By day he seemed to have gone straight, toiling on systems for computer-aided war. But by night he burglarized telephone switching offices, adopting the personae and aliases of his favorite comic-book anti heroes - the Watchmen. When authorities found a locker crammed with swiped telecommunications equipment, Poulsen became a fugitive from the FBI, living the life of a cyberpunk in a neon Hollywood underground. Soon he made the front pages of the New York Times and became the first hacker charged with espionage. Littman takes us behind the headlines and into the world of Poulsen and his rogues' gallery of cyberthieves. Drawing on hundreds of hours of interviews with Poulsen, his confederates, and the authorities, he spins a thrilling chase story on the electronic frontier. The nation's phone network was Poulsen's playground. On Los Angeles's lucrative radio giveaways, Poulsen worked his magic, winning Porsches and tens of thousands of dollars. He secretly switched on the numbers of defunct Yellow Pages escort ads and took his cut of the profits. And he could wiretap or electronically stalk whomever he pleased, his childhood love or movie stars. The FBI seemed no match for Poulsen. But as Unsolved Mysteries prepared a broadcast on the hacker's crimes, LAPD vice stumbled onto his trail, and an undercover operation began on Sunset Strip.

    Tracing the rise, fall, and alarming resurrection of the digital mafia behind the two largest spam pharmacies and countless viruses, phishing, and spyware attacks he delivers the first definitive narrative of the global spam problem and its threat to consumers everywhere.Blending cutting-edge research, investigative reporting, and firsthand interviews, this terrifying true story reveals how we unwittingly invite these digital thieves into our lives every day. From unassuming computer programmers right next door to digital mobsters like "Cosma" who unleashed a massive malware attack that has stolen thousands of Americans' logins and passwords, Krebs uncovers the shocking lengths to which these people will go to profit from our data and our wallets.Not only are hundreds of thousands of Americans exposing themselves to fraud and dangerously toxic products from rogue online pharmacies, but even those who never open junk messages are at risk. As Krebs notes, spammers can—and do—hack into accounts through these emails, harvest personal information like usernames and passwords, and sell them on the digital black market. The fallout from this global epidemic doesn't just cost consumers and companies billions, it costs lives too.Fast-paced and utterly gripping, Spam Nation ultimately proposes concrete solutions for protecting ourselves online and stemming this tidal wave of cybercrime, before it's too late."Krebs's talent for exposing the weaknesses in online security has earned him respect in the IT business and loathing among cybercriminals. His track record of scoops has helped him become the rare blogger who supports himself on the strength of his reputation for hard-nosed reporting." Bloomberg Businessweek

    You'll get quick, easy-to-follow advice on modern practices: which to use, and when they should be applied. This book avoids current fashion trends and marketing hype; instead, readers find page after page of solid advice, all tried and tested in the real world.Aimed at beginning to intermediate programmers, Ship It! will show you:Which tools help, and which don't How to keep a project moving Approaches to scheduling that work How to build developers as well as product What's normal on a project, and what's not How to manage managers, end-users and sponsors Danger signs and how to fix them Few of the ideas presented here are controversial or extreme; most experienced programmers will agree that this stuff works. Yet 50 to 70 percent of all project teams in the U.S. aren't able to use even these simple, well-accepted practices effectively. This book will help you get started.Ship It! begins by introducing the common technical infrastructure that every project needs to get the job done. Readers can choose from a variety of recommended technologies according to their skills and budgets. The next sections outline the necessary steps to get software out the door reliably, using well-accepted, easy-to-adopt, best-of-breed practices that really work.Finally, and most importantly, Ship It! presents common problems that teams face, then offers real-world advice on how to solve them.

    In the 1960s most computers filled an entire room, but the spacecraft's computer was required to be compact and low power. Although people today find it difficult to accept that it was possible to control a spacecraft using such a 'primitive' computer, it nevertheless had capabilities that are advanced even by today's standards.This is the first book to fully describe the Apollo guidance computer's architecture, instruction format and programs used by the astronauts. As a comprehensive account, it will span the disciplines of computer science, electrical and aerospace engineering. However, it will also be accessible to the 'space enthusiast'. In short, the intention is for this to be the definitive account of the Apollo guidance computer.Frank O'Brien's interest in the Apollo program began as a serious amateur historian. About 12 years ago, he began performing research and writing essays for the Apollo Lunar Surface Journal, and the Apollo Flight Journal. Much of this work centered on his primary interests, the Apollo Guidance Computer (AGC) and the Lunar Module. These Journals are generally considered the canonical online reference on the flights to the Moon. He was then asked to assist the curatorial staff in the creation of the Cradle of Aviation Museum, on Long Island, New York, where he helped prepare the Lunar Module simulator, a LM procedure trainer and an Apollo space suit for display. He regularly lectures on the Apollo computer and related topics to diverse groups, from NASA's computer engineering conferences, the IEEE/ACM, computer festivals and university student groups.

    Written for both experienced and new programmers alike, Learning Ruby is a just-get-in-and-drive book -- a hands-on tutorial that offers lots of Ruby programs and lets you know how and why they work, just enough to get you rolling down the road. Interest in Ruby stems from the popularity of Rails, the web development framework that's attracting new devotees and refugees from Java and PHP. But there are plenty of other uses for this versatile language. The best way to learn is to just try the code! You'll find examples on nearly every page of this book that you can imitate and hack. Briefly, this book:Outlines many of the most important features of Ruby Demonstrates how to use conditionals, and how to manipulate strings in Ruby. Includes a section on regular expressions Describes how to use operators, basic math, functions from the Math module, rational numbers, etc. Talks you through Ruby arrays, and demonstrates hashes in detail Explains how to process files with Ruby Discusses Ruby classes and modules (mixins) in detail, including a brief introduction to object-oriented programming (OOP) Introduces processing XML, the Tk toolkit, RubyGems, reflection, RDoc, embedded Ruby, metaprogramming, exception handling, and other topics Acquaints you with some of the essentials of Rails, and includes a short Rails tutorial. Each chapter concludes with a set of review questions, and appendices provide you with a glossary of terms related to Ruby programming, plus reference material from the book in one convenient location. If you want to take Ruby out for a drive, Learning Ruby holds the keys.

    You will be able to look over the shoulder of major coding and design experts to see problems through their eyes.This is not simply another design patterns book, or another software engineering treatise on the right and wrong way to do things. The authors think aloud as they work through their project's architecture, the tradeoffs made in its construction, and when it was important to break rules. Beautiful Code is an opportunity for master coders to tell their story. All author royalties will be donated to Amnesty International.

    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.

    As John invested in these skills his career took off, and he became a highly paid, highly sought-after developer and consultant. Today John helps more than 1.4 million programmers every year to increase their income by developing this unique blend of skills. "If you're a developer, green or a veteran, you owe it to yourself to read The Complete Software Developers Career Guide." - Jason Down, Platform Developer, Ontario, Canada What You Will Learn in This Book How to systematically find and fill the gaps in your technical knowledge so you can face any new challenge with confidence Should you take contract work - or hold out for a salaried position? Which will earn you more, what the tradeoffs are, and how your personality should sway your choice Should you learn JavaScript, C#, Python, C++? How to decide which programming language you should master first Ever notice how every job ever posted requires "3-5 years of experience," which you don't have? Simple solution for this frustrating chicken-and-egg problem that allows you to build legitimate job experience while you learn to code Is earning a computer science degree a necessity - or a total waste of time? How to get a college degree with maximum credibility and minimum debt Coding bootcampssome are great, some are complete scams. How to tell the difference so you don't find yourself cheated out of $10,000 Interviewer tells you, "Dress code is casual around here - the development team wears flipflops." What should you wear? How do you deal with a boss who's a micromanager. Plus how helping your manager with his goals can make you the MVP of your team The technical skills that every professional developer must have - but no one teaches you (most developers are missing some critical pieces, they don't teach this stuff in college, you're expected to just "know" this) An inside look at the recruiting industry. What that "friendly" recruiter really wants from you, how they get paid, and how to avoid getting pigeonholed into a job you'll hate Who Should Read This Book Entry-Level Developers This book will show you how to ensure you have the technical skills your future boss is looking for, create a resume that leaps off a hiring manager's desk, and escape the "no work experience" trap. Mid-Career Developers You'll see how to find and fill in gaps in your technical knowledge, position yourself as the one team member your boss can't live without, and turn those dreaded annual reviews into chance to make an iron-clad case for your salary bump. Senior Developers This book will show you how to become a specialist who can command above-market wages, how building a name for yourself can make opportunities come to you, and how to decide whether consulting or entrepreneurship are paths you should pursue.

    His assignment is to program the complex lunar landing phase in the Lunar Module's onboard computer. As he masters his art the reader learns about the computer, the mission, and a bit about spacecraft navigation and meets a cast of interesting characters along the way. As Apollo 11 approaches, the author flies lunar landings in simulators and meets the astronauts who will fly the LM for real. He explains the computer alarms that almost prevented Neil Armstrong from landing and describes a narrow escape from another dangerous problem. He helps Pete Conrad achieve a pinpoint landing on Apollo 12, and works with Apollo 16 commander John Young on a technique for landing even more precisely. On Apollo 14 he devises a workaround when a faulty pushbutton threatens Alan Shepard's mission, earning a NASA award, a story in Rolling Stone, and a few lines in the history books. Along the way the author hits the high points of his eclectic personal life, as he enters adulthood in the 1960s. He writes for students of the Apollo project, for whom the development of the flight software is still largely unexplored territory, but also for the young coders of the current digital culture, who will get the author's observations on the art of programming and who may identify as he explores sex, drugs, and the other excitements of the era. The underlying thesis is that the American space program in the 1960s was successful not in spite of, but in large measure because of the idealism, the freedom of thought, and the sense of exploration, inner and outer, that prevailed in the culture during that period. The memoir concludes in a party atmosphere at the spectacular night launch of Apollo 17 before a glittery crowd an occasion that marked the high water mark, so far, of human space exploration.

    These people are celebrities now. What was it like when they were just a couple friends with an idea? Founders like Steve Wozniak (Apple), Caterina Fake (Flickr), Mitch Kapor (Lotus), Max Levchin (PayPal), and Sabeer Bhatia (Hotmail) tell you in their own words about their surprising and often very funny discoveries as they learned how to build a company.Where did they get the ideas that made them rich? How did they convince investors to back them? What went wrong, and how did they recover?Nearly all technical people have thought of one day starting or working for a startup. For them, this book is the closest you can come to being a fly on the wall at a successful startup, to learn how it's done.But ultimately these interviews are required reading for anyone who wants to understand business, because startups are business reduced to its essence. The reason their founders become rich is that startups do what businesses do--create value--more intensively than almost any other part of the economy. How? What are the secrets that make successful startups so insanely productive? Read this book, and let the founders themselves tell you.

    Creative Selection recounts the life of one of the few who worked behind the scenes, a highly-respected software engineer who worked in the final years the Steve Jobs era--the Golden Age of Apple.Ken Kocienda offers an inside look at Apple's creative process. For fifteen years, he was on the ground floor of the company as a specialist, directly responsible for experimenting with novel user interface concepts and writing powerful, easy-to-use software for products including the iPhone, the iPad, and the Safari web browser. His stories explain the symbiotic relationship between software and product development for those who have never dreamed of programming a computer, and reveal what it was like to work on the cutting edge of technology at one of the world's most admired companies.Kocienda shares moments of struggle and success, crisis and collaboration, illuminating each with lessons learned over his Apple career. He introduces the essential elements of innovation--inspiration, collaboration, craft, diligence, decisiveness, taste, and empathy--and uses these as a lens through which to understand productive work culture.An insider's tale of creativity and innovation at Apple, Creative Selection shows readers how a small group of people developed an evolutionary design model, and how they used this methodology to make groundbreaking and intuitive software which countless millions use every day.

    A forward-thinking manifesto from three Stanford professors—experts who have worked at ground zero of the tech revolution for decades—which reveals how big tech’s obsession with optimization and efficiency has sacrificed fundamental human values and outlines steps we can take to change course, renew our democracy, and save ourselves.

    Billions of interconnected devices will be monitoring the environment, transportation systems, factories, farms, forests, utilities, soil and weather conditions, oceans and resources Many of these sensors and actuators will be networked into autonomous sets, with much of the information being exchanged machine-to-machine directly and without human involvement. Machine-to-machine communications are typically terse. Most sensors and actuators will report or act upon small pieces of information - chirps. Burdening these devices with current network protocol stacks is inefficient, unnecessary and unduly increases their cost of ownership. This must change. The architecture of the Internet of Things will entail a widely distributed topology incorporating simpler chirp protocols towards at the edges of the network. Rethinking the Internet of Things describes reasons why we must rethink current approaches to the Internet of Things. Appropriate architectures that will coexist with existing networking protocols are described in detail. An architecture comprised of integrator functions, propagator nodes, and end devices, along with their interactions, is explored. What you'll learn Teaches the difference between the "normal" Internet and the Internet of Things, Describes a new architecture and its components in the "chirp" context. Explains the shortcomings of IP for IoT. Describes the anatomy of the IoT. Re-frames key ideas such as reliability. Describes how to build the IoT Who this book is forThought leaders, executives, architectural, standards and development leaders in the evolving IoT industry