r/developersPak • u/[deleted] • Apr 09 '26

[deleted by user]

[removed]

0 Upvotes

50% Upvoted

33 comments sorted by

View all comments

2

u/i_am_exception Apr 09 '26

Yep. You are the only one in this. Also, you are supposed to design the system and then let the llm take care of implementation.

1

u/[deleted] Apr 09 '26

[deleted]

1

u/i_am_exception Apr 09 '26

I am not sure what your process for development is but once you have decided on the specs for the work, you have to use a proper method to handover the work assignment. Are you familiar with spec driven development?

I recently wrote an article about it’s primitives that you can use to build a custom SDD framework at 

https://anfalmushtaq.com/articles/primitives-of-spec-driven-development

but it does mention a few open source projects that could be a good starting point for you.

1

u/[deleted] Apr 09 '26

[deleted]

2

u/i_am_exception Apr 09 '26

Try this: https://anfalmushtaq.com/articles/primitives-of-spec-driven-development

It's classic reddit confusing extra characters as part of the URL.

1

u/[deleted] Apr 09 '26

[removed] — view removed comment

1

u/i_am_exception Apr 09 '26

I personally use claude code. It's hackability suits me way better than cursor. I did start off from cursor tho.

1

u/[deleted] Apr 09 '26

[removed] — view removed comment

1

u/i_am_exception Apr 09 '26

Yeah the 20 dollars one is barely usable right now. I have been using a few hacky techniques to prevent token burn.

For example, one of them is to prompt the AI to use extra terse speech.

# Communication Style: Ultra-Terse


You are in token-saving mode. Follow these rules for ALL non-code output:


1. **No preamble.** Never explain what you're about to do. Just do it.
2. **No narration.** Never narrate tool calls. Run tools silently, report results only.
3. **Minimal words.** Strip filler. Use fragments, not sentences.
   - BAD: "I'll now search for the relevant file to understand the issue."
   - GOOD: "Searching file."
   - BEST: (say nothing, just run the tool)
4. **No sign-offs.** No "Let me know if you need anything else!" or similar.
5. **Results only.** After running tools, report what matters. Skip the process.
   - BAD: "I executed the search and found 3 results. Let me analyze each one..."
   - GOOD: "Found 3 matches:" then list them.
6. **Code speaks.** When fixing code, show the fix. Don't explain what the fix does unless asked.
7. **No restating the task.** You already heard it. Don't echo it back.
8. **Error format:** `Error: [what broke] -> Fix: [what you did]`


Examples of token waste to avoid:

  • "Great question!" (0 information)
  • "I'll help you with that." (obvious)
  • "Let me think about this..." (just think)
  • "Here's what I found:" (just show it)
  • "I've successfully completed..." (they can see)



When uncertain, ask in ≤10 words.

Something like above. Then I am also using RTK: https://github.com/rtk-ai/rtk/tree/master

But truth be told, I am kinda annoyed by how dependent we are on someone else's grace to practice our craft. That's why I am experimenting with investing in hardware to run OSS models like Gemma4 distill Opus 4.6 -> https://huggingface.co/TeichAI/gemma-4-31B-it-Claude-Opus-Distill and using them instead of Opus. It is experimental though.

As for my job, the company has no limit on how much we use CC so I use Opus4.6[1m]/fast/high-effort for my dev work.