chunkymilk

There is no requirement to send prints through their servers. My P1S has never been logged into their cloud service in the year I've owned it.

It depends on where the hike is: Dropping an orange peel in a humid, temperate, low-elevation place is vastly different than a desert, high-alpine, tundra or other environment where organics take a long time to decompose.

Thank you for sharing this. It's the sub I didn't know I needed.

This was outside of Boulder, in Westminster, just west of 25 on 136th.

This was my experience when I moved to CO. On the east coast I had to drive to running trails and cycling routes by my house had no shoulders and a lot of traffic. In CO I had access to 120 miles of trails from my backyard and the roads had either dedicated bike lanes or wide shoulders.

Add in a walkable grocery store and I was a lot more active in CO than I was on the east coast.

> Always be kind, and say it’s your fault.

I do this with internal teams at work. I've found approaching other teams with issues with their library/framework in a "this could be our mistake" manner really helps in keeping them from getting defensive and stonewalling.

I've made the mistake of driving home (to Philly) the day after IM Lake Placid the first time I raced it.

It's bad for a number of reasons, but the punch-drunk feeling was unexpected.

I made sure to stay an extra few days when I did it again.

The only "rule" around vacation is the longer the vacation the more notice you _should_ give. I've had colleagues take 5-6 weeks off, but they let the team know 4-5 months in advance so it wasn't a big deal and we could work around it.

I had the same thought looking at the photo of the level standing upright. Looks like the OpenGL programs I wrote in college.

Can't disagree. He's was doing what the incentives in place said he should be doing.

I would find it boring/tedious to keep rebuilding the same thing since I'm more of a solve the problem, operationalize the solution, then move on person.

My last place also called it promotion-driven-devevlopment.

It got to the point where some dude built a system that completely floundered but got him a promotion. He then re-wrote it so it sucked slightly less and got another promotion. Last I heard he was working on v3.

Never mind that someone with actual domain knowledge would have either not built the system (since it didn't _really_ need to exist) or would have built a much simpler/more reliable system to get the job done.

I don't but know folks who do. They keep track of things they want to watch until they get to the point where subscribing for a month makes sense then cancel at the end of the month.

The hard part is keeping track of what you want to watch and what service it's on and whether it's still there when you want to watch.

The "Judging Sam" podcast had some color on this from a reporter who was there. It felt to them like she was a bit overwhelmed at being walked into a packed courtroom with everyone staring at her then being asked to point out a guy who's appearance had changed a lot recently (haircut and suit/tie).

Personally, I can't imagine being very composed in that situation at that age.

My background is in linear (title VI and OTT) and ad-insertion. A big chunk of my job is explaining to folks that just because you solved VOD that doesn't mean you've solved linear. It's almost best to think of them as two distinct problems.