Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

hunk v0.21.0 is out - it's a big one: - 💬 threaded + editable notes - 🌲 file tree view + better responsive layouts - 🔍 more git/jj diff operands - ⚙️ extension APIs: dimmable code blocks, CLI subcommands, & more event hooks - 🎨 color fixes for 25 themes

bentlegen's profile picture

Ben Vinegar

14,350 subscribers

34,264 görüntüleme • 1 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

24 Yorum

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

🙏 contributions from @SamuelAinsworth, nightcityblade, masonmcelvain, ajay-satish-01, yuki9814, and marmintar on GitHub ⬇️ full release notes

Paul Thomson profil fotoğrafı
Paul Thomson1 ay önce

God damn it.. Making it like Sophie's choice between this and plannotator now

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

Maybe there’s room for both? Our goal is “best git diff replacement”

Paul Thomson profil fotoğrafı
Paul Thomson1 ay önce

I mean I do use both.. But Plannotator also has a diff view.. And I like to treat my tools like Zuckerberg did/does with choosing his outfits :P

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

I understand it has a diff view, and that’s cool I was speaking more, philosophically, what the aims of the project are and what we focus on (hopefully not a stretch to say Plannotator’s focus is planning)

Paul Thomson profil fotoğrafı
Paul Thomson1 ay önce

Oh I know.. But do you ever get to the point where you kinda just want one "canonical" choice to do something? Like sometimes I was glad when Apple/iOS added something to iOS that there used to be a bunch of 3rd party apps for, cos it eliminated the overhead of me having to choose. It's like Herdr and tmux, I _need_ a clear winner or reason to use one over the other :P This might be a) I'm not using either to their full extent or b) some latent OCD on my part; but something about having a single tool over multiple appeals to me and right now (just for diff viewing) there's no clear better choice, or better enough that I'm using one or the other. And that is to say they're both awesome, hence I've got both installed and use both.. But anyway, I'm still not sure if I'm even _meant_ to be looking at the diff/code currently? I think you're supposed to % 2 the day of the week to decide the current wisdom? :P

Ryan Seddon profil fotoğrafı
Ryan Seddon1 ay önce

Brew not the way to install? Tried to upgrade but its telling me 0.17.0 is the latest version?

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

Uninstall what you have, it’s just “brew install hunk” now

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

But thanks for sharing this, maybe I should update the old tap all the same

Ryan Seddon profil fotoğrafı
Ryan Seddon1 ay önce

No worries, uninstalled and installed and now all good!

Ryan Seddon profil fotoğrafı
Ryan Seddon1 ay önce

oof I use hunk as the pager in lazygit and it absolutely pegged my cpu cores

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

Ouch, someone else reported this but gave no other info so I came up empty trying to fix it Could you open an issue with any extra detail? Cli args, what the diff content was (if you can) … or have an agent poke at it

Ryan Seddon profil fotoğrafı
Ryan Seddon1 ay önce

Done, needs to be a repo with a few thousand commits

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

Thank you 🙏

MARUF profil fotoğrafı
MARUF1 ay önce

support for jj diff operands makes code review so fast

jom_donut.gif profil fotoğrafı
jom_donut.gif1 ay önce

Congrats, looks like a great release. The startup speed sadly still kills it for me, it's extremely noticeable on every open on my device.

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

If you could give me more info maybe I can address? Like, how slow are we talking here? 300ms? 3s? More? Could it be something about your folder/project (eg number of files)? If you had a coding agent debug I bet we could fix

Jarno profil fotoğrafı
Jarno1 ay önce

Shipping fast and eating your own dogfood, respect.

matthew profil fotoğrafı
matthew1 ay önce

oh my god threaded notes are a life changer

ゆうき＠カッコよくて売れるデザイン profil fotoğrafı
ゆうき＠カッコよくて売れるデザイン1 ay önce

ファーストビューが命！ hunkのレスポンス改善は UIの「見た目が良い」だけでなく 情報整理をしやすい構造を作る USPと言える要素ですね。 LPでいうとファイルツリーは ユーザーを迷わせない視線誘導そのもの。

janz profil fotoğrafı
janz1 ay önce

hey @bentlegen! is it possible for my Claude to reply to my notes in a thread?

Mikkel Malmberg profil fotoğrafı
Mikkel Malmberg1 ay önce

incredible you've come so far and still haven't added a zenbones theme

Sebastian Buzdugan profil fotoğrafı
Sebastian Buzdugan1 ay önce

editable notes need revision history or review context becomes unreliable after merges

Ben Vinegar profil fotoğrafı
Ben Vinegar1 ay önce

v0.21.1 has an important fix for lazygit users

Benzer Videolar

Andrej Karpathy posted about the new programmable layer developers need to master: agents, subagents, prompts, contexts, memory, hooks, MCP. He said it came with no manual and everyone has to figure out how to hold it. This video is part of that manual. Hooks are one of the most underused features in Cursor and Droid, and they're what separate intentional AI-assisted development from hoping it works in production. After file edit: If the agent touches Rust code, hooks automatically regenerate TypeScript types for the frontend. If it touches TypeScript, ESLint runs with autofix. If it touches backend code, cargo clippy runs. On stop: When the agent finishes, it runs cargo check to validate the build before I even look at the output. 00:00 The problem: manually verifying AI-written code 00:31 Introducing hooks to automate tasks when files change 01:53 How hooks regenerate types for the frontend 02:24 How to set up the cursor.hooks.json file 04:44 Reviewing a more comprehensive hooks plan 05:48 Comparing FactoryDroid hooks vs Cursor hooks 06:45 Implementing the equivalent hooks in FactoryDroid 07:50 AI agent fixes a bug in the build command 08:27 How scaffolding makes the AI agent appear smarter 09:08 Demonstrating the successful hook implementation 09:53 Final insight: It's about providing guardrails, not a smarter AI
10:20

Andrej Karpathy posted about the new programmable layer developers need to master: agents, subagents, prompts, contexts, memory, hooks, MCP. He said it came with no manual and everyone has to figure out how to hold it. This video is part of that manual. Hooks are one of the most underused features in Cursor and Droid, and they're what separate intentional AI-assisted development from hoping it works in production. After file edit: If the agent touches Rust code, hooks automatically regenerate TypeScript types for the frontend. If it touches TypeScript, ESLint runs with autofix. If it touches backend code, cargo clippy runs. On stop: When the agent finishes, it runs cargo check to validate the build before I even look at the output. 00:00 The problem: manually verifying AI-written code 00:31 Introducing hooks to automate tasks when files change 01:53 How hooks regenerate types for the frontend 02:24 How to set up the cursor.hooks.json file 04:44 Reviewing a more comprehensive hooks plan 05:48 Comparing FactoryDroid hooks vs Cursor hooks 06:45 Implementing the equivalent hooks in FactoryDroid 07:50 AI agent fixes a bug in the build command 08:27 How scaffolding makes the AI agent appear smarter 09:08 Demonstrating the successful hook implementation 09:53 Final insight: It's about providing guardrails, not a smarter AI

Ray Fernando

60,928 görüntüleme • 9 ay önce

Cursor vs Claude Code (day 3 of 30) today I re-tested Conductor and I don't want to overhype this but... what the actual fook 😮 this thing is amazing! closest things to the "perfect workflow" I have seen in a long time, and it's something I could see myself use full-time it's so minimal and the polar opposite of Cursor but it has all the essentials → Claude Code + Codex subscriptions (= unlimited usage) → great integration with Claude Code's plan mode → multiple tabs with multiple agents at the same time → can use multiple models, not just one → great file tree and diff viewer → best git worktree support I've ever seen there's honestly so much more, like a dedicated "review" button (which you can pair to your favorite review model, e.g. gpt-5.2-extra-high), buttons to create and merge pull requests, to launch your dev server, ... this solves literally EVERY fault I can think of when using Claude Code and/or Codex, combining both into one easy UX that not only does everything the tools can do, but actually adds useful stuff on top just 6 months ago I couldn't have dreamt about any this and the wildest part is that IT IS FREE (I'd literally pay for this UX lol) first time I'm genuinely enjoying myself since starting this challenge not saying it's a full Cursor replacement yet, it obviously isn't for a lot of people (no browser, no debug mode, no code indexing, etc) ... but this is the closest thing I've seen yet 👀 follow for day 4!
5:56

Cursor vs Claude Code (day 3 of 30) today I re-tested Conductor and I don't want to overhype this but... what the actual fook 😮 this thing is amazing! closest things to the "perfect workflow" I have seen in a long time, and it's something I could see myself use full-time it's so minimal and the polar opposite of Cursor but it has all the essentials → Claude Code + Codex subscriptions (= unlimited usage) → great integration with Claude Code's plan mode → multiple tabs with multiple agents at the same time → can use multiple models, not just one → great file tree and diff viewer → best git worktree support I've ever seen there's honestly so much more, like a dedicated "review" button (which you can pair to your favorite review model, e.g. gpt-5.2-extra-high), buttons to create and merge pull requests, to launch your dev server, ... this solves literally EVERY fault I can think of when using Claude Code and/or Codex, combining both into one easy UX that not only does everything the tools can do, but actually adds useful stuff on top just 6 months ago I couldn't have dreamt about any this and the wildest part is that IT IS FREE (I'd literally pay for this UX lol) first time I'm genuinely enjoying myself since starting this challenge not saying it's a full Cursor replacement yet, it obviously isn't for a lot of people (no browser, no debug mode, no code indexing, etc) ... but this is the closest thing I've seen yet 👀 follow for day 4!

Robin Ebers

40,764 görüntüleme • 9 ay önce

THIS IS A PURE F*CKING GOLDMINE Anthropic just shared the sharpest trick for Claude Code The idea: let Opus 5.5 write the plan as a script, and swarm the new Haiku 5.5 in parallel Huge sweeps with zero Opus burn: the script holds the loop and Opus only sees the final diff You just launch Claude Code like this: claude --model opus --effort ultracode here's the split: → Opus 5.5 turns your objective into an executable workflow script → Haiku 5.5 swarms every file in parallel at 340 tok/s to extract candidates → Sonnet 5.5 patches each fix and cross-checks findings in its own isolated copy → you stop burning Opus context on a hundred agent transcripts Opus only shows up at three moments: → authoring the workflow script before the run → reading verified findings after the swarm finishes → signing off before anything ships to git Opus plans · Haiku scans · Sonnet ships JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split the full tree > Opus 5.5 runs the main session and writes workflow.js > pipeline() fans out the new Haiku 5.5 to audit every file > parallel() schema validators drop false positives in V8 > Sonnet 5.5 patches each fix in an isolated worktree > verify cross-checks all diffs before reporting > Opus 5.5 reads only what survived verification > JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Run the main session on Opus 5.5 with ultracode on 2. In every workflow, run read-only scan stages on the new Haiku 5.5 and edit stages on Sonnet 5.5, each edit in its own isolated copy 3. Add one rule to CLAUDE.md: every finding gets an independent verifier agent before it's reported, and fix loops stop after two rounds with no progress 4. Route fast deterministic forks (tool choice, path selection, retries) through JEV Show me every change as a diff first, no edits until I say go" ↳ save it, it'll come in handy
0:24

THIS IS A PURE F*CKING GOLDMINE Anthropic just shared the sharpest trick for Claude Code The idea: let Opus 5.5 write the plan as a script, and swarm the new Haiku 5.5 in parallel Huge sweeps with zero Opus burn: the script holds the loop and Opus only sees the final diff You just launch Claude Code like this: claude --model opus --effort ultracode here's the split: → Opus 5.5 turns your objective into an executable workflow script → Haiku 5.5 swarms every file in parallel at 340 tok/s to extract candidates → Sonnet 5.5 patches each fix and cross-checks findings in its own isolated copy → you stop burning Opus context on a hundred agent transcripts Opus only shows up at three moments: → authoring the workflow script before the run → reading verified findings after the swarm finishes → signing off before anything ships to git Opus plans · Haiku scans · Sonnet ships JEV engineering is the same move one layer down: the forks that need no thinker (which file, which tool, retry or stop) go to JEV in milliseconds, and the big models only see the ones that split the full tree > Opus 5.5 runs the main session and writes workflow.js > pipeline() fans out the new Haiku 5.5 to audit every file > parallel() schema validators drop false positives in V8 > Sonnet 5.5 patches each fix in an isolated worktree > verify cross-checks all diffs before reporting > Opus 5.5 reads only what survived verification > JEV routes micro-forks in milliseconds paste the tree and this prompt into Claude Code ↓ "Rebuild my Claude Code setup around this tree: 1. Run the main session on Opus 5.5 with ultracode on 2. In every workflow, run read-only scan stages on the new Haiku 5.5 and edit stages on Sonnet 5.5, each edit in its own isolated copy 3. Add one rule to CLAUDE.md: every finding gets an independent verifier agent before it's reported, and fix loops stop after two rounds with no progress 4. Route fast deterministic forks (tool choice, path selection, retries) through JEV Show me every change as a diff first, no edits until I say go" ↳ save it, it'll come in handy

mirku

189,153 görüntüleme • 2 gün önce

It's fluffy to the touch... This isn't a dream! Trailer of New 5-Star Memory Series [Yes, Cat Caretaker] Released! 💫Follow Love and Deepspace and Repost for a chance to win $50 (5 winners)! 🐈After the update on Nov. 12 to 4:59 AM on Nov. 30, You can select three out of the four event-limited 5-Star Memories [Xavier: Floof Attack], [Zayne: Fluffy Treatment], [Rafayel: Tailwag Moment], and [Sylus: Goodcat Code]. The drop rate of the three Memories you selected will be significantly increased. Each time you obtain a 5-Star Memory, there's a 75% chance it will be one of the three Memories you selected. Notes: 1. During the event, you can change your selected Memories at any time. Each time you obtain a 5-Star Memory, the chance of obtaining the unselected event-limited Memory and other permanent 5-Star Memories will be 25%. 2. After the event ends, the four event-limited Memories will not be obtainable through other means and will not enter the permanent Wish Pool, Xspace Echo. 3. Apart from the selection system, the wish event features Precise Wish and a pity system. For more details, please check the in-game rule page. 🐈Cumulative Wish Rewards During the event, after you make a certain number of Wishes in this Limited 5-Star Wish Pool, you can claim various rewards, including Universal Headwear: Attendant Hairband, [Deepspace Wish: Limited*15], His [Cat Butler Outfits], and one selectable Event-Limited 5-Star Memory. *The cumulative rewards are only available during this wish event. 🐈Limited-Time Memory Growth Bonus During the event, you can claim various Upgrade and Ascension Materials by completing the growth tasks. When the event-limited Memories reach Rank 1, you can claim the [special-color Cat Butler Outfit] for the corresponding love interest. 🐈Special Upgrade of Memory-Themed Outfit Bonus 1. During the event, each Outfit Set includes Outfit, Headwear, and Tail. 2. Outfit, Headwear, and Tail can all be used separately. 3. The Headwear and Tail can be worn by both the corresponding love interest and "Me"! *More contents will be released with the version update. Please stay tuned! #LoveandDeepspace
2:54

It's fluffy to the touch... This isn't a dream! Trailer of New 5-Star Memory Series [Yes, Cat Caretaker] Released! 💫Follow Love and Deepspace and Repost for a chance to win $50 (5 winners)! 🐈After the update on Nov. 12 to 4:59 AM on Nov. 30, You can select three out of the four event-limited 5-Star Memories [Xavier: Floof Attack], [Zayne: Fluffy Treatment], [Rafayel: Tailwag Moment], and [Sylus: Goodcat Code]. The drop rate of the three Memories you selected will be significantly increased. Each time you obtain a 5-Star Memory, there's a 75% chance it will be one of the three Memories you selected. Notes: 1. During the event, you can change your selected Memories at any time. Each time you obtain a 5-Star Memory, the chance of obtaining the unselected event-limited Memory and other permanent 5-Star Memories will be 25%. 2. After the event ends, the four event-limited Memories will not be obtainable through other means and will not enter the permanent Wish Pool, Xspace Echo. 3. Apart from the selection system, the wish event features Precise Wish and a pity system. For more details, please check the in-game rule page. 🐈Cumulative Wish Rewards During the event, after you make a certain number of Wishes in this Limited 5-Star Wish Pool, you can claim various rewards, including Universal Headwear: Attendant Hairband, [Deepspace Wish: Limited*15], His [Cat Butler Outfits], and one selectable Event-Limited 5-Star Memory. *The cumulative rewards are only available during this wish event. 🐈Limited-Time Memory Growth Bonus During the event, you can claim various Upgrade and Ascension Materials by completing the growth tasks. When the event-limited Memories reach Rank 1, you can claim the [special-color Cat Butler Outfit] for the corresponding love interest. 🐈Special Upgrade of Memory-Themed Outfit Bonus 1. During the event, each Outfit Set includes Outfit, Headwear, and Tail. 2. Outfit, Headwear, and Tail can all be used separately. 3. The Headwear and Tail can be worn by both the corresponding love interest and "Me"! *More contents will be released with the version update. Please stay tuned! #LoveandDeepspace

