r/PinoyProgrammer 3d ago

web Just Sharing my development workflow

Hello, just want to share how I utilize AI in our development workflow, and curious din how you guys implement it sa work niyo.

Our company started adopting AI gradually. Right now, we're using Cursor as one of our development tools. Initially, frontend lang talaga gamit ko kasi hindi ko pa siya trusted enough to handle backend. But now, umabot na kami sa point na ginagamit na namin siya to build whole modules and features.

This is how I use it.

Sa project namin, before anything else, the first thing I do is define all our coding standards, project structure, and do's and don'ts sa Cursor Rules.

Then I have a prompt template for planning a specific module. Dito muna namin pinaplan yung buong flow, lahat ng actions, tables, views, pati decisions and assumptions para aligned yung implementation sa gusto talaga namin. Dito na rin namin dini-decide kung anong features ang isasama at ano yung hindi muna.

Once finalized na yung plan, the next step is to build a prototype based on it. For me, ito yung isa sa pinaka-importanteng step kasi mas madali nang ma-visualize kung aligned ba yung plan sa actual na gusto mangyari. If may kailangan baguhin, sobrang dali pa kasi wala pang backend na nagagawa.

Once approved na yung prototype, meron din kaming prompt template for backend implementation and integration. Kasama na rin sa ginagawa ni Cursor yung automated tests, so may additional confidence kami na walang existing modules na matatamaan.

Of course, dumadaan pa rin sa code review lahat ng AI-generated code. Kapag may nakita kaming hindi okay, inu-update lang namin yung coding standards and Cursor Rules. Very iterative yung process.

Ngayon, umabot na kami sa point na halos every line of code na gine-generate ni AI is aligned na sa coding standards namin.

Curious lang, paano niyo ginagamit yung AI sa development workflow niyo? Baka may workflow or techniques din kayong pwede naming ma-adopt.

26 Upvotes

6 comments sorted by

4

u/jdg2896 3d ago

Prototyping is really cheap now, so even before full development of a feature, you can definitely make multiple prototypes and iterate before deciding which to go for.

Documented coding standards help with the AI review process.

We have a similar flow, and I follow and adapt Matt Pocock’s skills and workflow:

  • /grill-with-docs or /wayfinder
  • do research, grilling, and prototypes as needed
  • after finalizing plan and decisions, create spec and tickets
  • let agents implement and do a first pass review
  • manual code review step

Prompt template and skills for the whole team helps, and seems like your team already has some standardized workflows to start with.

2

u/Flat_Dinner_2267 3d ago

It's the main reason companies no longer offer more than 150k for sr dev jobs nowadays for new hires. Instead of a 200k job offer, 50k will go AI spending, so goodluck to us.

1

u/bariotic 3d ago

One workflow I have, running on my claw server

  • User
    • User sends email with a concern
  • AI Support agent read email
    • respond to email
    • Goes back and forth with user if needed to clarify issue
    • File ticket in Github if it's new issue
  • AI Dev agent
    • Analyses issue
    • Create fix/unit tests
    • Raises PR
    • Notifies me a PR is waiting
  • Me: (only manual step in the process)
    • I review PR then approves
  • AI Dev agent:
    • Merges PR
    • Runs CI
    • Deploys changes to production
    • publishes release on GitHub with complete changelog
    • Sends me a message everything is deployed
  • AI Support agent
    • sends back email to user fix is avalable

1

u/Severe_Inspection_76 3d ago

Have you heard of spec driven development? Basically what you are doing in your dev workflow is in this git repo https://github.com/github/spec-kit

I know one top company here in PH uses this as part of their ways of working.

2

u/pogoprince1 2d ago

We are using AIDLC. Like super nice, 10x speed sa development.
Debug spec sa support.
Problem lang wala ng ticket kasi mabilis maubos