Quick & Erraza: Sortu karpeta bat eta Eduki mota bat esleitu (Edo, Zure KPIs eta beraiekin jan ere)

In order to work around a KPI problem I wrote about here, I did some testing and discovered that KPI’s work against folders with meta data in the same way that they work against documents or list items. I proved it out by creating a new content type based on the folder content type and then added a few fields. I created some indicators and proved to myself that KPIs work as expected. This was welcome news. It’s not perfect, because the drill-down you get from the KPI against the folders is not exactly what you want. This isn’t too much a drawback in my case because 1) erabiltzaileek ez dakite edozein hobeto eta 2) the drill-down goes to a folder. They click the folder name and they are at the item. It’s two clicks instead of one, eta hori ez da munduaren amaiera.

This flowed nicely with the work I was doing. I am creating a folder for every document that gets uploaded. This is done via an event receiver. Baten ondorioz, bat tarta zati mantentzen da karpeta gurasoa en meta data in sync with the KPI-driven meta data from the file itself since the plumbing is already in place. This allows me to have my KPI’s and eat them too 🙂

I modified the event receiver to add the folder and then set this new folder’s content type to my custom KPI-friendly content type. This bit of code did the trick:

 SPFolderCollection srcFolders = targetWeb.GetFolder("Documents").Azpikarpetak;
  SPFolder addedFolder = srcFolders.Add(properties.ListItem.ID.ToString());
  SPContentTypeId kpiCT = berria SPContentTypeId("0x0120002A666CAA9176DC4AA8CBAA9DC6B4039F");
  addedFolder.Item["Content Type ID"] = KpiCT;
  addedFolder.Item.Update();

Benetako Eduki mota ID lokalizatu, Eduki gune ezarpenak eta kopia bidez mota / itsatsi ezazu URL from orokorrak gisa sar dut:

image

</amaiera>

Nire blog Harpidetu!

Technorati Tags: ,

Azkarra eta erraza: Talde SPListItem baten SPFolder gertaera hargailuen batean

Aitortzen gorroto dut, but I struggled with this one all day. My event receiver needs to update a field of its parent folder. This little bit shows how to do it:

pribatua gal UpdateParentFolder(SPItemEventProperties propietate)
{

SPFolder thisItemFolder = properties.ListItem.File.ParentFolder;
thisItemFolder.Item["ZZ Approval Status"] = "Good news, guztiontzat!";
thisItemFolder.Item.Update();


} // UpdateParentFolder

Kasu honetan, Dokumentu liburutegi batekin ari naiz lanean, eta propietate dira ItemAdded gertaera datozen.

Tranpa da, ezin dela lortu Elementu SPFolder zuzenean elementua bera (I.E. properties.ListItem.Folder null). Horren ordez, du zerrendako elementu horrek lotutako File joan eta fitxategi horrek karpeta lortu.

</amaiera>

Nire blog Harpidetu!

Technorati Tags:

Yet Another Gertaera hargailuen Araztu Trick

I’m sure I’m not the first person to come up with this. Hala eta guztiz ere, I haven’t noticed anyone publish a trick like this since I started paying close attention to the community last July. Beraz,, Hau da, azkarra eta erraza arazketa punta bidaltzeko nuela pentsatu nuen.

Gertaera baten hartzailea duten hasi akats hau sortzeko nabil 12 hive:

Errorea kargatu eta exekutatzen gertaera hartzailea xyzzy en Conchango.xyzzyEventReceiver, 1.0.0.0 bertsioa =, Kultura = neutrala, PublicKeyToken = blahbalhbalh. Additional information is below. : Objektu erreferentzia ez objektu baten instantzia bat ezarri.

I didn’t know where I had introduced this bug because I had done too many things in one of my code/deploy/test cycles.

Saiatu dut irtenbide hau nire pdb lortzeko hor itxaropen dituzten SharePoint-en 12 hive automatikoa erakutsiko luke, but no luck. I don’t know if it’s possible and if someone does, please let me know 🙂

Posible al da, ezagutzen dut idatzi, zure log mezuak 12 hive. Frankly, Zerbait apur bat gutxiago scary eta azkarrago ezartzea nahi dut.

