Cover photo
Verified name


Here's our Video Deal of the Week: Software Architecture Fundamentals Part 1 - $44.99 (Save 50%) Use code VDWK

Software Architecture Fundamentals Part 1
Understanding the Basics
By Neal Ford, Mark Richards

In this anticipated video series, Neal Ford and Mark Richards examine the responsibilities of a software architect, specifically the knowledge and skills you need to be effective in that role.

The first video, Understanding the Basics, not only focuses on development techniques, but also pinpoints the skills you need to be a successful team leader. You’ll learn about the four main aspects of a software architect, and quickly discover the difference between architecture decisions and technology decisions. In this video, you’ll explore:

Soft Skills

Investigate techniques for communicating effectively as a team leader
Measure your technical knowledge, including technical depth vs. technical breadth, and multi-platform skills
Discover how to increase your expertise of business domains
Learn how ensure a successful implementation by matching methodology with architecture
Architectural Techniques:

Make your architecture more adaptable to changes in business and technology
Explore various techniques and patterns for integrating multiple applications and databases
Get a true understanding of enterprise architecture by examining the context and goals of an EA implementation
The topics in this video set the stage necessary to understand the enterprise architecture approaches and strategies demonstrated in the series’ second video: Software Architecture Fundamentals: A Deeper Dive.
#enterprisearchitecture   #softwarearchitecture   #softwaredevelopment   #OReilly  
Андрей Рогачёв's profile photoRey Ley's profile photo
Add a comment...


Shared publicly  - 
+Tim O'Reilly will be on +reddit today at 10:00AM PT for his first IAMA.

We'll post the link to the Reddit Thread at 9:30AM PT here:

Come join the conversation, ask Tim about the internet of things, the industrial internet, wearables, Hardware, Software, and just about anything.  
#OReilly   #IoT   #IndustrialInternet   #Wearables   #OreillySolid  +O'Reilly Solid  #Hardware   #Software   #reddit   #RedditAMA  
O'Reilly Webcasts's profile photoO'Reilly's profile photoSuzanne Axtell's profile photoO'Reilly Verlag's profile photo
From Rhops on reddit:
What prompted the start of BioCoder? Are people really doing biotech in their garages in the same way that many computer hardware and software innovations happened?

Tim's Answer:
Yes, there is definitely a biotech revolution. We've been watching this for some years. When IGEM (the International Genetically Engineered Machines competition for high schoolers) started some years back, we knew it was only a matter of time. We've been looking at this area for at least a dozen years, and it seems to be heating up.

Come join the conversation:
Add a comment...