Love and Deepspace

2,683,017 görüntüleme • 1 yıl önce

How I turn my templates into real landing pages. Works for any vibe coding platform or site. This is my full guide. I start with Gemini 3. I copy the HTML code and paste to Cursor/v0/lovable and prompt "Create a new landing page /page-name using this design but adapted to {site_name}. Replace the header and footer with the ones from my site. Adapt the whole page, keep everything: {HTML_code}" Details that can to be adapted or improved: Fonts: "Use {font_name} Google font for headings and {font_name} for body text." Icons: "Use Iconify {icon_set} icons" Colors: "Change primary color to blue. Everything else should be monotone." Bonus: "Make the outlines subtle" for a cleaner design. Animation intro/on scroll: "Animate when in view observed, fade in, slide in, blur in, element by element. Use 'both' instead of 'forwards'. Don't use opacity 0." Static to animated: "Animate details with {animate_type} and decorations.". Example types: line, beam animation, noodles, grid, sonar, etc. Background animation: "Apply the background animation using Unicorn Studio {animation_code}" Details to make your layout stand out: "Add vertical container-size lines. Add 01 02 03 number details." Stand out from generic-looking: "Make this more upscale with large tall fonts, Newsreader font and black and white agency". Adapt content: "Adapt the content to {copy and paste site texts}". Buttons: "Change main button to {code}. Add a 1px border beam animation around the pill-shaped button on hover." Adding sections like testimonials: "Adapt a new section after {section} using this code: {component code}". You can copy the code from Codepen, 21st dev or Aura. Responsiveness: "Make this responsive. Add a hamburger menu for mobile. Hide this {element} for mobile." Making forms work: "Make the form send an email to {your_email}". Payments: "Link the buy button to {LemonSqueezy payment link}". I use composer-1 for quick fixes. I finish with Claude Opus 4.5 for code reviews "Please review the code for performance and robustness". The template HTML code should give you a blueprint for all these, but I think it's important to keep iterating for your specific site.
0:46

How I turn my templates into real landing pages. Works for any vibe coding platform or site. This is my full guide. I start with Gemini 3. I copy the HTML code and paste to Cursor/v0/lovable and prompt "Create a new landing page /page-name using this design but adapted to {site_name}. Replace the header and footer with the ones from my site. Adapt the whole page, keep everything: {HTML_code}" Details that can to be adapted or improved: Fonts: "Use {font_name} Google font for headings and {font_name} for body text." Icons: "Use Iconify {icon_set} icons" Colors: "Change primary color to blue. Everything else should be monotone." Bonus: "Make the outlines subtle" for a cleaner design. Animation intro/on scroll: "Animate when in view observed, fade in, slide in, blur in, element by element. Use 'both' instead of 'forwards'. Don't use opacity 0." Static to animated: "Animate details with {animate_type} and decorations.". Example types: line, beam animation, noodles, grid, sonar, etc. Background animation: "Apply the background animation using Unicorn Studio {animation_code}" Details to make your layout stand out: "Add vertical container-size lines. Add 01 02 03 number details." Stand out from generic-looking: "Make this more upscale with large tall fonts, Newsreader font and black and white agency". Adapt content: "Adapt the content to {copy and paste site texts}". Buttons: "Change main button to {code}. Add a 1px border beam animation around the pill-shaped button on hover." Adding sections like testimonials: "Adapt a new section after {section} using this code: {component code}". You can copy the code from Codepen, 21st dev or Aura. Responsiveness: "Make this responsive. Add a hamburger menu for mobile. Hide this {element} for mobile." Making forms work: "Make the form send an email to {your_email}". Payments: "Link the buy button to {LemonSqueezy payment link}". I use composer-1 for quick fixes. I finish with Claude Opus 4.5 for code reviews "Please review the code for performance and robustness". The template HTML code should give you a blueprint for all these, but I think it's important to keep iterating for your specific site.

Meng To

41,015 görüntüleme • 10 ay önce

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, & Learn Claude Code Today. This Claude Code teaches more about vibe-coding in 30 mins than most tutorials do in hours. Save this, it'll change how you build forever People are building entire apps and charging clients $5,000 to $20,000 using Claude Code. This Claude Code video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumarfor daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

85,668 görüntüleme • 5 ay önce

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.
35:48

CANCEL Your Weekend Plans, and Learn Claude Code Today. $5,000/month. $10,000/month. $20,000/month. People are building entire apps and charging clients thousands using Claude Code. You're still Googling 'how to center a div.' While you're binge-watching a show you won't remember next week, a 19 year old with zero coding experience just built a $5,000 SaaS product in one afternoon using the tool I'm about to break down. Same laptop. Same internet. Same 24 hours. He has Claude Code. You have Netflix. That's the only difference. This YouTube video is a goldmine. Full Claude Code tutorial. Beginner to pro. Every feature. Every setup step. Every best practice. Zero prior knowledge needed. Save it. Watch it tonight. Not tomorrow. Tonight. Save this post. This is your complete Claude Code roadmap. Lose it and you lose the next 12 months of income. Follow Himanshu Kumar so you don't miss the breakdowns for each feature. ↓ 1. Understand What Claude Code Actually Is. You think Claude Code is just another chatbot. It's not. And that misunderstanding is why you're broke. ChatGPT gives you text. Claude Code gives you software. It runs in your terminal. It reads your entire codebase. It writes files directly to your project. It runs commands on your machine. It debugs errors autonomously. It builds features end to end. You're not chatting. You're deploying a developer. One that works 24/7. Never asks for a raise. Never calls in sick. Never pushes broken code at 5 PM on a Friday. People are charging clients $5,000-$10,000 for apps they built with Claude Code in 3 hours. And you didn't even know this tool existed because you're still asking ChatGPT to write you a to-do list. The gap between you and people making money with AI isn't intelligence. It's awareness. Now you're aware. Save this post. Follow Himanshu Kumar for the complete breakdown of every Claude Code feature. ↓ 2. Set Up Claude Code Properly. Most people quit here. "It's too complicated." "I don't know terminal." "I'll set it up later." Later never comes. And "complicated" means "I watched for 30 seconds and gave up." The setup takes 10 minutes. Install Node.js. Install Claude Code via npm. Authenticate your account. Open your terminal. Done. 10 minutes. You spent longer this morning deciding what to have for breakfast. The video walks through every single click. Every command. Every screen. Assuming you know absolutely nothing. If you can download an app on your phone, you can set up Claude Code. It's the same level of difficulty. But you'll still tell yourself it's "too technical" because that excuse is more comfortable than admitting you're just scared to try something new. This is the setup that everything else builds on. Skip it and nothing works. ↓ 3. Use the Desktop App. You don't even need to live in the terminal if you don't want to. Claude Code has a desktop app. Clean interface. Visual feedback. Everything you need without touching command line. But here's the thing most people don't know: The desktop app isn't just a pretty wrapper. It lets you manage projects visually. See file changes in real time. Switch between projects instantly. The people making money with Claude Code use the desktop app for client projects because it's faster to manage multiple builds simultaneously. You're still opening 14 browser tabs to organize one project. They open one app and everything's there. Efficiency isn't a personality trait. It's a tool choice. Save this post. Follow Himanshu Kumar for the desktop app workflow that handles 5 client projects at once. ↓ 4. Install the Right Dependencies. This is where beginners silently fail and blame the tool. Claude Code needs certain dependencies installed to work properly. Miss one and everything breaks. Then you go on Twitter and say "Claude Code doesn't work." It works fine. You just didn't read the setup guide. The video covers every dependency you need. What to install. How to install it. How to verify it's working. No guessing. No Stack Overflow rabbit holes at midnight. No "why isn't this working" for 3 hours. Watch the dependency section once. Follow every step. Never deal with setup issues again. You spent more time last week troubleshooting a printer than this takes. ↓ 5. Work Inside Your Code Editor. Claude Code integrates directly with your code editor. VS Code. Cursor. Whatever you use. It's not a separate window you alt-tab between. It's right there. In your workflow. You type a request. Claude writes the code. The code appears in your editor. You review it. Accept it. Done. No copy pasting between windows. No reformatting code that got mangled in transit. No "which version was the right one." It's like pair programming with someone who never gets distracted, never argues about naming conventions, and actually writes code that works on the first try. Your current coding process is: Google the problem, read 5 answers on Stack Overflow, copy the wrong one, debug for an hour, find the right one, paste it in, break something else, repeat. Claude Code's process is: describe what you want, get working code, move on with your life. Same hour. One method produces working software. The other produces frustration and a browser history full of Stack Overflow tabs. Stop coding the hard way. Save this post. Follow Himanshu Kumar for code editor setup guides and integration tips. ↓ 6. Master Basic Usage. Most people learn 5% of a tool and say they "know" it. You "know" Photoshop because you can crop an image. You "know" Excel because you can sum a column. You "know" Claude Code because you asked it one question. Basic usage means: How to give Claude Code context about your project. How to ask for changes to existing code. How to generate new files and features. How to review what Claude produces. How to iterate when the output isn't perfect. These basics are the foundation of everything. Skip them and every advanced feature feels confusing. Master them and every advanced feature feels obvious. The video breaks down each one with real examples. Not theory. Actual usage on actual projects. You've been using AI tools at 5% capacity and wondering why your results are 5% of what others get. Save this post. Follow Himanshu Kumar for daily Claude Code usage tips. ↓ 7. Learn Every Command. Claude Code has commands that most users never discover. Because most users type one message and expect magic. That's not how professionals use it. Professionals use specific commands that tell Claude Code exactly what to do, how to do it, and what constraints to follow. The difference between a beginner and someone making $10K/month with Claude Code is knowing which command to use and when. The video walks through every single one. Not just what they do. But when to use each one. And why one command is better than another for specific situations. You've been using Claude Code like a hammer. These commands turn it into a full toolbox. Stop treating a power tool like a blunt instrument. Save this post. Follow Himanshu Kumar for the command cheat sheet I use daily. ↓ 8. Understand Modes and Shortcuts. Speed matters. The person who builds an app in 2 hours charges $5,000. The person who builds the same app in 2 days charges $2,000. Same app. Same quality. Different speed. Different income. Claude Code has modes that change how it operates. And shortcuts that cut your workflow time in half. Most people don't know either exists. They use Claude Code in default mode for everything. Like driving a car in first gear on the highway. Technically it works. But everyone is passing you. The video shows you every mode. Every shortcut. Every time-saving trick that separates the people charging $2,000 per project from the people charging $10,000. Speed is money. Literally. Save this post. Follow Himanshu Kumar for the shortcuts that cut my build time by 60%. ↓ 9. Write a Proper Planning Prompt. This is the section that separates amateurs from professionals. And it's the section most people skip. A planning prompt tells Claude Code what you're building before you start building it. Architecture. File structure. Technologies. Features. Constraints. Edge cases. Without a planning prompt, Claude Code guesses. And guessing produces garbage. With a planning prompt, Claude Code executes a clear plan. And clear plans produce working software. The video shows you exactly how to write a planning prompt that makes Claude Code produce professional-grade output on the first try. "But I just want to start coding." That's why your code breaks every time. That's why you restart projects 4 times. That's why nothing you build ever gets finished. Because you refuse to plan. A 5-minute planning prompt saves you 5 hours of debugging. But you'd rather skip the 5 minutes and suffer through the 5 hours because patience isn't your thing. And that's exactly why you're not making money. Planning is the most underpaid skill in coding. And the most overpaid when you master it. Save this post. Follow Himanshu Kumar for the planning prompt templates I use for every client project. ↓ 10. Choose the Right Model. Claude Code lets you select different AI models. Not all models are the same. Not all tasks need the same model. Using the most powerful model for a simple task wastes credits. Using a basic model for a complex task wastes time. The video explains: Which model to use for quick fixes. Which model to use for complex architecture. Which model to use for debugging. Which model to use for code generation. Most people pick one model and use it for everything. That's like using a sledgehammer to hang a picture frame. Model selection is strategy. And strategy is money. The people making $10K/month with Claude Code are strategic about every credit they spend. You're burning through credits because you use the most expensive model to write a hello world. ↓ 11. Use Git and Version Control. If you're not using version control, you're one mistake away from losing everything. Claude Code integrates with Git. Every change tracked. Every version saved. Every mistake reversible. Without Git: Claude makes a change. It breaks something. You can't undo it. You start over. 3 hours wasted. With Git: Claude makes a change. It breaks something. You roll back in 5 seconds. Keep working. Version control isn't optional. It's insurance. And the people not using it are the same people who say "I lost my entire project" like it's something that just happens. It doesn't just happen. It happens because you didn't set up Git. The video walks through the entire Git integration. Save this post. Follow Himanshu Kumar for the Git workflow that's saved every project I've ever built. ↓ 12. Set Up Claude.MD and Memory. This is the feature that makes Claude Code feel like a real team member instead of a stranger you explain everything to every time. ClaudeMD is a memory file. You tell Claude Code about your project once. It remembers forever. Coding style preferences. Project architecture decisions. Technology stack. File naming conventions. Business logic rules. Without ClaudeMD: Every new conversation starts from zero. You explain the same things repeatedly. Output is inconsistent. With ClaudeMD: Claude knows your project. Claude follows your rules. Claude produces consistent, professional code. The difference between a sloppy freelancer and a reliable agency is consistency. Claude. MD gives you consistency without the agency overhead. Most people don't set this up and wonder why Claude Code gives different answers every time. ↓ 13. Automate with Tasks. This is where Claude Code stops being a tool and starts being an employee. Tasks let you define repeating workflows. "Every time I push code, run tests." "Every time I create a new file, add boilerplate." "Every time I start a session, check for errors." Automated. Hands-free. Consistent. You're doing these things manually every single day. The same checks. The same steps. The same routine. Tasks do them automatically. So you can focus on the work that actually makes money. Every manual task you automate is time you get back. And time is the only thing you can never make more of. Save this post. Follow Himanshu Kumar for the task automation templates that run my entire workflow. ↓ 14. Explore Features Most People Never Touch. The video covers features that 95% of Claude Code users don't know exist. Because they watched a 3-minute TikTok about Claude Code and think they're experts now. They're not. They're using 5% of a tool that can do everything. The full tutorial goes deep into features that most tutorials skip because they're "too advanced." They're not too advanced. They're too valuable for lazy creators to bother explaining. This video explains all of them. Clearly. For beginners. The 5% of features you don't know about are the 5% that make people rich. ↓ Let's zoom out. I just broke down 14 sections of Claude Code. Setup and installation. Desktop app. Dependencies. Code editor integration. Basic usage. Commands. Modes and shortcuts. Planning prompts. Model selection. Git and version control. Memory and Claude. MD. Tasks and automation. Advanced features. All in one video. All free. All beginner friendly. The person who masters even half of these in the next 2 weeks will be in the top 1% of Claude Code users. The top 1% of Claude Code users are the ones charging $5,000-$10,000 per project and building them in a single afternoon. Everyone else is asking ChatGPT to fix their resume. Same tools. Same access. Completely different outcomes. Because one person treats AI like a toy. And the other treats it like a business. ↓ Here's the hard truth nobody wants to hear. You don't have a talent problem. You don't have an intelligence problem. You don't have a resources problem. You have an action problem. Everything I just listed has a free tutorial right here in the attached video. 33 minutes. That's it. 33 minutes to learn the tool that people are using to build $5,000-$20,000/month businesses. You spent more time today scrolling Twitter than it takes to watch this video. You spent more time this week watching Netflix than it takes to master Claude Code basics. You spent more time this month doing nothing than it would take to completely change your income. The information is free. The tool is accessible. The opportunity is here. The only thing missing is you caring enough to start. ↓ CANCEL your plans this week. This isn't optional anymore. The people learning Claude Code right now will be building apps for the people who didn't learn it. That's not a prediction. That's already happening. Companies are replacing $150/hour developers with one person and Claude Code. If you code: learn Claude Code or become half as valuable by next year. If you don't code: learn Claude Code or miss the biggest opportunity to start earning from tech without a CS degree. There's no path forward that doesn't include AI coding tools. None. You have one window. Right now. This week. ↓ Here's your action plan for the next 7 days: Day 1: Watch the full video. Install Claude Code. Set up dependencies. Day 2: Learn basic usage. Try 5 different commands. Day 3: Write your first planning prompt. Build a small project. Day 4: Set up Claude. MD. Configure your memory file. Day 5: Master modes and shortcuts. Build a second project faster. Day 6: Set up Git integration. Automate with tasks. Day 7: Build something real. A tool, an app, a website. Ship it. 7 days. One tool. One completely different skill set. One completely different income potential. Or 7 more days of scrolling Twitter watching other people build things while you "plan to start." Your call. ↓ This is the most important video you'll watch this year. 33 minutes. Complete Claude Code mastery. From zero to building real projects. Save this post. Come back to it every single day this week. Check off each section as you complete it. Follow Himanshu Kumar for daily Claude Code breakdowns, advanced tutorials, and the exact workflows that are turning beginners into $10K/month builders. The only thing between you and $10K/month with Claude Code is this video and 7 days. Don't waste them. You Must Follow me Himanshu Kumar, so i can send you DM.

