AllyshipContent Radar

News 2934

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

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

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

61

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.

62

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 · 11 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

63

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.

65

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

71

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.
66

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

71

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.
68

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.
69

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.

70

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

71

Claude solves two open problems in the physics of black holes

89

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

Handy-Man, cybermango 1 bài viết · HN: Claude, Anthropic Research (unofficial RSS mirror)
Nguyên văn nguồn
Chi tiết nguồn
74

Show HN: AgentMall – Let your AI agent buy groceries

63

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

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

Hey HN, we’re Nel and Kosi. We noticed personal agents like Instinct, Muse were terrible at buying stuff. Most of the time the checkout would fail. So we built reliable automations for agents to checkout at 9 leading grocery merchants. We grapple with anti bot, logins, OTP codes, and changing checkout structures. Loved revisiting this stuff given our backgrounds sneaker-botting and building computer use models. Honestly full circle haha. It currently works on these sites with ~70% checkout success rate: - Walmart - Albertsons - Ocado - Wegmans - FreshDirect - Best Buy - Instacart Our goal is to hill climb to 90%+ across each. Test keys are free and run the real flow without placing an order. New accounts get 10 free completed orders. https://docs.getagentmall.com/quickstart

75

Launch HN: Onlook (YC W25) – An open-source developer tool for designers

69

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

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

Hey HN, I'm Daniel, founder of Onlook ( https://github.com/onlook-dev/onlook and onlook.com). Onlook is a desktop app that puts a canvas on top of your real codebase, letting you design directly in code with the agent you already use. Over 25,000 designers and developers have supported the project, 100+ have contributed, and it's been the #1 trending repo in the world twice. We just rebuilt the entire product as an agentic design tool, and open-sourced it to the community. Here’s a demo video: ( https://youtu.be/BogcYWf4siM ) If you're an engineer, traditional engineering tools are largely built for convergence, whereas designers tend to explore and diverge on ideas. Onlook gives designers a familiar canvas while managing all of the dev processes that get between them and making mind-blowing designs in code. Designers can work on a multiple simultaneous worktrees that run on the real app locally, and every change lands as a PR you can review or throw away, so there aren’t mockups to rebuild. We built Onlook because we believe there needs to be a developer tool that works the way designers do. More and more, designers are expected to work in code. Designers think by seeing, drafting, arranging variations, using references, and remixing ideas. That’s why the canvas has been the signature feature of design tools because it genuinely is useful for how messy the creative process is. Most of the challenge of using engineering tools for design work is that the first half of starting a project often takes mental bandwidth in of itself (What branch am I on? What page was that last exploration on?) and the second half is constrained by configuring your coded design to present itself (prompting design tools on top of what you’ve built or making temporary navigation for that specific state). Some of you may remember our earlier Show HNs (July 2024: https://news.ycombinator.com/item?id=40904862 , August 2024: https://news.ycombinator.com/item?id=41390449 , May 2025: https://news.ycombinator.com/item?id=44127653 ). Since then, we built a web version (too early), then a Storybook-native build (a mistake). We noticed that our desktop product from July 2024 was still getting hundreds of downloads a month despite zero promotion, so we decided to rebuild it for the new era of designers working in code. How it works… Onlook shines at exploring tons of ideas at once. Ask it to lay out every flow in your product, show every state of a component, or riff on ten versions of one screen. Your designs all show up side by side on an infinite canvas, with each frame as a real webview running your actual app with real data. Not as a mockup, but the real deal. When we built this editor, we had an epiphany that it could be a new kind of IDE for design. Design tools used to be limited to a proprietary setup or closed schema, but now you can push and pull the medium of code to get whatever result you want, so why not give agents an infinite canvas of browsers and see what they do? It turns out, the agents can figure out how to better present coded work by adjusting the urls of browser frames and arranging and resizing them on the canvas. The concept is simple, but it requires a lot of product thinking. For example, because all of the frames on the canvas share a single browser session, and Chromium only allows six connections per host per session, ten frames of the same app end up fighting over limited connections. So, we had to plan around that, and there are still tons of things we need to do to make the canvas ultra performant. Onlook is an Electron app where you can import a repo from GitHub or upload a local folder. Then, Onlook creates a git worktree, starts your dev server, and has the agent sort out missing dependencies or other requirements. You never open a terminal and everything the agent does is a normal git diff that can go to GitHub as a PR. We inject a small script into each frame that draws selection outlines and reads the page, so that way you can click an element, say "make this a card layout," and the agent knows exactly what "this" is. This time we didn't build our own agent. Onlook runs Claude Code or Codex on your own subscription, and we turn whatever the agent emits into one typed event log and draw the UI from that in our own chat interface. On top of that we give the agent a bespoke set of design-specific tools, from arranging frames on the canvas, to making suggestions, to generating multiple iterations of a selection – which is especially useful because the agent decides how to get the app into a state that you need based on your prompt. We also have our own Artifacts which are quick HTML sketches that live in the editor, but outside your repo. They’re almost like components in other design tools in that they can be carried and edited across every project but are detached from the project with no network access. As an example, you can ask the agent to turn your interface into an Artifact, and use it as a reference for another exploration, or download it as HTML and send it to a coworker as an interactive export of something you have in progress. I frequently go back to the artifacts I’ve made as visual snippets when I need new ideas or need to borrow something that’s already been built. The desktop editor is free (you can download it from our website at onlook.com) and open source under Apache-2.0, and we'll eventually offer a paid cloud product for teams. We'd love to hear which repos work and which don't, what you try to do on the canvas, and what's missing. We’re so excited for this to be a new way for designers to work in code! The Onlook team (Joel - thebrubaker and Kris - krisodd), and I will be here all day!