Shared publicly  - 
Do you want to ask +Tim O'Reilly  anything about +O'Reilly Solid? Join him on +reddit Tuesday, April 22nd for a live online event: 'I am Tim O'Reilly- Ask Me Anything (about #Iot )
Solymos Gellért's profile photoMarsee Henon's profile photo
Add a comment...
The Spring 2014 issue of BioCoder is out now, download your free copy Fungi; DIYBiomimicry; Hacking Lab Equip + more

We’re at the start of a revolution that will transform our lives as radically as the computer revolution of the 70s. The biological revolution will touch every aspect of our lives: food and health, certainly, but also art, recreation, law, business, and much more.

BioCoder is the newsletter of that revolution. It’s about biology as it moves from research labs into startup incubators, hacker spaces, and even homes. It’s about a very old programming language that we’re just beginning to understand, and that’s written in a code made up of organic chemicals. It’s the product of a sharing community of scientists that stretches from grade school to post docs and university faculty.
#Biocoder   #DIYBiology   #Biology   #biotechnology   #BioTech  #OReilly  
Seiichi KASAMA's profile photoCampbell Hore's profile photo
Add a comment...
Have you ever picked a lock? Ever wanted to know how to?
Save 50% on Lock Picking Ebooks and Never Be Locked Out Again 

Learn the fun art of picking locks

Lock picking isn't just for locksmiths and security pros—thousands of amateurs enjoy it as a hands-on exercise for learning about lock mechanisms and how they keep you secure, or fail to. Written for pros and hobbyists alike,'s lock picking titles have easy-to-follow lessons to advance you in this fascinating field.

For one day only SAVE 50% on lock picking ebooks and unlock the secrets of door-ware security and more. 

Ebooks from are DRM-free. You get free lifetime access, multiple file formats, and free updates. Sync with Dropbox — your files, anywhere.

Use discount code DEAL - Deal expires April 12, 2014 at 5AM PT, and cannot be combined with other offers. Offer does not apply to Print, or "Print & Ebook" bundle pricing.
#Lockpicking   #LockPick   #Howtopickalock   #OReilly   #ebook  
Electrotechnology&GeneralEngineeringStudents's profile photoAkira Ishino's profile photoNicholas Dunn's profile photoFireicer Cooper's profile photo
Yes i have and i picked up the skill very quickly
Add a comment...
From the +The New York Times Technology section,
Heartbleed Highlights a Contradiction in the Web

“Open source is not magic fairy dust” that happens automatically, said +Tim O'Reilly , an early advocate of open source and the founder of O’Reilly Media. “It happens because people work at it.”

Read the rest of the New York Times Article here:
#OpenSource   #Technology   #heartbleed   #OReilly  
The bug that rattled the Internet last week exposed the paradox that some of the web’s most crucial coding depends on the efforts of volunteers.
Snow Andrews's profile photoLars Schotte's profile photo
Add a comment...
Toward an open Internet of Things
Vendors, take note: we will not build the Internet of Things without open standards. From +Mike Loukides via +O'Reilly Radar

In a couple of posts and articles, we’ve nibbled around the notion of standards, interoperability, and the Internet of Things (or the Internet of Everything, or the Industrial Internet, or whatever you want to call it). It’s time to say it loud and clear: we won’t build the Internet of Things without open standards.
What’s important about the IoT typically isn’t what any single device can do. The magic happens when multiple devices start interacting with each other. Nicholas Negroponte rightly criticizes the flood of boring Internet-enabled devices: an oven that can be controlled by your phone, a washing machines that texts you when it’s done, and so on. An oven gets interesting when it detects the chicken you put in it, and sets itself accordingly. A washing machine gets interesting if it can detect the clothes you’re putting into it and automatically determine what cycle to run. That requires standards for how the washer communicates with the washed. It’s meaningless if every clothing manufacturer implements a different, proprietary standard for NFC-enabled tags.
We’re already seeing this in lighting: there are several manufacturers of smart network-enabled light bulbs, but as far as I can tell, each one is controlled by a vendor-specific app. And I can think of nothing worse for the future of home lighting than having to remember whether the lights in the bedroom were made by Sylvania or Philips before I can turn them off. Philips’ API for their Hue light bulbs is a great start, particularly in the way they encourage interoperability between third party applications: “You are free to develop any kind of application you can imagine. … We want all your apps to work with our API to form a rich ecosystem of interoperable applications.” But that only gets us part of the way there. What about other vendors? After reading their terms of use, I suspect strongly that Philips would not be pleased by other light bulb manufacturers using the Hue API for their bulbs. Can an API be copyrighted or patented? That question is working its way through the appellate courts now, in the notorious Oracle v. Google case.
A light bulb, even a high-tech smart LED light bulb, is a simple device. What do proprietary apps mean for larger, more complex devices, like cars? It’s all very well that one can use the Tesla app to communicate with a Tesla automobile, but for a real automotive Internet of Things, you want cars from different manufacturers to share information like traffic, road conditions, etc. Now, you might say this isn’t really the IoT — it’s just the Internet — since apps like Google Maps and Waze already do that on our smartphones, and they just ought to do it for our cars. And that’s exactly right. Those same apps from our phones ought to work in our cars, from car to car and from phone to car. According to Tim O’Reilly, the worst feature of his Tesla Model S is its non-standard software. Its licensed version of Google Maps has such a bad implementation of real-time traffic that you have to use maps on your phone (and this in a car with a full-featured web browser, in which access to Google Maps is disabled so they can sell you an “enhanced” electronics “upgrade” that includes their own broken version of Google Maps!) And while he loves being able to track the location of the car via the Tesla app, it is slow and buggy. How much better would it be if our cars and phones could share location data transparently with friends and family, with the information showing up in the mapping applications we already use.
One of the defining events of the early Internet was Interop, where device makers got together to make sure their devices could interoperate. (Interop is now largely marketing, a giant shadow of its former self.) We didn’t want a Cisco Internet and a Wellfleet Internet and a Bay Networks Internet, none of which could talk to each other. But now that we’re talking about “Things,” we’re about to build the mess that we avoided in the late 80s.
One reason the Internet works is that vendors weren’t allowed to implement protocols in a vacuum. The IETF would not standardize a protocol without “multiple, independent, and interoperable implementations.” And in practice, many of these implementations were based on publicly available code: for example, the BSD UNIX implementation of TCP/IP. That’s a good practice to remember. If the code isn’t visible, there are bound to be corner cases, gotchas, and maybe even secretive “embrace and extend” features to compromise interoperability.
The robustness principle is another of the Internet’s defining features: an implementation must “be conservative in what you do, be liberal in what you accept from others.” That is, participants should send data that obeys the specifications, but they should be willing to accept data that doesn’t. Again, this is about interoperability. If devices can only interact if they both interpret and implement protocols identically, we aren’t going anywhere. You might achieve interoperability between products from a single vendor (though even that seems doubtful), but you’ll never get frictionless interactions between products from different vendors. My Maytag washer might understand the tags on my Levis, but not on my shirts. A Tesla might be able to exchange information about road conditions with a Lexus, but not a Ford.
An Internet of standalone devices that don’t interoperate, whose only interaction is with a proprietary app that only runs on one brand of mobile phone: that’s just not interesting. That’s not a future. It might make a few geeks happy, and it might make an even smaller number of geeks wealthy, but I can’t imagine it ever becoming more than a curiosity. The engineers who designed the Internet — the Cerfs, the Kahns, the Postels — were wiser than that and developed a culture of interoperability from which everyone benefitted. Can a similar culture arise among the makers of Things? I hope so, but it’s not a sure thing.
Unfortunately, we’re still in a world where a manufacturer’s first reaction is to lock things down, to make devices incompatible, in an attempt to extract as much profit as possible from the system. If this is your mindset, you’re not going to release an API (as Philips did), let alone encourage your competition to build on the same API (as Philips hasn’t). And if you’re the competition, you’re more likely to develop your own API than to support your competitors’, even if doing so would provide a better market for all parties..
With the Internet, everyone won because nobody won. In the 80s, each computer vendor had a proprietary network: IBM, DEC, even startups like Apollo. The thinking was that if you made it hard to integrate equipment with other vendors, you could capture a client for yourself. The problem with that vision was simple: it was horrible for the customers. The assumption behind any “lock-in” strategy is ultimately that your product is poor and that customers will gladly switch vendors if given a chance. And customers did switch when they realized that they had a chance: away from the proprietary networks and toward the open TCP/IP protocols. By 1990, it was clear that the proprietary networks were disappearing and that we were converging on the open Internet standards. The rising tide did indeed float all the boats. The few vendors who tried to “differentiate” themselves with features that didn’t interoperate failed; Microsoft ultimately gave up on the desire to “embrace, extend, and extinguish” the web.
With the Internet of Things, it’s deja vu all over again. The vendors who provide public APIs and support open standards will succeed in the long run. Likewise, the vendors who try to trap consumers behind proprietary software and non-interoperable products will eventually fail, to everyone’s detriment. If you win the IoT, you lose it.
#Internetofthings #IoT #OpenSource #IndustrialInternet #OReilly #Solid #oreillysolid  
Андрей Рогачёв's profile photoRobert Le Blah's profile photoSolymos Gellért's profile photo
Add a comment...
Get the Job You Want by Gaining the Interview Skills You Need
Save 50% – Ebook Deal of the Day

You've landed the job interview and now you face a gauntlet of tough technical interviews, including language quirks, best practices, math, and the all-too-common coding-at-the-whiteboard test. Be prepared by studying a wide range of interview questions and acceptable answers. Learn what interviewers look for, and how to present your best side. Plus, know how to succeed once you've got the job.

For one day only, save 50% on career ebooks at and take your career forward.

Ebooks from are DRM-free. You get free lifetime access, multiple file formats, and free updates. Sync with Dropbox — your files, anywhere.

Use discount code DEAL - Deal expires April 19, 2014 at 5AM PT, and cannot be combined with
other offers. Offer does not apply to Print, or "Print & Ebook" bundle pricing.
#Jobs #interviewtips #OReilly #ebook  
Solymos Gellért's profile photoNick Petrov's profile photo
Add a comment...


Shared publicly  - 
We had a great time last week, and looking forward to seeing more folks join in this week,  Find out how, and mark your calendars.
#IoTChat Live Tweet Event by @OReillySolid is happening Wednesday April 16 at 6pm ET/ 3pm PT. This week's topic is #Robotics. Join special guest Tom Panzarella of Love Park Robotics and host +Jim Stogdill for 1 hour of intense conversation & a +romotive prize giveaway
Date: Wednesday, April 16th, 3 pm- 4 pm PST (12 pm - 1 pm ET) Location: #IoTChat (Search Hashtag on Twitter) or visit How to Join: Join #IoTChat Tweet Chat on April 16th about #robotics with Solid's @117132268332048906100 and guest Tom Panzarellla of Love Park Robotics. Join#IoTChat to be entered to win a free Romo Robot (  Connect with experts to discuss robotics a...
Carol Stephen's profile photo
I'll be there! But it's 6 pm ET, right?
Add a comment...
Here's our ebook Deal of the Day: Webmin Administrator's Cookbook - $13.49 (Save 50%) Use code DEAL 

Running your own dedicated server has become simpler and less expensive. These days, administering a development server or hosting sites and web applications has become part of the job for many developers. Webmin is an easy-to-use web-based tool which makes getting started with new administrative tasks and performing common jobs more simple and efficient.

Webmin Administrator's Cookbook offers practical, step-by-step recipes covering a range of topics related to setting up and administering a server. The book will show you how Webmin can help you configure an Apache web server, MySQL server, or PostgreSQL database server, as well as how to set up web applications running in PHP or Python.

The book starts by showing you how to set up Webmin on your server and provides you with clear, practical tutorials on configuring various services needed to run a full-fledged web server.

The book provides a handy reference for performing various administrative tasks using Webmin. Whether you want to lock down your server to put it on the Internet or open up more convenient access for use on an internal network, you'll learn how Webmin can help you do it.The book provides recipes for running Apache, MySQL, and PostgreSQL and for getting started with PHP, WordPress, Drupal, Python, and Django.Webmin Administrator's Cookbook will enable you to step more confidently into the world of server administration and prove to be a valuable add-on to your arsenal.
#WebAdmin   #Ebook   #webapplicationdevelopment   #PHP   #Drupal   #Python   #OReilly  
Add a comment...
O'Reilly Media spreads the knowledge of innovators.
Publisher of the iconic "animal books" for software developers, creator of the first commercial website (GNN), organizer of the summit meeting that gave the open source software movement its name, and prime instigator of the DIY revolution through its Make magazine, O'Reilly continues to concoct new ways to connect people with the information they need. O'Reilly conferences and summits bring alpha geeks and forward-thinking business leaders together to shape the revolutionary ideas that spark new industries.
Contact Information
Contact info
(707) 827-7000, (800) 998-9938
1005 Gravenstein Highway North Sebastopol, CA 95472