Gertatu zait ezin dudala gutxienez lortu zenbait aztarna oinarrizko informazioa eta harrapatzeko berriro bota hau bezalako salbuespenak by generic:

  saiatu {
    UpdateEditionDate(propietate);
  }
  harrapatzeko (Salbuespen eta)
  {
    bota berria Salbuespen("Dispatcher, UpdateEditionDate(): Salbuespen: [" + e.ToString() + "].");
  }

Honek erakutsi du parte 12 hive thusly:

Errorea kargatu eta exekutatzen gertaera hartzailea xyzzy en Conchango.xyzzyEventReceiver, 1.0.0.0 bertsioa =, Kultura = neutrala, PublicKeyToken = blahblahblah. Additional information is below. : Aztergailu, UpdateEditionDate(): Salbuespen: [System.NullReferenceException: Objektu erreferentzia ez objektu baten instantzia bat ezarri. at Conchango.xyzzyManagementEventReceiver.UpdateEditionDate(SPItemEventProperties propietate) at Conchango.xyzzyManagementEventReceiver.Dispatcher(SPItemEventProperties propietate, Katea eventDescription)].

Eman zidan xehetasun behera jarraitzeko bereziki arazo hori behar nuen guztia, eta erabili asko aurrera joatea espero dut.

</amaiera>

Nire blog Harpidetu!

Igandea Funny: “EZ esportatzeko”

Itzuli inguruan 1998, the company I worked for at the time received some funding to create a new e-commerce product. We had the full gamut of business requirements to meet. It had to be fast, azken erabiltzaileei erraza, flashy, multi-hizkuntza, etc. Sad to say, Seguru asko ez dut lan handinahi multzo bat bezala izan nahi dutenek ilusio hura betetzeko egun noiztik.

This effort pre-dated Microsoft.NET. Plain vanilla ASP was still somewhat new (edo, behintzat, oso nire enpresari Ohituta). "Brick and mortar" companies were doomed. Kondenatuta! This is to say that it was pioneering work. Partikula ez Collider aitzindari lana, baina gure mundu txiki batean, lana izan zen aitzindaria.

We were crazy busy. We were doing mini POC’s almost every day, out nola kalkulatzen egoera mantentzeko bat berez estaturik gabeko ertain, out kalkulatzen multi-hizkuntza gaiak, row-level security. We even had create a vocabulary to define basic terms (Egoera-iraunkorrak nahiago dut, baina arrazoiren batengatik, the awkward "statefull" irabazi eguna).

Ginen madly produktu hau asmatuz, the marketing and sales people were out there trying to sell it. Somehow, they managed to sell it to our nightmare scenario. Even though we were designing and implementing an enterprise solution, we really didn’t expect the first customer to use every last feature we built into the product day zero. This customer needed multi-language, a radically different user interface from the "standard" system but with the same business logic. Multi-language was especially hard in this case, beti gaztelaniaz edo frantsesez delako zentratu, baina kasu honetan, Txinako zen (horietatik bi byte karaktere eta behar bereziak manipulazio ematen dugu teknologia erabiltzen da).

Fast forward a few months and I’m on a Northwest airlines flight to Beijing. I’ve been so busy preparing for this trip that I have almost no idea what it’s like to go there. I had read a book once about how an American had been in China for several years and had learned the language. One day he was walking the city and asked some people for directions. The conversation went something this:

  • American: "Could you tell me how to get to [XX] kalean?"
  • Txinako: "Sorry, we don’t speak English".
  • American: "Oh, Mandarin ondo hitz egiten dut." eta haiei galdetu zuen berriro txineraz, baina argi eta garbi (onena izan zitekeen).
  • Txinako: Oso adeitsuki, "Sorry, we don’t speak English".

The conversation went on like that for bit and the American gave up in frustration. As he was leaving them he overheard one man speaking to the other, "I could have sworn he was asking for directions to [XX] kalean."

I had picked up a few bits and pieces of other China-related quasi-information and "helpful advice":

  • A Korean co-worked told me that the I needed to be careful of the Chinese because "they would try to get me drunk and take advantage of you" Niri pressuring negozio txarra erabakiak sartu zentzuan.
  • Dugu, ez ziren onartzen autoak gidatzeko (ez zen zenbait gisa nahasmena hau ote zen ohitura, legezko baldintza edo, besterik gabe, bezeroaren arau).
  • Baziren ohiturak igaro arau bereziak.
  • Dugu, ez ziren onartzen American dirua erabili nahi ezer.
  • You’re not supposed to leave tips. It’s insulting if you do.

