"I learned Unity the wrong way": developer warns against tutorial‑first learning after interview flop

The blog that sparked the thread

A developer named Darko Tomic published a candid blog post titled "How I learned Unity the wrong way," recounting three years of learning Unity by copying popular tutorials from Brackeys, Code Monkey and others. It has been reported that he built an AR game called Skeletons AR that reached the top of r/gamedev and allegedly remained the subreddit’s top post for a year — a splashy success that, he says, masked deeper gaps in his skills. The post went viral on Hacker News, and it has been reported that readers latched onto the moment he describes as his wake‑up call: a job interview in Belgrade where he could not explain why he had used Queue.

What went wrong — and why it matters

Tomic’s account is simple and stark: he followed tutorials, stitched forum scripts together, and treated a running build as proof of competence. He did not learn debugging, version control, or the reasoning behind common data structures; when something broke he changed lines at random and hit Play. Why did a one‑line interview question derail him? Because he had been copying patterns without understanding them — and in a technical interview, pattern recognition without explanation falls flat. He also notes, wryly, that this was before AI — seven‑day take‑home tasks were normal then — and that Googling isn’t the villain; it’s how you use search that separates a beginner from a senior.

The takeaway

The emotional center of the piece is clear: public praise felt like mastery until a single technical question stripped the illusion away. He wrote that moment was when he "knew I was not" a developer. Whether you’re starting out or mentoring someone, the lesson is blunt: shipping flashy demos can win applause, but fundamentals — debugging, data structures, and the ability to explain your choices — win jobs and careers.

Sources: darkounity.com, Hacker News