Tag Archives: software engineering

Link Roundup, 9/30/14: Mobile Wallets

Mobile Wallets

This blog post began as a mission to compare and contrast mobile wallet systems. Instead, it became a survey of why mobile wallets are not more popular. The reason is not that we’re lacking choice in the mobile wallet economy. We can choose from Amazon Wallet, Apple Pay, Coin, Google Wallet, LoopPay, and Verizon’s Softcard, among others.

Why Aren’t Mobile Wallets More Popular in the US? and The Future Of Mobile Digital Wallet Technology in the UK:  Lindsay Konsko at NerdWallet speculates on why the United States lags other countries in adopting virtual wallet technology; then Kristopher Arcand at Forrester explains why the UK lags the US.

Why Mobile Wallets Are Failing and Will Keep Failing: Kyle Chayka at Pacific Standard Magazine maintains that mobile wallets won’t be universally accepted by smartphone users until they are universally accepted by merchants. Continue reading

“What I learned at a SATURN conference and applied in my organization”

How has something you learned or saw at SATURN changed how you develop software?

Since the first conference in 2004, SATURN has been a place for software developers to share stories about our adventures in building software. Architects, managers, and programmers from across industries and the world came together once a year to share stories about our experiences applying software architecture-centric practices.

Continue reading

Link Roundup, 9/22/14: Consensus Algorithms and Distributed Systems

Consensus Algorithms and Distributed Systems

Consensus algorithms for distributed systems represent a growing field focused on increasing the efficiency of these systems while decreasing their vulnerability to attack and component failure. These recent blog posts offer some theory and practice on consensus algorithms.

The Space Between Theory and Practice in Distributed Systems: Marc Brooker at Marc’s Blog discusses the gap between theory and practice in materials on distributed systems, using consensus algorithms as an example. Much material exists on the theory end of the continuum; much exists on the practice end of the continuum. What’s in the middle?

Continue reading

SATURN 2015 Proposal Guidelines

One of our goals every year with SATURN is to create a solid technical program that is informative, engaging, and lasting. When evaluating proposals for the program, the review committee uses the following guidelines to help decide whether a proposal is a good match for this year’s conference. In these guidelines, the term “session” is used generically to describe any talks, workshops, tutorials, and so on in the conference program.

Informative sessions share meaningful insights with lessons that attendees will be able to apply directly with their teams after the conference.

  • Is the information proposed relevant to one of the topic themes in this year’s conference?
  • Are there succinct lessons supported by real-world examples, research, or direct experience?
  • Is the topic of broad or general interest?
  • Can the lessons be applied beyond small sub-communities of practice?

Engaging sessions create an active learning environment that promotes information retention and generally gets attendees excited about the topics discussed. Continue reading

Link Roundup, 9/8/14: Microservice Architecture

Microservice Architecture

Since James Lewis and Martin Fowler published their article on Microservices in March 2014, the microservices architecture pattern has been the subject of much debate in the blogosphere: Is there a good definition for it (or not), is it another form of SOA (or not), is it an answer to the monolith (or not), is it a fad or the next big thing? The following blog posts contribute to the discussion on some of these topics.

Failing at Microservices: Please avoid our mistakes!: Richard Clayton’s Unrepentant Thoughts on Software and Management recently included a blog post about his team’s attempt to implement a microservice architecture, four reasons why it failed, and some recommendations for avoiding these problems.

Microservices for the Grumpy Neckbeard: Chris Stucchio discusses what he sees as the two camps of the debate about microservices, the hipsters who see their many benefits and the neckbeards who are more suspicious, and describes an architecture that may serve to bring the two camps together. Continue reading

Jørn Ølmheim and Harald Wesenberg on Teaching Architecture Metamodel-First, George Fairbanks, SATURN 2014 Presentation

By Jørn Ølmheim and Harald Wesenberg
Statoil ASA

We were fortunate enough to be able to participate at SATURN 2014. For Jørn, this was his first time at SATURN, while for Harald it was the fourth SATURN conference. As always, we knew that the quality of the conference content is high, and we were looking forward to a fun week with learning new and interesting ideas from other practitioners.

In this group of excellent presentations and tutorials there were many that stood out, but to us George Fairbanks’ talk on teaching architecture was definitely one of the greatest. Many of the more experienced participants at the conference recognized George’s experiences of trying to teach the importance of architecture to the junior team members with varying degree of success, so we were well motivated for a discussion about how this can be done better. Many of us recognize the challenges of motivation and lack of commitment both from your peers and the company to spend time on such activities.

Continue reading

Link Roundup, 9/2/14: DevOps: Definitions and Misconceptions

DevOps: Definitions and Misconceptions

This month, Ben Kepes at Forbes reported on ScriptRock’s efforts to raise funding from investors to expand their operations in “To Help DevOps-ify The World.” Kepes opens with an explanation of how ScriptRock must first differentiate its product and services from vendors selling “DevOps in a box.” More agile software development in less time, however, may not fit neatly in that box. Here are some links to definitions of DevOps that include components that exist outside of the box.

Defining DevOps Might Be Harder Than Defining Design: In the Under Development podcast series, Bill Higgins and Michael Coté explain DevOps, metrics, and “the processes used by designers vs. software developers vs. management consultants vs. wedding planners.” Continue reading

SEI Presentations on DevOps and Testing in Chicago, September 18

Stephany Bellomo of the SEI will be speaking at the Unicom DevOps Chicago Summit on September 18, 2014 on “Design Implications of DevOps.” Here is an abstract of Stephany’s talk:

Continue reading

Link Roundup, 8/21/14: Wearable Computing

Wearable Computing

Wearable computing is coming to the masses in the forms of fitness, gaming, and medical devices while non-consumer markets such as defense and aerospace continue to push for advanced wearable technologies to enhance safety, mobility, and efficiency in places most people will never go. Here are some recent examples of the state-of-the-art technology in wearable computing and then some that, with a little tech-know-how, you can make at home:

Intel Battles Parkinson’s Disease with Big Data and Wearable Tech: Mike Wheatley at Silicon Angle describes a new project at Intel, in which a Big Data analytics platform combined with a wearable device will produce a better record of symptoms experienced by Parkinson’s patients .

The Inside Story of the Oculus Rift: Peter Rubin at Wired reports that, with the Rift, Oculus hacks the visual cortex to make a virtual-reality headset that doesn’t cause “cold sweat syndrome.”

The Cardboard Project: Google Developers show how you can build your own basic VR headset with a smartphone and some basic items that you can get at the hardware store.

Raspberry Pi GPS Helmet Cam: Martin O’Hanlon at Stuff About Code used his Raspberry Pi­-based car cam to develop a helmet cam, takes it snowboarding, and record data about speed, altitude, and temperature.

 

Link Roundup, 8/14/14: Test-Driven Development: Dead or Alive?

Test-Driven Development: Dead or Alive?

Back in the Spring, a single blog post sparked a debate that on the surface seems absurd. Is TDD actually useful and still relevant? The discourse that followed and is still following this discussion is spectacular and spans Twitter, blogs, and a series of video debates. We thank Michael Keeling of Never Let Down for bringing this debate to our attention.

TDD is dead. Long live testing.: David Heinemeier Hansson, the creator of Ruby on Rails, discusses the death of test-driven development and the need to transition from unit testing to system testing.

Is TDD Dead?: Martin Fowler engages Hansson and Kent Beck in a series of video conversations on the topic of test-driven development and its impact on software design, including confidence, test-induced design damage, and cost. Continue reading