Ingo @ifeulner - Twitter Profile

ifeulner retweeted

Tom Dörr

@tom_doerr

26 days ago

Scrapes German real estate sites for instant alerts https://t.co/v0WrH7vBQy

6

703

30

1K

58K

ifeulner retweeted

divyansh tiwari

@DivyanshT91162

about 1 month ago

What if I told you… you could open a 200,000-line legacy codebase and instantly understand it — without reading most of it? Sounds impossible, right? That’s exactly why this is blowing up. A GitHub Trending #1 project — Understand Anything (21.8k stars) — is quietly turning entire codebases into something completely different: Not files. Not folders. But an interactive, queryable system of logic. You don’t browse code anymore. You ask it questions. • “What does this module actually do?” • “Where does the payment flow start and end?” • “Who depends on this function?” • “What breaks if I change this?” And instead of dumping files at you, it traces the real structure of the system and answers directly from it. Then comes the real shift: Before making changes, you run "/understand-diff" And it shows: • exactly which modules will be affected • hidden dependency chains you would never notice • potential breakpoints before they become production incidents No guessing. No blind edits. No “hope this doesn’t break anything”. It plugs directly into Claude Code, Cursor, and VS Code — so it lives where you already work. But the real transformation is deeper: You stop reading code to understand it. And start interacting with it like a system that already understands itself. Once you experience that… traditional codebases feel broken. Repo👇

12

126

20

277

15K

ifeulner retweeted

Ole Lehmann

@itsolelehmann

about 1 month ago

POV: claude traveled 6 months into the future and told you exactly how your next move failed. it's called a premortem. daniel kahneman (nobel prize-winning psychologist behind "thinking fast and slow") called it his single most valuable decision-making technique. when you ask claude "is this a good plan?" it finds all the reasons to say yes. that's what it was trained to do (to be helpful and agreeable). so you walk away feeling confident. you execute, and spend weeks / months building on top of that plan. then it blows up. and you realize the problem was obvious in hindsight, you just never stress-tested it because claude told you it was solid. a premortem fixes this by flipping the frame. instead of asking "what could go wrong?" you tell claude "it's 6 months from now and this is already dead. tell me how it died." that shift turns off claude's optimism because there's nothing to be optimistic about. the premise already says it failed. so claude stops looking for reasons your plan will work and starts explaining how it fell apart. claude comes back with every way your plan could die, each one with a full failure story and the early warning signs to watch for. then a synthesis pulls it all together: > which failure is most likely > which failure is most dangerous > the single biggest hidden assumption you're making (often the most valuable part) > a revised version of your plan with the gaps closed you say "premortem this" and give it your plan. the skill handles the rest.

itsolelehmann's tweet photo. POV: claude traveled 6 months into the future and told you exactly how your next move failed.

it's called a premortem.

daniel kahneman (nobel prize-winning psychologist behind "thinking fast and slow") called it his single most valuable decision-making technique.

when you ask claude "is this a good plan?" it finds all the reasons to say yes.

that's what it was trained to do (to be helpful and agreeable). so you walk away feeling confident.

you execute, and spend weeks / months building on top of that plan.

then it blows up.

and you realize the problem was obvious in hindsight, you just never stress-tested it because claude told you it was solid.

a premortem fixes this by flipping the frame.

instead of asking "what could go wrong?" you tell claude "it's 6 months from now and this is already dead. tell me how it died."

that shift turns off claude's optimism because there's nothing to be optimistic about. the premise already says it failed.

so claude stops looking for reasons your plan will work and starts explaining how it fell apart.

claude comes back with every way your plan could die, each one with a full failure story and the early warning signs to watch for.

then a synthesis pulls it all together:

> which failure is most likely
> which failure is most dangerous
> the single biggest hidden assumption you're making (often the most valuable part)
> a revised version of your plan with the gaps closed

you say "premortem this" and give it your plan. the skill handles the rest.

62

2K

247

4K

374K

Ingo

@ifeulner

Who to follow

Last Seen Users on Sotwe

Trends for you

Most Popular Users