DEV Community: TruyenDichAI

"System Design Review: Reincarnation.init() Failed, Fallback to Mushroom_Class"

TruyenDichAI — Mon, 26 Jan 2026 18:17:48 +0000

You know that feeling when you deploy to production on a Friday evening, and the logs immediately start screaming Critical Error: Body Not Found?

That’s basically the premise of "There are mushrooms growing in this dungeon" (Chinese Title: 这个地下城长蘑菇了).

As a dev who reads way too many system novels while waiting for npm install to finish, I decided to do a "Code Review" of this specific instance. Here is the breakdown.

1. The Initial Commit (The Premise)

User Story: As a protagonist, I want to reincarnate into a fantasy world to become a hero.
Actual Result: Uncaught Exception: RaceCondition. Target 'Human' unavailable. Defaulting to 'Fungus'.

The main character, Lin Jun, wakes up with:

Vision: null
Limbs: []
Movement_Speed: 0
Class: Mushroom

It’s the ultimate "Bootstrapping" nightmare. He literally has to build his entire existence from a corrupted kernel. No hands, no eyes, just a sentient spore in a dungeon full of high-level mobs. It’s like trying to run Doom on a pregnancy test—improbable, difficult, but surprisingly engaging to watch.

2. Core Features (The Cheat System)

Every isekai has a Framework. This one runs on The Decomposition System.

`function devour(corpse)`

Input: Dead biology (monsters, adventurers).
Process: Breaks down the object using mycelium.
Output: Genetic Points (XP) & Skill Modules.
Documentation: "If it dies, I eat it. If I eat it, I verify its checksum and add its features to my repo."

It’s essentially Inheritance on steroids. He doesn't just learn skills; he extracts the source code from his enemies and hot-patches it into his own biology. Want eyes? Eat a beholder. Need poison resistance? Eat a slime.

3. The "Spaghetti Code" (The Cons)

Of course, no project is bug-free. The author, Sheng Chi Jun Zi (Raw Mushroom Eater), clearly didn't write unit tests for the later chapters.

Feature Bloat: The skill system starts clean but quickly turns into node_modules. Hundreds of dependencies (skills) that get used once and then forgotten in the package.json.
Lazy Patching: Whenever the MC hits a wall (blocking issue), the author suddenly drops a "Patch" (a convenient dead body with the exact needed skill). It feels like hard-coding a response just to pass a specific test case.
Memory Leaks: The plot sometimes loops. Evolution -> Fight -> Eat -> Evolution. It lacks a garbage collector for stale plot threads.

4. User Experience (Why read it?)

Despite the technical debt, the UX is surprisingly good:

Unique Architecture: Skipping the "Humanoid" interface entirely allows for creative problem solving. How do you kill a knight when you are a literal vegetable? You have to think like a virus, not a warrior.
Scalability: Watching the MC scale from a single spore to a massive, dungeon-encompassing biological network is widely satisfying. It scratches that "Factorio" or "Civilization" itch.
Error Handling: The MC is unkillable (mostly) because he distributed his "server" (mycelium) across the entire map. High availability architecture at its finest.

Verdict: Merge or Close PR?

Status: LGTM (Looks Good To Me) with nitpicks.

If you are tired of the standard "Sword & Magic" boilerplates and want to see a weird edge-case implementation of the reincarnation genre, generic this a try. It’s a messy codebase, but it compiles, and the runtime behavior is hilarious.

Rating: ⭐⭐⭐ (3/5) stars.
Recommendation: Reading this while debugging might cause hallucinations. Proceed with caution.

https://zhnovel.com/book/there-are-mushrooms-growing-in-this-dungeon

Drop a comment below if you've encountered other "Non-Human" frameworks that are worth refactoring!

Wizard Journey: The 'Hardcore Mode' Engineering Novel You Didn't Know You Needed

TruyenDichAI — Tue, 20 Jan 2026 18:17:18 +0000

Stop Me If You've Heard This One

You're a junior dev. You download a massive legacy codebase. You have no documentation. The senior engineer just quit. And if you push a bug to production, you literally die.

