k-goto

子持ちのSE。22歳ででき婚。 インフラ、プログラム(ruby, C++, golang，java，javascript, vuejs, aws)についてぼそぼそ呟きます。

[キタデ @kobenisikakatan]

ハーネスやらループやらのコード生成の方法論の前にこういう事業価値目線で語れるようになりたい
事業価値を生まないコードなら書かないほうがマシ
https://t.co/kCh2ZGZlQX

[naoya @naoya_ito]

最近コンサルとかそっち側でキャリアを積んできた人と話したんだけど、彼らと、我々ソフトウェアエンジニアって職業人としてのアイデンティティを何に立脚させるかって感覚がかなり違う。そして、我々は技術力やスキル、何ができるかみたいなことに重きを置きすぎているなと思った

[カック @kakakakakku]

「データガバナンス設計ガイドライン」と「データマネジメント設計ガイドライン」をセットで読むのが良いっていうのはなるほど💡

データマネジメント設計ガイドライン | フューチャー株式会社
https://t.co/VYqhRq2NaX

[カック @kakakakakku]

いろいろまとまっててイイ

・憲法の制定
・組織体制
・データマスキングポリシー
・技術トレンドとの付き合い方
etc

データガバナンス設計ガイドライン | フューチャー株式会社
https://t.co/tal8cJsjEf

[Takuto Wada @t_wada]

モデルの判断力向上により、Claude Codeのシステムプロンプトを性能を落とさず8割削減できた。判断はモデルに委ね、CLAUDE.md は軽量に保ち、詳細はSkill化して必要な時に必要なコンテクストを渡す

The new rules of context engineering for Claude 5 generation models
https://t.co/4LfmS0tGAN

[iwashi / Yoshimasa Iwase @iwashi86]

あとで読む

https://t.co/Md2BOZEqKx

[kmuto |『先輩データサイエンティストからの指南書』 @eycjur]

AWSで破産したかもしれなくて、手が震えている（表示はガチでこの数字）
126.6億ドル≒約2.06兆円

[Takuto Wada @t_wada]

仕様駆動開発は自然言語駆動開発ではないという話、わかる

[Boris Cherny @bcherny]

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things.

I think many of these automations have become even more important now. This is true for a number of reasons.

First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time.

Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time!

Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation.

Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

[Anthropic @AnthropicAI]

The US government, citing national security authorities, has issued an export control directive to suspend all access to Fable 5 and Mythos 5 by any foreign national, whether inside or outside the United States, including foreign national Anthropic employees.

The net effect of this order is that we must abruptly disable Fable 5 and Mythos 5 for all our customers to ensure compliance.

Access to all other Claude models is not affected.

We apologize for this disruption to our customers. We believe this is a misunderstanding and are working to restore access as soon as possible.

Read our full statement: https://t.co/bwn0sximKZ

[k-goto @kzdev003]

2026年のエンジニア運勢は

『中吉』

#Findyエンジニアおみくじ2026
#新年一発目

あなたも2026年を占ってみよう👇
https://t.co/d1NWfAncuF

[k-goto @kzdev003]

ドメインモデルパターンのクラス設計に取り組む現場の苦労ばなしに参加を申し込みました！ https://t.co/MoyG39j8Nj #ドメインモデルパターンに挑戦する苦労ばなし

[k-goto @kzdev003]

Go Conference 2021 Spring (Online) に参加を申し込みました！ https://t.co/O7DSBrDjLY #gocon

[k-goto @kzdev003]

FinTech Talk vol.4 メルペイCTO・COOの二人が今気になる ○○ に参加を申し込みました！ https://t.co/khdXGURGtd #merpay_fintech

[k-goto @kzdev003]

『ドメイン駆動設計入門』パネルディスカッション with レビュアーズ に参加を申し込みました！ https://t.co/xw5TZfIrSL #narusemi

[k-goto @kzdev003]

Sandbox Live #4 テーマ:ソフトウェア設計とアジャイル に参加を申し込みました！ https://t.co/Fr0XlbZRxr #匠真堂

[k-goto @kzdev003]

kotlinでspring使うとvalidationの書き方がいまいちだなあ。javaに戻すべきか

[k-goto @kzdev003]

@cissan_9984

[前澤友作 @yousuck2020]

🎍謹賀新年🎍

【総額10億円】#前澤お年玉 100万円を1000人にプレゼントします！

100万円で皆さまの人生がよりハッピーになりますように。

応募方法は僕のフォローとこのツイートのリツイート。締切は1月7日23:59まで。

企画趣旨や当選条件などはYouTubeで説明してます。
https://t.co/kBgwwmJoaP

[めいさん。フォロバ１０割 @meimeimeeei10]

結婚を前提とした彼女を家に連れてきて両親に挨拶したあと、一家のお墓で今はなき祖父母に二人で報告のお墓参りをして、そのとき彼女に向かって「一緒のお墓に入ろうな」というプロポーズのつもりで「ここがお前の墓場だ」と言い放った故郷の知人が来年結婚するそうです。