Andrey Tabunshchik πŸ‡ΊπŸ‡¦ (@UniqueAndrey) header
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ (@UniqueAndrey) profile picture

#toolsforthought Enthusiast | Product man | Entrepreneur πŸ€“ Building #xtilesHQ a #TfT and #Productivity app from #Ukraine πŸ‡ΊπŸ‡¦

Ukraine
Joined August 2021
Photo by Andrey Tabunshchik πŸ‡ΊπŸ‡¦ (@UniqueAndrey)Photo by Andrey Tabunshchik πŸ‡ΊπŸ‡¦ (@UniqueAndrey)Photo by Andrey Tabunshchik πŸ‡ΊπŸ‡¦ (@UniqueAndrey)
Product Hunt is finally done! It was an exciting experience!πŸ˜ŽπŸ˜‡ #1 Product of the Day πŸ₯‡ #1 Product of the Week πŸ₯‡ #2 Product of the Month πŸ₯ˆ So, what did we gain?πŸ€“ βœ” Over 2500 upvotes! βœ” We got over 500 comments! βœ” 70+ paid customers! Thanks to everyone who supported us
We're hosting a small webinar for founders this Wednesday on how to turn Claude + ChatGPT into your own virtual assistant. Kept it close to the network on purpose, so wanted to personally invite you. Grab a spot here: linkedin.com/events/74813610… #claude #cowrok #chatgpt
73
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
This works really well btw, at the end of your query ask your LLM to "structure your response as HTML", then view the generated file in your browser. I've also had some success asking the LLM to present its output as slideshows, etc. More generally, imo audio is the human-preferred input to AIs but vision (images/animations/video) is the preferred output from them. Around a ~third of our brains are a massively parallel processor dedicated to vision, it is the 10-lane superhighway of information into brain. As AI improves, I think we'll see a progression that takes advantage: 1) raw text (hard/effortful to read) 2) markdown (bold, italic, headings, tables, a bit easier on the eyes) <-- current default 3) HTML (still procedural with underlying code, but a lot more flexibility on the graphics, layout, even interactivity) <-- early but forming new good default ...4,5,6,... n) interactive neural videos/simulations Imo the extrapolation (though the technology doesn't exist just yet) ends in some kind of interactive videos generated directly by a diffusion neural net. Many open questions as to how exact/procedural "Software 1.0" artifacts (e.g. interactive simulations) may be woven together with neural artifacts (diffusion grids), but generally something in the direction of the recently viral xitter.cf/zan2434/status/2046982… There are also improvements necessary and pending at the input. Audio nor text nor video alone are not enough, e.g. I feel a need to point/gesture to things on the screen, similar to all the things you would do with a person physically next to you and your computer screen. TLDR The input/output mind meld between humans and AIs is ongoing and there is a lot of work to do and significant progress to be made, way before jumping all the way into neuralink-esque BCIs and all that. For what's worth exploring at the current stage, hot tip try ask for HTML.
1,051
2,034
485
19,419
4,102,003
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
Andrej Karpathy didn't make a course. He made THE course. Free. From the man who co-founded OpenAI and built Tesla Autopilot. Tokenization. Attention. Hallucinations. Tool use. RLHF. DeepSeek. AlphaGo.. Save the video. Watch it this Today & Start Building Ai Agents, Ai automation systems with the knowledge. This has the entire training stack of every modern LLM, explained by the engineer who actually built Open AI and more... More valuable than any $10,000 over priced AI course. Follow @codewithimanshu for breakdowns of every must-watch AI lecture for career upgrade. ↓ Karpathy doesn't teach AI like a YouTube influencer. He teaches it like the guy who built it. Founding member at OpenAI in 2015. Senior Director of AI at Tesla. This is the most comprehensive LLM breakdown ever published on Internet. The gap between engineers who understand this and engineers who don't isn't technical depth. It's the ability to conceive of entirely different things. ↓ Here's the actual content. Pretraining and the internet data layer. Where LLMs actually come from. How the entire internet gets turned into training data. Why some data sources matter more than others. Most "AI experts" can't explain this. Karpathy walks through it in 7 minutes. Tokenization. The single concept that explains why LLMs are bad at math and spelling. Why "strawberry" has 3 R's but ChatGPT used to say 2. Why your prompt costs what it costs. Why some languages are more expensive than others. This is the foundation. Skip it and nothing else makes sense. Follow @codewithimanshu for daily breakdowns of what AI engineers actually need to know. ↓ Neural network internals. What's happening inside the model when you hit "send." Inputs, outputs, the math layer that turns tokens into predictions. Karpathy strips away the abstractions that every other tutorial hides behind. You stop using AI like a magic black box and start using it like a tool you understand. GPT-2 training and inference. The exact same architecture as GPT-5. Just smaller. Once you understand GPT-2, you understand every modern LLM. Karpathy walks through it line by line. Llama 3.1 base model inference. How a real production model actually generates text in real time. This is the 5% of knowledge that separates engineers building AI products from people prompting them. Follow @codewithimanshu for production AI architecture breakdowns weekly. ↓ Pretraining vs post-training. The two phases that determine everything about how a model behaves. Pretraining gives the model knowledge. Post-training gives it personality. Most people don't know the difference. That's why their prompts produce inconsistent results. Post-training conversations. How AI models learn to actually have conversations. The exact data that goes in. Why some models feel "smarter" than others despite similar parameter counts. This explains why Claude feels different from GPT. And how to think about choosing models for production. ↓ Hallucinations, tool use, working memory. The most important section in the entire video. Where hallucinations actually come from. Why models confidently lie. How tool use was engineered to fix it. Every developer building with LLMs needs this section. It explains 90% of the bugs you'll hit in production. Knowledge of self. Why your AI agent doesn't know what model it is. Why it confidently claims to be GPT-4 when it's Claude. The architectural reason this happens and how to handle it. Follow @codewithimanshu for engineering patterns that fix production AI bugs. ↓ Models need tokens to think. The single insight that explains chain-of-thought prompting. Why "think step by step" works. Why some prompts produce 10x better outputs with the same model. The mechanical reason this happens. Once you understand this, you stop guessing prompts and start engineering them. Tokenization revisited. Why models struggle with spelling. Why character-level tasks fail. Why your specific use case might be impossible without a different approach. This is the section that determines whether your AI product ships or breaks. Jagged intelligence. Why models are superhuman at some tasks and terrible at others. The pattern that explains every "AI is so dumb sometimes" moment you've had. ↓ Supervised fine-tuning to reinforcement learning. The shift that made GPT-4 possible. The shift that made Claude great at conversation. How models actually learn from human feedback. Why it works. Where it breaks. Reinforcement learning. The technique behind every reasoning model in 2026. DeepSeek-R1. AlphaGo. The full lineage of how machines learned to think through problems instead of just predicting the next token. Follow @codewithimanshu for RL and reasoning model breakdowns weekly. ↓ DeepSeek-R1 and AlphaGo. The two case studies that explain modern AI reasoning. DeepSeek for language. AlphaGo for game theory. Same underlying principle. Once you understand both, you understand where AI is going next. RLHF. Reinforcement Learning from Human Feedback. The technique that made AI usable for normal humans. Why your favorite model "just feels right." How that feeling was engineered. Why it costs millions of dollars. This is the section that explains the actual cost structure of modern AI products. ↓ Where this puts you after 3 hours. Most engineers using AI know how to prompt it. After this video, you'll understand: > How models are pretrained > How they're fine-tuned > How they handle context > Why they hallucinate > How tool use works > Why some prompts work and others fail > What RLHF does > Where AI is going next That's not "AI literacy." That's architectural understanding. The kind of understanding that turns into $200K+ AI engineering roles. The kind of understanding that lets you build the next ChatGPT instead of just using it. ↓ 3 hours. Free. From the person who built it. You've watched longer Netflix series this week and learned nothing. This compounds for the rest of your career. People who watch it understand AI at the architect level. People who skip it stay confused about why their prompts fail in production. Save the video. Watch it this weekend. Build something with the knowledge by Monday. Follow @codewithimanshu for more high-signal AI content from the people actually building the future.
Anthropic's Claude Code team just teaches how to automate your entire engineering workflow with Claude Code SDK in under 30 minutes. For Free. From the engineers who built it. CANCEL Your Weekend Plans, and Learn to Automate Your Codebase Today. Bookmark it. Watch it. Ship your first headless automation this weekend. $5,000/month. $10,000/month. $25,000/month. People are automating entire engineering teams with Claude Code SDK and charging clients $$$$. You're still copy-pasting code from ChatGPT manually. This video fixes that tonight. Follow @codewithimanshu for more high-signal content that actually moves your AI engineering career forward. ↓ Sid Bidasaria runs engineering on Claude Code at Anthropic. He just gave away the entire SDK + GitHub Action playbook in 30 minutes. This is the talk that separates people automating their entire codebase from people still manually writing every commit. Here's everything inside. Follow @codewithimanshu for weekly Claude automation breakdowns. ↓ What the Claude Code SDK actually is. Most devs don't know this exists. They use Claude in the chat interface and call it a day. The SDK is the real unlock. Programmatic access to the Claude Code agent in headless mode. The primitive building block for every serious automation you'd ever want to build. Designed like a Unix tool. Drops directly into terminal pipelines, bash scripts, CI/CD automation. Use it to review code. Write linters. Build chatbots. Manage remote code environments. Run an entire engineering pipeline. This is how you stop "using AI" and start "shipping with AI." Follow @codewithimanshu for full Claude SDK breakdowns every week. ↓ Basic usage that 99% of devs miss. `claude -p` to prompt the agent directly from your terminal. `--allowed-tools write` for controlled file system access. Pipe anything into it: > Pipe `ifconfig` output β†’ ask Claude to debug your network > Pipe error logs β†’ get a fix before your coffee finishes brewing > Pipe a file β†’ get instant code review without opening an editor `--output-format JSON` for structured responses you can parse in automated systems. This is where Claude stops being a chat tool and becomes infrastructure. Follow @codewithimanshu for daily Claude SDK one-liners that save hours. ↓ Permission management without the security holes. The biggest reason teams don't deploy AI in production: permission concerns. Sid solves it cleanly: > No destructive permissions by default > `--allowed-tools` to pre-configure exactly what the agent can touch > `--permission-prompt-tool` to delegate authorization to an MCP server in real time Your AI agent gets full power exactly when it needs it. Zero access when it doesn't. This is enterprise-grade AI security packaged as a single flag. Most tutorials hand-wave this. This one shows the architecture. Follow @codewithimanshu for production AI permission patterns every week. ↓ Session persistence: the multi-turn unlock. Most AI integrations forget everything between calls. That's why your "AI assistant" feels like talking to someone with amnesia. Return a `session ID` and Claude resumes exactly where you left off. Full context preserved. Multi-turn conversations across hours, days, deploys. This is the foundation for building any real AI product that holds context. Customize the system prompt while you're at it. `--system-prompt 'talk like a pirate'` if you want. Or build a serious agent persona for production. Follow @codewithimanshu for persistent context patterns for AI agents. ↓ The Claude GitHub Action demo that should scare every dev. Sid runs a live demo on a real quiz app: > Files an issue: "add a 50/50 power-up and a skip power-up" > Claude creates a to-do list > Claude modifies the files > Claude opens a Pull Request The entire feature shipped from one issue. No human touching code. This is automated code review, automated bug triage, automated feature implementation. From GitHub issues directly. Junior dev work just got compressed into the time it takes to write an issue description. Follow @codewithimanshu for GitHub Action setups for production. ↓ Zero infrastructure required. Every other AI automation tool needs: > A separate server > A deployment pipeline > Monitoring infrastructure > Auth setup > Cost tracking The Claude GitHub Action uses your existing GitHub Action runners. `claude /install github action` in your local repo. Generates a YAML config. Done. You go from idea to production AI automation in 60 seconds. Most people pay $200/month for tools that do less than this free Action. Follow @codewithimanshu for free Claude Action templates. ↓ The 3-layer architecture nobody explains. Sid breaks down the actual stack: > Layer 1: SDK - the foundation, raw programmatic access > Layer 2: Base Action - wraps the SDK as a clean API interface > Layer 3: PR Action - adds comments, formatting, full GitHub UX Understanding these layers is the difference between someone who copies tutorials and someone who builds custom AI infrastructure for clients. This is the architectural insight that turns into $10K/month consulting contracts. Follow @codewithimanshu for weekly architecture deep dives. ↓ 30 minutes from the engineer shipping this in production. You'll learn more from this than from 6 months of YouTube tutorials made by people who've never automated a single deploy. People who watch this understand Claude Code automation at the infrastructure level. People who skip it keep manually reviewing PRs, manually filing issues, manually doing work that could've been automated last weekend. Save the video. Watch it tonight. Ship your first Claude SDK automation this weekend. Follow @codewithimanshu for more high-signal content that actually moves your AI engineering career forward.
38
66
1
348
68,652
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
L’équipe d’Anthropic vient de montrer comment utiliser correctement Claude Code. 30 minutes. gratuit. prΓ©sentΓ© par la personne qui a créé Claude Code. Regarde le workshop. Ajoute en signet πŸ”– Γ‡a vaut plus que tous les cours Γ  500$ que t’as failli acheter.
832
1,774
79
14,784
4,124,949
Who started using Atlas? ChatGPT. How to mention another tab in chat. #ChatGPT #atlas
18
Getting inside your target’s head is the most crucial part of copywriting. Here's how to learn everything there is to know about your target: And then turn it into high-converting copy. πŸ‘‡πŸ‘‡πŸ‘‡
12
18
1
119
40,270
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
4
10
593
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
5 most famous laws that shape our world: (Repost ♻️ if you enjoyed reading the hyper-visual)
8
513
4
2,209
485,662
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
Do you know @xTilesHQ? It's a cool and simple tool that helps you organize tasks, notes, and everything all in one place.
4
7
373
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
finally finished making the first page of my xtiles board
3
1
15
497
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
gonna explore this awesome tool @xTilesHQ this long weekend
2
3
410
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
As you say goodbye to 2023, use these 5 journaling prompts to practice the art of letting go: β€’ Why do I care about this item? β€’ Why do I care about this goal? β€’ Why do I care about this rule? β€’ Why do I care about this relationship? β€’ Why do I care about this memory?
2
9
1
75
8,362
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
What's in your productivity stack? 🀩 πŸ’ͺ🏼
33
8
4
68
27,415
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
Have you ever spent too much time designing a productive workspace instead of focusing on actual work? Read our interview with @kuchur_maksym about @xTilesHQ, the all-in-one workspace for notes, tasks & projects to manage your knowledge as you see fit πŸ‘‡ nesslabs.com/xtiles-featured…
3
11
1,316
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
πŸ“ MUST-HAVE APPS FOR STUDENTS If you're a student, or someone who wants to be productive, using these apps can help you to function throughout the dayπŸ˜‰ They will boost your productivity, gives you stimulation for a better mental state, and many more!
1
78
2
435
32,819
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
β€”β˜… xTiles β€” @xTilesHQ | s.id/xtilesinas/
1
2
10
2,318
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
Love these cultural context things. The πŸ‡¬πŸ‡§ do it the best… πŸ˜‚
44
144
27
1,230
376,353
Andrey Tabunshchik πŸ‡ΊπŸ‡¦ retweeted
I was asked by @xTilesHQ to share my experience with Notion, because they are building Ukrainian upgraded version of it. We figured out that Notion is mostly used for storage rather than operating platform.
1
2
4
336