I really liked it, and will borrow the “bulleted list” of characteristics that I will work towards myself…

• Mature engineers seek out constructive criticism of their designs.
• Mature engineers understand the non-technical areas of how they are perceived.
• Mature engineers do not shy away from making estimates, and are always trying to get better at it.
• Mature engineers have an innate sense of anticipation, even if they don’t know they do.
• Mature engineers understand that not all of their projects are filled with rockstar-on-stage work.
• Mature engineers lift the skills and expertise of those around them.
• Mature engineers make their trade-offs explicit when making judgements and decisions.
• Mature engineers don’t practice CYAE (“Cover Your Ass Engineering”).
• Mature engineers are empathetic.
• They don’t make empty complaints.
• Mature engineers are aware of cognitive biases.

This seems like a good list of ideals to work towards in the new year.

All about HA planning

29% of DataCenter outages caused by UPS failures - point: some defenses create their own failure modes

If you solve for Datacenter-sized outages, the ‘little stuff’ is mostly taken care of

Keynote: Performance of Web vs Apps

Apps are trending to have more impact/viewship/etc than the web

Fragmentism is a scary future with Apps

“Pushing Pixels” (i.e. highly graphical apps) seems to be best served by Apps right now

Responsiveness is very compelling when considering your choice

App lifecycle (approval, etc) is MUCH SLOWER than Web

“Conditional Tier Rendering” – use Node.js to choose client/server rendering

In many scenarios, Web seems to have the advantage right now

Keynote: [Political|Commercial] [Threats|Opportunities] for Faster & Stronger Web
(Union Square Ventures)

Ops as viewed by Investors: “Speed is a feature”. Invest in it.

Why has web been so successful:

• Supportive Legislation
• Decentralized Internet
• Open Standards

Now (+ Possible Future)

• Restrictive Legislation
• Walled Gardens
• Controlled Internet

Lame claim by ISPs: “We haven’t invested enough in infrastructure, so therefore we should be able to control what crosses it.” >:-|

App: No “View Source”, No Linking

Historically Recognized Patterns in Technological Adoption: ~20 years in there’s a temporary crash while the world adapts to a structure of Networks over the older Hierarchies

Combat the threats to the internet:

• Engage (politically)
• Build!

[? slashawesome.net ?]

Keynote: Lightning Talks

Intel – Agile Application Performance Management

SNOOZE!!

Akamai – Akamai Internet Observatory

Basically, they are opening up some subsets of their data to be analyzed by the ‘open data’ community.

Example: in 60 seconds, gather 1.3 BILLION log lines

Their data should give a view of 20-30% of world internet usage

http://www.akamai.io

Compuware – UX Management

SNOOZE

Citrix – Blah blah Network Utility pitch…

SNOOZE

GoDaddy – Blah blah

Unfortunately, it seems that misogyny is a point of company pride for them.

Lightning Demos

YSlow

• now has a cmd-line version
• now open-source
• new URL: yslow.org

integrates with PhantomJS; this can then integrate with Continuous Integration tools!!!

Chrome

about://tracing

you can see low-level chrome processing info

(can help you speed up a site)

“CrRenderMain” is the proc to keep an eye on

FYI, ~16ms is how often a redraw should happen for current refresh-rates
to see examples: jankfree.com

BrowserScope

Pretty cool tool to see actual API adherence from many browsers

Changing Culture and Being a Force for Awesome… – (Jesse Robbins)

“The right culture is a requirement for survival and success at web scale.”

Bad news: changing culture takes time

Jesse’s Rule: Don’t Fight Stupid, Make More Awesome

Changing Culture:

• start small, build trust & safety
• create champions
• use metrics to build confidence
• celebrate successes
• exploit compelling events

Hack for Change

• Starting Small
• small is safe
• call it an experiment
• Creating Champions
• get exec sponsors, start @ your boss
• give *everyone else* the credit
• give ‘special status’ (e.g. pins/shirts/hats/etc)

Metrics

• find KPI that supports change
• track & use that KPI ruthlessly
• first, use it to show value
• later, use it to show cost of lagging
• tell a story with your data, not just a number

Celebrate Success

• tell a powerful story
• always be positive about people and talk about how they
• overcame a problem
• NEVER about people who created a problem
• leave room for people to come to your side
• Exploit Compelling Events

just wait, it will happen
no “I told you so”, just “what do we do now?”

re: Permission - ”No” frequently means “I don’t know how to say Yes to you“: Use creativity to hack whatever the barriers are

Wisdom of the Crowd: Real User Measurement

• “RUM”
• Look into using BOTH of these: “window.performance” and “window.onerror”
• Google Analytics has been doing for ~1 year, you may already have the data!

Leveling Up – Take Your [Ops|Eng] Role to the Next Level

Work: “It’s not just *what* you do, it’s also *how* you do it.”

Decent talk, but I didn’t take many notes. Hopefully the slides will be put up later, but this blog post from the speaker covers a lot of the same ground: http://katemats.com/2012/05/29/rocking-your-job-leveling-up/

Logging as Event Streams – (Rackspace)

Logging meets the cloud

• many multi-tenant services
• many servers across many teams

Logging is an ‘Event Emitter’ (as realized when working with Node.js)

Structured Logging

• since 1995
• many producers, many consumers
• many programming languages

JSON
pretty much all languages can use it
can set up as newline terminated
*grep* works on it
can do hierarchical data (recommended: only go 1 level deep)

Message Tags / IDs

• Easy to search for strings (I.e. “AH02571″)
• Important for internal usage, and especially for Open Source

Ref: Zipkin: Uses 64bit integer as ID

Shipping Logs

• ALWAYS write to local disk first (ALWAYS!)
• svlogd (?)
• Scribe – Abandoned by Facebook
• Flume – Hadoop focused
• syslog – Solid contender, very robust

Chose Scribe

• does bulk log mv, can buffer / retry / etc

Graylog2

• opensource
• many imports
• indexes in to ElasticSearch
• use regex to build pre-fab notification sets

Log Data: You don’t need to keep it forever

Scalable System Ops – (Tumblr)

[Note: Lots of great info in this talk, but a lot was out of my experience. (Provisioning servers, etc.) Not gonna recreate it
here, but suggest anyone interested in provisioning to look for this talk.]

“Collins” – tool to help w/provisioning

Use a lot of Unix principles when building tools

[Note: By the afternoon I was super tired and worn out, so my notes got very terse, to the point that I will only sum up what I can about the talk.]

Down With the Fancy Pants

“Complex systems fail in complex ways.”

“Premature optimization is the root of all evil.”

Basically, this talk was a caution to critically look at your stack to see if you can reduce weaknesses by removing unproven technologies.

Solving IT Issues with Differential Diagnosis

The speaker talked about his success in adopting learnings from the medical community to apply Differential Diagnosis and the Hypothetico-
Deductive Model to IT problems.

Basically, he encourages us to use more scientific rigor when trying to find the root causes of system malfunctions.

Choose Your Own Adventure

This was a very fun talk, appropriately placed at the end of the conference.

Adam brought a long experience in Ops/SysAdmin/Dev to speak about a range of topics chosen by audience members yelling out their
preference from a list of choices.