Eta, azkenik,, Oroitzapenak nahiko freskoa izan dut Tiananmen sarraskia. When I was at college, I remember seeing real-time Usenet postings as the world looked on in horror.

Laburbilduz, I was very nervous. I wasn’t just normal-nervous in the sense that I was delivering a solution that was orders of magnitude more complicated than anything I had ever done before. I was also worried about accidentally breaking a rule that could get me in trouble.

Ni honetan I 14 orduko hegaldia eta zen enpresa klase nahiz, 14 ordu bat madarikatuak denbora luzea da. Besterik ez dira, beraz, modu asko zeure burua entretenitua irakurriz, watching movies or playing with the magnetized cutlery. Even a really good book is hard to read for several hours straight.

Azkenean, Ontzi-materiala irakurtzeko software pieza bat hasi dut nirekin bezeroaren esku-liburuetan izan dut, Netscape’s web server. I’m reading the hardware/software requirements, marketing blurbs du, argazki polita da eta bat-batean, bilatzen, I zero in on the giant "NOT FOR EXPORT" abisua, zerbaiti buruz 128 bit encryption. I stuffed the box back into my carry bag, aurpegia behera abisua (balitz bezala, lagundu duten zukeen) eta saiatu ikuspegi mantendu Midnight Express out of my head.

Atzera begira orain, Aukeratu behar izan nuen, kezkatuta, ez badu, denean US utzi nuen, not when I was entering China 🙂 Nothing untoward happened and I still consider that to be the best and most memorable business trip I’ve had the pleasure of making.

</amaiera>

Nire blog Harpidetu!

Technorati Tags: ,

Irtenbidea: SPQuery ez da bilaketa-karpetak

This past week I was implementing an "evolving" solution for a client that uses BDC and SPQuery and ran into some difficulty using SPQuery against a document library containing folders. Behean line: assign "recursive" bilaketara atributua ikuspegian.

Nire agertokia:

  • Astelehenean, Dokumentu bat igo dut, eta meta-datu batzuk hornitzeko.
  • Ondorengo astean, I upload a new document. Much of this new document’s meta data is based on the document I uploaded on Monday (which we call the "master document").
  • Sortu dugu, web-zerbitzu fatxada duten BDC errespetatzen interfaze bat eskaintzen du zerrenda hori, beraz, erabiltzaileek erraz kokatzeko Astelehena dokumentua izenburua bilaketa baten bitartez.
  • A BDC data column provides a friendly user interface. (Hau nire saiakera parte da BDC erabiliz Lookup gehiago errespetatzen zutabean at).

Amaierako BDC fatxada kontsulta zerbitzu bat erabiltzen du horrelako bilaketak egiteko:

 // Erabiltzen U2U tresna CAML kontsulta hau sortzen lagundu.
      oQuery.Query =
        "<Non>";

      bada (titleFilter.Length > 0)
        oQuery.Query   =
          "  <Eta>";

      oQuery.Query   =
        "    <Eta>" +
        "      <Geq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + MinID + "</Balio>" +
        "      </Geq>" +
        "      <Leq>" +
        "        <FieldRef Name=\"DocumentId\" />" +
        "        <Value Type=\"Text\">" + maxId + "</Balio>" +
        "      </Leq>" +
        "    </Eta>";

      bada (titleFilter.Length > 0)
        oQuery.Query   =
          "    <Dauka>" +
          "      <FieldRef Name=\"Title\" />" +
          "      <Value Type=\"Text\">" + titleFilter + "</Balio>" +
          "    </Dauka>" +
          "  </Eta>";
      oQuery.Query   =
        "</Non>";

