blog.mattgauger.com

Web414 Feb 11, 2010

Posted: 11 February 2010

These are my notes from the February 2010 Web414 meeting. I wrote them in Markdown as the meeting progressed, so there’s not a whole lot of explanation or context.

Part 1: Workflow

What do you use for bug tracking?

Mantis, Trac, Bugzilla, Pivotal Tracker, Intervals

Hacking OpenAtrium case tracker to support bug tracking

What do photographers use? (Photographer Workflow)

• Lightroom, Photoscape (John December)
• The DAM book: thedambook.com

Bandwidth, backups

• There isn’t enough upload bandwidth to mirror all your content if you have a lot of data.
• Everyone sign up for Google’s fiber program.
• Amazon S3(Jungle Disk), Dropbox, Carbonite.

Then things went like this:

GIT GIT GIT GIT GIT GIT GIT Mercurial Microsoft GIT

IDEs:

• Eclipse/Aptana: No longer supports PHP ** Eclipse just got git support
• BBEdit
• Netbeans has some PHP support
• Textmate users? Quite a few.

Time trackers:

• Harvest
• Intervals
• MacFreelance or iRachet.

Batch processing / hourly jobs:

Do all of your photoshop tasks for different projects at once. Who makes that part of their workflow? 5 Getting Things Done: lump actions together

Pomodoro

Study technique. Way of focusing.

File transfer:

Replacement for Cyberduck?

• Transmit.app: costs money but it is included in Coda
• Filezilla
• Flow.app
• FireFTP - Firefox plugin

Customer Relation Managements

• Highrise - Manages people
• Sugar CRM
• CiviCRM
• Kevron is building CRM into their OpenAtrium project.
• Salesforce sucks!

Part 2: Frameworks versus CMSes

A web application framework has some things written, but things like delivering web pages is up to the coder. -> An incomplete web application, a framework that you hang your business logic on.

Arlen: “The future of the web is in frameworks, not in CMSes.”

• Every CMS does things its own way. “one size fits all.”

Arlen: ”I’m fighting the CMS. The CMS has a way it wants to do things. I have to write the business logic in such a way that the CMS can do it. Every CMS brings in POV.”

The big three of CMSes:

• Drupal
• Joomla
• Wordpress

Example web app frameworks: PHP:

• CakePHP
• Zend
• CodeIgniter (behind ExpressionEngine)

Other languages:

• Ruby on Rails for the Ruby language.
• Django for Python
• Catalyst for Perl
• Seaside for Smalltalk
• Lift for Scala.
• ASP.NET MVC or .NET Webforms

Derek: “Are we arguing the semantic difference between being a developer and being an integrator?”

[ Discussion on integration and its worth. I’m not going to even try to record it all here. ]

Arlen: ”I’m worth more as a developer than an integrator.”

Steve Kleibel: “It’s about solving problems and delivering solutions. And most people don’t care about what’s going on under the cover.”

Curtis: “Most of the time it is about how fast can I get this up and running? I know that Drupal/Joomla/Wordpress are well tested and quick to set up.”

Arlen: “I think the future in web developers is in frameworks.”

Kevron: “He said bit-twiddling. That was amazing.”