Challenges to Cultural Change

These are slides to a talk that I didn’t attend, but this echo’s a bunch of good advice from Jesse Robbins’ Keynote presentation. I’m including it because it was well recieved: http://www.slideshare.net/lnxchk/challenges-to-cultural-change

EDIT: 28 June 2300h – light editing for formatting

Also, I didn’t properly charge my laptop, so I couldn’t take notes with that. It took me until 10AMish before I found a notebook for jotting down my notes, so the first couple are very incomplete. Mea culpa.

Keynote by Facebook:

I found the discussion of their new hire process very interesting: ”New Hire Cave” for 6 weeks w/Mentors and fixing bugs

They also had some interesting results with iteration, even when applied to the building of their datacenters and hardware.

Keynote by Google:

Prediction APIs, giving browser hints as to ‘normal’ or expected flows

“chrome://predictions” – Chrome 20+, can see url suggestion trees

Keynote – Lightning Demos:

http://webpagetest.org

• “page speed index” = how long until pixels rendered
• PageSpeed Insights (Google)
• render order vs load order
• public as of today
• can see “critical (render) path”

http://httparchive.org

• real-life data from ‘in the wild’
• free
• see trends
• based on WebPageTest.org

Keynote – “How Complex Systems Fail”

A.k.a. How Complex Systems DON’T Fail

(Speaker comes from medical background, but research translates to what we do in Ops)

We should be programming for resilience in addition to reliability

I.e. how the operations people can use/fix/tune our apps

Design for Resilience:

• support continuous maintenance
• reveal control to operators
• show the ‘lift points’ (heavy equip analogy)
• support mental simulation
• open objects/methods
• deep six “don’t touch me”‘s

Keynote – “Broadening the User Perspective”

historically web ops have concentrated on load-times

new metrics:

• when browser starts painting
• when full screen displayed
• when window becomes interactive
• “Web Timings” spec

“Beyond CDN” – (Akamai)

Major ISPs are peering networks, secondary networks have to pay to exchange/interchange data with main ISPs
Growth Expectations in the near future:

• First Mile (Site -> Interchanges) – 20X
• Last Mile (ISP -> End User) – 50X
• Middle Mile (Interchange -> Interchange) – only 6X – THIS IS GOING TO BE BOTTLENECK!

ISPs not motivated to invest in Middle Mile, cost center

Interesting Example: The two major Brazilian ISPs hate each other, routes via Miami for interchange

“Real Time at Twitter”

monolithic app ['monorail' ] -> JVM based SOA

1st problem: ops visibility

• was all in nagios & Ganglia
• difficult to change (not responsive)

solved: created visibility stack

• self-service timings infrastructure (w/a query language?)

then abstracted out network substrate

• started as local interfaces
• evolved to remote interface

“Zipkin” – github project; trace tool

“Iago” – github project; load generation tool

“Finagle” – github project; enabled much of their SOA

“Thrift” also used as common ‘language’ between services

They started by deploying new features ‘dark’, then slowly turned up usage

“Rollbacks: The Impossible Dream”

Entire concept based on transactional db model

No One Tests: Disaster Recovery / Rollback

Preventative Design:

• Increased Resilience – less need for rollback
• DevOps – better integration b/w engineers and ops
• Small, Iterative changes
• Accept that sometimes failure happens
• TEST! – There are only a *few* things that truly “can’t be tested”
• “Assumption is the mother of all fuckups”

Ops Mythologies (“it can’t be done”) come from scar tissue – kill your myths!

“Using Node.js to Improve the Performance of Mobile Apps and Mobile Web”

radio waves suck! – vs fiber/copper

high latency requests b/c of physical movement/constraints

client-side MVC sucks

maybe we should emulate the Google homepage, which ‘barfs’ the whole site out quickly

Interesting: mobile networks try to ‘guarantee’ delivery of data once it’s actually made it to the mobile network itself

Rendering HTML vs rendering JSON have tradeoffs to be considered for mobile

“Mojito” for rendering page fragments via Node.js

“Stability Patterns” – (Michael Nygard)

[Note: this was a subset of the book "Release It!" which everyone should just buy & read]

A killer test harness would be one that throws “Out-of-Spec” errors:

• E.g. Returns MP3 instead of XML when on XHR
• E.g. … many other evil considerations

“Time to First Tweet” – (Twitter)

Moving initial load from Client-Side Rendering -> Server-Side Rendering

Performance is highly contextual

Used “Navigation Timing API” – supported by IE9, FF7, Chrome

Represents most users, pulled data from small % of users

Because they are in the middle of a Rails -> JVM change, they have a multi-language templating solution

• Templating on Client: Mustache.js -> Hogan.js
• Templating on Server: Mustache.java
• (and another C++ implementation w/ Ruby bindings)

Migrating away from HashBang

Loading JS

• CommonJS and AMD
• decouple loading from execution
• enables multiple loading times: lazy, parallel, etc
• transparent to JS developers

Layering On pushState support

• want fast in-app navigation
• want to avoid full-page refreshes in modern browsers
• keeps simple index-ability
• Best of Both Worlds!

In Browser: on click; if has History API support then intercept the click and request link via XHR

On Server: if request is via XHR send just the partial, otherwise send whole HTML page (decorate)

Cut 95th percentile by 75%

Summary

Overall, it was a pretty good day.

I think the presentations I’ve seen were pretty good. The best and most polished presentations are on all the new front-end and/or client-side tooling and techniques. The (still strong but) weakest presentations seem to be around some of the back-end and server-side techniques. I guess my critique is the tone of these presentations: they seem to be saying “this is the way we’re going”, rather than coming from a position of “we’ve done this and it was successful because of X, Y, Z.”

I actually didn’t hate the exhibit hall for this conference. For the most part the vendors seem to be staffing with actual staff, and only about 30% are resorting to ‘booth babes’. (EdgeCast and Dyn seem to be the worst ‘booth babe’ offenders. I’m considering telling them tomorrow that they lose some credibility that way. I am also considering asking the GoDaddy staff “WTF is wrong with your CEO?”)

I’m looking forward to tomorrow, but I can tell I’m going to be a zombie once the
day is over.

PS: Too tired to format this mind dump right now… Will come back and fix it up in the next couple of days.

EDIT: Formatting mostly fixed on 28 June 2300h.

I went about casting a net on my Twitter account, and I already have two potential occupiers lined up. But, from that post I also received encouragement to scale this up and accept donations.

I’ve never done this before, but I signed up for an account on WePay. I am now accepting donations if anyone wants to add their support sending people to sit with the #OWS movement.

This blog post serves as a way of providing the social proof of who is behind the donation page. If you donate and you don’t like how your money got spent, I am the guy you’re going to come talk to.

So, if you want to help have your voice, as a part of the 99%, to be heard but you don’t have the time to spare, please consider donating.

At one point in my life, I was a volunteer Firefighter/EMT. During my time working in paramedicine, I learned a valuable concept: the pertinent negative.

Let’s say you’re examining someone who fell from a height. In your report you node that yes, they had a laceration on their hand. But it is also important to note that you examined them and found no evidence of any other broken limbs. Not noting your investigation into broken limbs could mean one of two things: either you didn’t check their limbs, or you did and found nothing of concern.

