Arko Senapati

About

As a professional, I am deeply involved in VLSI and microelectronics and have robust grasp on semiconductor technologies. My skills extend from RTL coding to deep transistor level design. Thoroughly worked in RTL front end domain but also have keen understanding and knowledge of STA , DFT and physical design.

Badges

Tastemaker
Tastemaker
Gone streaking
Gone streaking

Forums

🗂️ Lancetta 0.68.0 — One place for every session

Lancetta 0.68.0 is out

Every Claude Code and Codex session, in one place: what waits on you, what you finished, and what the agents still keep on disk

•

3d ago

Pressing Back on my result page dropped users into onboarding. How do you handle history in wizards?

I have a multi-step onboarding wizard in Next.js that ends on a generated result page. All my checks passed. Then I finished the flow by hand, pressed the browser Back button on the result page, and landed in onboarding again, not on the main screen a finished user should return to.

The cause was one word. Each navigation in the wizard used router.push, which adds a new entry to the browser s history. So the whole wizard stayed in the history stack, and Back walked straight into it. It happened in three places in one component.

The fix: router. replace instead of router.push at those three places. replace overwrites the current history entry instead of adding one, so finished steps don t pile up behind the result page. I kept router.refresh() so the server data still reloads. I merged it and confirmed it by pressing Back on a real finished flow.

Why I missed it: unit tests check what a screen renders and what a function returns. History is browser state, and no test of mine pressed Back. I found it by hand.

When will traditional studios and agencies fully move to AI video?

Not just use AI for moodboards or a few shots but make it part of the normal production workflow.

What has to change first: quality, control, client trust, rights, pricing, or something else?

View more