AllyshipContent Radar

News 2911

Chủ đề cộng đồng đang thảo luận

Crawl live-1795140900000 · 09:15 20 thg 11, 2026 · Xuất bản 09:31 20 thg 11, 2026

100 / 2911 chủ đề đạt ngưỡng 55 trong khoảng này.

41

Join us next Tuesday, November 24 in San Francisco for an evening with the teams building open weight models

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

artificialanlys 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Join us next Tuesday, November 24 in San Francisco for an evening with the teams building open weight models We'll kick things off with the latest Artificial Analysis benchmark data, followed by lightning talks and a panel. Register 👇 https://luma.com/artifi-mkho?utm_source=x

42

Amazon SageMaker AI now detects latency drift, idle GPUs, and missed optimizations on your inference endpoints

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Hazim Qudah 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p>Every inference endpoint is well tuned the day it goes into production. Teams choose an instance type, serving configuration, and scaling settings that suit the model and its traffic at launch. With the endpoint serving smoothly, they understandably move on to the next priority. The workload, however, rarely stays still. Traffic patterns evolve, prompts grow longer, serving engines such as vLLM ship new releases, SageMaker inference develops new optimization techniques, and new fine-tuned checkpoints change the resources your model needs. Over time, a well-tuned endpoint quietly drifts. Latency and time to first token edge upward. A configuration that was never quite ideal keeps missing available performance gains. A GPU provisioned for demand that never materialized sits idle week after week. Because nothing has failed, no alarm sounds, and the drift goes unnoticed until users feel it or the bill reflects it.</p> <p><a href="https://aws.amazon.com/sagemaker/ai/" target="_blank" rel="noopener">Amazon SageMaker AI</a> now monitors your generative AI inference endpoints and tells you when a change could improve performance or lower cost by using <a href="https://aws.amazon.com/blogs/machine-learning/amazon-sagemaker-ai-now-supports-optimized-generative-ai-inference-recommendations/" target="_blank" rel="noopener">Generative AI optimized inference recommendations</a>&nbsp;feature with Agentic experience in &nbsp;<a href="https://aws.amazon.com/sagemaker/ai/studio/" target="_blank" rel="noopener">Amazon SageMaker Studio</a>. Monitoring is on by default for SageMaker AI inference endpoints using vLLM serving containers and GPU instances, with no setup required, and you can opt out of endpoints. SageMaker AI looks only at operational signals: latency, GPU utilization, and the endpoint’s serving configuration. It does not read your requests or responses. From those signals, it surfaces three kinds of findings:</p> <ul> <li><strong>Latency drift:</strong> A week-over-week rise in median (p50) end-to-end latency or time to first token.</li> <li><strong>Unused capacity:</strong> GPUs you pay for that sit mostly idle.</li> <li><strong>Configuration gaps:</strong> A serving container that’s missing newer performance improvements or security patches, or an optimization such as speculative decoding or GPU kernel tuning that your model supports but the endpoint doesn’t use.</li> </ul> <p>SageMaker AI sends a finding through AWS Health, with one notification per endpoint that covers that endpoint’s findings. When a notification arrives, you can act on it in one place. It opens the SageMaker AI agentic experience in Amazon SageMaker Studio with the endpoint, and its recent traffic already filled in. From there, you run inference recommendations to benchmark your current configuration against alternatives and compare them side by side on response time, throughput, and cost per million tokens. That turns a judgment call into a decision backed by data. Benchmarks run on separate compute, and nothing changes on your endpoint until you choose to apply a result.</p> <p>In this post, we show how SageMaker AI monitors your endpoints and how to read the notifications it sends through AWS Health. We then show how to go from a notification to a benchmarked decision in SageMaker Studio. We walk through three example scenarios, show how to apply or dismiss a recommendation safely, and explain how to opt an endpoint out of monitoring.</p> <h2 id="solution-overview">Solution overview</h2> <p>SageMaker AI inference recommendations follow a four-step loop: observe, notify, recommend, and decide. Each step is designed so that you stay in control, and your production endpoint isn’t changed without your explicit action.</p> <ol type="1"> <li><strong>Observe –</strong> Monitoring of latency and capacity usage is on by default for eligible endpoints. It doesn’t read your requests or responses, and it carries no additional GPU cost.</li> <li><strong>Notify –</strong>&nbsp;When there is something worth acting on, you receive a plain language notification in AWS Health, plus email, explaining what was observed, why it matters, and a recommended next step.</li> <li><strong>Recommend (opt in) –</strong>&nbsp;One selection opens the SageMaker AI agentic experience in SageMaker Studio, prefilled with the endpoint and its observed traffic, so you can benchmark alternatives on separate compute.</li> <li><strong>Decide –</strong>&nbsp;Compare response time, throughput, and cost side by side. Production is not changed until you apply a result.</li> </ol> <p>The feature produces a few types of findings. The following table summarizes what triggers each one and what gets tested when you choose to benchmark.</p> <table border="1px" width="100%" cellpadding="10px"> <tbody> <tr> <td><strong>Finding</strong></td> <td><strong>What triggers it</strong></td> <td><strong>What a benchmark tests</strong></td> </tr> <tr> <td>Latency drift</td> <td>Response time moves relative to the endpoint’s week-over-week trends</td> <td>Tensor parallelism settings and alternate instance types or sizes</td> </tr> <tr> <td>Underutilized GPUs</td> <td>GPU utilization stays well below capacity over the window</td> <td>Cheaper instance types and smaller sizes at observed peak traffic</td> </tr> <tr> <td>Speculative decoding not enabled</td> <td>Model and container support it, but it is off (configuration based)</td> <td>Current configuration compared to speculative decoding enabled</td> </tr> <tr> <td>Serving container</td> <td>The endpoint’s serving container has a newer version with a performance improvement and security patches for critical and high finding Common Vulnerabilities and Exposures (CVEs).</td> <td>Current compared to updated container</td> </tr> <tr> <td>Untuned GPU kernels</td> <td>Kernel configuration is not tuned for the model and hardware</td> <td>Default compared to tuned kernels</td> </tr> </tbody> </table> <h2 id="prerequisites">Prerequisite