By noting the pertinent negative, you clear up that ambiguity.

I find this concept incredibly useful in software. Frequently, I need a pertinent negative to do my job well. (Did that script complete without errors, or did it not even run? In a report, a 0 entry tells me that the item did fit my search criteria and it had no requests. Etc.)

I have to say that this concept of pertinent negatives keenly reminds me of how important an ‘invention’ zero was.

I recently went to my second South by Southwest Interactive (SxSW or SxSWi) in Austin, TX. If you’re not familiar with the conference, it is a 5-day internet and technology subsection of the greater SXSW conference which also has Music and Film components.

SxSWi has a long history of being a great place for cutting-edge technology makers and creators to mingle and share ideas. I personally saw, felt, and benefited from this great tradition. However, people who have been attending the conference for more than 3 years say that it has changed substantially as its influence has been recognized, and there are continually growing populations of the ‘business-y’ (read ‘douchebag’) hangers-on: marketers, salespeople, and those I think of as ‘traders in idea derivatives’. (Luckily, for my part, I was able to find a tribe of people who are actually creative and engaged in what they do, so I was able to minimize my exposure to the unsavory, financially-motivated elements.)

But not fully. There are several blog posts I’m sure I could write about the interactions between ‘the Makers’ and ‘the Sellers’, but one aspect of our differences really calls out to me for comment: business cards.

Some people can be really, really intense about business cards. (Check out this guy.) In some business cultures, not treating the business card exchange with the proper respect can end up costing you potential partners.

My impression is that at SxSW, people think of business card dispensing as a quantity-over-quality proposition. Some members (with whom I am friends) of the “How Not to Be a Douchebag at SXSW” panel (2010, 2011) panel even give advanced warnings that there are people who approach business-card delivery in this manner.

The whole business card thing is so ripe for mockery that @scottyiseri and I created a fake ‘Angel Investment’ firm, just so we could give out the fake business cards you see at the top of the post. (I ended up dispensing these cards out to friends, so they could in turn use them as a way to avoid giving their actual information to someone who was being egregiously douche-y.)

But it wasn’t the blatant card-distributors that got to me, it was the nuanced ones. After one session, I ended up with a card from a recruiter from North Carolina, and another from a small-business efficiency consultant from New Jersey. These cards were handed to me while I was having actual, pertinent conversation about the session with the card-givers. Twenty minutes later in my hotel room I was tearing the cards up and throwing them away. I had zero need for these cards.

On the plane ride home I got to thinking about those cards. I realized that every single unwanted card that ended up in my possession was a symbol of laziness: my laziness in protecting my integrity. (And I’m pretty into my integrity.) If I have absolutely no interest in your business card, and have no intent of ever trying to contact you ever again, why accept the business card? (You may say ‘politeness’, but I don’t buy it, because any ‘good’ marketer will politely bully their way into your wallet if you give them the chance.)

Going forward I have a new resolution. I will no longer passively accept business cards, I will either actively accept (less likely) or actively reject (more likely) any business card that is offered to me.

Will you join me? (Why not?)

Both of the the Bit.ly referrers (like “forexmarket”) just resolves to this URL “www.plus500.com/SiteNotAvailable.aspx”.

It’s just a stupid banner page with a big GIF built to look like an actual web page.

What the fuck is the point? Yah, I was interested enough to investigate it, but only forensically… There is no way I would ever do any business with this place.

The other thing that frustrates me is that Bit.ly let the redirect through, even though they know it’s a spammy thing. (A couple of weeks ago when I first found these types of referrers, I tried to follow the link, but Bit.ly warned me about not-above-board behavior of the link. Why no longer?)

Also, the landing page is using Google Analytics. Does this mean all the good tools that those of us who aren’t devil-spawn are being used by they outright shitheads? I guess I know the answer, even if it does hit me right in my idealism.

For the past year or two I’ve had an ongoing side project where I post to the Twitter account @bman_countdown. It started out as just a simple countdown, but I realized I could use it as an opportunity to provide more information about the event, so I started to tack on links to relevant content on the BurningMan.com website.

Over time I’ve increased the functionality from being a static set of links, to mixing in the most recent blog post from the Burning Blog. (Actually, this functionality just went live today.)

This has been a great ‘toy’ project that I use to experiment with different technologies.

The Environment

For the first couple of iterations it was a Ruby script that I ran off of my ‘media server’ (a Mac Mini which I had set up as recommended by MacMiniColo). To emulate cron functionality, I used launchd to run the script once a day.

Predictably, this setup caused some hiccups in the continuity of the service: when my ISP service went out; when my router borked; when the hard drive failed; when I moved; etc. (Yay for providing non-mission-critical projects!)

Around the time of the 2010 Burning Man event, Twitter removed the ability to use Basic Auth, which is what the library I used relied upon. I decided the service could take a break right after the event while I figured out what I was going to do with it.

I had done some minor playing with Google AppEngine in Java, so I was familiar with the basic services GAE provides. (I love AppEngine’s first-class cron support. And the TaskQueue concept ecourages truly asynchronous and scalable design.) But, since this project is what I use to experiment with stuff, I figured I’d try out Python.

Meeting Python

First, I had to get up to speed on Python itself. So, I got the book Programming in Python 3. I studied several chapters of this book and did a couple of the ‘programming assignments’ (which I thought was a great idea), until I felt I was familiar enough with the language to take a poke at upgrading the countdown.

I came to realize that the process of developing in Python is so easy! (Even more so in GAE, as the development server environment that you get is great, and shit just works: just save the changes to the file and you can hit the page, and you get instant feedback.)

I know I’m a latecomer and I am treading dangerously close to Programming Language War territory here, but I have to say that I am entirely fed up with the edit/build/deploy cycle that leaks time and energy in Java projects. Do you realize that in big Java shops, there are engineers whose entire function is to iterate on the build process? Remember that whole “Google App Engine in Maven + IntelliJ” blog post that I made? In Python, the build-cycle-via-build-tool process doesn’t exist. Imagine a future where you don’t need to wrestle through Maven’s bullshit to get stuff done. I can see this future in Python, and it gives me tingles in my naughty bits!

Sure, I’ve got rose-colored glasses on here. I am a native speaker of high-protocol Java (my kingdom for a native “?” operator!), who is currently a tourist in a strange land speaking a stilted pidgin version of Python. Admittedly, I have an incomplete grasp on what the costs and benefits are when moving from a compiled language to an interpreted one. But it sure seems easier so far.

Future of Java

I was originally pulling for the Java ecosystem, whether that comes from a selfish (it’s where my bread gets buttered) or a philanthropic (because I’ve seen so much good Open Source stuff come out of it) point of view, I’m not sure. I was happy when some very smart people talked about ways that at least the JVM could stay relevant by embracing more dynamic languages built on top of it.

But then there was last weeks announcement that Mac OS X would deprecate support for Java. This generated a lot of excellent discussion. My favorite post both described why this is a death knell for Java, while also outlining a strategy for ensuring Java could continue to function (by breaking up it’s fairly monolithic API into discrete modules).