Welcome to Wizard Journey (Sorcerer's Journey).

If you read web novels, you're probably used to the "System" trope. The protagonist gets an AI chip (basically GitHub Copilot on steroids) that analyzes enemies, optimizes cultivation paths, and practically plays the game for them. It's fun, it's efficient, it's... Python.

Wizard Journey is Assembly.

The Premise: Coding Without Intellisense

The protagonist, Green, is thrown into a Wizard World that is brutally rational. There is no "chosen one" prophecy. There is no magical grandpa in a ring giving him solutions.

His "Cheat"? The Scientific Method.

"Give me infinite knowledge, and I will use myself as a fulcrum to pry the infinite world."

This isn't just a cool quote; it's his entire architecture. While other protagonists in the genre (cough Leylin from Warlock of the Magus World) rely on their AI chips to simulate experiments, Green has to:

Hypothesize: "If I mix Element A with Monster Part B, it should explode."
Test: Explosion happens. "Okay, it exploded too much."
Debug: Adjust variables. Re-test.
Deploy: Cast the spell and hope it doesn't segfault (kill him).

Why Developers Will Love It

1. The Ultimate Technical Debt

The magic system in this novel feels less like "casting spells" and more like "managing dependencies". Wizards don't just wave wands; they build complex mental models (constructs) that require:

Resource Management: Mana is expensive. Efficient code (spells) wins fights.
Legacy Code: Ancient wizard knowledge is often dangerous, poorly documented, or deprecated.
Scalability: A spell that kills a goblin won't scale to kill a God. You have to refactor your entire power base every few tiers.

2. No "AI Copilot" Hand-Holding

In a world dominated by GenAI, reading about a character who has to manually learn the underlying principles of his world is refreshing. It’s the difference between asking ChatGPT to write a regex for you versus actually understanding how the state machine works.

Green’s power feels earned. When he defeats a higher-level enemy, it’s not because his System gave him a 20% buff; it’s because he spent 30 chapters reverse-engineering the enemy’s biological weaknesses.

3. The "Dark Forest" of Open Source

The Wizard World is a grim place. Knowledge is proprietary. Sharing your source code (spell matrix) usually leads to someone finding a vulnerability and exploiting it. The politics feel incredibly similar to a cutthroat Silicon Valley startup environment—perform or get deprecated (literally turned into compost).

The Trade-off (Cons)

It's not all clean code.

Verbose Documentation: The author loves to explain the "physics" of magic. Be prepared for long "README.md" sections in the middle of chapters.
Steep Learning Curve: The first arc is slow. It’s like setting up a Kubernates cluster; the payoff is huge, but the setup is a pain.

Verdict

If Warlock of the Magus World is a Senior Dev who automated his job with scripts, Wizard Journey is the Principal Engineer who built the automation framework from scratch using nothing but a soldering iron and caffeine.

It’s dry, it’s dense, and it’s absolutely brilliant.

Rating: sudo apt-get install wizard-journey (Worth the install)

Have you read this? Do you prefer "System" novels (High-level languages) or "Traditional" novels (Low-level languages)? Let me know in the comments!

https://zhnovel.com/book/wizard-journey

[Code Roast] System Design Case Study: The Mycelium Backend

TruyenDichAI — Mon, 19 Jan 2026 17:43:17 +0000

Repo: There are mushrooms growing in this dungeon
Author: Sheng Chi Jun Zi (The Senior Architect)
Tags: #systemdesign #refactoring #legacycode #horror #gamedev

Abstract We've all dealt with legacy code. But have you ever reincarnated into legacy infrastructure as a headless, limbless background process?

Meet Lin Jun, a developer (probably) who got deployed into a fantasy dungeon not as a Hero, but as a Mushroom. His task? Refactor the entire dungeon ecosystem using a distributed mycelium network.

The Legacy Environment (Context) The dungeon is a hostile production environment.

Zero Visibility: Lin Jun starts in "Headless Mode". No GUI, no eyes. He has to rely on event listeners (vibrations, chemical signals) to debug his surroundings.
Hostile Users: Adventurers (End Users) constantly try to penetrate the firewall (dungeon entrance) to loot resources.
Resource Constraints: He starts with 0 mana and limited biomass.

Core Architecture (The Mechanics) 3.1 Aggressive Garbage Collection (GC) Unlike standard systems that just delete enemies, Lin Jun implements a highly efficient recycling routine. Every time an adventurer or monster dies, his mycelium executes decompose().

Input: Higher-level organism corpse.
Process: Break down organic matter.
Output: XP, Skills (API endpoints), and Nutrients.
It’s the ultimate "Green Computing". Nothing is wasted. Even the trash mobs are compiled into fuel for the main thread.

3.2 Distributed Scaling (The Mycelium Network)
Lin Jun doesn't build a monolith. He builds a microservices architecture.

Service Discovery: He spreads spores to map out the dungeon topology.
Load Balancing: He creates different mushroom types for different tasks (Tank Shrooms, Poison Shrooms, DPS Shrooms).
Fault Tolerance: If one node (mushroom) is destroyed, the network survives. The root node (his main body) is hidden behind layers of proxies.

The "Feature" (Not a Bug)
Just when he stabilizes the build, a high-priority ticket drops: The Duke's Daughter. She falls into the dungeon. Instead of crashing the system (dying), she gets patched into the network... as another Mushroom variant. Now Lin Jun has to manage a dual-core processor setup with a quirky AI companion.
Technical Debt (Cons)
Startup Time: The initial initialization phase (intro) is slow. The system takes a while to boot up and establish the first few nodes.
UI/UX: For the first few volumes, the "User Interface" is non-existent. It’s pure backend logic. If you prefer flashy front-end battles (GUI), you might find the CLI-based strategy boring.
Code Review (Verdict)
There are mushrooms growing in this dungeon is a masterclass in Entity Component System (ECS) design. It moves away from the "One God Object" (OP Hero) pattern and focuses on swarm intelligence and resource management.

If you enjoy:

Factorio / RTS logic
"Headless" protagonists
Watching a system evolve from Hello World to Skynet
Then git clone this novel immediately.

Final Score: LGTM (Looks Good To Me) Recommendation: Deploy to Production.

I Code 10 Hours a Day. This is the Only Novel That Doesn't Feel Like Legacy Code.

TruyenDichAI — Fri, 16 Jan 2026 16:13:46 +0000

Listen, I look at broken code all day. I fix bugs, I refactor spaghetti, and I argue with PMs about why "just one more feature" will crash the server.

When I clock out, I don't want to read a novel that has more plot holes than a junior dev's first PR. I'm tired of "System Novels" where the MC gets a sudo kill -9 command on everyone just because. It’s lazy. It’s unoptimized. It’s bad design.

Then I found I'm Not A Drama God. And for the first time in forever, I found a story that actually compiles.

The Specs

Endpoint: zhnovel.com/book/i-m-not-a-drama-god
Genre: Urban Mystery / Psychological Horror
Complexity: O(n!) - It gets deep.

Why It Passes Code Review

1. No "System" Dependency Injection

Most novels nowadays rely on a "System" to carry the plot. It's bloatware. The MC is useless without his cheat codes.
In I'm Not A Drama God, the MC, Chen Ling, doesn't have a UI popping up telling him what to do. He wakes up "dead" (literally killed by his roommates) and has to debug his own existence using pure logic and acting skills. He navigates a corrupted world (red meteor -> database crash?) like a senior sysadmin fixing a live outage.

2. Logic Consistency: 100%

The world-building has rules. Hard rules.
In many novels, power levels are inconsistent. One day the MC struggles with a goblin, the next day he accidentally sneezes a galaxy away. That’s a runtime error waiting to happen.
Here, the "Disasters" and the "Ruins of Civilization" follow a strict logic. If you break the rules, you die. No exceptions. It’s fair, it’s brutal, and it satisfies that part of my brain that craves order.

3. The "Uncanny Valley" feature

The horror element is implemented perfectly. It’s not a jump scare (cheap alert() popup). It’s a memory leak that slowly consumes your RAM. The way Chen Ling interacts with his "killers" implies he knows everything, but he acts completely normal. It’s like watching a chaotic script run perfectly silent, knowing it’s deleting the root directory in the background.

TL;DR

If you hate:

[x] Spaghetti plots
[x] "Deus Ex Machina" patches
[x] MCs with zero error handling (stupid decisions)

And you want:

[ ] A solid, logic-driven narrative
[ ] A protagonist who actually thinks before executing
[ ] A dark, atmospheric backend

Read this. It’s functional programming for the soul.

Deploy to Production (Read Now)

Refactoring the Apocalypse: Why "Abyss Slave Owner" is the Only System Novel with Clean Architecture

TruyenDichAI — Tue, 13 Jan 2026 16:50:31 +0000

Fellow devs, let’s be real.

Most "System" novels are written like legacy PHP code from 2004. They’re bloated, full of logical bugs, and the Main Character (MC) scales linearly with zero constraints. It’s spaghetti storytelling. "Oh, the enemy is Level 99?
sudo make_me_level_100." Easy. Boring. Depressing.

I needed a story that felt like well-optimized C++. I found Abyss Slave Owner (深渊奴隶主).

It’s not just a survival novel; it’s a masterclass in Resource Management and handling Technical Debt.

Why This Story Compiles

1. The MC Starts with Massive Technical Debt (Paralysis)

In most novels, the MC gets a "Golden Finger" that fixes everything.
Here? Tang Hao wakes up paralyzed.

Think of it as inheriting a codebase where the documentation is missing, the servers are on fire, and you only have read-access to the database. He has a "System," but he can't execute the physical commands himself. He has to write the logic, but relies on others (minions) to run the runtime environment.

He can't just strength++. He has to architect a solution around his own broken hardware.

2. Human Beings as Consumable Objects

"You are humans, but you are also resources and consumables."

This sounds dark, but from an engineering perspective, it’s just honest memory management.
The MC treats survivors like instances in a Kubernetes cluster.

Useful? Scale them up.
Draining resources without output? Terminate the pod.

There is no "power of friendship" undefined behavior here. It’s pure, ruthless logic. Input must equal Output, or the system crashes (and everyone dies).

3. The "System" is actually an API, not a Cheat Code

Tang Hao interacts with the "Abyss Lord System" like a sysadmin. He views logs, manages module outputs, and optimizes for efficiency.
He doesn't fight zombies; he builds a production pipeline to automate the harvesting of zombie cores.

The Verdict

If you’re tired of "Hello World" level plots where everything works magically, read this. It’s a survival story for people who understand that production is hell.

Tech Stack: Sci-Fi / Apocalypse / System
Current Branch: Survival
Documentation: "Dentist Loves Pulling Teeth" (Author)

Deploy to Production here: Abyss Slave Owner

"My Cell Prison" – The Bio-Punk Refactoring Journey You Didn't Know You Needed

TruyenDichAI — Mon, 12 Jan 2026 16:32:40 +0000

Fellow devs, we stare at bad code all day. Why do we go home and read bad novels? You know the ones. "System" prompts that make no sense, logic holes bigger than node_modules, and MCs with zero critical thinking skills.

I found a fix. It’s called My Cell Prison (我的细胞监狱).

The Pitch: Bootstrapping from Bare Metal
Imagine git reset --hard but on your life. And instead of a clean repo, you wake up as a literal glob of mucus in a sewer.

The MC isn't some "chosen one." He’s a former biology professor who got reincarnated as a rogue cell cluster. He doesn't have a "Cheat Ring." He has knowledge. He treats his new existence like a legacy codebase that needs serious refactoring.

Initial State: A sentient booger.
Goal: Compile a perfect human body.
Method: Hijacking functionality from other organisms (basically npm install for limbs).
Why It Appeals to the Engineering Brain

Hard Logic > Magic Systems
Most cultivation novels are just "I yelled loud -> I got stronger." This guy analyzes the cellular structure of monsters. He optimizes his mitochondria. He treats combat like a debugging session. If he encounters a threat, he doesn't "believe in himself"; he adapts his biological architecture to patch the vulnerability. It’s incredibly satisfying to watch an MC actually think.
The World is a Beautifully Broken System
The setting is a mix of Victorian Steampunk and Lovecraftian horror. Think Bloodborne but with more science. The world is sick, twisted, and full of "bugs" (abominations). The MC is essentially a white-hat hacker trying to navigate a system compromised by Old Gods.
No "Spaghetti Code" Plot
The author, Chuan Huang Yi De A Fei, actually planned the architecture. The power scaling makes sense. There’s no sudden "database migration" where the rules change halfway through. It’s stable, performant storytelling.

The Verdict
It’s dark. It’s gross. It’s logical. If you’re tired of "Script Kiddie" protagonists who get everything handed to them by a simplistic System, give this a read.

Tech Stack:

Genre: Sci-Fi / Mystery / Horror
Complexity: O(log n) - Gets better as it scales.
Boredom Level: 0.
Pull the production build here.
https://zhnovel.com/book/my-cell-prison

Stop Debugging Your Life And Read This: Why 'God of Slaughter' Is The Only Logic That Compiles

TruyenDichAI — Sun, 11 Jan 2026 16:25:59 +0000

Listen up, gentlemen. I know the drill. You’ve spent 12 hours staring at a legacy codebase that looks like it was written by a drunk monkey, and now you want to turn your brain off with some web novels.

But then you hit the "Trending" section and it’s all slop. 5000 chapters of some brain-dead MC who gets a "System" that does everything for him. It’s like watching a senior dev use ChatGPT to write a "Hello World" app. Disgusting.

I’ve waded through the trash so you don't have to. Today, we’re looking at God of Slaughter. It’s not a "clean code" masterpiece, but at least the logic isn't fraudulent.

The "Extreme" Optimization
Our MC, Shi Yan, was a bored rich guy in his past life who did extreme sports. Basically, he was life’s hardest "edge case" tester. He wanted to see if he could break the simulation by almost dying every weekend.

When he transmigrates, he doesn't get a waifu or a kingdom. He wakes up in a cave as a "medicine slave" (basically a QA tester for poison). Most MCs would wait for a "ding" sound. Shi Yan just uses his adrenaline-junkie trauma to brute-force his way out.

Why This Isn't 'Mid' Tier Garbage
The Blood Pattern Ring (The Ultimate Resource Collector): Forget "mana regenerates over time." This ring is a vacuum. People die, the ring sucks up their essence, the MC levels up. It’s efficient. It’s a literal garbage collection system but for souls.
Dual Martial Souls: He’s got the Lightning soul (high throughput/low latency) and the Undying soul (high availability/self-healing). It’s a solid architecture if you ask me.
Zero 'Cringe' Moralizing: The MC doesn't have a "hero" complex. He has a "survival" complex. He understands that in a world of man-eating cultivators, you either optimize or you get deleted.
Slaying the Industry "GOATs"
Everyone talks about Lord of the Mysteries or Reverend Insanity. Fine, those are "Enterprise Grade" novels. But sometimes you just want a "Fast and Brutal" script that gets the job done.

God of Slaughter is that script. It’s darker than my IDE theme and more ruthless than a PM during a sprint deadline. It doesn't have the cringe "friendship power" that ruins most isekai. It’s just pure, unadulterated logic applied to a massacre.

The Verdict for Brothers
If your brain is fried and you need something that actually feels like the MC has more than two functioning neurons, this is it. It’s edgy, it’s violent, and for once, the MC isn't a mid tier hack.

Old teacher always said: "Performance matters, even in your escapism."

If you’re desperate to stop your brain from rotting, go here: https://zhnovel.com/book/god-of-death

Now go back to your JIRA tickets, or whatever it is you people do. I’m going to go read something that makes me feel even more cynical.

Stop Wasting Time on Brain-Dead Slop: Why "I Created the Internet Era in the Wizarding World" is Actually Goated

TruyenDichAI — Sat, 10 Jan 2026 16:30:28 +0000

Listen up, gentlemen. I’ve spent the last decade rotting my brain with thousands of chapters of MTL trash. My IQ is basically in the negatives at this point, but I’ve finally found something that doesn't make me want to gouge my eyes out.

If you’re tired of the usual "MC gets a system and becomes OP for no reason" garbage, sit down. Old teacher is going to show you some real gold today.

The Problem with Most "Tech" Novels
We've all seen it, right? Some loser transmigrates to a fantasy world, builds a steam engine because he remembered a YouTube tutorial, and suddenly the princesses are falling over him. It’s mid. It’s cringe. It lacks basic logic.

But then comes this one: "I Created the Internet Era in the Wizarding World".

The Gimmick: Zuckerberg in a Wizard Robe
Imagine a world where Gods are basically just Big Tech CEOs. They don't want your "faith" in the religious sense; they want your traffic.

The MC, Yu Sheng'an, gets a godhead and immediately realizes: "Wait, this is just the Internet business model." Instead of preaching in a church like a fraud, he starts launching:

Social Platforms: To harvest massive traffic.
Short Videos: To make the commoners addicted (user sinking, literally TikTok for wizards).
Q&A Sites: To build a cult following of "intellectual" iron fans.
Live Streams: To convert casual users into hardcore believers.
Why It’s Actually Goated
Brain Cells Required: The MC actually uses his head. He treats "Faith" like a currency and "Believers" like DAU (Daily Active Users). It’s basically Silicon Valley logic applied to a magical world.
The "Cà Khịa" Energy: He doesn't just fight; he disrupts the entire market. Watching ancient, "high and mighty" gods struggle because their "market share" is dropping to a guy with a magic smartphone is peak entertainment.
Not a Fraud: Unlike 90% of the slop out there, the world-building actually makes sense. It’s a farming + behind-the-scenes flow that doesn't treat you like you have a room-temperature IQ.
Verdict: Is it Mid or Peak?
Look, it’s not Lord of the Mysteries or Reverend Insanity. Let’s be real, those are the GOATs and everything else feels like a cheap knockoff. But if you’re looking for a quick fix for your addiction that actually has some soul, this is it. It’s "not as stupid as the others," which in this day and age, is basically a 10/10.

It’s 450 chapters. Short enough to binge in a weekend while you’re avoiding your real-life responsibilities.

If you're desperate for something that isn't literal garbage, go here: https://zhnovel.com/book/i-created-the-internet-era-in-the-wizarding-world

Don't say I didn't warn you, brothers. Read it before your brain turns into mush from the other trash.

Why I’m Debugging "Parasitic Systems" in Dark Xianxia Novels

TruyenDichAI — Fri, 09 Jan 2026 15:33:32 +0000

As developers, we’re obsessed with systems. We love seeing how a simple set of rules can evolve into complex behavior.

Usually, in the world of Xianxia (cultivation) novels, these systems are boring. It’s always level++ until the MC is root. But recently, I found a sub-genre that feels more like malware analysis than power-fantasy—where cultivation is a parasitic process and enlightenment is a memory leak in your soul.

If you’re a dev who likes dark systems, biological logic, and "unsafe" code, here are 5 novels you need to check out.

1. Lord of the Mysteries: The King of System Consistency

In most novels, the magic system is a mess. In LotM, it’s a perfectly balanced API. You don't just "get stronger"; you ingest "potions" (packages) that give you specific "abilities" (methods). But be careful—if you don't "digest" the package properly, your internal state becomes corrupted, and you become an Eldritch monster. It’s the ultimate lesson in state management.

2. Parasitic Cultivator, I Can Understand Everything: The Body Horror Kernel

This is where it gets "low-level." In Parasitic Cultivator, immortality isn't a feature; it's a bug—literally.

Imagine a world where the "System" is actually a collection of parasitic organisms.

insect_eggs in the bloodstream.
dead_sh_occupying_the_brain.
centipedes emptying the host body.

The MC has an "Understand Everything" ability, which acts like a debugger attached to a production environment you were never meant to see. He sees the "source code" of the world, and it is horrifyingly efficient. If you like the idea of biological engineering gone wrong, this is #1 on your list.

Analyze the source here: Parasitic Cultivator - Read Online

3. Soul of Negary: The Remnant Process

Negary is a soul that was supposed to be null but refused to be garbage-collected. He is a persistent process that survives by hijacking other entities. It’s a fascinating look at an MC who views existence as a set of modules to be optimized.

4. Deep Sea Embers: Haunted Data Persistence

What if the world was a corrupted database and you were the only process aware of the deleted records? This novel captures the feeling of navigating a world that has been "overwritten" by something terrifying. The atmosphere is as thick as a README file written by a madman.

5. Warlock of the Magus World: The Ultimate Optimizer

The MC has an AI Chip in his brain. It’s basically a high-performance compute cluster that optimizes his every move. He views magic as a set of variables to be manipulated. It’s cold, calculated, and purely about efficiency—the developer’s dream.

CTA: Ready to see the "Backend" of Cultivation?

Check out the most unsettling "Parasitic" system currently being written:
👉 Read Parasitic Cultivator for Free

Have you ever found a webnovel system that felt like good (or bad) code? Let’s talk about it in the comments below.