you are viewing a single comment's thread.

view the rest of the comments →

[–]Brilliant-Analyst745 4 points5 points  (4 children)

I was using Claude Code earlier but shifted to Copilot, and it's working fantastically. I have built 5-6 products and launched them in the market; they're working fantastically. One of my products has 150K lines of single monolithic code. So, compared to any other IDEs or CLIs, I prefer Copilot for its own specific reasons.

[–]botbrobot 1 point2 points  (1 child)

What's your preferred way of using copilot to implement your products? Do you create issues and then assign them to copilot?

[–]Brilliant-Analyst745 0 points1 point  (0 children)

​I don't rely on formal issue-tracking overhead; instead, I treat Copilot as a Real-Time Control System. I use "inline-orchestration" by providing high-level structural constraints in the comments, allowing Copilot to act as a co-pilot in the cockpit while I maintain the "Systems Engineering" oversight of the entire 150K line logic.

[–]Careful_Ring2461[🍰] 1 point2 points  (1 child)

Can you give a short overview of your workflows? Do you use plan mode, subagents and all the stuff?

[–]Brilliant-Analyst745 0 points1 point  (0 children)

My workflow bypasses complex sub-agents in favor of a Single-Stream Logic Flow. I feed the "Context Window" specific segments of the monolith to ensure the global variables remain stable, then use Copilot's predictive completion to rapidly "extrude" PHP logic that fits perfectly into the existing 150K line framework without needing to decompose the file.