I Shipped a Tiny Internal Tool From the Browser
Here is the order that finally made ship a small internal tool stick for me.
Everyone does ship a small internal tool the hard way. The workflow: There is a faster path, and it starts with picking the right tool before you open it.
I reach for Replit for this. codes and deploys from a browser tab with no setup.
The step most people rush: review the output in place instead of regenerating from scratch. The workflow: Replit gets slow on big projects and debugging through a tab is limiting, so a quick edit beats a fresh prompt almost every time.
Step one is the boring part people skip: name the one result you want before you touch the tool. The workflow: The model cannot fix a vague goal, and a vague prompt just moves your confusion into its output.
Then I let Replit do the draft, but I keep my hands on the result. Replit codes and deploys from a browser tab with no setup, and that is exactly where it earns the time back.
Where it broke: gets slow on big projects and debugging through a tab is limiting. Watch that before you blame the tool.
I still do the thinking. Replit just does the assembly, and that is the right division of labor.