I was in Dogtown a year ago, but Sonic was just reselling AT&T to our address :(
Still very worthwhile to not have to talk to a Telco, but I had to rent + use AT&Ts garbage router because it did some proprietary negotiation step (With the ONT? There was a blog post where someone reverse engineered what was happening).
Now I'm in a smaller city and Sonic claims they have plans for us some day. For the time being, it's the Comcast nightmare.
Edit: and AT&T fiber was asymmetrical. Disappoint.
I'm in the same boat. I work there and can only get the resold AT&T service because my neighborhood was built pre-wired for only Comcast and AT&T, making it hard to service.
Still, like you noted, not having to deal with AT&T is a great selling point to a lot of people, and we're known for good support, so I'd like to think we're providing as good a service as those people can get until we build out our network in their area.
We have aggressive plans for the future, so I hope we're in your area sooner than later. :)
Same. About six months ago I started see Sonic trucks all over the neighborhood, five or six at a time covering multiple blocks. I asked if they were installing Fiber and was told no. Not much later, a sales rep knocked on my door. I said yes to the service before he could even greet me. It's been great.
As someone working on improving we vitals metrics, ad networks are 100% the biggest issue we face. Endless redirects, enormous payloads, and non optimized images. And on top of all that, endless console logs. I wish ad providers had higher standards.
My 2cents but I have noticed lots of small, minor updates to their front end over the last year. Things like better focus and hover states, branch copying, better mobile layouts, etc. Lots of minor front end polish.
That was an explicit paper cuts project by the GitHub team started prior to the acquisition.
Primary push was the Dear GitHub letter and the isaacs/GitHub repo which documented hundreds of such small issues. Also, the GitHub refined plugin, features of which GitHub keeps reimplementing now.
I would love to read a meta article on posts like: `so blessed with ${numOffers}, it was so hard to narrow down, i can't wait to start working at ${company}`
Most of flexbox is supported in IE11, but some "defaults" are not the same as other browsers --> see the known issues tab if you're interested, most of the time it works but when it doesn't it's frustrating https://caniuse.com/#feat=flexbox
Thanks for the great Redux docs. I was not able to find any solid information on how to use Redux with typescript in the docs. Since redux now comes with typescript types (I think), it would be nice to have documentation around how to use them and any best practices to follow and pitfalls to avoid.
We've got a work-in-progress PR on adding a docs page to discuss using TS with Redux: https://github.com/reduxjs/redux/pull/3201 . But, neither Tim nor I use TS ourselves (yet), so we're not experts and don't have the expertise to write this ourselves, or maintain the typings. That's gotta come from the community.
The React-Redux typings are separate, in Definitely Typed. We're considering moving the Redux typings over there as well.
