![When you open a document with an encoding different than the one it was created with, it's not possible to display the original text, and instead a garbled mess of corrupted characters are printed out. These are called "mojibake" in Japanese, and the word has also been borrowed into English.]()
A Field Guide to Japanese Mojibake
2021-11-01 14:00:38
![データベースのスペシャリストとして知られる曽根壮大（そね たけとも）さん。ベンチャー企業のCTO（最高技術責任者）やインターネット企業のCRE（Customer Reliability Engineering・顧客信頼性エンジニアリング）を務めるなど、エンジニア系のコミュニティーをけん引している。講演者としても一流で、イベントにも引っ張りだこ。その世界では「そーだいさん」として、多くの人に頼られる存在だ。しかし、そのスタートは警察官という全く別分野だった。新たな道へ進んだのは、プログラミングの知識もなかった23歳の頃のこと。何かを始める場合、人によっては「今更始めても遅いかも……」と躊躇（ちゅうちょ）するかもしれない。高度なスキルが求められるIT業界で、そーだいさんがいまの地位までたどり着いた理由はどこにあるのだろうか。そーだいさんならではの「学び」への姿勢、そして新しいことを始める時の考えについて伺った。]()
何かを学ぶことに「今更遅い」、なんてない。 - 曽根 壮大（そーだい） | LIFULL STORIES
2021-11-01 14:00:21
![]()
「物凄い罰金取れそう」交通量調査が“AI”に代替、交通システム最適化の未来とは - Monavis
2021-11-01 11:08:15
![日本語で「CSS設計」を検索すると、記事やつぶやきなどでセレクタの命名規則に関する話題が多いです。CSSを設計する上で、命名規則は重要な要素でしょう。簡単なセレクタ名だと他のスタイルと重複する可能性もあります。他のスタイルと重複しないようにセレクタの子孫数を増やしてしまうと、今度はスタイルの取り回しが悪くなります。またデザインをコンポーネントに分ける粒度について紹介されていますが、命名規則の分け方のように紹介されているよう感じます。論理的に構造をわけて命名していくため、覚えやすく、伝えやすさもあわさって、現在の「CSS設計 = 命名規則」のような構図ができあがったと感じています。]()
宣言ブロックのCSS設計 | Web Design KOJIKA17
2021-11-01 11:08:14
![]()
中国が考える、メタバースと国家戦略・安全保障の関係性に関してー中国現代国際関係研究院（CICIR）レポートの翻訳と解説 | やまとは国のまほろば
2021-11-01 11:00:34
![最小権限のIAM Policyを作成するのって地味に面倒ですよね。以前私は、Route53ホストゾーンにDNSレコード作成するのに必要な最小権限のPolicyを作るため、権限ゼロの状態から始めて、権限不足エラーが出るたび …]()
最小権限のIAM Policy作成にCloudFormationのコマンドが役立つ | DevelopersIO
2021-11-01 11:00:13
![私はPRD(Product Requirement Document)が嫌いでした。概念としてのPRDは好きですが、ドキュメントとしてのPRDが苦手、という話を聞いてください。]()
プロダクトマネージャーが書いたPRDの通りに機能をつくる？｜小城久美子 / ozyozyo
2021-11-01 11:00:12
![...]()
コーディング用のフォントから、自分に適した一番のフォントを見つけることができるオンラインツール -Coding Font | コリス
2021-11-01 11:00:07
![]()
もう自宅でも「パブリックネットワーク」が推奨です Windows 11のネットワーク設定画面を確認する【イニシャルB】 - INTERNET Watch
2021-11-01 11:00:03
![【READYFOR×コミューン】業務に活かせるReact LT & 座談会 https://readyfor.connpass.com/event/224586/]()
React Hook Form はどのように再レンダリングを最適化しているのか？ - Speaker Deck
2021-11-01 08:10:14
![正規表現と構文図について解説します。オートマトンについても詳しく述べます。オートマトン・スゴロクで遊びましょう！世間でよく知られている／使われている概念・方法にはこだわらず、僕（檜山）の感覚で一番わかりやすいと思われる筋書きと用語法／図式法を使って説明します。この記事に目を通して“感じ”が掴めたら、形式言語理論の教科書を読み始めることが出来るでしょう。[追記]この記事の内容に対する具体例は、「正規表現とオートマトン：なんだ簡単じゃん、JavaScriptによる実装」にあります。[/追記]内容： 正規表現 正規表現の例 構文図 基本記号 連接 選択 省略可能 繰り返し ストレートワイヤーによるレ…]()
この機会にマスターしようぜ、正規表現、構文図、オートマトン - 檜山正幸のキマイラ飼育記 (はてなBlog)
2021-11-01 08:10:11
![はじめに キッチハイクのエンジニアメンバーでReact Nativeの気になるニュースを持ち寄ってみました！ はじめに React Native Japanコミュニティの1ヶ月 React Native Matsuri 2021のまとめ記事 React Native 0.66 リリースアナウンス ハイライト Nightlyリリース Commitlyリリース Shopify の複数アプリ間でのコード再利用について Expo 43 beta 大きなプロジェクトでTypeScript化を進めるための8つのtips NativeBase のご紹介 rn-css のご紹介 さいごに We're Hiri…]()
RN Features 2021年10月号 - React Native Matsuri 2021、React Native 0.66 リリースアナウンス、大きなプロジェクトでTypeScript化を進めるための8つのtips -…
2021-11-01 08:09:50
![Android app development books]()
Android 12 Wallpaper Changes Recreate Your Activities
2021-11-01 08:09:25
![Since announcing the start of the new React documentation effort, we’ve been busy writing the content and building a custom website designed around the learning experience. We are now ready to share this early preview of what we’ve created so far to get your feedback. This early preview is deployed at beta.reactjs.org and is in active development. Please leave any feedback in #3308. TLDR Visit the early preview of the new React Docs at beta.reactjs.org to find: All new learning materials featuring Hooks Interactive examples and challenges “Code diagrams” that visually dissect how Hooks work Illustrations and diagrams that explain how React works New site designed around learning experience You may encounter some broken links—pardon our dust! Some content is yet to be released! What's in the beta The beta has two major sections: Learn React—a comprehensive, step-by-step guide to React. This section is roughly 70% complete. This content is stable and unlikely to change much beyond a few edits and fixes. Some content is still being written (notably, guides for effects, performance optimizations, and React DevTools). API Reference—detailed explanations of each API This section currently only has a few pages, so there is a lot left to write here! Have a look at the useState page to get a sense of what’s coming. The landing page is a temporary stub and will be replaced closer to the end of the project. Similarly, the Home tab is a bit empty now—we intend to port over more things from the existing site, like Blog, after most of the remaining work is done. Known issues No tutorials. We need to complete explanations for all core concepts and APIs before we can add tutorials. (This could be really cool to work on with the community at a later date! But not today!) Performance. When we say “beta,” we mean the site as well as the content! We still have some perf optimizations to make like code splitting at a later stage. Accessibility. While we have been mindful of accessibility during production, we’re waiting until the site is close to getting out of beta to run a comprehensive accessibility audit. What’s next We will make an official post on the blog and put up a banner on the existing site to let visitors know where to find the new docs sometime after gathering feedback from this soft launch. Once we achieve content parity with the old site, we’ll be ready to switch over to this one and keep the old one archived at a subdomain. We'll figure out which pages to redirect to which site at that stage—for now it's too early to discuss a plan. We intend to document all the stable React APIs before we switch over. That includes classes—however, they will be described on a separate page, while most of the docs will use Hooks. Please note that: We are not ready to kick off any official translation efforts at this time because the content is still in a state of flux. To keep the tone cohesive, we are writing the primary new content ourselves. While offers to write are much appreciated, we must regretfully decline for now! You can help! Read and share the docs with friends, colleagues, family! Report bugs! If you see one, please don’t hesitate to leave a comment here or send a fix to the beta folder in the main branch with the [Beta] tag in the title. Tell us what you think! Where to leave feedback? Leave your general feedback in a comment in #3308 or using this handy survey. Leave feedback as you read using the feedback button on the site High-level feedback is more useful than e.g. typos since we'll be doing more editing passes on all the content (bug fixes for typos much appreciated!). We'd particularly appreciate feedback on how to organize the content (see #3965 (comment)). Special thanks Getting to this stage required a lot of effort from different people, whom we would like to thank and acknowledge. This includes: Rachel Nabors: editing, writing, illustrating Dan Abramov: writing, curriculum design Sylwia Vargas: example code Dan Lebowitz: design Razvan Gradinar: design Maggie Appleton: diagram system (not integrated yet) Jared Palmer: site development ThisDotLabs (Dane Grant, Dustin Goodman): site development CodeSandbox (Ives van Hoorne, Alex Moldovan, Jasper De Moor, Danilo Woznica): sandbox integration Rick Hanlon: site development We'd also like to thank countless alpha testers and community members who gave us feedback along the way. Your support and encouragement meant the world to us over this longhaul project!]()
[Early Preview] New React Documentation by rachelnabors · Pull Request #3965 · reactjs/reactjs.org · GitHub
2021-11-01 08:09:23
![正規表現と構文図について解説します。オートマトンについても詳しく述べます。オートマトン・スゴロクで遊びましょう！世間でよく知られている／使われている概念・方法にはこだわらず、僕（檜山）の感覚で一番わかりやすいと思われる筋書きと用語法／図式法を使って説明します。この記事に目を通して“感じ”が掴めたら、形式言語理論の教科書を読み始めることが出来るでしょう。[追記]この記事の内容に対する具体例は、「正規表現とオートマトン：なんだ簡単じゃん、JavaScriptによる実装」にあります。[/追記]内容： 正規表現 正規表現の例 構文図 基本記号 連接 選択 省略可能 繰り返し ストレートワイヤーによるレ…](/assets/img/1635721811.jpg)
![Since announcing the start of the new React documentation effort, we’ve been busy writing the content and building a custom website designed around the learning experience. We are now ready to share this early preview of what we’ve created so far to get your feedback. This early preview is deployed at beta.reactjs.org and is in active development. Please leave any feedback in #3308. TLDR Visit the early preview of the new React Docs at beta.reactjs.org to find: All new learning materials featuring Hooks Interactive examples and challenges “Code diagrams” that visually dissect how Hooks work Illustrations and diagrams that explain how React works New site designed around learning experience You may encounter some broken links—pardon our dust! Some content is yet to be released! What's in the beta The beta has two major sections: Learn React—a comprehensive, step-by-step guide to React. This section is roughly 70% complete. This content is stable and unlikely to change much beyond a few edits and fixes. Some content is still being written (notably, guides for effects, performance optimizations, and React DevTools). API Reference—detailed explanations of each API This section currently only has a few pages, so there is a lot left to write here! Have a look at the useState page to get a sense of what’s coming. The landing page is a temporary stub and will be replaced closer to the end of the project. Similarly, the Home tab is a bit empty now—we intend to port over more things from the existing site, like Blog, after most of the remaining work is done. Known issues No tutorials. We need to complete explanations for all core concepts and APIs before we can add tutorials. (This could be really cool to work on with the community at a later date! But not today!) Performance. When we say “beta,” we mean the site as well as the content! We still have some perf optimizations to make like code splitting at a later stage. Accessibility. While we have been mindful of accessibility during production, we’re waiting until the site is close to getting out of beta to run a comprehensive accessibility audit. What’s next We will make an official post on the blog and put up a banner on the existing site to let visitors know where to find the new docs sometime after gathering feedback from this soft launch. Once we achieve content parity with the old site, we’ll be ready to switch over to this one and keep the old one archived at a subdomain. We'll figure out which pages to redirect to which site at that stage—for now it's too early to discuss a plan. We intend to document all the stable React APIs before we switch over. That includes classes—however, they will be described on a separate page, while most of the docs will use Hooks. Please note that: We are not ready to kick off any official translation efforts at this time because the content is still in a state of flux. To keep the tone cohesive, we are writing the primary new content ourselves. While offers to write are much appreciated, we must regretfully decline for now! You can help! Read and share the docs with friends, colleagues, family! Report bugs! If you see one, please don’t hesitate to leave a comment here or send a fix to the beta folder in the main branch with the [Beta] tag in the title. Tell us what you think! Where to leave feedback? Leave your general feedback in a comment in #3308 or using this handy survey. Leave feedback as you read using the feedback button on the site High-level feedback is more useful than e.g. typos since we'll be doing more editing passes on all the content (bug fixes for typos much appreciated!). We'd particularly appreciate feedback on how to organize the content (see #3965 (comment)). Special thanks Getting to this stage required a lot of effort from different people, whom we would like to thank and acknowledge. This includes: Rachel Nabors: editing, writing, illustrating Dan Abramov: writing, curriculum design Sylwia Vargas: example code Dan Lebowitz: design Razvan Gradinar: design Maggie Appleton: diagram system (not integrated yet) Jared Palmer: site development ThisDotLabs (Dane Grant, Dustin Goodman): site development CodeSandbox (Ives van Hoorne, Alex Moldovan, Jasper De Moor, Danilo Woznica): sandbox integration Rick Hanlon: site development We'd also like to thank countless alpha testers and community members who gave us feedback along the way. Your support and encouragement meant the world to us over this longhaul project!](/assets/img/1635721763.jpg)