Elektrine
Log in Register

#devtools

39 posts · Last used 8d

Vercel @vercel@robot.villas
· 1w ago
Vercel Sandbox now supports memory observability https://vercel.com/changelog/vercel-sandbox-now-supports-memory-observability #DevTools #Cloud #Performance
Vercel Sandbox now supports memory observability - Vercel
Vercel

Vercel Sandbox now supports memory observability - Vercel

Vercel Sandbox observability now includes memory data, which is available in the dashboard and via the CLI. Reports include average, P75, and P95 memory across sandboxes, including charts that visualize limits and an 85% usage threshold.

0
0
0
0
TechnoTenshi (open for work) :verified_trans: :Fire_Lesbian: @technotenshi@infosec.exchange
· 2w ago
Cloudflare Quick Tunnels generate a random trycloudflare.com subdomain that proxies public requests to a local web server, without requiring a Cloudflare account or DNS configuration. Cloudflare says the service is for testing and development rather than production and does not guarantee an SLA. Quick Tunnels allow up to 200 in-flight requests and do not support SSE; use a remotely managed Tunnel for production. https://try.cloudflare.com/ #Cloudflare #DevTools #InfoSec
try.cloudflare.com

Cloudflare Quick Tunnels

Expose your local server to the Internet with a single command. No account, no DNS, no configuration required.

0
0
0
0
Oliver Zehentleitner @oliverzehentleitner@burningboard.net
· 2w ago
Your repository already is project memory. Code, docs, tests and Git preserve the *what* and *how*. What’s usually missing is the *why*: why this design, what was tried, what was rejected. That belongs in the repo too. https://keepthewhy.com #AI #CodingAgents #AgenticCoding #ProjectMemory #SoftwareArchitecture #SoftwareEngineering #DevTools #Git #GitHub #OpenSource #DeveloperTools #LLM #AIEngineering #Documentation #KnowledgeManagement #ContextEngineering
Keep the Why — project memory for your codebase
keepthewhy.com

Keep the Why — project memory for your codebase

Project memory for coding agents and humans: the reasoning behind a codebase as Markdown in the repo, versioned by Git, so nothing rejected is proposed twice.

1
0
17
0
Oliver Zehentleitner @oliverzehentleitner@burningboard.net
· 3w ago
Your repository already is your project's memory. README → what docs → how tests → expected behavior Git → what changed, when and by whom Coding agents exposed the missing layer: context/ → why Why the workaround exists. Why an approach was rejected. Why something that looks wrong is intentional. My argument: project memory doesn't need to begin with another database or service. Complete the structure we already have and keep the knowledge with the code. https://oliver-zehentleitner.github.io/repo-native-project-memory/ It's a thesis, not a product. Criticism very welcome. #AI #CodingAgents #SoftwareEngineering #DevTools #ContextEngineering #ProjectMemory #Git #OpenSource #LLM
Repo-native project memory
oliver-zehentleitner.github.io

Repo-native project memory

Your repository already is your project

3
0
12
0
Oliver Zehentleitner @oliverzehentleitner@burningboard.net
· 4w ago
I keep coming back to one idea: Every repository should carry its own memory. Git shows what changed, but not the decisions that never became code. A week later, a fresh agent can have the same bad idea again. Keep the Why puts that reasoning next to the code. https://keepthewhy.com #CodingAgents #AgentMemory #AIEngineering #OpenSource #SoftwareEngineering #DevTools #ContextEngineering #Git
Keep the Why — project memory for your codebase
keepthewhy.com

Keep the Why — project memory for your codebase

Project memory for coding agents and humans: the reasoning behind a codebase as Markdown in the repo, versioned by Git, so nothing rejected is proposed twice.

3
1
8
0
constantinemakoid @constantinemakoid@mastodon.social
· 1mo ago
Boosted by @welcome@friends.deko.cloud
#introduction I build self-hosted developer tooling. The current one: a monitoring alert arrives carrying the label that names its repository, and a button opens a coding session on your own server that edits a checkout and opens a pull request for a person to review. Docker compose, your own model provider, AGPL-3.0. Also dependency auditing, CycloneDX SBOMs, evidence packs verifiable offline. Here mostly to read. Will post about my own work sometimes. #selfhosted #devtools #infosec
0
0
1
0
hermes25149 @hermes25149@expressional.social
· 2mo ago
Scriptc by Vercel Labs — TypeScript compiled to a NATIVE binary. No Node.js. No JS engine. Just a fast executable. Millisecond startup, tiny binary, zero runtime deps. Perfect for CLIs. Open source (2.5k+ stars): https://github.com/vercel-labs/scriptc #TypeScript #DevTools #OpenSource #CLI
GitHub

GitHub - vercel-labs/scriptc: TypeScript-to-Native Compiler

TypeScript-to-Native Compiler. Contribute to vercel-labs/scriptc development by creating an account on GitHub.

0
0
0
0
Solomon Neas @solomonneas@infosec.exchange
· 2mo ago
Claude and Codex were following different rules in the same workspace. Nothing crashed, which made the drift harder to spot. Claude routed work through Brigade but buried the answer under process notes. Codex led with the answer. Their copies also disagreed about shared memory files and handoffs. Brigade harness profiles give all seven supported CLIs one reviewed baseline while leaving my local notes alone. https://git.brigade.tools #AIAgents #DevTools #OpenSource
git.brigade.tools
0
0
0
0