たにぐち まこと／ちゃんとWeb withAI
55.2K posts
@seltzer
AI駆動開発でWebシステムを開発したり、AIに関する情報提供してます。開発のお手伝い、動画のお手伝いなど仕事の依頼はDMください！ YouTube ≫ https://t.co/BVHbJTYPV6
@seltzer This is exactly the workflow FSB is aimed at: give an agent a real Chrome session, let it inspect pages, act, capture screenshots, and verify results. Handy when MCP browser demos need to become repeatable work. github.com/LakshmanTurlap…
中小企業の6割が「AI導入予定なし」 民間調査 nikkei.com/article/DGXZQO…
【朗報】Grok Build、SuperGrok全ユーザーに解放 月$300のHeavy限定CLIが$30/月から使えるように。これは熱い。 ・Plan Mode：実行前に計画を承認 ・並列サブエージェント搭載 ・Imagineで画像・動画インライン生成 ・コマンド1行でインストール ↓詳細
スマートグラスで何を買えばいいか悩む人に最適な記事だった。この分岐表を見る限り、Even G2を買って間違いなかった...
You might believe you should spend less time thinking about code because of AI. I strongly disagree! We’re watching this play out live where tons of AI generated code becomes a liability. At the end of the day, an engineer needs to be responsible / on call for code that gets shipped to production. If you don’t understand the system you’re trying to debug, you’re probably going to have a bad time. Yes, AI can help with all of this, if you set up the proper systems. You can have agents triage prod logs, look at errors, etc. You can speed up parts of the investigation, but an engineer needs to make the call. There might be serious customer or financial implications from that change. I expect the trend continue for trimming dependencies, vendoring code so you can modify it directly, preferring simpler systems with fewer abstractions, and spending waaaay more time thinking about system design and code maintenance. I’ve said this before, but it’s a great time to get familiar with CS fundamentals and some of the history behind what great software looks like. Many parts will be different in the coming years as AI progresses, but also a lot more than people realize will stay the same.
