If anyone else still is having issues with the hack on his/her WP blog, please check out the link above for some helpful tips to clear things up.  In my particular case I had an administrator account injected into my WP database and the nasty code was inserted into my footer.php file.  Luckily, that was it.

So apologies for temporary annoyances and any possible malware serving.

PS: If you are a WP user, double-check your wpconfig.php file permissions.  Apparently, a lot of folks (cough, cough, mine) had loose permissions on it.

I know the attendance was not what some people might have hoped, but I think it wasn’t bad considering that Capital Flash Camp was announced just a little over a month ago.  The DC area’s Flex community is not as large as other places (Flash Camp SF was the same day and heavily attended, but it’s a big hub for the community) so it’s worthwhile whenever we get together.

As an aside, the Naval Heritage Center is a great place to check out if you’re doing the tourist thing in DC.

So presentations…

Terry Ryan, Keynote: Terry is a platform evangelist from Adobe and gave an overview of all the features available in Flash Builder, Flash Catalyst, and CF Builder and discussed workflows between the three.  Even with all of the new presos on Flex 4, there was still plenty to learn (I had no idea about the two-way binding in Flex 4).

Jeff Tapper, Flex 4 for Flex 3 Developers: As always, Jeff gave a great preso between his straightforward-yet-humorous delivery and his ability to explain the why’s behind the how’s and what’s.

Christian Saylor, The Art of Storytelling: Really enjoyed how Christian (Anti-Chris) relating storytelling to designing applications and more importantly his take on how and why some applications and products take hold of us and change our ways, while others don’t.

Carl Smith, It’s a Matter of Trust: Carl’s presentation was a hilarious overview about the different ways that trust affects how we interact with the world in general and with technology in particular.  I had the pleasure of chatting with Carl, owner of nGen Works, and he’s got a brilliant perspective on what makes for good applications.  Ask him about usability if you get a chance to talk to him.

Adnaan Ahmad, Introduction to Flash Catalyst: It was good to actually get a demo of Flash Catalyst and I wish Adnaan had gotten more time to go more in depth with it.  Nice job though.

Dave Watts, Using Flash Builder 4’s Data-Centric Development with ColdFusion 9: I’m not a CF person and so a bit of the preso was lost on me, but it seems that there are a bunch of niceties for connecting to various data sources and wiring them up to your Flex apps.

Chris Scott, Swiz Framework – Brutally simple micro-architecture for Rich Internet Application development with Adobe Flex: I personally got a ton out of Chris’s talk since I’m using Swiz for this first time at the current gig. The Swiz team hasn’t quite caught up with their documentation, so it was good to have Chris talk about various features and how to apply them.

For anyone interested, here is my preso and the code from my examples. Not much is different than my 360|Flex preso and I left out code that I didn’t go over this time around.

Slides (1.1MB)

Greenthreading MSNBC Data Set (ZIP, 2.6MB)

Overall, it was a great day.

\m/\m/

If you can, please join us tomorrow in the District.  :)

As promised I have updated slides and code here:

Slides (PDF, 1.1MB)

Greenthreading MSNBC Data Set Code (3MB)

Multithreading Code (5.4MB)

A huge thanks to everyone who showed up.  Really appreciate all the comments and the chance to give this presentation. I want to reiterate that what I am presenting is just a package of the great work of other people, namely Charlie Hubbard, whose library and great series of articles I use for this.

Again I am just really glad I got a chance to talk to you guys and present you with something that I hope you will find useful.

Please feel free me to ping me with comments, suggestions, or just to say hello.

\m/\m/

360FLEX – THE SPEAKERS – HUYEN TUE DAO

Say that you have an enhancement that can be made to speedup some part of an application.
And say that you know how much runtime you can save with the enhancement.
And say that you know what fraction of the total runtime that part of the application takes up.
Then you can determine how much you will speedup the application as a whole by making that enhancement.

Why is this valuable?

You might be in a situation where you have to justify time and effort spent (and fancy formulas help to dazzle the crowd).
You might have two different enhancements or changes that could be made but only have time to do one. Which should you choose?
You might just want to know how badass your idea really is.

So, I present to you Amdahl’s Law:

Formulas borrowed lovingly from Hennessy + Patterson’s Computer Architecture: A Quantitative Approach

You could use this formula for any other performance metric.  For example, if you were more concerned with memory consumption, the formulas still hold: just replace “runtime” with “memory use” and “speedup” with “memory reduction.”

Hope you find this helpful someday.  I’ll try to keep so many equations out of the next post.

