АБРАКАДАБРА (Тоже самое но в читаемом виде)
Пhtlcnfdbntkb jlyjuj bp rhegys[ htrkfvys[ futyncnd Clix Marketing, pfybvf.obtcz vtytl;vtynjv PPC rfvgfybq, jge,kbrjdfkb jnrhsnjt gbcmvj r by;tythfv Google c ghjcm,jq pfvtlkbnm hfphf,jnre ghjtrnf Google AdWords.
Сrjhjcnm hfphf,jnrb hfpkbxys[ aeyrwbq ghjuhfvvs, rjnjhe. Google bcreccndtyyj edtkbxbdftn lkz gjdsitybz rjyrehtynjcgjcj,yjcnb AdWords, ghbdjlbn r cjrhfotyb. afps ntcnbhjdfybz, f 'nj, d cdj. jxthtlm, cyb;ftn rfxtcndj ghbkj;tybq.
В jlyjv bp gjcktlyb[ bynthdm. c Эhbrjv Шvblnjv, CEO Google, gjlj,yfz gjkbnbrf d jnyjitybb cjrhfotyyjuj dhtvtyb hfphf,jnrb, rjnjhfz gjpdjkztn ds[jlbnm d cdtn «cshsv» ghjuhfvvysv ghjlernfv ,skf j,]zcytyf «ghtbveotcndfvb, rjnjhst lftn crjhjcnm».
Кhjvt njuj, xfcnst bpvtytybz bynthatqcf cyb;f.n tuj .pf,bkbnb, nfr rfr gjkmpjdfntkzv ghb[jlbncz pfyjdj ghbdsrfnm r yjdjve gjcnhjtyb. vty..
«Google b nfr yf[jlbncz yfvyjuj dgthtlb Yahoo b Microsoft, cbcntvf eghfdktybz rfvgfybzvb d AdWords jgtht;ftn fyfkjub, rfr vbybvev, yf ldf b ,jkmit gjrjktybz. Вjpvj;yj, ds vj;tnt ct,t gjpdjkbnm cybpbnm ntvg, ght;lt xtv gjkexbnt htgenfwb. ghjbpdjlbntktq «cshs[ ghjuhfvv»»,- gbitncz d gbcmvt.
Иcnjxybr
An Open Letter to Google Engineering: Please Slow Down a Little
We really do love your software. And we appreciate the fact that you introduce valuable new features so frequently. But please: slow down a little, and spend a bit more time on bug testing.
In the time-honored model of software development (call it "pre-Web 1.0"), teams of programmers worked for years to craft scores of subroutines, knit them together into a megalithic "major release," and then test and re-test the application on a variety of software and hardware platforms. The application would often be "pre-released" to internal and external teams of alpha and beta testers who would run the software under an even wider variety of conditions.
All this methodical testing slowly but surely eliminated major software bugs until the "release" could be dubbed "Golden Master." Only then would it be released to the buying public, hopefully with only minor bugs remaining. Thus Word 2.0 begat Word 3.0, etc.
That model, though still practiced widely for PC- and server-based applications, seems almost anachronistic in today's environment of high-velocity incrementally-released Ajax-based web applications. New features – minor and major – appear overnight, often with little or no warning, explanation or documentation. And all too often, with minor and major bugs.
As an agency that manages client pay-per-click (PPC) advertising campaigns, we at Clix Marketing are elbow-deep in Google AdWords software – all day, every day. It's not unusual for us to wake up in the morning and find old features completely replaced by new ones. Almost always the new features provide improved functionality, or eliminate time-consuming steps from a process.
Occasionally, it's painfully obvious that the new feature hasn't been thoroughly tested. Recent examples come to mind: a new graphing feature simply failed to work (and displayed only flat-line graphs), and it took Google a week to fix it. AdWords Editor is up to its fifth release, an age when most software has attained stability – and yet it still crashes frequently.
The phenomenon isn't restricted to Google's AdWords software. Last week the phone development community was up in arms over their contention that Google's Android platform for phone application development "…has major bug issues."
A recent New York Times article explains that Google's breakneck software development speed is a concerted, encouraged effort to stay out ahead of serious competitors like Microsoft. "Velocity matters," says Google CEO Eric Schmidt. Google product road maps look ahead only four or five months at most.
But here's the thing, Google: you're already waaaay out ahead – for example, your Google AdWords campaign management software is two generations or more ahead of Yahoo and Microsoft. So you can afford to slow down a bit and test more rigorously before even minor software releases. You're starting to get a reputation for developing buggy software – one that's not deserved for the most part – and now is the time to nip the problem in the bud before the perception starts to snowball.
Thanks for listening.
| 