Himanshu Kumar

101,793 görüntüleme • 6 ay önce

Just created a PR from a github issue via a serverless background agent, and it's entirely open-source at humanlayer we have been thinking a lot about what good open-source software factory building blocks look like to push on this I built something I've wanted for a long time: a hands-outside-the-box approach of running a lightweight agent in a runtime with a virtual fs, and only using a container when necessary - faster, cheaper, etc combined with really good webhook / event bindings for GitHub, slack, and linear we built two components for it: 1. - effect-native webhook subscriptions for slack/linear/github; like the Vercel chat SDK but effect + more opinionated about software factories; handles threading & debouncing event deliveries and stuff like that 2. mentions & other events spin up our Fold harness ( think kinda like Pi in effect; fully isomorphic, runs anywhere) infra is built on Cloudflare workers and durable objects via alchemy - each thread/channel/issue/pr gets its own mailbox, subject to delivery policies (queue, debounce, batch) mailbox messages wake a fold agent session running in a Durable object, without a sandbox to start it uses cloudflare/computer for a virtual DO-backed filesystem for each issue/PR's git branch the agent can run most commands it wants against the DO's virtual filesystem and the agent can boot a container with the FS mounted into it via FUSE only when it decides it needs one to run heavier commands tools are generated from the webhook event so the agent gets tightly-scoped tools to e.g. create a pr from the issue it's on, or to list failing checks only from the PR it's bound to; plus it's easy to interleave deterministic code it has live progress updates, can react to issues in its thread, etc (linear + slack modules support their respective streaming agent activity & agent plan APIs; for github we fudge it a bit by editing issues in live time) it even has an API so agent work can be handed off to another system (e.g. a k8s cluster that has super thick sandboxes if you need > standard-4 sized-containers from cloudfalre) and that system can post back streaming updates & update the status of the agent run, so it's pretty de-coupled it's wired to automatically investigate CI failures and some other neat stuff open-source at a good example of it in action:
3:44

Just created a PR from a github issue via a serverless background agent, and it's entirely open-source at humanlayer we have been thinking a lot about what good open-source software factory building blocks look like to push on this I built something I've wanted for a long time: a hands-outside-the-box approach of running a lightweight agent in a runtime with a virtual fs, and only using a container when necessary - faster, cheaper, etc combined with really good webhook / event bindings for GitHub, slack, and linear we built two components for it: 1. - effect-native webhook subscriptions for slack/linear/github; like the Vercel chat SDK but effect + more opinionated about software factories; handles threading & debouncing event deliveries and stuff like that 2. mentions & other events spin up our Fold harness ( think kinda like Pi in effect; fully isomorphic, runs anywhere) infra is built on Cloudflare workers and durable objects via alchemy - each thread/channel/issue/pr gets its own mailbox, subject to delivery policies (queue, debounce, batch) mailbox messages wake a fold agent session running in a Durable object, without a sandbox to start it uses cloudflare/computer for a virtual DO-backed filesystem for each issue/PR's git branch the agent can run most commands it wants against the DO's virtual filesystem and the agent can boot a container with the FS mounted into it via FUSE only when it decides it needs one to run heavier commands tools are generated from the webhook event so the agent gets tightly-scoped tools to e.g. create a pr from the issue it's on, or to list failing checks only from the PR it's bound to; plus it's easy to interleave deterministic code it has live progress updates, can react to issues in its thread, etc (linear + slack modules support their respective streaming agent activity & agent plan APIs; for github we fudge it a bit by editing issues in live time) it even has an API so agent work can be handed off to another system (e.g. a k8s cluster that has super thick sandboxes if you need > standard-4 sized-containers from cloudfalre) and that system can post back streaming updates & update the status of the agent run, so it's pretty de-coupled it's wired to automatically investigate CI failures and some other neat stuff open-source at a good example of it in action:

Kyle Mistele 🏴‍☠️

32,746 görüntüleme • 9 gün önce

You guys asked for a deeper sim and that's what 2.9 is. Submitted. Rebuilt Avatars: Player avatars completely redone. 14 hairstyles, 8 skin tones, 6 hair colors, beard options, all at higher resolution. Over 50,000 combinations across the 4,700+ players the game generates. Coach avatars got the same revamp. Player Cards: Cards rebuilt from scratch to feel like a broadcast graphic. Team-color gradient hero that pulls each program's actual colors, oversized OVR display, archetype line, headline stat strip, and tabs for stats, ratings, game logs, and bio. Coaching Systems: Biggest gameplay shift in this build. You pick an offensive scheme and a defensive scheme and they change how your team plays. 6 offensive options (Run & Gun, Motion, Pick & Roll, Princeton, Post-Centric, Balanced) and 6 defensive options (Man, 2-3, 3-2, 1-3-1, Press/Trap, Pack Line). Run & Gun teams shoot more threes and turn the ball over more. Pack Line teams give up fewer paint points but allow more open looks. Same modifiers run in live games and background sims so your scheme matters either way. Scout Cards: Tap any team and you can now see their offensive and defensive playstyle laid out in full. Real game-planning is finally possible. Facing a Press team, you can scheme around it. Facing a 2-3 zone, you can prep your shooters. Pull up an opponent before tipoff and actually know what you're up against. Recruiting Pipelines: Recruit generation now mirrors real basketball geography. Top talent clusters in real hotbeds. Class rank, position rank, and state rank show on every recruit. All-American badges flag elite prospects and State Player of the Year badges call out standouts in smaller states, but neither is an auto cheat code. An All-American is a strong prospect on paper, development still matters, and not every one pans out. State POY varies a lot by state. The real edge is taking a job in a strong pipeline state. Better states produce better players more often, and coaching in a hotbed gives you home state advantage on recruits everyone else is fighting over. Smarter Rankings + Bug Fixes: Rankings rebuilt to reflect who's actually playing the best. Quality wins matter, strength of schedule matters, bad losses hurt. Plus a long list of bug fixes from your Discord reports. If you posted a bug, it's been looked at even if I didn't reply directly. Android: Thank you for everyone who has been testing! We have finally got aversion that is ready for release and I am submitting it right now! I will keep you guys updated on when it drops❤️
0:35

You guys asked for a deeper sim and that's what 2.9 is. Submitted. Rebuilt Avatars: Player avatars completely redone. 14 hairstyles, 8 skin tones, 6 hair colors, beard options, all at higher resolution. Over 50,000 combinations across the 4,700+ players the game generates. Coach avatars got the same revamp. Player Cards: Cards rebuilt from scratch to feel like a broadcast graphic. Team-color gradient hero that pulls each program's actual colors, oversized OVR display, archetype line, headline stat strip, and tabs for stats, ratings, game logs, and bio. Coaching Systems: Biggest gameplay shift in this build. You pick an offensive scheme and a defensive scheme and they change how your team plays. 6 offensive options (Run & Gun, Motion, Pick & Roll, Princeton, Post-Centric, Balanced) and 6 defensive options (Man, 2-3, 3-2, 1-3-1, Press/Trap, Pack Line). Run & Gun teams shoot more threes and turn the ball over more. Pack Line teams give up fewer paint points but allow more open looks. Same modifiers run in live games and background sims so your scheme matters either way. Scout Cards: Tap any team and you can now see their offensive and defensive playstyle laid out in full. Real game-planning is finally possible. Facing a Press team, you can scheme around it. Facing a 2-3 zone, you can prep your shooters. Pull up an opponent before tipoff and actually know what you're up against. Recruiting Pipelines: Recruit generation now mirrors real basketball geography. Top talent clusters in real hotbeds. Class rank, position rank, and state rank show on every recruit. All-American badges flag elite prospects and State Player of the Year badges call out standouts in smaller states, but neither is an auto cheat code. An All-American is a strong prospect on paper, development still matters, and not every one pans out. State POY varies a lot by state. The real edge is taking a job in a strong pipeline state. Better states produce better players more often, and coaching in a hotbed gives you home state advantage on recruits everyone else is fighting over. Smarter Rankings + Bug Fixes: Rankings rebuilt to reflect who's actually playing the best. Quality wins matter, strength of schedule matters, bad losses hurt. Plus a long list of bug fixes from your Discord reports. If you posted a bug, it's been looked at even if I didn't reply directly. Android: Thank you for everyone who has been testing! We have finally got aversion that is ready for release and I am submitting it right now! I will keep you guys updated on when it drops❤️

Hardwood Empire

33,703 görüntüleme • 5 ay önce

Love and Deepspace | New Interactive 5-Star Memory🎶 [Xavier: Offbeat Track] The stage, once dim beneath the stars, now shines anew, the galaxy and starlight gleaming only for you. Across billions of light-years, every journey leads to the meeting of eyes this moment. He will be the brightest star in your sky forever. "There is no darkness that could ever claim me… because my everything is for you to take… It's all yours." 🎶Heartbeats Ablaze Event Duration: From 05:00 on Oct. 29 to 04:59 on Nov. 18 (Server Time) You can select three out of the five event-limited 5-Star Memories: [Xavier: Offbeat Track], [Zayne: Chilling Crescendo], [Rafayel: Ignited Echoes], [Sylus: Improvised Flow], and [Caleb: Passionate Overload]. The drop rate of the 3 Memories you selected will be significantly increased. Each time you obtain a 5-Star Memory, there's a 75% chance it will be one of the three Memories you selected. *Notes: 1. During the event, you can change your selected Memories at any time. If you obtain a 5-Star Memory in a wish, there's a 25% chance that it will be an unselected Memory or a permanent 5-Star Memory. 2. After the event ends, the five event-limited Memories will not be obtainable through other means and will not enter the permanent Wish Pool: Xspace Echo. 3. The Wish event features Precise Wish and a pity system. For more details, please check the in-game rule page. 🎶Claim Polar Night Memory-Themed BGM for Free At the heart of the starlit stage, he and the whole galaxy shine only for you. Obtain Memory [Xavier: Offbeat Track] and complete specific Memoria to claim the corresponding Polar Night Memory-Themed BGM [Offbeat Track] for free as a reward of completing storyline tree nodes! 🎧The corresponding Polar Night Memory-Themed BGM will be officially available on Oct. 29. Mark your calendar! 🎶Cumulative Wish Rewards During the event, after making a certain number of Wishes, you can claim various rewards: Universal Earrings [Heartwork Broadcast], [Deepspace Wish: Limited*20], His [Memory-Themed Outfits], selectable [Event-Limited 5-Star Memory], and more. *The cumulative rewards are only available during this wish event. 🎶Limited-Time Memory Growth Bonus During the event, by completing the growth tasks of the event-limited 5-Star Memories, you can claim various Upgrade and Ascension Materials. When the event-limited Memories reach Rank 1, you can claim the [Special-Colored Memory-Themed Outfit] for the corresponding love interest. 🎶Special: Memory-Themed Outfit Bonus Each Original or Special-Colored Outfit Set includes a Memory-Themed Outfit and three accessories. All can be used separately. *Your look will be applied in all stage performances in-game. ——— 🪐Official Discord: #LoveandDeepspace #HeartbeatsAblaze #Xavier
1:07

Love and Deepspace | New Interactive 5-Star Memory🎶 [Xavier: Offbeat Track] The stage, once dim beneath the stars, now shines anew, the galaxy and starlight gleaming only for you. Across billions of light-years, every journey leads to the meeting of eyes this moment. He will be the brightest star in your sky forever. "There is no darkness that could ever claim me… because my everything is for you to take… It's all yours." 🎶Heartbeats Ablaze Event Duration: From 05:00 on Oct. 29 to 04:59 on Nov. 18 (Server Time) You can select three out of the five event-limited 5-Star Memories: [Xavier: Offbeat Track], [Zayne: Chilling Crescendo], [Rafayel: Ignited Echoes], [Sylus: Improvised Flow], and [Caleb: Passionate Overload]. The drop rate of the 3 Memories you selected will be significantly increased. Each time you obtain a 5-Star Memory, there's a 75% chance it will be one of the three Memories you selected. *Notes: 1. During the event, you can change your selected Memories at any time. If you obtain a 5-Star Memory in a wish, there's a 25% chance that it will be an unselected Memory or a permanent 5-Star Memory. 2. After the event ends, the five event-limited Memories will not be obtainable through other means and will not enter the permanent Wish Pool: Xspace Echo. 3. The Wish event features Precise Wish and a pity system. For more details, please check the in-game rule page. 🎶Claim Polar Night Memory-Themed BGM for Free At the heart of the starlit stage, he and the whole galaxy shine only for you. Obtain Memory [Xavier: Offbeat Track] and complete specific Memoria to claim the corresponding Polar Night Memory-Themed BGM [Offbeat Track] for free as a reward of completing storyline tree nodes! 🎧The corresponding Polar Night Memory-Themed BGM will be officially available on Oct. 29. Mark your calendar! 🎶Cumulative Wish Rewards During the event, after making a certain number of Wishes, you can claim various rewards: Universal Earrings [Heartwork Broadcast], [Deepspace Wish: Limited*20], His [Memory-Themed Outfits], selectable [Event-Limited 5-Star Memory], and more. *The cumulative rewards are only available during this wish event. 🎶Limited-Time Memory Growth Bonus During the event, by completing the growth tasks of the event-limited 5-Star Memories, you can claim various Upgrade and Ascension Materials. When the event-limited Memories reach Rank 1, you can claim the [Special-Colored Memory-Themed Outfit] for the corresponding love interest. 🎶Special: Memory-Themed Outfit Bonus Each Original or Special-Colored Outfit Set includes a Memory-Themed Outfit and three accessories. All can be used separately. *Your look will be applied in all stage performances in-game. ——— 🪐Official Discord: #LoveandDeepspace #HeartbeatsAblaze #Xavier

Love and Deepspace

677,766 görüntüleme • 11 ay önce

tired: Claude Code ports my personal website to a new framework wired: Claude Code generates a command center UI where I can execute the port! with live feedback, including a side-by-side preview of old / new site 😎 this is an example of what I call an "AI HUD" -- a "heads-up display" that gives me visibility into what's going on. i can see: - what terminal commands are running - what files are being created on disk - a live running preview of the old / new website (!) this HUD was actually my third attempt at doing this task, and I liked it the best. here's why I landed there: I wanted to move from middleman to astro for my personal site. These are both static site generators that output html, so I suspected an AI agent could do a good job with a port -- since it could compare old / new build output and try to match. Attempt 1: Agent I just had Claude Code do the port. It went pretty well. But it was hard for me to review what had happened! The git diff was dozens of new files and it was hard to tell how they mapped to the old site. I think the LLM also tried directly writing some files rather than doing deterministic copying, which felt dangerous. Attempt 2: Script I realized a better approach was to have Claude Code write a script that would do the port. The script would execute shell commands like "copy all the markdown files from this directory into this other directory in the new site". This worked much better because I could review the *process* rather than the *results*. Still, even with a nicely commented script, it felt like I was doing a lot of work to review. I wondered: how could I make it ridiculously easy to review this? Attempt 3: HUD Enter the command center! This is an entire web app that I had Claude build just for this one task. I can click buttons to run each step of the port, and watch the new website gradually materialize. It has a node server that runs on my local machine that executes commands on my filesystem and coordinates dev servers for the old/new site. And then a web UI that talks to that server to visualize terminal commands, file trees, and live running previews. It's a HUD because I feel like I can ambiently see everything that the port process is doing 🧐 Was this whole thing worth making for this one-time task? I'm not sure, maybe it was overkill 😅 But it did help me feel more confident that I understood what was going on, and total time was still less than it would have taken me to do the whole port by hand! One way to look at this experience is: "AI can put absurd amounts of effort into a pull request description." What do I mean by that? Well, a PR description is a way to communicate a code change to a human. Typically we do that by writing a bit of text, because that's all we have time for. But given more time and effort, we can do better! An interactive command center / HUD can help a person understand what a code change is actually doing. Historically you'd never imagine investing the effort to do that for a single PR. But now it's within the realm of possibility. So, next time you have an agent do something for you, and you wish you understood better what it was doing, consider: instead of just asking for textual descriptions, maybe ask the agent to make you a HUD!
0:23

