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.

    Based on experience, it is a guide for navigating the blockers, buzzwords and bloody-mindedness that doom any analogue organisation trapped into thinking that while the internet has changed the world, it won't change their world. Companies that grew up on the web have changed our expectations of the services we rely on. We demand simplicity, speed and low cost. Organizations founded before the Internet aren't keeping up - despite spending millions on IT, marketing and 'innovation'. This book is a guide to building a digital institution. It explains how a growing band of reformers in businesses and governments around the world have helped their organizations pivot to this new way of working, and what lessons others can learn from their experience. It is based on the authors' experience designing and helping to deliver the UK's Government Digital Service (GDS). The GDS was a new institution made responsible for the digital transformation of government, designing public services for the Internet era. It snipped �4 billion off the government's technology bill, opened up public sector contracts to thousands of new suppliers, and delivered online services so good that citizens chose to use them over the offline alternatives, without a big marketing campaign. Other countries and companies noticed, with the GDS model now being copied around the world.

    Remember what a wild frontier the early days of home gaming were? Manufacturers releasing new consoles at a breakneck pace; developers creating games that kept us up all night, then going bankrupt the next day; and what self-respecting kid didn't beg their parents for an Atari or a Nintendo? This explosion of computers, consoles, and games was genuinely unlike anything the tech world has seen before or since.This thoroughly researched and geeky trip down memory lane pulls together the most entertaining stories from this dynamic era, and brings you the classic tech that should never be forgotten.

    From creating new data-driven products through to increasing operational efficiency, big data has the potential to makeyour organization both more competitive and more innovative.As this emerging field transitions from the bleeding edge to enterprise infrastructure, it's vital to understand not only the technologies involved, but the organizational and cultural demands of being data-driven.Written by O'Reilly Radar's experts on big data, this anthology describes:- The broad industry changes heralded by the big data era- What big data is, what it means to your business, and how to start solving data problems- The software that makes up the Hadoop big data stack, and the major enterprise vendors' Hadoop solutions- The landscape of NoSQL databases and their relative merits- How visualization plays an important part in data work

    This bestselling Sybex study guide covers 100% of all exam objectives. You'll prepare for the exam smarter and faster with Sybex thanks to expert content, real-world examples, advice on passing each section of the exam, access to the Sybex online interactive learning environment, and much more. Reinforce what you've learned with key topic exam essentials and chapter review questions. Along with the book, you also get access to Sybex's superior online interactive learning environment that includes: Four unique 250 question practice exams to help you identify where you need to study more. Get more than 90 percent of the answers correct, and you're ready to take the certification exam. More than 650 Electronic Flashcards to reinforce your learning and give you last-minute test prep before the exam A searchable glossary in PDF to give you instant access to the key terms you need to know for the exam Coverage of all of the exam topics in the book means you'll be ready for: Security and Risk Management Asset Security Security Engineering Communication and Network Security Identity and Access Management Security Assessment and Testing Security Operations Software Development Security

    With jokes, puns, and a rigorous problem solving based approach. You can download all the code samples used in the book from here: http://www.robmiles.com/s/Yellow-Book...

    This book is aimed at the working Rails developer who is looking to grow and evolve Rails projects while keeping them flexible, maintainable, and robust. The focus is on pragmatic solutions which tread a “middle way” between the expedience of the Rails “golden path”, and rigid OO purity.

    Why is this open-source tool so popular? Because it automates a tedious task: persisting your Java objects to a relational database. The inevitable mismatch between your object-oriented code and the relational database requires you to write code that maps one to the other. This code is often complex, tedious and costly to develop. Hibernate does the mapping for you.Not only that, Hibernate makes it easy. Positioned as a layer between your application and your database, Hibernate takes care of loading and saving of objects. Hibernate applications are cheaper, more portable, and more resilient to change. And they perform better than anything you are likely to develop yourself."Hibernate in Action" carefully explains the concepts you need, then gets you going. It builds on a single example to show you how to use Hibernate in practice, how to deal with concurrency and transactions, how to efficiently retrieve objects and use caching.The authors created Hibernate and they field questions from the Hibernate community every day-they know how to make Hibernate sing. Knowledge and insight seep out of every pore of this book."What's Inside"- ORM concepts- Getting started- Many real-world tasks- The Hibernate application development process

    Most developers have a limited understanding of compositional techniques. It's time for that to change.In "Composing Software", Eric Elliott shares the fundamentals of composition, including both function composition and object composition, and explores them in the context of JavaScript. The book covers the foundations of both functional programming and object oriented programming to help the reader better understand how to build and structure complex applications using simple building blocks.You'll learn: • Functional programming • Object composition • How to work with composite data structures • Closures • Higher order functions • Functors (e.g., array.map) • Monads (e.g., promises) • Transducers • LensesAll of this in the context of JavaScript, the most used programming language in the world. But the learning doesn't stop at JavaScript. You'll be able to apply these lessons to any language. This book is about the timeless principles of software composition and its lessons will outlast the hot languages and frameworks of today. Unlike most programming books, this one may still be relevant 20 years from now.This book began life as a popular blog post series that attracted hundreds of thousands of readers and influenced the way software is built at many high growth tech startups and fortune 500 companies.

    It also includes real world cases.

    Now the retail banking business model looks set to be transformed too. In Bye Bye Banks? James Haycock and Shane Richmond describe these startups, and to which areas of the banking industry they are laying siege. It shows that this assault is already well underway and that many incumbents are poised to be displaced, diminished and disintermediated. It draws on extensive research and on-and-off the record interviews with senior executives in some of the biggest banks. Haycock and Richmond conclude with the recommendation that traditional banks need to reinvent themselves by launching a ‘Beta Bank’: a lean, stand-alone organisation fit for the future for which they provide a ten-point operating model. This short book is a bold, urgent and timely analysis of the forces shaping the future of financial services. Its message to industry leaders in the sector could not be more simple: adapt or prepare to be disrupted. “This work accurately and concisely captures the effects of the disruption brought to the banking industry by the digital revolution. The comments by other banking and innovation professionals about their own experiences are particularly intriguing.” - Alessandro Hatami, former Innovation Executive at Lloyds Banking Group “James Haycock is a key voice for how the banking industry should and will change.” - Tom Hopkins, Product Innovation Director, Experian Consumer Services “If you are an incumbent retail bank, read it, get on with it, make it happen.” - Lee Sankey, former Group Design Director, Barclays

    District Judge Stanley Sporkin. Teamed with the daughter of one of Bill Gates's closest associates, thirteen-year Microsoft veteran Marlin Eller shows us what it was like at every step along Gates's route to world domination, making all that's been written before seem like a rough guess. If the Justice Department had Eller and Edstrom investigating the current-headline-making antitrust case, they would have on the record many of Microsoft's most respected developers directly contradicting the "authorized" version of events being presented in court. They would know the real scoop on how Windows was developed in the first place, shedding new light on the 1988 Apple v. Microsoft lawsuit over the alleged copying of the Mac. They would even know the real story of how Microsoft killed off Go Corporation, told for the first time by the man who did the deed, Marlin Eller himself. Revealing the smoke-and-mirror deals, the palms greased to help launch a product that didn't exist, and the boneyard of once-thriving competitors targeted by the Gates juggernaut, this book demonstrates with often hilariously damning detail the Microsoft muddle that passes for strategic direction, offset by Gates's uncanny ability to come from behind to crush whoever's on top.

    This is necessary because, in the words of Michael Polanyi, "we can know more than we can tell." Our design choices are not the result of an ineluctable chain of logic; they come from a deeper place, one which is visceral and inarticulate.Polanyi calls this "tacit knowledge", a thing which we only understand as part of something else. When we speak, we do not focus on making sounds, we focus on our words. We understand the muscular act of speech, but would struggle to explain it.To write software, we must learn where to draw boundaries. Good software is built through effective indirection. We seem to have decided that this skill can only be learned through practice; it cannot be taught, except by example. Our decisions may improve with time, but not our ability to explain them. It's true that the study of these questions cannot yield a closed-form solution for judging software design. We can make our software simple, but we cannot do the same to its problem domain, its users, or the physical world. Our tacit knowledge of this environment will always inform our designs.This doesn't mean that we can simply ignore our design process. Polanyi tells us that tacit knowledge only suffices until we fail, and the software industry is awash with failure. Our designs may never be provably correct, but we can give voice to the intuition that shaped them. Our process may always be visceral, but it doesn't have to be inarticulate.And so this book does not offer knowledge, it offers clarity. It is aimed at readers who know Clojure, but struggle to articulate the rationale of their designs to themselves and others. Readers who use other languages, but have a passing familiarity with Clojure, may also find this book useful.

    This is not a handbook. It’s more like a history book.Marshall McLuhan once said:We look at the present through a rear‐view mirror. We march backwards into the future.But in the world of web design, we are mostly preoccupied with the here and now. When we think beyond our present moment, it is usually to contemplate the future—to imagine the devices, features, and interfaces that don’t yet exist. We don’t have time to look back upon our past, and yet the history of web design is filled with interesting ideas.The World Wide Web has been around for long enough now that we can begin to evaluate the twists and turns of its evolution. I wrote this book to highlight some of the approaches to web design that have proven to be resilient. I didn’t do this purely out of historical interest (although I am fascinated by the already rich history of our young industry). In learning from the past, I believe we can better prepare for the future.You won’t find any code in here to help you build better websites. But you will find ideas and approaches. Ideas are more resilient than code. I’ve tried to combine the most resilient ideas from the history of web design into an approach for building the websites of the future.I hope you will join me in building a web that lasts; a web that’s resilient.

    It's friendly, accessible, and reliable -- all qualities that apply to its official guidebook, too. This book captures the welcoming feel of the Ubuntu community, inviting you to get involved both as user and participant. But it also covers all the techniques you need to succeed happily with Ubuntu: from installation and configuration to "office applications," CD burning to instant messaging, networking to troubleshooting. There are plenty of specific answers: how to make Ubuntu run faster on older computers; better coexistence with Windows; fixes for balky microphones and scroll-wheel mice; tips for recovering lost system passwords, and much more. You'll even find chapters on Kubuntu (Ubuntu preconfigured with the KDE graphical user interface) and Edubuntu (Ubuntu optimized for schools). Plus, instant gratification: This book's DVD contains the full 7.0.4 "Feisty Fawn" distribution. Bill Camarda, from the October 2007 href="http://www.barnesandnoble.com/newslet... Only