http___www.stochasticgeometry.ie_ga_2010_07_20_interviews-google__1.xml
1.1 2.1 2.2 2.3 3.1 3.2 3.3 3.4 4.1 4.2 5.1 5.2 5.3 6.1 6.2 6.3 6.4 6.5 7.1 7.2 7.3 7.4 8.1 8.2 8.3 8.4 8.5 8.6 8.7 9.1 9.2 9.3 9.4 10.1 10.2 10.3 10.4 10.5 11.1 11.2 11.3 12.1 12.2 12.3 12.4 13.1 13.2 13.3 14.1 14.2 15.1 15.2 15.3 15.4 15.5 15.6 16.1 16.2 16.3
So I’ve now completed the interview process twice with Google (once in 2007 and once in 2010), and while I’m not sure advice from someone not hired after two run-throughs is all that useful, I figured that the more information out there for those undergoing pre-Google-Interview stress, the better, so here’s how it went. In both cases, I was contacted out of the blue by a Google recruiter. The first time I had been considering looking for a new role and pursued it immediately; the second time I hadn’t been and put off the recruitment process for several months, during which the same recruiter contacted me again twice to follow up. If nothing else, that’s a nice ego boost, but a more cynical mind might be considering the shotgun approach to a narrow recruiting filter and commissions First, a quick data point, I was applying for an SRE(SA) position on both occasions – Site Reliability Engineer (System Administration), because in most of my roles to date, I’ve been doing both sysadmin and development work and I’ve never seemed to drift towards one pigeonhole or another. SRE(SA) seemed optimal – interesting sysadmin work on large-scale systems and quite a bit of tool-writing to boot. This was decided on between myself and the recruiter, based on the self-assessment form you are given to fill out. I would love to know how they get around illusory superiority and the Dunning-Kruger effect with those forms, especially given the wierd bias they’d have in the dataset from having so many of the best in their fields working there. Both times, the process proceeded in the same way: the recruiter themselves carried out the initial phone screening, an idiot test of basic knowledge. The questions at this level are more broad than deep, and you really are talking about easy things like basic unix commands and the like. The second phone screen was more demanding technically, and was of the same mould as the famous “why is the sky blue?” physics exam question, with an initial simple answer and then drilling more and more into that answer. In my case, both were focussed on the level where user-level unix meets the underlying systems, the sort of thing you’d encounter in writing any kind of sysadmin tool. If I had to give hints here, it would be to know the underlying systems, their APIs, and the unix philosophy for writing tools to work with them. I’m not sure hints are of much use for Google interviews though – there are many sites saying they have questions used in Google interviews, but I’ve not yet encountered one of those examples after fourteen interviews. Knowing how to tackle Fermi questions (back-of-the-envelope estimates using what seem to be reasonable assumptions, such as “how many golf balls fit in a bus”) is probably a good idea, though I’ve only encountered them in passing; and big O notation has never come up. However, I think that SRE(SA) questions probably lean far more heavily towards the practical workaday stuff than towards application-level design fundamentals. Presumably there’s a different balance for developers. Certainly, practicing fault diagnosis in networked systems would be a good idea, and having your internal process for diagnosing faults well defined in your own head would be an even better one – that’s what the interviews are looking for and if you don’t have it clear for yourself, they can’t spot that. I would also suggest practicing writing code longhand, in one of the Google languages (C++, Python and shell script seemed to be the most popular). And I don’t mean coding on a machine, I mean writing the code longhand into a notebook and then typing it verbatim into a machine to test it. For a nice side effect, this’ll improve your penmanship and that may prove useful because you will be working a lot with a whiteboard. Incidentally, one of the better tips I’ve come across was to bring your own whiteboard markers (thin ones); it effectively gives you more room to work with, and whiteboards are never big enough, no matter how big they are… On both occasions, I then went on to do the on-site interviews. In my case, this was logistically easy as I was very close to the Dublin office, which is currently the second-largest Google office worldwide, so I didn’t have to fly to California or anything so onerous, but all five on-site interviews were held on one day, back-to-back, which is a bit exhausting. And on both occasions, the experience was about the same; initially you notice very Californian decor, with even the temp receptionist surrounded by a dozen or so lava lamps in alternating colours, with everything nice and brightly lit, and with swiss balls everywhere acting as seats and so forth. It does sound very Dr. Seuss, and it is in a way, but it’s a lot nicer than that sounds to be honest (if a bit… young), and there’s definitely an element of creating a culture through a particular physical appearance. The entire office complex is self-contained for the most part, with its own on-site canteen (which, by the way, is quite impressive – any canteen that can cook cous-cous properly for a thousand or so servings, while serving up at least four other lunch menus, is showing off very competent catering skills indeed, even if noone’s noticing most of the time), gyms and so on. In fact, walking around the streets you’d never know how many people are working in the offices from a casual glance. Again, on both occasions, the procedure was the same – I was met in reception after checking in by the recruiter, who’d booked an interview room and who walks you around the office a bit on the way there. Take a look around at this point; it’s an interesting office setup. Once there, the recruiter introduces the first interviewer and leaves you to the interview process and retrieves you at the end of the day to walk you out (after which point, the interviewers write up their reports and the hiring committee makes a decision. Start to finish, it’s been three to four weeks each time from initial contact to final decision). There were five interviews back-to-back each time, and the technical areas covered for me were those you’d expect for such a role: Design and Coding approaches; Unix/Linux sysadmin stuff; Networking; Scripting; Troubleshooting and problem-solving; Disk and storage systems. One google expert in each area, with the brief to start light and then push and push until you’re out of your comfort zone and well into your sweaty, stressed, exploding-head zone. If nothing else, you do wind up learning things from Google interviews, which is reason enough to undergo them to be honest. I didn’t know about isatty() until this round of interviews, for example. I don’t know of any other interview process that could be counted as a continuing professional development activity I’ve read accounts of Google interviewers being uninterested in the interviews they’re carrying out and being borderline rude in some cases; I have to say, I never encountered anything like that in any of the fourteen interviews I did over the two occasions, and never encountered anyone doing an interview who was less than professional about it; and most, if not all, were quite happy people during the interviews. Honestly, I never picked up on any personal or professional issues towards me, there was nothing but buy-in to their way of doing things. Which was quite impressive – I’ve interviewed with companies before where the interview felt more like a test of how much abuse you could tolerate, or where the company was simply wasting my time and theirs (for example, calling me in for an onsite interview that ate half a day, only to announce that they couldn’t pay me more than 60% of the expected salary). There’s not much feedback in the interviews though. That’s about the only real criticism I have of them. I can understand the hyping of the interviews – as much as you try to null it out, it does create mental stress and some think that gives greater insights into your real abilities (although frankly, it’s not the same kind of stress as you get during your daily work, so I don’t think it’s as useful as you’d imagine). I can understand the mythologising of the Google workplace (and given the professional and personal advantages that workplace offers, I can accept it as the cost of doing business). Actually, to digress for a moment on the workplace, I should point out that one of my main concerns while interviewing was how Google and professionals with families get along. Famously, Google is a young work environment, and while an eighty-hour work week, all-nighters and completely obsessive behaviour around your job is something you can manage to do in your early twenties, I don’t think you should do it – I think it’s one of our industry’s worst cases of macho-driven work practices, and a main reason for the high instance of IT project failures. Beside that opinion however, there’s the very real point that by the time you hit your thirties, you have to worry about wives, children, and other family things outside of work; and often you are faced with a choice between being a good employee and being a good person (and yes, I count letting obsession with work take over time that belongs to your family as a character failing; and no, that’s not the same thing as having to work long hours, that’s a different thing entirely). Google, however, seems to have taken this on-board, and everyone I spoke to about it had similar experiences – the mean age of the work force in Google is increasing, and more and more now have young families and work practices and facilities are changing to match the new demands. Childcare is the new free food, being family-friendly is now part of doing no evil. Feedback, however, is still a verboten topic. Interviewers don’t (and one told me they’re not allowed to) give feedback; nor are you given any if the hiring committee decides not to go with you as a candidate (which is what happened in both cases for me). That is rather fustrating – there’s no way to tell if you flunked a particular area, or if it was just that it wasn’t thought that you’d fit in with the Google environment. So you can wind up going through a process taking a few weeks, bringing a lot of stress, go through seven (or more) interviews, and not learn at the end if the problem was your technical proficiency or your popularity. Which is… suboptimal, at least from the interviewee’s point of view. From the interviewing company’s point of view, I suppose it could be said that every minute spent on a candidate after a decision to not hire them is a wasted minute; but the fact that you could be coming back to that person in a year or three does somewhat argue against that view. In short, it’s pretty tough, you will have to study hard for it (well, that’s to be expected), you may find your brain stalls because of the stress on things you fully grok day-to-day (that happened to me several times), and at the end of it all, you might be turned down purely on social reasons without ever being told it was because of workplace fit instead of technical competence. It’s still worth doing though, if only for the experience. Good luck!
1.1 2.1 2.2 2.3 3.1 3.2 3.3 3.4 4.1 4.2 5.1 5.2 5.3 6.1 6.2 6.3 6.4 6.5 7.1 7.2 7.3 7.4 8.1 8.2 8.3 8.4 8.5 8.6 9.1 9.2 9.3 9.4 10.1 10.2 10.3 10.4 10.5 11.1 11.2 11.3 12.1 12.2 12.3 12.4 13.1 13.2 13.3 14.1 14.2 15.1 15.2 15.3 15.4 15.5 15.6 16.1 16.2 16.3
Mar sin, tá mé críochnaithe anois leis an bpróiseas agallaimh faoi dhó le Google (uair amháin sa bhliain 2007 agus uair amháin sa bhliain 2010), agus cé nach bhfuil mé cinnte comhairle a fháil ó dhuine nach fhostaigh tar éis dhá rith chun throughs Is léir go úsáideach, figured mé go bhfuil níos mó eolais amach ann dóibh siúd ag dul faoi strus réamh-Google-Agallamh, is amhlaidh is fearr, tá anseo mar sin conas a chuaigh sé. Sa dá chás, bhí mé i dteagmháil amach as an gorm ag earcaitheoir Google. An chéad uair a bhí mé ag smaoineamh ag lorg ról nua agus lean sé láithreach; an dara huair nach raibh mé agus a chur as an bpróiseas earcaíochta ar feadh roinnt míonna, ar lena linn a hearcóir céanna chugam arís faoi dhó a leanúint suas. Má tá aon rud eile, tá go borradh ego deas, ach d'fhéadfadh aigne níos ciniciúil bheith ag smaoineamh ar an gcur chuige gunna gráin a scagaire earcú caol agus coimisiúin Gcéad dul síos, pointe sonraí mear, bhí mé ag cur isteach ar SRE (SA) seasamh ar an dá ócáid - Suíomh Iontaofacht Innealtóir (Córas Riaracháin), mar gheall ar i is mó de mo róil go dtí seo, tá mé ag déanamh sysadmin agus forbairt oibre agus mé araon 'Ve riamh an chuma chun sruth i dtreo pigeonhole amháin nó eile. SRE (SA) an chuma is fearr is féidir - obair sysadmin suimiúil ar chórais mhórscála agus go leor le beagán de uirlis-scríbhneoireachta a tosaithe. Socraíodh seo ar idir mé féin agus an hearcóir, bunaithe ar an bhfoirm féin-mheasúnaithe a thugtar duit a líonadh amach. Ba mhaith liom grá a fhios conas a fhaigheann siad superiority ar fud illusory agus an éifeacht Dunning-Kruger leis na foirmeacha, go háirithe mar gheall ar an claonadh aisteach gur mhaith leo a bheith i tacar sonraí as a bhfuil an oiread sin de na fearr ina réimsí ag obair ann. An dá uair, chuaigh an próiseas ar an mbealach céanna: an earcaitheoir iad féin a rinne an scagadh fón tosaigh, tástáil leathcheann ar eolas bunúsach. Is iad na ceisteanna ag an leibhéal níos leithne ná domhain, agus má tá tú i ndáiríre ag caint faoi rudaí éasca mhaith orduithe Seol bunúsacha agus a leithéidí. An scáileán an dara fón a bhí níos éilithí go teicniúil, agus go raibh an múnla céanna leis an cáiliúil "cén fáth a bhfuil an spéir gorm?" Ceist scrúdaithe fisic, le freagra simplí tosaigh agus ansin druileáil níos mó agus níos mó i sin a fhreagairt. I mo chás féin, bhí an dá dírithe ar an leibhéal i gcás ina gcomhlíonann an úsáideoir-leibhéal UNIX na córais bunúsacha, an saghas rud gur mhaith leat teacht ar i scríbhinn de chineál ar bith uirlis sysadmin. Má bhí mé a thabhairt leideanna anseo, bheadh sé a fhios ag na córais is bun, a APIs, agus an fhealsúnacht UNIX le huirlisí a bheith ag obair leo scríobh . Níl mé cinnte go bhfuil leideanna ar úsáid i bhfad chun agallaimh Google cé - tá go leor suímh ag rá go bhfuil siad ceisteanna a úsáidtear i agallaimh Google, ach ní tá mé a bhíonn go fóill ar cheann de na samplaí tar éis agallaimh a ceathair déag. A fhios agam conas dul i ngleic ceisteanna Fermi (meastacháin ar ais-ar-an-clúdach ag baint úsáide cad is cosúil a bheith boinn tuisceana réasúnta, mar shampla "cé mhéad liathróidí gailf oiriúnach i bus") Is dócha go bhfuil smaoineamh maith, cé bhí mé a bhíonn ach amháin iad i rith; agus riamh nodaireacht O mór teacht suas. Mar sin féin, is dóigh liom go dócha SRE (SA) ceisteanna lean i bhfad níos mó go mór i dtreo an stuif workaday praiticiúla ná dtreo bunúsacha dearadh iarratas-leibhéal. Is dócha níl cothromaíocht difriúil d'fhorbróirí. Cinnte, bheadh ag cleachtadh diagnóis locht i gcórais líonraithe a bheith ina smaoineamh maith, agus go mbeadh a bhfuil do phróiseas inmheánach do lochtanna a dhiagnóisiú dea-shainithe i do cheann féin a bheith ina níos fearr fós ar cheann - go bhfuil an méid atá na hagallaimh lorg agus más rud é nach bhfuil tú é soiléir ar do shon féin, ní féidir leo a láthair sin. Ba mhaith liom a mholadh freisin ag cleachtadh cód scríbhneoireachta ngnáthscríobh, i gceann de na teangacha Google (C + +, Python agus script bhlaosc an chuma a bheith ar an chuid is mó tóir). Agus ní féidir liom a chiallaíonn códú ar mheaisín, ciallóidh mé ag scríobh an ngnáthscríobh cód isteach i leabhar nótaí agus ansin clóscríobh sé focal ar fhocal isteach i meaisín a thástáil sé. Chun éifeacht taobh deas, beidh sé seo feabhas a chur ar do peannaireacht agus a d'fhéadfadh a bheith úsáideach mar go mbeidh tú a bheith ag obair ar a lán le clár bán. Teagmhasach, ar cheann de na leideanna is fearr mé teacht trasna a bhí a thabhairt do marcóirí clár bán féin (na cinn tanaí); Tugann sé go héifeachtach tú seomra níos mó a bheith ag obair le, agus nach bhfuil cláir bhána mór go leor, is cuma cé chomh mór atá siad ... Ar an dá ócáid, chuaigh mé ansin ar a dhéanamh ar na hagallaimh ar an láthair. I mo chás féin, ba é seo logistically éasca mar a bhí mé an-aice leis an oifig i mBaile Átha Cliath, a bhfuil an Google oifig dara-is mó ar fud an domhain faoi láthair, mar sin ní raibh mé a eitilt go California nó aon rud mar sin trom, ach go léir na cúig ar an láthair Cuireadh agallaimh ar siúl ar an lá amháin, ar ais-le-ais, a bhfuil beagán tuirsiúil. Agus ar an dá ócáid, bhí an taithí faoi mar an gcéanna; tú faoi deara ar dtús decor an-California, le fiú an fáilteoir teocht timpeallaithe ag dosaen nó mar sin lampaí lava i dathanna alternating, le gach rud deas agus brightly lit, agus le liathróidí na hEilvéise i ngach áit ag gníomhú mar shuíocháin agus mar sin de. Déanann sé fuaim an-Dr.Seuss, agus tá sé ar bhealach, ach tá sé a lán níos deise ná go fuaimeanna a bheith macánta (más le beagán ... óg), agus níl sí gné de chultúr a chruthú trí cuma fhisiciúil ar leith. Is é an casta oifig ar fad féin-atá don chuid is mó, lena rialacha bunreachtúla féin ceaintín ar an láthair (a, dála an scéil é, go leor go hiontach - aon ceaintín féidir a cócaireacht cous cous-i gceart ar feadh míle nó mar sin riar, ag fónamh suas ar a laghad ceithre biachláir lón eile, ag taispeáint as scileanna an-inniúil lónadóireachta go deimhin, fiú má Noone ar noticing an chuid is mó den am), gyms agus mar sin de. Go deimhin, riamh gur mhaith ag siúl ar fud na sráideanna a fhios agat cé mhéad duine atá ag obair sna hoifigí ó Sracfhéachaint ócáideach. Arís, ar an dá ócáid, bhí an nós imeachta mar an gcéanna - bhí bhuail mé i fáiltiú tar éis a sheiceáil i ag an hearcóir, ba mhaith in áirithe a seomra agallaimh agus a shiúlann tú thart ar an oifig le beagán ar an mbealach ann. Breathnaigh thart ag an bpointe seo; tá sé thus oifige suimiúil. Nuair atá ann, tugtar isteach an hearcóir an chéad agallóra agus fágann tú leis an bpróiseas agallaimh agus retrieves tú ag an deireadh an lae a shiúlann tú amach (i ndiaidh an bpointe, na agallóirí a scríobh suas a gcuid tuarascálacha agus déanann an coiste cinneadh a fhostú. Tosaigh le chríochnú, tá sé curtha 03:57 seachtaine gach uair ó chéad teagmháil le cinneadh deiridh). Bhí cúig agallamh ar ais-le-ais gach uair, agus réimsí teicniúla clúdaithe le haghaidh dom iad siúd gur mhaith leat a bheith ag súil le haghaidh a leithéid de ról: Dearadh agus cur chuige Coding; Unix / Linux stuif sysadmin; Líonrú; Scriptiú; Fabhtcheartú agus réiteach fadhbanna; Córais Diosca agus stórála. Saineolaí google amháin i ngach ceantar, leis an treoir a thosú solas agus ansin a bhrú agus a bhrú go dtí go bhfuil tú as do chrios chompord agus go maith i do sweaty, béim, crios pléascadh-cheann. Má tá aon rud eile, a dhéanann tú a fhoirceannadh rudaí a fhoghlaim ó agallaimh Google, a bhfuil cúis go leor chun dul faoi iad a bheith macánta. Ní raibh a fhios agam faoi isatty () go dtí seo babhta agallamh, mar shampla. Níl a fhios agam ar aon phróiseas agallaimh eile a d'fhéadfaí a áireamh mar ghníomhaíocht forbairt ghairmiúil leanúnach Tá cuntais na agallóirí Google á uninterested sna hagallaimh a bhíonn siad ag a chur i gcrích agus a bheith drochbhéasach i roinnt cásanna borderline léigh mé; Caithfidh mé a rá, ní bhíonn mé aon rud mar sin in aon cheann de na n-agallamh a rinne mé ceithre bliana déag d'os cionn an dá ócáid, agus ní bhíonn aon duine ag déanamh agallamh a bhí níos lú ná gairmiúla mar gheall air; agus an chuid is mó, más rud é nach go léir, bhí daoine sásta go leor le linn na n-agallamh. Go hionraic riamh, phioc mé suas ar aon saincheisteanna pearsanta nó gairmiúil i dtreo dom, nach raibh aon rud ach a cheannach-i do ar a mbealach rudaí a dhéanamh. Cé acu a bhí go leor go hiontach - Tá mé agallamh le cuideachtaí sula nuair a bhraith an t-agallamh níos mó cosúil le tástáil ar cé mhéad mí-úsáid a d'fhéadfadh tú a fhulaingt, nó i gcás ina raibh an chuideachta wasting ach mo chuid ama agus inniúlacht siúd (mar shampla, glaoch orm i le haghaidh agallaimh ar an láthair gur ith leath an lae, ach amháin a fhógairt nach bhféadfadh siad a íoc dom níos mó ná 60% den tuarastal ag súil leis). Ní Tá aiseolas i bhfad sna hagallaimh cé. Sin mar gheall ar an cáineadh ach fíor go bhfuil mé iad. Is féidir liom a thuiscint hyping na n-agallamh - an oiread agus mar iarracht tú a margadh saothair sé amach, a dhéanann sé strus mheabhrach a chruthú agus a roinnt cheapann go dtugann léargas níos fearr isteach i do chumas fíor (cé frankly, ní hí sin an cineál céanna strus mar a fhaigheann tú le linn do chuid oibre laethúil, mar sin ní dóigh liom go bhfuil sé chomh úsáideach mar gur mhaith leat a shamhlú). Is féidir liom a thuiscint mythologising an ionaid oibre Google (agus mar gheall ar na buntáistí gairmiúla agus pearsanta a thairgeann san ionad oibre, is féidir liom glacadh leis mar an costas a bhaineann le gnó a dhéanamh). I ndáiríre, a digress ar feadh nóiméad ar an ionad oibre, ba chóir dom a chur in iúl go bhfuil ceann de mo phríomh imní cé agallamh a bhí conas Google agus gairmiúla a bhfuil teaghlaigh a fháil chomh maith. Famously, tá Google timpeallacht oibre óg, agus cé go seachtain oibre ochtó uair an chloig, is é uile-nighters agus iompar obsessive hiomlán thart ar do phost rud is féidir leat a bhainistiú a dhéanamh i do fichidí luatha, ní dóigh liom gur cheart duit é a dhéanamh - Sílim go bhfuil sé ar cheann de na ár dtionscal ar cásanna is measa de cleachtais oibre macho-tiomáinte, agus ar chúis is mó le haghaidh an gcéad dul ard teipeanna tionscadal TF. In aice leis an tuairim sin, áfach, níl an pointe an-dáiríre go bhfuil ag an am a bhuail tú do tríochaidí, caithfidh tú a bheith buartha faoi mhná céile, leanaí, agus rudaí teaghlaigh eile lasmuigh den obair; agus is minic a bhfuil tú ag tabhairt aghaidhe rogha idir a bheith ina fhostaí maith agus a bheith ina duine maith (agus tá, líon mé a ligean ar cíos obsession le hobair a ghlacadh le himeacht ama a bhaineann le do theaghlach mar charachtar ina éagmais; agus ní, ní ar sin an rud céanna mar a bheith ag obair uaireanta fada, tá go rud difriúil go hiomlán). Google áfach, is cosúil,, a ghlac an ar bord, agus gach duine a labhair mé faoi go raibh sé taithí a fuarthas - Is é an meán-aois an fhórsa oibre in Google a mhéadú, agus níos mó agus níos mó anois go bhfuil teaghlaigh óga agus cleachtais oibre agus áiseanna athrú a mheaitseáil leis an éilimh nua. Is é cúram leanaí an bia nua saor in aisce, a bheith teaghlach-chairdiúil anois mar chuid den déanamh aon olc. Aiseolas, áfach, fós ina ábhar verboten. Nach bhfuil agallóirí (agus inis dom ceann amháin nach bhfuil cead acu) aiseolas a thabhairt; ná go bhfuil tú tugtar ar bith má chinneann an coiste fhostú gan dul in éineacht leat mar iarrthóir (a bhfuil cad a tharla sa dá chás dom). Is é sin in áit fustrating - níl aon bhealach a insint má flunked tú i limistéar áirithe, nó más rud é go raibh sé ach nach raibh sé gur shíl sé gur mhaith leat a d'oirfeadh i leis an gcomhshaol Google. Mar sin, is féidir leat a fhoirceannadh ag dul trí phróiseas cur cúpla seachtain, rud a thug a lán de strus, dul trí seacht (nó níos mó) agallaimh, agus ní foghlaim ag an deireadh má bhí an fhadhb do chumas teicniúil nó do tóir. Cé acu is ... fo-optamach, ar a laghad ó thaobh an agallaí ar an dearcadh. Ó thaobh na cuideachta faoi agallamh de, is dócha go bhféadfaí a rá gur chaith gach nóiméad ar iarrthóir tar éis cinneadh a nach iad a fhostú nóiméad amú; ach ní beag an bhfíric go bhféadfaí tú a bheith ag teacht ar ais go dtí an duine sin in aghaidh na bliana nó trí argóint i gcoinne an dearcadh sin. I mbeagán focal, tá sé deas diana, beidh ort chun staidéar a dhéanamh go crua chun é (go maith, sin a bheith ag súil leis), is féidir leat teacht ar do stallaí inchinn mar gheall ar an strus ar rudaí leat go hiomlán grok-lá-go-lá (a tharla dom arís agus arís eile), agus ag an deireadh ar fad, d'fhéadfá a bheith iompaithe síos amháin ar chúiseanna sóisialta gan a bheith in iúl riamh go raibh sé mar gheall ar ionad oibre oiriúnach in ionad inniúlacht theicniúil. Tá sé fós fiú a dhéanamh áfach, más rud é amháin chun an taithí. Ádh mór oraibh!