正在加载视频...

视频加载失败

返回首页

WIP update on my PCG Geometry Decals 👇 • UV mapping • Vertex displacement • Normals • Static mesh baking (Editor Utility) • Landscape‑conforming stamping Would you use this workflow in production? #UnrealEngine #PCG #ProceduralContentGeneration

WWeynants's profile picture

Wouter Weynants

1,707 subscribers

13,972 次观看 • 1 年前 •via X (Twitter)

#UnrealEngine#PCG#ProceduralContentGeneration
LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

Environment and Prop Artist Christopher Wallace wanted to see just how far this Tram model could go without having unique UVs and bakes 🚊 This meant Christopher had to rely on vertex painting and a tileable/trim workflow with weighted normals. In addition, he created 8 shaders for the asset and some grungey decals for that authentic streetcar-in-use feel. Hop on board over on ArtStation to see more of the asset and the larger project it comes from, Neon Point:
0:35

Environment and Prop Artist Christopher Wallace wanted to see just how far this Tram model could go without having unique UVs and bakes 🚊 This meant Christopher had to rely on vertex painting and a tileable/trim workflow with weighted normals. In addition, he created 8 shaders for the asset and some grungey decals for that authentic streetcar-in-use feel. Hop on board over on ArtStation to see more of the asset and the larger project it comes from, Neon Point:

Unreal Engine

14,402 次观看 • 1 年前

In the final stages of testing my Blender Compositor Line Art addon before release. Here's a look at how it works on a very high detail character. We have lines based on toon shading and vertex color ID groups. You can see it works very cleanly in some areas, but then runs into issues in others. That is because this mesh is complex but doesn't have smoothed normals yet, which causes the toon shading to create very small shaded areas that become lines. (We'll see it with Smoothed Normals next update.) This is the double-edged sword of this method, and any other Screen Space Extraction method, including the new Raycast Node: they are extremely precise, which allows very high detail and fine control, but also means you need to guard against bad inputs. But my toolset gives you full control over what data you create lines from, so you can ensure clean ID groups, run lines on different Normals than you shade with, mask at any stage, or anything else you need! And of course, most line methods (especially Inverted Hull) completely fail on complex or dirty geometry.
0:59

In the final stages of testing my Blender Compositor Line Art addon before release. Here's a look at how it works on a very high detail character. We have lines based on toon shading and vertex color ID groups. You can see it works very cleanly in some areas, but then runs into issues in others. That is because this mesh is complex but doesn't have smoothed normals yet, which causes the toon shading to create very small shaded areas that become lines. (We'll see it with Smoothed Normals next update.) This is the double-edged sword of this method, and any other Screen Space Extraction method, including the new Raycast Node: they are extremely precise, which allows very high detail and fine control, but also means you need to guard against bad inputs. But my toolset gives you full control over what data you create lines from, so you can ensure clean ID groups, run lines on different Normals than you shade with, mask at any stage, or anything else you need! And of course, most line methods (especially Inverted Hull) completely fail on complex or dirty geometry.

aVersionOfReality

17,063 次观看 • 5 个月前

🧑‍🏫 How to make a glass/refraction shader: 🍷 Refraction will ultimately have the effect that whatever is behind your mesh should appear distorted by the surface of the mesh itself. We're not going for external caustics projection, just modelling glass-like, distorting "transparency". 🌆 In Unity, you can sample the *global* _CameraOpaqueTexture (make sure it's enabled in your URP asset settings), which is what your scene looks like rendered without any transparent objects. In Shader Graph, you can simply use the Scene Colour node. 🔢 The UVs required for this texture are the normalized screen coordinates, so if we offset/warp/distort these coordinates and sample the texture, we ultimately produce a distorted image. We can offset the UVs by some normal map, as well as a refraction vector based on the direction from the camera -> the vertex/fragment (flip viewDir, which is otherwise vertex/fragment -> camera) and normals of the object. 📸 Input the (reversed) world space view direction and normal into HLSL refract. **Convert the refraction direction vector to tangent space before adding it to the screen UV.** Use the result to sample _CameraOpaqueTexture. refract(-worldViewDirection, worldNormal, eta); eta -> refraction ratio (from_IOR / to_IOR), > for air, 1.0 / indexOfRefraction (IOR). IOR of water = 1.33, glass = 1.54... 💡 You can also do naive "looks about right" hacks: fresnel -> normal from grayscale, which can be used for distortion. Or distort it any other way (without even specifically using refract at all), really... 🧠 Thus, even if your object is rendered as a transparent type (and vanilla Unity URP will require that it is), it is fully 'opaque' (max alpha), but it renders on its surface what is behind it, using the screen UV. If you distort those UVs by the camera view and normals of the surface it will be rendered on, it then appears like refractive glass on that surface. > Transparent render queue, but alpha = 1.0.
0:39

🧑‍🏫 How to make a glass/refraction shader: 🍷 Refraction will ultimately have the effect that whatever is behind your mesh should appear distorted by the surface of the mesh itself. We're not going for external caustics projection, just modelling glass-like, distorting "transparency". 🌆 In Unity, you can sample the *global* _CameraOpaqueTexture (make sure it's enabled in your URP asset settings), which is what your scene looks like rendered without any transparent objects. In Shader Graph, you can simply use the Scene Colour node. 🔢 The UVs required for this texture are the normalized screen coordinates, so if we offset/warp/distort these coordinates and sample the texture, we ultimately produce a distorted image. We can offset the UVs by some normal map, as well as a refraction vector based on the direction from the camera -> the vertex/fragment (flip viewDir, which is otherwise vertex/fragment -> camera) and normals of the object. 📸 Input the (reversed) world space view direction and normal into HLSL refract. **Convert the refraction direction vector to tangent space before adding it to the screen UV.** Use the result to sample _CameraOpaqueTexture. refract(-worldViewDirection, worldNormal, eta); eta -> refraction ratio (from_IOR / to_IOR), > for air, 1.0 / indexOfRefraction (IOR). IOR of water = 1.33, glass = 1.54... 💡 You can also do naive "looks about right" hacks: fresnel -> normal from grayscale, which can be used for distortion. Or distort it any other way (without even specifically using refract at all), really... 🧠 Thus, even if your object is rendered as a transparent type (and vanilla Unity URP will require that it is), it is fully 'opaque' (max alpha), but it renders on its surface what is behind it, using the screen UV. If you distort those UVs by the camera view and normals of the surface it will be rendered on, it then appears like refractive glass on that surface. > Transparent render queue, but alpha = 1.0.

Mirza Beig

125,253 次观看 • 1 年前

Here is the Geometry Nodes Weighted Normals with Laplacian Blur on a full character (a vroid). It easily improves the shading even on game topology with almost no setup. I built this as part of my quest to improve real time toon shading. 3D anime models are popular, but use of dynamic light is rare even among high quality vtuber models. This is for several reasons, but a big one is simply that it takes a lot of Custom Normals work to make 3D cel shading not look like a jagged mess (other pieces of the puzzle are issues like deformations, multiple lights, etc). And fixing Normals is tedious, especially on existing game topology. I have focused on proxy meshes for priority areas like character faces, but they aren't an efficient solution for the whole body + outfit. I wanted something I could just throw on any model and make it at least not a jagged mess anymore even if it wasn't perfect. As you can see from this clip, this does that very well! And vertex groups can be used to control the style of the effect and power. It still can't smooth beyond what the topology density can support, but the topo itself is no longer a problem (for higher res, could be run on a subdivided version of the model and then baked to a Normal Map.) The only changes I made to this model were adding a weld modifier to merge split edges during interpolation, and a vertex group to select the skirt. I have not yet added full handling and logic for detecting edges with big angles like the skirt, or for handling boundaries like on the hair, so both those areas can get better too. You can also see that while it successfully smooths out the Face, it isn't really stylistically correct there. That is still best done with a proxy mesh to define a new shape. This is part of the tools I am working on for Fondant. We are putting together a Blender Addon to release this + a proxy mesh tool for the face, and are working on resolving other problems in-engine to fully bring dynamic light to real time 3D toon shading. Give us a follow, and send them a DM if you are interested in testing these tools as they develop!
2:17

Here is the Geometry Nodes Weighted Normals with Laplacian Blur on a full character (a vroid). It easily improves the shading even on game topology with almost no setup. I built this as part of my quest to improve real time toon shading. 3D anime models are popular, but use of dynamic light is rare even among high quality vtuber models. This is for several reasons, but a big one is simply that it takes a lot of Custom Normals work to make 3D cel shading not look like a jagged mess (other pieces of the puzzle are issues like deformations, multiple lights, etc). And fixing Normals is tedious, especially on existing game topology. I have focused on proxy meshes for priority areas like character faces, but they aren't an efficient solution for the whole body + outfit. I wanted something I could just throw on any model and make it at least not a jagged mess anymore even if it wasn't perfect. As you can see from this clip, this does that very well! And vertex groups can be used to control the style of the effect and power. It still can't smooth beyond what the topology density can support, but the topo itself is no longer a problem (for higher res, could be run on a subdivided version of the model and then baked to a Normal Map.) The only changes I made to this model were adding a weld modifier to merge split edges during interpolation, and a vertex group to select the skirt. I have not yet added full handling and logic for detecting edges with big angles like the skirt, or for handling boundaries like on the hair, so both those areas can get better too. You can also see that while it successfully smooths out the Face, it isn't really stylistically correct there. That is still best done with a proxy mesh to define a new shape. This is part of the tools I am working on for Fondant. We are putting together a Blender Addon to release this + a proxy mesh tool for the face, and are working on resolving other problems in-engine to fully bring dynamic light to real time 3D toon shading. Give us a follow, and send them a DM if you are interested in testing these tools as they develop!

aVersionOfReality

14,904 次观看 • 1 年前

Most people building in n8n are sitting on way more potential than they realize. You don’t need another backend workflow. You need a front-end that makes it usable. This week I built a micro-app in Bolt that does exactly that. Drop in a TikTok keyword, hit go - and behind the scenes, it: - scrapes trending videos - pulls pain points, emotional triggers, hooks - rewrites the script to pitch your product - pipes it all back into the UI, ready to use this approach has me thinking less like "how do i build a workflow" and more like "what micro-app would actually be useful to me or my team?" feels like the missing piece between powerful automations and actual utility. if you're building in n8n and not playing with custom UIs yet... you're sleeping. drop a comment if you want a walkthrough of how I built this, including the prompts I used to code the whole thing - I’ll record it ASAP.
5:41

Most people building in n8n are sitting on way more potential than they realize. You don’t need another backend workflow. You need a front-end that makes it usable. This week I built a micro-app in Bolt that does exactly that. Drop in a TikTok keyword, hit go - and behind the scenes, it: - scrapes trending videos - pulls pain points, emotional triggers, hooks - rewrites the script to pitch your product - pipes it all back into the UI, ready to use this approach has me thinking less like "how do i build a workflow" and more like "what micro-app would actually be useful to me or my team?" feels like the missing piece between powerful automations and actual utility. if you're building in n8n and not playing with custom UIs yet... you're sleeping. drop a comment if you want a walkthrough of how I built this, including the prompts I used to code the whole thing - I’ll record it ASAP.

J.B.

97,429 次观看 • 1 年前

