const daksh = {
    location: "Delhi, India",
    title: "student",
    approach: "say yes first, code frantically, deliver something better than expected",
    currentFocus: ["anything that sounds interesting", "whatever breaks next"],
    funFact: "I once fixed a VB script by pure spite for Excel"
};

this chaos-driven approach has resulted in me learning: web dev, mobile apps, video/photo/audio editing, music production, 3D modeling, UI/UX, robotics, electronics, PCB design, CAD, hardware modding, soldering, game modding, a concerning amount of repair work and science-y things.

accept task → panic → research furiously → build thing → fix till thing works → repeat

also dabbled in: debates, GK competitions, and various other things i said "sure, i can do that" to.

i don't believe more lines of code/number of commits/consistency of commits means better code. when a measure becomes a target, it ceases to be a good measure. for any differing opinions, you may refer to Goodhart's Law.

TL;DR: people who don't know what they're talking about should not be making decisions about said thing.

#!/bin/bash
while true; do
    read -p "new challenge accepted? (y/n): " answer
    case $answer in
        [Yy]* )
            echo "confidence level: 0%"
            sleep 2
            echo "opening 47 Stack Overflow tabs..."
            grep -r "how to" ~/brain/* 2>/dev/null || echo "no prior knowledge found"
            
            until [ $success -eq 1 ]; do
                ./attempt_solution.sh
                [ $? -eq 0 ] && success=1 || echo "failed. trying again at 3 AM..."
            done
            
            echo "somehow works"
            echo "better than expected lol"
            git add skills.log && git commit -m "accidentally learned another thing"
            ;;
        * ) 
            echo "lies. we both know you'll say yes."
            ;;
    esac
done

• learned cinematography, audio design and modding via video game camera mods (shoutout to Matti Hietanen and Mikhael Sharov for enabling this madness)
• fixed printers multiple times (humanity's greatest challenge)
• won robotics competitions with robots assembled the night before (procrastination-driven development)
• built competition drones that actually flew (surprising everyone, including myself)
• can argue politics as well as debug code (equally exhausting, equally satisfying)