[Googler who works with the Flutter team]

I'm a big fan of your app! It has become the main way I consume and watch stock data.

There are some minor issues however. The "Watchlist" header has an issue where it renders under the back button both on Android and iOS. Also the Watchlist view can have some jank while scrolling unlike other sections of the app. Finally it'd be great if the app responded to the system level dark mode setting instead of having it's own toggle.

Overall though, great stuff so keep up the good work :D

Wow, thanks a lot! That's such a nice compliment.

And thanks for your suggestions as well. Currently working on migrating to Flutter 2 and will look into it after that. :)

On a somewhat related note, I've always been impressed by the number and quality of charting libraries for the web. A while back I was looking for native charting libraries for Android/iOS and was disappointed. Has the ecosystem changed at all or are most people better off with embedded web views?

fwiw, I've liked https://github.com/danielgindi/Charts for iOS, which is based on an android charting library called MPAndroidChart.

Exciting match with top notch commentary. I'm rooting for a sweep of the series.

I had the exact same experience coming from T-Mobile as well. No issues after the reset and enjoying the service so far, especially when I travel internationally.

Reminds me of something I built: http://garyroumanis.com/2015/03/15/TVRemote-app/

Definitely pricey and a little off the beaten track but I absolutely love my Chromebook Pixel LS. Ubuntu was super easy to set up using Crouton. Everything worked out of the box, the only minor modification I made was replace the synaptic touchpad drivers with a ported version of Chromebook's. When I'm not developing I usually keep it in ChromeOS as it is extremely snappy and responsive. A quick keypress and I can drop into Ubuntu to get some work done.

I currently do pager duty (DRI) for a team within Microsoft. Like most teams that have this duty, we cycle a developer each week to have the responsibility to answer any escalations that might occur. The role of this developer is simply to mitigate the issue. Investigations into the root cause and potential preventative items are reserved for work hours.

The amount of escalations obviously varies from week to week. Some weeks I forget that I'm even on call (well that's actually not true as we have to carry a Lumia 1520 - the thing is a fucking brick) while other weeks are absolutely painful (waking up every couple hours in the middle of the night). Thankfully we have enough developers on the team that I'm only on duty every 6 to 7 weeks. What also helps is that my manager has no problem with me sleeping in and showing up late after a long night of escalations. Overall it isn't too bad and in fact sometimes can be fun to solve head scratching issues. Honestly, the worst part of being on call is not being able to make plans that would involve you being far away from a computer. You can turn this into a somewhat positive thing though by being productive at home whether it is cleaning, working on side projects etc.

Great write up! I'll have to get my hands on one in the near future.

I work on Bing at Microsoft. What you have stated is correct. We have already done away with our test and operation teams. Moreover, a number of PMs were let go last week. Developers are now expected to wear many more hats. We are also reducing the number of middle managers in the name of agility. All good things in my eyes.

Another interesting thing to note is that we are trying to reduce the size of projects and break apart the notion of "cores" within an org. The idea is to allow features that span several different areas to be implemented with greater ease. I like the idea but I am concerned with how these features will be maintained after they are completed.

How is that working out?

FWIW - I spent about 7 years in MS and now >5 in Amazon - I overall like the MS model, at least from a developer perspective.

It gave you a lot of time to focus on getting your complicated piece right with unit tests - and you could leave the integration tests / PM'ing to the respective folks. Amazon is like where Bing is going - but the end result is that it ends up favoring breadth oriented folks more than depth folks. That's ok if you are building a business logic / app tier, system teams are a different story.

For the same reason, the latest MS path doesn't seem right to me. It feels like they are taking the wrong lessons from startups / AWS.

But again, it has been 5 years since and I don't have the big picture - so I guess I will wait and watch.

Although I have a couple friends at Amazon, I was unaware that their development model is what Microsoft is aiming for. The points you make don't bother me right now since I am so young in my career. I haven't developed deep expertise in any particular area yet. In fact, one of my strongest assets is the ability to quickly pick up technologies. Hopefully this will serve me well when I eventually have to jump from system to system with the new development model.

My impression is that most all developers have their own office at MS, or at least share an office with 1-2 other devs (not sure if this is different inside bing teams or not either)

Has this 'more-hats' change you describe (specifically ops) changed that at all? Where I work, I hear an argument against offices: that they promote and encourage isolation in what can be an ops-heavy role at times (I see the merits but think there are better ways to combat that)

My company is at orders-of-magnitude different size than MS, wondering if something similar occurs there.

I also work in Bing.

Most people are in offices or in an area with a few people, but (at least for me) our team is scattered around, so we're not nearby each other at all. It's not easy to stop by or ask a quick question without going for a short walk.

Personally I like the office arrangement - you can make it silent, control the temperature, etc. I do wish that teams were grouped more closely together but that doesn't seem to be a concern for anyone higher up.

We're moving towards more open spaces. Buildings like 44 have large scrumish workrooms, no private offices.

It depends where you work in Microsoft. Most everybody I work with has their own office. I have several friends at Microsoft who work in open office spaces. As with most things in life, there are benefits and downsides. Personally I like my own office, but I have yet to work in an open environment.

I have been prototyping with Elasticsearch for the last couple of months. I have nothing but great things to say about the software and documentation. Several other partner teams have taken notice of my work and will likely incorporate the software as well. Very exciting!