Same, but I don't have the 3G (which would have been cool). I, too, have a case with a light, and would prefer a built-in light, but I don't think spending $100 is justified to get it. Everything else is awesome about it.

Just a heads up: this is a different river (off the Columbia) up in Idaho and beyond. I'm familiar with the Salmon up in your neck of the woods (used to mine in it!). It's super beautiful, and has a lot of the same problems with fisheries as the one in the article.

Sure, I can see how that might be the case. I don't think it is, though, because I'm actively looking and seeing what the mix is. I'm noticing what everyone has, not just when it's a Surface device. And over the last several years the amount of Surface devices (nearly all Surface Pros) has increased a lot. They are very common.

Fair enough. I appreciate you criticizing from your vantage point rather than a point of universal truth. I have a surface book. I've had two over the last couple years. For me it's amazing. It's light, portable, well built, looks good, and the touch screen with stylus lets me sign PDFs and return them. I 100% do real work with it (and it helps me an my company make (sometimes lots) of money. Which is great, that's what I need my equipment to do. It also lets me game when I'm on the road and stuck in a hotel or airport and I don't feel like working. Some of the games, like Human Resource Machine, also do great with the touchscreen, so it's modular form factor and touch work well for me.

You nailed this. Your experiences match my own. I have had a couple Surface devices over the last few years and also support some coworkers with them. You are spot on with your observations.

See, that's weird! I *am* that guy! I see them all the time in airports. I fly anywhere between once a month to once a quarter, and they are all over the place in airports. Full disclosure, I also have a Surface Book, and I go out of my way to look at what people have because I'm always curious about the mix of equipment I see out in the world.

I suspect you are right. The old apps that we use (and love) have mostly existed for a very long time, and have developed a lot of functionality over time. It takes a *ton* of work to do a rewrite that is feature complete. I think it's why some of the "new" stuff, like the UWP PDF readers are pretty great: they are new and aren't ports of existing stuff. They just started scratching the developers' biggest itches, and consequently are really good (sometimes) at what they do.

You really don't. The "legacy" client isn't going anywhere, and runs just as great as ever. In 5 years maybe it will be different, but then again, in five years it will be different!

Man, there are days that I think it's the best piece of software Microsoft has ever created. I use it every day, and it's fast, easy to use, and has great searching and some thoughtful workflow options. It has clients for every platform (that I use). I love it. I'm kinda bummed about the transition, because the "legacy" client still does quite a bit more, but the modern version is slowly catching up, to the point where I at least don't mind using it.

Sure it does! There is literally a sprint planning meeting that happens at a set interval. It's literally baked in. Beyond that, teams should be experimenting to find out what planning strategies (including style and quantity) they need, and crucially, are working for them (as determined on a set schedule as part of the retrospective). You didn't give me much to work with, but I feel like you are working from a basis that is... misunderstood.

I'm no fan of ITIL, because I think it's overkill for almost everyone. But Agile? What's not to like about planning, developing, and evaluating the outcome of your work regularly? What's not to like about having the right amount of specs/documentation? What's not to like about letting the experts (the developers) work in the way they see best?

Gawd yes. You are the first person that I think nailed this. It's nuts. Somehow our culture has distilled into "I can be an expert after a 10 minute youtube video" and it's ruining us. A scrum master and product owner should be just as committed to expertise in the framework as developers are to writing good code. *That* engenders respect and, I posit, results that are actually good.

But if you actually *aren't* doing it right, then it's not a failure of the framework! And it's nuts how many people *don't* do it the right way. Hell, look at the top comments right now... 6 hour standups. Christ, I could make good money doing scrum consulting. If standup is timeboxed to 15 minutes, and you take 6 freaking hours... then you can't blame the framework, because you aren't using the framework. It's like me blaming my Ferrari for sucking at off-roading, and it turns out I really drive a Ford Focus. It's NONSENSE.

I really, really, *really* doubt that organizations like that have a scrum certified anybody around! Every time I see this, it's because someone thought they could read and article or watch a "scrum in 10 minutes" youtube video and then do it with perfection.

That hasn't been my experience, but I'm glad it's working for you!