Weekly highlights and insights

Stop standardizing HTML, persistence of plastic, social media's 2.0 moment, map of U.S. terror attacks 1970-2011

Stop standardizing HTML: Simon St. Laurent writes “HTML itself is still useful—many people and tools know how to read and write it—but there is less and less reason to let the HTML vocabulary be a cage limiting our possibilities.” His unique take on the issue prompted an uproar on Slashdot.

The persistence of plastic: Did you know that plastic production during the past decade equals that of the entire twentieth century?

Agile in name only: James Turner calls out companies that claim to embrace agile development, but don’t really understand it. Is agile really agile if you end up going over a waterfall at the end?

Social media’s 2.0 moment: Over on O’Reilly Radar Joshua-Michéle Ross wonders if apps like SnapChat and Poke are creating a massive acceleration in the traditional timeline needed to create branded content.

Visualization of the Week: Gain some perspective and cut through the jungle canopy that is the 24/7 news cycle. Using START Global Terrorism Database, the Guardian’s Simon Rogers mapped every U.S. terror attack between 1970 and 2011.

Comment |

A human approach to postmortem reviews

Dave Zwieback on how considering the human side of outages and postmortems can help build more resilient systems and teams.

There is nothing pleasant about postmortem reviews following an outage, and many companies struggle to execute positive, effective reviews. In a recent interview, Dave Zwieback (@mindweather), head of infrastructure at Knewton, said that we often focus only on technical issues during postmortems, to the exclusion of human elements. We also tend to fall into the “blame game” and point fingers when assessing particularly bad outages, he said.

In the following interview, Zwieback addresses the importance of including human and organizational elements in postmortem reviews, and outlines contributing factors to take into consideration, such as particular stressors and cognitive biases. He will address these issues further in a free online webcast, The Human Side of Postmortems, at 1 p.m., (PT) April 30.

How are postmortems typically approached, and why is it so important to make human and organizational factors more of a concern?

Read more…

Comment |

How you can stop trashing PHP code

Design patterns for PHP

William Sanders (@williebegoode) is a Professor of Interactive Information Technology at the University of Hartford and author of over 40 technical books! His latest book with us is Learning PHP Design Patterns. We recently sat down to talk about design patterns and how they can help create reusable code and save you valuable time. You can also check out more from Bill at his website.

  • Why use design patterns for PHP? [Discussed at the 0:28 mark.]
  • Big programs and lots of code can become unwieldy [Discussed at the 2:06 mark.]
  • Mobile devices and PHP design patterns [Discussed at the 5:30 mark.]
  • Bill talks common design patterns and how they help [Discussed at the 7:25 mark.]
  • How to start using design patterns with PHP [Discussed at the 10:15 mark.]

You can view the entire interview in the following video:

Related:

Comment |

Stop standardizing HTML

It's time for developers to create their own vocabularies

When HTML first appeared, it offered a coherent if limited vocabulary for sharing content on the newly created World Wide Web. Today, after HTML has handed off most of its actual work to other specifications, it’s time to stop worrying about this central core and let developers choose their own markup vocabularies and processing.

When the W3C first formed, it formed around HTML, the core standard of content on the Web, defining the structure, appearance, and behavior of content. Over the next few years, however, it became clear that HTML was doing too much, and the W3C and other groups refactored appearance, behavior, and many semantics into separate specifications:

  • Cascading Style Sheets (CSS) took responsibility for presentation and layout.

  • JavaScript took responsibility for behavior, aided by the Document Object Model (DOM) and a variety of APIs for handling device and multimedia interactions.

  • WAI-ARIA took responsibility for accessibility semantics, ensuring that content remained available to a broad audience even if developers pushed the current boundaries of markup.

It’s not a completely neat separation – some of CSS feels like behavior, and JavaScript can manipulate presentation, for example, but it certainly took a lot of pieces out of HTML. A few aspects of HTML, notably media inclusion, are still mostly handled at the markup level, but most of them aren’t any longer. Forms and linking are both still defined in HTML itself, but aren’t difficult to implement separately.

Read more…

Comments: 53 |

Yet another JavaScript book?

For the next 15 weeks, a new learning video every week.

Eric Freeman and I are writing a new book: Head First JavaScript Programming, and to go along with it, we’re creating a series of teaser videos to give you a taste of what’s coming in the book, and a chance to learn a few JavaScript tidbits.

Why undertake writing a JavaScript book now? After all, isn’t there already a Head First JavaScript book (not to mention all the many other JavaScript books on the market)? Well, to make a long story short, when we published Head First HTML5 Programming, a book that teaches you how to use all the new HTML5 APIs (with JavaScript, of course), we discovered something: a lot of folks know a little JavaScript, but really want to understand it at a deeper level. They want to go beyond just simple scripting. To remedy that, we ended up taking a month to write a brief introduction to JavaScript in our Head First HTML5 Programming book, but it wasn’t enough. Readers needed more.

Read more…

Comment |

Tech events you don’t want to miss

Codepalousa, TechCrunch Disrupt, MVA Live, and more

Each Monday, we round up upcoming event highlights from the programming and technology space. Have an event to share? Send us a note.


nicholas_c_zakasThe Best of Fluent: Maintainable JavaScript webcast

Date: 5 a.m. PT, April 24

Location: Online webcast

Why you shouldn’t miss it: Presenter Nicholas Zakas addresses best practices in writing maintainable JavaScript code. You can register for the free webcast on O’Reilly’s community website.


CodepalousaLogoCodepalousa

Date: April 25—27

Location: Louisville, KY

Why you shouldn’t miss it: It’s three days of nerding out in software dev sessions, workshops, and keynotes. For more information, visit the Codepalousa website.


