投稿時間:2022-03-15 10:30:36 RSSフィード2022-03-15 10:00 分まとめ(37件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	Apple、｢macOS Big Sur 11.6.5｣をリリース	https://taisy0.com/2022/03/15/154656.html	apple	2022-03-15 00:01:21
TECH	Engadget Japanese	Blue Origin4回目の有人飛行に「カーダシアンの新恋人」ピート・デヴィッドソンが搭乗	https://japanese.engadget.com/pete-davidson-will-be-on-blue-origins-next-spaceflight-005055895.html	blueorigin	2022-03-15 00:50:55
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 学生の約70％が「金融について学びたい」　身に付けたい知識は？	https://www.itmedia.co.jp/business/articles/2203/15/news068.html	ferci	2022-03-15 09:46:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] ワークマン、ジョギング・ランキングシューズを拡充　初心者から上級者向けまで展開	https://www.itmedia.co.jp/business/articles/2203/15/news034.html	itmedia	2022-03-15 09:35:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 大阪・豊中に「イオンタウン豊中庄内」22年冬開業　”食とサービス”のワンストップSC	https://www.itmedia.co.jp/business/articles/2203/15/news045.html	itmedia	2022-03-15 09:10:00
TECH	Techable（テッカブル）	巣鴨に「AIが描くNFTアート展」出現！ 3つのAIが共創した新感覚の絵画をVRで鑑賞	https://techable.jp/archives/175241	大正大学	2022-03-15 00:00:49
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	南紀白浜エアポート、ARによるメンテナンスやサイネージロボットなどの実証実験 | IT Leaders	https://it.impress.co.jp/articles/-/22840	itleaders	2022-03-15 09:30:00
IT	情報システムリーダーのためのIT情報専門サイト IT Leaders	パナソニック、画像センシングSaaS「混雑状況可視化アプリケーション」を提供 | IT Leaders	https://it.impress.co.jp/articles/-/22839	パナソニック、画像センシングSaaS「混雑状況可視化アプリケーション」を提供ITLeadersパナソニックシステムソリューションズジャパンは年月日、画像解析SaaS「現場センシングSaaS」を発表した。	2022-03-15 09:30:00
AWS	AWS	UnionBank Gains Agility to Innovate and Hyperscale with Infosys Finacle Digital Banking Suite on AWS	https://www.youtube.com/watch?v=hBsxGXRy8Uc	UnionBank Gains Agility to Innovate and Hyperscale with Infosys Finacle Digital Banking Suite on AWSDigital transformation is leading banking agendas and speed is vital to retain customer loyalty UnionBank of the Philippines UnionBank embraced the concept of ubuntu by combining the unique value propositions of fintechs to build financial solutions for individuals institutions and micro small and medium enterprises MSMEs and to increase technology adoption in the Philippines UnionBank worked with Infosys Finacle an AWS Partner to migrate its core banking platform from an on premises deployment to the Finacle Digital Banking Solution Suite on Cloud a software as a service SaaS With Infosys Finacle as UnionBank s SaaS partner the bank s IT team can assume more strategic roles to further innovate new digital banking services UnionBank estimates a lower TCO greater flexibility and scalability Learn more about AWS for Financial Services at Learn more about AWS and Infosys at Subscribe More AWS videos More AWS events videos ABOUT AWSAmazon Web Services AWS is the world s most comprehensive and broadly adopted cloud platform offering over fully featured services from data centers globally Millions of customers ーincluding the fastest growing startups largest enterprises and leading government agencies ーare using AWS to lower costs become more agile and innovate faster AWS AmazonWebServices CloudComputing AWSCustomer	2022-03-15 00:36:27
デザイン	コリス	これは覚えておきたい！ コンテナ・ラッパーを定義するCSSの古い書き方とモダンCSSを使用した書き方	https://coliss.com/articles/build-websites/operation/css/defines-container-using-modern-css.html	続きを読む	2022-03-15 00:36:10
Ruby	Rubyタグが付けられた新着投稿 - Qiita	【Railsチュートリアル】1章のHerokuデプロイでArgumentError	https://qiita.com/yoppy_yophy/items/af0d9eea05e524e52922	【Railsチュートリアル】章のHerokuデプロイでArgumentError要約HerokuでサポートされているRubyのバージョンと手元のバージョンを揃えたら解消した。	2022-03-15 09:50:36
Ruby	Railsタグが付けられた新着投稿 - Qiita	【Railsチュートリアル】1章のHerokuデプロイでArgumentError	https://qiita.com/yoppy_yophy/items/af0d9eea05e524e52922	【Railsチュートリアル】章のHerokuデプロイでArgumentError要約HerokuでサポートされているRubyのバージョンと手元のバージョンを揃えたら解消した。	2022-03-15 09:50:36
技術ブログ	Developers.IO	[体験レポ]2022国際ロボット展で京セラ株式会社のブースに行ってきました	https://dev.classmethod.jp/articles/irex-2022-kyocera-robotics/	onzukamuscle	2022-03-15 00:14:01
海外TECH	DEV Community	Total Share	https://dev.to/ushieru/total-share-4aip	Total ShareEn un capitulo más de esta serie llamada Ingeniero aburrido un fin de semana Han visto que Huawei tiene una funcionalidad llamada Huawei Share Algo muy al estilo de AirDrop Bueno pues mi laptop la tiene y yo no tengo un smarthphone Huawei pero me parecióinteresante el concepto Y bueno si hacemos algo asíque todos podamos usar independiente del OS que funcione en red que te parece todos los dispositivos cuentan con comunicación TCP IP asíque porque no Manos a la obra Para este proyecto decidíusar Flutter porque ya compila en todos lados por default asíque nos quitamos un peso de encima SocketIO vs TCP Sockets SocketIO es facilísimo de implementar y ya viene bastante preparado para estas cosas pero estos proyectos son para aprender cosas nuevas Que somos huevos o limones Esto no pretende ser un tutorial asíque Flutter Sockets Muchos colores TotalShareProbado en x Windows x Linux x Andorid iOS MacOS Te invitoA que clones el repo o le hagas un fork el código no es el mejor asíque pueden hacerle muchos cambios aparte de agregar funcionalidades como desconectar clientes rechazar archivos compartir por internet Las posibilidades son infinitas Y no creo darle demasiado soporte por ahora hehehe	2022-03-15 00:33:21
海外TECH	DEV Community	Merging Pull Requests in GitHub Has Never Been EASIER Thanks to Mergify	https://dev.to/n3wt0n/merging-pull-requests-in-github-has-never-been-easier-thanks-to-mergify-2lil	Merging Pull Requests in GitHub Has Never Been EASIER Thanks to Mergify The ProblemMerging code into a branch could be a really time consuming task especially on big projects with many developers or anyway when you have a big number of Pull Requests that have to be reviewed approved and merged in the correct order And it s not just the merge itself for each pull request you have to decide who the reviewers are assign the labels perhaps rebase your branches to the most updated version that was merged in the meantime and much more Wouldn t be nice if we could have a free automation tool which works with any CI integrates natively with GitHub and can do for us all the things I ve just mentioned Well today I have that very tool for you Let s talk about it VideoAs usual if you are a visual learner or simply prefer to watch and listen instead of reading here you have the video with the whole explanation and demo which to be fair is much more complete than this post Link to the video If you rather prefer reading well let s just continue The Solution MergifyWhat I have for you today is the review of a tool that promises to revolutionize the way we work with our Pull Requests and we do the merges Mergify Mergify is a tool that helps prioritizing queuing and automatically merging your pull requests and which can also rebase and update your branches while commenting labeling assigning and closing your pull requests If it sounds really powerful it s because it is I know what you re thinking can t I do some of these things in GitHub directly Well yes and no As we will see in a minute GitHub does have some of same the features that Mergify has but you need to either activate them manually or they are not as powerful and complete as the ones in Mergify Plus there are many other features that are simply not present in GitHub at least at the time of writing this You ll soon see what I mean Mergify OnboardingLet s start with quickly seeing how to setup the tool the first time you use it All you have to do is going to mergify com and click on sign up You will then need to insert you GitHub username and password Mergify in fact uses the GitHub authentication and you re in To interact with GitHub Mergify requires the installation of a GitHub App As always happens when installing GitHub Apps you can pick and choose the organizations and accounts where you want to install the app and then you can choose if you want it to access all your repos in that organization or only the hand selected ones And when it is done you ll be redirected to the Mergify Dashboard where a message will welcome you saying the setup of Mergify on your account is completed and that to fully utilize the service you should create a config file in the root directory of your repositories with the rules that you want to apply We will see how to do all of this in just a moment but let s go back to the dashboard and see what we have here out of the box Mergify DashboardAs you can see the dashboard is quite minimalistic On the left hand side we have the selection of the account or organization we want to work on It shows the organizations accounts where we have installed the app but we can always add more organizations Then we have the list of repositories currently visible to Mergify in the selected account We can pick the repo we want to work on using the dropdown list and we can add additional repos if we have enabled only a subset of repositories in the App Next is the Application Keys menu where as the name says we can create API keys to be used for integration with other tools that require API access We then have the billing section which we will explore later on when we talk about pricing and the Usage section which shows you the active users in your selected repos It is important to note that for Mergify they count every user that have write access to your repos as a seat We will take a look at the different plans later on but don t worry they do have a free forever plan If you decide you like to tool and you want to subscribe to their paid plans you can use the coupon code CODERDAVE to get months for free for any offer Initial Configuration and Config EditorLet s get now into the beefier stuff about Mergify and let s configure the first set of rules Check out this part of the video for a full demo Mergify relies on a configuration file called mergify yml in the root of your repo We can create this from scratch or we can use the Config Editor in the UI Just select the repo you want to work on click on the Config Editor Tab and there you are with the first default rule Let s take a closer look at it pull request rules name Automatic merge on approval conditions approved reviews by gt actions merge method mergeAs you can probably see the rule is very simple It will just wait for a PR to be approved from at least reviewer and then automatically merge it Analyzing the YAML we can see the general structure of it First off this is a Pull Request Rule we will see later that there can be different types of rules it has name which can be anything we want some conditions and some actions As you probably thought already the actions are executed when the conditions are verified Also you ve probably noticed the character in front of the condition That is part of the Mergify grammar and it means number If we were to use approved reviews by instead without we would have the list of reviewers Test Your ConfigurationOne thing I love about Mergify is that it allows you to test the configuration before even creating the config file Just write in the textbox the number of the PR in that repo which you want to test your configuration rules against and see the result In the example above you can see that the summary says potential rule This means that the rule we have tested can potentially be applied to that pull request if the conditions apply This is because the condition specify that the PR must be approved while it is currently not If I were to change the condition to this wouldn t make sense in practice but for demo purposes and re test the rule The rule would be marked as matching because all the conditions When you are ready to push your config to the repo you can just click on the Create a pull request with this configuration button and well I think the button text is descriptive enough ️Please note that if a configuration is pushed to a repo and some rules matches already the actions will be executed immediately More Pull Request RulesOf course we can write much more complex rules pull request rules name Automatic merge on approval PRs targeting README md conditions approved reviews by gt files README md actions merge method mergeThe rule above for example will execute on all and only the PRs that are approved and target the README md file As you ve probably noticed by default all the conditions have to match for the actions to be executed So what if we want one or the other pull request rules name Automatic merge conditions or approved reviews by gt files README md actions merge method mergeI can use a modifier like you see above to add an or condition to the rule The rule will now work on all PR that are either approved or target the README md file And in fact if we try and validate the rule we can see that the summary looks a little different You can in fact see that now we have the any of clause there And of course we can nest and combine those conditions Let take a look at this rule pull request rules name Automatic merge with and and or conditions and approved reviews by gt or files README md files actions merge method mergeWhat will it do It will automatically merge all the PRs that are approved and target either a README md file or target only file whatever it is Multiple Rules and Multiple ActionsAll we have seen so far included a single rule and a single action in that rule Config files tho can get much more interesting We can have multiple rules and each can have multiple actions Check out this part of the video for a full demo pull request rules name Automatic merge on approval conditions or files README md files actions merge method merge name Assign to nwtn if YAML and label as Enhancement conditions files yml closed actions assign add users nwtn label add enhancementLet s analyze this example First off we have two Pull Request rules The first one is the same we had before the second one is a little more interesting On the conditions part we want to target all the PRs that target yml files this is what the files yml means and that are not closed the in front of a condition is equivalent to not On the actions side instead you can see we have two actions assign and label Just as recap what the rule does is assigning the PR to the user specified and labeling it for all the PRs targeting YAML files and that are not closed And you can see it executing in the screenshot above Mergify Manual CommandNot bad right and we ve just scratched the surface of what this tool can do Mergify also exposes a set of Commands that you can trigger by commenting on the pull request Check out this part of the video for a full demo You can see the list of those commands on the Commands page in the docs but what they do is basically run some action directly without leveraging the rule system At the time of writing this article the available commands are rebaseupdatebackportcopysquashrefreshTo execute a command all you need to is tagging the mergify bot in the Pull Request comment section and specify a command For example if I want to update the branch associated with a pull request to include all the changes that have been made in the main branch I will comment this Mergifyio updateand Mergify will take care of the rest What Else Ok enough talking about Pull Request rules let s see what other actions and rules we can add to our configuration File First thing to mention is that there are main sections of the configuration file Pull Request Rules Queue Rules Command Restrictions DefaultsAnd you can have config files with all four of them or as little as just one of them And anything in between We have talked about Pull Request Rules until now As the name says they apply to pull requests You can use them to govern how and when your merges will happen As we have seen before those rules need to have a name some conditions and some actions to be executed Command RestrictionsCommand Restrictions are well as the name says they allow you to put restrictions on the commands that you can execute via the Mergify bot by commenting on the PRs commands restrictions backport conditions base mainFor example the rule above limits the execution of the backport command for pull requests coming from the main branch DefaultsThe Defaults section is used to define default configuration values for actions run by pull request rules and by commands If the options are defined in pull request rules they are used otherwise the values set in defaults are used For example the following configurationdefaults actions comment bot account Autobotpull request rules name comment with default conditions label comment actions comment message I Mergifyand this onepull request rules name comment with default conditions label comment actions comment message I Mergify bot account Autobotwill produce the same results Queue RulesTo understand Queue Rules we need first to understand what merge queues are and what problem they solve Merge Queues and The ProblemImagine that you have repository you make some changes and you open a PRYou PR is valid so the CI and all the test pass While the pull request is open another commit is pushed to main either directly or from another pull request The tests are run against the main branch by the CI and they pass as well The pull request is still marked as valid by the continuous integration system since it did not change As there is no code conflict the pull request is considered as mergeable by GitHub When you merge the PR however it is possible that the pull request that was once working breaks the main branch The stalled pull request might introduce regression or breakages into the production system Using a merge queue solves that issue by updating any pull request that is not up to date with its base branch before being merged That forces the continuous integration system to retest the pull request with the new code from its base branch If a merge queue were being used in the previous example Mergify would automatically merge the main in the base branch The continuous integration system would have rerun and marked the pull request as failing the test removing it from the merge queue altogether Mergify Queues provide this but we can even take this a step forward for example batching the merges of multiple PRs in the correct order etc When multiple pull requests are mergeable they are scheduled to be merged sequentially and are updated on top of each other The pull request branch update is only done when the pull request is ready to be merged by the engine for example when all conditions are validated That means that when a first pull request has been merged and the second one is outdated like you can see in this image Mergify will make sure the pull request is updated with the latest tip of the base branch before mergingWith this there s no way to merge a broken pull request into the base branch Queue RulesNow that we have seen this in theory let s see how to configure and use merge queues in Mergify Check out this part of the video for a full demo Let s start with a simple example This set of rules gives us the ability to enqueue our PR merges based on conditions queue rules name CoderDave queue conditions check success My CI Jobpull request rules name Merge using the merge queue conditions base main approved reviews by gt check success My CI Job actions queue name CoderDave queueOn the upper part we have the queue definition and the condition for auto merge in this case the success of the My CI Job Then we have a rule with the action of type queue this will send to the queue all the PRs that match the conditions This gives you a general idea of how this works you need to define queues and have conditions to decide which PRs to enqueue Let s take a look at another more complex example of a Queue Rule queue rules name urgent conditions check success My CI Job name default conditions check success My CI Jobpull request rules name move to urgent queue when reviews and label urgent conditions base main approved reviews by gt label urgent actions queue name urgent name merge using the merge queue conditions base main approved reviews by gt check success My CI Job label urgent actions queue name defaultIn this case we have two queues urgent and default The concept here is to be able to enqueue PRs base on their priority for example hotfixes vs features based on their label If a PR is labeled as urgent then it will be sent to the urgent queue otherwise it will be sent to the other queue In this case the urgent PRs will be merged more quickly because if you look at the rule they require the CI to pass only while in the queue The normal PRs instead need the CI to be successful also as prerequisite for them to be enqueued Finally let s talk about another feature that is part of the Queue Rules and that makes Mergify offering quite appealing I m talking about the Speculative Checks If your continuous integration system takes a long time to validate the enqueued pull requests it might be interesting to enable speculative checks This will allow Mergify to trigger multiple runs of the CI in parallel In the following example by setting the speculative checks option to Mergify will create up to new pull requests to check if the first three enqueued pull requests are mergeable ueue rules name default speculative checks conditions check success My CI Jobpull request rules name merge using the merge queue and speculative checks conditions base main approved reviews by gt check success Travis CI Pull Request actions queue name defaultMultiple pull requests can be checked within one speculative check by settings batch size For example by settings speculative checks and batch size Mergify will create two pull requests a first one to check if the first three enqueued pull requests are mergeable and a second one to check the three next enqueued pull requests queue rules name default speculative checks batch size conditions check success Travis CI Pull Requestpull request rules name merge using the merge queue and speculative checks conditions base main approved reviews by gt check success Travis CI Pull Request actions queue name defaultAt this point I should mention that both the multiple queues and speculative checks features are not present in the free plan they are part of the paid plans ️It is also important to note that in general a PR will be automatically removed from a queue if the conditions don t match anymore For example if one of the conditions is that the PR must be approved and someone removes the approval that PR will be taken off the queue if it has not been already merged of course Pricing and Save Some MoneyFinally let s talk about prices and how you can save some money on Mergify As I ve mentioned before they do have a forever free plan you can use for your repositories and that covers the use on public repos with unlimited actions and rules and even basic merge queues If you want more like using Mergify on private repos advanced queue features batch merge or even having a dedicated bot account to act on your behalf you can subscribe to one of their paid plans And as I ve mentioned before if you want to get months off any of their paid plans you can use the code CODERDAVE all uppercase at purchase But be quick because this is valid only for the first people who will use it Mergify Startup ProgramAnd if you are part of a startup it gets even better because you can get up to value of Mergify services free of charge The company has in fact launched their startup program a month partnership between new ventures and Mergify which gives access to all Mergify features for free If you want to apply to it you can do it from their Startup Program page link in the description below or email them at startup mergify io ConclusionsLet me know in the comments below what you think about Mergify and if you ve had a chance to use it already Also check out this video in which I explain how to properly manage Pull Requests in GitHub Like share and follow me for more content YouTube Buy me a coffeePatreonNewsletterCoderDave io WebsiteMerchFacebook page‍GitHubTwitterLinkedInPodcast	2022-03-15 00:08:41
Apple	AppleInsider - Frontpage News	iOS 15.4, watchOS 8.5 allow Apple Watches to be restored with a nearby iPhone	https://appleinsider.com/articles/22/03/15/ios-154-watchos-85-allow-apple-watches-to-be-restored-with-a-nearby-iphone?utm_medium=rss	iOS watchOS allow Apple Watches to be restored with a nearby iPhoneApple s new iOS and watchOS updates allow users to restore an Apple Watch using a nearby iPhone Credit AppleIn a support document updated on Monday Apple says that its new software updates which were released Tuesday allow users to restore Apple Watch firmware using an iPhone Read more	2022-03-15 00:05:48
医療系	内科開業医のお勉強日記	スタチン治療によるLDL-C値の絶対的な低下と個々の臨床転帰との決定的な関連は確立されていない	https://kaigyoi.blogspot.com/2022/03/ldl-c.html	試験選択総死亡率および心血管アウトカムの減少におけるスタチンの有効性を検討した大規模ランダム化臨床試験で計画期間が年以上LDLC値の絶対的変化を報告しているもの。	2022-03-15 00:57:00
金融	ニッセイ基礎研究所	中国も建国100周年を迎える頃には現役2人で高齢者を支える社会に！	https://www.nli-research.co.jp/topics_detail1/id=70521?site=nli	そして、現役世代となる生産年齢人口歳は年の億万人をピークに減少し始め、年には億万人となり、全人口に占める比率はまで低下した図表。	2022-03-15 09:50:52
ニュース	@日本経済新聞 電子版	経済制裁で外貨準備の5割が凍結されたロシアが、国債のデフォルト（債務不履行）を強行する公算。外貨建て債券の返済をルーブルで支払う姿勢を崩さないまま、期日が迫っています。 https://t.co/R29q7B3uEE	https://twitter.com/nikkei/statuses/1503525163350044678	経済制裁で外貨準備の割が凍結されたロシアが、国債のデフォルト債務不履行を強行する公算。	2022-03-15 00:15:07
ニュース	@日本経済新聞 電子版	米、ウクライナへ武器供与継続　「複数の補給路ある」 https://t.co/GNomUI3mNc	https://twitter.com/nikkei/statuses/1503521768132476930	複数	2022-03-15 00:01:38
海外ニュース	Japan Times latest articles	Anti-war protester disrupts Russian state TV as Ukraine humanitarian crisis grows	https://www.japantimes.co.jp/news/2022/03/15/world/us-china-russia-ukraine-state-tv-protest/	Anti war protester disrupts Russian state TV as Ukraine humanitarian crisis growsIn Russia a rare anti war protest occurred in a studio during the main news program on state TV s Channel One which is the primary source	2022-03-15 09:38:26
ニュース	BBC News - Home	Ukraine war: A baby born under bombardment in Bucha	https://www.bbc.co.uk/news/world-europe-60739206?at_medium=RSS&at_campaign=KARANGA	assistance	2022-03-15 00:49:38
ニュース	BBC News - Home	Ukraine war: Kyiv terrain will slow Russian troops, say Ukraine generals	https://www.bbc.co.uk/news/world-europe-60745493?at_medium=RSS&at_campaign=KARANGA	missiles	2022-03-15 00:52:17
ニュース	BBC News - Home	March 4 Justice: Has anything changed for Australian women?	https://www.bbc.co.uk/news/world-australia-60732889?at_medium=RSS&at_campaign=KARANGA	massive	2022-03-15 00:08:15
ニュース	BBC News - Home	Science and tech: The app founder inspiring kids	https://www.bbc.co.uk/news/science-environment-60736708?at_medium=RSS&at_campaign=KARANGA	founder	2022-03-15 00:05:54
ニュース	BBC News - Home	How barista training opens doors for refugees	https://www.bbc.co.uk/news/business-60683648?at_medium=RSS&at_campaign=KARANGA	empowers	2022-03-15 00:02:43
ニュース	BBC News - Home	'Double tap' attacks in Yemen's civil war	https://www.bbc.co.uk/news/world-middle-east-60742504?at_medium=RSS&at_campaign=KARANGA	months	2022-03-15 00:03:55
ニュース	BBC News - Home	The popular apps aiming to tame the chaos of family life	https://www.bbc.co.uk/news/business-60213795?at_medium=RSS&at_campaign=KARANGA	covid	2022-03-15 00:22:57
ニュース	BBC News - Home	War in Ukraine: Why Vladimir Putin couldn't have trained fighters in Africa	https://www.bbc.co.uk/news/60705629?at_medium=RSS&at_campaign=KARANGA	ukraine	2022-03-15 00:40:37
ビジネス	ダイヤモンド・オンライン - 新着記事	ロシアを見捨てられない中国、仲介役に限界 - WSJ発	https://diamond.jp/articles/-/299133	限界	2022-03-15 09:16:00
北海道	北海道新聞	戦禍の影くらしにも　ウクライナ侵攻、子どもにどう説明	https://www.hokkaido-np.co.jp/article/656747/	説明	2022-03-15 09:17:48
北海道	北海道新聞	時短の飲食店悩ます「居座る客」　コロナ禍の札幌、トラブル相次ぐ	https://www.hokkaido-np.co.jp/article/656769/	営業時間	2022-03-15 09:10:05
北海道	北海道新聞	士幌町長選に前副町長の高木氏が届け出	https://www.hokkaido-np.co.jp/article/656920/	十勝管内	2022-03-15 09:08:00
北海道	北海道新聞	札幌の新規感染４００人前後の見通し	https://www.hokkaido-np.co.jp/article/656919/	新型コロナウイルス	2022-03-15 09:06:00
ビジネス	プレジデントオンライン	転売ヤーは新宿西口でホームレスに声をかける…人気商品を買い占める｢並び｣の仕事の中身 - 頼まれた仕事は､ポケモンカード､Switch､Supreme…	https://president.jp/articles/-/55483	kadokawa	2022-03-15 10:00:00
マーケティング	AdverTimes	タカラレーベン、DX戦略統括部を新設（22年4月1日付）	https://www.advertimes.com/20220315/article379171/	部長	2022-03-15 00:47:33
海外TECH	reddit	It’s beige trench coat season again	https://www.reddit.com/r/japanlife/comments/tec166/its_beige_trench_coat_season_again/	It s beige trench coat season againBeige trench coat season is officially here If you are a woman don t forget to wear yours or else you will be shunned submitted by u bellow whale to r japanlife link comments	2022-03-15 00:26:11