Why a Front-End Veteran Turned to Blockchain: An InfoQ Interview with CSS Magic

InfoQ: Could you introduce yourself to our readers?

Hello, I’m known as “CSS Magic”. I entered the internet industry in Shanghai in 2008 and have accumulated ten years of front‑end experience, contributed to open‑source projects, run a technical public account, and translated a major CSS book in 2015.

What were the key turning points in your career?

Moving from a traditional industry to the internet was a major shift driven by curiosity. Joining Baixing.com five years ago marked another milestone that put my career on a steady track.

Earlier this year I encountered blockchain and DApp, and the excitement reminded me of my initial leap into the internet, suggesting another wave worth riding.

Why do blockchain and DApp attract you?

Initially I was indifferent to the hype, but I discovered that blockchain can not only record transactions but also run code, allowing developers to build applications directly on the chain.

A DApp (Decentralized Application) stores data on blockchain nodes and runs its logic there, eliminating the need for a separate backend.

For a front‑end engineer, this means I can create a complete product without learning a new backend language or maintaining servers, similar to the all‑in‑one experience of Flash creators.

How does a DApp’s architecture differ from a traditional web app?

A DApp consists of a client side (web, desktop or mobile UI) and a contract side (smart contracts). The client is familiar to front‑end developers, while the contract acts as the backend, exposing interfaces that the client calls to trigger business logic or CRUD operations.

What advantages do DApps have over traditional web apps?

Decentralization : Distributed nodes remove single points of failure, increasing data reliability and security.

Transparency : Most blockchains make block data and contract code publicly visible, enabling full public audit—a property rarely available in conventional web backends.

Immutability : Once deployed, contract code cannot be altered, which can be a benefit in scenarios where immutable rules are required.

These traits become advantages when applied to suitable use cases rather than being marketed as universal benefits.

Which application scenarios do you see for blockchain and DApps?

Data security and provenance for notarization, regulation, and voting.

Gaming, where an immutable ledger provides reliable asset ownership and trading.

Token economies, allowing developers to design incentive mechanisms within an ecosystem.

How do you choose a public chain for a DApp?

The first decision is similar to picking a mobile platform: you need a chain that is both easy to get started with and promising for the future . An easy‑to‑use chain gives quick wins, while a promising chain ensures the skills you acquire remain valuable.

Ethereum is the pioneering platform; despite some outdated technical parameters, its extensive ecosystem and ongoing evolution make it worth watching.

EOS offers strong performance and has attracted many developers, but its enterprise‑focused design and controversial choices raise a higher entry barrier, so I remain cautious.

There is also a newer public chain launched this year that quickly surpassed Ethereum in DApp count; I will reveal details in my upcoming QCon talk.

What skills, tools, and languages does a front‑end engineer need to build a minimal DApp?

Understanding blockchain fundamentals, DApp architecture, and product forms is essential.

On the client side you can use any familiar front‑end framework, editor, and build tool. Interaction with contracts typically requires the chain’s SDK.

The contract side follows the chain’s ecosystem: most chains provide a contract development framework, web IDE, and lint tools, but a small DApp can be written by hand after reading the documentation.

If a chain supports JavaScript as the contract language, the learning curve is minimal.

I will continue publishing tutorials on my public account to help developers.

Should front‑end engineers learn blockchain and consider a career shift?

It depends on personal risk tolerance. Cautious engineers may keep blockchain as a side interest while focusing on their planned path. Those who enjoy exploring new tech and tackling uncertainty may find the blockchain field more suitable.

The industry is still early and volatile, with unclear development directions and higher pressure, but it also offers the possibility of a career breakthrough for technically minded individuals.

Overall, blockchain is worth understanding for anyone planning their long‑term technical trajectory.