Shalomboy

The request definitely comes from the leagues' broadcast partners, right? They would want as many eyeballs concentrated in as few places as possible so they can sell ads for more.

I wouldn't take it that far. For most users we spoke to, its often a reflex to deny location privilege popups, and on mobile it wasn't easy enough to fix once denied. However for some of the less-engaged folks who might be out in the park casually and stumbled on something worth sharing, the idea that we need their exact location probably sounded overbearing. "I told them which park I was in, that should be enough!"

Yeah no kidding the vulnerable animal population is in the park, that's where all their threats are removed. But sometimes "the park" is 60,000 acres and it would be nice if you could help narrow it down.

You're absolutely right. Highways are a little better since they have mile markers, but once you get into a nature preserve you're dealing with a whole bunch of "If you pass the pond with the cattails on your left, you've gone too far." Fishermen, it turned out, LOVED sending coordinates for stuff they saw so long as their fishing spot wasn't nearby.

Cool article btw!

> I bet you could include this in a state parks app that you could also use for other useful purposes, like pulling up trail maps, paying for parking and camping, fishing licensing, signing up for volunteer events, receiving notifications with news around particular parks you frequent, etc.

I wanted us to do this so badly; inter-agency coordination was the biggest issue with I had with large-scale projects. The funny part about your comment is that each feature you listed was a function that a different agency or contractor handled. I won't name names, but the agency I worked for had better-than-expected public outreach and engagement and were organizationally flexible enough to get low-footprint, high-impact conservation PR like this out the door and in front of people in time to make a difference. But in state government, the idea of several agencies pooling resources for a permanent app store project is totally pie-in-the-sky thinking largely because nobody has the bandwidth to contribute. I'm trying to imagine submitting a PR to 'The State Parks App' org board to get this form shipped and in every instance, I'm getting yelled at.

> If people are wary of sharing their location with the conservation agency, you might have better luck if the website was run by a nongovernmental conservation group?

Our NGO partners were incredible for this sort of thing. People legitimately do not think twice about pinging a facebook group run by, say, the local aquarium and including their location, a description of the site, and photos of what they found. Social media removes a lot of metadata from uploads - they probably keep it someplace and I just can't get at it without a brokerage, idk - but it still gets better results than we did. One fix for the tortoise problem was to supply personal trail maps and golf pencils at trail heads. Hikers were encouraged to take them, mark on the map where they saw burrows along the trail, and put them in a box at the end of the trail/parking lot/ranger station. Park rangers would scan in the maps and upload the scans to our internal site and we would work it out from there.

I was being facetious there, to be clear. my bad.

Oh that's fascinating. I hadn't considered OS-level fuzzing as a hurdle until now. I'm an pixel guy and typically I get decently-accurate location heatmaps in the Photos app when I search by location; I wonder how we would have handled this. HABs are so difficult, they break my heart.

Well that's just it - in most of the submissions the coordinates weren't supplied at all, and when any location information was given it would come down to just a city name or a park name. They're trying to pipe these results into ArcGIS to inform park rangers where to reroute trails, public works departments where to survey before digging, and real estate developers which lots need proper relocation assistance before building on. They were depending on the average citizen to know how to fill out a technical field in this form and to do so accurately, and without and form validation. The whole project needed re-thinking.

My first eye-opening moment working within the government was with team of herpetologists at the state conservation agency. They had a pretty slick public education campaign around protecting Gopher Tortoise habitats and a grand call-to-action "let the agency know where and when they see their nests". The whole thing fell apart because they were getting tons of earnestly-submitted junk data from earnestly-engaged citizens. Turns out the application was just a form that they asked people to fill out. I suggested they ask for user photos and scrape the EXIF data or ask them to opt-into sending their location and got laughed out of the room. Turns out that they discovered users immediately nope out of government websites that ask for their location! What a shame.

Not OP but I would love to check that out

You should try getting _extremely_ good at Trading Card Games. Pokemon, Yu-Gi-Oh, and Magic The Gathering all have extremely active current player bases and loads of places to play across the Americas, Europe, and (mostly east) Asia. Getting deep into card advantage, deck construction, and hypergeometric theory has been an absolute blast. Plus, the online simulators are free for Yu-Gi-Oh and Pokemon are free and pretty current with the paper game. Making new friendships with people not in my usual circles has been so rewarding, I can't recommend it enough. Not to mention the most meaningful contribution of all - winning events moves the needle on the way the rest of the playerbase plays the game. I could go on and on about this.

This is a wonderful-looking infographic, but I truly don't think there are 49 GPUs that mattered in the PC gaming hardware space - let alone all of computer graphics. Call it recency bias, but after the Pascal cards it feels like maybe one or two more entrants actually mattered?

are there though?

Outstanding article; I'm glad you put these thoughts into words and published them because I've felt similarly this week since I've had time and reason to reminisce on my 2010 MacBook. I had AutoCAD on that poor little computer, working at the pace it could handle.

This is such a better deal than I had growing up, Apple has to be taking a bath on these.