Alas, because of a very specific interaction I had, I fear Chris Adamson’s cogent post will probably be ignored by Oracle. Back when the news came out that Oracle was buying Sun and therefore Java and MySQL, I spoke to a friend of mine who worked for Oracle. I told him I didn’t care if Oracle owned Java and MySQL as long as they didn’t fuck it up. His response: “Don’t worry. We’ll fuck it up.”

The mere fact that I heard this kind of pessimism coming from an employee within Oracle makes me think Java will be viewed more and more as a legacy system in the months and years to come.

Not that I have a whole lot to hide nor do I wear a tinfoil hat, but every once in a while I like to do a personal audit of where my privacy could be (or is) getting invaded. So, I’ve been collecting informal data points about my experience with the ClipperCard, which is what leads to this post.

What They Expect

Here is my daily paper trail (all times are approximate):

• 0800: “tag on” an inbound #14 MUNI near Duboce & Mission
• 0810: “tag on” an outbound #47 MUNI near 11th & Mission
• 0840: “tag on” at the CalTrain station at 4th & King
• CalTrain conductor scans my ClipperCard on the 0844 Southbound train
• 0926: “tag off” in Palo Alto on the Southbound side of the tracks
• 1700: “tag on” at the CalTrain station in Palo Alto on the Northbound side of the tracks
• CalTrain conductor scans my ClipperCard on the 1706 Northbound train
• 1744: “tag off” at the CalTrain station at 4th & King
• 1746: “tag on” to an inbound #47 MUNI at 4th & King
• 1800: “tag on” to an outbound #14 MUNI at 11th & Mission

Ways to Mess With the System

1. I have a monthly pass for the CalTrain. I’ve realized that my pass doesn’t ever require that I tag on and tag off, as long as it responds appropriately to the on-train scanning by the conductors.
2. The only times I’ve gotten away without being scanned by a CalTrain conductor is when the train is packed to standing-room-only because of a baseball game in the city. You might be able to sneak past the conductors, but I wouldn’t count on it.
3. Similarly to CalTrain, I don’t really need to tag on to the MUNI busses, as long as my monthly pass resolves itself to a Fare Inspector. Most of the drivers will either look at you funny or explicitly require you to least flash your card by the reader. However, you can get a beep out of the readers by placing your card on the reader, but then removing it quickly. The reader realizes there’s some kind of card in front of it, but I’m assuming it can’t figure out exactly whose card is there, so it gives an error-sounding beep. This usually satisfies the drivers. (Only once in a month of doing this did a driver shame me into fully tagging the reader.)

What They Can (Still) Learn

If I didn’t take the pains to mess with my own data, you could have a pretty good idea that I live somewhere near Duboce & Mission and that I work somewhere in Palo Alto. With further analysis (and further data that I didn’t provide here), you could also notice that on alternating Wednesdays I don’t go to Palo Alto, but I seem to take the 14 to work somewhere in downtown, probably near 3rd and Mission.

I was able to mostly obfuscate my whereabouts with regard to the MUNI surface busses, except for the occasional pedantic driver. Plus, there’s a built-in obfuscation because they don’t require a tag off. However, this obfuscation doesn’t hold if you are trying to get into one of the underground stations downtown (or BART, for that matter).

For CalTrain, I was able to obfuscate the specific stops where I get on and off, but since my monthly pass is specifically identified as a Zone 1 (SF to San Bruno) to Zone 3 (Atherton to Sunnyvale) and I use “Limited” or “Express” lines (which only service certain stations), they can still get a general idea as to where I’m located.

Additionally, if you look at the records of the conductor scans, you’ll find that on my return trip I am repeatedly found within 2 or 3 scans of specific other customers. You might be able to deduce that since I am likely coming back from work, these other people are highly likely to be my coworkers. And if these people explicitly tagged on, there’s a high probability that you now know where I got on, even though I didn’t tag on myself.

Other (Potential) Problems With the System

To use the website to add cash in addition to the loaded passes, you had to do some configuration. I didn’t recognize it as a problem at the time, but it required that you have a valid credit/bank card. A friend of mine (who had to cut up her credit cards to pursue a debt-free lifestyle) said she was basically left by the wayside with regards to the ClipperCard and the benefits of its use. (Which is becoming, more an more, mandatory for monthly pass holders.) I do not know if this is still the case, but it sounds like something the ClipperCard implementers would do.

Another thing to keep in mind is that all my travel is also hooked up to my Credit Card via the ClipperCard website. You’d have to talk to other black-hat-ier people than I to learn how vulnerable the ClipperCard site is. (As a none-too-impressed end user of the website, I am sure the implementation has plenty of security holes.)

One last thing to keep in mind is who has access to your ride records. A co-worker said he was able to get a CSV file of all his ClipperCard tag ins, just by calling the Customer Service line and the rep running a quick query to get all his activity. This means the reps probably have access to everyone’s records at their whim. I have dealt with Customer Service at ClipperCard, and I’m sure it’d be pretty easy to socially engineer one of them into giving up a whole bunch of information.

Do I Care?

What does this all mean? Well, with a little bit of effort, you could figure out where I am likely to be at several points during the week. Why do I care about this? Imagine a universe where I am a vocal proponent of a measure that takes aim at MUNI drivers’ pay, and people within the union want to find me at some point to change my mind for me… Is my data easily obtainable, especially to those within the public transit system? I think so.

Conclusion

In this exercise, I’ve tried to show just how vulnerable your personal location data can be, and how it could be used to gain some further bits of knowledge about you.

In reality, the biggest risk to the average person in the ClipperCard system are the potential for a third-party (hacker) to get your credit card and personally-identifying information. A far smaller secondary risk is having your historical transit records and patterns made vulnerable, specifically because access to this information is a lot less regulated than access to your personal financial information.

Here is how I see things happening:

1. Project starts. Choose the ‘industry standard’ JUnit. Heck, let’s even go with JUnit 4 because it supports Java 5 Annotations.
2. JUnit works great for unit tests.
3. Hey, we want to write an integration test (talking to a db? setting up a Spring ApplicationContext?) as well. We’re already using JUnit, so let’s keep using it for the new integration tests too.
4. Let’s write a second (and third; and more) integration test within JUnit just like that first one we wrote.
5. Hey, why is the build taking so long? Oh, hey, JUnit is causing us to do some heavyweight operations for each individual tests. Is there some way to only do the heavy operations once per a suite of tests?
6. Blogosphere says: “JUnit is a unit testing framework, it’s not meant for integration testing”; “You are doing it wrong”; “Sure you can do that, here’s the horrible atrocity of code that you need to implement to make it possible”.
7. Find that TestNG has a richer lifecycle and can help with this integration test scenario, while still being easy to use for unit tests. Shake your fist at the air in impotent rage that you didn’t just start with TestNG.

I’ve personally seen this happen in at least 2 large projects.

I am currently in the “impotent rage” phase of the cycle. My original impetus to write this blog post was to say that someone(*) should write the class that combines the org.junit.runners.Suite functionality and Spring’s AbstractTransactionalJUnit4SpringContextTests.

Here’s the straight scoop: You are probably going to want to do some integration testing in addition to unit testing. TestNG may only be a bit different from JUnit, but it is just enough different in all the right ways to make it the tool you want to use.

