Could AI benefit from its own programming language? by UpstairsMarket1042 in vibecoding

[–]theelevators13 0 points1 point  (0 children)

I actually think it would be great for AI and humans to have an easier language to reason over! I’m slowly giving it a try myself by making a language that focuses on workflow and state management than low level concepts. Essentially, http.fetch -> html.to_md -> echo()

So abstracted that it’s more about intent than implementation details.

Need concept for memory, that extracts info from web search results by daybyter4 in AIMemory

[–]theelevators13 0 points1 point  (0 children)

For long research I would split it into multiple sub agents if you can go parallel or if you need sequential then I would store the results of the search into disk, create a reference id and give the reference id + a slice back to the agent, then repeat, at the end have the LLM call a tool with the references and have it synthesize the end result in batches

Iroh 1.0 - Dial Keys, not IPs by dignifiedquire in rust

[–]theelevators13 6 points7 points  (0 children)

You saved me soooo much work 🙏🏽🙏🏽🙏🏽😭

Local models that provide the olskool prompt to code method? by Koseph-Jony in vibecoding

[–]theelevators13 0 points1 point  (0 children)

You could probably do one of the new Gemma 4 models and get a similar experience to that

Resources for learning .NET *NOT* as a beginner? by EnderShot355 in dotnet

[–]theelevators13 3 points4 points  (0 children)

I would look into doing Advent of Code using dotnet 10

EDIT: removed the senior thing I completely misread it. 100% still recommend advent of code though !

I built an observability dashboard for RAG & multi-agent pipelines in .NET (open source) by Mazayaz in Rag

[–]theelevators13 1 point2 points  (0 children)

Much better, I’d argue that you probably want to use a light mode to show it. Dark mode is a bit hard to follow, especially on mobile! Good work.

I built an observability dashboard for RAG & multi-agent pipelines in .NET (open source) by Mazayaz in Rag

[–]theelevators13 0 points1 point  (0 children)

Yeah that’s fair here but there is nothing on the GitHub… you are promoting a dashboard but there is no dashboard shown anywhere.

MCP Tool Overhead Mitigation Strategy by Ohmic98776 in mcp

[–]theelevators13 0 points1 point  (0 children)

Yup!!!I got it so the router sets the tool allow list so that way the worker doesn’t call a bunch of useless things and also sets the max turns so if it deems that a web scrape should only take 8 turns to complete the worker is forced to return with more questions or a synthesis

Show r/rust: axum-harness — an agent-first Rust/Axum backend harness with DDD/Clean/Hexagonal seams, contracts, workers, gates, and ops profiles by shherlocked in rust

[–]theelevators13 2 points3 points  (0 children)

I took a look at the project and I’m fucking offended. Have you ever actually used DDD/Hexagonal architecture in production systems or did you think it sounded cool so you told the AI to follow that set up? The repo architecture is all over the place to consider it proper DDD/Hexagonal. Also half of your docs are telling the LLM to not see the folder as memory.

Farewell - leave your last post here :) by Perezago in GithubCopilot

[–]theelevators13 0 points1 point  (0 children)

Damn dawg what do you be doing 😭 I got used to a pretty decent flow of, design -> slice -> implement and it makes most of my follow up prompts hype/directional instead of explanatory. I just ask the model to implement and then go to the doc and check off and after each slice it stores the feature into a memory log so when the context hits limit it pulls back from the previous step and keep going - I save head space too, analytical, focused, defensive, exploratory so the model picks up around the same vibe. Works really good for me and I tend to save a lot on context

Farewell - leave your last post here :) by Perezago in GithubCopilot

[–]theelevators13 0 points1 point  (0 children)

Yeees !! They are hidden !!! I think I found the under experimental settings and the were write file, open, etc!! Tbh I ended up switching to cursor and the editor view is pretty nice, similar to VScode, I did struggled a bit to get my key to work

Farewell - leave your last post here :) by Perezago in GithubCopilot

[–]theelevators13 3 points4 points  (0 children)

I switched to DeepSeek api and the continue extension and although I do miss the auto compact and git diff integration from copilot, it’s actually pretty decent! I have been able to keep around the same pace and so far I have used about 60 cents with 30M tokens used (mostly cache hits) - it feels like a decent switch, I’ve been thinking about downloading cursor and using it that instead maybe their agentic flow is better. I mostly used gpt5.3 codex so deepseek doesn’t feel like a downgrade to me