VoiceBox just did what everyone thought was impossible. It might have killed ElevenLabs overnight. No subscription. No cloud. No credits. Runs locally on your machine. Clones a voice from 3 seconds of audio. Powered by Qwen 3 TTS. Apache 2.0 license. Commercial use allowed. And your voice data never leaves your computer. For years, if you wanted high quality voice cloning, ElevenLabs was the default. Now there’s a free open-source alternative that sounds shockingly close. Plus it has a built-in multi-track editor, recording, transcription with Whisper, and a local API. This isn’t just another TTS tool. It’s a full voice production studio on your desktop. Open source AI is catching up fast. And this changes the game for creators and businesses. Would you trust the cloud with your voice… or keep it local? 👇
8:20

VoiceBox just did what everyone thought was impossible. It might have killed ElevenLabs overnight. No subscription. No cloud. No credits. Runs locally on your machine. Clones a voice from 3 seconds of audio. Powered by Qwen 3 TTS. Apache 2.0 license. Commercial use allowed. And your voice data never leaves your computer. For years, if you wanted high quality voice cloning, ElevenLabs was the default. Now there’s a free open-source alternative that sounds shockingly close. Plus it has a built-in multi-track editor, recording, transcription with Whisper, and a local API. This isn’t just another TTS tool. It’s a full voice production studio on your desktop. Open source AI is catching up fast. And this changes the game for creators and businesses. Would you trust the cloud with your voice… or keep it local? 👇

Julian Goldie SEO

59,167 次观看 • 7 个月前

"If Any Doctor Tells You To Stay Out Of The Sun...You Should Fire That Doctor Immediately." Dr Tel Oren, MD "The Sun Is Crucial For Our Health & You Should Never Use Chemical Sunscreen If You Want To Be Healthy." "The Sun Does Not Create Melanoma, It Protects Us From Melanoma." Over 90% of Melanoma Skin Cancer occurs on parts of the body NOT exposed to the healing benefits of the sun. Less than 10% of Melanoma occurs on the face & a majority of those occur on people who use facial SPF lotions/makeup everyday, creating a barrier that inhibits the sun's protective melanin benefits. Additionally, the SPF chemicals are carcinogens. The Entire Spectrum Of Light Is Necessary Including UV. Every Cell Communicates To Every Other Cell Through Light. Our Cells Require Sunlight. UVB Is Actually Essential & Using Sunscreen Is Sabotaging Your Health. Sunscreen & sunglasses block UV Rays of the sun that are supposed to enter the eyes & skin for melanin production. Cholesterol, Vitamin D & Melanin production all work together to keep the natural skin barrier healthy & cancer free. Cholesterol level above 200 mg/dL plus Vitamin D3 level above 50 ng/ml protects against all cancer including melanoma. Skin cancer is a reflection of skin that is already sick & corrupted from years of consuming seed oils. Industrial seed oils cause our skin to oxidize, causing inflammation & cell dysregulation. The rise of skin cancer directly coincides with the 328% rise in dietary seed oil consumption within the diet since the 1940s. Seed oils damage our skin from the inside out & melanoma is the terrible consequence of Big Food lying to us about industrial seed oils being healthy. Sun Exposure Is Crucial & Required For Vibrant Health: Optimal Vitamin D (with cholesterol foods in the diet) Stroke Prevention Cancer Prevention Heart Attack Prevention Bone Health Immune System Health Depression Prevention Natural Appetite Suppressant Natural Blood Sugar/Insulin Control Mood Enhancer Hair Keratin Production Naturally Lowers Blood Pressure Optimal Libido & Hormone Production Muscle Health & Injury Prevention The Dangers Of Chemical Sunscreens: Sunscreen Chemicals Reach 14X The FDA Limit In The Bloodstream After Only 1 Day Of Use. Sunscreens Do Not Prevent Cancer, They Cause It. These Chemicals Put A Toxic Load Onto Your Liver & Kidneys Causing Illness & Disease. OXYBENZONE: FDA’s 2020 study, it has been found in blood samples at levels 16 times above the FDA safety threshold. A powerful endocrine disruptor causing lower testosterone in males & causes increased breast cancer & endometriosis in females. OCTOCRYLENE: Readily absorbs through the skin at levels 14 times the FDA’s cutoff for systemic exposure. It is often contaminated with benzophenone, which is a known carcinogen. AVOBENZONE: Testing has revealed bloodstream levels 9 times above the FDA legal limit. Avobenzone disrupts the endocrine system & has been shown to block testosterone. ESCAMSULE: Also known as Mexoryl on ingredient labels, is a powerful endocrine disruptor. Adverse effects include elevation of hepatic liver enzymes, anemia & skin eruptions. When a natural protective barrier is needed for children or extended activities for hours & hours of direct sun exposure, use a safe grass fed beef tallow with the mineral zinc oxide as a protectant. Let me know if you would like a referral to the grass fed tallow skin care products my family & I use for all skincare. 👇Melanoma Is Not Caused By Sunlight👇 👇Vitamin D Deficiency & Chronic Disease👇 👇Sunscreen Toxic In Bloodstream Clinical Trial👇 Speaker: Dr Adiel Tel Oren, MD Video: WR
1:16

"If Any Doctor Tells You To Stay Out Of The Sun...You Should Fire That Doctor Immediately." Dr Tel Oren, MD "The Sun Is Crucial For Our Health & You Should Never Use Chemical Sunscreen If You Want To Be Healthy." "The Sun Does Not Create Melanoma, It Protects Us From Melanoma." Over 90% of Melanoma Skin Cancer occurs on parts of the body NOT exposed to the healing benefits of the sun. Less than 10% of Melanoma occurs on the face & a majority of those occur on people who use facial SPF lotions/makeup everyday, creating a barrier that inhibits the sun's protective melanin benefits. Additionally, the SPF chemicals are carcinogens. The Entire Spectrum Of Light Is Necessary Including UV. Every Cell Communicates To Every Other Cell Through Light. Our Cells Require Sunlight. UVB Is Actually Essential & Using Sunscreen Is Sabotaging Your Health. Sunscreen & sunglasses block UV Rays of the sun that are supposed to enter the eyes & skin for melanin production. Cholesterol, Vitamin D & Melanin production all work together to keep the natural skin barrier healthy & cancer free. Cholesterol level above 200 mg/dL plus Vitamin D3 level above 50 ng/ml protects against all cancer including melanoma. Skin cancer is a reflection of skin that is already sick & corrupted from years of consuming seed oils. Industrial seed oils cause our skin to oxidize, causing inflammation & cell dysregulation. The rise of skin cancer directly coincides with the 328% rise in dietary seed oil consumption within the diet since the 1940s. Seed oils damage our skin from the inside out & melanoma is the terrible consequence of Big Food lying to us about industrial seed oils being healthy. Sun Exposure Is Crucial & Required For Vibrant Health: Optimal Vitamin D (with cholesterol foods in the diet) Stroke Prevention Cancer Prevention Heart Attack Prevention Bone Health Immune System Health Depression Prevention Natural Appetite Suppressant Natural Blood Sugar/Insulin Control Mood Enhancer Hair Keratin Production Naturally Lowers Blood Pressure Optimal Libido & Hormone Production Muscle Health & Injury Prevention The Dangers Of Chemical Sunscreens: Sunscreen Chemicals Reach 14X The FDA Limit In The Bloodstream After Only 1 Day Of Use. Sunscreens Do Not Prevent Cancer, They Cause It. These Chemicals Put A Toxic Load Onto Your Liver & Kidneys Causing Illness & Disease. OXYBENZONE: FDA’s 2020 study, it has been found in blood samples at levels 16 times above the FDA safety threshold. A powerful endocrine disruptor causing lower testosterone in males & causes increased breast cancer & endometriosis in females. OCTOCRYLENE: Readily absorbs through the skin at levels 14 times the FDA’s cutoff for systemic exposure. It is often contaminated with benzophenone, which is a known carcinogen. AVOBENZONE: Testing has revealed bloodstream levels 9 times above the FDA legal limit. Avobenzone disrupts the endocrine system & has been shown to block testosterone. ESCAMSULE: Also known as Mexoryl on ingredient labels, is a powerful endocrine disruptor. Adverse effects include elevation of hepatic liver enzymes, anemia & skin eruptions. When a natural protective barrier is needed for children or extended activities for hours & hours of direct sun exposure, use a safe grass fed beef tallow with the mineral zinc oxide as a protectant. Let me know if you would like a referral to the grass fed tallow skin care products my family & I use for all skincare. 👇Melanoma Is Not Caused By Sunlight👇 👇Vitamin D Deficiency & Chronic Disease👇 👇Sunscreen Toxic In Bloodstream Clinical Trial👇 Speaker: Dr Adiel Tel Oren, MD Video: WR

Valerie Anne Smith

241,224 次观看 • 1 年前

Sora 2 has the capabilities to make an entire anime episode with time and effort. This is a turning point for generative AI models and it is terrifying to think what is next to come. The difference between Sora and Sora 2 is absolutely staggering. Yes, this looks cool. I put the time into it to make it as close to art as possible. This was not simple to make and not just prompting and throwing it in some editor. Every frame is generated of another scene and even the reference image for characters I used to start this project were AI generated. This was all created with 10 second clips pulled apart and chunked out into the final product. Regardless of the imagery you see, I did not directly use any artist's art for this video. This 10-minute video was generated over the course of a week from more than 700 text prompts. It was built on technology trained by scraping the uncredited, uncompensated contributions of countless human artists and animators. The creation of this single video consumed an enormous amount of energy and water, equivalent to powering a home for days and requiring hundreds of liters of fresh water for cooling. But that is nothing. In the 10 minutes you spend watching this, the global network of AI video generators will create over 6,250 more short videos. The combined energy required for that 10 minutes of global creation is enough to power an average household for nearly 2 years. - It's a double-edged sword. While AI uses immense amount of energy has clear immoral issues with scalping the hard work of artists, this also provides those a medium who have potentially spent their life attempting to draw out the ideas in their head and failing to grasp it. My sister is an artist, I grew up always attempting to draw but never could get the image in my head on paper, I've spent the better part of over 20 years to teach myself through watching videos and practice, however I don't have steady hands and frankly have just been unable to make any vision come to life. Which brings me to the conflict here. This would have been a dream of mine to be able to get frames created and flesh out the story in my head. To make this video professionally, it would be an absurd amount of money. A small studio by itself would be over a million dollars just to start up. To hire a studio would be most likely over ~200k. I would love to make this story I have in my head through legit and traditional means, I would love to start a Kickstarter to get funding and hire artists, voice actors, and a production team. However I know that would most likely be an impossible reach that would further fuel the hate. Regardless, I understand the worry this causes. The fear this produces. However, we can't just ignore where AI is currently at and just tell people not to use it or even worse threaten people who use it. People will always use the shiny new toy in front of them, so the real question is how do we either make it work for us and work along side it, or how do we ACTUALLY implement a method to protect art rather than tell people to not use it. Respect your artists. Review their ToS and don't upload their hard work to a model without permission.
10:33

