Raw-Dogging C Code in the AI Era: Why I Solve Basic Problems Without LLMs
slightly embarrassing thing to admit as someone building AI systems lol:
every couple of weeks, I turn off Claude Code, disable Cursor, open a bare Linux terminal, and spend an hour writing dead-simple C code from scratch.
no Copilot. no tab-autocomplete. no split-pane LLM.
just gedit, gcc, and raw terminal output.
right now, everyone is rushing straight into LeetCode mediums, graph theory, or complex system design.
and for day-to-day code? most engineers are just prompting an LLM, glancing at the diff, and hitting "accept".
it feels fast. it makes you feel like a 10x developer.
but I noticed something scary happening to my own brain:
when you outsource every single loop, string reversal, and condition to an AI, your active cognition drops to basically zero.
you stop thinking through edge cases before they run.
you stop mentally feeling off-by-one errors.
you become an autocomplete-approver instead of an engineer.
doing basic programming problems isn't about memorizing syntax or pretending AI doesn't exist. AI can solve all 100 of these in 10 seconds.
it’s about keeping the mental muscle alive.
if you can't raw-dog 15 lines of C logic without an AI holding your hand, you're not orchestrating intelligence, you're just dependent on it.
I put together 100 of these ground-zero manual problems in a repo called Grind.
basic I/O, loops, digits, manual string manipulation without library functions, pointers.
before you touch LeetCode or prompt your next AI agent, finish program 1 to 100 on a bare terminal.
your brain will thank you.
link to the repo in the first comment ↴
#softwareengineering #coding #cprogramming #buildinpublic #linux
📸 Recommended Visual Asset
- Format: Clean dark-mode Linux terminal screenshot (e.g. Ubuntu / Arch) or phone photo of code on screen.
- Content:
$ cd ~/code/c/Grind
$ cat Level-1/7.c
// Swap two numbers without using a third variable
$ gcc Level-1/7.c -o 7 && ./7
Enter two numbers: 14 29
Before: a=14, b=29
After: a=29, b=14
- Why it works: Shows authentic, raw developer reality—proves you actually run the code rather than using a corporate marketing slide.
💬 First Comment
Here’s the 100-problem curriculum: https://github.com/Drix10/Grind ↗
Start from Level 1, work in order, compile with gcc. No Copilot, no LLM in a split tab. Just you and the compiler.
🔗 Reference & Source Breakdown
- Source Material: Drix10/Grind Repository ↗
- Author: Drishtant Ghosh (@Drix10)
- Syndicated Channel: LinkedIn & Personal Blog Hub