Garapenaren hasierako fasean, this worked great. Hala eta guztiz ere, karpetak sartu dugu direktorioa arazo batzuk konpontzeko, eta bat-batean, my BDC picker wouldn’t return any results. I tracked this down to the fact that the SPQuery would never return any results. We used folders primarily to allow multiple files with the same name to be uploaded but with different meta data. When the file is uploaded, zerrenda-elementua ID oinarritutako karpeta bat sortuko dugu, eta ondoren fitxategia eraman (Idatzi dut hemen; izan dugu mistoak emaitzak Planteamendu honekin, baina, oro har,, ondo ari da lanean). The user don’t care about folders and in fact, don’t really understand that there are any folders. We have configured all the views on the library to show items without regard to folders.

I hit this problem twice as the technical implementation evolved and solved it differently each time. The first time, I wasn’t using the CONTAINS operator in the query. Without a CONTAINS operator, I was able to solve the problem by specifying the view on the SPQuery’s contructor. Instead of using the default constructor:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = berria SPQuery();

Ordez erabiltzen dut eraikitzaile bat zehaztu ikuspegi bat:

SPList oList = web.Lists["Documents"];

SPQuery oQuery = berria SPQuery(oList.Views["All Documents"]);

Hori arazoa konpondu eta nire emaitzak lortzeko hasi nintzen.

I then added the CONTAINS operator into the mix and it broke again. It turns out that the CONTAINS operator, orain arte bezala dizut, ez du ikuspegian lan egiteko modu berean bat GEQ errazagoa gisa / LEQ operators. I did some searching and learned that the query’s ViewAttributes should be set to "Recursive", bezala:

oQuery.ViewAttributes = "Scope=\"Recursive\"";

That solved the problem for CONTAINS. Izan ere,, hori ere konpondu nire jatorrizko bilaketa, arazo eta nuen zehazten recursive atributua lehenengo aldiz, Dut, ez luke alean sartu exekutatu berriro.

Izan ere, ikuspegi oinarritutako SPQuery bat operadore batzuen lanak (GEQ/LEQ) eta ez beste batzuk (CONTIENE), Izan ere, gero KPIs hori ez dirudi lan guztiak karpeta duten dokumentu liburutegi batekin eramaten uste SPQuery duela orthogonality gai batzuk ninduen.

Berezia esker:

  • Ona Folks at U2U eta beren kontsulta-tresna.
  • Michael Hoffer handia "egiten ikasteko" blog post, iruzkinak eta erantzunak.

</amaiera>

Nire blog Harpidetu!

MOSS KPI bug? Zerrenda adierazle Dokumentu liburutegia lotuta karpeta

UPDATE 02/29/08: I solved this problem by creating a folder and then assigning a content type to the folder which has the meta data I need for the KPIs. Duten deskribatzen dut Xehetasun gehiagorekin hemen.

We have implemented a technical solution where users upload documents to a document library. An event receiver creates a directory and moves the file to that directory (teknika bat zer idatzi nuen antzekoak erabiliz hemen). We’ve successfully navigated around the potential issues caused by event receivers that rename uploaded files (mainly because users never start their document by clicking on "New" baina horren ordez sortu docs lokalean eta gero igo).

The meta data for these documents includes a Yes/No site column called "Urgent" and another site column called "Status". We need to meet a business requirement that shows the percentage of "Urgent" documents whose status is "Pending".

Normalean erraz egin eta zerbait deskribatu dut oso atsegin dute hau SharePoint Beagle hartan pantaila plano asko galtzen interesa duten bazara.

Hitz batean, Honako hau egin nuen:

  • Create a view on the doc library called "Pending".
  • Konfiguratu ikuspegia karpeta-egitura ez ikusi egin.
  • Sortu KPI zerrenda bat.
  • Create an indicator in the list that points to the doc lib and that "Pending" ikusteko.

This simply does not work. The KPI shows my target (e.g. bost premiazko dokumentuak) but always shows the actual number of urgent documents as zero. Paradoxically, zulatzeko edukiz xehetasunak, it shows the five urgent documents in the list. I created a very simple scenario with two documents, one in a folder and one not. Here is the screen shot:

image

The above screen shot clearly shows there are two documents in the view but the "value" is one. The "CamlSchema" with blank document Id is in the root folder and the other is in a folder named "84".

Agertzen zait, nahiz eta duten ikuspegi bat zehaztu behar duzu, the KPI doesn’t honor the "show all items without folders" eta ezarpen ordez, mugarik berez erro karpeta.