(*) I know I should consider doing it. I will add it directly to the top of my “Things That Should Get Done But Won’t Ever See the Light of Day” list.

At first, I just developed the prototype in the default GAE/J Eclipse environment until I could deliver a functional POC. After finding the GAE/J capabilities more than adequate for what we wanted to do, I was challenged to bring the project into our standard IntelliJ + Maven development environment. For the rest of this post, I’ll share a couple of tips and tricks for getting your GAE/J project to operate in this environment.

Basic POM File

There’s some funny business and frustration around the Maven community’s adoption of GAE/J, but I’ll skip that part of the story for right now. What I found is that the maven-gae-plugin project is the best place to go to for help Mavenizing a GAE/J build.

I have to say that it’s not ‘use the archetype’ easy (their archetype failed for me), but with a bit of elbow-grease and rummaging through their documentation I was able to get a decent and functional POM file built. Here it is (with some of our proprietary information scrubbed to protect innocent servers):

 <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
          xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
   <modelVersion>4.0.0</modelVersion>
   <groupId>com.widgetbox</groupId>
   <artifactId>image-proxy-webapp</artifactId>
   <version>1.0-SNAPSHOT</version>
   <name>Widgetbox :: Image-Proxy :: Webapp</name>
   <packaging>war</packaging>
   <properties>
     <gae.version>1.3.0</gae.version>
     <gae.app.name>qa-image-proxy</gae.app.name>
   </properties>
   <dependencies>
     <dependency>
       <groupId>javax.jdo</groupId>
       <artifactId>jdo2-api</artifactId>
       <version>2.3-eb</version>
       <exclusions>
         <exclusion>
           <groupId>javax.transaction</groupId>
           <artifactId>transaction-api</artifactId>
         </exclusion>
       </exclusions>
     </dependency>
     <dependency>
       <groupId>javax.transaction</groupId>
       <artifactId>jta</artifactId>
       <version>1.1</version>
     </dependency>
     <dependency>
       <groupId>com.google.appengine.orm</groupId>
       <artifactId>datanucleus-appengine</artifactId>
       <version>1.0.4.1</version>
     </dependency>
     <dependency>
       <groupId>org.datanucleus</groupId>
       <artifactId>datanucleus-core</artifactId>
       <version>1.1.5</version>
       <exclusions>
         <exclusion>
           <groupId>javax.transaction</groupId>
           <artifactId>transaction-api</artifactId>
         </exclusion>
       </exclusions>
     </dependency>
     <dependency>
       <groupId>com.google.appengine</groupId>
       <artifactId>datanucleus-jpa</artifactId>
       <version>1.1.5</version>
       <scope>runtime</scope>
     </dependency>
     <dependency>
       <groupId>com.google.appengine</groupId>
       <artifactId>geronimo-jpa_3.0_spec</artifactId>
       <version>1.1.1</version>
       <scope>runtime</scope>
     </dependency>
     <dependency>
       <groupId>com.google.appengine</groupId>
       <artifactId>appengine-api-1.0-sdk</artifactId>
       <version>${gae.version}</version>
     </dependency>
   </dependencies>
   <build>
     <plugins>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-compiler-plugin</artifactId>
         <version>2.0.2</version>
         <configuration>
           <source>1.6</source>
           <target>1.6</target>
         </configuration>
       </plugin>
       <plugin>
         <groupId>net.kindleit</groupId>
         <artifactId>maven-gae-plugin</artifactId>
         <version>0.5.3</version>
       </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-war-plugin</artifactId>
         <version>2.1-beta-1</version>
         <configuration>
           <filters>
             <filter>${project.build.directory}/version.properties</filter>
           </filters>
           <webResources>
             <resource>
               <directory>src/main/external</directory>
               <targetPath>WEB-INF</targetPath>
               <filtering>true</filtering>
             </resource>
           </webResources>
         </configuration>
       </plugin>
       <plugin>
         <groupId>org.apache.maven.plugins</groupId>
         <artifactId>maven-antrun-plugin</artifactId>
         <version>1.3</version>
         <executions>
           <execution>
             <phase>compile</phase>
             <configuration>
               <tasks>
                 <echo file="${project.build.directory}/version.properties">
                     friendlyversion=${project.version}
                 </echo>
                 <replace file="${project.build.directory}/version.properties" token="." value="-"/>
                 <replace file="${project.build.directory}/version.properties" token="SNAPSHOT" value="snapshot"/>
               </tasks>
             </configuration>
             <goals>
               <goal>run</goal>
             </goals>
           </execution>
         </executions>
       </plugin>
     </plugins>
   </build>
   <repositories>
     <repository>
       <id>maven-gae-plugin-repo</id>
       <name>maven-gae-plugin repository</name>
       <url>http://maven-gae-plugin.googlecode.com/svn/repository</url>
     </repository>
   </repositories>
   <pluginRepositories>
     <pluginRepository>
       <id>maven-gae-plugin-repo</id>
       <name>maven-gae-plugin repository</name>
       <url>http://maven-gae-plugin.googlecode.com/svn/repository</url>
     </pluginRepository>
   </pluginRepositories>
 </project>

(FYI, we’re not actively using any datastore functionality just yet, so if you are going to use this template please forgive me if those dependencies are a little bit wonky.)

Since Google hasn’t (yet) decided to publish their development environment in a Maven-friendly way, there’s a bit of dependency wonkiness involved in getting the maven-gae-plugin to work. I included the repository information required by the plugin (lines 121 – 134), but if you use a repository manager (like Nexus), you’ll want to remove those lines from the POM and add a proxy for the maven-gae-plugin’s repository.

To get the development environment working the plugin also requires access to the unzipped SDK as packaged by Google. The plugin tries to help you set this up (“gae:unpack”) but that failed for me. I was able to get stuff working by manually unzipping the SDK artifact downloaded directly from Google to the following directory:

~/.m2/repository/com/google/appengine/appengine-java-sdk/1.3.0/appengine-java-sdk-1.3.0

Incremental Improvments

Initially, I had kept the appengine-web.xml within the WEB-INF directory, but I realized I could make our Release Manager’s life a bit easier if I added a bit of build-time substitution.

Here’s our appengine-web.xml:

<?xml version="1.0" encoding="utf-8"?>
<appengine-web-app xmlns="http://appengine.google.com/ns/1.0">
	<application>${gae.app.name}</application>
	<version>${friendlyversion}</version>
	<system-properties>
		<property name="java.util.logging.config.file" value="WEB-INF/logging.properties"/>
	</system-properties>
</appengine-web-app>

And you’ll see that I put it into a new source directory called ‘external’:

At build time, I use the AntRun plugin (lines 97-118) to create a small file under the target directory that holds a ‘sanitized’ version of the standard Maven version. (I.e. “1.0-SNAPSHOT” becomes GAE-friendly “1-0-snapshot”.) I then use the Maven filter functionality available in the WAR plugin (lines 80-96) to copy the appengine-web.xml into its proper directory with the version substituted in.

You’ll also notice in our appengine-web.xml that we substitute in our application name. By default this comes from the properties section of the pom.xml file (line 11). I did this because we’ve actually got 2 different applications up on GAE’s servers, the QA version and the Production version. By default we build using the QA server’s application name, but when our Release Manager is building to upload to Production, all that is needed is an additional command-line argument of “-Dgae.app.name=<prod-name>”.