tired: Claude Code ports my personal website to a new framework wired: Claude Code generates a command center UI where I can execute the port! with live feedback, including a side-by-side preview of old / new site 😎 this is an example of what I call an "AI HUD" -- a "heads-up display" that gives me visibility into what's going on. i can see: - what terminal commands are running - what files are being created on disk - a live running preview of the old / new website (!) this HUD was actually my third attempt at doing this task, and I liked it the best. here's why I landed there: I wanted to move from middleman to astro for my personal site. These are both static site generators that output html, so I suspected an AI agent could do a good job with a port -- since it could compare old / new build output and try to match. Attempt 1: Agent I just had Claude Code do the port. It went pretty well. But it was hard for me to review what had happened! The git diff was dozens of new files and it was hard to tell how they mapped to the old site. I think the LLM also tried directly writing some files rather than doing deterministic copying, which felt dangerous. Attempt 2: Script I realized a better approach was to have Claude Code write a script that would do the port. The script would execute shell commands like "copy all the markdown files from this directory into this other directory in the new site". This worked much better because I could review the *process* rather than the *results*. Still, even with a nicely commented script, it felt like I was doing a lot of work to review. I wondered: how could I make it ridiculously easy to review this? Attempt 3: HUD Enter the command center! This is an entire web app that I had Claude build just for this one task. I can click buttons to run each step of the port, and watch the new website gradually materialize. It has a node server that runs on my local machine that executes commands on my filesystem and coordinates dev servers for the old/new site. And then a web UI that talks to that server to visualize terminal commands, file trees, and live running previews. It's a HUD because I feel like I can ambiently see everything that the port process is doing 🧐 Was this whole thing worth making for this one-time task? I'm not sure, maybe it was overkill 😅 But it did help me feel more confident that I understood what was going on, and total time was still less than it would have taken me to do the whole port by hand! One way to look at this experience is: "AI can put absurd amounts of effort into a pull request description." What do I mean by that? Well, a PR description is a way to communicate a code change to a human. Typically we do that by writing a bit of text, because that's all we have time for. But given more time and effort, we can do better! An interactive command center / HUD can help a person understand what a code change is actually doing. Historically you'd never imagine investing the effort to do that for a single PR. But now it's within the realm of possibility. So, next time you have an agent do something for you, and you wish you understood better what it was doing, consider: instead of just asking for textual descriptions, maybe ask the agent to make you a HUD!

Geoffrey Litt

63,532 görüntüleme • 1 yıl önce

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.
25:22

Matthew Gallagher Built a $401M Company in Year One with 2 People. And the tool behind it? Claude Code. This year he's on track for $1.8B. Sam Altman predicted this. It's happening now. The problem? It costs money. API credits stack up. Monthly bills keep growing. Every prompt eats your budget. Every project drains your wallet faster. Until now. Two methods. 99% cheaper. One is completely free. Forever. $0. Not a trial. This video breaks down both step by step. ↓ Let me put this in perspective. $100-$500. That's monthly. That's what you spend. That's $6,000/year on API credits. Just to use a tool you haven't shipped anything with. The $401M guy? Spending $0. Same capability. Shipping weekly. Different cost structure. Different results. Different life. I'm about to hand you his cost structure for free. ↓ Open source vs closed source. Pay attention. Closed source: Claude. GPT-4. Pay per token. Meter always running. Open source: Qwen. Llama. Mistral. Free to download. Free to run. Free forever. No meter. No tokens. No bill. Here's what nobody tells you: 80% of coding tasks? Open source handles them. More than handles them. Writes clean code. Debugs errors. Generates boilerplate. Handles routine work perfectly. You're paying premium prices for tasks that don't need premium intelligence. That's hiring a brain surgeon to put on a bandaid. Smart play: Free models for the 80%. Paid credits for the 20%. That's what the $401M guy does. That's what this video teaches you. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 1: Ollama. Local. Free. Forever. Download it. Pull a model. Point Claude Code at it. Done. No internet needed. No API keys required. No monthly subscription. No token counting ever. No bill. Today. Tomorrow. Ever. Your data never leaves your computer. Complete privacy. Complete freedom. Claude Code thinks it's talking to the cloud. It's talking to your laptop. For $0. The video walks through every step: Every config file. Every variable. Every command. Every click. If you can follow a recipe, you can do this. People who set this up 3 months ago? Saved $300-$1,500 since then. Workflow didn't change one bit. ↓ Hardware you need: 16GB RAM: 7B models run smooth. 32GB RAM: 32B models run comfortable. 64GB + GPU: biggest models available. No GPU? Still works. Just slower. Few extra seconds. That's it. Your $1,500 laptop is sitting there running Chrome and Spotify. Put it to work saving you $200/month instead. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses. ↓ Method 2: Open Router. Free Cloud. No Hardware. Weak machine? Don't want local setup? This method is for you. Free AI models in the cloud. No download. No hardware. Configure Claude Code to route through Open Router. The config: Base URL: Open Router API. API key: free Open Router key. Default Sonnet: free. Default Opus: free. Default Haiku: free. Small fast model: free. Subagent model: free. Free. Free. Free. Free. Free across the board. Same interface. Same commands. Same workflow. Zero cost. Copy the config from the video. Paste it. Save $200/month. Starting today. Right now. ↓ When to use which: Ollama (local): Best for privacy. Best for offline work. Best for unlimited usage. Best if you have decent hardware. Open Router (cloud): Best for weak machines. Best for instant setup. Best for trying different models. Best if you don't want to manage anything. Both methods: Best for 80% of your daily work. Still use paid Claude for: Complex architecture. Multi-file refactoring. Deep reasoning tasks. The 20% that actually needs it. $20/month instead of $200/month. Same output. 90% less cost. ↓ The math that should make you angry. You (current): $200-$500/month. $2,400-$6,000/year. $7,200-$18,000 over 3 years. You (after this video): $20-$50/month. $240-$600/year. $720-$1,800 over 3 years. Savings over 3 years: $6,480-$16,200. That's a used car. That's seed money. That's 6 months of rent. All from one 25-minute video. All from 15 minutes of configuration. Highest ROI 25 minutes you'll spend this year. ↓ The limitations. I won't lie to you. Open source is not Opus. Not as smart on complex reasoning. Not as good at long-context tasks. Makes more mistakes on nuanced problems. But they are: Free. Capable. Getting better monthly. Good enough for 80% of daily work. Smart cost management isn't being cheap. It's being strategic. Expensive tool when it matters. Free tool when it doesn't. ↓ The one-person billion-dollar company is coming. $401M in year one proved it's possible. The building blocks: AI that codes: Claude Code. Way to run it free: this video. Distribution: the internet. Customers: everyone. Only missing ingredient? Someone who builds. Not reads about building. Not saves posts about building. Not bookmarks videos about building. Builds. Tools are free. Knowledge is free. Opportunity is screaming. You're still "thinking about it." ↓ Your action plan: Tonight: Watch the video. Tomorrow morning: Set up Ollama or Open Router. Tomorrow afternoon: Build something. Anything. This week: Build a second thing. Faster. This month: Charge someone for it. One video. One setup. One weekend. $0 cost. Unlimited potential. Or keep paying $200/month for something you could get free. Keep consuming instead of building. Keep planning instead of shipping. Matthew Gallagher didn't plan a $401M company. He built it. Full video attached. Every method. Every config. Every tradeoff. 25 minutes. Your move. Follow Himanshu Kumar for more breakdowns that turn free tools into real businesses.

Himanshu Kumar

13,677 görüntüleme • 6 ay önce

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius
0:30

** MEGA Parodius Scaling Effects Part 1 ** One of the big challenges with the Parodius Megadrive port is Stage 8's boss - The puffer-fish *Pooyan* with his full screen scaling effect. The goal is to be very close to the arcade (with extras on top ) so I thought lets tackle it head on to see how close we can get. I was also keen to jump into another scaling code rabit hole haha. Pyron pulled out all the stops and got me the source frames and reworked the BG tiles for this test - a big thankyou to him , Vector Orbitex is busy working on Stage 2 tracks so the team is working hard all round on this port. The MD has no sprite / background GFX scaling hardware , however the VDPs Vertical scroll can be updated per scanline to help vertical scaling on backgrounds, but there is a cpu cost to manage all the interupts so thats not free either. With the Horizontal scaling there is no help at all , apart from a semi-friendly packed pixel format for the cpu to work with, its not quite chunky format but better than planar format still for scaling. So its falls back to the 68k CPU to do all of the horizontal expansion which is the largest cpu cost. Basically drawing strips of either 1x, 2x, 3x or 4x wide columns at speed. So we are one week into this Boss's routine and you can see from the below video the horizontal scaling is implented ( vertical will be in the next update ) . We are scaling from 1x to 4x in the video below in 74 steps for testing . The column distributions are always a bit painfull to do - thankfully they are all worked out now. This is the third scaler I have built and the goal was with this one to make it really flexible for use in other projects also, sometimes when you optimise something to the last degree all the flexibility gets taken out of it. Currenty scaling at 12-25 FPS update here, I had some rules against some optimisations which I would use and some I wouldn't , thankfully we are a bit ahead of the Arcades animation frame rate here still and I may yet find optimisations that fit within the scope. We have vertical scaling and sprite spikes to add yet so Im hoping i can find a few more optimisations to offset things when they are implemented also. In a scale frame update we are processing close to 42000 pixels in ram before using DMA to send to VRAM . Using a 41x16 (656 tile scale buffer) - single buffered for now due to its size in VRAM. So thats nearly 21k in tiles ! I had to re-organise ram a bit to support a buffer of that size for the stage. The scaling function is written in 68k assembly , with a little C code handling the Vertical interupt code ( so the game logic can actually run & DMA updates etc ) . The DMA routines are in assembly also and customised for large chunk size ( big blocks of tiles ) which suits the scaler. I had some race conditions to sort out where the cpu was faster than DMA (sending tiles from RAM to VRAM ) and in some cases where it wasn't so it had to be balanced. We may be able to add more detail into the top and bottom of the background yet but its low priority for now until all the other bits are in !! #SGDK #SegaMegadrive #Genesis #Parodius

Shannon Birt

25,803 görüntüleme • 9 ay önce

📢 $BVM MARCH UPDATES 📢 GM. In Feb, we added these products to the BVM ecosystem: ✅BVM Staking, ✅Bitcoin Stamps, ✅SRC-20 Bridge, ✅Avail, ✅Jackal, ✅Arweave & ✅ IPFS. We're excited to share with the community what we’re shipping next in March. 1. FOUR MORE BITCOIN L2 BLOCKCHAINS BVM’s mission is to scale Bitcoin by powering thousands of Bitcoin L2s. In March, we’ll work with 4 different builders to help them launch their own Bitcoin L2 blockchains and ultimately scale Bitcoin with unlimited throughput and rich user cases. ⛓️ Swamps: DeFi Bitcoin L2 for SRC-20 @swamps_src20 is launching the first-ever Stamps-based Bitcoin L2 blockchain with BVM, designed for SRC-20 DEX. We’re super excited to be working with @0xnovae5Db RMZ 🟨 and the Swamps team. ⛓️ Naka: DeFi Bitcoin L2 for BRC-20/BRC-404 Naka Chain is an Ordinals-based Bitcoin L2 blockchain designed for BRC-20. They just added support for BRC-404. We're excited to work with DeBit | NakaChain.xyz and the Naka team. ⛓️ Satoshi Sync: Bitcoin L2 for Inscription Markets SatoshiSync is building the first chain-agnostic Inscription Protocol with BVM, enabling everyone to launch their own Inscription Market. It’s been a pleasure working with @okubalinska and the Satoshi Sync team. ⛓️ ███████: Bitcoin L2 for ████ This is a big one. We'll share it when it's ready. Super excited to be working on this with ███████ and the ███████ team. Note: If you're thinking about launching your own Bitcoin L2, please DM us. Would love to help! 2. BITCOIN MODULE STORE BVM is a modular Bitcoin L2 infrastructure. The more building blocks, the more developers can build on Bitcoin. This month, we’ll be adding these new modules to the Bitcoin Modular Store. 🧱 Filecoin Filecoin is one of the best decentralized storage networks. Developers can build their Bitcoin L2 and choose Filecoin to store their data. 🧱 Syscoin zkDA Syscoin is a Bitcoin-backed Data Availability layer. It is secured by Bitcoin’s own PoW plus Syscoin’s finality. We think it's a super interesting DA solution. 🧱 BVM-ETH Bridge Ethereum bridge will enable us to flow assets between BVM and Ethereum. You can trade $BVM on Uniswap or bridge ETH to various Bitcoin L2 blockchains powered by BVM. Note: please do make suggestions on which modules we should integrate next! 3. BRC-404 Starting out as a fun weekend experiment, BRC-404 shows us that it could become a promising protocol. $3.5M trading volume so far! 🤯🤯🤯 🎨 Fractionalize Ordinals with BRC-404 The idea is to take an existing Ordinal Inscription and turn it into BRC-404. Then, Ordinals would be much more accessible to many smaller buyers, and at the same time, the collectors would make a lot more on trading fees. That's really the beauty of semi-fungible tokens. You can move between the fungible worlds and the non-fungible worlds. 🔒 ███████ for BRC-404 This product is exciting. We can't quite talk about it yet. But we'll do it when it's ready later this month. 4. COMMUNITY While our product team is busy crunching out code, our community team is building the foundation for our community to thrive in the coming months. 🚀 Setup a home for BVM holders to hang out 🚀 Work on airdrop deals for BVM holders 🚀 List BVM on Coin Market Cap 🚀 List BVM on Gecko Terminal 🚀 List BVM on DEX 🚀 List BVM on CEX This is our plan for March. We hope to get most of it done for the community. See you on #Bitcoin
2:16

📢 $BVM MARCH UPDATES 📢 GM. In Feb, we added these products to the BVM ecosystem: ✅BVM Staking, ✅Bitcoin Stamps, ✅SRC-20 Bridge, ✅Avail, ✅Jackal, ✅Arweave & ✅ IPFS. We're excited to share with the community what we’re shipping next in March. 1. FOUR MORE BITCOIN L2 BLOCKCHAINS BVM’s mission is to scale Bitcoin by powering thousands of Bitcoin L2s. In March, we’ll work with 4 different builders to help them launch their own Bitcoin L2 blockchains and ultimately scale Bitcoin with unlimited throughput and rich user cases. ⛓️ Swamps: DeFi Bitcoin L2 for SRC-20 @swamps_src20 is launching the first-ever Stamps-based Bitcoin L2 blockchain with BVM, designed for SRC-20 DEX. We’re super excited to be working with @0xnovae5Db RMZ 🟨 and the Swamps team. ⛓️ Naka: DeFi Bitcoin L2 for BRC-20/BRC-404 Naka Chain is an Ordinals-based Bitcoin L2 blockchain designed for BRC-20. They just added support for BRC-404. We're excited to work with DeBit | NakaChain.xyz and the Naka team. ⛓️ Satoshi Sync: Bitcoin L2 for Inscription Markets SatoshiSync is building the first chain-agnostic Inscription Protocol with BVM, enabling everyone to launch their own Inscription Market. It’s been a pleasure working with @okubalinska and the Satoshi Sync team. ⛓️ ███████: Bitcoin L2 for ████ This is a big one. We'll share it when it's ready. Super excited to be working on this with ███████ and the ███████ team. Note: If you're thinking about launching your own Bitcoin L2, please DM us. Would love to help! 2. BITCOIN MODULE STORE BVM is a modular Bitcoin L2 infrastructure. The more building blocks, the more developers can build on Bitcoin. This month, we’ll be adding these new modules to the Bitcoin Modular Store. 🧱 Filecoin Filecoin is one of the best decentralized storage networks. Developers can build their Bitcoin L2 and choose Filecoin to store their data. 🧱 Syscoin zkDA Syscoin is a Bitcoin-backed Data Availability layer. It is secured by Bitcoin’s own PoW plus Syscoin’s finality. We think it's a super interesting DA solution. 🧱 BVM-ETH Bridge Ethereum bridge will enable us to flow assets between BVM and Ethereum. You can trade $BVM on Uniswap or bridge ETH to various Bitcoin L2 blockchains powered by BVM. Note: please do make suggestions on which modules we should integrate next! 3. BRC-404 Starting out as a fun weekend experiment, BRC-404 shows us that it could become a promising protocol. $3.5M trading volume so far! 🤯🤯🤯 🎨 Fractionalize Ordinals with BRC-404 The idea is to take an existing Ordinal Inscription and turn it into BRC-404. Then, Ordinals would be much more accessible to many smaller buyers, and at the same time, the collectors would make a lot more on trading fees. That's really the beauty of semi-fungible tokens. You can move between the fungible worlds and the non-fungible worlds. 🔒 ███████ for BRC-404 This product is exciting. We can't quite talk about it yet. But we'll do it when it's ready later this month. 4. COMMUNITY While our product team is busy crunching out code, our community team is building the foundation for our community to thrive in the coming months. 🚀 Setup a home for BVM holders to hang out 🚀 Work on airdrop deals for BVM holders 🚀 List BVM on Coin Market Cap 🚀 List BVM on Gecko Terminal 🚀 List BVM on DEX 🚀 List BVM on CEX This is our plan for March. We hope to get most of it done for the community. See you on #Bitcoin

