Both are terrific but I prefer the georeferenced one. You could toggle a satview underneath it.

Google meet seems the smoothest. You can have a persistent link address that any group of people can use at will.

I would like to hear about best practices also. The context window fills up pretty fast in my work.

I'm a Windows person who also did a Mint install or R and RStudio. I didn't find *much* more work. R2U is a must. eddelbuettel.github.io/r2u/

Wait, what? You can do that?

Very cool, Jake. Too bad you can't climb the pyramid any more. The view from the top is something. Though that rule is in place for a good reasons - preservation and danger.

Great stuff! Let me point out you should always use the duckplyr package on top of duckdb. With it you never have to do SQL translations yourself, just dplyr syntax and it’s even faster! outsiderdata.netlify.app/posts/2024-0...

The funny thing is Trump could end this war "tommorow." The Russians don't need to lose they "just" need to be convinced they will never win. And that is in Trump's power, he's just too dumb to see it.

In all seriousness, I have noticed that RStudio has starting hanging for me, often, in the last two weeks.2025.05.1

Oops. Forgot. Code here

gist.github.com/apsteinmetz/...

I should also point out this is gage height CHANGE from baseline before storms.

repost since animation of previous post was not...animated, for some reason.

The numbers don't lie, but....all languages are "dead." Long live "vibe."

I'm an old R-dog who can't write "Hello World" in Python, so I asked Claude to make a Shiny4Python app to display historical yield curves, just because. A few prompts and viola! Sort of takes the fun out of life.

excuse the typo. I am estimating the year the book was published, not when the author reached "pubish."

Here's the trivial #rstats code. I crudely estimate the publish date as birth year + 18 + half the lifespan after 18. Opinions may vary.