3 ms·

Some people view things like this as lip service but in my experience it definitely helps to have a principle like this down in writing. There were many times d

Some people view things like this as lip service but in my experience it definitely helps to have a principle like this down in writing. There were many times during my career at Google (2015 to 2021) where we were at an impasse around an ambiguous situation and I successfully persuaded my co-workers to pursue a painful/unpopular option by arguing that that option most closely followed Google's #1 principle ("focus on the user and everything else will follow"). In DevRel this happens all the time: the thing that creates a better experience for end users often also creates more pain for the developer (e.g. accessibility, i18n, load performance).

phkahler 5y ago
...the thing that creates a better experience for end users often also creates more pain for the developer. You mean I have to write a bunch of code for that! Yes, that's what computers are for, to do the stuff that people don't want to do. And developers exist to program the computers to do those things. Sometimes it sucks, but the product is better for it and life is a little better for some people.
karaterobot 5y ago
That is very true! But, at the same time (and without intending offense to you in particular) user-centric principles being written down does not prevent user-hostile behavior. I agree with you that this never hurts, and may sometimes help, but I think (and I'm sure you'd agree) having something firmer and more enforceable than a guiding principle in place is also necessary.
- Kinrany 5y ago
  Enforcement necessitates centralization. In the spirit of rough consensus, it may be possible to have a group tasked with maintaining principles but without any special powers.
- kaycebasques 5y ago
  No argument from me! In my original comment I was going to add something along the lines of "[I often used Google's principle to justify unpopular/painful options] but it was relatively easy to do so in my role (technical writer). I'm sure there are other roles where the incentives are stacked in such a way where it's much harder for them to follow the principle."

phkahler 5y ago

...the thing that creates a better experience for end users often also creates more pain for the developer. You mean I have to write a bunch of code for that! Yes, that's what computers are for, to do the stuff that people don't want to do. And developers exist to program the computers to do those things. Sometimes it sucks, but the product is better for it and life is a little better for some people.

karaterobot 5y ago

That is very true! But, at the same time (and without intending offense to you in particular) user-centric principles being written down does not prevent user-hostile behavior. I agree with you that this never hurts, and may sometimes help, but I think (and I'm sure you'd agree) having something firmer and more enforceable than a guiding principle in place is also necessary.

Kinrany 5y ago
Enforcement necessitates centralization. In the spirit of rough consensus, it may be possible to have a group tasked with maintaining principles but without any special powers.
kaycebasques 5y ago
No argument from me! In my original comment I was going to add something along the lines of "[I often used Google's principle to justify unpopular/painful options] but it was relatively easy to do so in my role (technical writer). I'm sure there are other roles where the incentives are stacked in such a way where it's much harder for them to follow the principle."