Running, Debugging, and Deploying

The two most valuable targets that maven-gae-plugin provide are “gae:run” and “gae:debug”. These will assemble your code in the standard Maven webapp target directories and run your app. (Note: “gae:debug” didn’t actually work for me until the 0.5.3 version of the plugin.)

There is also a “gae:deploy” target that is supposed to invoke the Google-supplied shell script that will upload your application to the Google servers, but it failed for me several time. Since then, I’ve defaulted to using the shell script directly to deploy my app once it has been built:

~/.m2/repository/com/google/appengine/appengine-java-sdk/1.3.0/appengine-java-sdk-1.3.0/bin/appcfg.sh \
    update \
    ./target/myApp-1.0-SNAPSHOT

Results

So, this is how we got up and running with GAE/J in our standard development environment. Hopefully this post ends up helping people out to reduce their bootstrap time when evaluating/investigating GAE/J for their own uses.

“The Anatomy of a Whale“: A nice write up on problem-finding and -solving within a large-scale operation.

X-hacker: If you're reading this, you should visit automattic.com/jobs and apply to join the fun, mention this header.

I think this is a pretty cute and subtle way of looking for technically adept potential employees.

I’ve been starting to play with Google App Engine, both for personal projects and at work. Since most of my environments are Maven-based, I thought I’d go out and find a Maven Archetype or some kind of a POM file to bring these projects into my environment. I did find several blog posts trying to help: here, here, etc… The annoying thing you’ll notice on those blog posts is that Brian Fox ((formerly?) of Sonatype) posts a comment pointing towards Jason van Zyl’s post describing his efforts to Maven-ize the GAE SDK.

That would be all well and good if things had actually progressed. If you look at JvZ’s post, you’ll see he ends with “hopefully I’ll be able to get this out for Maven users by the end of the week!” What happens after that? Bupkis, nil, nothing, NADA!

There’s comments as late as Dec ’09 expressing interest to use and/or help with the effort. But, there is NO RESPONSE from anyone at Sonatype.

I just find it galling that Sonatype would go on an all-out publicity spree talking people out of working on their own because JvZ himself was going to bring his skills to bear on the problem, only to completely fizzle out. I suspect the community at large would have been better off if those 4 or 5 early Maven + GAE adopters had continued on their own path, even if JvZ had succeeded.

Again: my patience with Maven/JvZ is waning. I’m eager to see what comes along next to take its place.

They gave me an electronic copy of the book to read, and asked for a 300 – 350 word review about the book. I’ve gotten it mostly to the point of ‘completion’, and any more changes would just fall under the category of ‘tinkering’.

Maven. I hate the word, as I hate hell, all Montagues, and MAKE.

Maven is a powerful Open Source build system which is becoming a de facto standard in Java development circles. Like any powerful tool, Maven has its own proponents and detractors, benefits and drawbacks. For example, one of the consistent issues that plagues the Maven ecosystem is a dearth of quality documentation.

When I heard about “Apache Maven 2 Effective Implementation”, I had hoped that it would be the One Book to rule them all, the One Book to find them, the One Book to bring them all and in the darkness bind them. Unfortunately, this is not that One Book.

“Apache Maven 2 Effective Implementation” is yet another effort by a Maven contributor to provide some clarity to Maven’s user community about how exactly to use Maven correctly. But much like the rest of the Maven documentation ecosystem, this book provides the type of documentation that only its author could love.

The author is obviously knowledgeable, however I can’t recommend this book as anything more than an incremental addition to the Maven user’s arsenal. Having been a Maven ‘believer’ since the late 1.x days, I would say that ALL the documentation I’ve seen on the subject has been no better than incremental. In most cases, like this one, the authors falls into a classical trap of technical documentation by explaining what to do, but rarely explaining why. (Nor, more importantly, explaining how to figure these things out for yourself).

I did find a few helpful tidbits of new information in the book. However, I’m not sure I would have been able to quickly find them again in a reference situation because the logical flow was all over the place. Example: Chapter 4 had ten pages of fundamental reporting information, which is great information to have; but maybe Chapter 5, which was titled “Reporting and Checks”, is where that information rightly should have resided.

Unlike some of the best technical books I’ve read, my ability to stay awake while reading this book was challenged because it is so very dry. I had no delusions of it being as compelling as the “Encyclopedia Galactica”, but the prose was completely wooden. This blandness and the previously mentioned problems render the book altogether forgettable.

I actually had a couple of people help me with the editing and/or proofreading of my review, and I’d like to thank Jennie-Sue, Eli, and Starchy for their offers of help.

If you haven’t noticed, I have ZERO advertising on my site. It only costs me a couple of bucks a year to keep this site going, and I didn’t want to spoil the relationship with my readers by trying to commodify their viewing. So, when I was approached to do the review, I was very specific that I would not pull any punches just because they gave me a free book. Packt also tried to sign me up with an affiliate link to the book, which you’ll notice is nowhere in this (or any) post.

As you can tell, I really didn’t use the kid gloves with this review. I’m not very happy with the general quality of Maven documentation (as I’ve noted before), and I wasn’t going to give this book high marks for being just as bad as the rest.

I did manage to sneak in (or are they clumsily manhandled?) 3 different literary fiction references, which I hope spices up the review and adds a bit of character. Let me know if you can name them.

I started out my trip in Bordeaux, where I found a pretty nice hotel to be my ‘base of operations’ whilst I tried to work out my motorcycle rental. I managed to find the website and then the physical location of Bordeaux Scooters, and this is where I rented the motorcycle for one whole week.

For the first day, I just rode around the city of Bordeaux a very little bit, trying to accustom myself to the Yamaha Fazer 650 (since I normally ride a Kawasaki Ninja 500).

On my first full day on the bike, I got out of Bordeaux and hit a bunch of secondary (C and D) roads. I hit places like Biscarosse(-en-Plage), Mimizan, and Léon, before I stopped for the night in Hasparren where I stayed at a cute Hôtes de Chambre (Bed & Breakfast). I was feeling pretty good and confident, both in my motorcycling ability and my language ability to operate in the hinterlands of France.

For my second day of riding, I figured I’d take some more scenic roads, and even cross over the Spanish border for a bit. I made it through the border just fine, and was cheerfully enjoying the nice big sweeping roads on the way to Elizondo, and then turned on the road towards Erratzu to make my way back into France near Saint-Etienne-de-Baïgorry.

It was just after a hairpin turn, not more than 1km from the French border and the summit of the hill. I noticed the old stone barn on the left side of the road, then I looked uphill and contemplated that I should be careful because of all the mountain mist that was probably making the road slippery. I brought my attention back to the road, and was alarmed to find that I had drifted close to the side of the road. I started to panic. I was so worried about the side of the road that I couldn’t look away, and motorcyclists know that’s exactly where I ended up.

Now that I was on the edge of the road, I made a snap decision to bite the bullet and take the bike off the road and try to stop before anything untoward happened. Something untoward happened. The mist I had been worrying about mere milliseconds before was coating the grass I was on and the front tire slipped sideways, dumping me and the bike onto our left sides.