Sora 2 has the capabilities to make an entire anime episode with time and effort. This is a turning point for generative AI models and it is terrifying to think what is next to come. The difference between Sora and Sora 2 is absolutely staggering. Yes, this looks cool. I put the time into it to make it as close to art as possible. This was not simple to make and not just prompting and throwing it in some editor. Every frame is generated of another scene and even the reference image for characters I used to start this project were AI generated. This was all created with 10 second clips pulled apart and chunked out into the final product. Regardless of the imagery you see, I did not directly use any artist's art for this video. This 10-minute video was generated over the course of a week from more than 700 text prompts. It was built on technology trained by scraping the uncredited, uncompensated contributions of countless human artists and animators. The creation of this single video consumed an enormous amount of energy and water, equivalent to powering a home for days and requiring hundreds of liters of fresh water for cooling. But that is nothing. In the 10 minutes you spend watching this, the global network of AI video generators will create over 6,250 more short videos. The combined energy required for that 10 minutes of global creation is enough to power an average household for nearly 2 years. - It's a double-edged sword. While AI uses immense amount of energy has clear immoral issues with scalping the hard work of artists, this also provides those a medium who have potentially spent their life attempting to draw out the ideas in their head and failing to grasp it. My sister is an artist, I grew up always attempting to draw but never could get the image in my head on paper, I've spent the better part of over 20 years to teach myself through watching videos and practice, however I don't have steady hands and frankly have just been unable to make any vision come to life. Which brings me to the conflict here. This would have been a dream of mine to be able to get frames created and flesh out the story in my head. To make this video professionally, it would be an absurd amount of money. A small studio by itself would be over a million dollars just to start up. To hire a studio would be most likely over ~200k. I would love to make this story I have in my head through legit and traditional means, I would love to start a Kickstarter to get funding and hire artists, voice actors, and a production team. However I know that would most likely be an impossible reach that would further fuel the hate. Regardless, I understand the worry this causes. The fear this produces. However, we can't just ignore where AI is currently at and just tell people not to use it or even worse threaten people who use it. People will always use the shiny new toy in front of them, so the real question is how do we either make it work for us and work along side it, or how do we ACTUALLY implement a method to protect art rather than tell people to not use it. Respect your artists. Review their ToS and don't upload their hard work to a model without permission.

LUͦʷCͦk

18,632 次观看 • 11 个月前

🚨 A Pennsylvania local utility company is proposing to run new high-voltage power lines across several miles of private farmland in Union and Lycoming counties for a Data Center This would affect about 20 farms and eminent domain is being considered The data center power lines will also effect farms that are officially protected as preserved farmland The lines will cut through their fields, take land out of production and hurt their ability to farm “My family and I operate an average size Pennsylvania dairy farm in Gregg Township, Union County. We have learned that PPNL would like to run a single source 230 kV line potentially across our property to feed a data center that's proposed in Allenwood. To give you an idea, the plot we're standing on is basically the home farm, which originally was a 93 acre farm purchased by my grandfather almost 100 years ago. My sons are the fourth generation here.” “They're proposing to take 150 foot right of way across our fields” He shows the area they want to take and it will be completely devastating to his farm. It will make it very difficult to farm and they will also do things like compact the soil that will reduce yield on at least 5 acres Using eminent domain like this isn’t helping the public. It’s being weaponized against the public for private companies Farmers and the Pennsylvania Farm Bureau say PPL, which is the utility company, has made clear it is prepared to use eminent domain if landowners refuse to sell or grant rights voluntarily
5:12

🚨 A Pennsylvania local utility company is proposing to run new high-voltage power lines across several miles of private farmland in Union and Lycoming counties for a Data Center This would affect about 20 farms and eminent domain is being considered The data center power lines will also effect farms that are officially protected as preserved farmland The lines will cut through their fields, take land out of production and hurt their ability to farm “My family and I operate an average size Pennsylvania dairy farm in Gregg Township, Union County. We have learned that PPNL would like to run a single source 230 kV line potentially across our property to feed a data center that's proposed in Allenwood. To give you an idea, the plot we're standing on is basically the home farm, which originally was a 93 acre farm purchased by my grandfather almost 100 years ago. My sons are the fourth generation here.” “They're proposing to take 150 foot right of way across our fields” He shows the area they want to take and it will be completely devastating to his farm. It will make it very difficult to farm and they will also do things like compact the soil that will reduce yield on at least 5 acres Using eminent domain like this isn’t helping the public. It’s being weaponized against the public for private companies Farmers and the Pennsylvania Farm Bureau say PPL, which is the utility company, has made clear it is prepared to use eminent domain if landowners refuse to sell or grant rights voluntarily

Wall Street Apes

130,460 次观看 • 2 个月前

Claude Code + Nano Banana 2.0 just killed the $15K/month web agency That’s a mid-tier retainer Now done by one solo with a laptop and 6 prompts This guy just dropped the 6-step workflow Here’s the breakdown 👇 Set up the stack like this: > Firecrawl - scrape competitor / brand refs, extract assets > Claude Code - generate 3 visual directions inside the project > Nano Banana 2.0 - render hero visuals + transition videos > Claude Code - auto-build the full site structure > Claude Code - polish + tighten existing HTML layouts > GitHub + Vercel - deploy in one push First prompt to Claude Code: > Use the Firecrawl output in /assets > Generate 3 visual directions (typography, palette, motion) > Pick the one matching the brand voice in /brief.md > Scaffold a Next.js site, hero + 4 sections > Wire up Vercel deploy on main After it works, tune: > hero motion timing > font pairing > palette contrast > section spacing > transition video length > mobile breakpoints > CTA placement The numbers: → 6 steps instead of 60 → 1 afternoon instead of 6 weeks → $0 tooling vs $15K/month to an agency → Production output - if the brief is strong Taste still wins Weak brief = generic site Strong brief = client thinks you have a 5-person team behind you Reply “SITE” + RT and I’ll send you my Firecrawl → Claude Code prompt pack Full 50-sec walkthrough 👇
0:49

Claude Code + Nano Banana 2.0 just killed the $15K/month web agency That’s a mid-tier retainer Now done by one solo with a laptop and 6 prompts This guy just dropped the 6-step workflow Here’s the breakdown 👇 Set up the stack like this: > Firecrawl - scrape competitor / brand refs, extract assets > Claude Code - generate 3 visual directions inside the project > Nano Banana 2.0 - render hero visuals + transition videos > Claude Code - auto-build the full site structure > Claude Code - polish + tighten existing HTML layouts > GitHub + Vercel - deploy in one push First prompt to Claude Code: > Use the Firecrawl output in /assets > Generate 3 visual directions (typography, palette, motion) > Pick the one matching the brand voice in /brief.md > Scaffold a Next.js site, hero + 4 sections > Wire up Vercel deploy on main After it works, tune: > hero motion timing > font pairing > palette contrast > section spacing > transition video length > mobile breakpoints > CTA placement The numbers: → 6 steps instead of 60 → 1 afternoon instead of 6 weeks → $0 tooling vs $15K/month to an agency → Production output - if the brief is strong Taste still wins Weak brief = generic site Strong brief = client thinks you have a 5-person team behind you Reply “SITE” + RT and I’ll send you my Firecrawl → Claude Code prompt pack Full 50-sec walkthrough 👇

ZEUS⚡️

21,910 次观看 • 4 个月前

I decided to make an UPDATED VERSION of Geno's Shapeless Man style and here's how it turned out! 👀 Below is a video comparison & image of the official Shapeless Man material not including the niagra (flame & distortion vfx) and my version of the Shapeless Man material. While making this, I made sure to use the SAME textures that were used on the official Shapeless Man style. Although I was a tad bit more restricted in Blender with what I could do, I still think it came out good. No disrespect at all to the artists who created the Shapeless Man style, but the biggest issue I have with it is that the lines on his body aren't animated. Along with the distortion, that was a huge factor in what made the Shapeless Man... well, shapeless. The animated lines were present in the Collision version of the Shapeless Man, so I'm not sure why they aren't present in the official style. 🫤 Another change I made to the material was Geno's eyes. In the Collision Event his eyes had a nice gradient and looked a lot more intimidating. Unfortunately that was niagra which I do not have access to in Blender, but I tried my best to recreate a similar look in Blender. Additionally, I also added back Geno's scarf around his neck (Yes, it's codenamed scarf). This was another big detail apart of the Shapeless Man that really made his look feel complete and it was unfortunate to see that was excluded in the official style. I'd like to thank Point⁉️🍉 for help with the node setup & aiden for providing me with the material for the original Shapeless Man style. 🫶 Despite some of my disappointments with the material itself, I LOVE the new unique mesh for the Shapeless Man. In comparison to the Collision version, this mesh makes Geno look a LOT more unsettling and the team behind it did a wonderful job on it! 👏 All in all, I'd love if Epic could take this into consideration and possibly update Geno's Shapeless Man style to look more like the version I'm suggesting. I only want the best for this character. 🤞 Support on this post would be appreciated and thank you to whoever took their time to read this! ❤️
0:47

I decided to make an UPDATED VERSION of Geno's Shapeless Man style and here's how it turned out! 👀 Below is a video comparison & image of the official Shapeless Man material not including the niagra (flame & distortion vfx) and my version of the Shapeless Man material. While making this, I made sure to use the SAME textures that were used on the official Shapeless Man style. Although I was a tad bit more restricted in Blender with what I could do, I still think it came out good. No disrespect at all to the artists who created the Shapeless Man style, but the biggest issue I have with it is that the lines on his body aren't animated. Along with the distortion, that was a huge factor in what made the Shapeless Man... well, shapeless. The animated lines were present in the Collision version of the Shapeless Man, so I'm not sure why they aren't present in the official style. 🫤 Another change I made to the material was Geno's eyes. In the Collision Event his eyes had a nice gradient and looked a lot more intimidating. Unfortunately that was niagra which I do not have access to in Blender, but I tried my best to recreate a similar look in Blender. Additionally, I also added back Geno's scarf around his neck (Yes, it's codenamed scarf). This was another big detail apart of the Shapeless Man that really made his look feel complete and it was unfortunate to see that was excluded in the official style. I'd like to thank Point⁉️🍉 for help with the node setup & aiden for providing me with the material for the original Shapeless Man style. 🫶 Despite some of my disappointments with the material itself, I LOVE the new unique mesh for the Shapeless Man. In comparison to the Collision version, this mesh makes Geno look a LOT more unsettling and the team behind it did a wonderful job on it! 👏 All in all, I'd love if Epic could take this into consideration and possibly update Geno's Shapeless Man style to look more like the version I'm suggesting. I only want the best for this character. 🤞 Support on this post would be appreciated and thank you to whoever took their time to read this! ❤️

Rezztro

34,474 次观看 • 1 个月前

