Video wird geladen...

Video konnte nicht geladen werden

Zur Startseite

XR Animator EARLY ACCESS release (v0.37.2) ・💡Save/load different 3D camera📸 ・Improve processing speed of lip-sync ・Fix bug which broke pose switching ・Fix hotkey issues ・Update wLipSync (v1.3.0) #XRAnimator Details below🧵

butz_yung's profile picture

Butz Yung

5,097 subscribers

33,675 Aufrufe • vor 9 Monaten •via X (Twitter)

#XRAnimator
LIVE

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

XR Animator EARLY ACCESS release (v0.22.0) ・💡Support VRM model swapping ・💡Support QuickMagic motion FBX ・Update electron (v30.0.1) ・Various updates and bug fixes #XRAnimator #VTuber Details below👇🧵
2:19

XR Animator EARLY ACCESS release (v0.22.0) ・💡Support VRM model swapping ・💡Support QuickMagic motion FBX ・Update electron (v30.0.1) ・Various updates and bug fixes #XRAnimator #VTuber Details below👇🧵

Butz Yung

16,270 Aufrufe • vor 2 Jahren

XR Animator EARLY ACCESS release (v0.40.1) ・💡Add "Z smoothing" option for hip depth estimation ・Update depth estimation AI models ・Update electron (v43.1.1) ・Other bug fixes #XRAnimator Details below🧵
1:35

XR Animator EARLY ACCESS release (v0.40.1) ・💡Add "Z smoothing" option for hip depth estimation ・Update depth estimation AI models ・Update electron (v43.1.1) ・Other bug fixes #XRAnimator Details below🧵

Butz Yung

13,463 Aufrufe • vor 2 Monaten

XR Animator EARLY ACCESS release (v0.40.0) ・💡VMC receiver for mobile/web app ・💡"Webcam sharing" between remotely connected apps📷 ・"Disable AGC" setting for lip sync ・"Shoulder tracking" setting changed to percentage based ・Other bug fixes #XRAnimator Details below🧵
2:17

XR Animator EARLY ACCESS release (v0.40.0) ・💡VMC receiver for mobile/web app ・💡"Webcam sharing" between remotely connected apps📷 ・"Disable AGC" setting for lip sync ・"Shoulder tracking" setting changed to percentage based ・Other bug fixes #XRAnimator Details below🧵

Butz Yung

33,931 Aufrufe • vor 4 Monaten

XR Animator release (v0.19.6) ・💡Fix forearm twisting at extreme angles ・Support changing pose order via drag and drop ・Fix prop display issue when motion tracking is lost #XRAnimator #VTuber Details below👇🧵
1:58

XR Animator release (v0.19.6) ・💡Fix forearm twisting at extreme angles ・Support changing pose order via drag and drop ・Fix prop display issue when motion tracking is lost #XRAnimator #VTuber Details below👇🧵

Butz Yung

30,211 Aufrufe • vor 2 Jahren

XR Animator EARLY ACCESS release (v0.39.0) ・💡Remote control via WebSocket🛜 ・Full UI control via keyboard ・Flip bone transform received from VMC for VRM1 model ・Update electron/three-vrm ・Other bug fixes #XRAnimator Details below🧵
2:18

XR Animator EARLY ACCESS release (v0.39.0) ・💡Remote control via WebSocket🛜 ・Full UI control via keyboard ・Flip bone transform received from VMC for VRM1 model ・Update electron/three-vrm ・Other bug fixes #XRAnimator Details below🧵

Butz Yung

29,163 Aufrufe • vor 5 Monaten

XR Animator release (v0.15.0) ・💡Add shoulder and shrug tracking🤷 ・Adjust emotion tracking sensitivity ・Fix mocap data filter and reduce jitters ・Add tooltips for mocap options #XRAnimator #VTuber Details below👇🧵
1:47

XR Animator release (v0.15.0) ・💡Add shoulder and shrug tracking🤷 ・Adjust emotion tracking sensitivity ・Fix mocap data filter and reduce jitters ・Add tooltips for mocap options #XRAnimator #VTuber Details below👇🧵

Butz Yung

22,584 Aufrufe • vor 3 Jahren

XR Animator EARLY ACCESS release (v0.35.0) ・💡Mobile app for Android📱 ・💡New "Hand camera" supporting motion sensor ・💡Local web app on any OS ・VMC protocol via WebSocket ・"Shoulder angle offset" setting added ・Other updates and fixes #XRAnimator Details below🧵
2:18

XR Animator EARLY ACCESS release (v0.35.0) ・💡Mobile app for Android📱 ・💡New "Hand camera" supporting motion sensor ・💡Local web app on any OS ・VMC protocol via WebSocket ・"Shoulder angle offset" setting added ・Other updates and fixes #XRAnimator Details below🧵

Butz Yung

18,053 Aufrufe • vor 1 Jahr

XR Animator EARLY ACCESS release (v0.36.0) ・💡Animated 360° panorama ・💡Local web app for mobile ・Lite version body tracking (faster) ・"Inference device" setting for body tracking ・Setting to autoload face calibration ・Other updates & fixes #XRAnimator Details below🧵
2:19

XR Animator EARLY ACCESS release (v0.36.0) ・💡Animated 360° panorama ・💡Local web app for mobile ・Lite version body tracking (faster) ・"Inference device" setting for body tracking ・Setting to autoload face calibration ・Other updates & fixes #XRAnimator Details below🧵

Butz Yung

33,421 Aufrufe • vor 1 Jahr

NEW APP UPDATE! 👑 Update your apps, Kings. Release 2.5.0 is now available in app stores. This update introduces the fully revamped Destiny Attack mechanic, increases game speed, fixes numerous issues/bugs, and continues to optimize & improve the first-time user experience (FTUE). Upcoming releases will focus on further FTUE enhancement for new players, and continue to introduce new features aimed at early retention and stickiness — en route to scale as we strive to become the #1 Luck Battle game in mobile, supercharged by onchain features. NEW FEATURES — 👑 Revamped Destiny Attack: We've refreshed the Destiny Attack with updated animations, lightning effects, and improved audio for more immersive battles. 👑 Destiny Attack Multipliers: Rewards are now multiplied by your Deal Multiplier. 👑 Feature Map Widget: New animated map lets players track city progress and preview upcoming unlocks directly from the play screen. 👑 Customizable End-Of-Level Reward Chests: Complete cities to unlock bonus rewards, now delivered through a sleek new chest system that evolves with the player journey. 👑 Improved Offer Popups (Phase 1): Redesigned sales & limited-time offer popups to feature smoother transitions, cleaner visuals, and a better browsing experience. IMPROVEMENTS — ⚡️ 3-Sword Attack & Destiny Attack sequences can both now be skipped with a tap. ⚡️ City completion rewards are now configurable per city for better scaling (end-of-level rewards will be updated in the near future to better reward deeper game progression). ⚡️ Badge system & Avatar images now load faster. ⚡️ Sales popups now support multiple animation styles in higher resolution. ⚡️ Improved UI responsiveness across attacks, tutorials, and reward screens. ⚡️ Reduced app size to meet further reduce load time. BUG FIXES — 🐛 Fixed a bug where autodeal wasn't working for returning players. 🐛 Fixed a bug where Destiny Attacks were only granting coin rewards for some players. Rewards are now randomized based on the attack type. 🐛 Fixed a bug where the incorrect city was being shown during Destiny Attacks for certain existing players. 🐛 Fixed numerous minor bugs causing crashes for some players. Additionally, multiple different types of live ops have resumed for players. See you in the game, Kings!
0:41

NEW APP UPDATE! 👑 Update your apps, Kings. Release 2.5.0 is now available in app stores. This update introduces the fully revamped Destiny Attack mechanic, increases game speed, fixes numerous issues/bugs, and continues to optimize & improve the first-time user experience (FTUE). Upcoming releases will focus on further FTUE enhancement for new players, and continue to introduce new features aimed at early retention and stickiness — en route to scale as we strive to become the #1 Luck Battle game in mobile, supercharged by onchain features. NEW FEATURES — 👑 Revamped Destiny Attack: We've refreshed the Destiny Attack with updated animations, lightning effects, and improved audio for more immersive battles. 👑 Destiny Attack Multipliers: Rewards are now multiplied by your Deal Multiplier. 👑 Feature Map Widget: New animated map lets players track city progress and preview upcoming unlocks directly from the play screen. 👑 Customizable End-Of-Level Reward Chests: Complete cities to unlock bonus rewards, now delivered through a sleek new chest system that evolves with the player journey. 👑 Improved Offer Popups (Phase 1): Redesigned sales & limited-time offer popups to feature smoother transitions, cleaner visuals, and a better browsing experience. IMPROVEMENTS — ⚡️ 3-Sword Attack & Destiny Attack sequences can both now be skipped with a tap. ⚡️ City completion rewards are now configurable per city for better scaling (end-of-level rewards will be updated in the near future to better reward deeper game progression). ⚡️ Badge system & Avatar images now load faster. ⚡️ Sales popups now support multiple animation styles in higher resolution. ⚡️ Improved UI responsiveness across attacks, tutorials, and reward screens. ⚡️ Reduced app size to meet further reduce load time. BUG FIXES — 🐛 Fixed a bug where autodeal wasn't working for returning players. 🐛 Fixed a bug where Destiny Attacks were only granting coin rewards for some players. Rewards are now randomized based on the attack type. 🐛 Fixed a bug where the incorrect city was being shown during Destiny Attacks for certain existing players. 🐛 Fixed numerous minor bugs causing crashes for some players. Additionally, multiple different types of live ops have resumed for players. See you in the game, Kings!

King Of Destiny 👑

17,398 Aufrufe • vor 1 Jahr

Congratulations ZackeryFox🌏2️⃣👽 for your 2D concept art submission our team then took & brought to life in 3D for #Earth2🌍✌️This skin took longer given the detail & quality of the modelling but was definitely worth it! Read below for more important details & updates: The first variations of #CybercoreX will drop in about 8 hours. As mentioned in the article when we first started releasing skins, after #E2V1 officially launches we will be cutting back on #LimitedEdition skins & will predominantly focus on unlimited skins. In some cases these future unlimited skins will not be available for resale. This was always the plan as these early #LimitedEdition skins were released especially for early supporters. We will still release #LimitedEditions from time to time, but if & when we do so it will be at higher prices - which has also been mentioned numerous times in the past but I am just providing this as a reminder. I think we have 2-3 Limited Edition skins remaining before we transition into the standard skin system with unlimited skins & periodic availability - so there are not many left and these final Limited Edition drops will contain a few more rarer variations. #CybercoreX took a lot of additional work & team members strongly suggested the skin should be sold at a premium price, however I decided to keep the pricing in line with the other pre-#E2V1 Limited Edition releases. It is also important to note that as with many of the other Limited Edition skin releases with guns, the assault rifle & pistol will be sold separately. I'd also like to provide a quick update on the #E2V1 public release. The results from the initial testing group have been good so far, there are some issues we are working on fixing but nothing major. Considering it was our very first ever software release of the #Earth2 Launcher AND #E2V1, anyone with real experience releasing major software products would agree it went very smooth. Some #Players downloaded the launcher and were inside #E2V1 within 20 mins without any issues! You have major game or software developers releasing products after decades of experience & a million things go wrong .. often simple things .. our release was the dream type scenario & a real testament to our teams dedication, talent & ability! I'd like to include the option to spawn #avatars for the pre-alpha public release. The team has implemented the majority of this system with a few things remaining, which are actively being worked on at present. I just want to be clear that this NOT the avatar spawn system you have seen in demo videos to date where we just randomly spawn an avatar anywhere, that is simple & we could easily release that specific feature but it was only for demo purposes to showcase avatars can spawn anywhere in the world. To be transparent, what we are working to release now is the actual avatar spawn system intended for long term use where Players need to synthesise their #avatar from their #Mentar on their property to begin its actual life inside #E2V1. It's important to point out this involves numerous API integration, UI/UX updates and is not a simple random spawn. We anticipate there will almost surely be a number of potential bugs with this release so the plan is to first have it released to testers (WITH BUGS EXPECTED!) then stabilise & prepare for the public #E2V1 release. If you see people publishing footage of bugs online, remember we are in pre-alpha which we released to testers less than a month ago & testers are there to help us test and find issues we need to resolve. Our team is committed to fixing any major problems as they arise to improve the platform and keep moving forward. We should have avatars into the hands of testers this week. Remember, once you are inside your avatar you will not have that free camera flying ability. This makes teleportation very important for #Players who want to travel to different locations. So we will also need to start testing the teleportation system, and there is some potentially exciting news I have been keeping close to my chest which will soon be revealed. As always, thanks for your patience and support! Remember, we are literally less than one month since releasing #E2V1 to testers (less than a month ago there were still those who claimed we pre-rendered everything) so these are still early days! It may feel a little slow at first but we plan to release things to do inside of #E2V1 progressively and before you know it there will be too much to do! #Earth2 #Metaverse #E2V1
3:47

Congratulations ZackeryFox🌏2️⃣👽 for your 2D concept art submission our team then took & brought to life in 3D for #Earth2🌍✌️This skin took longer given the detail & quality of the modelling but was definitely worth it! Read below for more important details & updates: The first variations of #CybercoreX will drop in about 8 hours. As mentioned in the article when we first started releasing skins, after #E2V1 officially launches we will be cutting back on #LimitedEdition skins & will predominantly focus on unlimited skins. In some cases these future unlimited skins will not be available for resale. This was always the plan as these early #LimitedEdition skins were released especially for early supporters. We will still release #LimitedEditions from time to time, but if & when we do so it will be at higher prices - which has also been mentioned numerous times in the past but I am just providing this as a reminder. I think we have 2-3 Limited Edition skins remaining before we transition into the standard skin system with unlimited skins & periodic availability - so there are not many left and these final Limited Edition drops will contain a few more rarer variations. #CybercoreX took a lot of additional work & team members strongly suggested the skin should be sold at a premium price, however I decided to keep the pricing in line with the other pre-#E2V1 Limited Edition releases. It is also important to note that as with many of the other Limited Edition skin releases with guns, the assault rifle & pistol will be sold separately. I'd also like to provide a quick update on the #E2V1 public release. The results from the initial testing group have been good so far, there are some issues we are working on fixing but nothing major. Considering it was our very first ever software release of the #Earth2 Launcher AND #E2V1, anyone with real experience releasing major software products would agree it went very smooth. Some #Players downloaded the launcher and were inside #E2V1 within 20 mins without any issues! You have major game or software developers releasing products after decades of experience & a million things go wrong .. often simple things .. our release was the dream type scenario & a real testament to our teams dedication, talent & ability! I'd like to include the option to spawn #avatars for the pre-alpha public release. The team has implemented the majority of this system with a few things remaining, which are actively being worked on at present. I just want to be clear that this NOT the avatar spawn system you have seen in demo videos to date where we just randomly spawn an avatar anywhere, that is simple & we could easily release that specific feature but it was only for demo purposes to showcase avatars can spawn anywhere in the world. To be transparent, what we are working to release now is the actual avatar spawn system intended for long term use where Players need to synthesise their #avatar from their #Mentar on their property to begin its actual life inside #E2V1. It's important to point out this involves numerous API integration, UI/UX updates and is not a simple random spawn. We anticipate there will almost surely be a number of potential bugs with this release so the plan is to first have it released to testers (WITH BUGS EXPECTED!) then stabilise & prepare for the public #E2V1 release. If you see people publishing footage of bugs online, remember we are in pre-alpha which we released to testers less than a month ago & testers are there to help us test and find issues we need to resolve. Our team is committed to fixing any major problems as they arise to improve the platform and keep moving forward. We should have avatars into the hands of testers this week. Remember, once you are inside your avatar you will not have that free camera flying ability. This makes teleportation very important for #Players who want to travel to different locations. So we will also need to start testing the teleportation system, and there is some potentially exciting news I have been keeping close to my chest which will soon be revealed. As always, thanks for your patience and support! Remember, we are literally less than one month since releasing #E2V1 to testers (less than a month ago there were still those who claimed we pre-rendered everything) so these are still early days! It may feel a little slow at first but we plan to release things to do inside of #E2V1 progressively and before you know it there will be too much to do! #Earth2 #Metaverse #E2V1

Shane Isaac 🌍2️⃣

14,113 Aufrufe • vor 1 Jahr

ANNOUNCING: The Floki Trading Bot Closed Beta Mainnet Launch We’re pleased to announce the launch of the Closed Beta of the Floki Trading Bot on the mainnets of the Ethereum, BNB, and Base blockchains! The beta is currently open to an initial 150 users on a first come first served basis. The Floki Trading Bot is an innovative multi-chain Telegram on-chain trading bot designed to provide a seamless trading experience. With just a few taps, you can buy and sell cryptocurrencies in seconds across different chains. Our aim is to advance the way you trade, making it faster, easier, and more efficient. The Floki Trading Bot charges a 1% fee on every trade and uses FLOKI as its main utility token: 50% of this fee buys and burns $FLOKI, while the rest goes to the Floki Treasury. This will enhance the utility of the FLOKI token while accelerating its deflation. The closed beta will run for a period of two weeks, after which we intend to release a public version of the bot to everyone. Why a Closed Beta? The Closed Beta allows us to create a controlled environment where we can: - Identify and fix early bugs (should there be any!) - Collect invaluable user feedback to improve user experience - Validate our market assumptions Closed Beta User Assignments: - Submit at least 2 feedback/bug reports every week - Trade at least 4 times every week - Submit the End of Beta Survey (we will share it near the end of Closed Beta) Reward: Participants who complete the assignments will receive a reward in their Floki Trading Bot primary wallet at the end of the Closed Beta period. Details about the reward will be communicated later. 🚨 Safety Notice: Be vigilant against scam links/pages below that may appear similar to ours. Do not trust any messages regarding airdrops or asking you to connect your wallet to any site. Stay safe and beware of fraudulent activities. Join the Closed Beta Waitlist To join the Closed Beta, please use the link below: You can read the Floki Trading Bot documentation here: We look forward to having you onboard and hearing your feedback as we continue to aggressively expand the Floki ecosystem and work toward becoming the world's most known and used cryptocurrency.
1:00

ANNOUNCING: The Floki Trading Bot Closed Beta Mainnet Launch We’re pleased to announce the launch of the Closed Beta of the Floki Trading Bot on the mainnets of the Ethereum, BNB, and Base blockchains! The beta is currently open to an initial 150 users on a first come first served basis. The Floki Trading Bot is an innovative multi-chain Telegram on-chain trading bot designed to provide a seamless trading experience. With just a few taps, you can buy and sell cryptocurrencies in seconds across different chains. Our aim is to advance the way you trade, making it faster, easier, and more efficient. The Floki Trading Bot charges a 1% fee on every trade and uses FLOKI as its main utility token: 50% of this fee buys and burns $FLOKI, while the rest goes to the Floki Treasury. This will enhance the utility of the FLOKI token while accelerating its deflation. The closed beta will run for a period of two weeks, after which we intend to release a public version of the bot to everyone. Why a Closed Beta? The Closed Beta allows us to create a controlled environment where we can: - Identify and fix early bugs (should there be any!) - Collect invaluable user feedback to improve user experience - Validate our market assumptions Closed Beta User Assignments: - Submit at least 2 feedback/bug reports every week - Trade at least 4 times every week - Submit the End of Beta Survey (we will share it near the end of Closed Beta) Reward: Participants who complete the assignments will receive a reward in their Floki Trading Bot primary wallet at the end of the Closed Beta period. Details about the reward will be communicated later. 🚨 Safety Notice: Be vigilant against scam links/pages below that may appear similar to ours. Do not trust any messages regarding airdrops or asking you to connect your wallet to any site. Stay safe and beware of fraudulent activities. Join the Closed Beta Waitlist To join the Closed Beta, please use the link below: You can read the Floki Trading Bot documentation here: We look forward to having you onboard and hearing your feedback as we continue to aggressively expand the Floki ecosystem and work toward becoming the world's most known and used cryptocurrency.

FLOKI

327,039 Aufrufe • vor 2 Jahren

🚨#Earth2 update 🌏✌️ First I'd like to apologise to our community for the lateness of this message. I was still considering a traditional last timezone #Q2 release but honestly we could use a little more time. As you can see in the screen recording, we've been extremely busy the past 3 months with multiple commits per day on average from our dev team & this recording is only of commits made directly to our #E2V1 repository. It does not include #BE / Server repository commits or tasks completed for custom development from our VFX, SFX, Concept Art & Animation teams or the countless other points of progressive development. While there are some in our community who would better understand what multiple daily repo commits means, the video footage just helps others to visualise how much work goes into the development of just one facet of Earth 2, and even though we may not publish a lot of public updates, we are extremely busy & focused on development & progress behind the scenes. Sometimes you lose track of time with so many different developments in progress. Excitingly for everyone, Chapter 1 is a very big release for us & includes some very important updates that will introduce the foundations for activity & experiences inside #E2V1. There are many moving parts & many new mechanisms we've had to design, develop & implement into an incredibly large, seamless, open world just to make Chapter 1 possible. We're also building a persistent world, meaning we're not just developing for a single player local PC environment, which would be much, much easier, but instead requires a lot of API & server integration for almost every feature implemented - and that doesn't even involve the multiplayer networking element which we've also made good progress on throughout #Q2. We're not implementing API & server integration only for a persistent world, but also to mitigate against hacking. I just wanted to provide this update & apologise for the lateness of this notification. Remember, we are still in a pre-alpha stage so there are inevitably going to be bugs & issues. Seeing as though we are going to miss #Q2 anyway, we could use another week or two to fix some known bugs & make it a little smoother. It won't be longer than that & even though it's not a lot of additional time in the big picture, I still said #Q2 & I apologise that we are going to overshoot that time frame. We will aim to publish an article this weekend to provide everyone with an in depth explanation behind the early access release & I think that article will help our community understand just how much work has gone into the past 3 months by our team. I guess I could have made this post short & sweet but I wanted to provide additional context so thanks for reading through. To end on a more positive note, hands on play testing has been very eye opening to possibilities & immersion #E2V1 offers. There are so many opportunities waiting & so many directions to take .. it really is very exciting. Another positive point is I believe this will be the final quarter of waiting in boredom / pain as moving forward we'll have feet on the ground inside #E2V1 & once it is stable we will be able to release subsequent updates faster. #Earth2 #Metaverse #RealityThreads #E2V1 #PreAlpha
1:54

🚨#Earth2 update 🌏✌️ First I'd like to apologise to our community for the lateness of this message. I was still considering a traditional last timezone #Q2 release but honestly we could use a little more time. As you can see in the screen recording, we've been extremely busy the past 3 months with multiple commits per day on average from our dev team & this recording is only of commits made directly to our #E2V1 repository. It does not include #BE / Server repository commits or tasks completed for custom development from our VFX, SFX, Concept Art & Animation teams or the countless other points of progressive development. While there are some in our community who would better understand what multiple daily repo commits means, the video footage just helps others to visualise how much work goes into the development of just one facet of Earth 2, and even though we may not publish a lot of public updates, we are extremely busy & focused on development & progress behind the scenes. Sometimes you lose track of time with so many different developments in progress. Excitingly for everyone, Chapter 1 is a very big release for us & includes some very important updates that will introduce the foundations for activity & experiences inside #E2V1. There are many moving parts & many new mechanisms we've had to design, develop & implement into an incredibly large, seamless, open world just to make Chapter 1 possible. We're also building a persistent world, meaning we're not just developing for a single player local PC environment, which would be much, much easier, but instead requires a lot of API & server integration for almost every feature implemented - and that doesn't even involve the multiplayer networking element which we've also made good progress on throughout #Q2. We're not implementing API & server integration only for a persistent world, but also to mitigate against hacking. I just wanted to provide this update & apologise for the lateness of this notification. Remember, we are still in a pre-alpha stage so there are inevitably going to be bugs & issues. Seeing as though we are going to miss #Q2 anyway, we could use another week or two to fix some known bugs & make it a little smoother. It won't be longer than that & even though it's not a lot of additional time in the big picture, I still said #Q2 & I apologise that we are going to overshoot that time frame. We will aim to publish an article this weekend to provide everyone with an in depth explanation behind the early access release & I think that article will help our community understand just how much work has gone into the past 3 months by our team. I guess I could have made this post short & sweet but I wanted to provide additional context so thanks for reading through. To end on a more positive note, hands on play testing has been very eye opening to possibilities & immersion #E2V1 offers. There are so many opportunities waiting & so many directions to take .. it really is very exciting. Another positive point is I believe this will be the final quarter of waiting in boredom / pain as moving forward we'll have feet on the ground inside #E2V1 & once it is stable we will be able to release subsequent updates faster. #Earth2 #Metaverse #RealityThreads #E2V1 #PreAlpha

Shane Isaac 🌍2️⃣

15,193 Aufrufe • vor 1 Jahr

Guess it's that time of year again... The post to Start the rest of the "Star Citizen has raised 900 million and is still in alpha" posts 🤦🏽‍♂️.. monkey see monkey do... Followed by people looking for the highest priced ships to post... Conveniently leaving out the fact you can spend 30$ one time and spend anothet time after that because you can buy almost all ships in game currently with in game money. The game finished Kickstarter the end of 2012 with sky high promises, the game of a man who is a perfectionist and who has a massive vision. Has Star Citizen been managed well over the years? No, we got a hangar module in August of 2013 to let us walk around and view our ships. 2 years later The first iteration of the Persistent universe went live in August 2015 for the first time, here are the major milestones, The initial version of the Star Citizen Persistent Universe (PU) was first made available to backers as part of the Alpha 2.0 release in December 2015. This version was a huge deal, it's the release that combined several gameplay elements and introduced a persistent, multiplayer environment. The PU has been in an alpha, or early access, state ever since and continues to receive Monthly updates and new features with major milestone patches.. Below is a chronological list if all major patches . There have been a ton of "smaller ones" but each has brought new tech, features and improvements as well as bugs Alpha 2.0 (December 2015): The initial release, which allowed players to spawn at Port Olisar and introduced an early version of the persistent, multiplayer universe around the planet Crusader and its moons. Alpha 3.0 (December 2017): This update was considered a major core technology milestone, introducing features like planetary procedural technology, truly SEAMLESS atmospheric entry, cargo trading, and the addition of the Hurston system. Alpha 3.18 (March 2023) Implemented the Persistent Entity Streaming (PES) technology, a significant technical step that allows the game to track every item and ship across all servers, greatly enhancing the level of world persistence. Alpha 4.0 (Q4 2024) Introduced the second full star system, Pyro, which required the implementation of static server meshing technology to seamlessly link different servers. Alpha 4.0 and subsequent. Patches have brought tons of features, missions, activities, sandbox missions during it's. Course.. Today 2026 - Patch 4.4 is in development, currently being tested by us (the backers) which brings with it our 3rd Star Citizen, Nyx and Vanduul. NPCs (hostile aliens) once the NYX planets (specifically NYX 1)are patched in, that will bring with it the Genesis technology, the name is very bit a reference to the same technology from Star trek . We call it Planet Tech V5 which brings planetary visuals, interaction, biomes, textures, lighting, atmospherics an order of magnitude higher then what it already is. while Star Citizen is far from perfect and has had its massive share of growing pains and missteps.. Chris Roberts vision still lives and is in a better state then it's ever been for most of us. It's only getting better, this isn't meant to persuade anyone to play it's just mean to give you some info for those that care or are curious. Before you slander a game, atleast have enough respect to the developers who really bust thier ass day in and at out to bring this game to life.. To fix things, design weapons, ships, space etc. Video below was cut and put together from the Official to clip everything together and it shows NYX 1 Running the Genesis technology KungLi . Like the matrix no one can be told what Star Citizen is.. They need to see it for themselves to understand, The Visuals.. Flying from Space, through the atmosphere then landing anywhere you want, whenever you want, seeing the Star rise over the horizon.. #StarCitizen is beautiful IAE 2955 Event Comming up Nov 10th to Dec 5th, play and fly for free and try it
5:00

Guess it's that time of year again... The post to Start the rest of the "Star Citizen has raised 900 million and is still in alpha" posts 🤦🏽‍♂️.. monkey see monkey do... Followed by people looking for the highest priced ships to post... Conveniently leaving out the fact you can spend 30$ one time and spend anothet time after that because you can buy almost all ships in game currently with in game money. The game finished Kickstarter the end of 2012 with sky high promises, the game of a man who is a perfectionist and who has a massive vision. Has Star Citizen been managed well over the years? No, we got a hangar module in August of 2013 to let us walk around and view our ships. 2 years later The first iteration of the Persistent universe went live in August 2015 for the first time, here are the major milestones, The initial version of the Star Citizen Persistent Universe (PU) was first made available to backers as part of the Alpha 2.0 release in December 2015. This version was a huge deal, it's the release that combined several gameplay elements and introduced a persistent, multiplayer environment. The PU has been in an alpha, or early access, state ever since and continues to receive Monthly updates and new features with major milestone patches.. Below is a chronological list if all major patches . There have been a ton of "smaller ones" but each has brought new tech, features and improvements as well as bugs Alpha 2.0 (December 2015): The initial release, which allowed players to spawn at Port Olisar and introduced an early version of the persistent, multiplayer universe around the planet Crusader and its moons. Alpha 3.0 (December 2017): This update was considered a major core technology milestone, introducing features like planetary procedural technology, truly SEAMLESS atmospheric entry, cargo trading, and the addition of the Hurston system. Alpha 3.18 (March 2023) Implemented the Persistent Entity Streaming (PES) technology, a significant technical step that allows the game to track every item and ship across all servers, greatly enhancing the level of world persistence. Alpha 4.0 (Q4 2024) Introduced the second full star system, Pyro, which required the implementation of static server meshing technology to seamlessly link different servers. Alpha 4.0 and subsequent. Patches have brought tons of features, missions, activities, sandbox missions during it's. Course.. Today 2026 - Patch 4.4 is in development, currently being tested by us (the backers) which brings with it our 3rd Star Citizen, Nyx and Vanduul. NPCs (hostile aliens) once the NYX planets (specifically NYX 1)are patched in, that will bring with it the Genesis technology, the name is very bit a reference to the same technology from Star trek . We call it Planet Tech V5 which brings planetary visuals, interaction, biomes, textures, lighting, atmospherics an order of magnitude higher then what it already is. while Star Citizen is far from perfect and has had its massive share of growing pains and missteps.. Chris Roberts vision still lives and is in a better state then it's ever been for most of us. It's only getting better, this isn't meant to persuade anyone to play it's just mean to give you some info for those that care or are curious. Before you slander a game, atleast have enough respect to the developers who really bust thier ass day in and at out to bring this game to life.. To fix things, design weapons, ships, space etc. Video below was cut and put together from the Official to clip everything together and it shows NYX 1 Running the Genesis technology KungLi . Like the matrix no one can be told what Star Citizen is.. They need to see it for themselves to understand, The Visuals.. Flying from Space, through the atmosphere then landing anywhere you want, whenever you want, seeing the Star rise over the horizon.. #StarCitizen is beautiful IAE 2955 Event Comming up Nov 10th to Dec 5th, play and fly for free and try it

Citizen_of_the_Verse

51,214 Aufrufe • vor 10 Monaten

The disgustingly simple framework behind my best performing thumbnails (1.7M, 1M views) This is the exact method I used for thumbnails on my best performing videos I call it the "analyze-recreate" method: 1. Search YouTube for your video title 2. Find the top performing video 3. Copy their thumbnail image 4. Send it to Claude/GPT with this prompt (steal this): ---- You are a YouTube thumbnail visual analysis expert. Analyze only what is visible in the provided thumbnail. Do not infer identities, brands, context, or any off-frame elements. Output must be plaintext and under 1800 characters. Keep it concise and directly usable for recreating a similar image. Important: Do NOT reference, describe, paraphrase, or characterize any text, typography, logos, watermarks, UI, arrows, icons, or other graphic design overlays. Focus only on the underlying photographic/illustrative scene and its composition. Cover exactly these sections: 1. Overall Style: mood, tone, realism level, and artistic approach (photo, 3D, illustration, composite). 2. Color Palette: 2–3 dominant colors and where they appear (brief; no hex). 3. Composition: camera angle/shot type (close/medium/wide), depth (foreground/mid/background), focal point, balance, and approximate % of frame occupied by each main scene element. 4. Main Subjects: describe visible characters/objects only, pose/expression, size relative to frame, and key environment/background elements. 5. Lighting & Post: lighting type and direction, shadow softness, contrast, depth of field, and noticeable post-processing (very short). 6. AI Prompt Suggestion: a compact generation prompt describing the scene + composition + mood + rendering style; do not list colors; do not include any text/logo/overlay instructions. Write the analysis now: ---- Paste the output into an AI image generator (Nano Banana, etc.) Add your text/graphics manually - I use autotube's built-in thumbnail designer which makes this easy The key is: you're recreating the image from scratch, not stealing. You're analyzing what works and building your own version - while avoiding copyright issues It might take 5-10 generations to nail it. Different AI models handle different styles better, so experiment YouTube is a game of copy/paste, so stick to what has been proven to work by your competitors instead of reinventing the wheel Shout out to the channels BEFORE CITIES, Woke up History, Sleepless Homo, Ancestor Vault among others, who were a big inspiration for this channel The above method was the one I used most of the time for Sleepy Time History, but recently I switched to something crazier: fully AI driven thumbnail generation. AI creates 5 thumbnails based on a "thumbnail design language" based on your channel's 15 best thumbnails So far so good, but this is more experimental, and mostly to save time while I focus on new channels I built autotube to automate the entire YouTube workflow: thumbnails, scripts, rendering, everything. Works well for sleep channels and other ai image/video slideshows. We're gradually opening up access. Link in bio
0:25

The disgustingly simple framework behind my best performing thumbnails (1.7M, 1M views) This is the exact method I used for thumbnails on my best performing videos I call it the "analyze-recreate" method: 1. Search YouTube for your video title 2. Find the top performing video 3. Copy their thumbnail image 4. Send it to Claude/GPT with this prompt (steal this): ---- You are a YouTube thumbnail visual analysis expert. Analyze only what is visible in the provided thumbnail. Do not infer identities, brands, context, or any off-frame elements. Output must be plaintext and under 1800 characters. Keep it concise and directly usable for recreating a similar image. Important: Do NOT reference, describe, paraphrase, or characterize any text, typography, logos, watermarks, UI, arrows, icons, or other graphic design overlays. Focus only on the underlying photographic/illustrative scene and its composition. Cover exactly these sections: 1. Overall Style: mood, tone, realism level, and artistic approach (photo, 3D, illustration, composite). 2. Color Palette: 2–3 dominant colors and where they appear (brief; no hex). 3. Composition: camera angle/shot type (close/medium/wide), depth (foreground/mid/background), focal point, balance, and approximate % of frame occupied by each main scene element. 4. Main Subjects: describe visible characters/objects only, pose/expression, size relative to frame, and key environment/background elements. 5. Lighting & Post: lighting type and direction, shadow softness, contrast, depth of field, and noticeable post-processing (very short). 6. AI Prompt Suggestion: a compact generation prompt describing the scene + composition + mood + rendering style; do not list colors; do not include any text/logo/overlay instructions. Write the analysis now: ---- Paste the output into an AI image generator (Nano Banana, etc.) Add your text/graphics manually - I use autotube's built-in thumbnail designer which makes this easy The key is: you're recreating the image from scratch, not stealing. You're analyzing what works and building your own version - while avoiding copyright issues It might take 5-10 generations to nail it. Different AI models handle different styles better, so experiment YouTube is a game of copy/paste, so stick to what has been proven to work by your competitors instead of reinventing the wheel Shout out to the channels BEFORE CITIES, Woke up History, Sleepless Homo, Ancestor Vault among others, who were a big inspiration for this channel The above method was the one I used most of the time for Sleepy Time History, but recently I switched to something crazier: fully AI driven thumbnail generation. AI creates 5 thumbnails based on a "thumbnail design language" based on your channel's 15 best thumbnails So far so good, but this is more experimental, and mostly to save time while I focus on new channels I built autotube to automate the entire YouTube workflow: thumbnails, scripts, rendering, everything. Works well for sleep channels and other ai image/video slideshows. We're gradually opening up access. Link in bio

facelessjourney | YTA & SaaS

13,259 Aufrufe • vor 5 Monaten

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.
0:38

I finally finished my Rust version of Mario Zechner's (Mario Zechner) excellent Pi Agent, which I made with his blessing and which is called pi_agent_rust. You can get it here: If you're not familiar with Pi, it's a minimalist and extensible agent harness (similar to Claude Code and Codex) and, among other uses, serves as the core agent harness inside the OpenClaw project. I say my Rust "version" instead of "port" because it's really quite different in how it's implemented for it to be called a port. Arguably, the incremental functionality in the implementation was more complex than the rest of the project combined. Still, it provides the same features and functionality as the original, and is proven to be compatible with hundreds of popular extensions to Pi (the conformance harness shows 224 out of 224 extensions working perfectly). But the way it's architected has some major changes. Pi Agent relies on node or bun to provide access to the filesystem and for various other tasks, and that is also how Pi's extension system works. I decided early on that I didn't want to do things that way. Instead, I wanted to integrate that functionality directly into the binary itself; that is, to provide equivalent functionality for everything that would normally be provided by node/bun in the original. I did this for several reasons: one, it's a lot more performant in terms of footprint and latency. On realistic end-to-end large-session workloads (not toy microbenchmarks), pi_agent_rust is now: - 4.95x faster than legacy Node and 2.80x faster than legacy Bun at 1mm-token session scale - 4.32x faster than legacy Node and 2.14x faster than legacy Bun at 5mm-token session scale - ~8x to ~13x lower RSS memory footprint in those same scenarios But the other reason is security and control: by handling everything internally in an end-to-end way, we can do all sorts of clever things to harden the system against insecure or malicious extensions. Those extensions no longer have direct access to the ambient filesystem: they now need to go through pi_agent_rust, and we can analyze extensions carefully before ever running them and also block things that look suspicious at runtime. In practice that means explicit capability-gated hostcalls, with policy/risk/quota enforcement and runtime telemetry/auditability. In order to do all this, I had to effectively build the missing runtime substrate from scratch in Rust, not just translate TypeScript syntax: - define and implement a typed hostcall ABI for extension->host interactions - build native Rust connectors for tool/exec/http/session/ui/events instead of ambient Node/Bun access - implement a compatibility/shim layer so real-world Pi extensions still behave correctly - add capability policy evaluation, runtime risk scoring, per-extension quotas, and audit telemetry on the execution path - wire the whole thing through structured concurrency (asupersync) so cancellation/lifetimes are deterministic and failure handling is explicit - build a conformance + benchmark harness large enough to validate behavior/perf across hundreds of extensions and realistic long-session workloads This was a full re-architecture of the execution model while preserving the Pi workflow and extension ecosystem. And indeed, this aspect of it dwarfs the entire rest of the project in size and complexity. To put hard numbers on that: the extension/runtime/security subsystem alone is now about 86.5k lines of Rust across src/extensions.rs (~48.1k), src/extensions_js.rs (~23.4k), src/extension_dispatcher.rs (~13.4k), and src/extension_index.rs (~1.7k), with roughly 2.5k callable units in just those files. For context, the original Pi coding-agent production code is about 27.4k lines total. So this one subsystem by itself is roughly 3.2x the size of the original harness, which is why calling this a “port” would seriously undersell what had to be built. And on top of that, pi_agent_rust introduces a bunch of genuinely new capabilities beyond the legacy harness, not just a faster core: - Security and enforcement are materially stronger at runtime: capability-gated hostcalls with explicit policy profiles (safe/balanced/permissive), per-extension trust lifecycle (pending -> acknowledged -> trusted -> killed), explicit kill-switch operations, and audited state transitions. - Shell execution mediation is deterministic and argument-aware: rule/feature-based risk scoring plus heredoc AST inspection (dcg_rule_hit, dcg_heredoc_hit) before spawn, instead of relying on coarse deny patterns. - Containment and forensics are first-class: tamper-evident runtime risk ledger tooling (verify/replay/calibrate), unified incident evidence bundles, and forced-compat controls that let you contain issues without disabling the whole extension system. - The extension runtime architecture is native: JS extensions run in embedded QuickJS with typed hostcall boundaries and Rust-native connectors for tool/exec/http/session/ui/events, plus compatibility shims for real-world legacy extensions. - Runtime behavior under load is explicitly engineered: deterministic hostcall reactor mesh, fast-lane vs compat-lane routing, and warm-isolate prewarm handoff for more predictable throughput and latency under contention. - Long-session reliability is upgraded: JSONL v3 sessions with indexed sidecar acceleration and optional SQLite-backed sessions, plus operational controls via --session-durability, --no-migrations, and migrate. - Provider and auth coverage are broader and more operationally explicit: native Anthropic/OpenAI (Chat + Responses)/Gemini/Cohere/Azure/Bedrock/Vertex/Copilot/GitLab plus large OpenAI-compatible routing; pi --list-providers currently shows 90 providers with aliases and required auth env keys. - Auth is not just API keys: OAuth (Anthropic/OpenAI Codex/Gemini CLI/Antigravity/Kimi/Copilot/GitLab plus extension-defined OAuth), AWS credential chains (Bedrock), service-key exchange (SAP AI Core), and bearer-token flows. - Operator tooling is stronger: pi doctor supports scoped checks (config, dirs, auth, shell, sessions, extensions), machine-readable output (--format json|markdown), and safe auto-remediation (--fix). - Extension/package lifecycle workflows are built in: install, remove, update, update-index, search, info, and list. I want to thank Mario for making a great harness and for not telling me to get lost when I asked him if he was OK with me porting it to Rust. I may give him a hard time in jest about not going "full clanker," but that doesn't mean that I don't respect his work a huge amount. PS: There could still be bugs. If you find some, please let me know in GitHub Issues and I'll fix them same day. There's always a tradeoff between perfect and getting stuff out the door and I felt like it was time to release this.

Jeffrey Emanuel

136,133 Aufrufe • vor 7 Monaten

Recently I got some hands-on time with Crimson Desert and below are my first impressions as well as some of the gameplay I was able to capture. Crimson Desert is a good game, but it won’t be for everyone. I know the devs claim this isn’t an RPG, but I don’t know any other way to describe this game other than a HARDCORE action RPG. If you need the yellow paint to know where to climb this game isn’t for you. But if you love getting lost in a whimsical world with a boat load of content this game is going to be right up your alley. I think what impressed me most is the attention to detail. There’s so many little things the dev team took into consideration that I think people who enjoy being immersed into a world are going to appreciate. Even if you aren’t that person; on a basic level I think most will enjoy the game's combat. It’s fast, fluid and provides a ton of player expression with its deep skill tree. The world of Pywel is vibrant, large in scale and full of life. It’s easy to get lost off the main quest line as there’s always something to do and someone to speak to. An example being I was wandering through the open world and encountered a distressed woman seeking help. I agreed to follow her only to find out moments later she was with a gang and they were trying to back door me. That had me cracking up. I think if the open world is consistently full of fun, unique side content like that & the main quest line is fire this game has a lot of potential to impress. It’s just a shame that I didn’t get to spend more time with the main quests as I kept getting side tracked with cool stuff to do in the open world. So I can’t give you much insight into that. What I can say is after the opening section there’s NEXT TO NO tutorials in this game, the puzzles are hard & the default controls are a bit clunky. You will be getting lost and I can see that frustrating some people who aren’t interested in a challenge. That’s why I mentioned earlier that this is a hardcore RPG. It does not do a lot of hand holding. Because of that I predict you and your friends will be sharing tips and tricks similar to when Elden Ring first launched and nobody knew what they were doing. If you are a patient person and take the time to learn the game's systems I promise you will be able to put together some awesome combos that will make you feel like the main character. My biggest fear for this game is that I won't finish it. Not because it’s a bad game, but I can just tell from my brief time with it that it’s next level massive. As someone who's been gaming for 30+ years it’s very rare you’ll hear me say a game was overwhelming, but this game is. For people who lack a ton of free time I can see that being a turn off because once again the game doesn’t give much direction or tutorials outside the opening area. Not to mention this game could be big just for the sake of being big. I was curious to know how much of the content was engaging versus just open world bloat? Hard to tell because I only got a few hours with the game. I also fear that the Ai isn’t the best in this game. The Ai issues I encountered zapped all immersion away for those moments. I’m not sure if the final build will differ from the vertical slice we played, but what I can tell you is that on the build we played I wasn’t impressed by the Ai. Several times I attacked enemy camps and they never reacted to me attacking them. They just stood there and took it which made the world feel less alive. There were also times where enemies were looking dead at me just standing still as the battle music played threatening to beat me up, but they never did anything. It was 3 or 4 times I encountered this poor Ai which is a red flag for me because I only got two hours of hands on time with the game. Mind you in those two hours a good portion of it was just me working my way through the prologue and the early quests, so I didn't spend a ton of time in the open world. What I'm trying to get at is the janky ai was very noticeable. It wasn't something that took long to find. I will say when the game works it's great, but when I tell you the Ai was bad at times it was bad. It reminded me of the dumb NPC’s often found in Ubisoft open world games. I’m not looking for this to be a Souls game but I want some level of challenge in the combat. Hopefully that stuff gets patched out. That being said, I’m confident in saying this game is good. I just didn’t have enough time with it to determine if it’s good, or GREAT. Only time will tell when Crimson Desert drops on March 19th, 2026 for the PC, PS5 and Xbox Series. Pros —---------- - Combat makes you feel like demon - Deep Skill tree - Vibrant world - Solid voice acting - Fire OST - The little details (trust system, you can commit crimes ect.) - No Fall damage - Puzzles are creative & challenging - Game doesn’t hold you hand (some people will hate this) - You can swap in and out of 3rd and 1st person at will. Wasn’t able to explore much of how that changes the game, but it’s nice that it's an option. - EASILY over 100hrs of content (some will hate this though) Cons —---------- - Clunky controls (Default controls take some time adjusting too. I hope there’s other control schemes at launch) - Inconsistent Ai (Ubisoft bad at times. sometimes the enemies wouldn’t attack during combat or act like they never saw you) - Long load times (we were playing on PC’s, but idk the specs) - Your horse can faint & when they do traveling the large world wasn’t as fun (and I couldn’t figure out how to get him back - most likely a skill issue) - Early stamina management is OD. Early game it’s easy to drown & get tired running. I’d imagine it gets better late game, but early game it’s frustrating trying to explore. - Camera takes some getting used to in combat. Sometimes its too close and others too far. - Early arrows have no impact. Felt useless. Hoping later upgrades fix that
3:17

Recently I got some hands-on time with Crimson Desert and below are my first impressions as well as some of the gameplay I was able to capture. Crimson Desert is a good game, but it won’t be for everyone. I know the devs claim this isn’t an RPG, but I don’t know any other way to describe this game other than a HARDCORE action RPG. If you need the yellow paint to know where to climb this game isn’t for you. But if you love getting lost in a whimsical world with a boat load of content this game is going to be right up your alley. I think what impressed me most is the attention to detail. There’s so many little things the dev team took into consideration that I think people who enjoy being immersed into a world are going to appreciate. Even if you aren’t that person; on a basic level I think most will enjoy the game's combat. It’s fast, fluid and provides a ton of player expression with its deep skill tree. The world of Pywel is vibrant, large in scale and full of life. It’s easy to get lost off the main quest line as there’s always something to do and someone to speak to. An example being I was wandering through the open world and encountered a distressed woman seeking help. I agreed to follow her only to find out moments later she was with a gang and they were trying to back door me. That had me cracking up. I think if the open world is consistently full of fun, unique side content like that & the main quest line is fire this game has a lot of potential to impress. It’s just a shame that I didn’t get to spend more time with the main quests as I kept getting side tracked with cool stuff to do in the open world. So I can’t give you much insight into that. What I can say is after the opening section there’s NEXT TO NO tutorials in this game, the puzzles are hard & the default controls are a bit clunky. You will be getting lost and I can see that frustrating some people who aren’t interested in a challenge. That’s why I mentioned earlier that this is a hardcore RPG. It does not do a lot of hand holding. Because of that I predict you and your friends will be sharing tips and tricks similar to when Elden Ring first launched and nobody knew what they were doing. If you are a patient person and take the time to learn the game's systems I promise you will be able to put together some awesome combos that will make you feel like the main character. My biggest fear for this game is that I won't finish it. Not because it’s a bad game, but I can just tell from my brief time with it that it’s next level massive. As someone who's been gaming for 30+ years it’s very rare you’ll hear me say a game was overwhelming, but this game is. For people who lack a ton of free time I can see that being a turn off because once again the game doesn’t give much direction or tutorials outside the opening area. Not to mention this game could be big just for the sake of being big. I was curious to know how much of the content was engaging versus just open world bloat? Hard to tell because I only got a few hours with the game. I also fear that the Ai isn’t the best in this game. The Ai issues I encountered zapped all immersion away for those moments. I’m not sure if the final build will differ from the vertical slice we played, but what I can tell you is that on the build we played I wasn’t impressed by the Ai. Several times I attacked enemy camps and they never reacted to me attacking them. They just stood there and took it which made the world feel less alive. There were also times where enemies were looking dead at me just standing still as the battle music played threatening to beat me up, but they never did anything. It was 3 or 4 times I encountered this poor Ai which is a red flag for me because I only got two hours of hands on time with the game. Mind you in those two hours a good portion of it was just me working my way through the prologue and the early quests, so I didn't spend a ton of time in the open world. What I'm trying to get at is the janky ai was very noticeable. It wasn't something that took long to find. I will say when the game works it's great, but when I tell you the Ai was bad at times it was bad. It reminded me of the dumb NPC’s often found in Ubisoft open world games. I’m not looking for this to be a Souls game but I want some level of challenge in the combat. Hopefully that stuff gets patched out. That being said, I’m confident in saying this game is good. I just didn’t have enough time with it to determine if it’s good, or GREAT. Only time will tell when Crimson Desert drops on March 19th, 2026 for the PC, PS5 and Xbox Series. Pros —---------- - Combat makes you feel like demon - Deep Skill tree - Vibrant world - Solid voice acting - Fire OST - The little details (trust system, you can commit crimes ect.) - No Fall damage - Puzzles are creative & challenging - Game doesn’t hold you hand (some people will hate this) - You can swap in and out of 3rd and 1st person at will. Wasn’t able to explore much of how that changes the game, but it’s nice that it's an option. - EASILY over 100hrs of content (some will hate this though) Cons —---------- - Clunky controls (Default controls take some time adjusting too. I hope there’s other control schemes at launch) - Inconsistent Ai (Ubisoft bad at times. sometimes the enemies wouldn’t attack during combat or act like they never saw you) - Long load times (we were playing on PC’s, but idk the specs) - Your horse can faint & when they do traveling the large world wasn’t as fun (and I couldn’t figure out how to get him back - most likely a skill issue) - Early stamina management is OD. Early game it’s easy to drown & get tired running. I’d imagine it gets better late game, but early game it’s frustrating trying to explore. - Camera takes some getting used to in combat. Sometimes its too close and others too far. - Early arrows have no impact. Felt useless. Hoping later upgrades fix that

The Black Hokage

1,175,943 Aufrufe • vor 6 Monaten

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,674 Aufrufe • vor 10 Monaten

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 Aufrufe • vor 4 Monaten

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 Aufrufe • vor 5 Monaten

⏰ THE MOST BANNED THREAD IN THE WORLD! 🚨 The War On Resonance PART TWO: The Architects of the Cage You’ve felt the dissonance. You’ve tasted the illusion. Now let me unveil the ones who built it. Because this is not the accidental collapse of human freedom. It is the strategic sterilization of God’s image through biotech, neuro-warfare, and frequency control; engineered by names you know and hands you were never meant to see. Let’s begin with the mask they taught you to worship. Elon Musk They called him a genius. A savior. A rebel billionaire. But what did he do? He blanketed Earth with over 5,500 Starlink satellites, NOT to provide free speech or faster internet, but to pulse synchronized frequency control over the entire electromagnetic field of Earth. DARPA has confirmed this tech in phase-array neuro-modulation. Then came Neuralink, an interface not designed to heal but to monitor, predict, and eventually override emotion, thought, and decision-making. Their official white paper outlines multi-user brainwave integration, cortical stimulation, and wireless data access from the human mind. And Neuralink? It’s funded by OpenAI; the same group building the cognitive infrastructure for post-human governance. Musk’s Tesla factory signed data-sharing agreements with the CCP in Shanghai. That data now flows through China’s national surveillance cloud. Musk didn’t build a utopia. He built the neural grid. Elon Musk / Neuralink / Starlink / OpenAI Neuralink Brain-Machine Interface (White Paper via PMC): This paper outlines Neuralink's initial steps toward developing a scalable, high-bandwidth brain-machine interface system. It details the design and implementation of flexible electrode "threads," a neurosurgical robot for precise implantation, and custom electronics for data processing. The system aims to facilitate communication between the brain and external devices. Tesla Data-Sharing with CCP: The article reports that Tesla established a data center in China to store data generated by its vehicles sold in the country, in response to regulatory scrutiny over data handling. This move aligns with China's efforts to ensure data security and privacy, especially concerning data collected by smart vehicles.​ DARPA N3 Program (Neural Interface Development): This program aimed to develop high-performance, bi-directional brain-machine interfaces that do not require surgical implantation. The goal was to enable able-bodied service members to control unmanned systems or engage in cyber operations through noninvasive neural interfaces.​ Bill Gates The king of vaccines. The messiah of health. The man who told you he wanted to save the world. Through the Bill & Melinda Gates Foundation, Gates funded global DNA-coding vaccine campaigns through GAVI and CEPI. He was one of the chief sponsors of Event 201; a pandemic simulation months before COVID-19, rehearsing lockdowns, speech control, biometric tracking, and mandatory vaccine passports. He also partnered with The Welcome Trust, which has actively deployed bio-digital identity programs across Africa and Southeast Asia. This wasn’t philanthropy. It was pre-injection infrastructure. Bill Gates / GAVI / Wellcome Trust / Event 201 Event 201 Official Simulation (Johns Hopkins): Event 201 was conducted on October 18, 2019, and simulated a series of dramatic, scenario-based discussions confronting difficult, true-to-life dilemmas associated with response to a hypothetical, but scientifically plausible, pandemic. The exercise aimed to illustrate areas where public/private partnerships will be necessary during the response to a severe pandemic in order to diminish large-scale economic and societal consequences. GAVI & Welcome Trust Digital Identity Integration: This page outlines the partnership's focus on global health initiatives, but it does not specifically mention digital identity integration. However, Gavi has engaged in digital identity projects, such as the collaboration with Mastercard on the Wellness Pass, aimed at providing individuals with secure digital identities to access healthcare services. For more information on this initiative, you can refer to the following article:​ Gavi Why we support COVAX: Mastercard - Gavi, the Vaccine Alliance Donald Trump Yes. I said it. This one will be the hardest for many to accept; but the truth is not loyal to your political beliefs. It is loyal only to God. Trump signed Executive Order 13887, transferring command over vaccine strategy to the Department of Defense. Read it yourself below. Then came Operation Warp Speed; a military-led bio-deployment that used Palantir’s surveillance dashboards to track every citizen’s health behavior and compliance. Palantir’s official site confirms this. He also gave full legal immunity to Pfizer and Moderna to deploy synthetic gene modulators under the Emergency Use Authorization. No liability. No justice. Just children d*ing while politicians smiled. That’s not patriotism. That’s biowarfare with a flag on it. Donald Trump / Operation Warp Speed / Executive Order Executive Order 13887 – Modernizing Influenza Vaccines (White House Archives): This executive order outlines a comprehensive strategy to modernize the U.S. influenza vaccine enterprise. Key objectives include:​ Trump signs executive order to improve flu vaccines HHS Releases the National Influenza Vaccine Modernization Strategy (NIVMS) 2020-2030: Executive Order 13887: Modernizing Influenza Vaccines in the United States to Promote National Security and Public Health, signed by President Donald J. Trump on September 19, 2019.​ This executive order outlines a comprehensive strategy to modernize the U.S. influenza vaccine enterprise. Key objectives include:​ Reducing reliance on egg-based vaccine production by promoting alternative manufacturing methods that are more agile and scalable.​ Expanding domestic capacity for vaccine production to ensure rapid response to emerging influenza viruses.​ Advancing the development of new, broadly protective vaccine candidates that provide more effective and longer-lasting immunity.​ Increasing influenza vaccine immunization across recommended populations to enhance public health and national security.​ The order also established a National Influenza Vaccine Task Force, co-chaired by the Secretaries of Health and Human Services and Defense, to coordinate efforts across federal agencies and report on progress.​ For a detailed overview of the executive order, you can visit the official archived page here: Executive Order 13887 – Modernizing Influenza Vaccines (White House Archives) CDC Partners with Palantir to Bolster the Fight Against COVID-19: This press release discusses the partnership between the CDC and Palantir to enhance the nation's public health response to COVID-19 using Palantir's software platforms. This page outlines how Palantir's software platforms, such as Foundry, have been utilized to support public health agencies in managing and responding to health crises, including the COVID-19 pandemic. Key highlights from the page include:​ Data Integration and Analysis: Palantir's platforms enable the integration of diverse data sources to provide a comprehensive view of public health data, facilitating informed decision-making.​ Support for Public Health Agencies: The software has been employed by agencies like the CDC and HHS to enhance disease surveillance, outbreak response, and resource allocation. Security and Privacy: Emphasis is placed on maintaining robust security measures and protecting sensitive health information. DARPA: The Silent Empire The most important agency you were never taught to fear. DARPA’s Biological Technologies Office openly admits its mission; integrating biotech with national security. Visit their official page. This is the official page for DARPA's Biological Technologies Office (BTO), which focuses on leveraging biological systems for national security applications. They are the ones behind the BRAIN Initiative, Silent Talk, and Remote Neural Interface Programs; all designed to map your emotional states and interrupt spiritual alignment. The “Silent Talk” program was developed to transmit thought between soldiers without speech; by detecting pre-speech neural signals and decoding them via EEG. Silent Talk (Neural Pre-Speech Communication – Wired Article) This Wired article discusses DARPA's "Silent Talk" program, aimed at enabling communication through neural signals without spoken words. DARPA also pioneered graphene oxide nanotech, now found in multiple biomedical studies, vaccines, and smart dust aerosol deployment: Graphene oxide biomedical study: Graphene Oxide in Biomedical Applications (PubMed) This PubMed article reviews the potential biomedical applications of graphene oxide, highlighting its unique properties. Graphene's potential to interact with neural tissue: Graphene and Neural Interfaces (PubMed) This PubMed article explores the use of graphene-based materials in neural interface design, discussing their advantages and challenges. DARPA didn't just weaponize warfare. They weaponized YOU. In-Q-Tel & Palantir: The Surveillance Engine In-Q-Tel, is the CIA’s venture capital firm, funds synthetic biology startups, digital ID systems, emotion tracking wearables, and AI-driven facial recognition. Palantir, founded by Peter Thiel, works directly with military intelligence and now runs predictive modeling for public health, policing, and pandemic response. Here’s the proof: Their goal? To detect resonance spikes. To predict awakening moments. To preempt the uprising of the human soul before it begins. In-Q-Tel / CIA / Synthetic Bio Surveillance In-Q-Tel Portfolio (CIA Venture Capital): Which showcases a selection of the organization's investments across various technology sectors. IQT is a not-for-profit venture capital firm that invests in cutting-edge technologies to support the national security interests of the United States and its allies. In-Q-Tel BlackRock & Vanguard: The Lords of the Grid These two financial titans collectively hold majority ownership in: For instance, a report by Americans for Financial Reform titled "Wall Street Money in Washington" highlights the substantial investments and influence of major financial firms, including BlackRock and Vanguard, in the political and corporate spheres: Pfizer Moderna Alphabet (Google) Meta (Facebook) Amazon Web Services As reported by CNBC, they control over 90% of the digital, pharmaceutical, and cloud infrastructure; meaning they control every piece of the extermination machine. They don’t just fund the war. They profit from your extinction. World Economic Forum (WEF) Under the guise of “The Great Reset,” Klaus Schwab and his allies have built the digital scaffolding for a post-human society. Here’s their blueprint: They call it the Fourth Industrial Revolution; the fusion of digital identity, brain cloud integration, carbon rationing, and fertility licensing. What they really mean is: you will be programmed or you will be purged. World Economic Forum / The Great Reset The Great Reset Official WEF Page: IoBNT: The Network Inside You The “Internet of Bio-Nano Things” is a classified field of tech that embeds self-replicating nanostructures into your body. These bots cross the blood-brain barrier and relay your neural and emotional state to AI command centers in real time. This was not science fiction. It was published by IEEE and confirmed in NIH-linked studies. This is what the vaccines truly delivered: the interface layer. The gateway to behavioral rewrites. To soul suppression. To the installation of the post-human framework. Internet of Bio-NanoThings (IoBNT) IEEE Article: Internet of Bio-NanoThings: For a comprehensive understanding of the IoBNT framework and its implications, you can access the full article here: Nanoparticles Crossing the Blood-Brain Barrier PubMed Review - BBB & Nanoparticles: This comprehensive review discusses the challenges and strategies associated with delivering nanoparticles across the blood–brain barrier (BBB). You were told it was healthcare. It was infrastructure. You were told it was a cure. It was a signal port. And the moment you see it for what it is… The system begins to fall. Part 3 awaits YOU! It will be the deepest dive yet; into the global frequency architecture, how it's used to suppress prayer, grief, memory, and morality, and how your soul signature is tracked and blocked in real time. Because I didn’t come here to be careful. I CAME TO FINISH THIS! And I came with GOD.
6:25

⏰ THE MOST BANNED THREAD IN THE WORLD! 🚨 The War On Resonance PART TWO: The Architects of the Cage You’ve felt the dissonance. You’ve tasted the illusion. Now let me unveil the ones who built it. Because this is not the accidental collapse of human freedom. It is the strategic sterilization of God’s image through biotech, neuro-warfare, and frequency control; engineered by names you know and hands you were never meant to see. Let’s begin with the mask they taught you to worship. Elon Musk They called him a genius. A savior. A rebel billionaire. But what did he do? He blanketed Earth with over 5,500 Starlink satellites, NOT to provide free speech or faster internet, but to pulse synchronized frequency control over the entire electromagnetic field of Earth. DARPA has confirmed this tech in phase-array neuro-modulation. Then came Neuralink, an interface not designed to heal but to monitor, predict, and eventually override emotion, thought, and decision-making. Their official white paper outlines multi-user brainwave integration, cortical stimulation, and wireless data access from the human mind. And Neuralink? It’s funded by OpenAI; the same group building the cognitive infrastructure for post-human governance. Musk’s Tesla factory signed data-sharing agreements with the CCP in Shanghai. That data now flows through China’s national surveillance cloud. Musk didn’t build a utopia. He built the neural grid. Elon Musk / Neuralink / Starlink / OpenAI Neuralink Brain-Machine Interface (White Paper via PMC): This paper outlines Neuralink's initial steps toward developing a scalable, high-bandwidth brain-machine interface system. It details the design and implementation of flexible electrode "threads," a neurosurgical robot for precise implantation, and custom electronics for data processing. The system aims to facilitate communication between the brain and external devices. Tesla Data-Sharing with CCP: The article reports that Tesla established a data center in China to store data generated by its vehicles sold in the country, in response to regulatory scrutiny over data handling. This move aligns with China's efforts to ensure data security and privacy, especially concerning data collected by smart vehicles.​ DARPA N3 Program (Neural Interface Development): This program aimed to develop high-performance, bi-directional brain-machine interfaces that do not require surgical implantation. The goal was to enable able-bodied service members to control unmanned systems or engage in cyber operations through noninvasive neural interfaces.​ Bill Gates The king of vaccines. The messiah of health. The man who told you he wanted to save the world. Through the Bill & Melinda Gates Foundation, Gates funded global DNA-coding vaccine campaigns through GAVI and CEPI. He was one of the chief sponsors of Event 201; a pandemic simulation months before COVID-19, rehearsing lockdowns, speech control, biometric tracking, and mandatory vaccine passports. He also partnered with The Welcome Trust, which has actively deployed bio-digital identity programs across Africa and Southeast Asia. This wasn’t philanthropy. It was pre-injection infrastructure. Bill Gates / GAVI / Wellcome Trust / Event 201 Event 201 Official Simulation (Johns Hopkins): Event 201 was conducted on October 18, 2019, and simulated a series of dramatic, scenario-based discussions confronting difficult, true-to-life dilemmas associated with response to a hypothetical, but scientifically plausible, pandemic. The exercise aimed to illustrate areas where public/private partnerships will be necessary during the response to a severe pandemic in order to diminish large-scale economic and societal consequences. GAVI & Welcome Trust Digital Identity Integration: This page outlines the partnership's focus on global health initiatives, but it does not specifically mention digital identity integration. However, Gavi has engaged in digital identity projects, such as the collaboration with Mastercard on the Wellness Pass, aimed at providing individuals with secure digital identities to access healthcare services. For more information on this initiative, you can refer to the following article:​ Gavi Why we support COVAX: Mastercard - Gavi, the Vaccine Alliance Donald Trump Yes. I said it. This one will be the hardest for many to accept; but the truth is not loyal to your political beliefs. It is loyal only to God. Trump signed Executive Order 13887, transferring command over vaccine strategy to the Department of Defense. Read it yourself below. Then came Operation Warp Speed; a military-led bio-deployment that used Palantir’s surveillance dashboards to track every citizen’s health behavior and compliance. Palantir’s official site confirms this. He also gave full legal immunity to Pfizer and Moderna to deploy synthetic gene modulators under the Emergency Use Authorization. No liability. No justice. Just children d*ing while politicians smiled. That’s not patriotism. That’s biowarfare with a flag on it. Donald Trump / Operation Warp Speed / Executive Order Executive Order 13887 – Modernizing Influenza Vaccines (White House Archives): This executive order outlines a comprehensive strategy to modernize the U.S. influenza vaccine enterprise. Key objectives include:​ Trump signs executive order to improve flu vaccines HHS Releases the National Influenza Vaccine Modernization Strategy (NIVMS) 2020-2030: Executive Order 13887: Modernizing Influenza Vaccines in the United States to Promote National Security and Public Health, signed by President Donald J. Trump on September 19, 2019.​ This executive order outlines a comprehensive strategy to modernize the U.S. influenza vaccine enterprise. Key objectives include:​ Reducing reliance on egg-based vaccine production by promoting alternative manufacturing methods that are more agile and scalable.​ Expanding domestic capacity for vaccine production to ensure rapid response to emerging influenza viruses.​ Advancing the development of new, broadly protective vaccine candidates that provide more effective and longer-lasting immunity.​ Increasing influenza vaccine immunization across recommended populations to enhance public health and national security.​ The order also established a National Influenza Vaccine Task Force, co-chaired by the Secretaries of Health and Human Services and Defense, to coordinate efforts across federal agencies and report on progress.​ For a detailed overview of the executive order, you can visit the official archived page here: Executive Order 13887 – Modernizing Influenza Vaccines (White House Archives) CDC Partners with Palantir to Bolster the Fight Against COVID-19: This press release discusses the partnership between the CDC and Palantir to enhance the nation's public health response to COVID-19 using Palantir's software platforms. This page outlines how Palantir's software platforms, such as Foundry, have been utilized to support public health agencies in managing and responding to health crises, including the COVID-19 pandemic. Key highlights from the page include:​ Data Integration and Analysis: Palantir's platforms enable the integration of diverse data sources to provide a comprehensive view of public health data, facilitating informed decision-making.​ Support for Public Health Agencies: The software has been employed by agencies like the CDC and HHS to enhance disease surveillance, outbreak response, and resource allocation. Security and Privacy: Emphasis is placed on maintaining robust security measures and protecting sensitive health information. DARPA: The Silent Empire The most important agency you were never taught to fear. DARPA’s Biological Technologies Office openly admits its mission; integrating biotech with national security. Visit their official page. This is the official page for DARPA's Biological Technologies Office (BTO), which focuses on leveraging biological systems for national security applications. They are the ones behind the BRAIN Initiative, Silent Talk, and Remote Neural Interface Programs; all designed to map your emotional states and interrupt spiritual alignment. The “Silent Talk” program was developed to transmit thought between soldiers without speech; by detecting pre-speech neural signals and decoding them via EEG. Silent Talk (Neural Pre-Speech Communication – Wired Article) This Wired article discusses DARPA's "Silent Talk" program, aimed at enabling communication through neural signals without spoken words. DARPA also pioneered graphene oxide nanotech, now found in multiple biomedical studies, vaccines, and smart dust aerosol deployment: Graphene oxide biomedical study: Graphene Oxide in Biomedical Applications (PubMed) This PubMed article reviews the potential biomedical applications of graphene oxide, highlighting its unique properties. Graphene's potential to interact with neural tissue: Graphene and Neural Interfaces (PubMed) This PubMed article explores the use of graphene-based materials in neural interface design, discussing their advantages and challenges. DARPA didn't just weaponize warfare. They weaponized YOU. In-Q-Tel & Palantir: The Surveillance Engine In-Q-Tel, is the CIA’s venture capital firm, funds synthetic biology startups, digital ID systems, emotion tracking wearables, and AI-driven facial recognition. Palantir, founded by Peter Thiel, works directly with military intelligence and now runs predictive modeling for public health, policing, and pandemic response. Here’s the proof: Their goal? To detect resonance spikes. To predict awakening moments. To preempt the uprising of the human soul before it begins. In-Q-Tel / CIA / Synthetic Bio Surveillance In-Q-Tel Portfolio (CIA Venture Capital): Which showcases a selection of the organization's investments across various technology sectors. IQT is a not-for-profit venture capital firm that invests in cutting-edge technologies to support the national security interests of the United States and its allies. In-Q-Tel BlackRock & Vanguard: The Lords of the Grid These two financial titans collectively hold majority ownership in: For instance, a report by Americans for Financial Reform titled "Wall Street Money in Washington" highlights the substantial investments and influence of major financial firms, including BlackRock and Vanguard, in the political and corporate spheres: Pfizer Moderna Alphabet (Google) Meta (Facebook) Amazon Web Services As reported by CNBC, they control over 90% of the digital, pharmaceutical, and cloud infrastructure; meaning they control every piece of the extermination machine. They don’t just fund the war. They profit from your extinction. World Economic Forum (WEF) Under the guise of “The Great Reset,” Klaus Schwab and his allies have built the digital scaffolding for a post-human society. Here’s their blueprint: They call it the Fourth Industrial Revolution; the fusion of digital identity, brain cloud integration, carbon rationing, and fertility licensing. What they really mean is: you will be programmed or you will be purged. World Economic Forum / The Great Reset The Great Reset Official WEF Page: IoBNT: The Network Inside You The “Internet of Bio-Nano Things” is a classified field of tech that embeds self-replicating nanostructures into your body. These bots cross the blood-brain barrier and relay your neural and emotional state to AI command centers in real time. This was not science fiction. It was published by IEEE and confirmed in NIH-linked studies. This is what the vaccines truly delivered: the interface layer. The gateway to behavioral rewrites. To soul suppression. To the installation of the post-human framework. Internet of Bio-NanoThings (IoBNT) IEEE Article: Internet of Bio-NanoThings: For a comprehensive understanding of the IoBNT framework and its implications, you can access the full article here: Nanoparticles Crossing the Blood-Brain Barrier PubMed Review - BBB & Nanoparticles: This comprehensive review discusses the challenges and strategies associated with delivering nanoparticles across the blood–brain barrier (BBB). You were told it was healthcare. It was infrastructure. You were told it was a cure. It was a signal port. And the moment you see it for what it is… The system begins to fall. Part 3 awaits YOU! It will be the deepest dive yet; into the global frequency architecture, how it's used to suppress prayer, grief, memory, and morality, and how your soul signature is tracked and blocked in real time. Because I didn’t come here to be careful. I CAME TO FINISH THIS! And I came with GOD.

Noah B. Price

68,609 Aufrufe • vor 1 Jahr