didn't mean to imply you were outraged but many clearly are over this. I just sympathize with hardworking enterprise devs. mistakes happen
-
-
I don't think the outrage is about this specifically, but this as a series of events of similar things happening... But (cont.)
1 reply 0 retweets 2 likes -
... this has been resolved now, so hurray :) That said, I'm not sure what the lesson is - get angry on Twitter and stuff gets fixed...?
1 reply 0 retweets 2 likes -
The lesson is let's work with people inside of Google who are motivated to get stuff changed.
1 reply 0 retweets 4 likes -
What's the best way to contact those people when stuff like this happens? Twitter is quite effective, but everyone comes away worse from it
2 replies 0 retweets 1 like -
Many of us follow eachother so DMs are a good option. I know it's a bit 90s but there's also email.
4 replies 0 retweets 3 likes -
Replying to @jaffathecake @cwiiis and
It'd be ideal if all Google sites had public-facing bug trackers.
2 replies 0 retweets 3 likes -
Replying to @jaffathecake @cwiiis and
Microsoft has been creating some GitHub bug trackers even w/o code. I love it.
2 replies 0 retweets 2 likes -
Off topic: I've been thinking of using Github issues instead of blog comments. Disqus' lack of markdown makes me sad.
1 reply 0 retweets 1 like -
Replying to @jaffathecake @cwiiis and
I turned off my comments years ago and am not sad about it. Not an elitist move, just thing we have better options now for replying.
2 replies 0 retweets 3 likes
Frankly I'd rather people tweet at me than reply on my blog.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.