I tried to find a way to explain the problem without getting all bogged down in tech details, so I tried to explain it like this:

Mom, your computer has two kinds of memory. One is called its “main memory,” and the other is called the “hard drive.” They both store information, but they’re pretty different. Think of your main memory as your kitchen counter. When you’re cooking you do your actual work there. You can put some stuff on the counter but not a lot, but when you need stuff on hand to grab quickly you put it there. Also in general you can’t leave stuff on your counter forever. You only use your kitchen counter when you’re cooking. Think of the hard drive as your refrigerator. Its for long term storage. You can put a lot more stuff in there, but it takes a little more time to go over, open the door, look for what you need (especially say if it’s hiding behind the milk), and bring it over to the counter where you’re actually doing stuff.

Your main memory.
Omelet fixings not included.

Your hard disk.
Need to defrag the eggs.

So when we upgraded your “main memory” we were giving you a bigger counter so you’d have more space to fit more stuff. That helps a lot if you’re making something really complicated or just doing a lot of cooking. But I forgot that you like to take a lot of photographs. Think of it as how you like to grow lots of your own veggies at home which you then store in the fridge. So after putting so many homegrown tomatoes in the fridge you basically ran out of fridge space (ran out of “hard drive” space). So what we need to do is get you a bigger refrigerator or at least an extra, maybe smaller one to hold just your veggies or drinks or something like that.

My mom really seemed to like and understand that pretty well. I had originally gone with long-term vs. short-term memory, but our family is all about the food-service business so I thought maybe going-with-what-you-know would help.

I suppose if you want to get really into it you could compare a cutting board to a cache, but maybe that’s a little too nerdy. O.o

I hope if you ever need ‘xplain to your mom or another loved one that this helps a little.

Now excuse me, I think I might have put that zip file I need behind the milk.

GitX is very similar to gitk, the Unix-based repository browser that comes as part of the git package.  Being an open source project, it has that nice price tag of $0.  It has a nice browser with a cute timeline-type representation of the repository history (just like gitk) as well as a flexible interface for staging commits.  The diff functionality is clear and easy. But that’s pretty much it.  You have to already have a repository setup locally, and you can only commit.  No pushes, pulls.  You can branch but no tags.

Gity by Mac Endeavor is less a repository browser and more of a straight-up gui for most git functionality.  Branches, tags, and remotes are listed on the left hand side, and the main page basically lists files in the currently repository.  There are toggles for untracked files, modified files, and staged files.  Commits are a simple dialog. The implementation of these features feels lacking compared to that of GitX.  However, Gity rocks when it comes to all the functionality that GitX omits.  You can clone repositories, create new remotes, fetch, push, pull, branch, tag, configure git, and other advanced functionality that flies over the head of this n00b. UPDATE Thanks to Aaron @ Mac Endeavor for giving some heads up in the comments on updates to Gity history and diff functionality.

Is one better than the other?  In my opinion, nope. I use Gitx daily.  I use Gity every now and again.  Gitx does what little it does very well.  Gity is loaded with features. GitX is free. Gity is $18 (after a 20 repo refresh trial).  Do I think that Gity is worth $18?  Eh.  I would pay $18 if GitX and Gity merged to have GitX’s interface with all of Gity’s extra functionality.  THAT would be epic, and I know people before me have said the same.  On a related note, anyone else notice how strangely similar their logos are?  Hm… *speculate, speculate*

But fanciful, wistful fantasies of applications-not-yet-written aside, if you do end up getting both GitX and Gity, you’ll be in good shape to getting going with your git-ting.

If anyone has any suggestions or questions still or ideas of whatever further extensions or clarifications they would like to see, please feel free to email me and hope to see you in San Jose!

Then tonight as I’m tidying up some code for my side project I see this tweet by Ben Clinkinbeard noting that adding a trace statement increased a loop’s runtime by 1 second.  So following Larson’s article with a little help from flexexamples.com for setting up a flex-config.xml file, I set conditional compiling for every single trace statement and then compiled a new release build.

Wow.  Just wow.  We’re talking seconds shaved off loading batches of images.  And I’m frequently loading these small batches of images so the additional time was just piling up.

I feel incredibly duh-I-should-have-known-that-I-am-such-a-noob.

But hey, live and learn, right?  And I apologize to folks following me on Twitter for the spam and gratuitous face-palming.

Update: Dave Rosenfeld informed me via Twitter that trace actually initiates some disk I/O.  No wonder.