Code

Code

172 bookmarks
Custom sorting
Agent HQ for VS Code: Local, Cloud and Background agents
Agent HQ for VS Code: Local, Cloud and Background agents
Agent HQ just got a major upgrade in VS Code! Agent HQ is your single view to kick off, monitor, and review agent sessions for local, background, and cloud agents all at once - so you can seamlessly delegate tasks to the best-suited agent. With a unified agent experience in the Chat view, you can track every agent session, review code changes, and build smarter with GitHub Copilot in VS Code. 🔎 Chapters: TBD 00:00 Intro 00:29 Local agents 01:34 Cloud agents 01:54 Background agents 02:50 In summary 🔗 Link: VS Code release notes: https://aka.ms/VSCodeRelease 🎙️ Featuring: Kyle Daigle (@kdaigle) #vscode #agents
·youtube.com·
Agent HQ for VS Code: Local, Cloud and Background agents
devlikeapro/waha: WAHA - WhatsApp HTTP API (REST API) that you can configure in a click! 3 engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go)
devlikeapro/waha: WAHA - WhatsApp HTTP API (REST API) that you can configure in a click! 3 engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go)
WAHA - WhatsApp HTTP API (REST API) that you can configure in a click! 3 engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go) - devlikeapro/waha
·share.google·
devlikeapro/waha: WAHA - WhatsApp HTTP API (REST API) that you can configure in a click! 3 engines: WEBJS (browser based), NOWEB (websocket nodejs), GOWS (websocket go)
Why Reliability Demands Functional Programming: ADTs, Safety, and Critical Infrastructure
Why Reliability Demands Functional Programming: ADTs, Safety, and Critical Infrastructure
In banking, telecom, and payments, reliability is not a nice to have. It is table stakes. The most reliable systems I have worked on reduce entire classes of bugs before the code even runs. Functional programming and Algebraic Data Types (ADTs) let you push correctness into the type system, so illegal states cannot be constructed in the first place. **What you will learn** - How invalid states show up in real systems and why they cause costly incidents - How ADTs encode business rules so the compiler enfo...
·blog.rastrian.dev·
Why Reliability Demands Functional Programming: ADTs, Safety, and Critical Infrastructure
Software 2.0
Software 2.0
I sometimes see people refer to neural networks as just “another tool in your machine learning toolbox”. They have some pros and cons, they…
·karpathy.medium.com·
Software 2.0
L'Europa ha scritto un algoritmo per decidere quanto un cloud è sovrano e sganciarsi dalle big tech. Ma è più facile a dirsi che a farsi
L'Europa ha scritto un algoritmo per decidere quanto un cloud è sovrano e sganciarsi dalle big tech. Ma è più facile a dirsi che a farsi
La Commissione ha stabilito 8 obiettivi per raggiungere l'indipendenza dai fornitori Usa. Ma ci sono ostacoli tecnologici che rischiano di far fallire l'operazione
Riuscirà un algoritmo a trovare la strada verso quel cloud “sovrano” che da anni l'Unione europea insegue, senza successo? A stabilirlo sarà l'esito
·wired.it·
L'Europa ha scritto un algoritmo per decidere quanto un cloud è sovrano e sganciarsi dalle big tech. Ma è più facile a dirsi che a farsi
I Built the Same App 10 Times: Evaluating Frameworks for Mobile Performance | Loren Stewart
I Built the Same App 10 Times: Evaluating Frameworks for Mobile Performance | Loren Stewart
I needed to choose a framework for a mobile-first app at work. I started comparing Next.js, SolidStart, and SvelteKit, then expanded to 10 frameworks. Here's what I discovered about bundle sizes, performance, and the real cost of framework choices.
Next-Gen Frameworks Deliver Instant Performance: Marko (39ms), SolidStart (35ms), SvelteKit (38ms), and Nuxt (38ms) all achieve essentially instant First Contentful Paint in the 35-39ms range. This is 12 to 13 times faster than Next.js at 467ms.
While site downtime causes 9% permanent user abandonment, slow performance causes 28% permanent abandonment. That’s over 3x worse. Even more revealing: slowdowns occur 10x more frequently than outages, resulting in roughly 2x total revenue impact despite lower per-hour costs
·lorenstew.art·
I Built the Same App 10 Times: Evaluating Frameworks for Mobile Performance | Loren Stewart
SQL Anti-Patterns You Should Avoid - by Jordan Goodman
SQL Anti-Patterns You Should Avoid - by Jordan Goodman
Introduction
One of the most common mistakes I’ve seen is developers using SELECT DISTINCT as a quick way to eliminate duplicates that appear after a bad join. It’s an easy fix, but it hides a deeper problem. Usually, the duplicates exist because the join condition is incomplete or the relationship between tables isn’t truly one-to-one
·datamethods.substack.com·
SQL Anti-Patterns You Should Avoid - by Jordan Goodman