My high school required students to bring their own laptops to school when I started in 2010. Their shopping list suggested a MacBook Pro 13" with a case - I looked up "MacBook Pro price" for the first time in my life and just about walked into traffic. I didn't have a laptop to bring, I didn't want to bring the wrong kind of laptop and get double-screwed, so I bit the bullet and brought my car savings to the Apple store at the mall. A tremendously thoughtful sales rep told me "that's crazy, what school requires a MacBook Pro for 9th graders?", led me to the white unibody MacBooks on the side, and showed me that if I was buying it for school, I would get a discount on the laptop, a free inkjet printer (with ink!), and a free iPod Touch. This blew my mind. I thought it was a scam.

If I recall, that model of MacBook compared admirably against the same year's base model MacBook Pro 13 on a stat sheet but felt worse in hand. The MacBook Neo might actually bring up the rear on fit and finish at the expense of I/O and like, the questionable idea of running an A-series chip in a laptop running Tahoe and Chrome. I'm thrilled with this release.

I could use a laugh today, do you have a link to the leica comment? It wasn't that one review of the Fuji X Half, was it?

> K-to-12 edu customers don’t care for that and just want a keyboard with a screen with dead-simple admin options.

Which is why I highly doubt this is a play for the K-12 education space. Lots of school-owned chromebook repairs get done at the district level before making their way to the OEM for RMA/replacement. There's no way Apple is supporting that system, they'll want all repairs done under their roof. Not to mention MacOS adminware options lag behind what's built-into ChromeOS. Are you really gonna tell your severely-underpaid sysadmin to put 10,000 devices on Kandji? They'll walk into traffic before you finish speaking.

Agreed. The SWEs already receive a steady supply of conflicting demands from every possible business unit; the value add for these teams is a working PMO to prioritize the requests coming in.

Google bought out HTC 8 years ago to the day, and if I recall correctly that exacerbated a lot of the tension in the Android OEM space that the original Google Pixel rollout caused in the first place.

I've been a pixel guy since HTC was making them for google, and honestly jumping from the 6 to the 9 has made me think that pastures are greener someplace else.

This is true for bricks, but it is not true if your dog starts up your car and hits a pedestrian. Collisions caused by non-human drivers are a fascinating edge case for the times we're in.

My favorite manager told me a similar analogy before I left, but with a caveat; a good manager has to provide cover for the team, but it's up to the team to hold the manager up - just like an umbrella.

Well that's clearly an example of putting the cart before the horse. You should be able to sleep at night so long as you remember that Git isn't what enables Palantir to power an army of federalized brownshirts; it's the people making the tools explicitly for an army of federalized brownshirts with Git that are morally culpable.

I found Blazor WASM to be extremely helpful if you have to start from the opposite side of the spectrum. I was working in a self-proclaimed gov agency "Microsoft Shop" whose head of development was adamantly opposed to any sort of JS-driven web app development, but kept accepting requesting apps that fit perfectly into the SPA model. .NET 6 released a few months after I started and with it came a huge amount of progress with Blazor WASM. I had plenty of experience with Vue and Typescript, so Blazor WASM and C# mapped really easily to my existing model of how to build. That similarity also made it easy to onboard new grads who had experience in web dev but weren't familiar with C#. After enough evangelizing, we built a critical mass of projects leveraging Blazor WASM to convince leadership to reconsider his position on Typescript. I can't say enough nice things about the work Steve Sanderson has done to bring Blazor to the public.

Well first off, it is very expensive. Vendors that supply to DHS and DOD have to be selective about who they sell their services to as well. Citizen-developed services to track ICE are routinely shut down by Apple and Google.

> Another thing to consider, it seems JS devs use more AI for work than .NET devs for example, which might be in more old-school companies and industries.

Speaking from years of .NET work in state and federal government, the sort of dev groups that lean on Telerik or DevExpress have less leverage to build new things for themselves than you would expect, so the use of AI inside of them is predominantly for maintaining existing software. Decisions on how things get built at most public agencies still revolve around MS Access and WebForms due to a whole bunch of BS ordinances that legislators put in place; for those sorts of places a reliable vendor can absorb the blame if concerns surrounding accessibility, compliance, or security of your ancient web services crop up, while Claude and Codex put the liability back on your org.

Not to diminish your skepticism, but your reply comes off jaded in a way that might be hurting you. The author's suggestion for employees seeking promotion is to operate on a higher level than they're asked to and keep operating in that fashion for a sustained window of time. Show growth, in other words.

Russell paints a convincing picture of cargo cult programming with this article, but it all seems to hinge on the supposition that the datasets are compiling complete logs of what web developers are doing with all their SPA-driven DOM manipulation capabilities. I'm happy to be proven wrong, but the idea that developers are just recreating MPAs with React sounds silly.

There will still be new engineers, scientists, and doctors by then. But aptitude won't be a factor in who matriculates into those fields anymore. That's the worrying part.

The author hints at this idea with their title and their closing remarks, but it feels like the folks selling LLM services are selling insurance to white collar workers. I wish they had expanded on this observation more, rather than harp on the WSJ puff piece for being silly.

That's a non-starter if you want to maintain any sort of upward mobility in Florida.