Isang Maikling Kasaysayan ng SharePoint (Mula sa pananaw ng isang bagong dating Kamag-anak ni)

Nota: This article was originally posted to www.endusersharepoint.com. Nakalimutan kong mai-post ito sa sarili kong blog 🙂

SharePoint ay umunlad ng mahusay na deal nito mula noong unang bahagi ng araw bilang isang uri ng pagpapapisa ng itlog ng isang teknolohiya sa Microsoft –ito ay umunlad halos tulad ng isang pelikula malaking sindak, where the mad scientist’s creation takes on a life of its own, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 object model is richer and more complex than WSS 2.0, which was itself an improvement over earlier versions. The next version will no doubt show tremendous improvement over 3.0. From an End User’s perspective, gayunman, SharePoint’s evolution is even more significant.

In the early days, SharePoint didn’t offer much to End Users. They would have their usual functionality requirements, work with IT to define them well and implement a solution. IT would use SharePoint to solve the problem. The product wasn’t very accessible to End Users. I’ve thought threw a few analogies, but I decided to stick Venn Diagrams to show what I mean. When Microsoft first released SharePoint to the world as a commercial offering, it followed a relatively traditional pattern of End User <-> IT relationship. A lot of End Users, communicating and working with a very small number of It people to deliver solutions that solve business problems:

The overall problem domain for which SharePoint is a suitable delivery platform is small (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: tukuyin ang mga kinakailangan sa IT, maghintay para sa IT gawin ang kanilang trabaho sa likod ng tabing at kumuha ng paghahatid ng panghuling produkto.

Tulad ng SharePoint upang umunlad ang 2.0 mundo (WSS 2.0 at SharePoint Portal Server), several things happened. Una, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Halimbawa, hindi mo gusto sa tingin masyadong matigas tungkol sa pagpapatupad ng isang seryosong solusyon sa paghahanap sa isang kapaligiran sa SharePoint hanggang sa SPS (at kahit na pagkatapos, ito ay hindi bilang mabuting bilang ito kinakailangan upang maging). Sa parehong oras, Mga End User magkaroon ng isang hindi pa nagagawang kakayahan upang hindi lamang tukuyin ang, but also implement their own solutions with little or no IT support.

The 3.0 platform (WSS and MOSS) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 platform. Virtually every department in a company, ranging from manufacturing health and safety departments to marketing, from sales to quality control – they can find a good use for SharePoint (and it’s not a case of mashing a round peg into a square hole). Sa parehong oras, the platform empowers even more End Users to implement their own business solutions. I try to capture that with this diagram:

This has proven to be both a potent and frustrating mixture. The 3.0 platform turns previously stable roles on their heads. Suddenly, End Users are effectively judge, jury and executioner business analyst, application architect and developer for their own business solutions. This gets to the heart of the problem I’m writing about. But before I dive into that, let’s consider the elephant in the room.

Peering into the Crystal Ball

How will SharePoint 2010 affect this pattern? Will it be incremental or revolutionary? Will more, fewer or about the same number of End users find themselves empowered to build solutions in SharePoint 2010? Will SharePoint 2010’s problem domain expand even further or will it just refine and streamline what it already offers in WSS 3.0 / Lumot?

There’s enough information “out there” to safely say that the general answer is:

• The problem domain is going to dramatically expand.
• Mga End User ay mahanap ang kanilang mga sarili kahit na higit pa kaysa empowered bago.

The Venn Diagram would be larger than this page and cause some IT Pros and CxO’s to reach for their Pepto.

I believe it’s going to be a tremendous opportunity for companies to do some truly transformational things.

Walang Bulls sa Aking China Shop!

Ito mahusay na tunog, ngunit mula sa aking mga punto ng view ng bilang isang consultant SharePoint at paglalagay ng sarili ko sa shoes ng isang IT manager, I see this vision. I own a China shop with beautiful plates, kristal, at iba pa (aking SharePoint kapaligiran). I’ve rented a space, I’ve purchased my inventory and laid it all out the way I like it. I’m not quite ready to open, ngunit sa mga pag-asa, I look at the door to see if my customers are lining up and I notice an actual bull out there. I look more closely and I actually see dalawa bulls and even a wolf. Then I notice that there are some sheep. Sheep are kaya masama, but are they maybe disguised wolves? I don’t want bulls in my china shop!

It gets worse! When I rented the space, I couldn’t believe how nice it was. Wide and open, terrific amenities, very reasonable price. Gayunman, now I’m realizing that the wide open spaces and the huge door is just perfectly sized for a bull to come wandering in and lay waste to my china.

I’m pushing this analogy too far, mangyari pa. End Users are not bulls (most of them, gayon pa man) and IT departments don’t (o dapat ay tiyak na hindi) view their user community with that kind of suspicion. Gayunman, mayroong ganitong uri ng perpektong banggaan nagaganap pa sa mga 3.0 platform that I expect will only get worse in SP 2010. SharePoint already empowers and encourages End Users to define and implement their own solutions.

Iyan ay mahusay at lahat, ngunit ang katotohanan ay na pa ito sa isang napaka-teknikal at produkto pa rin ng mga tawag para sa uri ng malusog na kinakailangan pagtatasa ng negosyo, design and general planning and management that technical projects require to be successful. These are not the kind of skills that a lot of End Users have in their bag of tricks, especially when the focus is on a technical product like SharePoint.

I’ve given this a lot of thought over the last year or so and I don’t see any easy answer. It really boils down to education and training. I think that SP 2010 is going to change the game a bit and it’s going to play out differently and in slow motion as companies roll out their SP 2010 solutions over 2010 and beyond. In order to succeed, End Users will need to transform themselves and get a little IT religion. They’ll need to learn a little bit about proper requirements
analysis. They will need some design documentation that clearly identifies business process workflow, halimbawa. They need to understand fundamental concepts like CRUD (create, update and delete), dev/test/qa/prod environments and how to use that infrastructure to properly deploy solutions that live a nice long time and bend (not break) in response to changes in an organization.

In the coming weeks, I plan to try and provide some of my own new ideas, as well as link to the great work done by many other authors (sa www.endusersharepoint.com at sa ibang lugar) so that interested End Users can learn that old time IT religion. Keep tuned.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

[Nota: This article cross-posted to End User SharePoint dito: http://www.endusersharepoint.com/2009/09/09/sharepoint-a-case-study-in-ask-the-expert/]

Kung minsan, kapag nagtatrabaho ka bilang isang consultant (bilang isang propesyon, o sa isang pakonsulta papel sa loob ng iyong kumpanya), you find yourself living in an Onion story. The Onion has a series of articles called “Ask an [dalubhasa] tungkol sa [ang ilang mga problema]". This follows the famous “Dear Abby” format where a concerned person is asking for personal advice. The onion’s “expert”, gayunman, is so focused on his/her area of expertise and current problems that the expert ignores the question entirely and rambles on about his area of expertise. As consultants, we need to keep that in mind all the time and avoid falling into that trap. It’s classically described like this – “when you use a hammer all day long to solve your problems, everything starts to look like a nail.” We professional consultants are always on guard against that kind of thing, but we come into contact with people who are serious professionals in their own role, but are not consultants. They don’t have the same need or training to do otherwise.

Huling na-linggo, I wrote about one of my company’s clients and an on-going project we have to enable high quality collaboration between various eye doctors in the US and Canada performing clinical research on rare disease. In addition to leveraging core SharePoint features to enable that collaboration, we’re also working an expense submission and approval process. It’s complicated because we have so many actors:

• A handful of individuals at different doctors’ practices who can enter expenses on line.
  • There are over 40 doctors’ practices.
  • At some practices, the doctor uses the system directly.
  • At many practices, the doctor’s staff uses the system directly.
• A financial administrator (who works for my direct client) who reviews the expenses for accuracy and relevancy, approving or denying them at the organizational level.
• A 3rd party accounts payable group. These people pay all of the bills for out client, not just bills coming out of the rare disease study.

The Accounts Payable group has been a challenge. Working with them yesterday reminded me of the Onion series. In my role as business consultant, I explained the need to the accounts payable company:

• Clinical studies sites (doctors’ practices) incur study-related expenses.
• They log onto the “web site” and enter their expenses using an online form. Sa kasong ito, the “web site” is hosted with SharePoint and the expenses are entered into an InfoPath form. Expense receipts are scanned, uploaded and attached directly to the form.
• An automated workflow process seeks approval from the appropriate financial administrator.
• You, dear 3rd party AP company – please review and approve or deny this expense. I’ll send it to you any way that you want (within reason).At this point in the discussion, I don’t really care how it needs to be bundled. I want to work with the AP group to understand what they need and want.

When I explained the need, the 3rd party took a deep dive into their internal mumbo jumbo lingo about expense approval processes, Oracle codes, vice presidential signatures, 90 day turn-arounds, at iba pa. And panic. I shouldn’t forget about the panic. One of the bed rock requirements of the consulting profession is to learn how to communicate with people like that who are themselves not trained or necessarily feel a need to do the same. Among other things, it’s one of the best parts of being a consultant. You get to enter a world populated with business people with completely different perspectives. I imagine it’s a little bit like entering the mind of a serial killer, except that you aren’t ruined for life after the experience (bagaman pagpasok sa isipan ng isang AP manager ay hindi isang lakad sa parke 🙂 [see important note below***] ).

One of the great things about our technical world as SharePoint people is that we have ready-made answers to many of the very valid concerns that people such as my AP contact have. Is it secure? How do I know that the expense was properly vetted? Can I, as the final payer, see all the details of the expense? How do I do that? What if I look at those details and don’t approve of them? Can I reject them? What happens if the organization changes and the original approver is no longer around? Can we easily change the process to reflect changes in the system? Can I revisit this expense a year later if and when I get audited and need to defend the payment?

As SharePoint people, we can see how to answer those questions. In my client’s case, we answer them more or less like this:

• InfoPath form to allow sites to record their expenses and submit them for approval.
• Sites can return to the site to view the status of their expense report at any time.
• As significant events occur (e.g. the expense is approved and submitted for payment), the system proactively notifies them by email.
• The system notifies the financial administrator once a report has been submitted for approval.
• Financial administrator approves or denies the request.
• Upon approval, the expense is bundled up into an email and sent to the 3rd party payer organization.
• The 3rd party payer has all the information they need to review the expense and can access the SharePoint environment to dig into the details (primarily audit history to verify the “truth” of the expenses).
• 3rd party payer can approve or reject the payment using their own internal process. They record that outcome back in the SharePoint site (which triggers an email notification to appropriate people).
• In future, it would be nice to cut out this stilly email process and instead feed the expense information directly into their system.

In conclusion, there’s a life style here that I describe from the professional consultant’s point of view, but which applies almost equally to full time employees in a BA and/or power user role. Work patiently with the experts in your company and extract the core business requirements as best you can. With a deep understanding of SharePoint features and functions to draw upon, more often than not, you’ll be able to answer concerns and offer ways to improve everyone’s work day leveraging core SharePoint features.

***Mahalagang paalala: I really don’t mean to compare AP people to serial killers. Gayunman, I could probably name some AP pro’s who have probably wished they could get a restraining order against me stalking them and asking over and over again. “Where’s my check?” “Where’s my check?” “Where’s my check?"

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

[Nota: ang blog na ito post ay tumawid na nai-post sa Mark Miller ng site dito: http://www.endusersharepoint.com/?p = 1897]

Isa sa ng aking kumpanya higit pang mga hindi karaniwang mga kliyente ay isang New York City doktor kung sino ay isang pinuno sa kanyang mga partikular na larangan ng medisina (mata pag-aalaga). Like many doctors, he has a strong interest in research. He wanted to do some research on a rare eye disorder that affects a relatively small number of people in the U.S. and Canada. I don’t know the number, but it’s really too small for a large pharmaceutical company to invest its own private funds with an eye toward eventual commercial success. I’m sure large pharma’s do some amount of research into rare diseases, ngunit naniniwala ako na ang U.S. government is probably the largest source of funding. Tulad ng anumang bagay, resources are scarce. Many doctors across the country want to perform research and trials. Bilang isang resulta, there’s more than a little competition for that government funding. This is where my company and SharePoint enter the picture.

The fundamental idea is that a master organization will recruit other doctors across the country and enlist those doctors’ practices in a particular research study. These individual practices must sign up with the master organization and then, pagkaraan, sign up for a particular study. The relationships look like this:

• One master organisasyon.
• Mga kasanayan sa maraming iba't ibang mga doktor mag-sign up sa pagkakabuo master.
• The master organization obtains funding for individual studies. At the outset, doon lamang ang isa sa mga pag-aaral sa isang partikular na bihirang sakit sa mata kahit na mayroon kaming ramping up para sa isa pang pag-aaral.
• Individual doctors’ practices sign up for specific studies. A specific practice could sign up for one or multiple studies.

Ang master organisasyon mismo ay hinati-hati sa mga grupo:

• Executive komite
• Pangunahing lupon
• Indibidwal na pag-aaral ng komite
• Pangangasiwa
• mga iba

Sa wakas, kapag practice ng tukoy na doktor-sign up upang lumahok sa isang pag-aaral, kailangan nila upang magbigay ng mga propesyonal upang matupad ang iba't ibang mga tungkulin:

• Investigators (kabilang ang isang pangunahing tagapag-usig, normal isang doktor, kasama ang isa o higit pang mga karagdagang mga investigators)
• Coordinators
• Technicians
• Grants administrator
• mga iba

The above roles have very specific and highly proscribed roles that vary by study. I won’t get into more detail here, ngunit kung interesado ka, mag-iwan ng komento o email sa akin.

At ngayon maaari kong sagutin ang tanong, SharePoint - Ano ito mabuti para sa? The answer – it’s really good for this scenario.

Intro ito ay mas mahaba kaysa sa inaasahan ko, kaya kailangan ko sabihin sa maikling pangungusap ang mahalagang papel na SharePoint ay gumaganap sa solusyon at pagsisid sa mga detalye sa isang hinaharap na artikulo (kung hindi ka maaaring maghintay, email sa akin o mag-iwan ng komento at ikalulugod kong upang talakayin at marahil kahit na subukan na gawin ang isang demo). We are leveraging a wide array of SharePoint features to support this concept:

• Sites para sa komite, indibidwal na mga tungkulin (coordinator site, tagapag-usig site, at iba pa).
• Security upang matiyak na ang iba't ibang mga kasanayan sa hindi nakakakita ng iba pang mga kasanayan 'data.
• InfoPath forms services for online form entry. This is a particularly big win. Normal, mga mahihirap na mga form ay naka-print, ipapadala sa koreo sa mga kasanayan sa, filled out and mailed back. The advantages to the online forms are obvious. They do introduce some complexities (paglilisensya at pantao) ngunit iyan ay isa pang kuwento.
• Out ng kahon ng mga bahagi ng web, tulad ng mga anunsyo (kailan matatapos ang komite [x] matugunan?) at natutugunan ang mga puwang sa trabaho.
• Forms based authentication sa kumbinasyon na may isang CodePlex tool upang magbigay ng self-registration at password kalimutan mga tampok.
• Customized na mga listahan at listahan ng mga tanawin para sa kakayahang makita sa mga aktibidad na pag-aaral lamang ay hindi posible sa dalisay papel at lapis approach.

Sa pamamagitan ng pagbubukod ng mga form based na authentication module at ang maliit na bilang ng mga form InfoPath, proyektong ito ay gumagamit ng halos lahat ng palabas ng pag-andar kahon SharePoint.

Bago ko tapusin ito min-case study, Gusto kong ituro ang isang bagay napakahalaga - walang kinalaman sa may proyektong ito (bukod sa aking kumpanya ng kurso) has any idea that a thing called “SharePoint” is playing such a fundamental technical role. Nearly all of my end users view this as “the web site.” Our client values us because we’re solving their business problem. SharePoint is a great technical blob of goodness, ngunit tapos kanan, that’s irrelevant to end users. They need a problem solved, hindi isang kahanga-hangang patak ng teknolohiya.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

O isa lamang sa akin? I’ve received three or four calls at my house since late September looking for SharePoint work. I’m used to the email solicitations, but these phone calls are a little unnerving. I haven’t had an updated resume on a job site I(like Monster pr Dice) since almost two years ago exactly. And back then, my resume was all about BizTalk and MS CRM. That’s the only place my phone number appears on line anywhere, sa abot ng alam ko.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

The closing thought on this otherwise dull article speaks well to problems we often face in the technical community:

"Such dreary developments, inaasahang may katiyakan, dapat na makitid ang isip philosophically."

This puts me in mind of one of the presentations I gave at the SharePoint Best Practices conference last month. I was describing how to get "great" business requirements and someone in the audience asked, in effect, what to do if circumstances are such that it’s impossible to get great requirements. Halimbawa, a given company’s culture places IT in front of the requirements gatherer / business analyst, preventing direct communication with end users. This is a serious impediment to obtaining great business requirements. My answer was "walk away." I’m not a big humorist, so I was surprised at how funny this was to the audience. Gayunman, I’m serious about this. If you can’t get good requirements, you can be certain that a dreary outcome will result. Who wants that? I’m a consultant, so it’s more realistic (although terribly painful and drastic) for me to walk away. Gayunman, if you’re entrenched in a company and don’t want to, or can’t, walk away, George (for once 🙂 ) shows the way.

</dulo>

Mag-subscribe sa aking blog.

Sundin ako sa Twitter sa http://www.twitter.com/pagalvin

Gaano kadalas ang mga ito mangyari sa iyo? I’m sitting at my laptop, pagbabasa mga blog, pagtugon sa mga forum ng mga pag-post, 2 mga kopya ng visual studio bukas at VPN'd out sa isa pang server na may sariling visual studio + 15 browser sa window (isang karaniwang araw) at isang tao na may pangalang Samantha (aking asawa, sa malas) Sinasabi sa akin, "We have be there in 30 minuto. Get dressed."

Nakukuha ko up sa isang mawalan ng ulirat, igala ang bahay confusedly, kumuha sa isang kotse at susunod na bagay na alam ko, Ako ay sa isang partido na may beer sa aking mga kamay at may isang taong nagtatanong sa akin, "So, Ano ang inyong trabaho?"

Ang mga pag-uusap ay hindi kailanman pumunta rin.

Sa akin: "Ahh … Isa akong arkitekto solusyon para sa EMC."

Hindi mailarawan Tao: blangko pangsingaw

Sa akin: "I work with a product called SharePoint … ito ay mula sa Microsoft."

NP: "Aha! Ko na narinig na ng kumpanya! What is SharePoint?"

Sa akin: "Umm … ginagawa nito pakikipagtulungan … mga tao gamitin ito upang ibahagi ang impormasyon … Ito ay isang platform para sa gusali busines sol…"

NP: Mata glazing.

Sa akin: "I’m a programmer."

NP: "Aha! I know people in my company that do programming! When I was in high school, I-play sa paligid na may BATAYANG."

At sa bahaging iyon ng pag-uusap sa ibabaw, lumiko kami sa isang bagay na mas madali ang pag-uusapan, tulad ng politika.

Sinuman pangangalaga upang ilarawan kung paano sila hawakan ito?

</dulo>

Mag-subscribe sa aking blog.

Ko pa sa klase ang mga nakalipas na dalawang linggo at isang bagay na naaabot sa akin ay na mayroong ng maraming nag-isip, matalinong tao ang pagtatrabaho sa SharePoint (bilang tagapayo o kawani ng IT) hindi nag-blog, nerbiyos, mukhang alam ng pampublikong boards mensahe tulad ng MSDN forum o SharePoint University, panatilihin ang mga profile sa Facebook o LinkedIn, at iba pa. They are pure information consumers. Not bad, lamang kawili-wiling.

</dulo>

Mag-subscribe sa aking blog.

Ang isang grupo ng mga taon na nakalipas, my boss asked me to train some users on a product called Results. Results is an end user reporting tool. It’s roughly analogous to SQL Server Reporting Service or Crystal. Sa oras, ito ay dinisenyo upang tumakbo sa mga berdeng tubes (e.g. Wyse 50 hantungan) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" at na kung saan ang lahat ng mga problema sa magsimula.

Ang client ay isang kemikal kumpanya out sa southern California at si lamang tungkol sa balot up ng isang pangunahing pagpapatupad ng ERP batay sa QAD ni MFG/PRO. The implementation plan now called for training power end users on the Results product.

I wasn’t a big user of this tool and had certainly never trained anyone before. Gayunman, Ako ay isinasagawa ng isang bilang ng iba pang mga klase sa pagsasanay at naging mabilis sa aking mga paa, so I was not too worried. Dennis, ang tunay na full-time na magtuturo Resulta, had given me his training material. Looking back on it now, it’s really quite absurd. I didn’t know the product well, had never been formally trained on it and had certainly never taught it. What business did I have training anyone on it?

Upang makapagpalubha bagay logistically, I was asked to go and meet someone in Chicago as part of a pre-sales engagement along the way. The plan was to fly out of New Jersey, pumunta sa Chicago, meet for an hour with prospect and then continue on to California.

Mahusay, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Kaya, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, Tingin ko out na ang kliyente ay pag-aaral ng mas mababa sa 24 hours before my arrival that "Paul Galvin" ay nagtuturo ng klase, not Dennis. The client loves Dennis. They want to know "who is this Paul Galvin person?" "Why should we trust him?" "Why should we pay for him?" Dennis obviously didn’t subscribe to my "magbigay ng masamang balita maaga" philosophy. Awesome.

Dumating ako sa airport at para sa ilang mga hindi kapani-paniwalang nakababagod dahilan, I had checked my luggage. I made it to LAX but my luggage did not. Sa akin, nawawala ang luggage ay isang maraming tulad ng pagpunta sa pamamagitan ng pitong yugto ng kalungkutan. Eventually I make it to the hotel, na walang luggage, pagod, gutom at suot ang aking (sa ngayon, napaka bayuot) business suit. It takes a long time to travel from Newark — to O’Hare — sa isang client — pabalik sa O'Hare — at sa wakas sa LAX.

Ako sa wakas mahanap ang aking sarili upo sa kuwarto hotel, munching sa isang bar paggalikgik, exhausted and trying to drum up the energy to scan through the training material again so that I won’t look like a complete ass in front of the class. This was a bit of a low point for me at the time.

Ako woke up sa susunod na araw, did my best to smooth out my suit so that I didn’t look like Willy Loman on a bad day and headed on over to the client. As is so often the case, sa tao siya ay magaling, polite and very pleasant. This stood in stark contrast to her extremely angry emails/voicemails from the previous day. She leads me about 3 miles through building after building to a sectioned off area in a giant chemical warehouse where we will conduct the class for the next three days. The 15 o 20 mga mag-aaral mabagal mag-ipon, most them still expecting Dennis.

Ako palaging simulan-off ang aking mga klase sa pagsasanay sa pamamagitan ng pagpapakilala ng aking sarili, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", Isulat ko ang aking pangalan, email and phone number up on the white board in big letters so that everyone can see it clearly. I address the fact that I’m replacing Dennis and I assure them that I am a suitable replacement, at iba pa. I have everyone briefly tell me their name and what they want to achieve out of the class so that I can tailor things to their specific requirements as I go along. The usual stuff.

We wrap that up and fire up the projector. I go to erase my contact info and … I had written it in permanent marker. I was so embarrassed. In my mind’s eye, ito ay mukhang ganito: There is this "Paul Galvin" tao, last minute replacement for our beloved Dennis. He’s wearing a crumpled up business suit and unshaven. He has just written his name huge letters on our white board in permanent marker. What a sight!

Ito ang lahat ng natapos na maligaya, gayunman. This was a chemical company, sa wakas. A grizzled veteran employee pulled something off the shelf and, malamang na lumalabag sa mga regulasyon EPA, cleared the board. I managed to stay 1/2 day ahead of the class throughout the course and they gave me a good review in the end. This cemented my "pinch hitter" reputation at my company. My luggage arrived the first day, kaya ako ay higit na mas maganda araw ng dalawa at tatlong.

Habang ako ay paglalaan ng red eye kamalig, I was contemplating "lessons learned". There was plenty to contemplate. Communication is key. Tell clients about changes in plan. Don’t ever check your luggage at the airport if you can possibly avoid it. Bring spare "stuff" in case you do check your luggage and it doens’t make it. I think the most important lesson I learned, gayunman, noon ito: laging subukan ang isang marker sa ibabang kaliwang sulok ng isang puting board bago magsulat, sa malaking titik, "Paul Galvin".

</dulo>

Due to some oddball United Airlines flights I took in the mid 90’s, I somehow ended up with an offer to transform "unused miles" into about a dozen free magazine subscriptions. That is how I ended up subscribing to Scientific American magazine.

Tulad ng software / pagkonsulta sa mga tao, we encounter many difficult business requirements in our career. Most the time, we love meeting those requirements and in fact, it’s probably why we think this career is the best in the world. I occasionally wonder just what in the world would I have done with myself if I had been born at any other time in history. How terrible would it be to miss out on the kinds of work I get to do now, at this time and place in world history? Sa tingin ko: pretty terrible.

Over the years, some of the requirements I’ve faced have been extremely challenging to meet. Complex SharePoint stuff, building web processing frameworks based on non-web-friendly technology, complex BizTalk orchestrations and the like. We can all (hopefully) look proudly back on our career and say, "yeah, that was a hard one to solve, but in the end I pwned that sumbitch!" Mas mahusay pa, even more interesting and fun challenges await.

I personally think that my resume, in this respect, is pretty deep and I’m pretty proud of it (though I know my wife will never understand 1/20th of it). But this week, I was reading an article about the Large Hadron Collider in my Scientific American magazine and had one of those rare humbling moments where I realized that despite my "giant" status in certain circles or how deep I think my well of experience, there are real giants in completely different worlds.

The people on the LHC team have some really thorny issues to manage. Consider the Moon. I don’t really think much about the Moon (though I’ve been very suspicious about it since I learned it’s slowing the Earth’s rotation, which can’t be a good thing for us Humans in the long term). Pero, the LHC team does have to worry. LHC’s measuring devices are so sensitive that they are affected by the Moon’s (Earth-rotation-slowing-and-eventually-killing-all-life) gravity. That’s a heck of a requirement to meet — produce correct measurements despite the Moon’s interference.

I was pondering that issue when I read this sentence: "The first level will receive and analyze data from only a subset of all the detector’s components, from which it can pick out promising events based on isolated factors such as whether an energetic muon was spotted flying out at a large angle from the beam axis." Really … ? I don’t play in that kind of sandbox and never will.

Next time I’m out with some friends, I’m going to raise a toast to the good people working on the LHC, hope they don’t successfully weigh the Higgs boson particle and curse the Moon. I suggest you do the same. It will be quite the toast 🙂

</dulo>