Software Engineering Prompt(s)

[silk falcon]

Add a hashtag before Software and delete this line
Software Engineering Prompt(s) (SWE)

• [] 1. Discuss the Problem, Users, and Ethical Considerations
  • "AI, let's define the problem we're solving, identify our users, and address any ethical implications of our solution."
• [] 2. Create and Refine the High-Level Design
  • "AI, help me create a design document. We need to ensure illegal states are unrepresentable and refine our design based on potential feedback."
• [] 3. Setup Tools, Define Testing Strategy, and Write Unit Tests
  • "AI, let's identify the tools we need and write unit tests that focus on important behaviors and edge cases."
• [] 4. Write, Review, and Integrate Code
  • "AI, let's start writing SOLID code, review it together, and commit it frequently to integrate with the existing codebase."
• [] 5. Validate System with End-to-End Tests
  • "AI, let's write end-to-end tests to validate the entire system works from the user's perspective."
• [] 6. Document and Get Feedback
  • "AI, let's update our design document with final details, write user-level documentation, and actively seek out feedback."
• [] 7. Reflect and Learn
  • "AI, let's conduct a retrospective analysis to learn from our failures and successes."

[solar perch]

What's it supposed to do?

It would be interesting to compare and contrast the different prompts folks are using for software engineering.

[silk falcon]

it's supposed to implement a software project! by following the checklist and not moving on until each step is done, the process promotes a principled workflow with TDD and SOLID, thus preventing lots of bugs and frustration; for me the difference was night and day: making the high level design and tests before the code, is absolutely crucial to provide the best context and to verify the code works; it's tempting to ask them to write the code right away, and in my experience, that approach runs into major issues as soon as you attempt to add new features to the initial implementation, because without tests and SOLID, you wind up breaking old code when you add new code, and you don't even have unit tests to isolate where the broken code is

[solemn moth]

You have a real time sample to show case the use?

[silk falcon]

Let’s make one @solemn moth what kind of sample are you looking for?

[solemn moth]

i have a use case to build a Engineering Playbook... Eg: A new engineering Manager /Architect /Engineer Comes to a group , the Engineering AI PLaybook should be easy to tell step by step what to do , what process the org follows , stuffs to read , know the products , engineering practices , release practices , compliance practices .. also deviations on the playbook should be identified and understood on advantage and disadvantages...

From the playbook we can drill down to what you are saying in terms of design principles etc... kind of subset ...to the larger picture

[marble sentinel]

This might be interesting, do you have an actual chat session you could share using this? it would be an excellent example.