4 ms·

Maybe I am misunderstanding, but if I read this correctly, he says that he pushed out a major v2.0 release with new dependencies just minutes before a launch ev

Maybe I am misunderstanding, but if I read this correctly, he says that he pushed out a major v2.0 release with new dependencies just minutes before a launch event that cannot be moved or changed. Even worse, he says that he never ran the prod build, and only in his personal browser. If this is in fact the case, this sounds like a severe lack of testing or foresight.Testing should include prod builds in multiple browsers and operating systems, and it should most certainly be released at least a few days before any launch events, if you depend on a potentially lengthy review process. He didn't even take into account that the original v2.0 review could have also been delayed. Maybe I am severely misinterpreting what happened here (apologies if I did), but to me it sounds like a he is blaming Google's review process when he should be looking at his release and test practices.

willcipriano 3y ago
Releasing to big fanfare the instant the product exists is a mistake and a common one. Deploy it and let some friends try it first.
- binwiederhier 3y ago
  This is the way. What strikes me as odd is that the conversation on Twitter seems to be centered around the Google review not being fast enough, instead of the obvious mistakes with the release timeline and testing. What gets me too is that he doesn't seem to see any fault in his behavior, and only in the review process. In business and in public, be humble and apologize.
  - ozim 3y ago
    Well he makes me feel better about my salary when I tell my boss to slow down and double check things and use proper processes that I work on. For me it goes so well that I double guess if we need to be that careful but better safe than sorry I guess.
- Oldandwise 3y ago
  That doesn't align with the adage of 'ship every six hours'
nottorp 3y ago
To quote a wise man with production experience that I worked for (and has retired early). "It won't crash on our machines. It will crash at the customers."
- Obscurity4340 3y ago
  Problem exists between enduser and enduser's screen
  - nottorp 3y ago
    They're holding it wrong?
    - Obscurity4340 3y ago
      Where do I put my feet?
      - binwiederhier 3y ago
        This has, for many years, been my favorite gif of all time. It's the end user using the product: https://media.tenor.com/OC3DCjhCp_gAAAAC/endusers-customers.gif https://media.tenor.com/OC3DCjhCp_gAAAAC/endusers-customers....
        Obscurity4340 3y ago
        Ever heard of Obecalp? Halcyon days, those were
  - hightrix 3y ago
    PEBKAC - Problem exists between keyboard and chair.
    - Obscurity4340 3y ago
      I'm never saying that in the verbatim lol
dogleash 3y ago
> If this is in fact the case, this sounds like a severe lack of testing or foresight. It also sounds like every single webapp I've been privy to the inner workings of. I can't fault this guy too hard.
- binwiederhier 3y ago
  Except that this is not a webapp. It's more like an endpoint-deployed application, like an iOS and Android app. Since it's gated by Google, you have to anticipate that things take really really long to deploy or are rejected.
jstarfish 3y ago
> Maybe I am severely misinterpreting what happened here (apologies if I did), but to me it sounds like a he is blaming Google's review process when he should be looking at his release and test practices. While you make all good points, you're a career SWE who's already witnessed or made all of these mistakes enough to articulate what he should have done. His own release and test practices be damned-- if devs can't quickly push a hotfix for a launch bug, I assume there is no framework to respond to anything more pressing (like security issues) in a timely manner either. If you discover one of your libraries has been compromised, what's the quickest path to remediation in that scenario (that doesn't involve your app being de-listed altogether)?
- JCharante 3y ago
  > if devs can't quickly push a hotfix for a launch bug This is exactly why he should be very careful before pushing updates. It takes days to put out a fix and deploying on launch date instead of doing a soft launch would terrify any developer.
  - penjelly 3y ago
    in my exp you have to fix it yourself if you want turnaround. so either log a bug and open a pr on the lib with a reasonable fix or fork and fix it yourself and publish or selfhost with jfrog/etc

willcipriano 3y ago

Releasing to big fanfare the instant the product exists is a mistake and a common one. Deploy it and let some friends try it first.

binwiederhier 3y ago
This is the way. What strikes me as odd is that the conversation on Twitter seems to be centered around the Google review not being fast enough, instead of the obvious mistakes with the release timeline and testing. What gets me too is that he doesn't seem to see any fault in his behavior, and only in the review process. In business and in public, be humble and apologize.
- ozim 3y ago
  Well he makes me feel better about my salary when I tell my boss to slow down and double check things and use proper processes that I work on. For me it goes so well that I double guess if we need to be that careful but better safe than sorry I guess.
Oldandwise 3y ago
That doesn't align with the adage of 'ship every six hours'

nottorp 3y ago

To quote a wise man with production experience that I worked for (and has retired early). "It won't crash on our machines. It will crash at the customers."

Obscurity4340 3y ago
Problem exists between enduser and enduser's screen
- nottorp 3y ago
  They're holding it wrong?
  - Obscurity4340 3y ago
    Where do I put my feet?
    - binwiederhier 3y ago
      This has, for many years, been my favorite gif of all time. It's the end user using the product: https://media.tenor.com/OC3DCjhCp_gAAAAC/endusers-customers.gif https://media.tenor.com/OC3DCjhCp_gAAAAC/endusers-customers....
      - Obscurity4340 3y ago
        Ever heard of Obecalp? Halcyon days, those were
- hightrix 3y ago
  PEBKAC - Problem exists between keyboard and chair.
  - Obscurity4340 3y ago
    I'm never saying that in the verbatim lol

dogleash 3y ago

> If this is in fact the case, this sounds like a severe lack of testing or foresight. It also sounds like every single webapp I've been privy to the inner workings of. I can't fault this guy too hard.

binwiederhier 3y ago
Except that this is not a webapp. It's more like an endpoint-deployed application, like an iOS and Android app. Since it's gated by Google, you have to anticipate that things take really really long to deploy or are rejected.

jstarfish 3y ago

> Maybe I am severely misinterpreting what happened here (apologies if I did), but to me it sounds like a he is blaming Google's review process when he should be looking at his release and test practices. While you make all good points, you're a career SWE who's already witnessed or made all of these mistakes enough to articulate what he should have done. His own release and test practices be damned-- if devs can't quickly push a hotfix for a launch bug, I assume there is no framework to respond to anything more pressing (like security issues) in a timely manner either. If you discover one of your libraries has been compromised, what's the quickest path to remediation in that scenario (that doesn't involve your app being de-listed altogether)?

JCharante 3y ago
> if devs can't quickly push a hotfix for a launch bug This is exactly why he should be very careful before pushing updates. It takes days to put out a fix and deploying on launch date instead of doing a soft launch would terrify any developer.
- penjelly 3y ago
  in my exp you have to fix it yourself if you want turnaround. so either log a bug and open a pr on the lib with a reasonable fix or fork and fix it yourself and publish or selfhost with jfrog/etc