投稿時間:2022-11-30 05:34:35 RSSフィード2022-11-30 05:00 分まとめ(36件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
python	Pythonタグが付けられた新着投稿 - Qiita	GPT3を使ってみた	https://qiita.com/Yu_unI1/items/112deff0583884cd2d85	apikey	2022-11-30 04:18:59
Ruby	Rubyタグが付けられた新着投稿 - Qiita	CentOS 7 に Ruby 3.1.3 がインストールできなかったら	https://qiita.com/scivola/items/6a299a2ff70983cf7187	centos	2022-11-30 04:17:22
技術ブログ	Developers.IO	ラスベガスのマクドナルドで、kioskを使って便利に朝食を食べてきました #reinvent	https://dev.classmethod.jp/articles/mcdonalds-kiosk/	kiosk	2022-11-29 19:44:59
技術ブログ	Developers.IO	[速報]AWS Clean Rooms（プレビュー）が発表されました！#reinvent	https://dev.classmethod.jp/articles/aws-clean-rooms-announced/	adamselipskykeynote	2022-11-29 19:41:16
技術ブログ	Developers.IO	[速報] Amazon Connect で機械学習を利用した予測、要員管理、スケジューリングが可能になる新機能が一般提供開始(GA)になりました！ #reinvent	https://dev.classmethod.jp/articles/reinvent-2022-amazon-connect-forecasting-capacity-planning-and-scheduling/	keynote	2022-11-29 19:22:53
技術ブログ	Developers.IO	[プレビュー] Contact Lens for Amazon Connect にエージェントのパフォーマンスの評価フォームを追加され、よりエージェントの管理がしやすくなりました！#reinvent	https://dev.classmethod.jp/articles/contact-lens-for-amazon-connect-reinvent/	contactlens	2022-11-29 19:21:38
海外TECH	Ars Technica	Epson quitting laser printers doesn’t address its bigger sustainability issue	https://arstechnica.com/?p=1900571	inkjet	2022-11-29 19:20:50
海外TECH	MakeUseOf	How to Fix the "No Audio Output Device Is Installed" Error on Windows	https://www.makeuseof.com/windows-no-audio-output-device-installed-error/	How to Fix the amp quot No Audio Output Device Is Installed amp quot Error on WindowsIf Windows is having trouble finding where to output its audio try these tricks and get the quot no audio output device is Installed	2022-11-29 19:16:15
海外TECH	MakeUseOf	Hackers Spreading Malware via TikTok "Invisible Body" Challenge	https://www.makeuseof.com/hackers-spreading-malware-tiktok-challenge/	infostealer	2022-11-29 19:08:17
海外TECH	DEV Community	Auto-magically generate sequence diagrams of your code's runtime behavior	https://dev.to/appmap/auto-magically-generate-sequence-diagrams-of-your-codes-runtime-behavior-597a	Auto magically generate sequence diagrams of your code x s runtime behaviorSequence diagrams are frequently described as the best part of UML Their inherent structure objects flowing across the page time flowing down the page is intuitive and easy to learn And they are one of the best tools for developers and technical non developers like engineering managers and product managers to use when discussing code design Historically creating a sequence diagram required specialized software But accordance with the “everything as code movement tools like PlantUML and Mermaid have kept sequence diagrams relevant by providing a fairly basic text language that can be used to generate sequence diagrams Think Markdown for diagrams But while it s fairly easy and rewarding to create sequence diagrams using text files it still takes effort And being documentation diagrams as code still suffer from the achilles heel of documentation namely getting out of date What if you could have the best of both worlds sequence diagrams with no effort Read on to learn how you can generate sequence diagrams just by running your code Note This is part of a part series In part I ll show how to use sequence diagrams to visually compare the runtime behavior of two different code versions or features How it worksA sequence diagram illustrates a particular code flow like an HTTP request or the processing of a job So the first step in generating a sequence diagram is to run your code through a particular flow I suggest two ways you can do this Run a test caseRun your app and interact with it either through its UI or by sending API requests from a tool like Postman In order to generate a diagram of the code behavior we need to record exactly what happens as the code runs For this we ll use AppMap a free and open source runtime code analysis tool that I created You can use AppMap with Ruby Python Java and JavaScript you can find AppMap setup instructions here AppMap can record both test cases and live application API requests so you can use either technique to acquire the diagram data Once you ve recorded a test case or an interactive session you can use either the AppMap CLI or the AppMap extension for VSCode to generate a sequence diagram I ll cover both options here In both cases the AppMap tools will generate a PlantUML file which will then be rendered as SVG So before proceeding download the PlantUML JAR file the latest version at the time of this writing is plantuml jar The rest of this post will assume that you ve saved this file as Downloads plantuml jar Adjust as necessary Note You can find copies of all the files used in this blog post in this Gist VSCode extensionFirst using the VSCode extension because it s a bit easier Start by installing the AppMap extension from the VSCode Marketplace You ll be prompted to configure your project for AppMap if you haven t done so already Once you ve set up your project commit the AppMap configuration changes to Git so that other members of your team can use AppMap without having to go through the setup process themselves Now open VSCode Settings Then search for “AppMap Sequence Diagram and Configure the location of the PlantUML JAR Enable the Sequence Diagram feature it s currently in Preview You re ready to generate a sequence diagram Open the AppMap view by clicking the icon in the extensions sidebar then right click an AppMap to open the context menu Choose “AppMap View Generate Sequence Diagram Now you ll get prompted twice The first time through just hit Enter to accept the defaults Once you ve seen the generated diagram you can customize its behavior using these options You ll see a brief progress indicator and then your diagram will open in the browser Interpreting the diagramHere s a sequence diagram that I generated from the Rails Sample App th Edition Are you feeling adventurous Try generating AppMaps of Mastodon From left to right you see the inbound HTTP server request POST login From there the code flows to the controllers package then through helpers models to the database and through views Each left to right arrow is an HTTP server request function call SQL query or HTTP client request The right to left arrows are the return values When code runs in a loop you ll see a Loop box enclosing the repeated behavior Here s an example of a Loop also from the Rails Sample App in which a sequence of two SQL queries is repeated times This is a common performance flaw called N query here s a blog post all about N queries in Rails N queries can be tricky to find because all these queries are issued automatically by an ORM system like ActiveRecord Rails Hibernate Java or Django ORM Python In a sequence diagram they are really obvious You can also use AppMap to automatically identify performance flaws like this one Exporting and sharingIf you want to see the generated the PlantUML code click an AppMap to open it and then go to the Explorer view Next to the appmap json file you ll see the PlantUML file uml and SVG svg You can take this UML file or SVG and drop it into any other tool like a GitHub Issue Jira ticket pull request or Slack message CLIYou can also generate sequence diagrams using the AppMap CLI The AppMap CLI is an NPM package called appland appmap so there are three ways to invoke it Install it with npm npm install save dev appland appmap npm run appmap Install it with yarn yarn add dev appland appmap yarn run appmap Run it with npx npx appland appmap latest I ll use option because it s easy to document But to avoid downloading the package from NPM over and over you ll probably want to use or First let s look at the command help npx appland appmap latest sequence diagram helpappmap sequence diagram appmapGenerate a sequence diagram for an AppMapPositionals appmap string required Options version Show version number boolean v verbose Run with verbose logging boolean help Show help boolean d directory program working directory string output dir directory in which to save the sequence diagrams format output format choices plantuml json default plantuml exclude code objects to exclude from the diagramFor basic usage the only option you really need is the appmap argument Here s an example npx appland appmap sequence diagram tmp appmap minitest Following followers page appmap jsonPrinted diagram tmp appmap minitest Following followers page sequence umlNote that the diagram is printed as a sequence uml file in the same directory as the AppMap file Now we ll use PlantUML to convert this to an SVG java jar Downloads plantuml jar tsvg tmp appmap minitest Following followers page sequence umlCheck that the file exists ls tmp appmap minitest Following followers page sequence svg tmp appmap minitest Following followers page sequence svgOpen it in the browser open tmp appmap minitest Following followers page sequence svg There you have it Of course if you want to you can edit the UML by hand and you can upload and share both the UML and SVG files anywhere you like Wrap upThe AppMap CLI appland appmap includes the sequence diagram command which generates a PlantUML text file from AppMap data which by the way is JSON The PlantUML JAR file can transform the text file into SVG or other formats like PNG The AppMap extension ties all these tools together into an integrated UI experience that makes it easy to continuously write code run your app write tests create AppMaps generate sequence diagrams and share them with your team Now try it yourself If you have questions thoughts or comments join us in the AppMap Slack We d love to hear from you	2022-11-29 19:43:46
海外TECH	DEV Community	Make PRs the BEST PART of Programming	https://dev.to/devsatasurion/make-prs-the-best-part-of-programming-1l95	Make PRs the BEST PART of ProgrammingIn this blog post I d like to share some of my thoughts on how I ve been able to effectively think about software development What I m suggesting is not all that new most of us do something similar already I m not advocating for a revolution Rather I hope to empower teams with a mindset the transforms the rote painful and mundane into something powerful and efficient Introducing PRO Programming In our early days as developers we often find ourselves searching for information on what to program Where is this type error coming from How am I supposed to use this poorly documented library Or even What does this horrible JavaScript snippet actually do But as we mature and grow in our careers we become more confident in writing code At some point we transition from thinking about what to program and begin asking how we should program We start to ask more challenging questions like How can multiple developers work together on the same task How do I write code changes so as to have the lowest chance of causing a production outage What s the most efficient way of running a software development team PRO Programming falls into this second category it helps us know how to program not what to program PROP R O aka Pull Request Oriented Programming is a way to prioritize developer time and quantize the delivery of code The Pull Request is a developer s discrete unit of code On a PRO team each developer has the following priorities Top Priority Deliver Excellent PRs Second Priority Unblock teammate PRs Third Priority Protect the high quality codebase Now let s go through and break down how each of these tenants works in practice First off what is a pull request The Pull Request is a developer s discrete unit of code If you ve developed using git in any kind of team environment you probably understand why everyone pushing to the main branch is a bad idea Pull Requests aka Merge Requests or Code Reviews depending on your stack are the gatekeeper for the official codebase protecting against merge conflicts and silly bugs I ve yet to work on a team that doesn t use this model where automated tests and other team members must approve your changes before they become part of the codebase If a developer s job is to deliver a feature fix a bug or to some other end modify a technical asset the way they do it is by making a code change Under PRO we no longer think of Pull Requests as a necessary evil or even just as the process by which I get my code change in The Pull Request is the deliverable Or rather a series of pull requests is the deliverable Importantly the pull request includes more than just making a code change Pull requests include The code change The documentation Comprehensive and documented testing steps Evidence of all automated checks passing Approval from code owners A successful merge and deploymentWhen I pick up a task on a PRO team I m not finished with that task until the Pull Request is complete As the author I m responsible to make sure tests are passing I ve received approval from code owners and even after merging that the deployment was successful PRs may rely on one another They must necessarily be the product of multiple developers approvals But at the end of the day they are the fundamental smallest quanta of code and through the sum of them the codebase is built As a Developer this distillation of responsibilities into the PR unit allows for the following straightforward priorities Deliver Excellent PRsTo be as effective as possible a developer s primary area of focus should be the tasks they ve been assigned We don t want to get bogged down in a long review cycle so we need to make PRs as easy to review as possible The goal of a PR is to convince other developers that this change will improve the codebase Excellent PRs are As small and focused as possible Well tested and documented Free from bugsSmall and focused PRs are easier to develop test and review Don t include any code changes that aren t directly involved in the task you re solving Only solve one task at a time Prioritize limiting the number of files and number of lines changed to make it easier for reviewers Smaller scope also makes it easier to debug and fix broken tests Well tested and documented PRs help reviewers now and the whole team in the future You tested your changes share how you tested Explain why the change is happening and include a link to your issue tracker That makes it easier for reviewers and months from now you ll be able to remember why you made the change Bug free PRs seem like a no brainer but hear me out The code review process is not a time for teammates to catch your typos Before submitting a PR you should code review your own PR Asking code owners to catch simple bugs syntax errors and typos in your PR is a waste of their time and frankly is disrespectful Tip When you ask others for PR reviews you are presenting a finished product that is ready to be merged as soon as they approve You should be confident in the code before you ask for reviews Unblock teammate PRsFew great projects are built in isolation and still fewer projects that pay a good salary As a team member I am responsible for doing everything I can to unblock the PRs of my teammates The most straightforward way of doing this is by submitting code reviews but it s not the only way Pair programming team discussions and shipping high quality internal tooling are all important tasks as well That said here are a few tips on giving high quality code reviews High quality code reviews are timely When a teammate requests a code review a code owner should submit a review within work day I find it s easiest to have a daily routine of reviewing all open PRs This applies both for initial reviews and for re reviews Tip It is the PR author s responsibility to request reviews This can be tedious to request manually on every PR but Github allows you to auto assign reviewers High quality code reviews have a certain tone to them Writing comments in a way that is respectful humble and as often as possible open ended can lead to more efficient collaboration and faster code changes Defensiveness and arguing dramatically slow down the PR process Reviews should look at the PR holistically but also keep in mind the goal of limiting the scope of each PR Don t ask for changes to things that aren t part of the original scope opt instead for opening a tech debt ticket Call out changes that are too broad in scope or seem irrelevant More small PRs are better than fewer big PRs Tip If a developer repeatedly receives the same feedback on their PRs they should discuss offline with senior team members how they can prioritize delivering excellent PRs Protect the high quality codebaseThe metaphor of PRs as a gatekeeper for the codebase was used earlier in this post and it still stands Each and every PR could be a trojan horse for debilitating technical debt There s a balance to draw between delivering code quickly unblocking teammates and enforcing the high standards we have for our codebase Tip PR reviews around code quality style and functionality can be one of the most effective ways of sharing knowledge within the team If you don t understand something post a comment asking a question If the PR author made some mistake help them understand your team s best practices Be a stickler Read every line of code in a PR you approve If you approve a PR with tech debt or a bug in it you are just as much responsible as the author if the PR if not more Validate the functionality A comprehensive test suite can confirm a lot of things but it often can t confirm that a PR does what it says it will do Manually validating the changes in a test or local environment is the best way to confirm the quality of a PR Automate the things humans are bad at formatting import sorting unit testing etc IDE extensions git hooks and automated workflows are highly effective at this sort of task You shouldn t ever need to post a PR comment asking someone to fix indentation or import order use tooling Whether you use Github Actions Circle CI Travis or something else automated tests are vital for maintaining code quality The principles and best practices of PRO Programming have empowered me and the teams I m part of to write code quickly and effectively I hope they give you clarity and level up your teams too Kaeden Wile	2022-11-29 19:07:54
Apple	AppleInsider - Frontpage News	Court approves Apple's $50M settlement to end Butterfly Keyboard lawsuit	https://appleinsider.com/articles/22/11/29/court-approves-apples-50m-settlement-to-end-butterfly-keyboard-lawsuit?utm_medium=rss	Court approves Apple x s M settlement to end Butterfly Keyboard lawsuitA court has given its preliminary approval to a million settlement ending the Butterfly keyboard class action lawsuit against Apple Apple s Butterfly keyboard mechanism and membraneOriginally agreed by Apple in July the U S District Court for the Northern District of California has granted the preliminary approval for a settlement in the class action lawsuit concerning the controversial Butterfly keyboard mechanism Read more	2022-11-29 19:53:13
海外科学	BBC News - Science & Environment	Bird flu: Free range turkey supplies hit by bird flu	https://www.bbc.co.uk/news/science-environment-63797896?at_medium=RSS&at_campaign=KARANGA	avian	2022-11-29 19:51:32
海外科学	BBC News - Science & Environment	Somalia meteorite: Joy as scientists find two new elements	https://www.bbc.co.uk/news/world-africa-63800879?at_medium=RSS&at_campaign=KARANGA	nightfall	2022-11-29 19:27:21
海外科学	BBC News - Science & Environment	Shenzhou-15: China sends astronauts to Tiangong space station	https://www.bbc.co.uk/news/world-asia-china-63798391?at_medium=RSS&at_campaign=KARANGA	outpost	2022-11-29 19:22:55
医療系	医療介護 CBnews	新サービス類型、訪問介護崩壊阻止のわずかな望みか-快筆乱麻！masaが読み解く介護の今（83）	https://www.cbnews.jp/news/entry/20221129153122	介護保険	2022-11-30 05:00:00
ニュース	BBC News - Home	Host of top hospitals targeted by nurse strikes	https://www.bbc.co.uk/news/health-63799244?at_medium=RSS&at_campaign=KARANGA	december	2022-11-29 19:23:02
ニュース	BBC News - Home	Bird flu: Free range turkey supplies hit by bird flu	https://www.bbc.co.uk/news/science-environment-63797896?at_medium=RSS&at_campaign=KARANGA	avian	2022-11-29 19:51:32
ニュース	BBC News - Home	World Cup 2022: USA lead Iran in must win game	https://www.bbc.co.uk/sport/av/football/63802131?at_medium=RSS&at_campaign=KARANGA	world	2022-11-29 19:55:17
ニュース	BBC News - Home	Wales v England: Rate the players from World Cup 2022	https://www.bbc.co.uk/sport/football/63801293?at_medium=RSS&at_campaign=KARANGA	qatar	2022-11-29 19:10:25
ビジネス	ダイヤモンド・オンライン - 新着記事	「円安一服」は日銀に追い風、物価目標達成を理由に政策修正の道が開いた - 経済分析の哲人が斬る！市場トピックの深層	https://diamond.jp/articles/-/313669	物価上昇	2022-11-30 05:00:00
ビジネス	ダイヤモンド・オンライン - 新着記事	吉野家は増収率1割に届かず、すき家は2割超の増収…牛丼「業績格差」のワケ - ダイヤモンド 決算報	https://diamond.jp/articles/-/313668	その状況下で、好決算を記録した企業とそうでない企業の差は何だったのか。	2022-11-30 04:55:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「来年の予測」を投資家が信じてはいけない3つの理由 - 山崎元のマルチスコープ	https://diamond.jp/articles/-/313667	資産運用	2022-11-30 04:50:00
ビジネス	ダイヤモンド・オンライン - 新着記事	CAが「やられた！」と白旗、食品メーカー社長の“一流”を感じた振る舞い - ファーストクラスに乗る人の共通点	https://diamond.jp/articles/-/313517		2022-11-30 04:45:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「30万円で家が買える」中国の元炭鉱街へ、ローン地獄を逃れ移住する若者たち - ふるまいよしこ「マスコミでは読めない中国事情」	https://diamond.jp/articles/-/313569	「万円で家が買える」中国の元炭鉱街へ、ローン地獄を逃れ移住する若者たちふるまいよしこ「マスコミでは読めない中国事情」一人っ子政策などの影響で、中国の代はいま、かつてないほど高学歴だ。	2022-11-30 04:40:00
ビジネス	ダイヤモンド・オンライン - 新着記事	サプライチェーンの脱中国化をコスト増なしで!?無茶ぶり経営への現実解とは - サプライチェーン難問山積	https://diamond.jp/articles/-/313674		2022-11-30 04:37:00
ビジネス	ダイヤモンド・オンライン - 新着記事	ワークマン「Excel経営」が超進化！次のデータ分析ツールに選んだのは？ - 酒井真弓のDX最前線	https://diamond.jp/articles/-/313666	excel	2022-11-30 04:35:00
ビジネス	ダイヤモンド・オンライン - 新着記事	カインズの「立つほうき」がiPhoneと同じ画期的イノベーションな訳 - News&Analysis	https://diamond.jp/articles/-/313481	カインズの「立つほうき」がiPhoneと同じ画期的イノベーションな訳NewsampampAnalysisブランドを活性化させるためには、大なり小なりイノベーションを起こしていく必要があります。	2022-11-30 04:30:00
ビジネス	ダイヤモンド・オンライン - 新着記事	人とAIのコラボが生み出す「仕事を奪うのではなくサポートする」クリエイティブとは - 及川卓也のプロダクト視点	https://diamond.jp/articles/-/313648	人とAIのコラボが生み出す「仕事を奪うのではなくサポートする」クリエイティブとは及川卓也のプロダクト視点今年月、アドビの年次イベント「AdobeMAX」が年ぶりにリアルの場で開催された。	2022-11-30 04:27:00
ビジネス	ダイヤモンド・オンライン - 新着記事	パナソニックはなぜテスラになれなかった？精神科医・和田秀樹の答え - ニュース3面鏡	https://diamond.jp/articles/-/312971		2022-11-30 04:25:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「他人の目ばかり気にしてしまう」人の3つの愚かな考え - ニュース3面鏡	https://diamond.jp/articles/-/313665	「他人の目ばかり気にしてしまう」人のつの愚かな考えニュース面鏡「承認欲求」は、心理学の世界ではずいぶん前から存在していた概念です。	2022-11-30 04:20:00
ビジネス	ダイヤモンド・オンライン - 新着記事	中国のデモ参加者、「監視国家」の標的に - WSJ発	https://diamond.jp/articles/-/313714	監視国家	2022-11-30 04:19:00
ビジネス	ダイヤモンド・オンライン - 新着記事	マッチングアプリの沼にハマる44歳女性のリアル、お金・危険・結婚願望… - ニュース3面鏡	https://diamond.jp/articles/-/313254	マッチングアプリの沼にハマる歳女性のリアル、お金・危険・結婚願望…ニュース面鏡沼とは何かある特定のことにはまったり、収集がやめられないことを「沼にはまる」と言います。	2022-11-30 04:15:00
ビジネス	ダイヤモンド・オンライン - 新着記事	がんの予防やネガティブ感情軽減に「アブラナ科の野菜」が効果か - カラダご医見番	https://diamond.jp/articles/-/313612	国立がん研究センター	2022-11-30 04:10:00
ビジネス	ダイヤモンド・オンライン - 新着記事	志願者数急増中の「関東学院中高」で新任校長が見つけたもの - 中学受験のキーパーソン	https://diamond.jp/articles/-/313189	中学受験	2022-11-30 04:05:00
ビジネス	東洋経済オンライン	コロナ禍の海外旅行､治安良く物価安い国を選べ 乗り鉄､撮り鉄ともに大満足の国はどこか？ | 海外 | 東洋経済オンライン	https://toyokeizai.net/articles/-/632680?utm_source=rss&utm_medium=http&utm_campaign=link_back	東洋経済オンライン	2022-11-30 04:30:00