I am lucky because I had just recently come out of a tight turn and I wasn’t going all that fast. I landed face down with my torso on the pavement, and did only about 1 1/2 horizontal pirouettes before I came to a rest. While the helmet I was wearing was scraping across the pavement, I remember thinking “Boy, a helmet is a really good idea!”

I was up in an instant, just in time to see that the hard case (holding most of my possessions) rolling down the hill. In my adrenaline-addled mind, I decided that I really needed to get my stuff back. So, I went careening down the side of the mountain in my full gear. I found the case 1 1/2 switchbacks down. I brought it up to the road (1 full switchback below the motorcycle) and only then did I decide to take off some of my gear and inspect for damage. Other than a little bit of scuffed up skin, I was actually fine.

As I was walking back up to inspect the bike, a younger French guy in a car stopped to give me a hand. He helped me turn the bike over, and point it away from downhill. He told me he expected insurance (assurance in French) could be found in any town, and that they’d have me set back up in no time. I thanked him for his help and advice, and sent him on his way, while I figured out what I needed to do.

After I got all my stuff assembled, and took a couple of pictures, I sat down and tried to call the rental shop. I ended up calling Ryan (in the U.K) for some research help because I didn’t know what the country-code is for France. After we got that figured out, I realized the rental shop was on their stated lunch break until 2PM. (It had just turned about 12:30PM.) I sat there for a bit trying to keep myself calm and counting my lucky stars. After I changed into some less-sweaty and warmer clothes, I decided that I should try to get to ‘civilization’, preferably on the French side of the border since the motorcycle was rented from France.

Eventually a nice (German?) couple on motorcycles stopped to give me a hand. We were formulating an elaborate me-plus-my-stuff-on-their-bikes plan, when I realized it was a bit soon for me to be riding on a motorcycle again. I got them to help me flag down a passing carpenter, who agreed to take me and my stuff in his truck to the mechanic’s in Saint-Etienne-de-Baïgorry. The local mechanic was of no help, other than trying to help me call the rental shop again, which I knew was still closed. After he basically told me to go away because he didn’t deal with motorcycles and he was on his lunch break, I walked towards town center and sat on the steps of a hotel/brasserie that was also closed for lunch. I decided to wait out the remaining hour or so until the rental shop opened up by chilling out and reading my Kindle on those steps.

Once I did get the rental shop on the phone, they told me that I needed to get the bike transported back to Bordeaux (250km) by whatever means necessary. The shop owner offered to see if he could find someone to do it, and I said I’d look around at my end. After our conversation, I had no idea if I would be stuck in the town of Saint-Etienne-de-Baïgorry overnight, but I figured I’d check into the hotel until things settled, and if I had to leave early, I could just lump one night’s charge.

As I was checking into Full-screenHotel Juantorena, I mentioned (or whined) to Mélanie (who I later found out was one of the owners) that I had just been in a motorcycle accident and needed to find a truck to bring the broken motorcycle back to Bordeaux. She said that her husband might be able to help me out. Bixente came out from the kitchen, and called around to some truck services in Biarritz, and found me a quote of €1,200. I thanked him and said I would call back to Bordeaux to see if the rental place had found me a better quote. The rental place said to call back in a couple of hours because the friend they were going to ask was out at the moment and it would be a while before they got an answer.

It turns out that Bixente is also a motorcyclist, and offered to take me (after he finished setting up his kitchen for the evening) to pick up the motorcycle on his motorcycle trailer to bring it down (the 10 km) to his hotel parking lot. I was kind of amazed at this, but just went with it after the day I was having. About a 1/2 hour later, after I had washed off some of my road rash, he called me down to the front of the hotel where he, his truck, and his motorcycle trailer were waiting for me. He drove me up to the crash spot where we loaded up the wreck, and brought it back to the hotel.

The ride up and back could have been horrible. But after figuring out my French skills needed just a bit of annunciation and a slower pace, Bixente actually took the time to get to know me. We had a really nice conversation, and I’ve come to look back upon that conversation as one of the nicest moments during my time in France.

After getting back to the hotel, I called the rental shop to tell them that the bike was now in the parking lot. In addition to the location of the bike, we had some (mis-)communication where I thought they said to wait several more hours to verify that the truck from Bordeaux would be interested in the job. So, I took a little nap, then read some more whilst having a beer in the bar. I was really surprised when Bixente told me the truck driver was at the other end of town and would be arriving soon. (Evidently, when I thought the rental shop was telling me that I was waiting for confirmation, they were actually telling me that I was waiting for the arrival of the truck.)

The truck driver, myself, and Bixente loaded up the bike into the truck. It was now about 8 or 9PM, and the driver hadn’t eaten, and neither had I, so we had dinner at the restaurant. The driver was kind of gruff, and not all that friendly, but I managed to get some small-talk in. After dinner, using Bixente as a patient go-between, we established that it was best if I went with the truck driver back to Bordeaux with the bike. (I didn’t realize there was more for me to do there.) So, I checked out of the hotel. I tried to convince Mélanie to keep my room charge, but she wouldn’t hear of it. She insisted that if I weren’t staying overnight they wouldn’t even think about keeping my money.

The driver brought be back to Bordeaux, and dropped me off at midnight at a hotel right near the rental shop. The next day, I went to the rental shop to find out that we were waiting for a verdict from the motorcycle repair shop. When I remembered that I hadn’t yet paid the driver from the evening before, the rental shop owner called him for the price. Since I was paying in cash for the truck ride, it only came out to €500, which is a great deal compared to the other quotes I had received.

Later that afternoon, the verdict came down that the bike’s frame was bent and therefore “totaled”. I went back over to the rental shop to sign the credit card slip for the €1800 security deposit that I had now forfeited. And thus ends my motorcycle adventure in France.

Looking Back

Now, people say all sorts of horrible things about the French. In general, I can tell you that much of this is wrong. In specific, I can tell you that Mélanie and Bixente are some of the warmest and most caring people I’ve ever run into in my travels. They took the time to patch up and help this stupid American with bad French and even worse motorcycle skills, and not ask for anything in exchange, other than an email greeting at some time in the future. I hugged Mélanie and Bixente fiercely, and I left their hotel with tears in my eyes because I felt really fortunate to have met these beautiful people.

I realize that I directly benefited from what I refer to as the Motorcyclist (a.k.a. Motard) Fraternity. Without knowing me, but because I spend time on two wheels like they spend time on two wheels, both the German couple and Bixente went way out of their ways to make sure I was taken care of. I guess it’s a similar thread amongst motorcyclists to help out your fellow motorcyclists.

Doing Them A Solid

In addition to adding Mélanie and Bixente to my Xmas card list, I have decided to send as many people as I can to them. So, if any of you readers are ever interested in a quaint village in the beautiful Basque region of France, might I suggest Hotel Juantorena? Also, spreading this info to motorcyclists far & wide would be much appreciated.

(I will try to scan in their pamphlet, but in the mean time, here’s their contact info:) t

Hotel Restaurant Juantorena

64430, Baigorry

Pyrénées-Atlantiques, Aquitaine, France

Lat/Long: 43.17405, -1.34875

Phone: 05 59 37 40 78

