Backbone using Extensible Database APIs over HTTP + Webpack for the win!

On March 18th, 2015 I hosted the Backbone.js Hackers meetup in San Francisco, CA at Remind.

Thanks Avenue Code for sponsoring the food and drinks and Brenda Campbell from Remind for arranging the venue!

On this meetup we had 2 talks:

1) Jerry Su - Upgrading your JavaScript with Webpack

Webpack is a flexible and extensible module bundler that can boost your productivity when building web applications. If you use or have heard of Browserify and RequireJS, then you know how these module systems improve code organization. webpack goes a step further and bundles not only JavaScript, but also CSS, images, fonts, and all other static resources with little effort. webpack also provides a development server that can improve your workflow by eliminating all or most of your build with an environment that is more fun to work with (linting in the browser, hot code replacement, and more) while minimizing differences between your production environment. I will focus on how you can start using webpack today on an existing codebase so that you can begin to take advantage of these many benefits.

Check out the list of commits showed in upgrading the TodoMVC/RequireJS app to use Webpack.

2) Max Neunhöffer - Extensible database APIs and their role in software architecture

These days, more and more software applications are designed using a micro services architecture, that is, as suites of independently deployable services, talking to each other with well-defined interfaces. This approach is helped by the fact that many NoSQL databases expose their API through HTTP, which makes it particularly easy to define the interfaces.

In this talk I will explain the benefits of this approach to the
software architecture and development process. I will keep the presentation practice oriented by showing concrete examples in ArangoDB and JavaScript, using Backbone.js

Check out Backbone using Extensible Database APIs over HTTP + Webpack for the win!.

You can also watch the videos for slides and speakers.

Revisiting XP - be a thoughtful programmer by exercising more collective ownership

In March, 2015 I published an article on InfoQ, about effectively exercising collective ownership to avoid confrontation and technical debt.

Article Revisiting XP: be a thoughtful programmer by exercising more collective ownership - InfoQ


All in all, developers face regular frustration. This is pretty much because we are all artful individuals, so every single developer has his own tenets. Such tenets represent much more than what is taught in college - they actually constitute the developer’s personality! They are your fingerprint, something that can identify you. When a second developer reads your code, he will start making assumptions about you.

When two developers’ personalities run into each other, there is generally confrontation. While this can be extremely educational and uplifting, it can also be disturbing and troublesome if both parties don’t share a positive attitude. A key factor here is exercising what I call “thoughtful programming”.

This article will give a few suggestions about how to program in a more thoughtful way, by revisiting one of the XP (Extreme programming) rules: the concept of collective ownership.