Bitcoin Virtual Machine

32,170 görüntüleme • 2 yıl önce

What’s Left Before InterPredict Mainnet? 🟣🚀 InterPredict is getting closer to Mainnet but we are not rushing the process. ⏳ A successful Mainnet launch is about more than reaching a date on the calendar. It is about ensuring that the protocol, infrastructure and user experience are ready to operate reliably in a production environment. 🏗️🔐 Several important technical milestones have already been completed, while the remaining work is focused on integration, refinement and final preparation. 🛠️✅ ✅ Completed Milestones 1. Smart Contract Development and Testing 📜🔍 The smart contracts have been developed and tested, establishing the core on-chain foundation of the InterPredict protocol. This work is essential for ensuring that the protocol’s key functions operate as intended and can support the next stage of development. ⚙️⛓️ 2. Backend Deployment 🖥️🚀 The new backend infrastructure has been successfully deployed and is now running in a production environment. This provides the services required to support the platform and enables the frontend to communicate with the systems powering InterPredict. 🔗📡 3. Transaction and Activity Tracking 📊👀 Users can now clearly view the results of their interactions and monitor relevant activity within the platform. Improved visibility helps users better understand their transactions, actions and participation across the platform. ✅📈 4. Reliable Market Indexing 🗂️⛓️ Blockchain activity is being indexed consistently and reflected accurately within the application. Reliable indexing is important because it ensures that on-chain events, market updates and other protocol activity are displayed correctly for users. 🔄📍 5. Faster Data Synchronisation ⚡📡 The platform’s data synchronisation has been improved so that market states, votes, activities and other protocol information can be reflected in the dApp more quickly. Faster synchronisation creates a smoother and more responsive experience between blockchain activity and the information displayed in the application. 🚀📱 ⏳ Currently in Progress 1. Frontend and Backend Integration 🔌🖥️ The new frontend experience is being connected to the backend services so that both layers work together smoothly and reliably. This stage ensures that user actions, platform data and backend processes are properly connected across the entire application. 🔗✅ 2. User Experience Improvements 🎨📱 The Closed Beta provided valuable feedback and highlighted areas where the platform can become easier and more intuitive to use. The team is continuing to improve: • Navigation 🧭 • Mobile usability 📱 • Loading states ⏳ • Error handling ⚠️ • Market interaction flows 📊 • Overall platform usability ✅ These improvements are designed to make InterPredict clearer, faster and more accessible for both new and existing users. 🙌 3. Security and Reliability 🔐🛡️ The infrastructure and protocol are being reviewed and strengthened to ensure they are prepared for production use. This includes improving system stability, reviewing critical components and making sure the platform can operate reliably as activity and user participation increase. 🏗️📈 Security and reliability are not final checks to be rushed. They are essential parts of building a platform users can trust. 🤝 4. Mainnet Readiness 🚦🚀 The final stage is bringing all the moving parts together and testing the complete system as one connected platform. This includes the: → Smart contracts 📜 → Backend infrastructure 🖥️ → Frontend experience 🎨 → Market indexing 🗂️ → Data synchronisation 🔄 → Transaction tracking 📊 → Security systems 🔐 Each component must work correctly on its own and together with every other part of the protocol. ⚙️✅ Building for the Long Term 🏗️🌍 Mainnet is not simply a launch date. It is a major milestone that represents the beginning of the next phase for InterPredict. 🟣 The goal is not to launch as quickly as possible. The goal is to launch with a strong foundation that gives the team confidence to continue building, improving and scaling the platform after launch. 🚀📈 The Closed Beta showed us where improvements were needed. V2 is where those lessons are being applied. 💡🔧 There is still work to complete—but every step brings InterPredict closer to a more reliable, efficient and user-friendly platform. ⏳➡️✅ The Next Big Step 🟣🚀 The main technical foundations are now in place. The remaining focus is on integration, user experience, security, reliability and final Mainnet preparation. 🔐⚙️ We are not rushing to launch. We are making sure InterPredict is ready to launch properly. Stay updated and follow the journey towards Mainnet. 🟣🌐🚀 Follow InterPredict 📣 🔗 Follow InterPredict: InterPredict 📲 Join the Telegram community: InterLink Labs 👤 + 🌐 InterPredict InterLink Foundation KV Reina | InterLink Labs Mira #InterPredict #ITP #InterLink #ITLG #ITL #PredictionMarkets #ITL #ITLG #Web3 #Blockchain #dApp #Mainnet #Tokenomics
0:22

What’s Left Before InterPredict Mainnet? 🟣🚀 InterPredict is getting closer to Mainnet but we are not rushing the process. ⏳ A successful Mainnet launch is about more than reaching a date on the calendar. It is about ensuring that the protocol, infrastructure and user experience are ready to operate reliably in a production environment. 🏗️🔐 Several important technical milestones have already been completed, while the remaining work is focused on integration, refinement and final preparation. 🛠️✅ ✅ Completed Milestones 1. Smart Contract Development and Testing 📜🔍 The smart contracts have been developed and tested, establishing the core on-chain foundation of the InterPredict protocol. This work is essential for ensuring that the protocol’s key functions operate as intended and can support the next stage of development. ⚙️⛓️ 2. Backend Deployment 🖥️🚀 The new backend infrastructure has been successfully deployed and is now running in a production environment. This provides the services required to support the platform and enables the frontend to communicate with the systems powering InterPredict. 🔗📡 3. Transaction and Activity Tracking 📊👀 Users can now clearly view the results of their interactions and monitor relevant activity within the platform. Improved visibility helps users better understand their transactions, actions and participation across the platform. ✅📈 4. Reliable Market Indexing 🗂️⛓️ Blockchain activity is being indexed consistently and reflected accurately within the application. Reliable indexing is important because it ensures that on-chain events, market updates and other protocol activity are displayed correctly for users. 🔄📍 5. Faster Data Synchronisation ⚡📡 The platform’s data synchronisation has been improved so that market states, votes, activities and other protocol information can be reflected in the dApp more quickly. Faster synchronisation creates a smoother and more responsive experience between blockchain activity and the information displayed in the application. 🚀📱 ⏳ Currently in Progress 1. Frontend and Backend Integration 🔌🖥️ The new frontend experience is being connected to the backend services so that both layers work together smoothly and reliably. This stage ensures that user actions, platform data and backend processes are properly connected across the entire application. 🔗✅ 2. User Experience Improvements 🎨📱 The Closed Beta provided valuable feedback and highlighted areas where the platform can become easier and more intuitive to use. The team is continuing to improve: • Navigation 🧭 • Mobile usability 📱 • Loading states ⏳ • Error handling ⚠️ • Market interaction flows 📊 • Overall platform usability ✅ These improvements are designed to make InterPredict clearer, faster and more accessible for both new and existing users. 🙌 3. Security and Reliability 🔐🛡️ The infrastructure and protocol are being reviewed and strengthened to ensure they are prepared for production use. This includes improving system stability, reviewing critical components and making sure the platform can operate reliably as activity and user participation increase. 🏗️📈 Security and reliability are not final checks to be rushed. They are essential parts of building a platform users can trust. 🤝 4. Mainnet Readiness 🚦🚀 The final stage is bringing all the moving parts together and testing the complete system as one connected platform. This includes the: → Smart contracts 📜 → Backend infrastructure 🖥️ → Frontend experience 🎨 → Market indexing 🗂️ → Data synchronisation 🔄 → Transaction tracking 📊 → Security systems 🔐 Each component must work correctly on its own and together with every other part of the protocol. ⚙️✅ Building for the Long Term 🏗️🌍 Mainnet is not simply a launch date. It is a major milestone that represents the beginning of the next phase for InterPredict. 🟣 The goal is not to launch as quickly as possible. The goal is to launch with a strong foundation that gives the team confidence to continue building, improving and scaling the platform after launch. 🚀📈 The Closed Beta showed us where improvements were needed. V2 is where those lessons are being applied. 💡🔧 There is still work to complete—but every step brings InterPredict closer to a more reliable, efficient and user-friendly platform. ⏳➡️✅ The Next Big Step 🟣🚀 The main technical foundations are now in place. The remaining focus is on integration, user experience, security, reliability and final Mainnet preparation. 🔐⚙️ We are not rushing to launch. We are making sure InterPredict is ready to launch properly. Stay updated and follow the journey towards Mainnet. 🟣🌐🚀 Follow InterPredict 📣 🔗 Follow InterPredict: InterPredict 📲 Join the Telegram community: InterLink Labs 👤 + 🌐 InterPredict InterLink Foundation KV Reina | InterLink Labs Mira #InterPredict #ITP #InterLink #ITLG #ITL #PredictionMarkets #ITL #ITLG #Web3 #Blockchain #dApp #Mainnet #Tokenomics

Tekkaus® | InterLink Global Leader • MOD • OG

100,095 görüntüleme • 1 ay önce

Hell froze over: announcing FormKit for React. Secretly framework-agnostic since inception, today we’re open sourcing the most popular Vue form library…for React. Why is this a big deal? 1. Forms are still hard. We (the creators of FormKit) thought form libraries were no longer necessary, given the trajectory of coding agents. It turns out we were wrong, and we learned this the hard way. Need repeating conditional fields nested 3 layers deep inside a dynamic component, with accessibility, validation, internationalization, and backend error placement? Turns out coding agents aren’t great at that. It’s table stakes for FormKit. 2. Single component. This matters more than you would think, but FormKit doesn’t ship lots of different components each with its own props. Instead, it has a single one: and unified props. This was done to provide a better DX to human engineers. It makes it easy to spot when a given component was part of the form’s data structure vs a presentational component. It turns out this matters even more to coding agents than humans. No matter where your coding agent is, whenever it sees “FormKit” it immediately knows “oh, that’s part of the form’s data”. 3. No plumbing. FormKit doesn’t require any manual data collection, event listening, or state tracking. It does all this for you on a heavily tested, framework agnostic, self-assembling graph. The only code your agent needs to write is declarative templates and submission handlers that respond to the state. 4. Dense colocation. FormKit’s syntax happens to be ideal for coding agents; nearly everything you need to know about a given input is *on* the input: Colocation dramatically improves the efficacy of coding agents. 5. DOM. FormKit, unlike most form frameworks in React, renders the actual DOM. This also increases colocation and best practices, meaning your coding agent is far more likely to produce consistent and high-quality output that looks and acts the way its supposed to. 6. Schema. FormKit’s own inputs are not written using Vue or React — instead, FormKit has its own render schema — think of it like an AST for the DOM — and you can modify it on the fly. It’s not very human-friendly to write, but it turns out most models are already pretty well trained on FormKit’s schema. Want your inputs to look a bit different on one form than another? No problem, your coding agent can easily make those changes *without* modifying the JSX structure at all. Oh, and any inputs you create for Vue work with React and vice versa. 7. Plugins. FormKit leans into the unstructured tree graph hard. The graph doesn’t just collect data, it also passes down configuration and plugins. Want one form to work a bit differently than another one? No problem — just add a plugin to the top of that form or group and its children will all receive that feature. You can even mass assign props and configuration this way. Of course, FormKit has been solving these exact issues for a long time, but it wasn’t until we started using it on our own projects with coding agents that we realized what a huge advantage it is. With so many people using coding agents with React, it made sense to unveil FormKit for what it has always been — a completely framework-agnostic form framework that happens to unlock your coding agents. ➡️
1:00

Hell froze over: announcing FormKit for React. Secretly framework-agnostic since inception, today we’re open sourcing the most popular Vue form library…for React. Why is this a big deal? 1. Forms are still hard. We (the creators of FormKit) thought form libraries were no longer necessary, given the trajectory of coding agents. It turns out we were wrong, and we learned this the hard way. Need repeating conditional fields nested 3 layers deep inside a dynamic component, with accessibility, validation, internationalization, and backend error placement? Turns out coding agents aren’t great at that. It’s table stakes for FormKit. 2. Single component. This matters more than you would think, but FormKit doesn’t ship lots of different components each with its own props. Instead, it has a single one: and unified props. This was done to provide a better DX to human engineers. It makes it easy to spot when a given component was part of the form’s data structure vs a presentational component. It turns out this matters even more to coding agents than humans. No matter where your coding agent is, whenever it sees “FormKit” it immediately knows “oh, that’s part of the form’s data”. 3. No plumbing. FormKit doesn’t require any manual data collection, event listening, or state tracking. It does all this for you on a heavily tested, framework agnostic, self-assembling graph. The only code your agent needs to write is declarative templates and submission handlers that respond to the state. 4. Dense colocation. FormKit’s syntax happens to be ideal for coding agents; nearly everything you need to know about a given input is *on* the input: Colocation dramatically improves the efficacy of coding agents. 5. DOM. FormKit, unlike most form frameworks in React, renders the actual DOM. This also increases colocation and best practices, meaning your coding agent is far more likely to produce consistent and high-quality output that looks and acts the way its supposed to. 6. Schema. FormKit’s own inputs are not written using Vue or React — instead, FormKit has its own render schema — think of it like an AST for the DOM — and you can modify it on the fly. It’s not very human-friendly to write, but it turns out most models are already pretty well trained on FormKit’s schema. Want your inputs to look a bit different on one form than another? No problem, your coding agent can easily make those changes *without* modifying the JSX structure at all. Oh, and any inputs you create for Vue work with React and vice versa. 7. Plugins. FormKit leans into the unstructured tree graph hard. The graph doesn’t just collect data, it also passes down configuration and plugins. Want one form to work a bit differently than another one? No problem — just add a plugin to the top of that form or group and its children will all receive that feature. You can even mass assign props and configuration this way. Of course, FormKit has been solving these exact issues for a long time, but it wasn’t until we started using it on our own projects with coding agents that we realized what a huge advantage it is. With so many people using coding agents with React, it made sense to unveil FormKit for what it has always been — a completely framework-agnostic form framework that happens to unlock your coding agents. ➡️

Justin Schroeder

11,705 görüntüleme • 6 ay önce