Email: hotel.juantorena@orange.fr

Their pamphlet shows that they have a website (http://www.hotelrestaurantjuantorena.fr) but it doesn’t seem to be working?

I was blown away today when I got an email from Brittany saying that not only will Widgetbox management support me in this endeavor, but they are going to add a 1 day per year allowance to our policies for all the employees to pursue similar efforts. Wow!

This just cements for me that I am totally working with the right set of people in a company that is just the right size for me. I feel appreciated, listened to, and respected, even when I bring forth crazy ideas like sending me off on our investors’ dime to save the world.

Yeah, my life: it doesn’t suck!

To get a feel for how many of these problems existed (after I just-in-time fixed the individual JSPs that crossed my path), the boss wanted me to run a precompile against our whole JSP codebase.

I found the instructions on the Tomcat site, which proved to be incomplete and/or incorrect (of course).

Here is what I ended up with:

<project name="Webapp Precompilation" default="all" basedir=".">
   <import file="${tomcat.home}/bin/catalina-tasks.xml"/>
   <target name="jspc">
       <jasper
             validateXml="false"
             uriroot="${webapp.path}"
             webXmlFragment="${webapp.path}/WEB-INF/generated_web.xml"
             outputDir="${webapp.path}/WEB-INF/src"
             compilerTargetVM="1.5"
             compilerSourceVM="1.5"
             failOnError="false" />
  </target>

  <target name="compile">
    <mkdir dir="${webapp.path}/WEB-INF/classes"/>
    <mkdir dir="${webapp.path}/WEB-INF/lib"/>
    <javac destdir="${webapp.path}/WEB-INF/classes"
           optimize="off"
           debug="on" failonerror="false"
           srcdir="${webapp.path}/WEB-INF/src"
           source="1.5"
           target="1.5"
           excludes="**/*.smap">
      <classpath>
        <pathelement location="${webapp.path}/WEB-INF/classes"/>
        <fileset dir="${webapp.path}/WEB-INF/lib">
          <include name="*.jar"/>
        </fileset>
        <pathelement location="${tomcat.home}/lib"/>
        <fileset dir="${tomcat.home}/lib">
          <include name="*.jar"/>
        </fileset>
        <fileset dir="${tomcat.home}/bin">
          <include name="*.jar"/>
        </fileset>
      </classpath>
      <include name="**" />
      <exclude name="tags/**" />
    </javac>
  </target>

  <target name="all" depends="jspc,compile"></target>

  <target name="cleanup">
        <delete>
        <fileset dir="${webapp.path}/WEB-INF/src"/>
        <fileset dir="${webapp.path}/WEB-INF/classes/org/apache/jsp"/>
        </delete>
  </target>
</project>

The real stroke of luck is this piece:

             compilerTargetVM="1.5"
             compilerSourceVM="1.5"

Their document said stuff about adding some parameters (source="1.5" target="1.5") to the “javac” target, but they neglected the “jasper” target. The error messages complained about the above two parameters being set to 1.4, so as an experiment I plugged them into the ANT target with 1.5′s and the compilation ran correctly!

Another word of note, the “showSuccess” directive did not work as their documentation states, but the “failOnError” directive does.

I hope this helps others!

I do not like Facebook. I do not like it one bit. I want nothing to do with Facebook at all, and I’ve been very adamant about not signing up for an account despite the urging of everyone and their brother.

So, when I recently gained an understanding of how Facebook Connect works, I got a bit upset. Let me show you why with an example.

Let’s say I want to create an account at MapMyRun.com which implements Facebook Connect, I will use my primary email address of “nelz@example.xxx”. After my account gets created MapMyRun then encrypts my email address with a one-way hash, which for the sake of argument looks like “BIGBADHASH”, and sends this hash to Facebook. “So what?” you think. Sure, they can’t figure out anything about me from a single one-way-hash of my email address, right?

Well, then let’s say I register for an account at io9, again with my primary email address “nelz@example.xxx”. Since io9 also implements Facebook Connect, they also hash my email address and send it to Facebook. Guess what? The resulting string, “BIGBADHASH”, is the exact same as what MapMyRun just sent them.

Now, Facebook knows that someone with an email address that hashes to “BIGBADHASH” has an account on both MapMyRun and io9. Again you think “So what?” That one-way-hash protects my identity from being associated with any of these specific behaviors, right? Au contraire, mon frère.

Now one of my well-meaning friends, who doesn’t know how much I loathe Facebook, tells Facebook that they want to connect with someone at the address “nelz@example.com”.

This was the last piece of the puzzle that Facebook needed. Facebook need only apply the one-way-hash to the plaintext email that my friend just provided them with, and they get “BIGBADHASH”. Then, they look up in their database where they’ve seen that hash before, and now they know that a user with an email address of “nelz@example.com” has an account on both MapMyRun and io9.

Now I, who has never ever logged into Facebook, am getting tracked by Facebook whether I like it or not.

External Remediation

Okay. So what can we do about this?

I looked on Facebook.com, and I found a Privacy Policy. But everything on there requires that you have an account on Facebook. I guess I could create an account, then delete it, but I don’t want an account on Facebook! What Facebook really needs is some web form for non-members that says “Forget anything you have, or will, ever collect about email XYZ”. But, that’s not likely to happen.

What about the end-points, the sites that are implementing Facebook Connect? Personally, during their sign-up processes, I’d like to see a check box that says “Don’t sell me out to Facebook.” Again, that’s not likely to happen.

Personal Remediation

Now, don’t get me wrong, I’m not a n00b. I realize there are all sorts of sites tracking my footprints across the digital landscape every day. (Quantcast, DoubleClick, etc…) For most of them, if I were paranoid and technical enough I could purge their cookies or set up a proxy that doesn’t let my browser connect to those URLs.

But this Facebook thing is different, because it’s highly likely that the communication back to Facebook is not coming from my browser, but from the servers of sites like io9 and MapMyRun. And I have no way to stop it.

How about using a different email address for each site. Sure, that could work. If I had my own mail server, I could create “io9@nelzserver.xxx” for io9 and “mapmyrun@nelzserver.xxx” for MapMyRun, but how many people will have access or technical ability for something like that?

Gmail has a feature that could help out here. If I have an email address like “example@gmail.com”, I will still get the mail if it is sent to “example+io9@gmail.com” or “example+mapmyrun@gmail.com”. I found two challenges with this pattern: 1. it can break the “Forgot My Password” functionality if you forget what email you signed up with, and 2. emails with “+” in them don’t always pass the (incorrect) regex‘s sites use to validate emails.

Conclusion

As I have said before, I am living life pretty openly on the internet. And like I said above, I know there are countless other companies doing much more specific tracking and profiling of me.

But Facebook’s hegemonic desires to run the internet frustrate me, and I don’t want to be a part of it. And it pisses me off that there’s nothing I can do to extract myself.

Update: Found this interesting blog post – “Dark Stalking on Facebook“

So, here is the short version:

1. Have Rocking Goals
2. Be Ambitious
3. Invest In Yourself
4. Healthy Lifestyle
5. Be Responsible
6. Patience Is The key
7. Never Give Up
8. Learn From Failures
9. Remain Positive
10. Celebrate Success