Vinicius Oike

When I say that Claude is very good at coding in R, there are caveats.

As G10 countries succumb to simplistic populism, reckless fiscal policy and fiscal dominance of their central banks, the line between the G10 and EM is getting blurred. Real long-term interest rates in the G10 have begun to rise towards EM levels...
robinjbrooks.substack.com/p/the-global...

Closeread Prize winners are here! 🏆

Want to create engaging, scroll-based stories with your data? See stunning scrollytelling examples made with Quarto: posit.co/blog/closere...

Learn more about Closeread and its power to create dynamic narratives. Congrats winners! #Quarto #RStats #Python

Claude can be savage at times

What happens when you get lazy and don't follow your own advice...

Happy to know I'm not the only one who creates a ggplot2 theme package for every company I work with #positconf.

Not only does it standardize communication, but it also makes a great impression. theme_quintoandar() took about a day to make and led to me reporting directly to the C-level.

One strategy I'm using is to ask ClaudeCode to write a small summary of what it's done + add context for future work when it's almost done with a task. I then use /clear, ask Claude to read the document, and give it instructions on the next task.

4. Avoid auto-compacting

The last point is directly tied to this one. ClaudeCode has a context limit (the UI warns when approaching this limit) and it auto-compacts by default. The quality of compacting can sometimes be unreliable and I found it best to just workaround it.

You can ask for ClaudeCode to take notes of useful information and store it in separate md files to help build this knowledge.

Claude R Tidyverse Expert Claude R Tidyverse Expert. GitHub Gist: instantly share code, notes, and snippets.

A great example of useful context to provide Claude with (from @sarahjohnson.io) gist.github.com/sj-io/3828d6...

3. Knowledge

Anthropic recommends that you create a CLAUDE.md file to store important context. Currently, I'm experimenting with an entire claude/ directory stashed with useful content. Before starting a new task I ask Claude to read the relevant content.

Ex: I asked ClaudeCode to download an Excel file, import it in R, and make it tidy. The download, however, failed due to network issues and Claude decided to invent a dataset with fake values instead of stopping and pointing this error.

2. Manually approve

While ClaudeCode seems magical when it "just works" it often doesn't. Auto-accept can lead to errors that hard to detect since Claude can sometimes omit them and say that everything worked according to plan.

1. Make plans

Always start a new task in plan mode and invest some time making sure that Claude has a solid plan. A neat tip from Anthropic is to use "think more...", "think hard about potential issues...", "think step by step ... ".

"think" < "think hard" < "think harder" < "ultrathink."

Been working with ClaudeCode for the past ~2 months (mainly R and Quarto). My main tips:

1. Plan a lot.
2. Manually approve (auto-accept only for very simple tasks).
3. Create knowledge that can be referenced.
4. Avoid /compact and auto-compacting.

I've been using Air since switching to Positron and have been loving it. My only criticism is the styling of tibbles (it just breaks them). Apparently that has been solved

# fmt: tabular

coming soon

#PositConf

The fastest way to start using & exploring the new 2024 1-year ACS data?

R with tidycensus + mapgl.

With just a few lines of code, you can pull down any of the thousands of variables available in the new data and explore on an interactive MapLibre map.

Bolsonaro Convicted of Attempting a Coup in Brazil, Sentenced to 27 Years in Prison Brazil’s Supreme Court convicted the former president of trying to cling to power after losing the 2022 election, including a plan to assassinate his opponent.

Jair Bolsonaro was sentenced to more than 27 years in a Brazil prison for attempting a coup after losing the 2022 election.

Claude R Tidyverse Expert Claude R Tidyverse Expert. GitHub Gist: instantly share code, notes, and snippets.

I was loving Claude Code... until I tried it with #rstats. Constant errors, wouldn't use the tidyverse even when asked, "optimized" functions were slower.

Frustrated, I started a session just to teach R to Claude and summarize what it learned into a CLAUDE.md file gist.github.com/sj-io/3828d6...

Saw a post from an influencer telling followers to "stop using R for anything -- use Python like a normal person"

As a 10+ year R & Python user, the irony is that 2025 is the best time EVER to be using R.

Here's why:

a computer monitor displays the message data does n't lie ALT: a computer monitor displays the message data does n't lie

Worst of all, since the numbers were generated with *data* they were heralded as an objective fact of the universe.

The new dot com bubble is here: it’s called online advertising In 2018 $273bn was spent on digital ads globally. We delve into the world of clicks, banners and keywords to find out if any of it is real. What do we really know about the effectiveness of digital ad...

What a great piece on online advertising. Summarizes beautifully my frustrations when working as a data scientist (with econ background) in a big marketing department.

Leaders justified decisions with bad metrics, fueled by biased samples.

thecorrespondent.com/100/the-new-...

There's certainly some latin to know in economics: ex ante, ex post, ad hoc, per capita, ceteris paribus, de gustibus non est disputandum...

I recently made this switch. Took me about 2-3 weeks to get adjusted but I've been enjoying Positron a lot. Highly recommend reading this positron.posit.co/migrate-rstu...

Fun with Positron | Andrew Heiss Combine the best of RStudio and Visual Studio Code in Posit’s new Positron IDE

Forgot some Positron shoutouts,

@andrew.heiss.phd has a nice post talking about Positron (www.andrewheiss.com/blog/2024/07...) and Albert Rapp also has one (3mw.albert-rapp.de/p/using-the-...)

I do plan on splitting up my site. I think it's a bit too all over the place, and I find myself second-guessing whether I should write in Portuguese or English, whether I should break down my analysis in a tutorial or just present it as is, whether I should show the code or hide it, etc. etc.

I'm both glad that I kept on doing my side projects and that I no longer work there 🙏

At a previous workplace, I discovered that some of my coworkers were actually quite dissatisfied with my website, suggesting I was slacking at work and focusing only on personal projects. This reached a point where it was implied I should stop completely (delete the site and stop side projects).

It features a bit of everything I like, and both the tone and content of the posts reflect different phases of myself.

Over time, it became kind of a repository for everything I did. Sometimes I even created posts with snippets of code I felt like I was using a lot and having it online made it easier to find later.

I'm very proud of my site and I'm glad I kept on posting throughout the years.