A tree stood in that backyard for probably 40 years. Nobody who walked past it, sat under it, leaned a bike against it, ever knew what was living inside the trunk. Then someone cut into it. And what came out shouldn't be possible. Not sap. Not resin. Water. Gallons of it. Pouring out of solid wood like someone left a hose running inside a living organism. If your first reaction is "that's fake" — I understand. I had the same reaction the first time I saw footage like this. Trees are supposed to be dry on the inside. Bark, wood, rings, maybe some sticky sap if you're unlucky enough to touch a pine. Nobody grows up learning that a tree can be a pressurized tank. But here's the thing nobody tells you in school: some trees are. There's a real, documented, scientifically studied phenomenon behind this, and once you understand it, you will never look at a tree the same way again. I'm going to walk you through exactly what's happening inside these trees, why it happens, which species are famous for it, the wild historical accounts of people discovering it by accident (sometimes violently), and why arborists still get caught off guard by it after decades on the job. Stick with me. This gets stranger the deeper you go. — FIRST: the phenomenon has a name. Arborists and plant pathologists call it "wetwood," and in its more advanced, foul-smelling form, "slime flux." It's not folklore. It's not an urban legend some guy made up on a forum. It's in forestry textbooks, USDA plant pathology bulletins, and arborist training manuals. Here's the mechanism, stripped down to plain English: Trees have a core of heartwood — the dead, structural center of the trunk that no longer transports nutrients. It's basically the tree's skeleton. In most trees, that heartwood is just dry, solid wood. But in certain species, under certain conditions, bacteria colonize that heartwood core. Anaerobic bacteria — the kind that thrive without oxygen — move in and start fermenting the wood tissue from the inside. That fermentation process does two things. First, it draws in and traps enormous amounts of water inside the wood, way beyond what healthy wood would ever hold. Second, it produces gas as a byproduct — methane, carbon dioxide, hydrogen sulfide — and that gas has nowhere to go. It's sealed inside solid wood, inside bark, inside a living, growing tree. So you end up with a chamber, sometimes several feet long, sitting inside the trunk, completely pressurized, completely hidden, holding a mixture of bacteria-laden water and trapped gas — sometimes under enough pressure that when the seal finally breaks, it doesn't drip. It sprays. It gushes. It pours out like the tree itself is bleeding. Now imagine you're an arborist. You've cut down thousands of trees. You know the drill: bark, sapwood, heartwood, done. And then one day your saw breaks through into a hidden pocket you had no way of detecting from the outside, and suddenly you're standing in a puddle that came from inside a tree trunk. That moment is what you're about to see. — Let me give you some numbers, because the scale of this is what makes people stop scrolling. Documented cases of wetwood trees have released water measured in the dozens of gallons from a single cut. Some large elms and cottonwoods have been recorded discharging water continuously for hours after being wounded, with foresters describing "streams" running from the trunk down to the base of the tree and pooling on the ground like a slow leak from a cracked pipe. Certain species are repeat offenders. Elm. Poplar. Cottonwood. Mulberry. Certain oaks. These trees, especially older ones with some history of trunk injury (a old pruning wound, storm damage, a lightning strike, construction damage to the roots), are far more likely to develop internal wetwood pockets, because any breach in the bark is an open door for the bacteria that start this whole process. That's the part that should sit with you for a second. It usually starts with something small. A branch snapped off in a storm. A lawnmower nick at the base. A woodpecker hole. Something that looks like nothing. And over years — sometimes decades — that tiny wound becomes the entry point for a slow-motion transformation happening entirely out of sight, turning part of the tree's interior into a sealed reservoir. You could have one in your own yard right now. You'd have no way of knowing. That's not a scare tactic, that's just how wetwood works — it's invisible from the outside until the tree is cut, cored, drilled, or storm-damaged enough to expose the pocket. — There's an older, uglier cousin of wetwood, and it's called "slime flux," and I promise you the name undersells it. When the pressure inside a wetwood pocket gets high enough, it doesn't wait for someone with a chainsaw. It finds its own way out — through cracks in the bark, through old wounds, through the base of branches. And when that fluid meets open air, the bacteria and yeast in it start reacting with oxygen, and the whole thing turns into a foul, fermenting slurry running down the bark. Old-time foresters called this "flux disease," and some described the smell as somewhere between rotten cabbage and spoiled beer. Insects love it. Certain flies and beetles are specifically drawn to fluxing trees, and some entomologists have documented entire miniature ecosystems living in the wet, fermented bark of a heavily infected wetwood tree. So the version you're about to watch — a clean cut suddenly releasing a rush of water — is actually the tamer version of this phenomenon. It's what happens when the pressure is released fast and deliberately, in a controlled way, instead of slowly seeping and fermenting on the bark for months. It's dramatic, but it's not even the strangest form this condition takes. — Here's where it gets almost unbelievable if you didn't grow up around old-growth forests or work in forestry: this isn't new, and it isn't rare enough to be dismissed as a one-off. Loggers in the 19th and early 20th centuries wrote about "water trees" and "spring trees" — trunks that, when felled or split, would release surprising volumes of water, sometimes described as clean and cold enough that thirsty travelers would drink straight from a freshly cut trunk. Some of these accounts read almost like myth: a felled tree in a dry stretch of forest becoming an impromptu water source for a work crew that had run out of canteens. Indigenous and folk traditions across multiple continents have stories about trees that "cry" or "bleed" water, long before anyone had a bacteriological explanation for it. In parts of the American South, old-timers used to warn newcomers about certain elms and cottonwoods being "wet-hearted," a term passed down generation to generation with no formal science behind it — just observation. They knew, decades before plant pathologists gave it a Latin name, that some trees were different on the inside. There's something almost humbling about that. A phenomenon that sounds like it belongs in a fantasy novel — a tree holding a hidden reservoir inside its trunk — turns out to be something people quietly knew about for centuries, passed down as folk wisdom, and modern science eventually caught up and explained the mechanism. — Let's talk about pressure, because this is the part that turns a "huh, neat" fact into something genuinely dramatic to witness. Wetwood pockets aren't just wet. They're pressurized. Researchers who have studied this by drilling into infected trees and measuring the internal gas pressure have recorded readings significantly above normal atmospheric pressure — high enough that when a probe finally punctures the pocket, gas and liquid don't just seep out, they can audibly hiss, spray, or in some documented cases, forcefully eject material several feet from the trunk. Think about what that means physically. You have a living tree. Roots pulling water up. Leaves doing their thing. Bark looking completely normal, maybe a little bit of old staining near a wound if you know exactly what to look for. And inside, invisible to anyone walking by, there's a sealed chamber behaving less like "wood" and more like a bottle of soda that's been shaken and capped for years. Cut into that with the wrong angle, at the wrong depth, and you are opening something that has been building pressure since before some of you reading this were born. That is not an exaggeration. Some of these wetwood pockets, in old trees with a long history of minor trunk injuries, have been forming and sealing and re-sealing for twenty, thirty, forty years before anyone finally exposes them. — I want to address the skeptics directly, because there's always a version of this that goes semi-viral and the replies fill up with "CGI," "staged," "fake," before anyone bothers to check. This is genuinely, boringly, documented science. Forestry extension offices at multiple universities have publications specifically on wetwood and slime flux — the kind of dry, unglamorous PDF nobody reads unless they're an arborist student cramming for an exam. Plant pathology courses cover it. It's in the same category as things like "trees can produce enough root pressure to push water dozens of feet upward with no pump" — real, measurable, and honestly stranger than most fiction, which is exactly why it keeps going viral every time footage surfaces. The wild part isn't that it's fake. The wild part is that it's real, it's been known for over a century, and most people are hearing about it for the first time through a random video instead of a biology class. — Here's a question worth sitting with: how many trees around you, right now, could be holding something like this? You're not going to know by looking. That's the unsettling part. Wetwood doesn't announce itself from the outside in any reliable way most people would recognize. Sometimes there's a dark wet-looking stain running down the bark from an old wound — that's actually one of the only visible clues, and most people who see it assume it's just water damage or normal bark discoloration, not a sign of a pressurized internal reservoir. Arborists who specialize in tree risk assessment actually have to factor this into their evaluations, because a wetwood pocket can also be a structural weak point — the internal decay associated with it can compromise a tree's strength in ways that aren't visible from a standard visual inspection. So this isn't purely a "huh, cool fact" situation. For professionals, it's something they're trained to watch for, because it changes how a tree behaves, how it should be pruned, and in some cases whether it's even safe to keep standing near a structure. — Let's go species by species for a second, because the "which trees do this" question comes up every single time this kind of footage circulates. Elms are probably the most famous offenders — American elm and Siberian elm both show up repeatedly in wetwood and slime flux case studies. Cottonwoods and poplars are right behind them, especially older specimens with a history of storm damage or pruning wounds. Mulberry trees have a documented tendency toward it as well. Certain oaks can develop it, though it's less common and usually tied to a specific injury history. Willows, with their notoriously soft and moisture-loving wood, are also frequent candidates. What connects almost all of these species isn't some exotic trait — it's actually pretty mundane. They tend to be fast-growing, softer-wooded trees that are more prone to storm damage, cracking, and wound formation over their lifespan, which means more entry points for the bacteria that kick off the entire process. Slower-growing, denser hardwoods are comparatively less prone, though not immune. So if you've got an old elm, cottonwood, poplar, willow, or mulberry anywhere near you — especially one that's taken some damage over the decades, a lost limb, a lightning strike, an old chainsaw wound from a previous trim — there's a real, non-zero chance that tree is sitting on its own hidden reservoir right now, quietly pressurizing, waiting for the day someone finally cuts into the wrong spot. — There's a specific kind of moment that happens on video like this, and if you've watched enough tree-work content you already know it: the split second between the cut going in and the reaction on the face of whoever's holding the saw. That reaction is real. You cannot fake genuine, immediate confusion. Professionals who have done this job for years, who have felled hundreds or thousands of trees, who think they've seen every possible thing a tree trunk can do — and then something happens that their entire career didn't prepare them for. That's the part that makes this kind of footage so different from staged "reaction" content you see everywhere else online. Nobody scripts confusion that specific. Nobody fakes the half-second delay where someone's brain is visibly trying to process what their eyes are showing them. — I'll leave you with this. Every single day, all over the world, people are cutting down trees for completely mundane reasons — storm cleanup, construction, disease removal, firewood, somebody's yard finally getting redone. Thousands of trees. Every day. Most of the time it's exactly as boring as it sounds: cut, drop, haul, done. And then every so often, completely without warning, one of those ordinary trees turns out to be something else entirely. A tree that's been quietly filling itself with water for years, maybe decades, completely undetectable from the outside, sealed shut under bark that looks exactly like every other tree on the block. Nobody plans for that. Nobody sees it coming. That's exactly what makes it worth watching when it happens to be caught on camera. You already scrolled past the video once. Go back and actually watch what happens the second that bar breaks through. You will not believe how much comes out. And once you know why, you'll start looking at every old tree in your neighborhood a little differently. — Let's talk about the pressure numbers again, because I glossed over just how absurd they get in the most extreme documented cases. Standard atmospheric pressure at sea level is about 14.7 pounds per square inch. Some measured wetwood pockets have registered internal gas pressures multiple times higher than that — enough that when researchers insert a hollow probe to sample the gas, it doesn't calmly bubble out, it forces its way through with an audible hiss, sometimes strong enough to make a sound loud enough to hear from several feet away. Now picture that same pressure, except instead of a thin research probe, it's a chainsaw bar plowing straight through the wall of the pocket in one continuous motion. There's no controlled release valve. There's no slow bleed-off. The seal just fails all at once, and whatever's inside — water, gas, fermented bacterial slurry — takes the fastest path out, which is usually straight toward whoever is standing closest. That's not drama for the sake of drama. That's just fluid dynamics doing what fluid dynamics does when a pressurized container gets breached in one violent motion instead of a slow leak. — People love comparing this to other "trees doing things they shouldn't" phenomena, so let's run through a few, because it puts wetwood in context. Root pressure is a real, separately documented thing — some trees, particularly certain maples and grapevines, can generate enough internal pressure through osmosis alone to push water dozens of feet upward through their trunk with zero mechanical pump involved, which is part of why maple syrup tapping works in early spring: cut a hole, and sap doesn't just sit there, it actively flows out under real pressure. Bamboo, meanwhile, has hollow internal chambers between each node that can fill with water and, when punctured, release a surprising rush for something that looks like solid stalk from the outside. Certain cacti and succulents store such enormous internal water reserves that a single barrel cactus can hold multiple gallons, enough that desert survival guides have long described (with real caveats about bitterness and toxicity in some species) cutting into one as an emergency water source. None of those are the exact same mechanism as bacterial wetwood. But they all share the same core surprise: the outside of a plant tells you almost nothing about what's happening on the inside. Trees and plants in general are far better at hiding internal reservoirs, chambers, and pressure systems than most people ever consider, because we're trained from childhood to think of "wood" as uniformly solid and dry. — Here's a question I want you to actually think about instead of just scrolling past: why does this footage hit people so hard emotionally, when it's "just" water? I think it's because it breaks a category we didn't know we had. Somewhere in your brain, without ever being taught it explicitly, you built a rule: solid things don't have hidden liquid interiors. Rocks are solid. Wood is solid. A tree trunk, no matter how big, is filed under "solid object" right next to a brick or a fence post. So when a tree trunk suddenly behaves like a punctured water balloon, it's not just surprising — it's a small, harmless violation of a rule you didn't know you were relying on. That's the exact same psychological mechanism behind why people can't look away from videos of hidden compartments, false walls, geodes cracked open to reveal crystal interiors, or ice cores pulled from glaciers showing air bubbles thousands of years old. The object looked like one thing on the outside and turned out to be something completely different on the inside. Our brains are wired to lock onto that specific kind of surprise and replay it. — I want to walk through what's actually happening at a microscopic level too, because the bacteria part is honestly the wildest piece of this whole story and it usually gets skipped over. The bacteria responsible for wetwood are largely anaerobic — meaning they thrive specifically in environments with no oxygen, which describes the sealed interior of a heartwood pocket perfectly. Species commonly implicated include various strains that also show up in other low-oxygen fermentation processes elsewhere in nature. These bacteria essentially treat the interior of the tree the way yeast treats a sealed fermentation vessel: they break down wood sugars and cellulose components, and as a byproduct of that metabolic process, they release gas. Methane. Carbon dioxide. Sometimes hydrogen sulfide, which is the compound responsible for the "rotten egg" smell associated with some of the worst slime flux cases. Here's the part that should genuinely unsettle you a little: this process can continue, essentially undisturbed, for years. The bacteria don't need light. They don't need a food source refill from outside — the wood itself is the food source. They don't need anything from us at all. They just sit there, fermenting slowly, generation after generation, quietly filling an internal chamber with liquid and gas, completely indifferent to whatever's happening in the world outside the bark. Somebody could mow the lawn around that tree every single week for fifteen years and never once suspect that a private, self-sustaining microbial ecosystem is operating a few inches away, sealed inside solid wood. — Foresters have their own folklore around this too, separate from the old "wet-hearted tree" naming I mentioned earlier, and some of it is genuinely unsettling if you sit with it. There are accounts — some documented in forestry incident reports, some passed around as workplace stories among tree crews — of wetwood pockets releasing enough pressurized gas and liquid on impact to knock a chainsaw sideways out of the operator's hands, or to spray fluid several feet, catching a nearby coworker completely off guard. Tree removal is already one of the more dangerous manual trades that exists — statistically it's consistently ranked among the more hazardous occupations — and wetwood is one of those factors that experienced crews specifically train new hires to be aware of, precisely because it's invisible until the exact moment it isn't. Some crews have a rule: if you see that telltale dark wet staining running down bark from an old wound, you treat the cut differently. Different angle. Different bracing. A moment of hesitation most people watching a video would never think to expect from someone who cuts trees for a living every single day. That hesitation, when you see it, is not caution for no reason. It's caution earned from someone else's story about the day their trunk sprayed back. — Let's zoom out for a second and talk about why nature keeps doing this to us — hiding things in plain sight that overturn assumptions we didn't even know we were making. Geodes look like plain gray rocks from the outside and crack open into crystal cathedrals. Certain seemingly solid ice formations conceal air pockets and liquid water inside glacial ice that's been sealed for centuries. Some seeds remain dormant and viable inside dry-looking husks for years, sometimes decades, before conditions trigger germination. Nature is, on some fundamental level, extremely good at packaging surprising internal states inside boring, unremarkable exteriors, because there's rarely an evolutionary or physical reason for the outside of something to accurately advertise what's happening on the inside. A tree trunk covered in bark has absolutely no obligation to tell you what's going on underneath. And most of the time, honestly, there's nothing dramatic going on under there — it really is just solid wood, rings, sapwood doing its normal job. But every so often, under the right combination of an old wound, the right bacteria finding their way in, and years of undisturbed fermentation, you get this. A tree that's secretly been operating as a sealed, pressurized reservoir the entire time, waiting for someone with a saw to finally find out. — A few quick things people always ask once they learn about this, so let's knock them out here. Is the water safe to drink? Historically, some accounts describe it as drinkable in a pinch, but modern guidance is far more cautious — wetwood fluid is loaded with bacteria and fermentation byproducts, and depending on the tree and how advanced the infection is, it can range from relatively clean-tasting to genuinely foul and bacterially loaded. Not something to treat as a reliable water source by modern standards, whatever old logging stories might say. Does it kill the tree? Not necessarily, and that's part of what makes it so strange. Trees can live with wetwood for years, even decades, functioning normally from the outside — leafing out every spring, growing new rings — while quietly carrying an internal pocket the entire time. It's more of a chronic condition than an acute one in most cases, though severe cases can weaken the tree structurally and contribute to internal decay. Can you tell from the outside before cutting? Sometimes, if you know exactly what to look for — that dark staining running from an old wound is the main visible tell. But plenty of wetwood trees show no obvious external sign at all until the moment someone cuts into the wrong spot. — If you made it this far, you now know something about trees that the overwhelming majority of people who scroll past videos like this never bother to learn. You know the name of the phenomenon. You know the bacterial mechanism behind it. You know which species are most prone to it, why old wounds matter, how much pressure can actually build up inside, and why experienced tree crews still treat certain trunks with real caution. That's a strange amount of knowledge to walk away with from what looks, at first glance, like just another oddly satisfying clip. But that's usually how it goes with the genuinely wild stuff nature does — it looks small on the surface, and then you pull one thread and end up somewhere you didn't expect. Go watch it again with all of that in your head this time. Watch the exact frame where the bar breaks through. Watch what the water does the instant it has somewhere to go. Watch the reaction on the person holding the saw — that's not performance, that's genuine surprise from someone who has almost certainly done this exact job a thousand times before and never seen a tree do this. Some trees really are just wood, top to bottom, nothing hiding inside. And then there are the ones that have been quietly running their own private reservoir for twenty or thirty years, sealed under ordinary-looking bark, waiting for exactly one cut to finally let it out. You just watched what that looks like the moment it happens.
0:49

