@ajay4ai I was blamed over a year ago to be so 90s when I started to do 'exactly' this but with different AI models/agents.
Well, now it is
a) the 90s or
b) not back to the 90s but 30 years later
However, from experience I can tell, this saves tons of tokens and computing time.
GITEX AI 2026 Berlin, quite small but with surprisingly nearly no typical exhibitors. Also the talks and the staff at the booths where surprisingly experts, not the typical staff at all.
@GITEX_GLOBAL go on like this, happy to come back next year.
It is so said to her that he died and good to know he had a good life. By many meanings he was a mentor to me and I learned much more about life and doing things from him than from most other people I can call my mentors. Luckily I was able to say thank you when we met last time
Alan Greenspan, who piloted the economy through two decades of global upheaval but who critics say fell short on financial regulation, has died. He was 100. 🔗 https://t.co/UPJ7MygfMN
Eine SMS von Amazon:
[...]
Ich werde bald mit deiner Lieferung ankommen. Bitte stelle ggf. sicher, dass deine Haustiere in Sicherheit sind und schalte das Licht ein, wenn es dunkel ist.
[...]
Nun, der Lieferant garantierte keine Haustiere anzugreifen 😌
Don't just reset Codex rate limits for fun, it costs money.
Don't just reset Codex rate limits for fun, it costs money.
... but the vibes are good ...
I have reset Codex rate limits for ALL paid plans to celebrate a good week and allow everyone to build more with GPT-5.5. Enjoy
The creator of Claude Code Teaches more about vibe-coding in 30 minutes than most paid tutorials do in 10 hours.
Absolutely Free. From the guy who built the tool.
Save it. Watch tonight. It'll change how you build forever.
You've been using Claude Code wrong for months without knowing it.
This fixes that in 30 minutes.
Follow @codewithimanshu for more high-signal content that actually moves your career forward.
↓
Boris runs technical staff at Anthropic.
He built Claude Code.
He just gave away the entire playbook.
This is the talk that separates people making $10K/month with AI coding from people still Googling "how to fix this error."
Here's everything he covers in 30 minutes.
Follow @codewithimanshu, I break down a video like this.
↓
Installation and setup the right way.
Not the wrong way you did it.
`npm install` to get Claude Code running.
`terminal setup` to enable Shift+Enter for new lines and themes.
GitHub app integration to @-mention Claude directly on issues and pull requests.
Mac users: system-level dictation for hands-free prompting.
Most people skip these steps and wonder why their Claude Code workflow feels clunky.
Follow @codewithimanshu For Full Claude Code setup guides.
↓
The workflow most users miss entirely.
Codebase Q&A is the real starting point.
Not "write me code."
Ask Claude about your codebase first.
It explores locally. No indexing. No data upload.
You can ask:
> Why was this function written this way?
> What did I ship this week?
> What's the git history of this file?
Understand the codebase before you touch it. That's how senior engineers think. That's how Claude Code wants to work with you.
Follow @codewithimanshu for more high-signal content that actually moves your career forward.
↓
Interactive coding that actually ships.
Claude uses file editing, bash commands, and file search to execute tasks in real time.
Boris's rule: brainstorm and plan BEFORE you trigger code generation.
Skip the planning step and you get garbage. Do the planning step and Claude ships production-ready code.
This alone is the difference between "AI wrote my app" and "AI wrote an app that actually works."
More ship-ready Claude prompts already posted on @codewithimanshu.
↓
Tool integration nobody uses.
Custom CLI tools. MCP servers. Integrated directly into your Claude Code workflow.
Claude calls your tools. Uses your data. Executes tasks across your entire stack.
This is where Claude Code stops being a coding assistant and starts being a full engineering team.
Follow @codewithimanshu for MCP server breakdowns every week.
↓
Iterative feedback loops.
Give Claude access to your unit tests. It refines until they pass.
Give Claude screenshots of your UI. It iterates until the design matches.
Most people run Claude Code once and accept the first output. The best users build feedback loops that let Claude improve itself.
I share the exact feedback loops I use daily.
↓
Context management: Claude MD.
Place a `claude(dot)md` file in your project root.
Persistent context. Shared across every session.
Enterprise config for global policies across teams.
This is the file that separates hobby Claude Code users from production users.
I'll post my full claude(dot)md template next week.
Follow me @codewithimanshu.
↓
Slash commands and memory.
`/memory` to view or modify how Claude remembers instructions.
Slash commands for automating complex workflows.
Example: auto-labeling GitHub issues with one command.
Slash command library coming soon on @codewithimanshu.
↓
Pro key bindings Boris drops at the end.
Shift+Tab: auto-accept mode for edits. Saves hours.
!Command: execute a bash command and pipe output into context.
Escape: safely stop Claude without corrupting your session.
Drag and drop images. Paste screenshots for UI implementation. Multimodal from day one.
Follow me @codewithimanshu for Daily Claude Code tips.
↓
30 minutes from the guy who built the tool.
You'll learn more from this than from 50 YouTube tutorials made by people who've never shipped production code with Claude.
This is where the gap gets built.
People who watch it understand Claude Code at the architect level.
People who skip it keep copying commands they don't understand.
Save the video. Watch it tonight. Build something tomorrow.
Follow @codewithimanshu for more high-signal content that actually moves your career forward.
We are hiring a Head of Preparedness. This is a critical role at an important time; models are improving quickly and are now capable of many great things, but they are also starting to present some real challenges. The potential impact of models on mental health was something we saw a preview of in 2025; we are just now seeing models get so good at computer security they are beginning to find critical vulnerabilities.
We have a strong foundation of measuring growing capabilities, but we are entering a world where we need more nuanced understanding and measurement of how those capabilities could be abused, and how we can limit those downsides both in our products and in the world, in a way that lets us all enjoy the tremendous benefits. These questions are hard and there is little precedent; a lot of ideas that sound good have some real edge cases.
If you want to help the world figure out how to enable cybersecurity defenders with cutting edge capabilities while ensuring attackers can't use them for harm, ideally by making all systems more secure, and similarly for how we release biological capabilities and even gain confidence in the safety of running systems that can self-improve, please consider applying.
This will be a stressful job and you'll jump into the deep end pretty much immediately.
https://t.co/bnFRnDE4O7
Christmas greetings from the Nordic Air Forces ⭐
This year, the 🇸🇪 invited 🇫🇮 and 🇩🇰 to join its Christmas tree flight over all three nations, while 🇳🇴 continued its iconic F-35 Christmas star
A festive salute from the air, and valuable precision-flying training for the crews
@Thomas139778461 Die Frage ist doch in den Kontext nicht ernsthaft gestellt, oder,? Zumal ich der Meinung bin dass genau genug formuliert zu haben. Die ~2% errechnet sich aus den veröffentlichten Zahlen beider Landkreise (kumuliert wie auch einzeln unter 2%)
Dieser und ähnliche Posts machen gerade die Runde, da wird allerdings vergessen die Fakten komplett darzustellen.
Es fehlt zum Beispiel die Tatsache dass bis dato nicht einmal 2% der Flüchtlinge in beiden Landkreisen gegangen mit dieser Begründung gegangen sind...
@ChrisEbner_FM Es ist nicht notwendig eine #festung zu errichten.....mach's wie Thüringen ...Problem erledigt. Kein Geld, keine (Pseudo) Flüchtlinge ⬇️😉
https://t.co/Xbtnchuih1
@BlogerPisarz Es fehlt die Feststellung das hier ca. 2% der Flüchtlinge mit dieser Begründung gingen. >98% blieben, wendet man die kolorierte Logik vieler Kommentatoren konsequent an, sind diese >98% dann "echte" Flüchtlinge!
Und nun?