ny-disrupt-2013-logoTechCrunch Disrupt NYC 2013

Date: April 27—May 1

Location: New York City

Why you shouldn’t miss it: The shindig kicks off with a 24-hour hackathon. And you might get to meet Ashton Kutcher. For more on the event and information on tickets, visit TechCrunch.


Read more…

Comment |

Agile in name only

Agile isn't agile if you end up going over a waterfall at the end.

In politics, the term RINO is used to refer to a candidate who is “Republican in Name Only,” i.e., claiming the mantle of the party, but not conforming to the platform or belief system. In software development, there’s a similar phenomenon: companies that claim to embrace agile development principles, but really don’t understand agile. They’re Agile in Name Only (AINO).

I’ve written before about “waterfall with a crunchy agile shell,” the problem that if you are trying to control all three of the variables (time, features, resources), you can’t really do agile. Agile acknowledges the uncertainty in development estimates, and requires the team to stay “ready to ship,” so that when the decision is made to pull the trigger on a release, all the work done to date can be easily consolidated and shipped. But focusing on keeping shippable units in shippable shape only makes sense if you also embrace the idea of frequent releases, and putting only in the release what fits in the bucket.

In contrast, a company that’s agile in name only will cling to a distant release date and a laundry list of features, but still insist on short sprints and closing stories. At this point, the benefit of short sprints isn’t for the developers or the team, it’s for management, because it lets them focus on their burn-down charts, and chart the progress toward that eventual release that may be a year away.
Read more…

Comment |

Twisted Python: The engine of your Internet

Learn to build event-driven client and server applications

I want to build a web server, a mail server, a BitTorrent client, a DNS server, or an IRC bot—clients and servers for a custom protocol in Python. And I want them to be cross-platform, RFC-compliant, testable, and deployable in a standardized fashion. What library should I use?

Use Twisted

Twisted is a “batteries included” networking engine for writing, testing, and deploying event-driven clients and servers in Python. It comes with off-the-shelf support for popular networking protocols like HTTP, IMAP, IRC, SMTP, POP3, IMAP, DNS, FTP, and more.

To see just how easy it is to write networking services using Twisted, let’s run and discuss a simple Twisted TCP echo server:

from twisted.internet import protocol, reactor
class Echo(protocol.Protocol):
    def dataReceived(self, data):
        self.transport.write(data)
class EchoFactory(protocol.Factory):
    def buildProtocol(self, addr):
        return Echo()
reactor.listenTCP(8000, EchoFactory())
reactor.run()

With Twisted installed, if we save this code to echoserver.py and run it with python echoserver.py, clients can now connect to the service on port 8000, send it data, and get back their echoed results. Read more…

Comment |

Commerce Weekly: Amazon patent indicates its interest in the payments space

Amazon patent may address payment privacy concerns, Warby Parker outfits store with sensors, and Alipay launches sound wave payments.

Editor’s note: This will be the final installment of our Commerce Weekly series.

Mobile payments security, privacy concerns rise; Amazon may have a solution

AmazonPatentFig8The race is on to democratize mobile payments, to create a solution that improves the payment experience for consumers and merchants to the extent that it will replace traditional payment methods. Some experts, however, are concerned that technology developments are failing to address increasing concerns with security and privacy.

Kirk Ladendorf reports this week that smartphone security software company NQ Mobile noted a rise in worldwide phone malware threats from 24,000 in 2011 to 65,000 in 2012. In an interview with Ladendorf, Gavin Kim, chief commercial officer at NQ Mobile, warned that “[s]martphone sales are booming, and they are becoming a much more targeted device by hackers.”

Brent Warrington, CEO of online and mobile payment company SecureNet, disagreed, telling Ladendorf that he’s “comfortable and confident in the level of security of [payment] transactions” through his company, noting that the transaction information is “encrypted from end to end.”

While security concerns may be getting addressed, Ladendorf says that privacy advocates don’t see the same attention being given to privacy concerns and the “potential misuse of growing mountains of electronic data tied to the spending patterns of individual consumers.” Ladendorf notes that the same advances that make mobile payments more enjoyable and convenient also make it easier for companies to mine consumer data. He quotes from a McClatchy newspaper interview with Jeff Chester, executive director of the Center for Digital Democracy, in which Chester said, “[Mobile payment] is about exposing your financial behavior to a daisy chain of financial and other marketers who have a very detailed understanding of where you are, how you spend your time and what you buy.”

Read more…

Comment: 1 |

Do’s and don’t's for changing the ratio of women in tech

Etsy's Marc Hedlund shares the tactics he's using to boost the diversity of his engineering team

You’ve probably heard of Etsy, the bustling online marketplace for crafters and artists. You probably wouldn’t be surprised to learn that most of its customers are women, both buyers and sellers. Ditto that the Etsy team is a pretty good representation of the Earth’s gender ratio.

Yet when Marc Hedlund took the helm of Etsy’s Product Development & Engineering department, 97% of the engineering department were men. Hedlund realized that in his nearly two decades in IT, he’s hired no more than 20 women for engineering positions. This began to bother him. Especially after his daughter was born.

“You’re in a position of authority. What have you done to make it better?”

While she’s only four, Hedlund imagines this is the pointed question his daughter will ask him when she’s old enough to follow in his footsteps in the computing industry.

Impatient to change the gender ratio before his daughter enters the workforce, Hedlund decided to take action. Last year, he partnered with Hacker School to create a training program to address the engineering shortage in general and the lack of gender parity in particular.

The result: women now make up 15% of Etsy’s engineering team.

How did he do it? In his video interview, Hedlund offers concrete advice for companies who want to hire more women in technical roles.

Read more…

Comments: 26 |