Reo Ogusu

Saying not knowing how to code gives you an advantage in building software (thanks to AI) is like saying not knowing anything about filmmaking gives you an advantage in making films (thanks to having a smartphone + apps to edit stuff) Ignore this stuff and keep learning+building

Not knowing how to code giving you an advantage is absolute nonsense. The more you understand, the better your prompts, the better the feedback you give, the better product you ship. What will change is that the intricacies of syntax, compilers, module systems, the finer details of type systems, won’t matter as much to everyone. But you should absolutely understand how the pieces fit together. From syscall to pixels. Learn how data flows, because you’ll be able to secure your systems. Learn about performance, because you’ll be able to push your agent further. Learn about APIs, because they determine how to integrate systems. Learn about how systems fail, because you’ll be able to make reliable programs.

世界はそれをREADME.​md と呼ぶんだぜ

how did we ever write all that code by hand

Unpopular opinion: Current code review tools just don’t make much sense for AI-generated code When reviewing code I really want to know: - The prompt made by the dev - What corrections the other dev made to the code - Clear marking of code AI-generated not changed by a human

A few things I've noticed as all devs write code with AI. When you write foundational / architectural code of a new project by hand, you "feel" the code pushing back if your abstraction isn't right. You feel when something is harder than it should be. The code is telling you it's not in the right shape. Good engineers are sensitive to this. When you're using an LLM, you keep pushing right through this in a way that feels like you're making progress, and it may even be directionally correct in a sense, but the underlying foundation of it all is actually bad in a way that either kills progress of the LLM later as it buckles under the complexity it has created or destroys your ability to maintain the code long term. Related to this, I see a general restlessness with just sitting and thinking about a problem for a while. As I've been working on a new library here at Laravel, there have been days where it feels like I mainly just stare at my screen thinking about something. When Claude Code is at your fingertips, it's tempting to just start yapping into the terminal and watching code come out the other end. Again, directionally correct in some ways, but often doesn't land on the elegant solution that is waiting to be discovered.

@takosu802774521 wow already looking great...

I've been working on the UI design for my new work-in-progress app today... But, oh man, designing by hand is tough. (Yes, I'm doing it by hand to learn designing so I don't have to rely 100% on AI.)

🔥🔥🔥🔥🔥

生成AIとパチンコは本質的に似ている

これ、いまだに誤解が多いので。 AIが進歩すれば、コードを「書ける」スキルは必要なくなっていきますが、そのかわり「読める」スキルの重要性は増します。 なぜか。 「理解を移譲することはできない」からです。 これを言ったのは、椅子などのデザインで有名なイームズです。 justinprather.com/eames-never-de… 問題は、それを解こうとして取り組んだときにはじめて本質が見えてくる。だから、手を動かす部分は部下やAIに任せてもいいけれど、問題の本質についての理解を深めるためには、そのプロセスをしっかりとグリップしてなければいけない。 理解できていなければ、AIに的確な指示を出すこともできない。成果物の説明責任を果たすこともできない。それだけが唯一、人類に残された仕事になろうという時に。 AIは全力で使い倒し、そのプロセスを通じて学び、成長し、テストし、理解を深めることが大切です。 理解が深まる喜びにつながらないAIの使い方は、スロットマシーンを脳死状態で回し続けているのと同じだからです。

Do you like aviation and games? We have the perfect match for you - Skycards a game from Flightradar24. Download now from skycards.app and join thousands of players already playing the game.

Quitting programming as a career right now because of LLMs would be like quitting carpentry as a career thanks to the invention of the table saw.

@lgrammel @jueungraceyun Got it. thanks!

@ogureo @jueungraceyun june - with an alpha this week or next

AI SDK 5 preview: ChatStore & ChatTransport ChatStore synchronizes chat write operations and manages streaming state. You can use it directly or through framework integrations like useChat. ChatTransport makes backend integrations more flexible, allowing for client-only usage.

. @hwchase17 I've resisted dumping on @langchain publically until now (despite how easy it would be) but if you're going to start publishing BS like this, I'll stop being so restrained: * LangSmith caused a well known AI company to pivot away from Python because its tracing mess hung for 500ms on every function call. * LangChain is blocked in at least one major public tech company for security reasons. It's pretty brave of you to start referring to other people's libraries as "not really production ready". Pick a fight with @OpenAI if you like, but leave @pydantic out of it.

見たままから再構築された現実へ koriym.github.io/blog/2025/03/3…

Mastra @mastra 日本で盛り上がっているみたいだけど、触ってみた感じやっぱり無駄な抽象化に感じる。LangChainと同じ。似たようなことしたいなら@triggerdotdev とかでBackground Jobでロジック作れば十分だと思う。

Good post! It will take some time to settle on definitions. Personally I use "vibe coding" when I feel like this dog. My iOS app last night being a good example. But I find that in practice I rarely go full out vibe coding, and more often I still look at the code, I add complexity slowly and I try to learn over time how the pieces work, to ask clarifying questions etc.

Number of Super Bowl wins, by country: 🇺🇸 USA: 59 🇨🇦 Canada: 0 🇦🇺 Australia: 0 🇨🇳 China: 0 🇮🇳 India: 0 🇯🇵 Japan: 0 🇬🇧 UK: 0 🇷🇺 Russia: 0 🇩🇪 Germany: 0 🇪🇸 Spain: 0 🇮🇹 Italy: 0