by Design and Engineering team at PIXTA
texta.fmは、ピクスタで働くデザイナー・エンジニアによる技術ブログ「てくすた」のポッドキャスト版です。 本ポッドキャストに関するご意見・ご感想は、ハッシュタグ #textafm にお寄せください。
Language
🇯🇵
Publishing Since
8/27/2020
Email Addresses
1 available
Phone Numbers
0 available
March 13, 2023
<p>技術顧問の和田卓人さんと、技術調査レポートを利用した情報収集の仕方について話しました。</p> <p>Show Notes:</p> <ul> <li><a href="https://texta.pixta.jp/">ピクスタ技術ブログ「てくすた」</a></li> <li><a href="https://gihyo.jp/book/2020/978-4-297-11462-6">パーフェクトRuby on Rails【増補改訂版】</a></li> <li><a href="https://anchor.fm/textafm/episodes/10--Server-side-JavaScript-e1lmvb7">10. Server-side JavaScript</a> (2022年7月配信)</li> <li><a href="https://web-salad.hateblo.jp/entry/2022/09/30/130000">経営とソフトウェアエンジニアリングの接続</a></li> <li><a href="https://www.thoughtworks.com/radar">Technology Radar</a> (Thoughtworks)</li> <li><a href="https://stateofcss.com/en-us/">State of CSS</a></li> <li><a href="https://stateofjs.com/en-us/">State of JavaScript</a></li> <li><a href="https://www.puppet.com/resources/state-of-devops-report">State of DevOps Report</a> (Puppet)</li> <li><a href="https://www.devops-research.com/research.html">State of DevOps Report</a> (Google Cloud/DORA)</li> <li><a href="https://www.puppet.com/resources/history-of-devops-reports">A Brief History of the State of DevOps Reports</a></li> <li><a href="https://engineering.visional.inc/blog/463/four-keys-consideration-part1/">ソフトウェアデリバリーパフォーマンスに関する考察（前編） - State of DevOps 2022では何が示されたのか</a></li> <li><a href="https://engineering.visional.inc/blog/469/four-keys-consideration-part2/">ソフトウェアデリバリーパフォーマンスに関する考察（後編）- Four Keysと向き合うとはどういうことか</a></li> <li><a href="https://insights.stackoverflow.com/survey">Stack Overflow Annual Developer Survey</a></li> <li><a href="https://www.jetbrains.com/lp/devecosystem-2022/">The State of Developer Ecosystem 2022</a> (JetBrains)</li> <li><a href="https://stackshare.io/posts/top-developer-tools-2022">The Top 100+ Developer Tools 2022</a> (<a href="https://stackshare.io/">stackshare</a>)</li> <li><a href="https://www.datadoghq.com/state-of-serverless/">The State of Serverless</a> (Datadog)</li> </ul>
July 27, 2022
<p>技術顧問の和田卓人さんと、ECMAScriptの検討中の仕様、サーバーサイドJavaScriptにおける技術選定について話しました。</p> <p>Show Notes:</p> <ul> <li><a href="https://texta.pixta.jp/">ピクスタ技術ブログ「てくすた」</a></li> <li><a href="https://gihyo.jp/book/2020/978-4-297-11462-6">パーフェクトRuby on Rails【増補改訂版】</a></li> <li><a href="https://anchor.fm/textafm/episodes/8--Class-based-Programming-e1c914c">8. Class-based Programming</a></li> <li><a href="https://github.com/tc39/proposal-call-this">tc39/proposal-call-this</a> (Stage 1)</li> <li><a href="https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/call">Function.prototype.call()</a></li> <li><a href="https://github.com/tc39/proposal-bind-operator">tc39/proposal-bind-operator</a> (Stage 0)</li> <li><a href="https://jsprimer.net/">JavaScript Primer</a></li> <li><a href="https://en.wikipedia.org/wiki/ECMAScript">ECMAScript</a></li> <li><a href="https://jschoi.org/22/es-dataflow/">Holistic JavaScript dataflow proposals v2</a></li> <li><a href="https://zenn.dev/yuku/articles/b169ac62ac3271">JavaScriptを大きく変えうる Dataflow Proposals の概要と論点(Call-this, Pipe Operator)</a></li> <li><a href="https://github.com/tc39/proposal-pipeline-operator">tc39/proposal-pipeline-operator</a> (Stage 2)</li> <li><a href="https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/functions/#pipelines">F#のPipe operator</a></li> <li><a href="https://docs.hhvm.com/hack/expressions-and-operators/pipe">HackのPipe operator</a></li> <li><a href="https://www.martinfowler.com/bliki/UniformAccessPrinciple.html">UniformAccessPrinciple</a></li> <li><a href="https://en.wikipedia.org/wiki/Bertrand_Meyer">Bertrand Meyer</a> （プログラミング言語<a href="https://www.eiffel.org/">Eiffel</a>の作者、「<a href="https://www.seshop.com/product/detail/7595">オブジェクト指向入門 第2版 原則・コンセプト</a>」の著者）</li> <li><a href="https://github.com/tc39/proposal-extensions">tc39/proposal-extensions</a> (Stage 1)</li> <li><a href="https://anchor.fm/textafm/episodes/Sideshow-4--Worse-is-Better-eqsi31">Sideshow 4. Worse is Better</a></li> <li><a href="https://speakerdeck.com/yasaichi/architecture-decision-for-the-next-10-years-at-pixta">Active Recordから考える次の10年を見据えた技術選定</a></li> <li><a href="https://typeorm.io/">TypeORM</a></li> <li><a href="https://www.prisma.io/">Prisma</a></li> <li><a href="https://martinfowler.com/eaaCatalog/tableDataGateway.html">Table Data Gateway</a></li> <li><a href="https://www.martinfowler.com/eaaCatalog/transactionScript.html">Transaction Script</a></li> <li><a href="https://speakerdeck.com/qsona/architecture-decision-for-the-next-n-years-at-studysapuri">GraphQL と Prisma から考える次のN年を見据えた技術選定</a></li> <li><a href="https://github.com/tc39/proposal-decorators">tc39/proposal-decorators</a> (Stage 3)</li> <li><a href="https://github.com/tc39-transfer/proposal-function-pipe-flow">tc39-transfer/proposal-function-pipe-flow</a> (Stage 0)</li> </ul>
April 18, 2022
<p>技術顧問の和田卓人さんに、普段どのようにTDDを実践しているのかを伺いました。</p> <p>Show Notes:</p> <ul> <li><a href="https://ja.wikipedia.org/wiki/%E5%AE%88%E7%A0%B4%E9%9B%A2">守破離</a></li> <li>CheckingとTesting（cf. <a href="https://www.developsense.com/blog/2009/08/testing-vs-checking/">Michael Boltonによるブログエントリ</a>）</li> <li>付録C ＝ <a href="https://www.ohmsha.co.jp/book/9784274217883/">テスト駆動開発（Kent Beck 著、和田 卓人 訳）</a>収録の訳者解説</li> <li>今回のSoftware Design ＝ <a href="https://gihyo.jp/magazine/SD/archive/2022/202203">Software Design 2022年3月号</a></li> <li><a href="https://en.wikipedia.org/wiki/Unix_philosophy">UNIX哲学</a></li> <li><a href="https://en.wikipedia.org/wiki/Read%E2%80%93eval%E2%80%93print_loop">REPL</a></li> <li>さっき未知と既知の話をした ＝ <a href="https://anchor.fm/textafm/episodes/9--The-20th-Anniversary-of-TDD-e1fbh4j">9. The 20th Anniversary of TDD</a></li> <li><a href="https://en.wikipedia.org/wiki/JUnit">JUnit</a></li> <li>Learning Test（cf. <a href="https://www.ohmsha.co.jp/book/9784274217883/">テスト駆動開発</a>の14章、26章）</li> <li>内部品質（cf. <a href="https://speakerdeck.com/twada/quality-and-speed-2020-autumn-edition?slide=64">質とスピード</a>）</li> <li>プログラマーは怠惰で傲慢で短気 ＝ <a href="https://en.wikipedia.org/wiki/Larry_Wall">Larry Wall氏</a>が提唱した<a href="https://wiki.c2.com/?LazinessImpatienceHubris">プログラマーの三大美徳</a></li> <li>オレってばスゲー（<a href="https://web.archive.org/web/20051224072314/http://www.ascii.co.jp/books/detail/4-7561/4-7561-4441-1.html">Lightweight Language MAGAZINE</a>という書籍における軽量プログラミング言語の定義が元ネタ）</li> </ul>
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at [email protected] for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.