For the first time in my life, I feel I get to merge the 2 things that I love: production & web3. When I look at web3, the space is so rich in stories. Founder stories, product stories, user stories. I believe storytelling is ultimately what will help people see this space for what it is and to give them a different perspective on the media headlines. And it's not often that as a creative you can work side by side with brands and cos that you truly align with. So on May 24th, when I got the call from Arcade Research and Blast to see if I could help Pacman | Blur + Blast share the story and vision for Blast- I knew it was going to be sprint but it was an easy yes. Really excited to share that I had the privilege of directing and producing the Blast Phase 2 announcement video and a deep dive interview with Pacman about the vision for Phase 2. From a little campaign video to a deep dive interview- we covered it all and we ran it back ;) The last 30 days have been a non-stop sprint literally up until yesterday, with 2 productions in LA and NYC. And I’m so grateful to have been a small part of what feels like history in the making. A campaign like this does not happen on such a tight turnaround time without an incredible crew and post-production team. This would not have been possible able to do this without them. Proud of this crew and it was an honor to work alongside them. Excited to be properly stepping back into the world of production to tell the stories of Web3. We experimented, FAFO’d, and had an actual Blast. Plz gib a round of applause for these legends who made it all possible 👏🐐👇 Production Co: Remint Reality Director/Producer: RIP Director of Photography: Josh Park Production Designer: Briana Gonzales 1st AC: Wade Young 2nd AC/DIT: Che Song “Jay” Pak 2nd AC: Mitchell Schultz Editor & Sound Designer: PANDAA (delusionally optimistic era) Motion Graphics & Animation: Suffoca Los Angeles Crew Stills Photographer: Hannah BTS Video: James Cortez Steadicam Op: Jaron Tauch Gaffer: Robin Banando G&E Swing: Eddie Loera Best Boy Electric: Geoff Stevenson Key Grip: Tony Banando Sound Mixer: Ferinand Almalvez Boom Op: Matt Brodnick Set Dresser: Chris Katus H/MU: Tayla Boz PA: LJ Benet New York Crew Gaffer: John Roche G&E Swing: Jeff Cunningham G&E Swing: Kevin Hunt Grip: Huttemberg Nassar Sound Mixer: Daniel Sheppard Boom Op: EJ Markland Set Dresser: Damani Pompey H/MU: Sol PA: Vitali A huge thank you Blast for taking a bet on me and bringing me in to work on this. This is just the beginning. Some BTS from the LA production 👀
1:29

For the first time in my life, I feel I get to merge the 2 things that I love: production & web3. When I look at web3, the space is so rich in stories. Founder stories, product stories, user stories. I believe storytelling is ultimately what will help people see this space for what it is and to give them a different perspective on the media headlines. And it's not often that as a creative you can work side by side with brands and cos that you truly align with. So on May 24th, when I got the call from Arcade Research and Blast to see if I could help Pacman | Blur + Blast share the story and vision for Blast- I knew it was going to be sprint but it was an easy yes. Really excited to share that I had the privilege of directing and producing the Blast Phase 2 announcement video and a deep dive interview with Pacman about the vision for Phase 2. From a little campaign video to a deep dive interview- we covered it all and we ran it back ;) The last 30 days have been a non-stop sprint literally up until yesterday, with 2 productions in LA and NYC. And I’m so grateful to have been a small part of what feels like history in the making. A campaign like this does not happen on such a tight turnaround time without an incredible crew and post-production team. This would not have been possible able to do this without them. Proud of this crew and it was an honor to work alongside them. Excited to be properly stepping back into the world of production to tell the stories of Web3. We experimented, FAFO’d, and had an actual Blast. Plz gib a round of applause for these legends who made it all possible 👏🐐👇 Production Co: Remint Reality Director/Producer: RIP Director of Photography: Josh Park Production Designer: Briana Gonzales 1st AC: Wade Young 2nd AC/DIT: Che Song “Jay” Pak 2nd AC: Mitchell Schultz Editor & Sound Designer: PANDAA (delusionally optimistic era) Motion Graphics & Animation: Suffoca Los Angeles Crew Stills Photographer: Hannah BTS Video: James Cortez Steadicam Op: Jaron Tauch Gaffer: Robin Banando G&E Swing: Eddie Loera Best Boy Electric: Geoff Stevenson Key Grip: Tony Banando Sound Mixer: Ferinand Almalvez Boom Op: Matt Brodnick Set Dresser: Chris Katus H/MU: Tayla Boz PA: LJ Benet New York Crew Gaffer: John Roche G&E Swing: Jeff Cunningham G&E Swing: Kevin Hunt Grip: Huttemberg Nassar Sound Mixer: Daniel Sheppard Boom Op: EJ Markland Set Dresser: Damani Pompey H/MU: Sol PA: Vitali A huge thank you Blast for taking a bet on me and bringing me in to work on this. This is just the beginning. Some BTS from the LA production 👀

Jenn

94,514 次观看 • 2 年前

My company hit $2,000,000 ARR in 7 months. There’s 1 main acquisition channel we used: LinkedIn. And it’s still significantly underused. Here’s the exact content system we used to grow to $2M in 7 months: 1. Content Strategy • Interview your team to brainstorm ideas • Study what's performing in the niche • Analyze post-performance weekly • Use AI for research + concepts 2. Winning Formats The best creators double down on formats. These are our winning formats: TOF → Personal stories, milestones, industry stories MOF → Resource giveaways, infographics, carousels BOF → Feature demos, case studies, product launches 3. Content Team It’s easier to scale content when you have a team. Here's how we structure our team: • Writer • Designer • QA/Editor 4. Content Pipeline We run everything through Notion: • Comments for feedback • Link back to idea sources • Kanban stages for production 5. Content Calendar You won't stay consistent without planning. So: • Stick to the same posting time • Use ordinal to schedule posts • Block off Sundays to plan the week • Build a backlog of posts to choose from — And after lots of trial and error... We packaged this entire content system into a notion workflow. It helps us: 1. Get ideas down quickly 2. Develop them systematically 3. Collaborate with the design team AND includes our framework on how to plan a LinkedIn content strategy: • Content Types • Content Pillars • Content Formats • Content Calendar (plus a post creation template with our own custom embedded LinkedIn previewer) Today, I’m giving the entire thing away for FREE. Want it? Comment "NOTION" And I'll send over our template. (must be following)
0:33

My company hit $2,000,000 ARR in 7 months. There’s 1 main acquisition channel we used: LinkedIn. And it’s still significantly underused. Here’s the exact content system we used to grow to $2M in 7 months: 1. Content Strategy • Interview your team to brainstorm ideas • Study what's performing in the niche • Analyze post-performance weekly • Use AI for research + concepts 2. Winning Formats The best creators double down on formats. These are our winning formats: TOF → Personal stories, milestones, industry stories MOF → Resource giveaways, infographics, carousels BOF → Feature demos, case studies, product launches 3. Content Team It’s easier to scale content when you have a team. Here's how we structure our team: • Writer • Designer • QA/Editor 4. Content Pipeline We run everything through Notion: • Comments for feedback • Link back to idea sources • Kanban stages for production 5. Content Calendar You won't stay consistent without planning. So: • Stick to the same posting time • Use ordinal to schedule posts • Block off Sundays to plan the week • Build a backlog of posts to choose from — And after lots of trial and error... We packaged this entire content system into a notion workflow. It helps us: 1. Get ideas down quickly 2. Develop them systematically 3. Collaborate with the design team AND includes our framework on how to plan a LinkedIn content strategy: • Content Types • Content Pillars • Content Formats • Content Calendar (plus a post creation template with our own custom embedded LinkedIn previewer) Today, I’m giving the entire thing away for FREE. Want it? Comment "NOTION" And I'll send over our template. (must be following)

Dan Rosenthal

20,428 次观看 • 6 个月前

I've never heard Elon Musk be so bullish on Tesla ⚡️ here's my video analysis of the $TSLA Q4 2024 earnings call: -Robotaxi launch in Austin, June 2025 -California & other states launch robotaxi late 2025 -Cybercab in 2026 -Optimus V1 in 2025, 1K/month production line -Optimus V2 in 2026, 10K/month production line -2026 good year for Tesla, 2027/28 insanely good & more!! Timestamps- 0:00 Intro 0:44 Elon Opening Remarks 13:29 SAY Retail Questions 22:37 Analyst Questions 25:04 Gali Final Thoughts/Rant also here are my notes I typed during the conference call if you're interested! (may be errors) Tesla Q4 2024 Earnings Call Notes INTRO- ELON OPENING REMARKS -Q4 set record, delivered cars at rate of almost 2M cars/year -Model Y best-selling vehicle of any kind on earth (elon focused and talking quickly) -10Xing on autonomy, not doubling -many investments made this year that will bear immense fruit in the future, for AI -see a path for Tesla to the worlds most valuable company by far, worth more than the next 5 companies combined, difficult but achievable path -overwhelmingly due to autonomous vehicles and autonomous robots -setting up for an epic 2026, and ridiculously good 2027 and 2028 -meeting FSD now is like meeting a toddler -human intuition is linear, we’re seeing exponential progress -#1 recommendation is try it -typical passenger car has 10 hours of use out of 168, when its autonomous, itll be used for 55 hours a week … can deliver packages in the middle of thenight, or supply restaurants, all hours of the day or night. 5X increase in utility -more on self driving, continued improvements in safety numbers, much safer to use FSD -V14 will be another big step from V13 -launched CORTEX training cluster at Giga Austin, big step for FSD, continue to invest in training needs -Optimus training needs are about 10X what’s needed for the car -cost of training is dropping dramatically over time -Optimus has potential to be north of $10T in revenue, can put a lot training compute into that situation, even pumping $500B into it would be a good deal -future very different from the past, incredible inflection point in human history -proof is in the pudding -launching in June this year in Austin, already have cars moving autonomously in Fremont, thousands of cars per day driving, soon in Austin then elsewhere in the world -toe in the water at first to make sure everything is cool, but we have a general solution for autonomy , then put a few more toes, then a foot. Safety of the general public and those in the car as the top priority -with regard to Optimus, making insane revenue projections that sound insane, i realize that. But i think they will prove to be accurate -several thousand bots made this year, they will be doing useful things by the end of this year, im confidence, production design one at the tesla factories, then will learn for production design two -ramp optimus production faster than anything has ever launched, doesn’t take very many years before we’er making 100M of these things per year , 500% growth per year -tried using all these suppliers to get it to build Optimus, but nothing worked, had to build it internally from first principles, the hand is increibdle -long term Optimus will be the value of the company -back to Energy,/earth, -energy storage is a big deal, becoming more important, enables far greater energy output to the grid than is currently possible. -grid has no storage, designed for peak storage, lots of waste -once you have grid energy storage, the potential of the grid is unlocked, at least double -this will drive demand of battery packs as to as much as we can possibly make -shanghai factory starting operation, starting another factory -cant shoot our selves in the foot, battery capacity can only go into storage or mobility, so always making that tradeoff -demand for total Gigawatt hours for batteries, transportation or stationary will grow in a very big way over time 2025 a pivotal year for tesla, launch of full self driving, biggest year in tesla history, maybe even bigger than first car or model s, 3 or y … probably most important year in tesla’s history I don’t even know who is in 2nd place in real world AI, would need a telescope to see them SAY QUESTIONS -FSD Unsupervised launched in California this year as well -most likely release it in many regions of the US by the end of this year -40K people day everyday no mention, some scrapes a shin with autonomous car its headlines news -need to use insane amounts of caution -discussions about licensing FSD? Yes -best way to know to work with us, bbuy a car and take it apart -only worth very high volume cars/production partners -tesla engineering very focused on getting it to roll out for tesla first -soon will be obvious that if you don’t have FSD you’re dead as an OEM -is Optimus design locked? -Optimus is not design locked, constantly iterating, best robotics engineers in the world, and other ingredients, battery pack, charging, great electronics, great communications, great connectivity, real world AI, then you need to scale that production to real world levels -prototypes are easy production is hard -thijs year close loop with using optimus internally at tesla, would could obviously use a few thousand robots for the most boring annoying tasks at the company -with production version 2, launches sometime next year, would like beginning, might be middle though, -production line will be doing 10K units per month capacity for v2, first line designing is for roughly 1,000 units per month, then next line will be for 100,000 units per month -could start delivering them late next year, will go so fast, will ramp like crazy, demand will not be a problem, even at a high price, once were above 1M units per year, production costs of optimus will be less than $20,000 -if you compare complexity of optimus to complexity of a car, its much less than a car -price of optimus will be set buy market demand -Semi ramping next year, TCO no brainer, like optimus, will be massive demand, will meaningfully contribute to tesla’s revenue at scale -tesla semi with autonomy, is incredibly valuable -we actually have a shortage of truck drivers here in the US -will HW3 owners need a hardware update, got 12.6 which is like a baby v13, have’t given up on it, releases will trail HW4 releases … “honest answer” is were going to have to upgrade for those who have bought full self driving, will be painful and difficult and we’ll get it done “Happy not many people bought FSD” -solar roof, given up on ramping it? -lots of customer interest despite premium, making easier to install, focused on growth through certified installers, many been installing for many years -supply product to the roofing industry -it’s a premium product like S/X -combined with Tesla powerwall you can be self sufficient for several days ANALYST QUETIONS -robotaxis in Austin and several other cities this year, and next year all over america -america innovates, europe regulates, to release FSD in europe, have to go through massive paperwork through netherlands, then presents to EU in may, some big country committee, nothing we can do to make it happen sooner. -can’t do training in china with video training, publicly available videos in china are being run through the tesla system to be used for training, bus lanes are complicated and a big challenge -tesla can keep manufacturing even if geopolitical tensions rise to very high levels -Pierre question on June in Austin, -can i try unsupervised myself, or will it be the Tesla fleet? -it will be the Tesla fleet testing it, that’s the toe in the water, scrutinizing everything -autonomous ride hailing for money in june -probably next year for you to put your car on network -trump removing EV incentives? -all transport will go electric, can’t be stopped, even planes, will be like stopping the steam engine or combustion engine -only thing holding back EVs was range, and thats a solved problem -right now solving battery production, not demand, big battery retooling for model y coming up, short term impact on output
33:55