Dut oker bada, mesedez, jaregin me lerro bat edo iruzkina utzi.

</amaiera>

Nire blog Harpidetu!

Technorati Tags:

SPD Workflow “Erabiltzaile biltzeko, datuak”: Aldatzeko sortutako Task formularioa

I’m working on a project that uses five different SharePoint Designer work flows to handle some document approvals. SPD provides the "collect data from a user" ekintza da, beraz, informazio-bit desberdinak erabiltzaileari galdetuko dezakegu, onetsiko dira, hala nola, bertan duzun, zenbait iruzkin eta agian zer eskatu zuten afaria beste gau.

The forms are perfectly functional. They are tied to a task list as a content type. Dira 100% system-generated. This is their strength and weakness. If we can live with the default form, then we’re good to go. Hala eta guztiz ere, we don’t have too much control over how SPD creates the form. If we don’t like that default behavior, hainbat trikimailu jotzea da mugitu behar dugu (adibidez, lehentasuna ezartzeko zeregin batean).

Zeregin bat inprimaki horietan lotura duten ikuspegi ireki propietate eman behar nuen (dispform.asxp) of the "related item" in a new window. This provides one-click access to the meta data of the related item. This is what I mean:

image

Zorionez, we can do that and it’s not very hard. Broadly speaking, sua sortu SPD, navigate to the directory that houses the workflow files and open the ASPX file you want to modify. These are just classic XSL transform instructions and if you’ve mucked about with itemstyle.xsl, bilaketa edo beste XSL eszenatoki, this will be easy for you. Izan ere,, Izango da, oro har, errazago aurkitu dut sortutako forma zertxobait errazagoa baita bilaketa-core emaitzak web parte aldean jarraitu behar (edo nightmarish CWQP).

Jakina, there is one major pitfall. SPD’s workflow editor expects full control over that file. If you modify it, SPD will happily overwrite your changes give the right set of circumstances. I did two quick tests to see how bad this could get. They both presuppose that you’ve crafted a valid SPD workflow that uses the "collect data from a user" urratsa.

Test 1:

  • Aldatzeko eskuz fitxategia ASPX du.
  • Probatu ezazu (egiaztatu diren aldaketak behar bezala gorde, eta ez du ezer apurtu).
  • Ireki workflow eta kanpoko ekintza bat gehitu (such as "log to history").
  • Gorde eu.

Emaitza: Kasu honetan, SPD ez da berriro sortu inprimakia.

Test 2:

  • Bera egiten gisa #1 except directly modify the "collect data from a user" Ekintza.

Emaitza: Hau hutsetik formularioa re-sortzen, Zure aldaketak baino gehiago idazten.

Final Oharrak:

  • Gutxienez bi SPD sortzeko ekintza hau bezalako forma: "Collect Data From a User" and "Assign To Do Item". Both of these actions’ forma eskuz alda daiteke.
  • Gai nire dispform.aspx lotura sortu nahi izan dut delako, kasu honetan, the relate item always has its ID embedded in the related item’s URL. I was able to extract it and then build an <href bat> based on it to provide the one-click meta data access feature. It’s unlikely that your URL follows this rule. There may be other ways to get the ID of the related item but I have not had to cross that bridge, beraz, ez dakit leizetik beste aldean bada lortzen.
  • Ez dut ikertu, baina ez nuke ez da harritu batzuk txantiloi fitxategi mota badago 12 hive SPD nola sortzen lehenetsi forma eragin hori ezin dut aldatu (askoz bezala alerta txantiloiak alda dezakegu).

</amaiera>

Nire blog Harpidetu!

Technorati Tags: ,

Dira “Akats ezezaguna” Mezuak Benetan Stack Trace bat baino hobea?

Madhur bloga zer nintzen irakurtzen nola an automatikoa gaitu pantailetan eta orain galdetzen dut: zergatik ez erakutsi dugu beti pila arrastorik?

Nor zen, arau hori, eta zergatik jarraitu dugu?

End users will know something is wrong in either case. At least with a stack trace, sakatu kontrol-printscreen daitezke, copy/paste into an email and send it to IT. That would clearly reduce the time and effort required to solve the issue.

</amaiera>

Technorati Tags:

Igandea (Lotsa) Funny: “Nire izena da Paul Galvin”

