投稿時間:2022-05-18 17:36:57 RSSフィード2022-05-18 17:00 分まとめ(38件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
フリーソフト	新着ソフトレビュー - Vector	ベストセラー「億万長者ボード」シリーズの著者が独自の理論でロト6の買い目を予想するソフト「ロト6で億万長者」	https://www.vector.co.jp/magazine/softnews/210122/n2101221.html?ref=rss	億万長者	2022-05-18 17:00:00
ROBOT	ロボスタ	NECのAI技術で杉並区の交通流・人流を細かく分析　スマート街路灯、IoTやカメラを駆使　業務時間を90％以上削減	https://robotstart.info/2022/05/18/nec-ai-suginami-traffic-flow.html		2022-05-18 07:09:38
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] ダイソー、300円ショップ「THREEPPY」を千葉県に初出店	https://www.itmedia.co.jp/business/articles/2205/18/news160.html	itmedia	2022-05-18 16:55:00
IT	ITmedia 総合記事一覧	[ITmedia News] 「LINEでふるさと納税」スタート	https://www.itmedia.co.jp/news/articles/2205/18/news159.html	itmedia	2022-05-18 16:38:00
IT	ITmedia 総合記事一覧	[ITmedia News] マランツも値上げ　電子部品の価格上昇などで「限界を超えた」	https://www.itmedia.co.jp/news/articles/2205/18/news156.html	itmedia	2022-05-18 16:18:00
AWS	AWS Japan Blog	マルチテナントソリューションでAmazon SQSを使う	https://aws.amazon.com/jp/blogs/news/using-amazon-sqs-in-a-multi-tenant-saas-solution/	SaaSアプリケーションのキューイングモデルを設計する際には、データの分離、パフォーマンス、および運用を考慮する必要があります。	2022-05-18 07:34:54
python	Pythonタグが付けられた新着投稿 - Qiita	Pythonで文字列をn文字ごとに区切る	https://qiita.com/iwata-n/items/1092017d9d691f9dbca9	wxyznsiinforiinrangelensn	2022-05-18 16:23:24
Ruby	Rubyタグが付けられた新着投稿 - Qiita	【30歳から目指すwebエンジニア学習録】bootstrap5系の導入でちょっとつまづいた話	https://qiita.com/hk_GoldenRetriever/items/cd4d9ea9b79f0bd03de2	bootstrap	2022-05-18 16:19:44
Ruby	Railsタグが付けられた新着投稿 - Qiita	rails5 progate 整理メモ	https://qiita.com/masatom86650860/items/6e33c0f220fbda49d986	railsprogate	2022-05-18 16:24:00
Ruby	Railsタグが付けられた新着投稿 - Qiita	【30歳から目指すwebエンジニア学習録】bootstrap5系の導入でちょっとつまづいた話	https://qiita.com/hk_GoldenRetriever/items/cd4d9ea9b79f0bd03de2	bootstrap	2022-05-18 16:19:44
技術ブログ	Developers.IO	Google Apps ScriptでGoogleドライブ上のファイルにOCRを行ってスプレッドシートに書き込んでみる	https://dev.classmethod.jp/articles/gas-ocr-output/	googleapps	2022-05-18 07:56:58
技術ブログ	Developers.IO	[小ネタ] 気になるあの時系列データをpandasで可視化してみた	https://dev.classmethod.jp/articles/visualize-my-weight-using-pandas/	pandas	2022-05-18 07:19:30
海外TECH	DEV Community	Zero-Runtime Scoped Component Styling Made Easy!	https://dev.to/blusk/zero-runtime-scoped-component-styling-made-easy-2cno	Zero Runtime Scoped Component Styling Made Easy BackgroundI have traditionally been a Vue user though recently I have decided to write an app in Solid Unfortunately turns out Solid doesn t have anything like lt style scoped gt in Vue I saw some recommendations for CSS in JS solutions but I didn t really like adding additional runtime just for styling and integrations with tooling were painful a lot of the time I needed something with better compatibility and less runtime preferably CSS Modules are almost perfectAs in they seem to address the problem I have almost perfectly One small issue though making a CSS module for every new component gets tedious Imagine having a new CSS file for every component sitting in the same folder Introducing vite plugin inline css modulesSo I wrote a simple Vite plugin that lets you write CSS modules inside of your components It s blazingly fast due to its simplicity and features no additional runtime since it transpiles directly to a CSS module Let s see it in action import css from vite plugin inline css modules const classes css root background color f apply rounded md export const Root gt lt div class classes root gt Hello world lt div gt Transforms to import classes from virtual inline css modules App module css export const Root gt lt div class classes root gt Hello world lt div gt No runtime Also side note this also can help with messy tooling such as integrating Tailwind UnoCSS since I ve experienced problems in the past with CSS in JS solutions and using apply The rule is simple any valid CSS module syntax is going to also be valid inside of a inline CSS module Because that s what it transpiles to Also this ll work with any framework without any sort of special integration because CSS modules are standard across all frameworks Just declare a template string with styles and it should just work Check out the plugin here	2022-05-18 07:18:29
海外TECH	DEV Community	Docs for Everyone!	https://dev.to/meganesulli/docs-for-everyone-28pm	Docs for Everyone Note This article is adapted from a talk I gave at GatsbyCamp Fall which you can watch below In my life before being a developer I was a teacher and curriculum writer And one of the best feelings as an educator was helping learners who felt confused or overwhelmed gain confidence in their abilities to create cool things Similarly one of things I love about documentation is that it lets you have that same impact of helping people deepen their skills But with documentation you have that impact at a much larger scale than is possible through interactions Want numbers Last March I taught an Intro to Gatsby workshop that had around participants After the workshop I rewrote that same curriculum as online documentation in the form of the new Gatsby Tutorial which was getting around views a day With that one set of new docs I m able to reach as many students as if I taught four live workshops every day But as you scale your documentation and your audience grows there s a wider and wider variety of people you re trying to write for The bare bones API reference that worked when your team was just a few internal engineers isn t going to cut it when you have new users trying to use your product for the first time So how do you build one documentation site that works for all your users In this article I outline my top techniques for creating high quality documentation that serves as many users as possible Expose the architectureSet the stageLet readers chooseCheck for understandingGet user feedbackNote I ll mainly look at this challenge through the lens of experience level In other words how can you create a documentation site that works for newcomers to your product as well as your existing power users Tip Expose the architectureIn order for your users to make the most of your documentation they need to understand the big picture of what kinds of information is included in your docs and where to find it A major factor in that comes down to the information architecture of how your docs are organized Imagine you re a user showing up to your product s docs site for the first time It might not be obvious to you where to find the information you re looking for or even what kinds of information is available to you As a documentarian it s your job to provide new users with a clear map and signposts that they can use to navigate the content of your docs Define the architectureOne example of an information architecture that you can use to organize your documentation is the Diátaxis framework by Daniele Procida This is what the Gatsby docs structure is based on The Diátaxis framework splits up documentation into four different categories Tutorials Hold the reader s hand through their first experience with your product These are specifically tailored for newcomers who may not know anything about your product or how it works How To Guides Practical step by step guides to help readers accomplish a specific task Kind of like a recipe you would use for cooking Reference Describes the technical details of how your product works like an API spec or a user manual Explanation Explores more big picture concepts and helps readers deepen their understanding of a topic Gatsby calls these docs “Conceptual Guides Expand for detailed image description The four documentation types can be charted into four quadrants based on their content type and intended use case Tutorials are learning oriented They include practical steps that are meant to serve our study when we re in learning mode How To Guides are task oriented They also contain practical steps but they re focused more on serving our work when we re actively trying to get something done Explanation is understanding oriented It s more theoretical knowledge meant to serve our study Reference is information oriented It s theoretical knowledge that can serve our work The key thing about the Diátaxis framework is that it categorizes documentation based on the reader s current goal Someone using your product for the first time is going to need very different information from a professional actively working on fixing a bug for a client site By organizing your docs in a way that centers your reader s end goal you make it easier for them to discover the resource that they need when they need it Expose the architecture to your readersIt s not enough to just sort all of your docs into organized categories Once you have a structure in place let your readers know what it is This is where the idea of exposing the architecture comes into play For example after we reorganized the Gatsby docs to use the Diátaxis framework we adjusted the site s design to reflect the new information architecture On the docs home page we tell readers what different types of documentation they ll find on our site and when each type is most useful We also list the four doc types in the navigation menu at the top of the page and in the sidebar so that we can keep reinforcing our docs structure in the reader s mind Ultimately it all comes back to helping readers find what they re looking for more easily Tip The expose the architecture principle can also be applied within individual docs Use headings to break down the content within a doc Within a particular doc type use a consistent heading structure so that users know what to expect and can use their pattern matching skills to parse information more quickly Tip Set the stageNow that your overall docs structure is in place it s time to zoom in and focus on the content within each doc That brings us to tip set the stage In other words help your users understand what you re talking about before jumping into the weeds of explaining a new topic When I was a curriculum writer my team had three things that we always checked for in each lesson that we designed context relevance and application Context Explain what you re talking about so that all your readers start with the same baseline understanding This is where you define key terms and concepts link to any prerequisite background knowledge you expect readers to have and explain how the main idea of this doc ties fits into the overall structure of your product ecosystem Relevance Why should readers care about this topic What problem does it help solve Are there specific use cases when they might choose to use this feature over another one Application Walk readers through how to use the feature in their work Most docs already do a good job of the application piece but the context and relevance pieces are especially important because those are what help readers develop their mental model of how all the pieces of your product fit together An exampleLet s see what context relevance and application look like in practice Here s how I used them in Part of the new Gatsby Tutorial which is all about plugins Context What are plugins Plugins are npm packages that let you add pre built functionality to your Gatsby site Relevance Why do we care about plugins Because plugins let you add new features to your site more quickly than if you were to write them yourself from scratch Application How do we add a plugin to our site First we install it with npm Then we configure it in our gatsby config js file Finally we use whatever unique plugin features are relevant in our site In your actual docs you d go into much more detail than this but hopefully that s enough to give you an idea of what you re going for Having these three pieces nailed down early on in your writing process can help you stay focused and make sure your final doc will help all readers regardless of how much previous experience they have with your product Tip Let readers chooseThis next tip is about giving readers multiple ways to consume information on your docs site so that they can choose the option that works best for them Note In education this technique is called differentiation We ll look at two different ways you can give readers options providing multiple forms of engagement and letting users opt into additional details Multiple forms of engagementBy explaining the same concepts in multiple ways you increase the chances that readers will find one option that resonates with their preferred learning style And that means they ll ultimately leave with a better understanding of the overall topicIn the new Gatsby Tutorial in addition to the standard text explanations we also include a variety of other ways that readers can engage with the main ideas DiagramsAnalogiesVideo DiagramsDiagrams can help readers visualize processes like this one that shows how data flows through Gatsby s GraphQL data layer Diagrams are especially useful for complex technical systems or architectures with several moving parts AnalogiesAnalogies help map product specific concepts that readers might not be familiar with onto everyday things that they ve probably encountered in their own lives For instance this illustration explains the difference between the StaticImage and GatsbyImage components using the analogy of asking for directions to a specific street address like Main Street versus asking for directions to a generic location like “the best coffee shop in town Want to learn more Maggie Appleton has an excellent talk called Drawing the Invisible which is about visual metaphors and how they can make technical concepts easier to learn Ever wondered how React is like a potato plant Check out this talk VideoSome readers would rather follow along with someone as they work through the material In that case it can help to embed videos into your docs showing someone walking through all the steps Each part of the Gatsby Tutorial includes an embedded YouTube video like the one below where a colleague and I walk through the content for that part Note Livestreams analogies and diagrams don t replace the text in your doc They complement each other Each of these formats still require text to set the context and explain why this image or resource is relevant Opting into additional detailsAnother way you can provide readers choices is by making it easy for them to opt into or out of additional levels of detail In the new Gatsby Tutorial we do this by making use of MDX s ability to use React components inside of Markdown files We have two different components that clearly separate extra optional content from the main flow of the document announcements and collapsible sections For both components the goal is to clearly indicate to users what content is required the main steps of the Tutorial and what is supplementary and can be skipped That way readers can tailor their experience through the doc to match the level of detail they re interested in AnnouncementsIn the Gatsby Tutorial blue announcement boxes like the one shown below add extra information that stands out visually from the normal flow of the document Sometimes these callouts include Syntax Hints for JavaScript or React newcomers who might not be familiar with a particular piece of syntax Other times they have Pro Tips which go into more detail about things that aren t required for readers to know but that they might find interesting Tip Adding consistent labels to your callouts is another way to expose the architecture of your docs to readers When readers are familiar with the types of callouts they ll see in your docs they ll be able to parse through new docs more quickly Our brains are hard wired for pattern matching When you wrap this optional content in a visually distinct container it helps readers who want to skip that content quickly see where to start reading again Collapsible SectionsThe second component used in the Gatsby Tutorial is a purple collapsible box which lets you hide content behind an expandable dropdown Under the hood it s using the details and summary HTML elements We use this to hide background information that might be helpful for React or GraphQL newcomers but that isn t strictly necessary reading for people who want to just follow along with the steps of the Tutorial This would also be a good component to use if you wanted to document common error messages that users might encounter For example you could have the error name in the summary tag and then users could click to expand for more information on what the error is and how to fix it Tip Check for understandingOnce your users have found the doc they re looking for and they ve read the content how do you know whether they get it By adding in checks for understanding you can use to make sure that your readers leave your docs understanding the things you were hoping they d learn Checks for understanding are built in opportunities for your readers to self assess whether or not they understood the material in the doc Note Depending on what information architecture you decided on for your docs checks for understanding may make more sense in some types than others For example if you re using the Diátaxis framework checks for understanding may make more sense in a Tutorial or Explanation doc than in a Reference doc In the new Gatsby Tutorial each part is book ended by the following At the beginning A list of learning objectives which outline what readers should be able to do by the time they finish reading the doc At the end Separate lists for questions like a mini quiz and key takeaways to help readers reflect on whether or not they achieved the expected learning objectives Want an example Here are some concrete examples of these lists from Part of the Gatsby Tutorial Lesson Objectives By the end of this part of the Tutorial you will be able to Use GraphiQL to explore the data in the data layer and build your own GraphQL queries Use the useStaticQuery hook to pull data into a “building block component Use the gatsby source filesystem plugin to pull data into your site from your computer s filesystem Create a page query to pull data into a page component Summary Questions How do you get data into the data layer How can you see what data is in the data layer How do you get data out of the data layer What are the differences between a page query and useStaticQuery How would you decide which one to use Key Takeaways Source plugins pull data from their original location into the Gatsby GraphQL data layer You can use the GraphiQL endpoint localhost graphql to explore the data in the data layer and design GraphQL queries You can write GraphQL queries to pull data out of the data layer and into your React components To pull data into a “building block component use the useStaticQuery hook To pull data into a page component use a page query These bulleted lists are a super low lift option But you could also do something more interactive like having a CodePen or custom built component to let readers practice the skills they learned Apollo where I work now has a learning platform called Odyssey that uses different kinds of interactive checks for understanding including multiple choice questions fill in the blank paragraphs and embedded code challenges Regardless of the format by providing opportunities for readers to self assess how well they understood the material you re giving them a chance to strengthen their memories of the key ideas covered in your doc which will make it easier for them to remember in the future Tip Get user feedbackOnce you ve gotten all your docs in place and you re happy with how they re organized and the content that s in them the only way you can know whether your docs experience is good or not is by hearing from actual users For the Gatsby docs we have a feedback widget at the bottom of every page which lets readers rate whether the current doc was great fine or bad It also has a space for them to write in a comment if they want to tell us a bit more about their experience All of those feedback responses get stored in a database which is connected to a Gatsby site that pulls all the ratings and comments into a table From there we can look at overall trends and average ratings to see which docs people really like and which ones need to be improved But ultimately what s more interesting to me is reading through all the comments that people leave Positive comments validate assumptionsSome of the comments are really positive which is great for morale But more importantly positive feedback helps us validate our assumptions about which things we thought would resonate with users For example when I was rewriting the Gatsby Tutorial one of the things I wanted to make sure to preserve was how the old Tutorial was approachable for readers without any prior React or GraphQL experience And by reading through the comments on the new Tutorial it s been reassuring to see that several people have called out the fact that the new content doesn t make assumptions about what people already know or use a ton of jargon Constructive comments lead to incremental improvementsBut not all reviews are positive and that can be a good thing By addressing constructive comments and listening to user suggestions you can make incremental improvements that gradually help make your docs experience better for your future users For example the Gatsby Tutorial received one comment from a reader suggesting we add a “continue button to the bottom of each page of the Tutorial which was an easy fix to improve the reader experience Other readers wrote in that they were confused about a particular aspect of CSS modules so I added in an additional Syntax Hint announcement to explain what was going on under the hood And now we don t get comments on that anymore Addressing constructive comments is also a good way to show your users that you care about their experience and that you re actually listening to their feedback This helps build trust with the people in your community which is always a good thing Wrap It UpAnd those are my secrets for creating high quality docs that work for both newcomers and power users To recap what we ve covered It s hard to make one docs site that works for everyone But there are concrete steps you can take to improve your docs experience Expose the architecture to help users understand the big picture of how your docs are structured Set the stage by making sure each doc provides context relevance and application Let readers choose what works best for them by explaining the same idea in a variety of ways and make it clear when they can opt into or out of additional information Check for understanding by providing opportunities for self assessment through questions that align to each doc s learning objectives Get user feedback so that you can validate your assumptions and continue making incremental improvements I hope that you learned at least one new technique that you can use to improve your docs experience for your users Have other tips that I didn t cover I d love to hear about them You can reach me on Twitter meganesulli ResourcesLinked in this post The official Gatsby TutorialDiátaxis documentation frameworkDifferentiation in educationDrawing the Invisible How to Explain React through Visual Metaphors Maggie Appleton s talk for Women of React What is Pattern Matching Apollo OdysseyAdditional resources Docs for Developers An Engineer s Field Guide to Technical Writing by Jared Bhatti Zachary Sarah Corleissen Jen Lambourne David Nunez and Heidi Waterhouse A great book for anyone looking to improve their documentation skills	2022-05-18 07:14:57
金融	JPX マーケットニュース	[東証]上場廃止等の決定：（株）アルテ　サロン　ホールディングス	https://www.jpx.co.jp/news/1023/20220518-11.html	上場廃止	2022-05-18 16:10:00
金融	日本銀行：RSS	展望レポートのハイライト（2022年4月）	http://www.boj.or.jp/mopo/outlook/highlight/ten202204.htm	展望レポート	2022-05-18 17:00:00
海外ニュース	Japan Times latest articles	Around 130 Toyota affiliates affected as leak disrupts industrial water supply	https://www.japantimes.co.jp/news/2022/05/18/business/aichi-water-supply/	Around Toyota affiliates affected as leak disrupts industrial water supplyA massive leakage at a reservoir in Aichi Prefecture has disrupted supplies although many have switched to using stored or well water to continue business	2022-05-18 16:58:43
海外ニュース	Japan Times latest articles	Japan urges China to play ‘responsible role’ for peace in Ukraine	https://www.japantimes.co.jp/news/2022/05/18/national/japan-china-ukraine-peace/	Japan urges China to play responsible role for peace in UkraineChina which has close ties with Russia has refrained from condemning Moscow over its invasion of Ukraine that started more than two months ago	2022-05-18 16:43:50
ニュース	BBC News - Home	UK inflation hits highest for 40 years as energy bills soar	https://www.bbc.co.uk/news/business-61483175?at_medium=RSS&at_campaign=KARANGA	march	2022-05-18 07:27:57
ニュース	BBC News - Home	Conservative MP bailed after arrest on suspicion of rape	https://www.bbc.co.uk/news/uk-politics-61490957?at_medium=RSS&at_campaign=KARANGA	conservative	2022-05-18 07:18:16
ビジネス	ダイヤモンド・オンライン - 新着記事	中国債券、外国人投資家が３カ月連続の売り越し - WSJ発	https://diamond.jp/articles/-/303414	外国人投資家	2022-05-18 16:04:00
北海道	北海道新聞	３月の道内小売、まん防終了で回復　百貨店２％、コンビニ３％増	https://www.hokkaido-np.co.jp/article/682331/	経済産業局	2022-05-18 16:36:00
北海道	北海道新聞	「紅蓮華」が２年連続１位　２１年度、著作物使用料ランク	https://www.hokkaido-np.co.jp/article/682330/	jasrac	2022-05-18 16:34:00
北海道	北海道新聞	ＵＳＪ、ＶＩＰラウンジを開設　７月から、特別ツアー客向け	https://www.hokkaido-np.co.jp/article/682329/	開設	2022-05-18 16:34:00
北海道	北海道新聞	バスのカーテンに火を付けた疑い　喫煙断られ、男逮捕　滋賀	https://www.hokkaido-np.co.jp/article/682328/	滋賀県警	2022-05-18 16:32:00
北海道	北海道新聞	米国で若者の死因トップに銃関連　犯罪急増、交通関連抜き初めて	https://www.hokkaido-np.co.jp/article/682325/	関連	2022-05-18 16:29:00
北海道	北海道新聞	北欧２国、ＮＡＴＯ加盟申請　ロシア脅威で軍事非同盟を転換	https://www.hokkaido-np.co.jp/article/682317/	非同盟	2022-05-18 16:06:19
北海道	北海道新聞	ＫＤＤＩ「月額０円」継続　楽天廃止で申し込み倍増	https://www.hokkaido-np.co.jp/article/682324/	申し込み	2022-05-18 16:21:00
北海道	北海道新聞	燃油補助３６円、上限を突破　ガソリン高止まり、１７０円超	https://www.hokkaido-np.co.jp/article/682318/	経済産業省	2022-05-18 16:09:00
ビジネス	東洋経済オンライン	池上氏解説｢新聞やテレビが報じない｣情報の裏側 自身も記者時代に｢地獄を見た｣裏取りとは | リーダーシップ・教養・資格・スキル | 東洋経済オンライン	https://toyokeizai.net/articles/-/588444?utm_source=rss&utm_medium=http&utm_campaign=link_back	東洋経済オンライン	2022-05-18 17:00:00
ビジネス	東洋経済オンライン	本を出したい人の大半が｢出せないまま終わる｣訳 企画と人脈で出版は可能だが行動する人は少数 | 角田陽一郎と加藤昌治の｢あんちょこ通信｣ | 東洋経済オンライン	https://toyokeizai.net/articles/-/587945?utm_source=rss&utm_medium=http&utm_campaign=link_back	加藤昌治	2022-05-18 17:00:00
マーケティング	MarkeZine	AJAのコネクテッドテレビ特化型動画広告「インクリー」、Webサイト来訪計測機能に対応	http://markezine.jp/article/detail/39019	計測	2022-05-18 16:30:00
IT	週刊アスキー	『ウマ娘 プリティーダービー』のトーク番組「そこそこぱかライブTV Vol.12」が5月19日19時から配信決定	https://weekly.ascii.jp/elem/000/004/091/4091849/	cygames	2022-05-18 16:35:00
IT	週刊アスキー	ココス「10層」のレモンパフェなど爽やか初夏スイーツ！レモン＆フロマージュフェア開催	https://weekly.ascii.jp/elem/000/004/091/4091811/	北海道産	2022-05-18 16:30:00
IT	週刊アスキー	夜のロマンスカーで一夜を過ごそう！　小田急電鉄「ロマンスカー・VSEで一夜を明かすナイトツアー」6月25日・7月2日開催	https://weekly.ascii.jp/elem/000/004/091/4091835/	小田急電鉄	2022-05-18 16:30:00
IT	週刊アスキー	本日5月18日20時からの「カプコンTV！」にモンハン実況者「茶々茶」さんが出演決定。「狩猟笛」限定のオンラインマルチプレイも	https://weekly.ascii.jp/elem/000/004/091/4091844/	出演決定	2022-05-18 16:10:00
マーケティング	AdverTimes	「高さ日本一」から「オンリーワンの立体都市」へ（近鉄不動産）／販促コンペ・企業オリエン	https://www.advertimes.com/20220518/article384117/	応募期間	2022-05-18 07:58:59
マーケティング	AdverTimes	ハウスメーカーの「同質の競争」から脱したい（パナソニック ホームズ）／販促コンペ・企業オリエン	https://www.advertimes.com/20220518/article384109/	応募期間	2022-05-18 07:55:47