I've never heard Elon Musk be so bullish on Tesla ⚡️ here's my video analysis of the $TSLA Q4 2024 earnings call: -Robotaxi launch in Austin, June 2025 -California & other states launch robotaxi late 2025 -Cybercab in 2026 -Optimus V1 in 2025, 1K/month production line -Optimus V2 in 2026, 10K/month production line -2026 good year for Tesla, 2027/28 insanely good & more!! Timestamps- 0:00 Intro 0:44 Elon Opening Remarks 13:29 SAY Retail Questions 22:37 Analyst Questions 25:04 Gali Final Thoughts/Rant also here are my notes I typed during the conference call if you're interested! (may be errors) Tesla Q4 2024 Earnings Call Notes INTRO- ELON OPENING REMARKS -Q4 set record, delivered cars at rate of almost 2M cars/year -Model Y best-selling vehicle of any kind on earth (elon focused and talking quickly) -10Xing on autonomy, not doubling -many investments made this year that will bear immense fruit in the future, for AI -see a path for Tesla to the worlds most valuable company by far, worth more than the next 5 companies combined, difficult but achievable path -overwhelmingly due to autonomous vehicles and autonomous robots -setting up for an epic 2026, and ridiculously good 2027 and 2028 -meeting FSD now is like meeting a toddler -human intuition is linear, we’re seeing exponential progress -#1 recommendation is try it -typical passenger car has 10 hours of use out of 168, when its autonomous, itll be used for 55 hours a week … can deliver packages in the middle of thenight, or supply restaurants, all hours of the day or night. 5X increase in utility -more on self driving, continued improvements in safety numbers, much safer to use FSD -V14 will be another big step from V13 -launched CORTEX training cluster at Giga Austin, big step for FSD, continue to invest in training needs -Optimus training needs are about 10X what’s needed for the car -cost of training is dropping dramatically over time -Optimus has potential to be north of $10T in revenue, can put a lot training compute into that situation, even pumping $500B into it would be a good deal -future very different from the past, incredible inflection point in human history -proof is in the pudding -launching in June this year in Austin, already have cars moving autonomously in Fremont, thousands of cars per day driving, soon in Austin then elsewhere in the world -toe in the water at first to make sure everything is cool, but we have a general solution for autonomy , then put a few more toes, then a foot. Safety of the general public and those in the car as the top priority -with regard to Optimus, making insane revenue projections that sound insane, i realize that. But i think they will prove to be accurate -several thousand bots made this year, they will be doing useful things by the end of this year, im confidence, production design one at the tesla factories, then will learn for production design two -ramp optimus production faster than anything has ever launched, doesn’t take very many years before we’er making 100M of these things per year , 500% growth per year -tried using all these suppliers to get it to build Optimus, but nothing worked, had to build it internally from first principles, the hand is increibdle -long term Optimus will be the value of the company -back to Energy,/earth, -energy storage is a big deal, becoming more important, enables far greater energy output to the grid than is currently possible. -grid has no storage, designed for peak storage, lots of waste -once you have grid energy storage, the potential of the grid is unlocked, at least double -this will drive demand of battery packs as to as much as we can possibly make -shanghai factory starting operation, starting another factory -cant shoot our selves in the foot, battery capacity can only go into storage or mobility, so always making that tradeoff -demand for total Gigawatt hours for batteries, transportation or stationary will grow in a very big way over time 2025 a pivotal year for tesla, launch of full self driving, biggest year in tesla history, maybe even bigger than first car or model s, 3 or y … probably most important year in tesla’s history I don’t even know who is in 2nd place in real world AI, would need a telescope to see them SAY QUESTIONS -FSD Unsupervised launched in California this year as well -most likely release it in many regions of the US by the end of this year -40K people day everyday no mention, some scrapes a shin with autonomous car its headlines news -need to use insane amounts of caution -discussions about licensing FSD? Yes -best way to know to work with us, bbuy a car and take it apart -only worth very high volume cars/production partners -tesla engineering very focused on getting it to roll out for tesla first -soon will be obvious that if you don’t have FSD you’re dead as an OEM -is Optimus design locked? -Optimus is not design locked, constantly iterating, best robotics engineers in the world, and other ingredients, battery pack, charging, great electronics, great communications, great connectivity, real world AI, then you need to scale that production to real world levels -prototypes are easy production is hard -thijs year close loop with using optimus internally at tesla, would could obviously use a few thousand robots for the most boring annoying tasks at the company -with production version 2, launches sometime next year, would like beginning, might be middle though, -production line will be doing 10K units per month capacity for v2, first line designing is for roughly 1,000 units per month, then next line will be for 100,000 units per month -could start delivering them late next year, will go so fast, will ramp like crazy, demand will not be a problem, even at a high price, once were above 1M units per year, production costs of optimus will be less than $20,000 -if you compare complexity of optimus to complexity of a car, its much less than a car -price of optimus will be set buy market demand -Semi ramping next year, TCO no brainer, like optimus, will be massive demand, will meaningfully contribute to tesla’s revenue at scale -tesla semi with autonomy, is incredibly valuable -we actually have a shortage of truck drivers here in the US -will HW3 owners need a hardware update, got 12.6 which is like a baby v13, have’t given up on it, releases will trail HW4 releases … “honest answer” is were going to have to upgrade for those who have bought full self driving, will be painful and difficult and we’ll get it done “Happy not many people bought FSD” -solar roof, given up on ramping it? -lots of customer interest despite premium, making easier to install, focused on growth through certified installers, many been installing for many years -supply product to the roofing industry -it’s a premium product like S/X -combined with Tesla powerwall you can be self sufficient for several days ANALYST QUETIONS -robotaxis in Austin and several other cities this year, and next year all over america -america innovates, europe regulates, to release FSD in europe, have to go through massive paperwork through netherlands, then presents to EU in may, some big country committee, nothing we can do to make it happen sooner. -can’t do training in china with video training, publicly available videos in china are being run through the tesla system to be used for training, bus lanes are complicated and a big challenge -tesla can keep manufacturing even if geopolitical tensions rise to very high levels -Pierre question on June in Austin, -can i try unsupervised myself, or will it be the Tesla fleet? -it will be the Tesla fleet testing it, that’s the toe in the water, scrutinizing everything -autonomous ride hailing for money in june -probably next year for you to put your car on network -trump removing EV incentives? -all transport will go electric, can’t be stopped, even planes, will be like stopping the steam engine or combustion engine -only thing holding back EVs was range, and thats a solved problem -right now solving battery production, not demand, big battery retooling for model y coming up, short term impact on output

Gali

79,178 次观看 • 1 年前

** Sega Genesis 3D Engine Update 8 ** Significant improvements all round as you can see and hear from the last update !! Foremost - A huge thanks to Toni Gálvez - Megastyle - BG. who has joined the project to create a bit of 16bit low poly magic. Toni's an Amiga fan but also crazy about game dev in general, he's worked on GBC, GBA, PC, MD, PSP, C64, CPC, MSX... and others. Gaming titles include War Times, Metal Gear, Rocketman, Tintin & Asterix to name a few. He's provided the great new ship model you see on screen - new striped buildings, all the backgrounds / palettes etc. There's a lot of models he's given me which need to be added, also he will be planning a lot of the level design. Very happy to have him help me turn this into something more than a tech demo as I have my hands tied pushing the MD as far as it can go haha - there is no cpu cycle to be spared. Also many thanks to my good friend CYBERDEOUS - Crouzet Laurent for the Music for this showing , I wanted to have the music load occurring so we have a realistic benchmark for performance and he was only too obliging. If you're into MD chiptunes check him out !! Since last update : New player model , substantially more detailed than the Arwing. Last update had a 23 triangle Arwing , this update has a 39 triangle custom model from Toni. We had several to choose from , others will be used for enemies . 3D Buffer size increased 25% to 256x160. This was quite tricky as I'm close to the DMA limit even with an extended vblank . Spent a few days thinking of how to do this as like anything retro every solution has a drawback, finally got a workable solution. It makes a big difference to have a bit more vertical height . Z Rotation added ( the screen tilting left to right ) , small hit to vertex transform on cpu thanks to look up tables doing the heavy lifting, saving 4 multiplies per vertex. Multiple speed ups in rendering code. Onscreen paths with no range checking used until Z is close enough to cause clipping , partial onscreen drawing pathes that need to check boundaries, quad rendering completely rewritten - was very very painfull to get right . I found out the hard way that things are great when they are not rotating in the Z axis haha . Partial buffer draw optimisations - which have helped with the massive dma load , sending up to a 20kb buffer in a single frame needs a lot of optimisation. Min / Max tile lines are analysed and only sent if dirtied , reducing most buffer swaps substantially. Still some issues to sort out , at times you can see the flicker near top of screen when frames are near full height . I need to optimise that a bit. Due to the onscreen buffer system a full Sprite background had to be implemented almost Neo Geo style. This flips the usual MD rendering system on its head as it uses both foreground and background layers for a foreground 3d plane and sprites for the background. This presents a few issues, one is to get a tilt effect on the background by using narrow sprites (16x32) we run out of sprites when trying to cover the screen. Thankfully the MD is not limited to 80 sprites, to fix this a 114 sprite multiplexor is used to draw the background, its completely made up of 16x32 sprites ! Why do things this way ? speed . Its the interleaved foreground/background layers that allow a double buffered ram system writing to write to vram using dma in a completely linear fashion - virtually no tile translation needed. The negative is you have no planes for the background, that's where the sprites come in . Thanks to H40 mode we still have a few sprites we can use for effects in the forground also . Thankfully we can implement a fairly good tilt still for the background using sprites, in future updates this will be able to move horizontally also and a bit of vertical movement. XGM1 music driver in use to simulate music cpu load, XGM2 unfortunately with the massive DMA needed to shift the 3d buffers would slow down at times rendering it unusable, XGM1 plays at full speed - albiet with a bit more of a cpu hit. Together with the sprite multiplexor and the music driver active theres a 10 % hit to cpu so I've had to play around with draw distances / object heights and other optimisations to offset that. Not to mention the larger buffer takes more cpu to fill also. Everything is placeholder so will be changed with proper stage design. We are averaging 20 FPS in the current video, I'll push for more as always !! Progress continues on my other projects , updates soon on those - retirement can't come quick enough . #SGDK #SegaGenesis #SegaMegadrive
1:17

** Sega Genesis 3D Engine Update 8 ** Significant improvements all round as you can see and hear from the last update !! Foremost - A huge thanks to Toni Gálvez - Megastyle - BG. who has joined the project to create a bit of 16bit low poly magic. Toni's an Amiga fan but also crazy about game dev in general, he's worked on GBC, GBA, PC, MD, PSP, C64, CPC, MSX... and others. Gaming titles include War Times, Metal Gear, Rocketman, Tintin & Asterix to name a few. He's provided the great new ship model you see on screen - new striped buildings, all the backgrounds / palettes etc. There's a lot of models he's given me which need to be added, also he will be planning a lot of the level design. Very happy to have him help me turn this into something more than a tech demo as I have my hands tied pushing the MD as far as it can go haha - there is no cpu cycle to be spared. Also many thanks to my good friend CYBERDEOUS - Crouzet Laurent for the Music for this showing , I wanted to have the music load occurring so we have a realistic benchmark for performance and he was only too obliging. If you're into MD chiptunes check him out !! Since last update : New player model , substantially more detailed than the Arwing. Last update had a 23 triangle Arwing , this update has a 39 triangle custom model from Toni. We had several to choose from , others will be used for enemies . 3D Buffer size increased 25% to 256x160. This was quite tricky as I'm close to the DMA limit even with an extended vblank . Spent a few days thinking of how to do this as like anything retro every solution has a drawback, finally got a workable solution. It makes a big difference to have a bit more vertical height . Z Rotation added ( the screen tilting left to right ) , small hit to vertex transform on cpu thanks to look up tables doing the heavy lifting, saving 4 multiplies per vertex. Multiple speed ups in rendering code. Onscreen paths with no range checking used until Z is close enough to cause clipping , partial onscreen drawing pathes that need to check boundaries, quad rendering completely rewritten - was very very painfull to get right . I found out the hard way that things are great when they are not rotating in the Z axis haha . Partial buffer draw optimisations - which have helped with the massive dma load , sending up to a 20kb buffer in a single frame needs a lot of optimisation. Min / Max tile lines are analysed and only sent if dirtied , reducing most buffer swaps substantially. Still some issues to sort out , at times you can see the flicker near top of screen when frames are near full height . I need to optimise that a bit. Due to the onscreen buffer system a full Sprite background had to be implemented almost Neo Geo style. This flips the usual MD rendering system on its head as it uses both foreground and background layers for a foreground 3d plane and sprites for the background. This presents a few issues, one is to get a tilt effect on the background by using narrow sprites (16x32) we run out of sprites when trying to cover the screen. Thankfully the MD is not limited to 80 sprites, to fix this a 114 sprite multiplexor is used to draw the background, its completely made up of 16x32 sprites ! Why do things this way ? speed . Its the interleaved foreground/background layers that allow a double buffered ram system writing to write to vram using dma in a completely linear fashion - virtually no tile translation needed. The negative is you have no planes for the background, that's where the sprites come in . Thanks to H40 mode we still have a few sprites we can use for effects in the forground also . Thankfully we can implement a fairly good tilt still for the background using sprites, in future updates this will be able to move horizontally also and a bit of vertical movement. XGM1 music driver in use to simulate music cpu load, XGM2 unfortunately with the massive DMA needed to shift the 3d buffers would slow down at times rendering it unusable, XGM1 plays at full speed - albiet with a bit more of a cpu hit. Together with the sprite multiplexor and the music driver active theres a 10 % hit to cpu so I've had to play around with draw distances / object heights and other optimisations to offset that. Not to mention the larger buffer takes more cpu to fill also. Everything is placeholder so will be changed with proper stage design. We are averaging 20 FPS in the current video, I'll push for more as always !! Progress continues on my other projects , updates soon on those - retirement can't come quick enough . #SGDK #SegaGenesis #SegaMegadrive

Shannon Birt

35,025 次观看 • 2 个月前

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 次观看 • 5 个月前

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 次观看 • 6 个月前

Moneytaur study blueprint 🗺️ The process I used to go from not knowing what an order block is to pulling cash from the crypto markets in under 6 months using 🎯 Master concepts. Proof of performance, past 120 days👇 Start date: 09/03/2025 Requirements: - A PC/laptop - Wifi - A basic understanding of trading. ( What candlesticks are, how to actually place trades , etc ) - A free mind - Time or the ability to free up time. Starting: - Structure and routine - Stick to that routine + Pre mortem plan. - Notion / Obsidian setup. The first thing you need to create is a clear routine moulded around how you intend to approach this very large and complex task. This will not be linear and you will naturally adapt it as you progress but especially in the beginning some resemblance of structure each day is vital. This is an individual process but it is important to understand from the beginning that this will require a majority of your free time assuming you work a full time Job or study as a student. For me in the beginning this looked like: - Wake up at 6:30. - Shower - Study/work for 1h 45m before leaving for work. - 09:00 -> 17:00 work - 17:30 Exercise / Train - Eat - 19:00 resume study/work - 22:30 Start to wind down and get ready to sleep. It changed several times over the months and especially now I am full time but this is irrelevant, the only thing that matters is sticking with what you choose. Whatever your own routine may look like, it is important to understand it will inevitably require sacrifice. --- The next thing once you have established a draft framework of your routine is ensuring you will actually stick to that routine. Something I implemented which I found particularly beneficial was the concept of a Pre-Mortem plan. This involves creating several scenarios of a future in which you have failed and working backwards from each of these to find where it went wrong. Here is a video which explains it fully: When I did this I came up with 3 scenarios as well as prevention and cure for each. In the 6 months that followed each scenario presented at some point but I was able to catch them early due to having done this. The last thing is to not over complicate this, don't hyper focus on systems and loose momentum optimizing each detail. Just ensure you do the fucking work. I was a little guilty of the above at times, trying to craft the perfect routine. In reality the person who just gets up, drinks too much coffee and works his ass off out performs the workflow perfectionist who visualizes and repeats affirmations, any day of the week. --- Next you need somewhere to store your notes, journal your trades and build your knowledge. For me this was Obsidian but I have also used Notion before and it is an equally viable option. Whichever one of these you choose be warned you will inevitably want to bang your head against a wall trying to use them for the first few days, but they will both click pretty quick and are 100% better options the word document or paper alternative. Here is my full obsidian setup tutorial: Here is a link to MisterPA 's notion Journal: Here is how I create "Meta-Notes" using obsidian: The process: - How I did it. - How I would do it if doing it again. Now I did things the "hard way" and manually worked my way back through each of MT's tweets starting in 2021, reading every one and logging those that I felt where relevant. You can see in my first post: the very first system I used to do this. I quickly adapted though after about a week and focused less on just logging each relevant tweet but trying to find and focusing on those which contained the most information. There where a lot of charts I looked at then skipped over because especially at the start of his timeline they contained little useful information and my time was better spent finding those where there was something to decode. Now this does not mean skip out on "work" just use your time efficiently. -- If however if I was to start from the beginning again with the goal of levelling up technical understanding as quickly as possible I would take a different approach. To start with I would familiarise myself with all relevant SMC concepts, I have linked the best free recourses for this below 👇 CryptoChase beginner friendly index: Barncore's "The Moneytaur Way" series: Gian's Trading bootcamp playlist: Following this I would then work through all of Taur's subscription posts working backwards, recreating his charts and taking notes on his logic. The subscription feed has the highest value density and least noise. Video example of my notes from his subscription posts 👇: --- Okay so now once you have a basic understanding of concepts and can re-recreate them on charts of your own it is time to put this in to practice. The next step is vigorous backtesting, you can use the trading view tool but I think trade Zella offers a more use friendly option if you pay for the subscription. Especially as it allows you to change timeframes without skipping ahead to candle close time of the timeframe you change too ( like Trading view does ) *my only note would be that their LTF/Micro TF data feed with be different to brokerage charts you will use on Trading view, to start with though you should not be going low enough that this is an issue. When you backtest in this context, treat it like real trading. That means journal and logging like you would if real cash was on the line. Take time, do not rush and focus on quality. Stick to BTC, ETH, Major FX pairs or indices as these assets are less reliant on confluence, backtesting a shitcoin is near useless as whether levels work or not will be highly dependent on Majors PA. Go on HTF, scroll back a couple years and try not too look at chart while doing so and then begin. Start with HTF analysis and work down to 2H or wherever you feel comfortable, chart it fully and then identify setups. Make rough notes / plans and then press play, execute the setups as they hit, log and journal trade management as well as observations and key notes. It is very important to not cheat when you do this, do not skip back and adjust your stoploss because it hit by 0.1%, do not skip back and adjust plan because you missed a block and your TP got frontrun. Instead these are the things you journal, embrace these mistakes because they are the cheapest mistakes you are going to make. Grind this, do it for hours, put some music on and enjoy. To start with focus on HTF's, as you get better and start netting $ on paper you can drop the timeframes and increase the difficulty. HTF = Normal, MTF = Medium, LTF = Hard. Even if you do not intend to day trade, learning how to read the lower TF's that force you to think faster, harder and prepare you for lower win rates / loss streaks can greatly improve your ability on higher TF's. While you are doing this as you start to have concepts click you now want to build up your real trading experience, take a sum of money that you care about but will be okay loosing and dedicate this to live trading. Start taking real trades and expect net losses in the beginning. This is where you will make you 2nd cheapest mistakes. This is also where you can begin to learn about your psychology. You may encounter some elements already in backtesting but the real market is where true colours really start to show. Mental issues are inevitable and part of the game, get used to them and start working to identify and fix them. Reading and applying books like Trading in the Zone and Mental Game of Trading are important and will help a lot but there is no easy fix, for some stuff you I believe you just have to get used to it and it goes away with experience. Losses suck at the beginning but after you loose 100 times you starting getting pretty numb to it, same goes for the winners. To accelerate the learning process, build connections and get advice there is also always the option of private groups, while I never personally chose this route and committed to learning everything through my own endeavours there is no denying that having nearly all the information you need structured and compiled in one place is valuable and can save time. Beyond this having access to real time thoughts and opinions of profitable traders can accelerate performance, however it carries the risk of being a double edged sword if not used properly, if relying on it like a crutch and using it as a substitute for real work you will not succeed. With that said if you take it for what it is, a learning opportunity then I believe it can be very beneficial. I am not a member of, nor affiliated with any paid group. There are now many options available within the community, all run by different people with different styles, tailored to different needs. If I was to make a recommendation though, as a non-member, it would be Albert & Co's 618'ers simply due to the diversity in styles of the traders running it and results I have seen from members I know personally. It is important that as you start to trade with real capital you reduce noise in your social feeds or eliminate it all together. You do not need 5 different opinions, you also do not need 2 people telling you the same thing in their own way so you feel re-assured. What you do need is to develop your independent thinking as a trader and be comfortable making different decisions to others, even traders ahead of yourself if it fits with your system or understanding of market. Taur here is perhaps an exception as this is who you are learning from but down the line a real test of your own ability and independence will be being able to stick with your own plan even when it differs from his. Don't get me wrong, counter trading him is retarded but you must learn to adapt his gift to your own style. This will make sense at some point. The next stage is taking your understanding of specific concepts to higher level as you simultaneously snowball experience. Look back through your journal and review where you lost money and made money, do not over extrapolate from a small sample but start to take notes and observe if trends in performance emerge. This is the beginning of the transition to self reliance, you now understand the strategy but must learn for yourself when and where it works. Here you can also learn more nuanced secondary concepts such as VSA, orderflow etc and add these to your game where appropriate. Do NOT get lost in the sauce though and remember mastery of basics is key. IMO a big focus should be understanding correlation thoroughly but especially on HTF's this is the most important thing and what triggers the majority of large swings where most of your cash will be made and losses recovered. Some people will disagree with me here but IMO you should also not be *focusing* on Odd TF's. These are secondary at best and most people overweight their significance leading to avoidable losses while wondering why price did not care about their 327minute Breaker Block which they think is the key to the market. Study Taurs feed and take note of how he mostly uses: 3M, 1M, 3W, 2W, 1W, 5D, 4D, 3D, 2D, 1D, 12H, 8H, 6H, 4H, 2H, 1H, 30m, 15m + micro time frames. The only thing left is time and repetition, you must show up each day and really do this, for months. Maybe you start to see result's, you catch your first key swing and where able to trade where others froze. Congratulations. Learn from these winners and repeat the actions. Find what assets work best for you, find your style, refine and grow. --- The last thing I will include is a short list of tools or links that can be helpful. - Trading view tutorial: - Dictionary: - Market news Calendar: --- Thank you too all those who have read this, I hope this has been helpful for the beginners who want to start but are just not sure how. 🫶 Don't just bookmark this and move on, start 🙃
0:38

Moneytaur study blueprint 🗺️ The process I used to go from not knowing what an order block is to pulling cash from the crypto markets in under 6 months using 🎯 Master concepts. Proof of performance, past 120 days👇 Start date: 09/03/2025 Requirements: - A PC/laptop - Wifi - A basic understanding of trading. ( What candlesticks are, how to actually place trades , etc ) - A free mind - Time or the ability to free up time. Starting: - Structure and routine - Stick to that routine + Pre mortem plan. - Notion / Obsidian setup. The first thing you need to create is a clear routine moulded around how you intend to approach this very large and complex task. This will not be linear and you will naturally adapt it as you progress but especially in the beginning some resemblance of structure each day is vital. This is an individual process but it is important to understand from the beginning that this will require a majority of your free time assuming you work a full time Job or study as a student. For me in the beginning this looked like: - Wake up at 6:30. - Shower - Study/work for 1h 45m before leaving for work. - 09:00 -> 17:00 work - 17:30 Exercise / Train - Eat - 19:00 resume study/work - 22:30 Start to wind down and get ready to sleep. It changed several times over the months and especially now I am full time but this is irrelevant, the only thing that matters is sticking with what you choose. Whatever your own routine may look like, it is important to understand it will inevitably require sacrifice. --- The next thing once you have established a draft framework of your routine is ensuring you will actually stick to that routine. Something I implemented which I found particularly beneficial was the concept of a Pre-Mortem plan. This involves creating several scenarios of a future in which you have failed and working backwards from each of these to find where it went wrong. Here is a video which explains it fully: When I did this I came up with 3 scenarios as well as prevention and cure for each. In the 6 months that followed each scenario presented at some point but I was able to catch them early due to having done this. The last thing is to not over complicate this, don't hyper focus on systems and loose momentum optimizing each detail. Just ensure you do the fucking work. I was a little guilty of the above at times, trying to craft the perfect routine. In reality the person who just gets up, drinks too much coffee and works his ass off out performs the workflow perfectionist who visualizes and repeats affirmations, any day of the week. --- Next you need somewhere to store your notes, journal your trades and build your knowledge. For me this was Obsidian but I have also used Notion before and it is an equally viable option. Whichever one of these you choose be warned you will inevitably want to bang your head against a wall trying to use them for the first few days, but they will both click pretty quick and are 100% better options the word document or paper alternative. Here is my full obsidian setup tutorial: Here is a link to MisterPA 's notion Journal: Here is how I create "Meta-Notes" using obsidian: The process: - How I did it. - How I would do it if doing it again. Now I did things the "hard way" and manually worked my way back through each of MT's tweets starting in 2021, reading every one and logging those that I felt where relevant. You can see in my first post: the very first system I used to do this. I quickly adapted though after about a week and focused less on just logging each relevant tweet but trying to find and focusing on those which contained the most information. There where a lot of charts I looked at then skipped over because especially at the start of his timeline they contained little useful information and my time was better spent finding those where there was something to decode. Now this does not mean skip out on "work" just use your time efficiently. -- If however if I was to start from the beginning again with the goal of levelling up technical understanding as quickly as possible I would take a different approach. To start with I would familiarise myself with all relevant SMC concepts, I have linked the best free recourses for this below 👇 CryptoChase beginner friendly index: Barncore's "The Moneytaur Way" series: Gian's Trading bootcamp playlist: Following this I would then work through all of Taur's subscription posts working backwards, recreating his charts and taking notes on his logic. The subscription feed has the highest value density and least noise. Video example of my notes from his subscription posts 👇: --- Okay so now once you have a basic understanding of concepts and can re-recreate them on charts of your own it is time to put this in to practice. The next step is vigorous backtesting, you can use the trading view tool but I think trade Zella offers a more use friendly option if you pay for the subscription. Especially as it allows you to change timeframes without skipping ahead to candle close time of the timeframe you change too ( like Trading view does ) *my only note would be that their LTF/Micro TF data feed with be different to brokerage charts you will use on Trading view, to start with though you should not be going low enough that this is an issue. When you backtest in this context, treat it like real trading. That means journal and logging like you would if real cash was on the line. Take time, do not rush and focus on quality. Stick to BTC, ETH, Major FX pairs or indices as these assets are less reliant on confluence, backtesting a shitcoin is near useless as whether levels work or not will be highly dependent on Majors PA. Go on HTF, scroll back a couple years and try not too look at chart while doing so and then begin. Start with HTF analysis and work down to 2H or wherever you feel comfortable, chart it fully and then identify setups. Make rough notes / plans and then press play, execute the setups as they hit, log and journal trade management as well as observations and key notes. It is very important to not cheat when you do this, do not skip back and adjust your stoploss because it hit by 0.1%, do not skip back and adjust plan because you missed a block and your TP got frontrun. Instead these are the things you journal, embrace these mistakes because they are the cheapest mistakes you are going to make. Grind this, do it for hours, put some music on and enjoy. To start with focus on HTF's, as you get better and start netting $ on paper you can drop the timeframes and increase the difficulty. HTF = Normal, MTF = Medium, LTF = Hard. Even if you do not intend to day trade, learning how to read the lower TF's that force you to think faster, harder and prepare you for lower win rates / loss streaks can greatly improve your ability on higher TF's. While you are doing this as you start to have concepts click you now want to build up your real trading experience, take a sum of money that you care about but will be okay loosing and dedicate this to live trading. Start taking real trades and expect net losses in the beginning. This is where you will make you 2nd cheapest mistakes. This is also where you can begin to learn about your psychology. You may encounter some elements already in backtesting but the real market is where true colours really start to show. Mental issues are inevitable and part of the game, get used to them and start working to identify and fix them. Reading and applying books like Trading in the Zone and Mental Game of Trading are important and will help a lot but there is no easy fix, for some stuff you I believe you just have to get used to it and it goes away with experience. Losses suck at the beginning but after you loose 100 times you starting getting pretty numb to it, same goes for the winners. To accelerate the learning process, build connections and get advice there is also always the option of private groups, while I never personally chose this route and committed to learning everything through my own endeavours there is no denying that having nearly all the information you need structured and compiled in one place is valuable and can save time. Beyond this having access to real time thoughts and opinions of profitable traders can accelerate performance, however it carries the risk of being a double edged sword if not used properly, if relying on it like a crutch and using it as a substitute for real work you will not succeed. With that said if you take it for what it is, a learning opportunity then I believe it can be very beneficial. I am not a member of, nor affiliated with any paid group. There are now many options available within the community, all run by different people with different styles, tailored to different needs. If I was to make a recommendation though, as a non-member, it would be Albert & Co's 618'ers simply due to the diversity in styles of the traders running it and results I have seen from members I know personally. It is important that as you start to trade with real capital you reduce noise in your social feeds or eliminate it all together. You do not need 5 different opinions, you also do not need 2 people telling you the same thing in their own way so you feel re-assured. What you do need is to develop your independent thinking as a trader and be comfortable making different decisions to others, even traders ahead of yourself if it fits with your system or understanding of market. Taur here is perhaps an exception as this is who you are learning from but down the line a real test of your own ability and independence will be being able to stick with your own plan even when it differs from his. Don't get me wrong, counter trading him is retarded but you must learn to adapt his gift to your own style. This will make sense at some point. The next stage is taking your understanding of specific concepts to higher level as you simultaneously snowball experience. Look back through your journal and review where you lost money and made money, do not over extrapolate from a small sample but start to take notes and observe if trends in performance emerge. This is the beginning of the transition to self reliance, you now understand the strategy but must learn for yourself when and where it works. Here you can also learn more nuanced secondary concepts such as VSA, orderflow etc and add these to your game where appropriate. Do NOT get lost in the sauce though and remember mastery of basics is key. IMO a big focus should be understanding correlation thoroughly but especially on HTF's this is the most important thing and what triggers the majority of large swings where most of your cash will be made and losses recovered. Some people will disagree with me here but IMO you should also not be *focusing* on Odd TF's. These are secondary at best and most people overweight their significance leading to avoidable losses while wondering why price did not care about their 327minute Breaker Block which they think is the key to the market. Study Taurs feed and take note of how he mostly uses: 3M, 1M, 3W, 2W, 1W, 5D, 4D, 3D, 2D, 1D, 12H, 8H, 6H, 4H, 2H, 1H, 30m, 15m + micro time frames. The only thing left is time and repetition, you must show up each day and really do this, for months. Maybe you start to see result's, you catch your first key swing and where able to trade where others froze. Congratulations. Learn from these winners and repeat the actions. Find what assets work best for you, find your style, refine and grow. --- The last thing I will include is a short list of tools or links that can be helpful. - Trading view tutorial: - Dictionary: - Market news Calendar: --- Thank you too all those who have read this, I hope this has been helpful for the beginners who want to start but are just not sure how. 🫶 Don't just bookmark this and move on, start 🙃

Ace

45,752 次观看 • 10 个月前

Hyperspace: The Agentic OS Apple Should Have Built On December 19th, 2024, we announced the world’s first Agentic Browser. What followed was a movement — a new category was born which led to many early products in this space and recently the hundreds of people lining up outside the The Agentic Browser Summit in San Francisco underscored that. Silicon Valley instinctively gets it, from students to tech executives, people can feel a revolutionary new change in computing is in the air. Past year taught us why such a product was inevitable, a hard engineering effort, and also the last mover in the entire software world this decade if and when done right. All paths are headed in the same direction: one tool which orchestrates them all. At Hyperspace we showed that path with essays and products we launched in earlier months: from a spatial UI of orchestrating agents, to showcasing transparent activity in how the AI system operates which leads to user trust, to presenting the software end-game, which massively improves human productivity. We also built the world’s largest AI network, drawing participation from people in almost 6000 cities around the world contributing their machines as nodes in the network. Think Uber, but for AI. That is, planetary-scale. And now we are stretching this industry ambition further with our end-to-end vision of the Agentic Supercomputer, the first breakthrough new AI OS, and an effort which spans from AI research to distributed systems to inventing a new UI to inventing a new business model to complement it. All of this together helps us in serving our mission, of delivering “Everyone’s Personal Supercomputer”. While others have built AI-native browsers, no one though has built something agentic from the ground up — with AI as the foundation, not a feature. How do you fundamentally improve the lives’ of billions around the world ? We believe that requires building a native environment for agents to be viewed, created, deployed, executed, discovered and priced in. That is a world where we move on from static apps, to dynamic agents. But, as my 2 year old niece likes to ask: “but why ?” The issue is that the world of software today is fragmented, and everyone is sprinkling on AI as a feature and charging a subscription fees for it. From browser makers, to IDEs, to design and other productivity tools. This leads to a fragmented UX, where people have to learn to use AI in each app, their memory and other context is not shared between all these apps, and they also have to pay separately for compute for each such AI-enhanced app. Each app maker has to figure out basics such as compute, and leads to the issues we saw with Cursor pricing recently. This is not the future. What if AI was the foundation instead of a feature ? What if Apple had built a fundamentally new AI OS from the ground up and what would it have looked like ? At Hyperspace, that is what we did. On July 15th we introduced three breakthrough key pillars of our AI OS: 1. Agentic Browser 2. Agentic Memory 3. Agentic Payments And we didn’t stop there. We also introduced a breakthrough new user interface called the Spatial AI which is inspired both from the spreadsheet and the HyperCard - each card is an agent, with it’s own inputs and outputs, endlessly extensible and pluggable with others, just like cells of a spreadsheet. Update one cell and all the dependents update, like a spreadsheet formula. It goes beyond a static linear workflow to being able to operate in all directions. This revolutionary new interface helps manage all of the below: 1. Multiple websites being browsed in parallel 2. Multiple desktop apps being browsed in parallel 3. Multiple server tools being used in parallel 4. Multiple smartphone apps streamed to your device or opened via an emulator All the software which you need comes together in this one seamless, agent-native interface. This interface provides you access to the largest network of models, vectors, agents and compute on the planet. The Browser. The IDE. The Notepad… they are not separate products: they are all in one, the Agentic Browser. As Steve Jobs famously said at the iPhone announcement, “are you getting it ?” And beneath this UI lies a new intelligence routing layer — leveraging both swarms of specialized models to the Hyperspace Matrix model that recalls thousands of tools in real-time, not by context window hacks, but through retrieval, ranking, and reuse. To many, this will feel like AGI. Not one big system by one big company, but an intelligent network. Now lets talk about privacy… Are you comfortable with one company owning all your memory forever ? I am not. So we have invented Agentic Memory as a new open protocol which provides full power over memory to you, the user. Your memory is yours, encrypted, on your device, and portable if and how you want. Anyone can build on it without our permission, but not without your permission. This protocol, and the decentralized vector database spread out across the world, would enable apps and agents to share context and memory. Think copy-paste, but for the AI world. It doesn’t just remember — it knows what matters. VectorRank helps your AI weigh your life’s most relevant moments over time, just like the way our minds elevate memories. Now each time you use an agent, your experience with other agents will also continuously improve: you don’t have to keep repeating the same things about yourself, while fully preserving your privacy. Agentic Memory is accessible within the Agentic Browser to manage. And there is one more thing… AI as the foundation requires compute to be available at the base layer, but this base layer spans models running on your own device, to cloud APIs, to also running across the peer-to-peer distributed network. Agentic Payments provides a singular interface to all of that compute, running a spot auction clearing marketplace every second to determine the fair price of compute. This results in price transparency, and you as the user paying the lowest possible cost. If you want predictability, you can reserve compute in advance. This end-to-end system provides the most streamlined world for agents to operate in. In order to enable this world and the world of agents being able to pay each other in sub-cent increments millions of times a second, we had to also invent a fundamentally new agentic micropayments blockchain. All of this together would enable a world where you as a user, or the agent itself, can efficiently call and utilize other agents built by others and also pay for content which is unique and useful. This enables a move away from the current AI exploitative economy for bloggers and other content creators, to a web with a fundamental new business model. Earlier we didn’t have the right infrastructure to enable such a world. Now, all the dots connect. The Hyperspace AI OS would give the power of a supercomputer in everyone’s hands. This isn’t a browser, or an IDE or limited to any device or cloud. It’s an entire AI operating system — with a breakthrough new spatial UI, local and distributed compute, agentic memory, agentic payments, and orchestration built into the foundation. As a user, we move the choice back in your hands with an experience you will love and find delightful. You get to choose the level of privacy, cost, and utility you want. And while Apple should have done it, we could not wait, and we feel this just required a new level of passion and DNA which we bring here. We are just getting started. Thank you, Varun Mathur Cofounder and CEO, Hyperspace cc Naval Marc Andreessen 🇺🇸 Vinod Khosla Andrej Karpathy Sam Altman
2:52

Hyperspace: The Agentic OS Apple Should Have Built On December 19th, 2024, we announced the world’s first Agentic Browser. What followed was a movement — a new category was born which led to many early products in this space and recently the hundreds of people lining up outside the The Agentic Browser Summit in San Francisco underscored that. Silicon Valley instinctively gets it, from students to tech executives, people can feel a revolutionary new change in computing is in the air. Past year taught us why such a product was inevitable, a hard engineering effort, and also the last mover in the entire software world this decade if and when done right. All paths are headed in the same direction: one tool which orchestrates them all. At Hyperspace we showed that path with essays and products we launched in earlier months: from a spatial UI of orchestrating agents, to showcasing transparent activity in how the AI system operates which leads to user trust, to presenting the software end-game, which massively improves human productivity. We also built the world’s largest AI network, drawing participation from people in almost 6000 cities around the world contributing their machines as nodes in the network. Think Uber, but for AI. That is, planetary-scale. And now we are stretching this industry ambition further with our end-to-end vision of the Agentic Supercomputer, the first breakthrough new AI OS, and an effort which spans from AI research to distributed systems to inventing a new UI to inventing a new business model to complement it. All of this together helps us in serving our mission, of delivering “Everyone’s Personal Supercomputer”. While others have built AI-native browsers, no one though has built something agentic from the ground up — with AI as the foundation, not a feature. How do you fundamentally improve the lives’ of billions around the world ? We believe that requires building a native environment for agents to be viewed, created, deployed, executed, discovered and priced in. That is a world where we move on from static apps, to dynamic agents. But, as my 2 year old niece likes to ask: “but why ?” The issue is that the world of software today is fragmented, and everyone is sprinkling on AI as a feature and charging a subscription fees for it. From browser makers, to IDEs, to design and other productivity tools. This leads to a fragmented UX, where people have to learn to use AI in each app, their memory and other context is not shared between all these apps, and they also have to pay separately for compute for each such AI-enhanced app. Each app maker has to figure out basics such as compute, and leads to the issues we saw with Cursor pricing recently. This is not the future. What if AI was the foundation instead of a feature ? What if Apple had built a fundamentally new AI OS from the ground up and what would it have looked like ? At Hyperspace, that is what we did. On July 15th we introduced three breakthrough key pillars of our AI OS: 1. Agentic Browser 2. Agentic Memory 3. Agentic Payments And we didn’t stop there. We also introduced a breakthrough new user interface called the Spatial AI which is inspired both from the spreadsheet and the HyperCard - each card is an agent, with it’s own inputs and outputs, endlessly extensible and pluggable with others, just like cells of a spreadsheet. Update one cell and all the dependents update, like a spreadsheet formula. It goes beyond a static linear workflow to being able to operate in all directions. This revolutionary new interface helps manage all of the below: 1. Multiple websites being browsed in parallel 2. Multiple desktop apps being browsed in parallel 3. Multiple server tools being used in parallel 4. Multiple smartphone apps streamed to your device or opened via an emulator All the software which you need comes together in this one seamless, agent-native interface. This interface provides you access to the largest network of models, vectors, agents and compute on the planet. The Browser. The IDE. The Notepad… they are not separate products: they are all in one, the Agentic Browser. As Steve Jobs famously said at the iPhone announcement, “are you getting it ?” And beneath this UI lies a new intelligence routing layer — leveraging both swarms of specialized models to the Hyperspace Matrix model that recalls thousands of tools in real-time, not by context window hacks, but through retrieval, ranking, and reuse. To many, this will feel like AGI. Not one big system by one big company, but an intelligent network. Now lets talk about privacy… Are you comfortable with one company owning all your memory forever ? I am not. So we have invented Agentic Memory as a new open protocol which provides full power over memory to you, the user. Your memory is yours, encrypted, on your device, and portable if and how you want. Anyone can build on it without our permission, but not without your permission. This protocol, and the decentralized vector database spread out across the world, would enable apps and agents to share context and memory. Think copy-paste, but for the AI world. It doesn’t just remember — it knows what matters. VectorRank helps your AI weigh your life’s most relevant moments over time, just like the way our minds elevate memories. Now each time you use an agent, your experience with other agents will also continuously improve: you don’t have to keep repeating the same things about yourself, while fully preserving your privacy. Agentic Memory is accessible within the Agentic Browser to manage. And there is one more thing… AI as the foundation requires compute to be available at the base layer, but this base layer spans models running on your own device, to cloud APIs, to also running across the peer-to-peer distributed network. Agentic Payments provides a singular interface to all of that compute, running a spot auction clearing marketplace every second to determine the fair price of compute. This results in price transparency, and you as the user paying the lowest possible cost. If you want predictability, you can reserve compute in advance. This end-to-end system provides the most streamlined world for agents to operate in. In order to enable this world and the world of agents being able to pay each other in sub-cent increments millions of times a second, we had to also invent a fundamentally new agentic micropayments blockchain. All of this together would enable a world where you as a user, or the agent itself, can efficiently call and utilize other agents built by others and also pay for content which is unique and useful. This enables a move away from the current AI exploitative economy for bloggers and other content creators, to a web with a fundamental new business model. Earlier we didn’t have the right infrastructure to enable such a world. Now, all the dots connect. The Hyperspace AI OS would give the power of a supercomputer in everyone’s hands. This isn’t a browser, or an IDE or limited to any device or cloud. It’s an entire AI operating system — with a breakthrough new spatial UI, local and distributed compute, agentic memory, agentic payments, and orchestration built into the foundation. As a user, we move the choice back in your hands with an experience you will love and find delightful. You get to choose the level of privacy, cost, and utility you want. And while Apple should have done it, we could not wait, and we feel this just required a new level of passion and DNA which we bring here. We are just getting started. Thank you, Varun Mathur Cofounder and CEO, Hyperspace cc Naval Marc Andreessen 🇺🇸 Vinod Khosla Andrej Karpathy Sam Altman

Varun

190,566 次观看 • 1 年前