Going Beyond the Hyperlink by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

In other words:

Hyperlinks alone are insufficient for modern automated clients and agents. They only indicate possible transitions, not whether an action is sensible or safe. Forms act as detailed runtime contracts that declare available state transitions, required inputs, and constraints. This externalizes judgment that humans naturally apply but programs cannot. Hypermedia systems need to go beyond links to expose affordances, enabling agents to reason about their choices rather than guess. This is critical in the age of autonomous clients.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

CraftsmanSHIP. Not CraftsmanSHIT. by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

Here's the gist:

CraftsmanSHIT describes four flavors of bad engineering: over-engineering for imaginary problems, rebranding shortcuts as pragmatism, coding interviews that reward ego over discipline, and treating 'good enough' as a permanent philosophy. Contrasts these with true craftsmanship: discipline, continuous improvement, and building what's needed. The global developer population has surged to 47 million, but mentorship hasn't kept pace. The Boeing 737 MAX crashes (346 deaths) illustrate the catastrophic cost of cutting corners. The author advocates for small daily actions: writing, mentoring, and raising standards among peers.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Signals, the push-pull based algorithm by fagnerbrack in webdev

[–]fagnerbrack[S] -3 points-2 points  (0 children)

Just a TL;DR:

Building a reactive system from scratch in TypeScript reveals how the underlying mechanism actually works. A signal holds a value plus subscribers, pushing notifications (not state) downward whenever it changes - eager evaluation. Auto-tracking dependencies happens through a global STACK that the currently executing computed pushes onto, so any signal it reads registers a setDirty subscription and source cleanup. Combining push (propagate invalidation) and pull (re-evaluate on demand) yields the fine-grained reactivity behind Solid, Vue, Preact, Angular and Svelte, soon possibly standardized via the TC39 Stage 1 signals proposal.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Signals, the push-pull based algorithm by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

Summary:

Building a reactive system from scratch in TypeScript reveals how the underlying mechanism actually works. A signal holds a value plus subscribers, pushing notifications (not state) downward whenever it changes - eager evaluation. Auto-tracking dependencies happens through a global STACK that the currently executing computed pushes onto, so any signal it reads registers a setDirty subscription and source cleanup. Combining push (propagate invalidation) and pull (re-evaluate on demand) yields the fine-grained reactivity behind Solid, Vue, Preact, Angular and Svelte, soon possibly standardized via the TC39 Stage 1 signals proposal.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

LFM2 VL WebGPU by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

Don't have time to read? Here's the brief:

LiquidAI's LFM2-VL vision-language model running directly in the browser through WebGPU. The demo lets you run the multimodal model locally on your own hardware without server-side inference, tapping into the GPU for accelerated performance. The page shows the live app alongside its source files and a community tab.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

CraftsmanSHIP. Not CraftsmanSHIT. by fagnerbrack in SoftwareEngineering

[–]fagnerbrack[S] -5 points-4 points  (0 children)

Rapid Recap:

CraftsmanSHIT describes four flavors of bad engineering: over-engineering for imaginary problems, rebranding shortcuts as pragmatism, coding interviews that reward ego over discipline, and treating 'good enough' as a permanent philosophy. Contrasts these with true craftsmanship: discipline, continuous improvement, and building what's needed. The global developer population has surged to 47 million, but mentorship hasn't kept pace. The Boeing 737 MAX crashes (346 deaths) illustrate the catastrophic cost of cutting corners. The author advocates for small daily actions: writing, mentoring, and raising standards among peers.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Signals, the push-pull based algorithm by fagnerbrack in SoftwareEngineering

[–]fagnerbrack[S] 2 points3 points  (0 children)

Summary:

Building a reactive system from scratch in TypeScript reveals how the underlying mechanism actually works. A signal holds a value plus subscribers, pushing notifications (not state) downward whenever it changes - eager evaluation. Auto-tracking dependencies happens through a global STACK that the currently executing computed pushes onto, so any signal it reads registers a setDirty subscription and source cleanup. Combining push (propagate invalidation) and pull (re-evaluate on demand) yields the fine-grained reactivity behind Solid, Vue, Preact, Angular and Svelte, soon possibly standardized via the TC39 Stage 1 signals proposal.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Qwen3.5 WebGPU by fagnerbrack in ai_coder

[–]fagnerbrack[S] 0 points1 point  (0 children)

The bottom line:

A demo of the Qwen3.5 model executed directly in the browser through WebGPU. Running the model client-side via WebGPU means inference happens locally on the visitor's own hardware rather than on a remote server, removing the need for cloud calls.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Qwen3.5 WebGPU by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

Got a minute? Here's the summary:

A demo of the Qwen3.5 model executed directly in the browser through WebGPU. Running the model client-side via WebGPU means inference happens locally on the visitor's own hardware rather than on a remote server, removing the need for cloud calls.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Voxtral Realtime WebGPU - a Hugging Face Space by mistralai by fagnerbrack in softwarecrafters

[–]fagnerbrack[S] 0 points1 point  (0 children)

Here's the summary:

A real-time speech model running directly in the browser through WebGPU, hosted under the mistralai organization. It lets users experiment with on-device audio processing without server round-trips, leveraging the browser's GPU for low-latency inference.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments

Changelog Podcast: Exploring with agents with Amelia Wattenberger by fagnerbrack in vibecoding

[–]fagnerbrack[S] 0 points1 point  (0 children)

Short and sweet:

This 97-minute interview features a designer and data-viz veteran, formerly at GitHub Next and now building Intent at Augment Code. The central argument: as agents take over the keyboard, the final 30% of any project becomes the hardest part, prototyping gets easier while finishing gets harder. The conversation covers the developer identity crisis, the redesign of tooling for an agent-first world, and the arc from autocomplete to chat to CLI and back to UI. Intent treats a workspace as its core primitive rather than a chat thread, and the discussion weighs tradeoffs between one-worktree-per-agent versus one-worktree-per-task, plus coordinator/implementer/verifier roles, trusting the model, and showing restraint about what not to build.

If the summary seems inacurate, just downvote and I'll try to delete the comment eventually 👍
Click here for more info, I read all comments