2024-11-24
https://gyazo.com/255a7417f72986b08aa9d62e9b00e0e9https://gyazo.com/f6b530fb21fda05da26597cc16cf9dc7
https://gyazo.com/290d56f7d618d5eae8d03a38e0879521https://gyazo.com/fe39847fcf98e67dfd49c0895fb90249
https://gyazo.com/a2cfac62e6e8a9457a1ba308b968f033
尊すぎる…
https://gyazo.com/1164ee29515785fb3f6f3cf1816c3a3ehttps://gyazo.com/495622754cd97d3244e529b5e08e4659
https://gyazo.com/ef9dc08debc6bc96b205b76dd453a17f
この場合は<script>の内容が読まれていた
https://gyazo.com/eb083024bfb899dfc815e326e1cecb4c
@github: Generate a summary of a pull request in seconds with GitHub Copilot on https://t.co/VDZYKUklba. ⚡ Now available for all Individual and Business users. ⬇️ https://pbs.twimg.com/media/Gc8fTkiXkAAzcke.jpg
仕事では必要な項目を埋めてくれる形であれば楽なのかもしれない…?
@antfu7: Thank you GitHub, but that’s not how we build software. AI should help us focus more on reasoning, design, communication. Filter spam and unnecessary noise, not helping creating them.
@youyuxi: Agreed. The value of PR descriptions is often in things that are NOT directly inferable from the changes: - What original problem led to this PR?
- Are there related issues / prior discussions?
- What alternatives have been tried? Does this supersede previous attempts?
- Why are certain seemingly unreasonable choices made? What are the tradeoffs?
AI that generates summary based on the changes of an isolated PR is not really helpful in a meaningful way. Good PR descriptions need not only a holistic understanding of the entire codebase, but even the contribution history of the project. That’s of course harder to do, but I think it’s a possible direction to make it actually useful.
https://pbs.twimg.com/media/GdFBIV2aAAApZAY.jpg
なくない…?
修正されてた
https://www.youtube.com/watch?v=vypeheX6RJ8
https://www.youtube.com/watch?v=7zXF-qD1ybY
@evenstensberg: Very excited to announce that webpack is joining TC39 as experts. We were very lucky to have two webpack members participating in discussions around evolving the JavaScript language and its direction and development of JavaScript itself. Because webpack is a tool that affects a lot of the ecosystem, we need to align with the community, language and input people have, in order for Front End to evolve and improve.
Thanks to TC39 for inviting us! https://pbs.twimg.com/media/GdFsu1sXoAADf2x.jpg
Microsoftの後方互換性、W3Cの仕様、なんでも良いけどITの要素技術って至る所に社会的配慮がある。夜中メンテとかもまさに。これだけITが生活に浸透してる今、ITは社会的配慮辞めていいって暴論というか主語デカすぎて草
いやこれはなぁ…
これなー、会社ですらそうなるんだよね……
https://pbs.twimg.com/media/Gc9wUrcaAAA65LW.png
https://gyazo.com/e0b7e97fc730d1b7470fd65f4c626c03