A tree stood in that backyard for probably 40 years. Nobody who walked past it, sat under it, leaned a bike against it, ever knew what was living inside the trunk. Then someone cut into it. And what came out shouldn't be possible. Not sap. Not resin. Water. Gallons of it. Pouring out of solid wood like someone left a hose running inside a living organism. If your first reaction is "that's fake" — I understand. I had the same reaction the first time I saw footage like this. Trees are supposed to be dry on the inside. Bark, wood, rings, maybe some sticky sap if you're unlucky enough to touch a pine. Nobody grows up learning that a tree can be a pressurized tank. But here's the thing nobody tells you in school: some trees are. There's a real, documented, scientifically studied phenomenon behind this, and once you understand it, you will never look at a tree the same way again. I'm going to walk you through exactly what's happening inside these trees, why it happens, which species are famous for it, the wild historical accounts of people discovering it by accident (sometimes violently), and why arborists still get caught off guard by it after decades on the job. Stick with me. This gets stranger the deeper you go. — FIRST: the phenomenon has a name. Arborists and plant pathologists call it "wetwood," and in its more advanced, foul-smelling form, "slime flux." It's not folklore. It's not an urban legend some guy made up on a forum. It's in forestry textbooks, USDA plant pathology bulletins, and arborist training manuals. Here's the mechanism, stripped down to plain English: Trees have a core of heartwood — the dead, structural center of the trunk that no longer transports nutrients. It's basically the tree's skeleton. In most trees, that heartwood is just dry, solid wood. But in certain species, under certain conditions, bacteria colonize that heartwood core. Anaerobic bacteria — the kind that thrive without oxygen — move in and start fermenting the wood tissue from the inside. That fermentation process does two things. First, it draws in and traps enormous amounts of water inside the wood, way beyond what healthy wood would ever hold. Second, it produces gas as a byproduct — methane, carbon dioxide, hydrogen sulfide — and that gas has nowhere to go. It's sealed inside solid wood, inside bark, inside a living, growing tree. So you end up with a chamber, sometimes several feet long, sitting inside the trunk, completely pressurized, completely hidden, holding a mixture of bacteria-laden water and trapped gas — sometimes under enough pressure that when the seal finally breaks, it doesn't drip. It sprays. It gushes. It pours out like the tree itself is bleeding. Now imagine you're an arborist. You've cut down thousands of trees. You know the drill: bark, sapwood, heartwood, done. And then one day your saw breaks through into a hidden pocket you had no way of detecting from the outside, and suddenly you're standing in a puddle that came from inside a tree trunk. That moment is what you're about to see. — Let me give you some numbers, because the scale of this is what makes people stop scrolling. Documented cases of wetwood trees have released water measured in the dozens of gallons from a single cut. Some large elms and cottonwoods have been recorded discharging water continuously for hours after being wounded, with foresters describing "streams" running from the trunk down to the base of the tree and pooling on the ground like a slow leak from a cracked pipe. Certain species are repeat offenders. Elm. Poplar. Cottonwood. Mulberry. Certain oaks. These trees, especially older ones with some history of trunk injury (a old pruning wound, storm damage, a lightning strike, construction damage to the roots), are far more likely to develop internal wetwood pockets, because any breach in the bark is an open door for the bacteria that start this whole process. That's the part that should sit with you for a second. It usually starts with something small. A branch snapped off in a storm. A lawnmower nick at the base. A woodpecker hole. Something that looks like nothing. And over years — sometimes decades — that tiny wound becomes the entry point for a slow-motion transformation happening entirely out of sight, turning part of the tree's interior into a sealed reservoir. You could have one in your own yard right now. You'd have no way of knowing. That's not a scare tactic, that's just how wetwood works — it's invisible from the outside until the tree is cut, cored, drilled, or storm-damaged enough to expose the pocket. — There's an older, uglier cousin of wetwood, and it's called "slime flux," and I promise you the name undersells it. When the pressure inside a wetwood pocket gets high enough, it doesn't wait for someone with a chainsaw. It finds its own way out — through cracks in the bark, through old wounds, through the base of branches. And when that fluid meets open air, the bacteria and yeast in it start reacting with oxygen, and the whole thing turns into a foul, fermenting slurry running down the bark. Old-time foresters called this "flux disease," and some described the smell as somewhere between rotten cabbage and spoiled beer. Insects love it. Certain flies and beetles are specifically drawn to fluxing trees, and some entomologists have documented entire miniature ecosystems living in the wet, fermented bark of a heavily infected wetwood tree. So the version you're about to watch — a clean cut suddenly releasing a rush of water — is actually the tamer version of this phenomenon. It's what happens when the pressure is released fast and deliberately, in a controlled way, instead of slowly seeping and fermenting on the bark for months. It's dramatic, but it's not even the strangest form this condition takes. — Here's where it gets almost unbelievable if you didn't grow up around old-growth forests or work in forestry: this isn't new, and it isn't rare enough to be dismissed as a one-off. Loggers in the 19th and early 20th centuries wrote about "water trees" and "spring trees" — trunks that, when felled or split, would release surprising volumes of water, sometimes described as clean and cold enough that thirsty travelers would drink straight from a freshly cut trunk. Some of these accounts read almost like myth: a felled tree in a dry stretch of forest becoming an impromptu water source for a work crew that had run out of canteens. Indigenous and folk traditions across multiple continents have stories about trees that "cry" or "bleed" water, long before anyone had a bacteriological explanation for it. In parts of the American South, old-timers used to warn newcomers about certain elms and cottonwoods being "wet-hearted," a term passed down generation to generation with no formal science behind it — just observation. They knew, decades before plant pathologists gave it a Latin name, that some trees were different on the inside. There's something almost humbling about that. A phenomenon that sounds like it belongs in a fantasy novel — a tree holding a hidden reservoir inside its trunk — turns out to be something people quietly knew about for centuries, passed down as folk wisdom, and modern science eventually caught up and explained the mechanism. — Let's talk about pressure, because this is the part that turns a "huh, neat" fact into something genuinely dramatic to witness. Wetwood pockets aren't just wet. They're pressurized. Researchers who have studied this by drilling into infected trees and measuring the internal gas pressure have recorded readings significantly above normal atmospheric pressure — high enough that when a probe finally punctures the pocket, gas and liquid don't just seep out, they can audibly hiss, spray, or in some documented cases, forcefully eject material several feet from the trunk. Think about what that means physically. You have a living tree. Roots pulling water up. Leaves doing their thing. Bark looking completely normal, maybe a little bit of old staining near a wound if you know exactly what to look for. And inside, invisible to anyone walking by, there's a sealed chamber behaving less like "wood" and more like a bottle of soda that's been shaken and capped for years. Cut into that with the wrong angle, at the wrong depth, and you are opening something that has been building pressure since before some of you reading this were born. That is not an exaggeration. Some of these wetwood pockets, in old trees with a long history of minor trunk injuries, have been forming and sealing and re-sealing for twenty, thirty, forty years before anyone finally exposes them. — I want to address the skeptics directly, because there's always a version of this that goes semi-viral and the replies fill up with "CGI," "staged," "fake," before anyone bothers to check. This is genuinely, boringly, documented science. Forestry extension offices at multiple universities have publications specifically on wetwood and slime flux — the kind of dry, unglamorous PDF nobody reads unless they're an arborist student cramming for an exam. Plant pathology courses cover it. It's in the same category as things like "trees can produce enough root pressure to push water dozens of feet upward with no pump" — real, measurable, and honestly stranger than most fiction, which is exactly why it keeps going viral every time footage surfaces. The wild part isn't that it's fake. The wild part is that it's real, it's been known for over a century, and most people are hearing about it for the first time through a random video instead of a biology class. — Here's a question worth sitting with: how many trees around you, right now, could be holding something like this? You're not going to know by looking. That's the unsettling part. Wetwood doesn't announce itself from the outside in any reliable way most people would recognize. Sometimes there's a dark wet-looking stain running down the bark from an old wound — that's actually one of the only visible clues, and most people who see it assume it's just water damage or normal bark discoloration, not a sign of a pressurized internal reservoir. Arborists who specialize in tree risk assessment actually have to factor this into their evaluations, because a wetwood pocket can also be a structural weak point — the internal decay associated with it can compromise a tree's strength in ways that aren't visible from a standard visual inspection. So this isn't purely a "huh, cool fact" situation. For professionals, it's something they're trained to watch for, because it changes how a tree behaves, how it should be pruned, and in some cases whether it's even safe to keep standing near a structure. — Let's go species by species for a second, because the "which trees do this" question comes up every single time this kind of footage circulates. Elms are probably the most famous offenders — American elm and Siberian elm both show up repeatedly in wetwood and slime flux case studies. Cottonwoods and poplars are right behind them, especially older specimens with a history of storm damage or pruning wounds. Mulberry trees have a documented tendency toward it as well. Certain oaks can develop it, though it's less common and usually tied to a specific injury history. Willows, with their notoriously soft and moisture-loving wood, are also frequent candidates. What connects almost all of these species isn't some exotic trait — it's actually pretty mundane. They tend to be fast-growing, softer-wooded trees that are more prone to storm damage, cracking, and wound formation over their lifespan, which means more entry points for the bacteria that kick off the entire process. Slower-growing, denser hardwoods are comparatively less prone, though not immune. So if you've got an old elm, cottonwood, poplar, willow, or mulberry anywhere near you — especially one that's taken some damage over the decades, a lost limb, a lightning strike, an old chainsaw wound from a previous trim — there's a real, non-zero chance that tree is sitting on its own hidden reservoir right now, quietly pressurizing, waiting for the day someone finally cuts into the wrong spot. — There's a specific kind of moment that happens on video like this, and if you've watched enough tree-work content you already know it: the split second between the cut going in and the reaction on the face of whoever's holding the saw. That reaction is real. You cannot fake genuine, immediate confusion. Professionals who have done this job for years, who have felled hundreds or thousands of trees, who think they've seen every possible thing a tree trunk can do — and then something happens that their entire career didn't prepare them for. That's the part that makes this kind of footage so different from staged "reaction" content you see everywhere else online. Nobody scripts confusion that specific. Nobody fakes the half-second delay where someone's brain is visibly trying to process what their eyes are showing them. — I'll leave you with this. Every single day, all over the world, people are cutting down trees for completely mundane reasons — storm cleanup, construction, disease removal, firewood, somebody's yard finally getting redone. Thousands of trees. Every day. Most of the time it's exactly as boring as it sounds: cut, drop, haul, done. And then every so often, completely without warning, one of those ordinary trees turns out to be something else entirely. A tree that's been quietly filling itself with water for years, maybe decades, completely undetectable from the outside, sealed shut under bark that looks exactly like every other tree on the block. Nobody plans for that. Nobody sees it coming. That's exactly what makes it worth watching when it happens to be caught on camera. You already scrolled past the video once. Go back and actually watch what happens the second that bar breaks through. You will not believe how much comes out. And once you know why, you'll start looking at every old tree in your neighborhood a little differently. — Let's talk about the pressure numbers again, because I glossed over just how absurd they get in the most extreme documented cases. Standard atmospheric pressure at sea level is about 14.7 pounds per square inch. Some measured wetwood pockets have registered internal gas pressures multiple times higher than that — enough that when researchers insert a hollow probe to sample the gas, it doesn't calmly bubble out, it forces its way through with an audible hiss, sometimes strong enough to make a sound loud enough to hear from several feet away. Now picture that same pressure, except instead of a thin research probe, it's a chainsaw bar plowing straight through the wall of the pocket in one continuous motion. There's no controlled release valve. There's no slow bleed-off. The seal just fails all at once, and whatever's inside — water, gas, fermented bacterial slurry — takes the fastest path out, which is usually straight toward whoever is standing closest. That's not drama for the sake of drama. That's just fluid dynamics doing what fluid dynamics does when a pressurized container gets breached in one violent motion instead of a slow leak. — People love comparing this to other "trees doing things they shouldn't" phenomena, so let's run through a few, because it puts wetwood in context. Root pressure is a real, separately documented thing — some trees, particularly certain maples and grapevines, can generate enough internal pressure through osmosis alone to push water dozens of feet upward through their trunk with zero mechanical pump involved, which is part of why maple syrup tapping works in early spring: cut a hole, and sap doesn't just sit there, it actively flows out under real pressure. Bamboo, meanwhile, has hollow internal chambers between each node that can fill with water and, when punctured, release a surprising rush for something that looks like solid stalk from the outside. Certain cacti and succulents store such enormous internal water reserves that a single barrel cactus can hold multiple gallons, enough that desert survival guides have long described (with real caveats about bitterness and toxicity in some species) cutting into one as an emergency water source. None of those are the exact same mechanism as bacterial wetwood. But they all share the same core surprise: the outside of a plant tells you almost nothing about what's happening on the inside. Trees and plants in general are far better at hiding internal reservoirs, chambers, and pressure systems than most people ever consider, because we're trained from childhood to think of "wood" as uniformly solid and dry. — Here's a question I want you to actually think about instead of just scrolling past: why does this footage hit people so hard emotionally, when it's "just" water? I think it's because it breaks a category we didn't know we had. Somewhere in your brain, without ever being taught it explicitly, you built a rule: solid things don't have hidden liquid interiors. Rocks are solid. Wood is solid. A tree trunk, no matter how big, is filed under "solid object" right next to a brick or a fence post. So when a tree trunk suddenly behaves like a punctured water balloon, it's not just surprising — it's a small, harmless violation of a rule you didn't know you were relying on. That's the exact same psychological mechanism behind why people can't look away from videos of hidden compartments, false walls, geodes cracked open to reveal crystal interiors, or ice cores pulled from glaciers showing air bubbles thousands of years old. The object looked like one thing on the outside and turned out to be something completely different on the inside. Our brains are wired to lock onto that specific kind of surprise and replay it. — I want to walk through what's actually happening at a microscopic level too, because the bacteria part is honestly the wildest piece of this whole story and it usually gets skipped over. The bacteria responsible for wetwood are largely anaerobic — meaning they thrive specifically in environments with no oxygen, which describes the sealed interior of a heartwood pocket perfectly. Species commonly implicated include various strains that also show up in other low-oxygen fermentation processes elsewhere in nature. These bacteria essentially treat the interior of the tree the way yeast treats a sealed fermentation vessel: they break down wood sugars and cellulose components, and as a byproduct of that metabolic process, they release gas. Methane. Carbon dioxide. Sometimes hydrogen sulfide, which is the compound responsible for the "rotten egg" smell associated with some of the worst slime flux cases. Here's the part that should genuinely unsettle you a little: this process can continue, essentially undisturbed, for years. The bacteria don't need light. They don't need a food source refill from outside — the wood itself is the food source. They don't need anything from us at all. They just sit there, fermenting slowly, generation after generation, quietly filling an internal chamber with liquid and gas, completely indifferent to whatever's happening in the world outside the bark. Somebody could mow the lawn around that tree every single week for fifteen years and never once suspect that a private, self-sustaining microbial ecosystem is operating a few inches away, sealed inside solid wood. — Foresters have their own folklore around this too, separate from the old "wet-hearted tree" naming I mentioned earlier, and some of it is genuinely unsettling if you sit with it. There are accounts — some documented in forestry incident reports, some passed around as workplace stories among tree crews — of wetwood pockets releasing enough pressurized gas and liquid on impact to knock a chainsaw sideways out of the operator's hands, or to spray fluid several feet, catching a nearby coworker completely off guard. Tree removal is already one of the more dangerous manual trades that exists — statistically it's consistently ranked among the more hazardous occupations — and wetwood is one of those factors that experienced crews specifically train new hires to be aware of, precisely because it's invisible until the exact moment it isn't. Some crews have a rule: if you see that telltale dark wet staining running down bark from an old wound, you treat the cut differently. Different angle. Different bracing. A moment of hesitation most people watching a video would never think to expect from someone who cuts trees for a living every single day. That hesitation, when you see it, is not caution for no reason. It's caution earned from someone else's story about the day their trunk sprayed back. — Let's zoom out for a second and talk about why nature keeps doing this to us — hiding things in plain sight that overturn assumptions we didn't even know we were making. Geodes look like plain gray rocks from the outside and crack open into crystal cathedrals. Certain seemingly solid ice formations conceal air pockets and liquid water inside glacial ice that's been sealed for centuries. Some seeds remain dormant and viable inside dry-looking husks for years, sometimes decades, before conditions trigger germination. Nature is, on some fundamental level, extremely good at packaging surprising internal states inside boring, unremarkable exteriors, because there's rarely an evolutionary or physical reason for the outside of something to accurately advertise what's happening on the inside. A tree trunk covered in bark has absolutely no obligation to tell you what's going on underneath. And most of the time, honestly, there's nothing dramatic going on under there — it really is just solid wood, rings, sapwood doing its normal job. But every so often, under the right combination of an old wound, the right bacteria finding their way in, and years of undisturbed fermentation, you get this. A tree that's secretly been operating as a sealed, pressurized reservoir the entire time, waiting for someone with a saw to finally find out. — A few quick things people always ask once they learn about this, so let's knock them out here. Is the water safe to drink? Historically, some accounts describe it as drinkable in a pinch, but modern guidance is far more cautious — wetwood fluid is loaded with bacteria and fermentation byproducts, and depending on the tree and how advanced the infection is, it can range from relatively clean-tasting to genuinely foul and bacterially loaded. Not something to treat as a reliable water source by modern standards, whatever old logging stories might say. Does it kill the tree? Not necessarily, and that's part of what makes it so strange. Trees can live with wetwood for years, even decades, functioning normally from the outside — leafing out every spring, growing new rings — while quietly carrying an internal pocket the entire time. It's more of a chronic condition than an acute one in most cases, though severe cases can weaken the tree structurally and contribute to internal decay. Can you tell from the outside before cutting? Sometimes, if you know exactly what to look for — that dark staining running from an old wound is the main visible tell. But plenty of wetwood trees show no obvious external sign at all until the moment someone cuts into the wrong spot. — If you made it this far, you now know something about trees that the overwhelming majority of people who scroll past videos like this never bother to learn. You know the name of the phenomenon. You know the bacterial mechanism behind it. You know which species are most prone to it, why old wounds matter, how much pressure can actually build up inside, and why experienced tree crews still treat certain trunks with real caution. That's a strange amount of knowledge to walk away with from what looks, at first glance, like just another oddly satisfying clip. But that's usually how it goes with the genuinely wild stuff nature does — it looks small on the surface, and then you pull one thread and end up somewhere you didn't expect. Go watch it again with all of that in your head this time. Watch the exact frame where the bar breaks through. Watch what the water does the instant it has somewhere to go. Watch the reaction on the person holding the saw — that's not performance, that's genuine surprise from someone who has almost certainly done this exact job a thousand times before and never seen a tree do this. Some trees really are just wood, top to bottom, nothing hiding inside. And then there are the ones that have been quietly running their own private reservoir for twenty or thirty years, sealed under ordinary-looking bark, waiting for exactly one cut to finally let it out. You just watched what that looks like the moment it happens.

