Monday, December 31, 2012
Thursday, October 11, 2012
Usage, behavior and patterns
Unhandled, thrown and caught exceptions
What’s getting in the way?
PreEmptive Solutions and Application Analytics
Sunday, October 7, 2012
Security and privacy concerns identified as most common obstacle to implementing application analytics
Half of all respondents identified security and privacy - a 20% higher response rate than the next two closest obstacles e.g. lack of expertise and general quality concerns).
Privacy and Security and PreEmptive Analytics
- Development teams own their own data. PreEmptive asks for no rights to aggregate, inspect or resell your data.
- A two-level opt-in switch is included ensuring user opt-in to transmit runtime data from both regular usage AND application exceptions. The logic itself can be injected post-build for .Net and Java and can always be defined by the development organization.
- All data is, by default, encrypted on the wire.
- Device ID's (if they are collected at all) are hashed before they are transmitted.
- Tamper-detection and defense can be used to detect and defend against any attempt to alter or redirect runtime data transmission.
- Obfuscation can be used to obscure inspection by third parties of what is being collected and transmitted.
- Unique keys identify both the organization and the application source for data.
Wednesday, October 3, 2012
The hallmarks of a successful DevOps organization (aka “the kick#@s crew”)
Friday, June 15, 2012
- · Which “ad” was displayed in which page and
- · What action (if any) users take with each flavor of ad.
Sunday, May 13, 2012
So why should anyone but PreEmptive care?
Second, when a hacked app also relies on external services (hosting, bandwidth, human support), these expenses are typically still borne by the true app developers.
Third, hacked apps cannot be trusted to be updated or to be as functionally reliable as the original. To the extent that poorly performing apps can cause damage to their users – this can become a public and personal safety hazard. (GPS, financial, etc. apps are often “mission critical).
Fourth, all of the privacy and security practices and ethical guidelines that legitimate software companies follow can be expected to be thrown out the door. Tracking, identity theft, hijacking of devices may all begin with a hacked/counterfeited app.
Pirated/look-alike/counterfeit apps may well be the single most unrecognized risk to consumers, children, and our economy – not just because of the lost revenue, but because of our dependence on this software (think about counterfeit cancer drugs and car parts as an analogy) and the intimate place these apps occupy on all of our devices.
Anarchy or organized attack?
Sunday, May 6, 2012
Wednesday, May 2, 2012
Thursday, April 26, 2012
Question: What is the application analog to yoga?
Answer: Feedback driven development and automated operational response to runtime behaviors.
How they line up…
Physical, mental and spiritual well being
User experience, software quality and development ROI
What it is we’re trying to get right (fine tune)
An organized approach to restoring balance
ALM & DevOps
The dimension of the practice focused on the real world.
Patterns and practices
Pose[s] or pattern(s) you can hold/implement with ease
Monday, April 16, 2012
Tuesday, February 14, 2012
To quote from the abstract, “[Kahneman’s] new insight has profound implications for economics, public policy -- and our own self-awareness” – but why stop there? Let’s add “user experience” (UX) on the human front and “ALM and SDLC” on the app front. This topic is going to be kind of long, so I’m going to break up UX and ALM and SDLC into two installments; let’s do UX first.
[…] This applies to laypeople thinking about their own happiness, and it applies to scholars thinking about happiness, because it turns out we're just as messed up as anybody else is. The first of these traps is a reluctance to admit complexity. It turns out that the word "happiness" is just not a useful word anymore, because we apply it to too many different things. I think there is one particular meaning to which we might restrict it, but by and large, this is something that we'll have to give up and we'll have to adopt the more complicated view of what well-being is. The second trap is a confusion between experience and memory; basically, it's between being happy in your life, and being happy about your life or happy with your life. And those are two very different concepts, and they're both lumped in the notion of happiness. And the third is the focusing illusion, and it's the unfortunate fact that we can't think about any circumstance that affects well-being without distorting its importance.
Now, here it is after I have made my mangling substitutions:
Everybody talks about User Experience these days. […] There is a huge wave of interest in User Experience, among researchers. There is a lot of User Experience coaching. Everybody would like to make people have better experiences. But in spite of all this flood of work, there are several cognitive traps that sort of make it almost impossible to think straight about User Experience.
Now this is just the opening of the lecture and neither version really proves anything – he’s just setting the stage – let’s look at two examples he cites to make his (and my) point.
…but it works the other way too…
He retells a well-documented study of two patients undergoing colonoscopies; patient B was subjected to a particularly painful exam that he verified by reporting on his pain every few minutes. BUT the last few minutes of his exam had no pain whatsoever. Patient A was subjected to a less painful exam – BUT their exam had the moderate-level pain throughout their relatively shorter and less extreme exam. Clearly, patient B suffered more -- their colonoscopies were longer, and every minute of pain that patient A had, patient B had, and more.
…And now Kahneman delivers the punch line; "The surprise is that Patient A had a much worse memory of the colonoscopy than Patient B.” The stories of the colonoscopies were different, and because a very critical part of the story is how it ends. It was much worse for patient A than for patient B in memory. “What defines a story are changes, significant moments and endings. Endings are very, very important and, in this case, the ending dominated.”
When something goes wrong for your user, the story isn’t over unless you let it be over. If you can get back to your user and fix or at least address their issue in some timely fashion – their memory (of their user experience) can be rehabilitated just as dramatically as it was decimated in the previous example.
“We don’t choose between [user] experiences, we choose between memories of [user] experiences. Even when we think about the future, we don’t think of our future normally as [user] experiences. We think of our future as anticipated memories.”
Kahneman’s independent research offers some of the strongest evidence yet on the importance (criticality) of using stories in operations and support, app design, user training, and in product management.
Wednesday, February 8, 2012
Spoiler alert, the answer involves butterflies and trees.
A: Of course, the answer is No. Sound is vibration, transmitted to our senses and recognized as sound only at our nerve centers – If there be no ears to hear, there be no sound at all.
Q: BUT, when a tree falls in a lonely forest, and no animal is nearby – does it matter?
A: Yes and its impact goes beyond the sleeping caterpillar in its cocoon = Consider the Butterfly effect where a small change at one place can result in large differences somewhere else (the name comes from the example of a hurricane's formation being dependent on whether or not a distant butterfly had flapped its wings several weeks before).
Q: When an app crashes in the wild and no developer is nearby, does it create a work item?
A: Sadly, the answer is No. Work items are specific tasks, transmitted to a dev organization and recognized as a work item within an IDE like Visual Studio. If there be no IDEs, there be no work items.
Q: BUT, when an app crashes in the wild and no developer is nearby – does it matter?
A: Yes and its impact goes beyond the individual user inside your app = consider the operational, reputational and social implications of a crushed user and the impact that a small incident in production can have.
A production incident can result in massive user defections, cratered development ROI and operational failure. (Don’t make me go into “for the want of a nail…”)
The material distinction between the hurricane and the “operations storm” is that while we can only forecast the weather, with the right information, development (dare I say “devOps”?) can effect operations through AGILE practices.
A: Of course, it’s the egg. Just ask the dinosaur back in the Triassic Period. The question as to which came first, the chicken egg or the chicken – well that’s a metaphysical question and has no place in a thinly veiled software blog like mine.
Q: Which came first, application development or operations?
A: Of course, it’s application development. Just ask the original time sharing providers back in the 60’s. The question as to which came first, the "development practices that are responsive to operational feedback" or operations is, in fact, one that I’m prepared to answer (as opposed to that chicken/egg deal).
Most applications today are deployed like the proverbial tree in the lonely forest – making no noise (because there are no developers around to listen) but whose crashes often reverberate across operations and then hit development like a hurricane.
Application Analytics is the emerging discipline plus supporting technologies specifically designed to connect application adoption, user behavior and production incidents to development practices, quality and impact.
Application Analytics is the evolutionary trigger that moves “the application” from the Triassic Period into modern times where cloud, mobile, web services and other forces are transforming our ecosystem.
If application analytics isn’t a part of your development process, well…. You just may end up in a mud pit with the rest of the dinosaurs.
Monday, January 9, 2012
- Who the F#$! is behind this? (and please let me meet them one day)
- How did they do this? (and is there something I could have done to prevent it?)
- What can I do about it? (and how much of my time is this going to suck up?)
- Is this a common problem (if so, why haven’t I heard about this before?)
- Why did they do this? (they don’t show ads and the apps are free)
- What other apps does this publisher have? (and are they also stolen?)
- And do I tell my wife? (because she is going to be even more pissed than me)
- music and video library
- phone identity and
- data services
- ► October (3)
- ► June (2)
- ► May (3)
- ► April (2)
- ► February (2)
- ► 2011 (10)