- Build Quality In — an e-book collection of Continuous Delivery and DevOps experience reports from the wild. Work in progress, and a collection of accumulated experience in the new software engineering practices can’t be a bad thing.
- UX Directory — collection of awesome UX resources.
- Designing for Large-Screen Cellphones (Luke Wroblewski) — In his analysis of 1,333 observations of smartphones in use, Steven Hoober found about 75% of people rely on their thumb and 49% rely on a one-handed grip to get things done on their phones. On large screens (over four inches) those kinds of behaviors can stretch people’s thumbs well past their comfort zone as they try to reach controls positioned at the top of their device. Design advice to create interactions that don’t strain tendons or gray matter.
- fastsocket (Github) — a highly scalable socket and its underlying networking implementation of Linux kernel. With the straight linear scalability, Fastsocket can provide extremely good performance in multicore machines.
Software engineer and author Jason Myers on changing roles in a changing market.
We often hear about how the tech job market is booming and has space for newcomers, but what does that mean for the developers already in the market? In December of 2014, Fortune.com predicted that 2015 would be an excellent year for developers to change jobs. Citing Dice.com, they note that jobs are popping up all over the country. In fact, Dice’s survey also reports 40% of hiring managers seeing voluntary departures, a higher number than was seen just six months earlier.
These are all large, general numbers. What does a job change, and the changing market, look like for individual developers? To get a better sense, I spoke with Jason Myers, who is working on our upcoming Essential SQLAlchemy, 2e title. Jason recently went from working for the email marketing service Emma, Inc., to working for networking giant Cisco. Here, he talks about how a change like that feels, and how the market looks to him.
In this O'Reilly Radar Podcast: Edd Dumbill on the data lake, and Rajiv Maheswaran on the science of moving dots.
In a recent blog post, Edd Dumbill, VP of strategy at Silicon Valley Data Science, wrote about the phrase “data lake.” Likening it to a dream, he described a data lake as “a place with data-centered architecture, where silos are minimized, and processing happens with little friction in a scalable, distributed environment…Data itself is no longer restrained by initial schema decisions, and can be exploited more freely by the enterprise.” He explained that he called it a “dream” because “we’ve a way to go to make the vision come true” — but noted he’s optimistic the dream can be realized.
Powering your app with open source and OpenShift
As a software developer, you are no doubt familiar with the process of abstracting away unnecessary detail in code — imagine if that same principle were applied to application hosting. Say hello to Platform as a Service (PaaS), which enables you to host your applications in the cloud without having to worry about the logistics, leaving you to focus on your code. This post will discuss five ways in which PaaS benefits software developers, using the open source OpenShift PaaS by Red Hat as an example.
No More Tedious Config Tasks
Most of us don’t become developers to do system administration, but when you are running your own infrastructure you end up doing exactly that. A PaaS can take that pain away by handling pesky config and important security updates for you. As a bonus, it makes your sys admin happy too by allowing you to provision your own environment for that killer new app idea you want to tinker with, rather than nagging them for root access on a new VM.
On OpenShift, it goes like this: let’s say you decide you want to test an idea for a Java app, using Tomcat and PostgreSQL (yes, we could argue about the merits of those choices, but work with me here). You can spin that up with a one-line terminal command:
rhc app create myawesomeapp tomcat-7 postgresql-9.2 -s
That -s on the end is telling the platform to make the app auto-scaling, which I will elaborate on later; yes, that’s all it takes. RHC (Red Hat Cloud) is just a Ruby Gem wrapping calls to the OpenShift REST API. You could also use the OpenShift web console or an IDE plugin to do this, or call the API directly if that’s how you roll. The key technologies in play here are just plain old Git and SSH — there’s nothing proprietary.
GUI Prototyping, Linux Containerisation, Searchable Apple Text, and Infosec Wargames
Retro Literacy, Open Source Car Middleware, Digital Textbooks, and Mario Reborn
- ActiveLit — interactive fiction as literacy tool. (via Text Adventures blog)
- Your Car is About to go Open Source (ComputerWorld) — an open-source IVI operating system would create a reusable platform consisting of core services, middleware and open application layer interfaces that eliminate the redundant efforts to create separate proprietary systems. Leaving them to differentiate the traditional way: ad-retargeting and spyware.
- The Digital Networked Textbook: Is It Any Good? (Dan Meyer) — “if you were hundreds of feet below the surface of the Earth, in a concrete bunker without any kind of Internet access, is the curriculum any different?”
- Full Screen Mario — web reimplementation of original Mario Brothers, with random level generator and a level editor, source on github. (via Andy Baio)
Art and Money, Probabilistic Programming, Feature Flow, and Good Drones
- How Jim Henson Turned His Art Into a Business (Longreads) — When Henson joined on to the experimental PBS show Sesame Street in 1968, he was underpaid for his services creating Big Bird and Oscar. Yet he spent his free nights in his basement, shooting stop-motion films that taught kids to count. If you watch these counting films, the spirit of Henson’s gift shines through. I think any struggling artist today could count Henson among their ilk. He had all the makings of a tragic starving artist. The only difference between him and us is that he made peace with money.
- Probabilistic Programming and the Democratization of AI (YouTube) — talk by Brian Ruttenberg, examples in Figaro, a Scala library which is apparently open source despite hiding behind a “give us your contact details” form.
- Linux Panel — love the crossflow of features: “Embedded today is what enterprise was five years ago,” Kroah-Hartman said. “You have a quad-core in your pocket. The fun thing about Linux is all the changes you make have to work on all the things.” The advances in power management driven by mobile devices initially weren’t that interesting to enterprise developers, according to Kroah-Hartman. That quickly changed once they realized it was helping them save millions of dollars in data center power costs.
- A Drone’s View of the Colorado Floods (DIY Drones) — some amazing footage.
Google Play Services, Self-Signed Kernels, Visualising Scientific Papers, and New Microcontroller
- How Google’s Defragging Android (Ars Technica) — Android’s becoming a pudgy microkernel for the Google Play Services layer that’s in userland, closed source, and a way to bypass carriers’ lag for upgrades.
- Booting a Self-Signed Linux Kernel (Greg Kroah-Hartman) — procedures for how to boot a self-signed Linux kernel on a platform so that you do not have to rely on any external signing authority.
- Paperscape — A map of scientific papers from the arXiv.
- Trinket — Adafruit’s latest microcontroller board. Small but perfectly formed.
The past, present, and future of Dell's project
Barton George (@barton808) is the Director of Development Programs at Dell, and the lead on Project Sputnik—Dell’s Ubuntu-based developer laptop (and its accompanying software). He sat down with me at OSCON to talk about what’s happened in the past year since OSCON 2012, and why he thinks Sputnik has a real chance at attracting developers.
Key highlights include:
- The developers that make up Sputnik’s ideal audience [Discussed at 1:00]
- The top three reasons you should try Sputnik [Discussed at 2:46]
- What Barton hopes to be talking about in 2014 [Discussed at 4:36]
- The key to building a community is documentation [Discussed at 5:20]
You can view the full interview here: