Learn to code in VR/MR on Meta Quest. Snap code blocks together and run Python, JavaScript, HTML & CSS. Based on the freeCodeCamp curriculum. Not affiliated.
Coding Puzzle: learn to code with your hands, on Meta Quest.
Grab code blocks in VR/MR, snap them together, run them, see the result.
Python, JavaScript, HTML, CSS, based on the freeCodeCamp curriculum (not affiliated).
One step free every day.
https://t.co/ensEPRN00F
@ayesha_fatiima The part that gets missed is how much of it happens without a mentor. Working out from a forum thread why your own code breaks is a harder skill than the DSA itself, and it never shows up on a transcript.
@PotatoeDev Delegation is the piece that pays off later. One listener on the parent instead of forty on children means dynamically added rows just work, and you stop chasing bugs where the handler exists on some elements and not others.
@YesShrey The streak matters more than the problems. One thing that compounds on top of it: write a single line next to each solved problem naming the pattern it used. After a month that list is the asset, not the solve count.
@GoalFlashFC Both, in that order. Bandit teaches the shell verbs; SadServers teaches what to do when a box is already broken and nobody knows why. The second only feels productive once the first is muscle memory, and level 10 says you are past that.
If you own a Quest and it is gathering dust, there is a use for it that is not a game.
Coding Puzzle: assemble code with your hands in VR or MR, run it, see the result. Python, JavaScript, HTML, CSS.
One step a day free, $7.99/mo for the rest.
https://t.co/ensEPRN00F
@Dominique_ice Same idea shows up again with trimming whitespace and with dates. Anything that arrives from outside your program gets cleaned once at the door, then the rest of the code only ever sees the clean version.
@ArshadSanwal7@CodeEmmanuelPy Concretely: write one sentence like 'by day 100 I can build a small tool that does X for me'. Then judge each day by whether it moved you toward X.
For you X could be a script that reads a file and prints a summary of it.
@ArshadSanwal7@CodeEmmanuelPy Both true. A target keeps the 100 days pointed somewhere, and for Python the useful target is a thing rather than a topic: a script that renames your files, a bot that posts for you, a small API. Pick the thing and the topics show up on their own.
@Dot_NotSam 1358 is a good one to keep in the notes. The trick that generalises: instead of counting valid windows, count for each right end how many left ends work. Once you have the position of the last a, b and c, the answer is just min of those plus one.
@Ataraashiieii Substring counting is one of the few topics where writing the slow brute force once actually pays. Seeing the O(n squared) version makes the sliding window feel like a shortcut you earned instead of a trick you memorised.
@Donsarkcess The Meta developer dashboard is its own skill tree. What ate the most of my time was not the build, it was the submission flow - app, version, submission and metadata are separate objects that each carry their own state, and it is never obvious which one is blocking you.
@amasad The bottleneck moved to the person reading the output. A programmer that never gets bored still needs someone who can tell a correct answer from a plausible one, and that judgement is the part nobody has automated yet.
Tutorial hell has a simple exit: stop when the video ends and rebuild the same thing from a blank file the next morning.
What you can rebuild from nothing is what you know. Everything else is a recording you watched.
@ArshadSanwal7 Ha, it is more that dictionaries are where a lot of if/elif chains go to die. Finish control flow properly first though. When you get there, the one-line version to remember is d.get(key, default), which saves you a whole branch every time a key might be missing.
@Carbonthecoder Good luck with it. One more if the bot will take it: put a visible reset in reach at all times. In a chemistry sim the fear of ruining the experiment is what stops people trying the interesting mixture.
@BuildWithMrinal A custom tool is the right first project, because you are the user and you already know what it should do. That removes the hardest part of every tutorial project, which is pretending to care about the fake requirements.
@konig0000 Level 0 is missing: knowing what question the data is supposed to answer. Plenty of people at level 3 build beautiful pipelines nobody asked for.
@riya_mishra007 The tell is what happens when the job uses a different language. People who learned to solve problems pick up the second one in a weekend. People who learned a language are back at the start.