Kratka povijest SharePoint (Od relativno pridošlica perspektive)

Primijetiti: Ovaj članak je izvorno objavljen u www.endusersharepoint.com. Zaboravio sam to objaviti na svom blogu 🙂

SharePoint je evoluirala mnogo od svojih ranih dana, kao svojevrsno inkubacije tehnologije u Microsoftu –to je evoluirala gotovo kao horor filma, gdje je ludi znanstvenik kreacija se na vlastiti život, breaking free of its creator’s expectations and rules. The technical evolution is obvious – the WSS 3.0 Objektni model je bogatiji i složeniji od 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, međutim, SharePoint evolucija je još značajniji.

U ranim danima, 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, to slijedi relativno tradicijski način za krajnjeg korisnika <-> IT relationship. A lot of End Users, komunikaciju i rad s vrlo malim brojem ljudi nje da dostavi rješenja koja rješavaju poslovne probleme:

Ukupna Problem domene za koje SharePoint je pogodna isporuku platforme je mala (especially compared to today’s SharePoint. End Users and IT worked in a more classic arrangement with IT: definirati zahtjeve za IT, čekati za to rade svoj posao iza zavjese i uzeti isporuku finalnog proizvoda.

Kao SharePoint evoluirao 2.0 svijet (WSS 2.0 i SharePoint Portal Server), several things happened. Prvi, the “problem domain” increased in size. By problem domain, I mean the kinds of business problems for which SharePoint could be a viable solution. Na primjer, ne bi previše razmišljati o provedbi ozbiljnu pretragu rješenje u SharePoint okoliš dok SPS (pa čak i onda, to nije bio tako dobar kao što je potrebno kako bi se). Istovremeno, Krajnji korisnici imaju neviđenu sposobnost ne samo definirati, but also implement their own solutions with little or no IT support.

The 3.0 platforma (WSS i MOSS) maintained and increased that momentum. The problem domain is enormous as compared to the 2.0 platforma. Virtually every department in a company, u rasponu od proizvodnje zdravlja i sigurnosti odjela za marketing, od prodaje kontrole kvalitete - oni mogu naći dobro iskoristiti za SharePoint (a to nije slučaj gnječenje okrugli klin u rupu trgu). Istovremeno, 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, Krajnji korisnici su učinkovito sudac, porota i krvnik Poslovni analitičar, 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, razmotrimo slona u sobi.

Prodiranje u Crystal Ball

Kako će SharePoint 2010 utjecati na ovaj uzorak? Will it be incremental or revolutionary? Will more, manje ili približno isti broj krajnjih korisnika nađu ovlaštena za izgradnju rješenja u sustavu 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 / MOSS?

Ima dovoljno informacija "vani" za sigurno reći da general odgovor:

• The problem domain is going to dramatically expand.
• Krajnji korisnici će se naći još više ovlasti nego prije.

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.

Nema Bullsi u moju staklarni!

To zvuči odlično, , ali s moje točke gledišta kao SharePoint konzultant i ja stavljanjem u cipele IT menadžer, I see this vision. I own a China shop with beautiful plates, kristal, itd. (moj SharePoint okoliš). 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, ali u iščekivanju, 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 dva bulls and even a wolf. Then I notice that there are some sheep. Sheep are tako loše, , ali su oni možda prikriveno vukove? I don’t want bulls in my china shop!

To se pogoršava! When I rented the space, I couldn’t believe how nice it was. Wide and open, nevjerojatan pogodnosti, very reasonable price. Međutim, sad sam shvatio da prostranstvima i ogromna vrata je upravo savršeno veličine za bika doći lutanja i položiti otpada na moj Kini.

Ja sam gura ovu analogiju predaleko, naravno. End Users are not bulls (većina ih, u svakom slučaju) i IT odjeli ne (ili sigurno ne bi) view their user community with that kind of suspicion. Međutim, postoji ova vrsta savršen sudara odvija već u 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.

To je super i sve, , ali činjenica je da je još uvijek vrlo tehnički proizvod i dalje poziva na kakve energične poslovne zahtjeve analize, 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 će se promijeniti igru ​​malo i to će se igrati drugačije i usporeno kao tvrtke razvaljajte svoju SP 2010 Rješenja više 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, for instance. They need to understand fundamental concepts like CRUD (stvoriti, ažuriranje i brisanje), dev / test / K / prod okruženja i kako koristiti tu infrastrukturu kako bi ispravno implementirati rješenja koja žive lijepo dugo vremena i iskrivi (Ne provaliti) kao odgovor na promjene u organizaciji.

U narednim tjednima, Planiram probati i dati neke svoje nove ideje, , kao i link na velikom djelu učinio mnogo drugih autora (na www.endusersharepoint.com i drugdje) so that interested End Users can learn that old time IT religion. Keep tuned.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

[Primijetiti: Ovaj članak objavljen na cross- Krajnjeg korisnika SharePoint ovdje: http://www.endusersharepoint.com/2009/09/09/sharepoint-a-case-study-in-ask-the-expert/]

Ponekad, kada radite kao konzultant (kao zanimanje, ili u savjetodavnu ulogu u vašoj tvrtki), you find yourself living in an Onion story. The Onion has a series of articles called “Ask an [stručnjak] oko [neki problem]". This follows the famous “Dear Abby” format where a concerned person is asking for personal advice. The onion’s “expert”, međutim, 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, ali dolaze u dodir s ljudima koji su ozbiljni profesionalci u svojoj ulozi, but are not consultants. They don’t have the same need or training to do otherwise.

Prošli tjedan, Sam pisao o jednom od moje tvrtke klijentima i da će projekt 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:

• Nekolicina pojedinaca na različitim liječničkim praksama koje mogu ući troškove na liniji.
  • Postoji više od 40 liječničke prakse.
  • Na nekim praksi, liječnik koristi sustav izravno.
  • Na mnogim praksama, na liječnička osoblje koristi sustav izravno.
• Financijska administrator (koji radi za moj klijent izravno) koji provjerava troškove za točnost i relevantnost, odobrava ili odbija ih na organizacijskoj razini.
• 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, Objasnio sam potrebu da se na obveze prema dobavljačima društva:

• Kliničke studije stranice (liječničke prakse) nastati troškovi studija-.
• They log onto the “web site” and enter their expenses using an online form. U tom slučaju, the “web site” is hosted with SharePoint and the expenses are entered into an InfoPath form. Expense receipts are scanned, postavljena i priključen izravno u obliku.
• Automatizirani proces tijek traži odobrenje odgovarajućeg financijskog administratora.
• Vi, dear 3rd party AP company – please review and approve or deny this expense. I’ll send it to you any way that you want (u roku od razloga).U ovom trenutku u raspravi, 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.

Kad sam objasnio potrebu, 3. Stranka je duboko zaroniti u svom unutarnjem mumbo jumbo žargon o troškovima odobrenja procesa, Oracle kodovi, potpredsjednika potpisa, 90 dan turn-zaobilazna, itd.. 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, osim što nisu srušene za život nakon iskustva (iako ulazak u um AP menadžera nije šetnja po parku 🙂 [vidi značajnu notu ispod ***] ).

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, kao konačni obveznik, vidjeti sve pojedinosti o trošku? 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? Mogu li ponovno ovu trošak Godinu dana kasnije, ako i kad sam se revidiraju i treba braniti plaćanje?

Kao SharePoint ljudi, we can see how to answer those questions. In my client’s case, ćemo odgovoriti na njih više ili manje kao što je ovaj:

• InfoPath obrazac kako bi se omogućilo web stranice kako bi snimili svoje troškove te ih podnijeti na odobrenje.
• Mjesta mogu se vratiti na mjesto kako biste vidjeli status svoje izvješće troškova u bilo koje vrijeme.
• Kako doći do značajnih događaja (e.g. Troškovi se odobrava i podnosi za plaćanje), Sustav proaktivno ih obavijesti putem e-maila.
• Sustav obavještava financijski administratoru jednom izvještaj podnesen na odobrenje.
• Financijski administrator odobrava ili odbija zahtjev.
• Nakon odobrenja, rashodi u paketu se u poruci e-pošte i poslati na 3rd party platitelja organizacije.
• 3. stranka obveznik ima sve informacije koje su potrebne za ocjenu troškove i mogu pristupiti SharePoint okoliš da kopaju u detalje (prvenstveno reviziju povijesti za provjeru "istina" od troškova).
• 3rd party payer can approve or reject the payment using their own internal process. They record that outcome back in the SharePoint site (koji izaziva obavijest e-poštom na odgovarajuće osobe).
• U budućnosti, bilo bi lijepo izrezati ovu tiho e proces i umjesto hrane troškova podatke izravno u sustav.

U zaključku, postoji stil života ovdje da opišem od stručnog konzultanta gledišta, 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, više nego često ne, ćete biti u mogućnosti odgovoriti na pitanja i ponuditi načine kako unaprijediti svačiji radnog dana utjecati osnovne značajke SharePoint.

***Važna napomena: I really don’t mean to compare AP people to serial killers. Međutim, 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?"

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

[Primijetiti: ovaj blog post je križ postavljen na Marka Millera stranice ovdje: http://www.endusersharepoint.com/?p = 1897]

Jedan od Moja tvrtka je više neobične klijenti je New York City liječnik koji je lider u svom određenom području medicine (očnog). 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, ali vjerujem da je SAD-a. government is probably the largest source of funding. Kao i sve, resources are scarce. Many doctors across the country want to perform research and trials. Kao rezultat toga, 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, zatim, sign up for a particular study. The relationships look like this:

• Jedan majstor organizacija.
• Mnogo različitih liječnika praksi se prijavite sa master organizacije.
• The master organization obtains funding for individual studies. At the outset, postoji samo jedna studija na određeni rijetke bolesti oka iako smo već ramping na drugoj studiji.
• Individual doctors’ practices sign up for specific studies. A specific practice could sign up for one or multiple studies.

Glavni sama organizacija je oborio u skupine:

• Izvršni odbor
• Upravni odbor
• Pojedini studijski odbori
• Uprava
• drugi

Konačno, Kad određena liječnička praksa prijavi za sudjelovanje u istraživanju, oni moraju osigurati stručnjake ispuniti različite uloge:

• Istražitelji (uključujući osnovne istražitelja, inače liječnik, zajedno s jednim ili više dodatnih istražiteljima)
• Koordinatori
• Tehničari
• Potpore administratori
• drugi

The above roles have very specific and highly proscribed roles that vary by study. I won’t get into more detail here, ali ako ste zainteresirani, ostavite komentar ili elektronička pošta mene.

I sada mogu odgovoriti na pitanje, SharePoint - Što je to dobro za? The answer – it’s really good for this scenario.

Ovaj uvod je već više od očekivanog, pa ću prikazati vitalnu ulogu koju igra u SharePoint rješenja i uronite u detalje u budućnosti članak (ako ne mogu čekati, elektronička pošta mene ili ostavite komentar i ja ću biti sretan da raspravljaju i možda čak i pokušati napraviti demo). We are leveraging a wide array of SharePoint features to support this concept:

• Mjesta za odborima, pojedinačne uloge (koordinator stranice, Istraživač stranice, itd.).
• Sigurnosti kako bi bili sigurni da su različite prakse ne vidim drugih praktična rješenja "podataka.
• InfoPath forms services for online form entry. This is a particularly big win. Normalno, ovim teškim oblicima tiskani su, poslan u praksi, filled out and mailed back. The advantages to the online forms are obvious. They do introduce some complexities (licenciranje i ljudskih) ali to je druga priča.
• Od dijelova kutije web, kao i najavama (Kada odbor [x] susresti?) i ispunjavanje radnih mjesta.
• Obrasci provjera autentičnosti utemeljena u kombinaciji s alatom CodePlex kako bi osigurao sebi registracije i lozinku zaboraviti značajke.
• Prilagođene liste i popis pregleda za uvid u studijske aktivnosti koje jednostavno nije moguće s čistim papirom i olovkom pristupi.

Uz iznimku od oblika baziranu provjeru autentičnosti modula i pregršt InfoPath obrazaca, ovaj projekt koristi gotovo sve od funkcionalnosti kutija SharePoint.

Prije nego što sam završiti ovu min-studija slučaja, Želim istaknuti nešto vrlo važno - nema na uključeni u ovaj projekt (osim moje tvrtke, naravno) 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, ali učinio pravo, that’s irrelevant to end users. They need a problem solved, ne divna blob tehnologije.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Ili je to samo mene? 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, pa koliko ja znam.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Zatvaranje mislila na ovaj drugi način glup članak govori i do problema često se susreću u tehničkoj zajednici:

"Such dreary developments, Predviđa se sa sigurnošću, Treba imati filozofski."

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" poslovni zahtjevi i netko u publici pitali, važeći, what to do if circumstances are such that it’s impossible to get great requirements. Na primjer, neko poduzeće kultura stavlja je ispred zahtjeva sakupljaču / Poslovni analitičar, 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. Međutim, 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, tako da je realnije (iako je užasno bolno i drastičan) for me to walk away. Međutim, ako ste ukorijenjeni u društvu i ne žele, ili se ne može, odšetati, George (jednom 🙂 ) pokazuje put.

</kraj>

Pretplatite se na moj blog.

Slijedite me na Twitter-u http://www.twitter.com/pagalvin

Koliko često se ovo dogoditi da vas? I’m sitting at my laptop, čitajući blogove, reagirati na forum postove, 2 kopije Visual Studio otvoren i VPN'd se na drugi poslužitelj s vlastitim Visual Studio + 15 browser prozore (Tipičan dan) i netko zove Samantha (moja supruga, izgleda) mi govori, "Mi smo se tamo u 30 minuta. Get dressed."

Ustajem u omamljen, lutaju oko kuće zbunjeno, dobiti u auto i sljedeća stvar znam, Ja sam na zabavi s piva u ruci, a netko me pita, "Tako, Kako zarađujete za život?"

Ti razgovori nikada ne idu dobro.

Me: "Ahh … Ja sam arhitekt rješenja za EMC."

Bezimeni osoba: stara prazno

Me: "Radim s proizvodom pod nazivom SharePoint … to je iz Microsofta."

NP: "Aha! Čuo sam od te tvrtke! What is SharePoint?"

Me: "Umm … čini suradnju … ljudi ga koristiti za razmjenu informacija … To je platforma za izgradnju poslovanju sol…"

NP: Oči staklo.

Me: "Ja sam programer."

NP: "Aha! I know people in my company that do programming! When I was in high school, Igrao sam s oko BASIC."

I s tom dijelu razgovora tijekom, skrećemo na nešto lakše govoriti o, kao i politike.

Svatko njega opisati kako ih nositi ovu?

</kraj>

Pretplatite se na moj blog.

Ja sam bio u razredima ovih zadnjih dva tjedna, a jedna stvar koja me udari je da postoji mnogo promišljeni, pametni ljudi rade na SharePoint (kao savjetnika ili informatičkog osoblja) koji ne blog, cvrkut, Čini svjesni javnim forumima poput MSDN forumu ili SharePoint Sveučilišta, održavati Facebook ili LinkedIn profile, itd.. They are pure information consumers. Not bad, samo zanimljivo.

</kraj>

Pretplatite se na moj blog.

Hrpa godina, 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. U vrijeme, to je dizajniran za rad na zelenim cijevima (e.g. Wyse 50 terminal) connected to a Unix box via telnet.

My default answer to any question that starts with "Can you … " is "Yes" i to je mjesto gdje sve nevolje započeo.

Klijent je kemijska tvrtka u južnoj Kaliforniji, a upravo o zavrsio veliki ERP provedbu na temelju QAD je 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. Međutim, Imao sam provela niz drugih trening klase i bio brz na nogama, so I was not too worried. Dennis, pravi punim radnim vremenom Rezultati instruktor, 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?

Za komplicirati stvari logistički, 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, ići u Chicagu, meet for an hour with prospect and then continue on to California.

Dobro, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Tako, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, Ja saznali da klijent uči manje od 24 hours before my arrival that "Paul Galvin" predaje razred, 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 "daju lošu vijest rano" philosophy. Awesome.

Ja stići u zračnu luku i za neke nevjerojatno glupe razloga, I had checked my luggage. I made it to LAX but my luggage did not. Za mene je, gubitka prtljage je puno poput prolazi kroz sedam faza tuge. Eventually I make it to the hotel, bez prtljage, umoran, gladni i nosi moje (do sada, vrlo zgužvao) business suit. It takes a long time to travel from Newark — do O'Hare — za klijenta — natrag na O'Hare — i na kraju LAX.

Napokon sam pronaći sebe sjedi u hotelskoj sobi, munching na snickers bar, 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.

Probudio sam se sljedeći dan, 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, osobno ona je bila lijepa, 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 ili 20 Studenti se polako okupljaju, most them still expecting Dennis.

Uvijek sam krenuti moje tečajeve obuke po sebi predstavlja, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", Pišem moje ime, 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, itd.. 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, izgledalo je ovako: There is this "Paul Galvin" osoba, 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 trajni biljeg. What a sight!

Sve je završilo sretno, međutim. This was a chemical company, uostalom. A grizzled veteran employee pulled something off the shelf and, Vjerojatno u kršenje propisa 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, tako da sam bio puno više naočit dana dva i tri.

Kao što sam bio uzimajući crvenih očiju vratiti kući, 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, međutim, bio je to: Uvijek testirati marker u donjem lijevom kutu bijelom brodu prije pisanja, u ogromnim slovima, "Paul Galvin".

</kraj>

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.

Kao softvera / savjetovanje osoba, we encounter many difficult business requirements in our career. Most the time, volimo ispunjava ove zahtjeve i zapravo, 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, u ovo vrijeme i mjesto u svjetskoj povijesti? Mislim: prilično strašno.

Tijekom godina, some of the requirements I’ve faced have been extremely challenging to meet. Complex SharePoint stuff, izrada web obrada okviri temelje na ne-web-friendly tehnologiju, complex BizTalk orchestrations and the like. We can all (nadajmo se) izgleda ponosno vratiti na naše karijere i reći, "yeah, to je teško pitanje za rješavanje, ali na kraju sam pwned da sumbitch!" Better yet, još zanimljivih i zabavnih izazovi čekaju.

Ja osobno mislim da je moj životopis, u tom pogledu, je prilično duboko, a ja sam prilično ponosan na nju (iako znam da moja žena nikada neće shvatiti 1/20th od njega). But this week, Čitao sam članak o Large Hadron Collider in my Scientific American magazine and had one of those rare humbling moments where I realized that despite my "giant" status u nekim krugovima ili koliko duboko mislim da mi je dobro iskustvo, 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 (iako sam bio vrlo sumnjičav o tome jer sam saznao da je usporavanje Zemljine rotacije, koji ne može biti dobra stvar za nas ljude u dugom roku). Ali, the LHC team does have to worry. LHC’s measuring devices are so sensitive that they are affected by the Moon’s (Zemlje-rotacije usporavanje-a-vremenom-ubijanje-sve-život) gravity. That’s a heck of a requirement to meet — proizvesti ispravne mjerenja unatoč Mjesečeve smetnji.

Razmisljao sam taj problem kad sam pročitao ovu rečenicu: "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.

Sljedeći put sam se s nekim prijateljima, Ja ću podići zdravicu s dobrim ljudima koji rade na LHC-u, hope they don’t successfully weigh the Higgs boson particle and curse the Moon. I suggest you do the same. Bit će to pravi tost 🙂

</kraj>