A bunch of years ago, 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. At the time, it was designed to run on green tubes (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" and that’s where all the trouble started.

The client was a chemical company out in southern California and had just about wrapped up a major ERP implementation based on QAD’s 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. Hala eta guztiz ere, I had conducted a number of other training classes and was quick on my feet, so I was not too worried. Dennis, the real full-time Results instructor, had given me his training material. Atzera begira orain, 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?

To complicate things 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, go to Chicago, meet for an hour with prospect and then continue on to California.

Beno, I got to Chicago and the sales guy on my team had made some mistake and never confirmed the meeting. Beraz,, I showed up and the prospect wasn’t there. Awesome. I pack up and leave and continue on to CA. Somewhere during this process, I find out that the client is learning less than 24 hours before my arrival that "Paul Galvin" is teaching the class, 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 "albiste txarra eman hasieran" philosophy. Awesome.

I arrive at the airport and for some incredibly stupid reason, I had checked my luggage. I made it to LAX but my luggage did not. Niretzat, losing luggage is a lot like going through the seven stages of grief. Eventually I make it to the hotel, with no luggage, tired, hungry and wearing my (by now, very crumpled) business suit. It takes a long time to travel from Newark — to O’Hare — to a client — back to O’Hare — and finally to LAX.

I finally find myself sitting in the hotel room, munching on a 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.

I woke up the next day, 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, in person she was nice, 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 edo 20 students slowly assemble, most them still expecting Dennis.

I always start off my training classes by introducing myself, giving some background and writing my contact information on the white board. As I’m saying, "Good morning, my name is Paul Galvin", I write my name, 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, etc. 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, it looked like this: There is this "Paul Galvin" person, 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!

It all ended happily, Hala ere,. This was a chemical company, azken finean. A grizzled veteran employee pulled something off the shelf and, probably in violation of EPA regulations, 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, so I was much more presentable days two and three.

As I was taking the red eye back home, 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, Hala ere,, was this: always test a marker in the lower left-hand corner of a white board before writing, in huge letters, "Paul Galvin".

</amaiera>

Technorati Tags: ,

Perspektibak: SharePoint vs. Handia Partikula Collider

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.

Software gisa / aholkularitza pertsona, we encounter many difficult business requirements in our career. Most the time, eskakizun horiek bilera-maite dugu, eta hain zuzen ere,, 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, Une honetan, eta munduan historian at? Uste dut: nahiko terrible.

Urteetan zehar, some of the requirements I’ve faced have been extremely challenging to meet. Complex SharePoint stuff, Eraikin web prozesatzeko ez-web-friendly teknologian oinarritutako marko, complex BizTalk orchestrations and the like. We can all (Zorionez) itxura harro gure ibilbidean, eta esan, "yeah, duten gogor bat ebatzi zen, baina azkenean I pwned sumbitch duten!" Hobeto oraindik, are gehiago interesgarri eta dibertigarriak erronka zain.

Pertsonalki, uste dut nire curriculuma duten, Zentzu honetan, nahiko sakona da eta nahiko harro nago (nahiz eta jakin nuen, nire emazteak ez du inoiz ulertzen da 1/20th). But this week, Buruzko artikulu bat irakurtzen ari nintzen Partikula handiak Collider in my Scientific American magazine and had one of those rare humbling moments where I realized that despite my "giant" zirkulu jakin batean edo egoera nola sakona uste dut nire esperientzia ondo, 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 (izan naiz, nahiz eta oso susmagarria buruz ikasi dut geroztik Lurraren errotazio da motelduz, horrek ezin digu Gizakiak gauza ona izan daiteke epe luzera). Baina, the LHC team does have to worry. LHC’s measuring devices are so sensitive that they are affected by the Moon’s (Lurraren errotazio-moteltzea eta, azkenean, hil-guztiak-bizitza) gravity. That’s a heck of a requirement to meet — ekoizteko zuzena Neurketak Moon horrek interferentziak arren.

Alea izan zen I pondering denean esaldi hau irakurri nuen: "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.

Hurrengo denbora nago lagun batekin, Topa biltzeko eta LHC lanean jende ona izan dut, 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 🙂

</amaiera>

Technorati Tags: