Anthropicãšpstackãèšã£ãŠãããšããã®ã¯å³ã¡E2Eã§ããŒãã¹ã®ç©ŽãåããŠã»ããã ãã§ãããªãã®ã§ã¯ããšããæ°æã¡ã
E2Eã«é Œããããã¹ãã§ã¯ãªãããè¿ãå°æ¥äžèŠã«ãªãïŒ= 圢骞åããïŒããä»åŸã®å€æŽã«è¿œåŸã§ããªããªãããã®ã©ã¡ããã ãšæãã
ãæ€èšŒãéèŠïŒããšAnthropicãpstackãšåãããšèšã£ãŠãã
ç¹ã«éèŠãªã®ã¯ ã»E2Eãã¹ãïŒæåªå
ïŒ ã»ããããã£ãã¹ã ã»å·®åãã¹ã
å®éã«åãããŠç¢ºèªãã倱æã¯æå€§3åèªåä¿®æ£
âããã§ããã¡ãªã人éãžã
ããã§å質ãä¿ã¡ã€ã€å€§é䞊åãå¯èœ
claude.dev/blog/how-the-clauâŠ
104
å
šäœçã«æ¥æ¬èªè©±è
ã®æžããæç« ã£ãœãèŠããã
ãã©ã³ãµã æ»æïŒèº«ä»£éèŠæ±æ»æïŒããªããŠã«ãã³æžãã¯ã©ã³ãµã ïŒèº«ä»£éïŒãšèº«ä»£éãšããåèªãåãããŠããªããšæç«ããªãããAIãæ°ãå©ãããŠæ³šéãå
¥ãããšãèãã¥ããæ°ããã
224
ðš Mermaid has been rewritten, again. In Rust!
ð§ââïž Introducing Ondine. ð§ââïž
- 200B runtime.
- Renders diagrams in ~50µs.
- 1,943x smaller, 2.8x faster than Pele.
- 13,467x smaller, 670x faster than Mermaid.
- Still 0 dependencies.
ããããðŠ retweeted
As you invite more agents to our work, and create software factories to be more productive than ever, youâll soon outsource everything to an agent, even the thinking.
The work you will do will feel frictionless, it will feel amazing on the surface, but once you go a bit deeper, itâll feel extremely shallow. It wonât reflect the struggles you went through, your decisions, and ideas.
It will no longer remind you of you and the work you aspire to.
You will turn into just another extremely efficient producer of things, but not a creator like you were before.
Invite friction to your work.
i love writing. i never let agents write for me. whether it's docs, or tweets, or shitposts, or even prompts (okay maybe that one's harder as agents manage other agents)
there's a simple reason for that: i still strongly believe that writing is thinking. it's a skill i hope to never give up. it's also important to me that whatever i say is always authentic, mistakes and all. my favorite posts are the ones that i just full send without any editing
i suspect it also helps with prompting. being able to clearly express what i want, and knowing the vocabulary i need to be able to direct my agents does seem to make for more effective usage of agents. in the same way that engineers have an advantage when we prompt agents to write code, because we are intimately familiar with the words that make up the discipline
knowing the right word incantations to get an agent to produce a desired goal almost feels like spellcasting. as models get more capable, and that input box looks more and more like a magic box that can output anything, words become the interface between you and the genie
there may come a time when we give up the keyboard in exchange for brain-computer interfaces. but until then, i'm writing every word.
ããããðŠ retweeted
But how do we keep encouraging and incentivising third-party developers who want to make a useful and thoughtful change to an open source repo?
They might have used an AI agent, been assisted by AI, or handcoded the code update. This doesn't matter for this particular point. External developers and users still have something of value to provide, surely? Beyond the Issues tab, beyond DMs, beyond making suggestions on a roadmap.
To guarantee the long-term future of open source, we need to make this work. And for cybersecurity. To keep open source libraries secure â with rapid and thorough patching of vulnerabilities â we need third-party contributions. For as long as we have hallucinations and errors, AI agents won't find and fix everything, just like humans.
Third-party developers have expertise and real value beyond the subjective taste, quality standards and gatekeeping of core maintainers.
There is a real danger that open source and FOSS become merely source available.
ããããðŠ retweeted
I see this less as GitHub failing and more as open source evolving.
The current workflow is increasingly absurd: someone uses AI to generate a PR, I use a better AI to review it, then their AI and my AI go back and forth until we converge. Add AI-generated spam on top, and the human is mostly just acting as a router between agents.
Iâd rather skip that entire loop.
Imagine you use a project and want a feature. You go to the repo and describe what you want. The projectâs AI already knows its conventions, preferences, history, rejected ideas, and boundaries. It can immediately tell you whether the idea is likely to fit and what shape it should take.
If it makes sense, you press a button and the projectâs chosen AI implements it, validates it, and presents the maintainer with the request and the code as one thing.
No separate issue. No PR ping-pong. No two AIs talking through two humans.
What AI still canot replace is taste: deciding what a project should be, what belongs in it, and where its boundaries are.
markdownã®TUIãã¥ãŒã¯ãŒãäœã£ã
$ mdcat README.md docs/*.md
$ mdgit show d34db33f
$ mdgit diff branch/update-sugoi-skill..main
ããããcatãšgitã³ãã³ãã®ãµãã»ããã«ãªã£ãŠããŠãç¹ã«ä»æ§é§åéçºãšãã§mdã®å·®åãè¯ãæãã«æç»ããç®çã§äœ¿ã£ãŠãŸãã
github.com/shqld/mdcat
1
328
ããããðŠ retweeted
ææãäœæ¥ã¯æŠå¿µãå€ãã£ããšShopifyã®Tobi LÃŒtkeãèªãã
æã¯ã¢ãŠãããããå
šç¶åºããªã人ã ã£ãã®ããAIæä»£ã§ã¯ã¢ãŠãããããåºããããŠåšãã®äººã«ç¢ºèªäœæ¥ãå¢ããã®ãææãäœæ¥ã§ãããšäž»åŒµã
ããããðŠ retweeted
New experiment: json-render + jev
The future Generative UI is instant
Your components, your actions, your design system
Rendered in milliseconds
ããããðŠ retweeted
I recently helped someone with old React 16 codebase. I forgot how clean and simple React was back then when it took over web frontend.
Hooks were a huge mistake, even bigger than trying to get React to the servers. Insane complexity just to not use classes.
ãããã
人éçšã®é²èŠ§ã»æäœUIãšããŠã¯äžçªæé©ãªéžæè¢ã ãšæãã
ãã é¡ããã¯NotionããŒã¿ããŒã¹ãããæ±çšçã§ãã€LinearãããUIã®åºæ¥ã®è¯ããµãŒãã¹ãã»ããæ°æã¡ã
LinearãŸãã§äŸ¿å©
ã¡ãã£ãšå€åçã ãã©ãGoogle workspaceã®ãããªGUIæäœãå«ããGitã§ç®¡çã§ããªã瀟å
ã·ã¹ãã æ§ç¯ã«ã䜿ãã
äŸãã°ããŠãŒã¶ãŒãã¹ãã¬ããã·ãŒããæäœããŠâŠãã®ãããªèŠä»¶ãCodexã§ç®¡çãããšãã³ãŒãããŒã¹ããªãã®ã§Gitãšããã¹ãããŒã¹ã§ç¡çãã管çããããšã«ãªã£ãŠããŸã
ããã§Linearã®ããã«ç¶æ
管çã§ããPMããŒã«ãå
¥ããŠããããšã§ãGitãšã¯ç°ãªãã¯ãŒã¯ãããŒæŠå¿µãLLMã«çè§£ãããã圢åŒã§éçºã»ç®¡çã§ãã
ã³ãŒãããŒã¹ä»¥å€ã®ãGUIæäœãªã©ã®å¶çŽãå€ãã·ã¹ãã éçºç®¡çã«Linearãå°å
¥ãããšäŸ¿å©
1
497
TSã®BrandedåãnewtypeãšåŒã¹ãã®ãèããŠã¿ãããTSã¯éšååãããã®ã§äŸãã°UserId <: stringã®ãšãã«UserIdãnewtypeãšåŒãã§ãããã ã£ãïŒãšãªã£ãð€
> 代æ°çããŒã¿åã®ããèšèªã§ã¯äŸ¡å€ãç®æžãããŠããŸããValue Objectã®èŠåŸã¯newtypeãšç¶²çŸ
çmatchã§ä»£æ¿å¯èœ
DDDãã¯ãªãŒã³ã¢ãŒããã¯ãã£ã«ã€ããŠFableãå®éã®ãšããã©ãæã£ãŠãããïŒ
--
çµè«ããèšããšãã©ã¡ãããæ¬ç©ã®æŽå¯ããšãååŒåããéšåãã®æ±ãåããã§ã䟡å€ã®ååžã極端ã«åã£ãŠããŸããåããŠè©äŸ¡ããŸãã
DDDã§ä»ã第äžçŽã®äŸ¡å€ãããã®ã¯æŠç¥çèšèšã®åŽã§ããBounded ContextããŠããã¿ã¹èšèªãã³ã³ããã¹ãããããcore/supporting/genericã®ãµããã¡ã€ã³åé¡ããå€§èŠæš¡ãã¡ã€ã³ã®çµ±äžã¢ãã«ã¯å¹»æ³ã§ãã¢ãã«ã¯èšèªãšããŒã ã®å¢çã«æ²¿ã£ãŠå²ãã¹ãããšããæŽå¯ã¯20幎çµã£ãŠãæ©èããŠãããããã€ã¯ããµãŒãã¹ã®å¢çèšèšãããŒã ããããžãŒã®çè«çåºç€ã¯å®è³ªçã«ããããæ¥ãŠããŸããç¹ã«ãµããã¡ã€ã³åé¡ã¯ãèšèšæè³ãã©ãã«éäžãããããæ±ºããéå
·ãšããŠæãã¬ãã¬ããžãé«ãã®ã«ãæã䜿ãããŠããªãã
äžæ¹ãæŠè¡çãã¿ãŒã³(Entity / Value Object / Repository / Factory)ã®å€§åã¯2003å¹Žåœæã®Java/OOPã®å¶çŽã®ç£ç©ã§ã代æ°çããŒã¿åã®ããèšèªã§ã¯äŸ¡å€ãç®æžãããŠããŸããValue Objectã®èŠåŸã¯newtypeãšç¶²çŸ
çmatchã§ä»£æ¿å¯èœã§ããããã³ã³ãã€ã©ã匷å¶ããã"Make illegal states unrepresentable"ã®æ¹ããVOã®ã»ã¬ã¢ããŒããå°ãªãã³ãŒãã§åãç®çãéæããŸããWlaschinã瀺ããéããDDDã®æ¬è³ªã¯ã¯ã©ã¹éå±€ããåã§è¡šçŸããæ¹ãå¿ å®ã§ããEvansèªèº«ããã¿ããªæŠè¡ãã¿ãŒã³ã°ããèŠãããšç¹°ãè¿ããŒãããŠããã®ã¯ç€ºåçã§ãRepositoryã®äžã«ORMãå
ã¿ãè²§è¡ã¢ãã«ã«ãããã³ã°å±€ãéããã ãã®ããããDDD-liteã¯ãDDDã®å€±æãšããããDDDã®äžåšã§ãã
äŸå€ã¯Aggregateã§ãããã¯åã·ã¹ãã ã§ä»£æ¿ã§ããªãå¯äžã®æŠè¡æŠå¿µã ãšèããŠããŸããæ¬è³ªã¯ãã©ã®äžå€æ¡ä»¶ã«åŒ·æŽåãå¿
èŠã§ãã©ããçµææŽåã«èœãšãããããšãããã©ã³ã¶ã¯ã·ã§ã³å¢çã®èšèšå€æã§ãããããã¯ä»ã§ããã¡ã€ã³èšèšã®æ žå¿ã§ããåæã«æã誀çšãããããæŠå¿µã§ãããã倧ããããã°ããã¯ç«¶åãå°ããããã°äžå€æ¡ä»¶ãæŒããã
Clean Architectureã¯ãççŽã«èšãã°Hexagonal(Cockburn, 2005)ãšOnion(Palermo)ã®çµ±åãšãªãã©ã³ãã§ãäžèº«ãããã©ã³ãã£ã³ã°ã®åå©ã§ããæ žã®äž»åŒµââäŸåã¯å
åãããã¡ã€ã³ã¯ã€ã³ãã©ãç¥ããªãââã¯äŸåæ§é転ã®ã¢ãŒããã¯ãã£èŠæš¡ãžã®é©çšã§ãããèªäœã¯å¥å
šããã ãæ¬ã®å
容ã¯åœ±é¿åã«æ¯ããŠèããæ žå¿ã¯2012幎ã®ããã°èšäºäžæ¬ã«åãŸããŸããå®å®³ã¯åå¿åå³ãã4å±€ãã£ã¬ã¯ããª+å
šå¢çã«interfaceããšããæ§åŒãšããŠæ©æ¢°çã«è€è£œãããããšãå®è£
ãæ°žé ã«1ã€ãããªãtraitãDTOãããã³ã°ã®å±±ã1ãã£ãŒã«ããHTTPããDBãŸã§è¿œãã®ã«5ãã¡ã€ã«ãããã¯ææ©çæœè±¡åã§ãè¡äœ¿ããªããªãã·ã§ã³ã«ãã¬ãã¢ã ãæãç¶ããè¡çºã§ãã
äžã§ããDBã¯è©³çްãã¯åæžã§æãçããã䞻匵ã§ããå€ãã®ã·ã¹ãã ã§ã¯ããŒã¿ã¢ãã«ããéå¿ã§ãPostgresãå·®ãæ¿ããæ¥ã¯æ¥ãªãããããRepositoryã®è£ã«DBãé ããšããã©ã³ã¶ã¯ã·ã§ã³èšèšãã¯ãšãªæé©åãšãã£ãDBã®åŒ·ã¿ãæšãŠãã¡ã«ãªããsqlxã®ã³ã³ãã€ã«ææ€èšŒã¯ãšãªã®ãããªéå
·ã®äŸ¡å€ãtraitå¢çã®è£ã§æ»ã¬ã®ã¯å
žåäŸã§ããå®ã䟡å€ãããã®ã¯ãäŸåã®åãããšããã¡ã€ã³ã³ã¢ã®éé¢ãã ãã§ããªã³ã°ã®æ°ãçšèªã®æ£çµ±æ§ã¯ã©ãã§ãããããããŠRustãªããã®äŸåèŠåŸã¯crateåå²ã§éçã«åŒ·å¶ã§ããéåãã¬ãã¥ãŒã³ã¡ã³ãã§ã¯ãªãã³ã³ãã€ã«ãšã©ãŒã«ãªãã人éã®èªå¶å¿ã«ã¬ã€ã€ãŒèŠåŸãé Œãåå
žã®å§¿ããããã¡ãã®æ¹ããã»ã©çãããã
ãšããã³ã¹ã«ã€ããŠãæ£çŽã«èšããšãã©ã¡ãã广ã瀺ãå®èšŒç ç©¶ã¯ã»ãŒååšããŸããããœãããŠã§ã¢æ¹æ³è«å
šè¬ãããã§ããããããã¯çµéšè±å¯ãªå®åå®¶ã®ãã£ãšããããéžè©±ã§ãã£ãŠç§åŠã§ã¯ãªããã ããä¿¡å¥ãã¢ã€ãã³ãã£ãã£ã®å¯Ÿè±¡ã«ãã¹ãã§ã¯ãªããçµæžæ§ã®åé¡ãšããŠæ±ãã¹ãã§ãã鿥局ã»ååŒã»åŠç¿ã³ã¹ããšãããã¬ãã¢ã ãæã£ãŠãç¹å®ã®å€æŽãå®ããªãæš©å©ããè²·ãååŒã§ãããä»éçã«ãå
±æèªåœãšäºæž¬å¯èœãªæ§é ããªã³ããŒãã£ã³ã°ã³ã¹ããäžãããšãã調æŽäŸ¡å€ããããäžå€æ¡ä»¶ãè€éã§å¯¿åœã®é·ããã¡ã€ã³ââéèãäŒèšãèŠå¶å¯Ÿå¿ââã§ã¯ãªãã·ã§ã³ãã»ãŒç¢ºå®ã«è¡äœ¿ãããã®ã§è²·ã䟡å€ãããããžã§ããªãã¯ãªCRUDãµããã¡ã€ã³ã§è²·ãã®ã¯ãã ã®æã§ãã
ãŸãšãããšãæŠç¥çDDDã¯æ¬ç©ãæŠè¡çDDDã¯Aggregateãé€ãåã·ã¹ãã ã§å€§å代æ¿å¯èœãClean Architectureã¯æ£ããåå1ã€+éå°ãªåŠæ¹ç®ãå®åã®æé©è§£ã¯ãæŠç¥çDDD+åé§åã¢ããªã³ã°+äŸåèŠåŸã®crateæ§é ã«ããéç匷å¶ããããã«åæããããšããã®ãç§ã®è©äŸ¡ã§ãã
305
ããåããããããçµå±C++ã®APIã®ãã€ã³ãã£ã³ã°ãå¿
èŠã«ãªã£ãŠæžãå§ãããã©äºææ§ã®ä¿èšŒããªãã®ã«ãªããããªå€§å€ãªããšãããªããšãããªããã ïŒãšããæ°æã¡ã«ãªãïŒV8ããè§Šã£ãŠãªããã©ïŒ
160
æè¿ãã£ãšRustã§JSã©ã³ã¿ã€ã ãäœã£ãŠãããã§ãããããã§å°çãèŠãŠãŸãããããžã
Bun 㯠JS ãšã³ãžã³ã§ã¯ãªã JavaScriptCore ãèŒããã©ã³ã¿ã€ã ã§ãJS ãªããžã§ã¯ããšãã€ãã£ãè³æºã®å¯¿åœã¯å¥ç©ãªãã§ããããBun ã®(ãšã³ãžã³ã§ã¯ãªã)åŠçç³»ã®å®è£
ã Rust ã«ãªã£ãã ããªã®ã§ã確ãã« Rust åŽã® Drop ãæææš©ã§ããã€ãã£ãå±€ã ãã®è§£æŸå¿ããã¯æžããã§ãããJS ã®ãªããžã§ã¯ãããã€ãã£ãã®æ¥ç¶ããããã¡ãã¿ã€ããŒãæããŠããšãJSC ã® GC ãååããªãéã Rust åŽãèœãšããªããã§ãããã
ãããå®è·µãããâŠâŠïŒ
ã¯ãŠãªããã°ã«æçš¿ããŸãã
ç§ãæèŠªäŒã§ãŒã£ã¡ã«ãªã£ããããããš - è
¹ã¯æžã blux.hatenablog.com/entry/20âŠ
#ã¯ãŠãªããã°
253
ããããðŠ retweeted
æ¶è²»è
åºãå
¬éããŠããæ¶è²»è
éšãããŒã¯ãã¿ãŒã³äŸãã®15åãå
šãŠç¶²çŸ
ãããã¡ã€ã³ååŸãµã€ãïŒãã¢ïŒãäœã£ãŠã¿ãïŒïŒ
project.activetk.jp/dark-domâŠ
ãã®ãµã€ãã«æ¶è²»è
éšãããŒã¯ãã¿ãŒã³äŸ15ã€åãããããèŒã£ãŠãã4ã7ã9ã15ã¯ãŸãã§ã¿ãæªãã§ã
caa.go.jp/policies/future/icâŠ


