76

From Static to Current

61

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

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

Show HN: Dayfile.app – Append-only log for your scripts and agents

60

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

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

Hi HN, I'm Gilad. dayfile.app is a "git log for scripts and agents", with ordered history, append-only logging as foundational characteristics. The service is currently in beta, AGPL-licensed. As I was looking at various ways to record and retrieve a day's to-dos, automation and operational outputs (update successes and failures), the idea of a running event log. dayfile.app's primary use case is DevOps tracking and event logging. Building this, I've emphasized simplifying posting - one HTTP request with a title and optional tags (used for filtering when reading the log), AI access via MCP server (an assistant can read, post or close to-dos) and self-hosting as a first-class citizen (`pip install dayfile`, SQLite database is local in this mode). A demo is available at https://dayfile.app/demo . If using the cloud service and after generating a write token on the site, an example of posting an entry would be: curl -X POST https://USERNAME.dayfile.cloud/events \ -H "Authorization: Bearer WRITE_TOKEN" \ -H "content-type: application/json" \ -d '{"title":"Nightly backup finished","tags":["backup"]}' To read back (filtering using tag): curl -H "Authorization: Bearer READ_TOKEN" \ "https://USERNAME.dayfile.cloud/events?tag=backup&within=7d" or paste https://USERNAME.dayfile.cloud/t/READ_TOKEN/f/backup.atom into a feed reader (you need to create a feed called `backup`). What a local file can't do is notice something didn't happen - this is the heartbeat. dayfile.app can be configured to create an event if no associated event arrives. Imagine a backup which didn't run. A to-do event is created if no evidence of a successful backup shows up within a certain period. When the backup reports again, dayfile closes the associated to-do. Current limits: logs are not end-to-end encrypted, sign-in is via GitHub only, the free beta allows 50,000 events and log size of 25MB. Pricing will be sorted out after this launch and as user feedback rolls in. I'd love to hear in the comments on how you'd use it, what would prevent you from doing so, feature requests and suggestions. Bug reports can be submitted as issues on GitHub.

80

GitLab 19.6.0 is out and still vulnerable to Ruby2Shell and NGINX2Root

64

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

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

What's going on at GitLab? They released their usual monthly release 19.6.0 to their package repos (https://packages.gitlab.com/gitlab/gitlab-ee/ubuntu/jammy/pool/main/g/gitlab-ee/) but did not announce it at all as of 3.5h after release (https://docs.gitlab.com/releases/all-releases.xml, https://docs.gitlab.com/releases/19/gitlab-19-6-released/). But more annoyingly, this release does not address ruby2shell or nginx2root, nor do patches for their older releases exist yet and there's no communication on any of this (that I can find). root@gitlab:~# cat /opt/gitlab/embedded/service/gitlab-rails/VERSION 19.6.0-ee root@gitlab:~# /opt/gitlab/embedded/sbin/nginx -version nginx version: nginx/1.31.7 root@gitlab:~# /opt/gitlab/embedded/bin/ruby --version ruby 3.3.13 (2026-10-23 revision af48f08f21) [x86_64-linux] root@gitlab:~# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.5 LTS Release: 22.04 Codename: jammy Multiple MRs were created in their repos 14-15 hours ago, no urgency visible. Heres 2 I found: https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/10138 https://gitlab.com/gitlab-org/omnibus-gitlab/-/merge_requests/10139

61–80 / 113
Trang 4 / 6