43

check out the results:

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

hesamation 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

check out the results: https://crusbench.com

44

Inside Amazon Connect Talent: The science of structured AI interviews

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

Sunitha Srivatsa 1 bài viết · AWS Machine Learning Blog
Nguyên văn nguồn
Chi tiết nguồn

<p><span class="TextRun SCXW252313659 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW252313659 BCX0">For organizations hiring </span><span class="NormalTextRun SCXW252313659 BCX0">hundreds or </span><span class="NormalTextRun SCXW252313659 BCX0">thousands of people, every interview presents the same challenge: How do you give candidates a consistent opportunity to </span><span class="NormalTextRun SCXW252313659 BCX0">demonstrate</span><span class="NormalTextRun SCXW252313659 BCX0"> their skills while gathering the evidence needed to make informed hiring decisions?</span></span><span class="EOP Selected SCXW252313659 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <p><span class="TextRun SCXW193008649 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW193008649 BCX0">Structured behavioral interviews offer a research-backed approach to this challenge. They use consistent, job-related questions and clear scoring criteria to give candidates an opportunity to </span><span class="NormalTextRun SCXW193008649 BCX0">demonstrate</span><span class="NormalTextRun SCXW193008649 BCX0"> their skills. Decades of research in industrial-organizational (I-O) psychology have shown that structured interviews help organizations evaluate candidates and predict job performance (Schmidt &amp; Hunter, 1998; Sackett et al., 2022). Yet delivering </span><span class="NormalTextRun SCXW193008649 BCX0">structured interviews</span><span class="NormalTextRun SCXW193008649 BCX0"> at scale requires </span><span class="NormalTextRun SCXW193008649 BCX0">significant time</span><span class="NormalTextRun SCXW193008649 BCX0"> and </span><span class="NormalTextRun SCXW193008649 BCX0">expertise</span><span class="NormalTextRun SCXW193008649 BCX0"> to develop</span><span class="NormalTextRun SCXW193008649 BCX0"> competencies, </span><span class="NormalTextRun SCXW193008649 BCX0">create q</span><span class="NormalTextRun SCXW193008649 BCX0">uestions, train interviewers, and evaluate responses consistently</span><span class="NormalTextRun SCXW193008649 BCX0">.</span></span><span class="EOP Selected SCXW193008649 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <p><span data-contrast="auto"><a href="https://aws.amazon.com/products/connect/talent/" target="_blank" rel="noopener">Amazon Connect Talent</a> <span class="NormalTextRun SCXW175523192 BCX0">brings established hiring science to AI-led interviews at scale. </span><span class="NormalTextRun SCXW175523192 BCX0">Connect Talent </span><span class="NormalTextRun SCXW175523192 BCX0">uses structured questions, adaptive follow-ups, and evidence-based scoring to help organizations gather consistent, job-related information while giving more candidates the opportunity to demonstrate their strengths.</span></span></p> <p><span class="TextRun SCXW66502508 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW66502508 BCX0">We built Connect Talent around three core design principles and evaluated how well the service </span><span class="NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW66502508 BCX0">applies</span><span class="NormalTextRun SCXW66502508 BCX0"> them through </span><span class="NormalTextRun SCXW66502508 BCX0">a combination of </span><span class="NormalTextRun SCXW66502508 BCX0">internal research and independent expert review. </span><span class="NormalTextRun SCXW66502508 BCX0">The </span><span class="NormalTextRun SCXW66502508 BCX0">findings offer a closer look at the science behind </span><span class="NormalTextRun SCXW66502508 BCX0">Connect Talent’s </span><span class="NormalTextRun SCXW66502508 BCX0">AI-le</span><span class="NormalTextRun SCXW66502508 BCX0">d,</span><span class="NormalTextRun SCXW66502508 BCX0"> structured interviewing.</span></span><span class="EOP Selected SCXW66502508 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <h2><b><span data-contrast="auto">Three core design principles</span></b></h2> <h3><b><span data-contrast="auto">1. Build interviews around job-related evidence</span></b></h3> <p><span class="TextRun SCXW227730746 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW227730746 BCX0">Connect Talent builds each interview around the competencies </span><span class="NormalTextRun SCXW227730746 BCX0">required</span><span class="NormalTextRun SCXW227730746 BCX0"> for the role. The service uses job requirements and </span><span class="NormalTextRun ContextualSpellingAndGrammarErrorV2Themed SCXW227730746 BCX0">established</span><span class="NormalTextRun SCXW227730746 BCX0"> occupational frameworks to create behaviorally anchored scorecards. Each scorecard defines specific strength and concern signals, and every interview question targets the behaviors it aims to uncover.</span></span><span class="EOP Selected SCXW227730746 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <p><span class="TextRun SCXW128739577 BCX0" lang="EN-US" xml:lang="EN-US" data-contrast="auto"><span class="NormalTextRun SCXW128739577 BCX0">The AI interviewer also adapts to each response. After every answer, it checks whether the candidate has provided enough evidence for the competency being assessed. When details are missing, it asks targeted follow-up questions. This approach preserves the structure of the interview while giving candidates more opportunities to explain their experience.</span></span><span class="EOP Selected SCXW128739577 BCX0" data-ccp-props="{&quot;201341983&quot;:0,&quot;335559739&quot;:0,&quot;335559740&quot;:278}">&nbsp;</span></p> <h3><b><span data-contrast="auto">2. Separate interviewing from scoring</span></b></h3> <p><span c

