An Agile Spree

Posted on Fri, 05/09/2014 - 12:20

At the heart of Agile is flexibility. This is designed into sprints that are intended to account for changes rolled into subsequent sprints.But, think of an overall backlog. A high level estimation will yield a given number of sprints. This structure actually is not very flexible at all. Unless, of course, each sprint has time allocated for reviewing, testing, and bug fixing. This is a slippery slope; a more substantial change can really throw off a sprint. So, how do you address the issue of quality?I have recently been reading a lot about corporations paying others to hunt bugs in their

development people

Risks and Unwavering Swagger

Posted on Fri, 05/02/2014 - 09:49

Push aside the user stories, contracts, and legalities. When push comes to shove, the developer delivers the goods. In my mind, there is huge risk to a project with the role of a developer. Let's be clear though. Every project has risks. Every project has some complexity behind it. What this means is that there is a dark art to the design decisions made by the developer. I've never seen a client accurately define what content types or modules need to be installed. Again, if they were that educated about what needed to be done, they wouldn't be paying you to do it. The developer must learn

development drupal people

The role of the noob

Posted on Wed, 04/23/2014 - 10:03

Peter Nixey describes good developers as both technology proficient and hard working in his blog post. His concept of "simplicity" is worth noting. I highly encourage developers to create code that limits complexity. But, there is an even more important aspect of complexity: usability.Simplicity and excellence are most reliably attained by starting with something, anything, that gets the job done and reworking back from that point.Enter the noob. Every project should have someone in this role. Technologically detached. Familiar with project goals, but does not look at one line of code. No

development drupal people

Migration Tips and Tricks

Posted on Wed, 04/09/2014 - 14:42

The Migrate module is, hands down, the defacto way to migrate content in Drupal. The only knock against it, is the learning curve. All good things come to those who take the time and learn it. I have summarized some tips and tricks I have learned. Thank you to Mike Ryan and Alex Ward for helping me get up to speed. Drupal's Migrate module is a code-centric approach to migration. As such, I highly recommend leveraging Drush during development. Here are some tips I have used, some of which require Drush to be installed. 1. drush mreg Quick and dirty way to register new Migration classes after


Towards organizational efficacy

Posted on Wed, 11/20/2013 - 09:48

As organizations evolve, traditional metrics and philosophies are being thrown out the window to further organizations. Such factors include efficacy, employee satisfaction/ownership, innovation, etc. I offer no beneficial contribution to this discussion, short of agreeing in principle with these efforts. However, I point you in the direction of two things I have found to be relevant: 1. Blog post from Github: Very limited management, remote employees, rapid change and growth. Read on... 2. Rework book by 37 signals:



Posted on Wed, 11/13/2013 - 15:47

Personally, I love bagels. The pinnacle of all bagels is the toasted everything bagel with plain cream cheese. I reserve the right to update this over time, but let this serve as the Bergstein Metrics of Bagelology. 1. Seeding Amount I've seen bagels under seeded, but I have also seen bagels way over seeded (see: Panera and Dunkin Donuts). Seeding is critical to the flavor, don't blow it folks. 2. Slicing Equality A clear sign of unprofessionalism is the equality of the bagel slices. No bagel deserves this discrimination. It's got to be ballpark 50/50. You start seeing some major issues with

Mediated web file content management

Posted on Thu, 10/31/2013 - 11:06

This is a topic I have grown all too familiar with, as this is my thesis topic for my master's degree. I thought I'd share some basics to set the stage in this area of work. Background Users upload files as content to web-based systems. Think of Facebook and how user's upload images and/or videos to share with friends. The key concept is around the notion of sharing. What is appropriate file sharing (anonymous access, authenticated access, membership-based access)? What is not appropriate sharing? This question changes based on application-level policy, meaning it's difficult to find a one

development drupal