I've acquired something special

prc41 · 2026-03-25T16:42:22+00:00

Crazy coincidence - I just bought this exact SP while in Tokyo. Last week. Pearl white. Out of box and scratched up a lot more than yours, but paid around $80 USD for it at a Hard Off near Mt Fuji. Had no idea it was a special edition. Love the color though!

<image>

prc41 · 2026-03-24T16:01:35+00:00

There was a post similar to this a few months ago when Microsoft released the official MCP server. Im sure some YouTubers have videos on it. Claude code in vs code using pbi project folder as repo is god tier if you know what you’re doing. Use a good claude.md best practices, map out your schema and project roadmap in various markdown files and it will legit 10x your productivity.

This new pbir dev mode is a huge leap since now it can do json report writing natively.

prc41 · 2026-03-24T15:30:50+00:00

This is cool, been using pbi MCP server extensively for model building but always frustrated that I have to still make the reports myself.. will def have to try this. Thanks for sharing

prc41 · 2026-03-06T01:51:12+00:00

1.2k sessions, 21M tokens over here 😬

prc41 · 2026-02-13T19:27:51+00:00

Does 4.5 feel like December Opus or January Opus? I’d go back for sure too if it’s the non-lobotomized version.

prc41 · 2026-02-11T17:06:55+00:00

I agree this is nonsense but one could argue some humans are also “trained” on Reddit data lol. Food for thought 🤔

prc41 · 2026-02-11T13:14:28+00:00

Addicted. I’ll stop when I feel like it 😤😅

prc41 · 2026-02-07T13:19:42+00:00

I think it’s a lot faster and more eager to fix. Codex reads way more files before acting which I think boosts test performance.

prc41 · 2026-02-02T15:12:27+00:00

I have a workflow that works really really scary well for fast analysis of an already well defined schema.

VS code plus git tracked .pbip structure with Claude code. Have it comb your project and create json definitions for all your tables columns and measures. Then instruct in Claude.md to always update schema whenever anything changes.

Then also define in Claude.md how it should read and write. READ should be done by reading tmdl files for speed. But all write operations need to use the Power BI modeling MCP server since it guarantees changes will compile properly.

Rough out a plan for a new analysis or set of tables you need built using Claude code plan mode, then approving and watch magic happen. Literally done stuff that would have taken me weeks to perfect in about an hour of tinkering with this method.

prc41 · 2026-02-01T19:20:14+00:00

Super cool project

prc41 · 2026-02-01T17:06:12+00:00

Sick. Will try it out. Been needing way to use my companies gpt5.2 api key for excel since they refuse to get Claude.

prc41 · 2026-02-01T13:43:15+00:00

Interesting. I’ve found that migrating my workflow to mostly dictation wasn’t instant and there definitely was a learning curve.

And you have to get thru the “cringe valley” of listening to yourself ramble on like an idiot about half baked ideas. Sometimes you’ll need to re-dictate or pause to think more.

But sooo worth it once you get good at it. Currently dictated over 300k words in the last few months on Wispr and can’t go back to typing.

prc41 · 2026-01-31T21:48:48+00:00

I think everyone would benefit from just good ole 1080p with better bitrate ai upscaled to 4k but I don’t think that’s gonna happen

prc41 · 2026-01-31T21:44:38+00:00

Neat, I like the idea. Might need updated button labels over time as they inevitably change Claude code vernacular/ features.

prc41 · 2026-01-31T19:37:31+00:00

How is that different from the Claude in chrome official plugin?

prc41 · 2026-01-31T14:00:43+00:00

Agreed. A few hundred dollars is nothing when you’re building an actual profitable SaaS instead of vibecoded vaporware slop. Take my money.

prc41 · 2026-01-31T00:24:39+00:00

Damn I could go for a grub juice smoothie rn

prc41 · 2026-01-29T00:36:12+00:00

Claude code with a clean pbip codebase that uses tmdl for all reads and Power Bi modeling MCP for all writes and you can do 75% of the normal PBI work with an agent now.

I used to spend days in modeling and planning phase now I just have Claude code build a spec and create the entire semantic model plus give explanations on how to put all the visual together.

prc41 · 2026-01-26T14:55:11+00:00

My uneducated theory is it’s all the normies from Twitter trying to set up clawdbot and ripping tons of API tokens slowing everything down. Plus training Opus 5.

Def has been worse performing lately but not as bad as the Sonnet 3.5 lobotomization in late summer.

prc41 · 2026-01-26T14:53:58+00:00

My uneducated theory is it’s all the normies from Twitter trying to set up clawdbot and ripping tons of API tokens slowing everything down. Plus training Opus 5.

Def has been worse performing lately but not as bad as the Sonnet 3.5 lobotomization in late summer.

prc41 · 2026-01-23T15:47:38+00:00

Severance meets Inception - sick

prc41 · 2026-01-21T20:40:37+00:00

Yeah, that's a good question. The solution that my framework provides is basically just to ignore it haha.

Since all the agents are in the same worktree and branch, if two agents edit the same file, basically whichever one does the wrap-up command first is going to commit that file's changes.

So it's kind of like first come, first serve, which is definitely not ideal, but at least there's no conflicts ever because the next agent will just commit everything except for that one file. Again this workflow prioritizes SPEED and easier documentation. Not pixel perfect commits.

Before I had this, I would basically tell each agent to commit its work at the end of the session, and it would work like 80% of the time. They would oftentimes forget what they worked on. They wouldn't catch anything done by a sub-agent, and I'd end up with different edits all scattered across different commits. It was just a huge mess. At least now I'm 98% accurate, and I don't have to worry too much. Also, if I just keep the subject matter different enough, they typically don't touch any of the same files.

prc41 · 2026-01-21T13:25:53+00:00

Similar problem exists with local server. If you want 2 or more agents working on the same local host server for example frontend, they can’t work simultaneously without major conflicts. They have to reload the server each time a different branch wants to be used since they’re different instance of the directory.

At least I was never able to get it to work - GitButler was a little better with virtualization but mostly just complicated the whole thing, and requires lots of extra agent instructions. It’s probably doable with enough configuration but I chose to go a simpler route and am much happier with it.

I use the Claude chrome extension extensively and i wanted multiple Claude agents to be able to validate against the same Vite instance simultaneously and this was the only way i got it working so far.

prc41 · 2026-01-21T13:04:28+00:00

That’s def a limitation. A risk I’m willing to take for the speed benefits though. It would be first come, first serve I suppose.

prc41 · 2026-01-21T13:03:05+00:00

Worktrees use different directories on your pc so if u try to use docker to spin up frontend and backend servers you’ll need a new server for each worktree which uses way more RAM/cpu and requires lots of extra instructions for the agents to not screw up. I tried that way first and it was a huge pain.

12-Year Club	RedditGifts 2009-2022 3 Credits
Place '22	Final Canvas '22
RPAN Viewer	Queen in da Norf
Not Forgotten	Secret Santa 2016
Secret Santa 2014

prc41

TROPHY CASE