Summersault Blog

Earlier this year, I made some notable contributions to various open-source projects, including:

• Tim Bunce, the author of Perl’s DBI asked me to be a committer on the DBIx::HA project, a high-availability/load-balancing Perl module.
• I uploaded a new release of CGI::Session, version 4.30. As the official maintainer of the module, I worked closely with Ron Savage who did most of the release work. Summersault will likely take advantage of these improvements in the future.
• Multiple people gave me praise for my help with the Darcs 2 release. One person wrote, “Mark Stosberg was an unsung hero of the darcs-2 project for diligently triaging and following-up on hundreds of bug tracker tickets. His quality-assurance work (including setting up automated buildbot tests) is an important reason that darcs-2 is much less buggy.” By patch count, I’ve committed the third most patches to the project due to numerous documentation and test suite improvements.

These are just some of the ways that Summersault staff participate in the online community and in the open-source software movement.

Sometimes I have to remind myself that just because we want to try to be all things to our clients doesn’t mean that we can be. Of course, for any given project, the conversation about what’s possible, and on what timeline, and at what cost is never a simple one. The bigger the project, the more complex that conversation becomes. It can be easy to over-promise and under-deliver if you’re not extremely careful.

Several years ago, we began using parts of the “Extreme Programming (XP)” software engineering paradigm in our development process, with the goal of improving our time estimates, better understanding what we were able to deliver to our clients and when. I’ve not found any part of XP to be more useful than the way it describes the interactions between these four variables:
Read the rest of this entry »

Ten reasons to work at Summersault:

1. Our mission is to build and sustain communities using the technologies of the Internet. Who wouldn’t want to be a part of that?
2. We offer flexible scheduling, so you can arrange your work around your life, instead of arranging your life around your work.
3. We’re always working with interesting tools and technologies.
4. We pay 100% of health insurance for full-time staff and competitive premiums for spouses and dependents, including vision and dental benefits.
5. In-depth performance reviews provide you with concrete professional goals and feedback on your successes.
6. We have a volunteer and community service program that compensates you for being active in the community.
7. Our employee wellness program helps you to stay healthy.
8. We offer paid vacation time, up to four weeks per year.
9. We regularly recognize outstanding contributions that our staff make, in the office, to our clients, and out in the world.
10. We’re locally owned, and we give back to the community.

Interested? Check out our current openings.

Today I uploaded the first release of Titanium, a web application framework. This project really began about eight years ago, with first release of CGI::Application.

CGI::Application was and is a great foundation for web applications and has always been well defined with a small scope for what it would provide in terms of a framework. Because of this it was able to mature and stabilize with few bugs ever reported and always provided great performance because of its small size. It grew in popularity, and over 50 CGI::Application plugins were released.

The contributed plugins were a great gift back to the community from the many users who made them, but for newcomers, the choices could be daunting. They meant getting started with CGI::Application for an application of any size often meant wading through the many options for plugins, yet often coming to the same conclusions about which ones to choose.

Read the rest of this entry »

I recently discovered some new source code control workflows that are possible with darcs.

Just after I record a patch in my local repository, I often feel compelled to review it one more time before pushing into the central repo. “Did I record changes in just the files I meant to? And even within specific files, did I include just the changes I meant to?” With darcs, this check is easily done
after recording with darcs changes --interactive --last 1 or just darcs changes -i --last 1, for short. They key part here is --interactive which launches darcs in interactive mode.

I press “x” to view the list of files affected, or “p” if I want to review a kind of “diff” in a pager, and of course “?” if I need help to remember what the options are. Very handy!

Read the rest of this entry »

Content that you create for your website is critical, and the way that text is presented is equally as important. Read the rest of this entry »

A friend recently noted that 4 of the 5 web-based applications he uses on a regular basis to manage his life are officially still in “beta” status. While I think this has become a fairly standard practice for many web application providers, I hope it’s one that we still treat with some healthy skepticism and concern.

At Summersault, when we develop software applications, beta is certainly one of the stages that the software goes through, but it’s not a stage we would ever turn the public loose on. Generally speaking, here are the stages of our software life-cycle:
Read the rest of this entry »

Just today, we’ve received two reports of our clients getting mailings from organizations claiming that payment is needed in order to maintain or renew services related their hosting account or domain, and in both cases, the mailing was just a scam. These mailings often come in the format of an official order form that appears to be important and time-sensitive, and so it scares the unsuspecting domain owner into sending a check rather than risk losing their website.

We’ve written here before about the horrors of domain management on the Internet, but this is a particularly troublesome practice, and adds a whole other layer of complexity and hassle to an already difficult and complex system. In another recent case, one of our customers did have their website go offline briefly because they’d sent payment to the wrong organization and ignored the notices from the real domain authority - yikes! Here are a few tips to avoid being swindled by these notices:
Read the rest of this entry »

I recently found a neat little application that has been useful both at work and in my at-home computing. It is called Prism, and what it does is allow you to run your favorite web applications (Remember the Milk, Facebook, Google Calendar, etc.) as if they were desktop applications. Because it was built on the Firefox engine, it will run any web applications you can run in your Firefox browser.
Read the rest of this entry »

I’ve been waiting for a while now to see what Google was going to do with their acquisition of JotSpot, the collaborative wiki site that a number of non-profit organizations I’m involved in has used to organize our internal information. In my opinion, the long wait was a big risk to take on Google’s part…I used to send people to JotSpot all the time. when Google acquired it and stopped accepting new accounts, I still sent people there, saying “I’m sure it will reopen soon, it’s worth it.” Eventually I stopped sending people there at all, and encouraged them to use other tools or to go to the trouble to set up their own intranet with software like Mediawiki, the tool that powers Wikipedia.

Well, as of today, I’m pretty sure I know where to send people for creating free, powerful internal websites: Google Sites, the new incarnation of what was JotSpot.
Read the rest of this entry »