Updated introduction

jeffremer · Apr 16, 2011 · 773130d · 773130d
1 parent d368b00
commit 773130d
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/_posts/2011-04-15-fliteapp.md b/_posts/2011-04-15-fliteapp.md
@@ -19,7 +19,7 @@ Our Studios were designed for click-and-build users. They were designed around t
 
 In Flite we create components, canvases, campaigns, placements.  We manage assets and feeds.  Widgetbox is agnostic about this - it's all just registrations, instances, and data.  I think that our product offering has changed overnight and our tools are still designed for someone who doesn't know how to code or automate at the near total expense of those who do.
 
-Our web-based studios are very nice for what they are, but a text editor is better.
+Our web-based studios are very nice for what they are, but a text editor is better - at least for me.
 
 I've outlined what I see as a loose plan for my ideal development cycle as a developer who would create or instantiate Flite products.