45

b12550

55

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

github-actions[bot] 1 bài viết · ggml-org/llama.cpp releases
Nguyên văn nguồn
Chi tiết nguồn

<details open=""> <p>ggml : add backend scheduler tests (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="5171818789" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/27258" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/27258/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/27258">#27258</a>)</p> <ul> <li> <p>Adds initial scheduler stress tests</p> </li> <li> <p>Adds new sleep op to simplify scheduler testing</p> </li> <li> <p>Adds testcase addressing <a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4474889411" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/23321" data-hovercard-type="issue" data-hovercard-url="/ggml-org/llama.cpp/issues/23321/hovercard" href="https://github.com/ggml-org/llama.cpp/issues/23321">#23321</a></p> </li> <li> <p>Adds experimental vulkan GGML_OP_SLEEP</p> </li> <li> <p>Improves structure and naming of previous tests. Adds new tests,<br> including one which detects the nkvo-bug correctly, and validates the<br> proposed hotfix.</p> </li> <li> <p>Cleanup: Removes CUDA specific comments and nvtx-markers</p> </li> <li> <p>Fix: forgot to add sleep specific test case</p> </li> <li> <p>Fix oversights identified by CI</p> </li> <li> <p>Drops default prints so that it behaves like other ctests. Adds -v flag<br> to toggle this behavior</p> </li> <li> <p>Fix: Early exit in CPU-only settings (cause for graviton CI fails)</p> </li> <li> <p>Improves stress_test_linked_list by removing overlap with<br> test_chain_all_backends and test_pair_user_inputs. The latter ones test<br> either activations or user inputs in isolation and just once, whereas<br> the stress test tests all combinations multiple rounds</p> </li> <li> <p>Exclude ACCEL devices from new tests due to incompatibility</p> </li> <li> <p>Fixes vulkan test failure in llvmpipe</p> </li> <li> <p>Adds asserts, improves comments and some checks</p> </li> <li> <p>Fixes nitpicks in white-space and variable naming</p> </li> <li> <p>Adds comments that certain vk drivers could time OP_SLEEP incorrectly</p> </li> <li> <p>Drops limitiation to CPU/GPU in test-sleep</p> </li> <li> <p>Aligns OP_SLEEP guards in cuda with vk guards (input shape and<br> contiguity)</p> </li> <li> <p>Implements feedback for OP_SLEEP to work in place (no copy)</p> </li> <li> <p>Apply non-code suggestions from JohannesGaesslers code review</p> </li> </ul> <p>Co-authored-by: Johannes Gäßler <a href="mailto:johannesg@5d6.de">johannesg@5d6.de</a></p> <ul> <li> <p>Removes struct backend_supports; enables tests to return skip, instead<br> of only pass/fail</p> </li> <li> <p>Make clang-tidy happy</p> </li> <li> <p>Removes sched_backend_caps, improves create_test_scheduler according to<br> feedback (L149)</p> </li> <li> <p>Removes "name" field from struct sched_check in favor of<br> ggml_set_name/ggml_get_name</p> </li> <li> <p>Drops unnecessary shader_clock.comp test and guards</p> </li> <li> <p>Replaces sched_ prefixes with helper_ prefix</p> </li> <li> <p>Moves test suite to new RAII types for better memory management</p> </li> <li> <p>Adds sleep option to test_chain_all_backends</p> </li> <li> <p>Adds sleep option to first-run arm of the y-shaped test</p> </li> <li> <p>Fix switchcase order for legibility in stress_test_dag</p> </li> <li> <p>Simplfies stress_test_linked_list via double for-loop</p> </li> <li> <p>Adds pseudo-random input to stress_test_linked_list, and runs all<br> transitions both with and without CPU input (next to activation copy as<br> input)</p> </li> <li> <p>Fix RPC Proto patch due to GGML_OPS bump</p> </li> <li> <p>Adds ggml-cpp.h treatment to test-sleep.cpp</p> </li> <li> <p>Adds TODO pointers for subsequent additional tests.</p> </li> <li> <p>Apply suggestion to ggml.h</p> </li> </ul> <p>Co-authored-by: Johannes Gäßler <a href="mailto:johannesg@5d6.de">johannesg@5d6.de</a></p> <ul> <li>Apply suggestion to tests/test-backend-sched.cpp</li> </ul> <p>Co-authored-by: Johannes Gäßler <a href="mailto:johannesg@5d6.de">johannesg@5d6.de</a></p> <ul> <li>Apply suggestion to tests/test-backend-sched.cpp</li> </ul> <p>Co-authored-by: Johannes Gäßler <a href="mailto:johannesg@5d6.de">johannesg@5d6.de</a></p> <ul> <li> <p>Fixes node compatibility check to not take buffer locations into account.<br> This led to skipped tests due to incorrectly rejected ops due to wrong buffer locations in multi-GPU (which is one of the scheduler behaviors under test)</p> </li> <li> <p>Apply batched suggestions from gg code review</p> </li> </ul> <p>Co-authored-by: Georgi Gerganov <a href="mailto:ggerganov@gmail.com">ggerganov@gmail.com</a></p> <ul> <li> <p>Completes callsite change of gg-suggestion</p> </li> <li> <p>Switch test-sleep from std::chrono::steady_clock::now() to ggml_time_us<br> to avoid mac clock drift and spurious test failures.<br> This makes the test a bit nonsensical on CPU (same clock checks itself),<br> but the test still has merit on the other backends where<br> independent device clocks are used.</p> </li> </ul> <hr> <p>Co-authored-by: Johannes Gäßler <a href="mailto:johannesg@5d6.de">johannesg@5d6.de</a><br> Co-authored-by: Georgi Gerganov <a href="mailto:ggerganov@gmail.com">ggerganov@gmail.com</a></p> </details> <p><strong>Website:</strong></p> <ul> <li><a href="https://llama.app" rel="nofollow">https://llama.app</a></li> </ul> <p><strong>Attestations:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/attestations/69858536">https://github.com/ggml-org/llama.cpp/attestations/69858536</a></li> </ul> <p><strong>macOS/iOS:</strong></p> <ul> <li><a href="https://github.com/ggml-org/llama.cpp/releases/download/b12550/llama-b12550-bin-macos-arm64.tar.gz">macOS Apple Silicon (arm64)</a></li> <li>macOS Apple Silicon (arm64, KleidiAI enabled) <a href="https://github.com/ggml-org/llama.cpp/pull/23780" data-hovercard-type="pull_

  • b12550 ggml-org/llama.cpp releases · 20 thg 11, 2026
46

Anthropic should give stock to Stack Overflow (and OpenAI too)

61

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 6 tương tác đã đo · Nguồn crawl

thetjmccarty 1 bài viết · HN: LLM
Nguyên văn nguồn
Chi tiết nguồn

Anthropic and OpenAI should give Stack Overflow a percentage of their company. They used all of Stack Overflow's data to train their AI models at the beginning of LLMs without paying for it because it was publicly available online. ChatGPT and Claude would not exist today without the 24 million coding questions and 36 million answers with code examples included, all created by real humans who took the time to write the questions and answers. Stack Overflow deserves to be rewarded for making Anthropic and OpenAI such a success. And all the developers who posted and answered questions on Stack Overflow should be given stock too.

48

QDA: Closed-Loop LLM Quantization Design with Agents

86

5 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · 9 tương tác đã đo · Nguồn crawl

Xingyang Li, Tianlang Zhao và 3 nguồn khác 1 bài viết · Hugging Face Papers, X
Biên tập tiếng Việt
Chi tiết nguồn

Bài báo nêu rằng post-training quantization là cách tiêu chuẩn để phục vụ LLM với chi phí thấp, nhưng công thức quantization tốt phụ thuộc vào từng mô hình và độ chính xác, nên chuyên gia phải thiết kế lại cho mỗi mô hình. Họ giới thiệu QDA, nơi một agent thiết kế recipe cho từng mô hình và độ chính xác. QDA đánh giá nhanh bằng cách chấm candidate theo KL divergence đầu ra so với mô hình gốc trên reasoning traces mà agent không thấy, và kiểm tra thêm các candidate hứa hẹn bằng long generations để bắt lỗi như repetition loops.

Post-training quantization is the standard way to serve large language models at low cost. However, the best quantization recipe differs across models and precisions. As a result, experts must redesign it for every new model, which is time-consuming and often sub-optimal. Fortunately, an LLM agent can take over this design by refining the recipe over rounds of building and evaluating candidates, so that more rounds lead to better recipes. However, evaluating one quantized reasoning model takes tens of GPU-hours, and combining methods from different codebases means porting each to the new architecture by hand. We present QDA, a system in which an agent designs the recipe for each model and precision. To make evaluation fast, QDA scores each candidate in minutes by its output KL divergence from the original model on reasoning traces that the agent never sees, and checks promising ones with long generations to catch failures such as repetition loops. To make building fast, QDA provides a library of public PTQ methods that are compatible with one another and with new model architectures. Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search. On the 320B-parameter MoE model GLM-5.3-Flash at NVFP4 W4A4, it recovers 98.3% of the FP8 model's accuracy, against 96.9% for the best vendor checkpoint. Every QDA checkpoint also runs on existing serving kernels with no inference overhead. We will release the library, the evaluator and the harness.

  • Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search.
  • Across four reasoning models, QDA improves accuracy over the strongest public recipe by 0.9, 1.4 and 2.2 percentage points on average at W4A16, W4A8 and W3A16, using 64 GPU-hours per search.
  • On the 320B-parameter MoE model GLM-5.3-Flash at NVFP4 W4A4, it recovers 98.3% of the FP8 model's accuracy, against 96.9% for the best vendor checkpoint.
  • Every QDA checkpoint also runs on existing serving kernels with no inference overhead.
51

Ask HN: Where do you see Software in 5 years?

64

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 26 tương tác đã đo · Nguồn crawl

Odbyteusz 1 bài viết · HN: GPT
Nguyên văn nguồn
Chi tiết nguồn

I wanted to hear some good opinions on all things AI and how they transform the Software industry. I'm anxious about the future and lack the foresight to form any opinion on what to do next. For context, I'm a L4 SWE that has more or less say 5-10 yrs of exp. I've enjoyed my work throughout my career, AI makes me ship more, much more than I could do 3 years ago. I feel I use it well and it translates into really good software. That said, what do you think happens in years to come with the Software industry in general? Do you think we'll go through a massive erosion of jobs? What's your perspective on that? I'm asking because I honestly don't know what to do: I can try to always keep up to date with newest technologies, best practices, but I'm only me; if the demand for SWEs and jobs falls to the floor, I'm not sure I'll always get a place at the table (i.e. land a job) and I'm wondering whether I should try to do something else in some other industry. It feels weird to be in a good position in life and still constantly worry about it getting worse.

52

Show HN: IT Thinks – Build a GPU from a Single NAND Gate

62

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 12 tương tác đã đo · Nguồn crawl

benbenhere 1 bài viết · HN: GPT
Nguyên văn nguồn
Chi tiết nguồn

Hi HN, I built a hardware puzzle game, you start with one NAND gate and every chip you finish becomes a part of next one. basic gates, adders, decoders, latches and finally GPU. last one are a chip that recognises handwritten digits. I am happy to discuss how we can create better levels to for those concepts. you can try demo/full game on Steam

53

Ask HN: Who Is Hiring? (November 2026 – We Give a Shit Edition)

61

1 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · 7 tương tác đã đo · Nguồn crawl

k_sze 1 bài viết · HN: AI agent
Nguyên văn nguồn
Chi tiết nguồn

This is a bit of a tongue-in-cheek. Since reading the "We need smart people who give a shit" story (https://news.ycombinator.com/item?id=50554045), and the comments underneath it, I realise that there is a good deal of engineers who are disgruntled by how AI is incompatible with smart people who give a shit, how it is turning us into meat proxies and Letzter Mensch. So this is a call for companies and employers with smart management who still give a shit, who do not demand that engineers replace their workflow with 5 parallel agent sessions, who appreciate the craftsmanship of humans, to step forward and post their job openings.

55

Orca - chạy một đội các coding agents bằng subscription của bạn

70

2 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

stablyai, orca_build 0 bài viết · GitHub discovery: AI agents, X
Biên tập tiếng Việt
Chi tiết nguồn

Orca được mô tả là cho phép chạy một “fleet of coding agents” (ví dụ Claude Code, Codex) với subscription của riêng bạn. Nền tảng có sẵn trên desktop, mobile và remote runtime.

Orca lets you run a fleet of coding agents (e.g. Claude Code, Codex) with your own subscription. Available on desktop, mobile and remote runtime.

  • Orca lets you run a fleet of coding agents (e.g. Claude Code, Codex) with your own subscription.
  • Orca lets you run a fleet of coding agents (e.g. Claude Code, Codex) with your own subscription.
  • Available on desktop, mobile and remote runtime.
56

Archify - biến ý tưởng/plan/codebase thành sơ đồ tương tác

70

2 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

tt-a1i, tom_doerr 0 bài viết · GitHub discovery: LLM, X
Biên tập tiếng Việt
Chi tiết nguồn

Archify được mô tả là chuyển mọi ý tưởng, kế hoạch hoặc codebase thành một sơ đồ tương tác “đẹp”. Nó là một agent skill cho Claude Code, Codex và nhiều nền tảng khác.

Turn any idea, plan, or codebase into a beautiful interactive diagram. An agent skill for Claude Code, Codex, and more.

  • Turn any idea, plan, or codebase into a beautiful interactive diagram.
  • Turn any idea, plan, or codebase into a beautiful interactive diagram.
  • An agent skill for Claude Code, Codex, and more.
58

LangChain Raises $300M Series C at $3B Valuation

79

3 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

langchain, hwchase17 và 1 nguồn khác 1 bài viết · LangChain Blog, X
Biên tập tiếng Việt
Chi tiết nguồn

LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.

LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.

  • LangChain raises $300M Series C at a $3B valuation, led by CapitalG, to help every company own its intelligence with LangSmith, the agent engineering platform.
  • LangChain raises $300M Series C at a $3B valuation, led by CapitalG
  • to help every company own its intelligence with LangSmith, the agent engineering platform.
59

LangSmith Tool Gateway: Secure, governed tool use for agents

62

1 tiếng nói · chưa gắn nhãn trưởng lab · 2 nền tảng · chưa có số tương tác · Nguồn crawl

langchain 1 bài viết · LangChain Blog, X
Nguyên văn nguồn
Chi tiết nguồn

LangSmith Tool Gateway, now in Public Beta, handles credentials, identity, and access for every agent tool call, with policies, approvals, and traces.

60

Read the process and how we're thinking about it here: https://www.llamaindex.ai/blog/building-toward-a-perfect-document-parsing-benchmark?utm_source=socials&utm_medium=tw_channel&utm_campaign=blogpos

63

2 tiếng nói · chưa gắn nhãn trưởng lab · 1 nền tảng · chưa có số tương tác · Nguồn crawl

LlamaIndex, jerryjliu0 0 bài viết · X
Nguyên văn nguồn
Chi tiết nguồn

Read the process and how we're thinking about it here: https://www.llamaindex.ai/blog/building-toward-a-perfect-document-parsing-benchmark?utm_source=socials&utm_medium=tw_channel&utm_campaign=blogpost&utm_content=blogperfectbenchmark

41–60 / 100
Trang 3 / 5