Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple APILearn More
Xoka8792yCan we also get an invitation to Google Foobar Challenge??
epse39042yI'd pass up Google, no question. I'm never ever working there. Even if I quickly ignore my gripes with Google as a company, it's plain too big. The stories coming from employees are equal parts horror and wonder. Google can take whoever they want, but not me. They don't even seem trustworthy towards their employees, and that's enough for me to turn my back, whatever the interviewing process.
Kasonnara832yI'm not a sysadmin but I feel like even for sysadmins, knowing at least some programming language other than command line seems to me like ... the basics.
I know you shouldn't require it, but there so many case where you get some shitty bugs that can be understood and solved quicker by yourself if your can read the app code.
Especially with java and python that are not compiled and very common.
So yes you do not absolutely require this skill but I'm confident having it is still usefull and if you are google you can expect you candidates to be better than average. In addition as google hold the sysadmins and the devs, i guess the devs will be happier if a sysadmin can already analyse a bug and make better feedback on his own.
Kasonnara832yFor the language choice: a long as you know one complete programming language, I consider you can do almost all of them (in the same field, here, general purpose programming language) with a little bit of additional time.
So it's not surprising that google only focus on java and python: well known by most candidates and supervisors, quick to write and quick to read
Condor349492y@Kasonnara I can read code in pretty much all languages, and get a general grasp of what it's trying to do. I mean I pretty much have to - can't go blindly execute any script on a server that I can't afford to be nuked or infected. What I do not know however - and am not really willing to learn either because there's already *a lot* of subjects to learn in the sysadmin field - is how to write in it. That is not my job and I will likely never need it.
Additionally, my field is not one in which I keep devs happy by being their QA or to give them bug reports with information other than whatever relevant information the system logs give me (usually my bug reports / support requests are fairly well-received so I believe I'm good there). What I do to keep the devs happy is keeping their servers up and running, healthily. What I do when a piece of server software consistently fails on a server I control, is indeed sending out a bug report with relevant error messages and if applicable, steps to reproduce. However, that's a troubleshooting skill, not a programming one. I am not going to look into the code of a program I use, just to make it as easy as possible to the dev by telling "here, this line here is where you're wrong". That's up to the dev to find out. I am not interested in the internals of their programs any more than I have to. I am not their QA team.