Nimra Tariq

For six months our users kept asking for an export to PDF option. We changed our plans. We spent three weeks building the export feature. To keep the dashboard simple we put the button inside an advanced settings menu.

We checked the analytics for two months. Out of 4000 users three people clicked the export button.

The export feature turned out to be unnecessary, for users. They only wanted to feel safe knowing their data could leave if they needed it. They never actually used the export. We spent three weeks building a psychological safety net, not a feature.

Has anyone else ever built an export feature just to reassure users? something they thought people wanted. No one ever touched the export.

A lot of WordPress code written with AI works on the first try, but WordPress adds its own traps: missing nonce and capability checks, unescaped output, and queries that are slow on big sites.

When AI hands you a plugin or theme snippet, what is your review routine before it touches a client site? Do you use a linter like PHPCS with the WordPress standards, a staging site, a second AI pass, or just read it line by line?

Has anyone else had this problem?

I tell Cursor to fix a database query and for no reason it starts "cleaning up" the frontend file I have open and removes all my Tailwind classes.

The backend code is working,. I just click accept.. Then I look at the browser and my user interface is completely messed up. I'm saving a lot of time on server logic. Spending all that time putting my styling back the way it was.

Is there a way to lock files so the AI can't change them at all during a refactor?