In Part 1, I covered how you earn trust from the client, and set the stage for how you start to fix a large pile of rubbish; a seriously broken piece of Flex software. Â While there are 5 aspects to fixing it using the 5 P’s: Programming, Prowess, Politics, Positivity, and Patience; the Programming one is large, so here is the second part.
Blog
-
Consulting Chronicles #2: Fixing a Pile of Rubbish – Part 1
Introduction
A lot of consulting revolves around fixing other peoples code. Sometimes this is pretty straightforward. Sometimes you perceive it as an unfixable disaster. Other times, not only is it a disaster, but you could be put into a situation where you are perceived as taking advantage of the situation when in fact you’re attempting to fix it.
Disaster recovery in consulting is solved by using the 5 P’s: Programming, Prowess, Politics, Positivity, and Patience.
Even if you aren’t a consultant, the tactics below should help you fix the un-fixable.
-
AIR 2 Chat Server & Client
Skip to Code & Application Install
Preface
While waiting for my current contract to get renewed + over the Thanksgiving holidays, I’ve been playing around with AIR 2. Â To me, the coolest new feature is a new class called “ServerSocket“. Â It’s like the existing Socket class, except it can “listen” for incoming Socket connections. Â That’s right, you can make an AIR application that is a server application AND optionally run the sucka via command line instead of making a GUI for it. Â How frikin’ cool is that!?
-
Good Memory Management When Using PureMVC
Preface
There are a lot of good articles already written & screen casts about memory management in Flash Player. Â I encourage you to read them first before reading the below. Â I cover memory management in a large application using a PureMVC architecture, typically on top of Flex.
(more…)