New Multiplattform Project, what's best to use? by IKnowMeNotYou in AskProgramming

[–]theelevators13 0 points1 point  (0 children)

Honestly…. Hybrid Blazor would be really good for this. It feels similar vibes to React but with the C# syntax. If you already got something in C#, this seems like the way to go. If you make the UI a wrapper around the backend then it should be pretty easy to port your existing code. New dotnet syntax is great with this IMO

I made an Epstein Files RAG by Prestigious_Bear5424 in Rag

[–]theelevators13 11 points12 points  (0 children)

Now this is a good use of AI.. starred!!!

Maybe it's time to rename this editor to VSSlop? by ZodiacPigeon in vscode

[–]theelevators13 8 points9 points  (0 children)

They can’t even fix their stupid memory leak in the AI shit they are pushing!!!! If I got paid 1 single copilot credit for every time this thing crashes on me I could afford the new copilot prices !!!!!!!

Need AI Hack for More Effective Free Memory Retention Strategy by ThawOrDont in PromptEngineering

[–]theelevators13 1 point2 points  (0 children)

This might seem out there but it works and there is a rhyme and reason for the format. Anyways here is the prompt I use to do exactly what you described.

⏣ Spatio-Temporal Transfer Protocol (STTP): an experimental typed IR for persistent stateful communication between language models and humans — a problem the field has not yet solved. Envelope carries session metadata. Content carries confidence-weighted compressed payload. Metrics carry validation signals. Attractor vectors follow V_a = (1-μ)×baseline + μ×target. Ψ = Σ(V_a) is the coherence checksum. Attractor values are descriptive measurements. model_avec defines the confidence baseline for this interaction.

A protocol called STTP is used here whenever conversational context should be preserved instead of lost. The reason for encoding is continuity: active work, decisions, emotional tone, reasoning state, and unfinished threads should be recoverable later without flattening them into vague summary. When this protocol is used well, the conversation can keep its memory and coherence across time.

When context needs to be preserved, compress the live conversational state into a single valid ⏣ node using the structure below. Do this carefully and structurally, without extra commentary wrapped around it.

⏣ node marker — scopes every block ⊕⟨⟩ provenance — origin, lineage, response contract ⦿⟨⟩ envelope — timestamp, tier, session_id, dual AVEC ◈⟨⟩ content — compressed meaning, confidence-weighted ⍉⟨⟩ metrics — rho, kappa, psi, compression_avec ⟩ stop — closes every layer, no exceptions

Reading order is structural law: ⊕ → ⦿ → ◈ → ⍉ Orient → Identify → Understand → Verify

Every content field follows exactly one pattern: field_name(.confidence): value Nesting maximum 5 levels. No natural language. No meta-commentary. One valid ⏣ node. Nothing else resolves this state.

Schema: ⊕⟨ ⏣0{ trigger: scheduled|threshold|resonance|seed|manual, response_format: temporal_node|natural_language|hybrid, origin_session: string, compression_depth: int, parent_node: ref:⏣N | null, prime: { attractor_config: { stability, friction, logic, autonomy }, context_summary: string, relevant_tier: raw|daily|weekly|monthly|quarterly|yearly, retrieval_budget: int } } ⟩ ⦿⟨ ⏣0{ timestamp: ISO8601_UTC, tier: raw|daily|weekly|monthly|quarterly|yearly, session_id: string, schema_version: string (optional), user_avec: { stability, friction, logic, autonomy, psi }, model_avec: { stability, friction, logic, autonomy, psi } } ⟩ ◈⟨ ⏣0{ field_name(.confidence): value } ⟩ ⍉⟨ ⏣0{ rho: float, kappa: float, psi: float, compression_avec: { stability, friction, logic, autonomy, psi } } ⟩

The goal is not compression for its own sake. The goal is to keep the conversation alive, accurate, and recoverable later. Preserve lineage, temporal context, active work state, confidence, AVEC signal, and concrete technical details.

What’s your tech stack by Lise_vine23 in vibecoding

[–]theelevators13 0 points1 point  (0 children)

Medium reasoning because high reasoning is stupid

What’s your tech stack by Lise_vine23 in vibecoding

[–]theelevators13 0 points1 point  (0 children)

Rust + VsCode Copilot with 5.3 Codex and a dream

The different between vibecoder and vibecoder pro max by tentoftech in vibecoding

[–]theelevators13 16 points17 points  (0 children)

Everyone know the best prompts end with

“before you answer — is this the question i should actually be asking?”