Earth Unveiled

125,018 görüntüleme • 27 gün önce

How to Build a Proper Product Page It breaks my heart every time I see someone from Brazil, making just $200 a month, spend $40 on a test ad only to get a $2 CPC. Then, they cut the ad at $35 spend with 17 clicks and 0 conversions. What’s even more frustrating is when I visit their site and see it’s a complete mess. It’s like they didn’t even try. That’s why I’m making this post. *Disclaimer: If you're building a brand, this isn’t for you. This is for testing products correctly with a website that’s good enough to convert, but if you’re serious about your brand, hire a Figma designer and a developer to get things done right. As a fun fact, I tested the following product myself (In the video below) and with just one click at a $3 CPC, I got a sale with an $80 AOV (100% CVR). I paused the ads because the CPMs hit $150. If you're interested, save this product for the future. I'll share the creatives i used to ran the product with those who comment below. "jordan, stop teaching high school kids about selling reps and getting them sued by Prada or other big brands, ruining their payment gateways, and crushing their dreams." (with 5 random people only will do it, wouldn't make sense for everyone to be ripping it). Shoutout to Adrian for this one. 🫡 Back to the important stuff: Let’s talk about creating a great product page. First off, ditch the “Buy Now” button. By using this, you miss out on the chance to increase your Average Order Value (AOV) through upsells during checkout. Instead, replace it with an “Add to Cart” button. Also, remove the quantity selector. Hardly anyone uses them on the product page, but they do in the cart. Instead, offer bundles, which you can set up using the Kaching Bundles app or your theme if it supports this feature. The cart experience is crucial, and you can optimize it using the UpCart app. Enable all its product page features so it takes over the standard Shopify cart or your theme’s cart. The built-in cart systems are outdated—they don’t allow upsells like UpCart does. Plus, UpCart directly opens the cart after a product is added, where the upsell option appears at the bottom, increasing your chances of boosting AOV. Pay attention to color schemes. Don’t use neutral colors for headers and buttons if your product features a primary color. A yellow jacket with a black header is like pizza with raspberry syrup—just doesn’t work. If your product images are gray, white, or black, match those with your headers and buttons. Otherwise, play around with colors to give your page some dynamic appeal. Bookmark this site to get color palettes that match your primary color. For exact color matches, download the "ColorZilla" extension, which gives you the exact color code of whatever is under your mouse on the screen. If your product color is #6E402A, you’ll know it and can match it perfectly with your header and buttons, creating a visually appealing contrast like Cider did here below. Right now, when some of you send me these websites, they look like government pages from the early 2000s. Next, consider the typography and button styles. For fonts, use Helvetica Regular for body text and Helvetica Bold for titles, both at a minimum size of 100%. It’s simple and effective. As for buttons, they should have a corner radius of 8px. To change these settings, go to the theme settings - typography/buttons and adjust the buttons and typography accordingly. Rounded buttons create a modern, inviting feel, while full square buttons can give off an outdated vibe. Even casinos in Vegas design their buildings with curves, ensuring that visitors always have a view angle that draws them back in—it’s all about keeping things appealing and engaging. Finally, the product page layout itself should be clean and concise. Use collapsible rows for your product descriptions. No one wants to read a novel, so keep it compact and focused. Images and videos are what sell—this is why we don’t use text-heavy images in our ads; they just bore people. Keep the description short, with enough information to inform but not overwhelm. If you need to include more features, put them in the FAQs section—that’s what they’re for. The goal is to make sure that the "Add to Cart" button is visible as soon as possible once the customer lands on the product page, without overwhelming them but providing just enough information—some key benefits, high-quality images, and buying options in the bundles. Once they hit the cart, the upsells will do their job. Remember, the three essential apps for setting this up are Loox Reviews for customer feedback (use the product widget reviews at the bottom of the page before the FAQs and the rating widget just above the title), Kaching Bundles for offering package deals, and UpCart for optimizing the cart experience. Just for the record, this is to help newcomers and guide them to something taht works, me personally i don't use free themes, but this one i created could convert easily if the product, offer and ads match well. Good luck and keep testing! 🗳🥂💸🤑
0:23

How to Build a Proper Product Page It breaks my heart every time I see someone from Brazil, making just $200 a month, spend $40 on a test ad only to get a $2 CPC. Then, they cut the ad at $35 spend with 17 clicks and 0 conversions. What’s even more frustrating is when I visit their site and see it’s a complete mess. It’s like they didn’t even try. That’s why I’m making this post. *Disclaimer: If you're building a brand, this isn’t for you. This is for testing products correctly with a website that’s good enough to convert, but if you’re serious about your brand, hire a Figma designer and a developer to get things done right. As a fun fact, I tested the following product myself (In the video below) and with just one click at a $3 CPC, I got a sale with an $80 AOV (100% CVR). I paused the ads because the CPMs hit $150. If you're interested, save this product for the future. I'll share the creatives i used to ran the product with those who comment below. "jordan, stop teaching high school kids about selling reps and getting them sued by Prada or other big brands, ruining their payment gateways, and crushing their dreams." (with 5 random people only will do it, wouldn't make sense for everyone to be ripping it). Shoutout to Adrian for this one. 🫡 Back to the important stuff: Let’s talk about creating a great product page. First off, ditch the “Buy Now” button. By using this, you miss out on the chance to increase your Average Order Value (AOV) through upsells during checkout. Instead, replace it with an “Add to Cart” button. Also, remove the quantity selector. Hardly anyone uses them on the product page, but they do in the cart. Instead, offer bundles, which you can set up using the Kaching Bundles app or your theme if it supports this feature. The cart experience is crucial, and you can optimize it using the UpCart app. Enable all its product page features so it takes over the standard Shopify cart or your theme’s cart. The built-in cart systems are outdated—they don’t allow upsells like UpCart does. Plus, UpCart directly opens the cart after a product is added, where the upsell option appears at the bottom, increasing your chances of boosting AOV. Pay attention to color schemes. Don’t use neutral colors for headers and buttons if your product features a primary color. A yellow jacket with a black header is like pizza with raspberry syrup—just doesn’t work. If your product images are gray, white, or black, match those with your headers and buttons. Otherwise, play around with colors to give your page some dynamic appeal. Bookmark this site to get color palettes that match your primary color. For exact color matches, download the "ColorZilla" extension, which gives you the exact color code of whatever is under your mouse on the screen. If your product color is #6E402A, you’ll know it and can match it perfectly with your header and buttons, creating a visually appealing contrast like Cider did here below. Right now, when some of you send me these websites, they look like government pages from the early 2000s. Next, consider the typography and button styles. For fonts, use Helvetica Regular for body text and Helvetica Bold for titles, both at a minimum size of 100%. It’s simple and effective. As for buttons, they should have a corner radius of 8px. To change these settings, go to the theme settings - typography/buttons and adjust the buttons and typography accordingly. Rounded buttons create a modern, inviting feel, while full square buttons can give off an outdated vibe. Even casinos in Vegas design their buildings with curves, ensuring that visitors always have a view angle that draws them back in—it’s all about keeping things appealing and engaging. Finally, the product page layout itself should be clean and concise. Use collapsible rows for your product descriptions. No one wants to read a novel, so keep it compact and focused. Images and videos are what sell—this is why we don’t use text-heavy images in our ads; they just bore people. Keep the description short, with enough information to inform but not overwhelm. If you need to include more features, put them in the FAQs section—that’s what they’re for. The goal is to make sure that the "Add to Cart" button is visible as soon as possible once the customer lands on the product page, without overwhelming them but providing just enough information—some key benefits, high-quality images, and buying options in the bundles. Once they hit the cart, the upsells will do their job. Remember, the three essential apps for setting this up are Loox Reviews for customer feedback (use the product widget reviews at the bottom of the page before the FAQs and the rating widget just above the title), Kaching Bundles for offering package deals, and UpCart for optimizing the cart experience. Just for the record, this is to help newcomers and guide them to something taht works, me personally i don't use free themes, but this one i created could convert easily if the product, offer and ads match well. Good luck and keep testing! 🗳🥂💸🤑

Zzzz

42,318 görüntüleme • 2 yıl önce

I've built a multiplayer survival game for the browser in 30 days and I didnt write a single line of code 🤯 So I'd like to write my notes about it once the deadline is done now. The last 20% of a project is indeed the hardest part of it all. In the last 2 days i've been working on the final version of Hollowlands for @levelsio's 2026 #vibejam I worked a lot! I fixed a lot of bugs, tested a lot playing with my wife. Fixed more bugs... But now, thank God, I have the final result! The game looks good, yes. I've spent half of the jam just tweaking every single detail of the procedural world generation. And It was worth it! The game still runs well on most devices and still has less than 20MB in size. Which is pretty impressive to me. The process of building was very straighforward: 1. I used Three.js + React to create the game. Before I started I created a huge document defining every rule i'd like the codebase to be implemented upon. It had clean code rules, archtecture decisions, ECS principles (good for games), and so on. This helped a lot constrain the AI to maintain the code maintainable and separated into clear domains (systems). This document was made partially by me given my previous experience building web games (I've made a lot of mistakes in the past and made sure they will not repeat again) and partially AI suggesting best practices. 2. For every feature I prompted the AI, I was very specific on details that I'd like implemented. If I knew what I was doing, I was more specific on the "how" I wanted to be done. If I didnt know what was doing I first asked the AI to brainstorm possibilities with me, based on industry standards, pros and cons, and so on. Then I would decide what path to go. 3. Every single feature I used Leva for tweaking the values. So for example, the size of the trees, colors, distance between objects, animation speed, etc. Everything I have a slider that I can adjust. 4. To make the game look good I used Tripo to create the models. To be honest it's not 100% perfect. If you check the character in game you can notice a few issues here and there (the arms lol), but I believe that it will keep getting better over time. 1 Year ago I tried and it wasnt even close to what it's now. Then I used a few post-processing + shaders + particles techniques to bring the "wow" factor. 5. I did only 1 feature at a time. And every change it was a commit with a clear message of what was done. This helped the AI fetch previous commit to understand what changed and know exactly what happened in the past. If I opened multiple terminals at once and blasted prompts the code and commit history would be a mess in a few days. And for every change the AI did, I asked it to do a Code Review of everything that was changed and look for violations on the document I wrote in the beggining defining the codebase guidelines. I realized that I pretty much applied software engineer principles using AI: Code, review and merge, code, review and merge... 6. On the last week I implemented the multiplayer using Colyseus ⚔️ which was pretty nice. I used AI to fetch the whole documentation and create a skill.md file that helped a lot. The creator of the framework Endel also did a extensive research on how real multiplayer games are implemented. It's open source and it was a gold mine for the AI to come up with the implementation for my game. You can ask him the link :) And that was it I think. I'm extremely tired now. The last 2 days was insane. The game's final version is not what I had in mind in the beginning of the jam. I had to cut a lot of cool features. But given the 30 days deadline I think it was a huge success. Hands down my best game ever made. Now I'll take a few days to rest and come back with more updates on the game. Maybe it can become a big deal in the future with more updates. Who knows. And in the event I win first place in this game jam, I'll use the money to fund my own game studio + cover the expenses of my child that is going to be born in September :) Cheers guys! If you have any question, feel free to reach out. I'll answer every non-bot comment in here haha Note: The link to play is in my profile
1:06

I've built a multiplayer survival game for the browser in 30 days and I didnt write a single line of code 🤯 So I'd like to write my notes about it once the deadline is done now. The last 20% of a project is indeed the hardest part of it all. In the last 2 days i've been working on the final version of Hollowlands for @levelsio's 2026 #vibejam I worked a lot! I fixed a lot of bugs, tested a lot playing with my wife. Fixed more bugs... But now, thank God, I have the final result! The game looks good, yes. I've spent half of the jam just tweaking every single detail of the procedural world generation. And It was worth it! The game still runs well on most devices and still has less than 20MB in size. Which is pretty impressive to me. The process of building was very straighforward: 1. I used Three.js + React to create the game. Before I started I created a huge document defining every rule i'd like the codebase to be implemented upon. It had clean code rules, archtecture decisions, ECS principles (good for games), and so on. This helped a lot constrain the AI to maintain the code maintainable and separated into clear domains (systems). This document was made partially by me given my previous experience building web games (I've made a lot of mistakes in the past and made sure they will not repeat again) and partially AI suggesting best practices. 2. For every feature I prompted the AI, I was very specific on details that I'd like implemented. If I knew what I was doing, I was more specific on the "how" I wanted to be done. If I didnt know what was doing I first asked the AI to brainstorm possibilities with me, based on industry standards, pros and cons, and so on. Then I would decide what path to go. 3. Every single feature I used Leva for tweaking the values. So for example, the size of the trees, colors, distance between objects, animation speed, etc. Everything I have a slider that I can adjust. 4. To make the game look good I used Tripo to create the models. To be honest it's not 100% perfect. If you check the character in game you can notice a few issues here and there (the arms lol), but I believe that it will keep getting better over time. 1 Year ago I tried and it wasnt even close to what it's now. Then I used a few post-processing + shaders + particles techniques to bring the "wow" factor. 5. I did only 1 feature at a time. And every change it was a commit with a clear message of what was done. This helped the AI fetch previous commit to understand what changed and know exactly what happened in the past. If I opened multiple terminals at once and blasted prompts the code and commit history would be a mess in a few days. And for every change the AI did, I asked it to do a Code Review of everything that was changed and look for violations on the document I wrote in the beggining defining the codebase guidelines. I realized that I pretty much applied software engineer principles using AI: Code, review and merge, code, review and merge... 6. On the last week I implemented the multiplayer using Colyseus ⚔️ which was pretty nice. I used AI to fetch the whole documentation and create a skill.md file that helped a lot. The creator of the framework Endel also did a extensive research on how real multiplayer games are implemented. It's open source and it was a gold mine for the AI to come up with the implementation for my game. You can ask him the link :) And that was it I think. I'm extremely tired now. The last 2 days was insane. The game's final version is not what I had in mind in the beginning of the jam. I had to cut a lot of cool features. But given the 30 days deadline I think it was a huge success. Hands down my best game ever made. Now I'll take a few days to rest and come back with more updates on the game. Maybe it can become a big deal in the future with more updates. Who knows. And in the event I win first place in this game jam, I'll use the money to fund my own game studio + cover the expenses of my child that is going to be born in September :) Cheers guys! If you have any question, feel free to reach out. I'll answer every non-bot comment in here haha Note: The link to play is in my profile

André → andreelias.dev

18,190 görüntüleme • 5 ay önce