AI coding is pretty mindblowing but sometimes it's a headache built on a mountain of bugs. Usually that comes down to issues with how you prompt. So, with that in mind, I'm starting a crowdsourcing discussion so we can all improve our prompts and in turn our apps.

Share the exact prompts that turn blank AI requests into real world code. Show us how you go from generate a REST API to a deployable service in just a few steps.

What to post:

Being an engineer myself, I see that many people are outputting more code than ever. Some of it being generated vs. written, the volume of code being outputted has definitely risen. 
There seems to be a shift from "is this something we can build?" to "should we build this and ship it?"
For people who have been recruiting or looking to recruit recently, what roles are you hiring for? 

1. Role title (I've seen a rise in PM's and Designers personally)

2. What exactly can they do that AI can't (yet)

3. Specific signal that you look for when hiring

Are you moving headcount from one type of role to another? 
Would be interested to hear from other growing teams! 

MIT just dropped a fascinating (and slightly scary) study.

They had participants write SAT-style essays using:

1. ChatGPT

2. Google

3. Just their brains

What happened?

I am possibly preparing for marketing my own tool (a Chrome extension) and collect the activities I can use for future visibility and possible purchases.
Right now, I am thinking about basics:

• SEO within the plugin (name, description, description in the Chrome Store + visuals)

• Listings in directories

• Reddit mentions

• Building in public

I am aware that it is not sufficient, and there will be much more work.

I m restyling a live app screen by screen, with Claude Code doing the edits. My test suite has 262 tests and all of them pass, but none of them check how a page looks. So a change to shared styles could break a screen and nothing would tell me.

Before each change, I have the agent screenshot every screen I m not supposed to touch, using a fake signed-in session and mocked API responses so no real data is involved. After the change, it captures them again and compares them pixel by pixel. Anything that differs has to be explained.

That caught something I would never have seen. 34 screens matched exactly. One modal didn t: 1,334 of about 215,000 pixels were different. To my eye, before and after looked identical. The cause was that my first version moved the page into a new wrapper, and the old container had been quietly centering the modal s heading. The new one didn t. No test would have complained.

It also showed that a modal kept outside the new wrapper still changed colour, because my theme variables are set on the whole page, not just the wrapper. I had to re-scope the old colours around the modal.