投稿時間:2022-04-06 09:37:26 RSSフィード2022-04-06 09:00 分まとめ(41件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	｢iOS 15.5 beta 1｣での新機能や変更点のまとめ	https://taisy0.com/2022/04/06/155477.html	apple	2022-04-05 23:52:23
IT	ITmedia 総合記事一覧	[ITmedia エグゼクティブ] 古米配合ブラシ　木製スプーン　プラごみ削減知恵絞る	https://mag.executive.itmedia.co.jp/executive/articles/2204/06/news070.html	itmedia	2022-04-06 08:11:00
TECH	Techable（テッカブル）	高品質の音を手軽に！ UGREEN発アンダー1万円のノイキャンイヤホン「HiTune X6」	https://techable.jp/archives/176506	hitunex	2022-04-05 23:00:11
Git	Gitタグが付けられた新着投稿 - Qiita	GitHubへのプッシュ時にfatal: remote origin already exists.と表示された場合の解決策	https://qiita.com/KazuyaInoue/items/b14669e2fae9dda78229	記事のとおりにコマンドを実行していけば、上記のエラーを解消しGitHubへpushできるはずです。	2022-04-06 08:41:28
技術ブログ	Developers.IO	【Xcode】ダークモードでの表示を確認する	https://dev.classmethod.jp/articles/angel-and-devil/	iphone	2022-04-05 23:00:38
海外TECH	DEV Community	Tracking My Progress With The Data Science Marathon (Week 2).	https://dev.to/seniorcitizen/tracking-my-progress-with-the-data-science-marathon-week-2-1cn7	Tracking My Progress With The Data Science Marathon Week Welcome to week a continuation of my progress series The previous week was quite a marathon and from that my guess is that this coming week will be more challenging but I m still prepared because Once you begin there s no quitting MondayThis is Day of the data science marathon I did an introduction to scikit learn with main focus on ensemble algorithms One thing that I always find fascinating is that every time I take a beginner approach towards learning I always encounter totally new concepts Today I learnt about the simplicity of the Scikit learn API design where I looked at the basic interfaces the submodules of Scikit learn i e Datasets sklearn datasetsPreprocessing sklearn preprocessingImpute sklearn imputeFeature Selection sklearn feature selectionLinear Models sklearn linear modelEnsemble Methods sklearn ensembleClustering sklearn clusterMatrix Decomposition sklearn decompositionManifold Learning sklearn manifoldMetrics sklearn metricsPipeline sklearn pipelineModel Selection sklearn model selectionEnsemble learning on the other hand is the process by which multiple models such as classifiers or experts are strategically generated and combined to solve a particular computational intelligence problem TuesdayFor day my focus was on XGBoost Algorithm which is an ensemble learning technique to build a strong classifier from several weak classifiers in series XGBoost stands for “Extreme Gradient Boosting and it is an optimized distributed gradient boosting library designed to be highly efficient flexible and portable to implement Machine Learning algorithms under the Gradient Boosting framework It provides a parallel tree boosting to solve many data science problems in a fast and accurate way Stay tuned for Wednesday and the rest of the week Hope you have a great and fruitful day For any errors observed in this article please mention them in the comments ‍	2022-04-05 23:47:00
海外TECH	DEV Community	Tips for Bootcamp Students	https://dev.to/mkienbus/tips-for-bootcamp-students-20m8	Tips for Bootcamp Students IntroductionI recently graduated from Flatiron School s Software Engineering course and would like to pass on some advice I learned firsthand during my learning experience to any current or future students While I attended Flatiron School this advice is applicable to students attending any program A lot of the advice I can give is focused on students learning online but some of it is universal to learning to program in general Note Everybody learns differently These tips are things I found helpful if they don t work for you then try something else Background InformationI chose to enroll in their flexible online program which was online and stretched over a period of ten months excluding one month of pre course work I went with this option because I was working full time and could not afford to quit work to attend a full time in person course Students were placed into a cohort of about fifteen students with one instructor Each week the cohort had two hour long class sessions together with the instructor Then once a week you and two other students had an hour long session with the instructor to go over any problems or topics the few of you wanted to discuss You were also able to schedule one on one time with your instructor as often as he she was available The course was broken into five phases Each phase consisted of a topic language to learn a project to be completed and assessed and a live coding challenge to be graded The phases built on each other and by phase five we were using everything we had learned Dedicate a workspace Set aside a physical workspaceMy wife and I lived in a single bedroom apartment with our newborn son taking up more space than I could have ever imagined an infant would When I went through this course we did not have a lot of space to spare At the start of the course I was just plopping my laptop on the kitchen table using it on the couch or wherever I thought I would want to study and work It was hard to really get into a work mindset and be able to focus on learning difficult concepts much less put them into practice My advice to you is to dedicate a specific workspace that nothing else in the house has claim over You don t need a dedicated home office room to accomplish this it can be a specific corner of the kitchen table a foldable table you set up in the basement or anything That way when you sit down and login to your computer your mind knows its time to focus and work because there is nothing else that is done in this spot of the house apartment While I did take my laptop with me for travels I was never quite as productive as when I was at my desk Time management Set aside time to workMuch like you set aside a physical space to work in set aside time that you work during Even with my wife and I both being back at work with a newborn baby I was able to set aside time to work While the class meeting times are set in stone you need to set time aside to learn and complete course material on your own There will be times during your curriculum that are slow paced and some that are fast paced For me I did most of my course work on my days off work and for two hours immediately after getting home from work before I got too tired It is a sacrifice and can be mentally draining but know that it is temporary and it helps you in the long term Connect with students and utilize your instructor Utilize the resources you are paying forDon t be shy Flatiron School utilized Slack to facilitate communication within the cohort and with the instructor If you are stuck on topic or problem message your cohort and see if anyone else is also stuck Everyone is in it together and your question is never beneath the group Topics you learned in the first month you might forget in a few months If you can t figure out your problem through research reach out for help And don t feel hesitant to schedule one on one meetings with your instructor They are paid to be available to you you are not inconveniencing them Do not get fixated on one problem Don t waste timeI didn t really learn this lesson until I was working on my final project I was determined to implement a new concept and library on my frontend for my final project When I started trying to use these new tools I got stuck I utilized online resources peers and my instructor to no avail The library was new to my instructor so we were more or less learning it together through our meetings instead of me more speedily implementing it into my project I did not work on other areas of my project while I was trying to figure out this one concept Bottom line I wasted two weeks on my final project on getting one concept to work This put me behind for the rest of my project and I was rushed for the remainder of the course If you are stuck on one topic in a project work on the topics you do understand You can build out other aspects of your program and come back to the problem area later Conclusion Those are my four biggest takeaways from remote learning These are pieces of advice I will take with me into my new career and I hope they help you during your studies	2022-04-05 23:23:24
海外TECH	DEV Community	Stop Writing DRY Code	https://dev.to/dbanty/stop-writing-dry-code-51em	Stop Writing DRY CodeCover photo created by Jazlyn Borkowski DRY is an acronym introduced seemingly universally to software engineers early in their education For example when I searched software engineering best practices of the top results mentioned DRY It stands for Don t Repeat Yourself and is one of the worst things you can teach a fledgling developer If you take nothing else away from this post take this DRY should never be a goal when writing code It is not an indicator of code quality it is at best a tool to be applied in some circumstances Code that does not repeat itself is not inherently better than code that does so DRY should never appear as a recommendation in your code reviews MOISTCode is a bit like cake A dry cake is brittle and likely crumble when you touch it Likewise DRY codeーcode that has no repetitionーwill resist extension and alteration By combining two implementations into a single one you bind them together making it so you can t change one without changing both On the other hand a wet cake will fall apart not holding its structure In software WET usually means something to the effect of write every time ーit s the opposite of DRY in that you constantly repeat yourself If your code is WET you can change one piece without breaking any others However two pieces of information that should be the same can easily fall out of sync The best cake and code is MOISTー Maintain One Indisputable Source of Truth Rather than being a hard and fast rule about writing code it gives you a reason why to refactor code MOIST gives you the best of both worlds by increasing rigidity to prevent bugs and keeping flexibility wherever possible As with all things balance is vital Let s look at an example where keeping your code MOIST is essential We re writing a program that handles semantic versioning for projects It has two commands auto reads your commit history and generates a new version The manual command takes a rule name from the user and bumps the version according to that rule A first attempt might look like this fn auto history amp Commit let mut version Version get current let mut major false let mut minor false let mut patch false for commit in history if commit message contains BREAKING CHANGE major true version major version minor version patch break else if commit message contains feat amp amp minor minor true version minor version patch else if commit message contains fix amp amp patch amp amp minor patch true version patch write version version fn manual rule String let mut version Version get current if rule major version major version minor version patch else if rule minor version minor version patch else if rule patch version patch else panic Unknown rule rule write version version Here we re maintaining two different implementations for applying a semantic rule to a semantic versionーtwo distinct truths about the rules Unfortunately this separation could easily lead to disparate behaviors between the two commands confusing users So let s maintain only a single source of truth for how to bump that version number fn auto history amp Commit let mut rule patch for commit in history if commit message contains BREAKING CHANGE rule major break else if commit message contains feat rule minor bump version rule fn bump version rule String let mut version Version get current if rule major version major version minor version patch else if rule minor version minor version patch else if rule patch version patch write version version fn manual rule String if rule major amp amp rule minor amp amp rule patch panic Unknown rule rule bump rule rule There all good right Well not entirely Our new bump version function is the arbiter of applying rules to versionsーbut now we have three different places those rules are defined If we want to add a prerelease rule we d have to remember to change every location separately which could easily cause a bug So again we ll maintain only a single source of truth enum Rule Major Minor Patch fn auto history amp Commit let mut rule Rule Patch for commit in history if commit message contains BREAKING CHANGE rule Rule Major break else if commit message contains feat rule Rule Minor bump version rule fn bump version rule Rule let mut version Version get current match rule Rule Major gt version major version minor version patch Rule Minor gt version minor version patch Rule Patch gt version patch write version version fn manual rule String if rule major bump version Rule Major else if rule minor bump version Rule Minor else if rule patch bump version Rule Patch else panic Unknown rule rule There we go one source of truth for the rules how to apply them to a semantic version how to generate them from commit messages and how to interpret a user s input But I see more repetition What if we changed to a single commit message contains statement with a map from the keywords to the rule they represent When considering any refactor it s crucial to think about the goal In the case of MOIST we have to ask ourselves what is the truth we re trying to protect Is it true that breaking changes and features should always be determined the same way No In fact this implementation is not consistent with Semantic Versioning yet and the two branches will eventually diverge further Coupling these two pieces of information would increase rigidity without protecting a single source of truth so we should not combine them What about the user input Surely we should factor out the string to rule map and only have a single function call location Let s try the same testーwhat is the single truth we re trying to protect Is it every rule should be determined by only a single string That feels more like an implementation detail In fact if we add a prerelease rule we ll need some additional info to select a prefix This change feels like it would be a reduction in repetition without a clear goalーit would bind the separate rules together making it harder to change just one without an obvious benefit MOIST can get subjective and be a bit mushyーas can any coding practice but it tries to draw a line between harmful repetition and benign code The key to successfully applying any best practice is understanding the true goal and always keeping that in mind RAINYCake aside there are a couple more worthwhile goals semi related to DRY I ll attempt to shoehorn them into more acronyms semi antonymic to DRY Reusable Abstractions Ideally Not Yours is another way of saying don t build when you can buy It is far more efficient for one person to solve a problem and share that solution than for hundreds of people to solve it independently This practice is applicable at many scales but achieves another one of the fundamental goals that DRY tries to stand for The best example of this is the open source community Rather than re do work that someone else has done you can build on top of what exists Likewise you can share solutions to problems you ve faced so that others don t need to waste future effortーand you multiply the impact of your work RAINY is like taking don t repeat yourself and applying it across our entire community More like let s not repeat ourselves As with everything there is a balance to be struck We don t want a MONSOON where Maintaining Open source is a Nuisance So Others Often Neglect it Basically as a consumer installing dependencies is a pain and keeping them up to date is even more of a pain you should be using Renovate to mitigate that though On the other side staying on top of issues and pull requests as a maintainer is burdensome and often thankless This level of effort on both sides can lead to relatively simple bugs never being fixed Balancing this is difficult and I think a conversation about the good and bad of open source can go far beyond this articleーso I m going to leave it there However if you d like a post titled either Do You Really Need that Dependency or When to Open Source it let me know FRESH Functions Read Easier in Short Hunks Yesーmy acronyms are getting more and more unhinged and also straying further from DRY I m not sorry Often reviewers use DRY as a code word for make that into a function Code readability is vital for maintainability and an easy way to improve readability is to split large functions into several smaller ones This way a reader can get a high level understanding of what the code is doing just by reading the function names in orderーand they should read a bit like prose Of course there s a tradeoff to be made here a function call is not always easier to read than the statements that make it up and calling functions can often have performance penalties Still as a goal refactoring to readability is far more valuable than refactoring simply to reduce duplication A TestHere s a set of questions I suggest you ask yourself next time you re wondering if you should be repeating yourself or not Are there two separate sources of truth for a single concept If yes try to unify them Is this code solving a general problem or something specific to me my work If it can be generalized consider publishing a reusable module whether open source or in a private corporate location Can I read through this code and understand what it s doing without stopping to inspect it For this one ideally have someone who didn t write the code answer the question in a code review If it s hard to parse for humans consider abstracting away details that aren t needed like with functions Hopefully all of my acronymic nonsense has provided you with enough alternatives to DRY that you never use it again Remember not repeating yourself is not a valuable outcome of refactoring Instead try keeping a goal in mind like improving correctness benefitting the community or making the code easier to read Now go enjoy some cake you ve earned it Was this post super helpful to you Tip me on GitHub Patreon or Ko Fi Have a question or comment about this post Leave it in the discussion thread on GitHub Want to be notified of future posts Watch releases in the GitHub repo or follow me on Twitter Have an idea or request for a future blog topic Drop it in the GitHub discussions under ideas	2022-04-05 23:14:24
海外TECH	DEV Community	O Básico: JWT - JSON Web Token	https://dev.to/gabrielhsilvestre/o-basico-jwt-json-web-token-2akc	O Básico JWT JSON Web Token JWT O que é Éum token gerado a partir de dados pessoais esse que pode ser trafegado entre aplicações ao se realizar requisições a APIs As informações contidas no token são públicas e podem ser lidas por qual quer um que o possua porém háum mecanismo de segurança que faz com que somente quem tenha a senha possa modificá lo O que faz De forma geral os tokens podem ser usados para diversas finalidades afinal eles são somente uma estrutura segura para o trafego de informações porém seu uso mais comum épara autorização de usuários em diversos serviços Estrutura HeaderO Header do token iráconter duas propriedades alg para definir o algoritmo de hash e typ para definir o tipo de token no nosso caso seráJWT alg algoritmo de hash typ JWT alg HS typ JWT PayloadO payload iráconter os dados do usuário esses que não devem ser dados sensíveis CPF cartão endereço etc apenas o essencial para dar ao usuário a autorização necessária para navegar e interagir com a aplicação username Big John name John Doe admin false isPrime true SignatureÉa assinatura utilizada para validar o token dessa forma conseguimos verificar se o token recebido do cliente éigual ao que enviamos anteriormente caso não sejam iguais o token éconsiderado inválido essa parte éa concatenação criptografada do Header Payload e serágerada para nós pelo JWT Usando o JWT InstalandoAntes de começarmos a implementar o JWT precisamos instalar a biblioteca que irágerar e validar os tokens para isso usamos o comando npm i jsonwebtokennpm i D types jsonwebtoken caso usar TypeScript seránecessário instalar os pacotes a parte ConfigurandoTendo instalado e importado o JWT para nosso arquivo iremos configurá lo Nas configurações podemos definir o algoritmo de hash o período de validade entre outas opções As configurações consistem em um Objeto JS com algumas chaves préexistentes Consultar a documentação para as chaves const jwtConfig expiresIn d lt Faz com que o token expire depois de dias algorithm HS lt Indica o algoritmo de hash HS para criptografia CriandoApós termos definido nossas configurações iremos chamar o método sign para realmente criarmos nosso token esse método iráreceber os dados o secret e as configurações como argumentos const jwt require jsonwebtoken lt importação do jwtconst secret meuSuperSegredo Considerações logo abaixo const user email gabriel gabriel com username Roxo lt usuário fake para demonstraçãojwt sign data user secret jwtConfig lt data éa chave padrão do JWT para passarmos os dados O secret deve ser armazenado em variáveis de ambiente para maior segurança da aplicação caso o declaremos hardcoded estaremos deixando nossa aplicação vulnerável e nossos tokens usuários em risco ValidandoPara validarmos um token basta chamarmos o método verify passando o token em questão e o secret utilizado como argumentos Não se preocupe em referenciar o token criado anteriormente pois a biblioteca do JWT faz isso para nós Caso o token seja inválido ou tenha expirado o próprio método irános retornar um erro logo precisamos trabalhar essa validação dentro de um bloco try catch ou algo equivalente Assim como na criação na validação do token precisamos importar o jwt e o secret No caso desse exemplo seria necessário criar uma outra constante para definir o secret NÃO RECOMENDADO jwt verify token secret	2022-04-05 23:12:37
Apple	AppleInsider - Frontpage News	Over 8 million customers affected in Cash App data breach	https://appleinsider.com/articles/22/04/05/over-8-million-customers-affected-in-cash-app-data-breach?utm_medium=rss	Over million customers affected in Cash App data breachOn Monday financial services and digital payment company Block Inc filed a report stating that the company had suffered a data breach when a former Cash App employee accessed customer records without permission The breach occurred on December when the former employee accessed and downloaded customer reports within the company s database Block the parent company of Cash App submitted a filing to the US Securities and Exchange Commission on April publicly acknowledging the breach Read more	2022-04-05 23:11:00
金融	JPX マーケットニュース	[OSE]国債先物における受渡適格銘柄及び交換比率一覧表の更新	https://www.jpx.co.jp/derivatives/products/jgb/jgb-futures/02.html	銘柄	2022-04-06 09:00:00
金融	金融総合：経済レポート一覧	先行指標との付き合い方は難しい：Market Flash	http://www3.keizaireport.com/report.php/RID/491162/?rss	marketflash	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	対ロシア金融制裁で注目されるCIPSとは	http://www3.keizaireport.com/report.php/RID/491165/?rss	大和総研	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	FX Daily（4月4日）～ドル円、122円台後半で推移	http://www3.keizaireport.com/report.php/RID/491169/?rss	fxdaily	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	【概要説明】通貨及び金融の調節に関する報告書 衆議院財務金融委員会における概要説明 日本銀行総裁 黒田東彦	http://www3.keizaireport.com/report.php/RID/491170/?rss	日本銀行	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	欧州大手保険グループの2021年末SCR比率の状況について（２）～ソルベンシーIIに基づく数値結果報告（比率の推移分析と感応度の推移）：保険・年金フォーカス	http://www3.keizaireport.com/report.php/RID/491172/?rss	結果	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	年金改革ウォッチ 2022年4月号～この10年で厚生年金加入者は577万人増、国民年金(1号・3号計)は700万人減	http://www3.keizaireport.com/report.php/RID/491173/?rss	厚生年金	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	プライム市場がスタート：ニッセイ年金ストラテジー	http://www3.keizaireport.com/report.php/RID/491174/?rss	研究所	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	日銀の金融政策正常化時にとるべき国内債券のアクティブ戦略：ニッセイ年金ストラテジー	http://www3.keizaireport.com/report.php/RID/491175/?rss	金融政策	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	企業型確定拠出年金の制度設計と商品選択：ニッセイ年金ストラテジー	http://www3.keizaireport.com/report.php/RID/491176/?rss	確定拠出年金	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	増える外国資本、長期投資の定着で優良不動産の取得はより困難に：ニッセイ年金ストラテジー	http://www3.keizaireport.com/report.php/RID/491177/?rss	外国資本	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	米国政府がロシア国債の償還・利払いを阻止との報道。ロシアはデフォルトか：木内登英のGlobal Economy ＆ Policy Insight	http://www3.keizaireport.com/report.php/RID/491178/?rss	lobaleconomypolicyinsight	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	Thought Leaderに訊く：金融情報システムの高度化対応～語り手 公益財団法人金融情報システムセンター（FISC） 常務理事 照内太郎氏	http://www3.keizaireport.com/report.php/RID/491180/?rss	thoughtleader	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	日本経済に強まる逆風と注目を集める日銀金融政策：金融市場	http://www3.keizaireport.com/report.php/RID/491184/?rss	日本経済	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	オペレーショナルレジリエンス再考：リスク管理	http://www3.keizaireport.com/report.php/RID/491185/?rss	野村総合研究所	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	変化するCX向上の優先課題：リテールビジネス	http://www3.keizaireport.com/report.php/RID/491186/?rss	優先課題	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	若年層に広がる資産運用とアドバイスニーズ：リテールビジネス	http://www3.keizaireport.com/report.php/RID/491187/?rss	資産運用	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	フィッシング詐欺対策で見直されるユーザー認証：セキュリティ	http://www3.keizaireport.com/report.php/RID/491188/?rss	野村総合研究所	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	保険会社の新規事業創出に必要なプロダクトマネジメント：保険の2030年アジェンダ	http://www3.keizaireport.com/report.php/RID/491189/?rss	保険会社	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	内外金利・為替見通し No.2022-01 ～日銀は緩和策を継続する見通しだが、早晩、インフレ率上昇に直面する公算大	http://www3.keizaireport.com/report.php/RID/491191/?rss	中小企業	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	不動産ESG：社会（S）を評価するガイダンス作成に向け、国土交通省が「中間とりまとめ」を公表：リサーチカフェ	http://www3.keizaireport.com/report.php/RID/491209/?rss	三井住友トラスト	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	【注目検索キーワード】グリーンインフラ	http://search.keizaireport.com/search.php/-/keyword=グリーンインフラ/?rss	検索キーワード	2022-04-06 00:00:00
金融	金融総合：経済レポート一覧	【お薦め書籍】5秒でチェック、すぐに使える! 2行でわかるサクサク仕事ノート	https://www.amazon.co.jp/exec/obidos/ASIN/4046053631/keizaireport-22/	結集	2022-04-06 00:00:00
海外ニュース	Japan Times latest articles	Elon Musk joins Twitter’s board, pitching ideas big and small	https://www.japantimes.co.jp/news/2022/04/06/business/corporate-business/elon-musk-twitter-board/	Elon Musk joins Twitter s board pitching ideas big and smallThe move has implications for a social network where world leaders lawmakers celebrities and more than million users conduct their daily public discourse	2022-04-06 08:10:53
ニュース	BBC News - Home	The Papers: Zelensky's impassioned UN speech and Putin's 'Dud's Army'	https://www.bbc.co.uk/news/blogs-the-papers-61004952?at_medium=RSS&at_campaign=KARANGA	focus	2022-04-05 23:19:26
GCP	Google Cloud Platform Japan 公式ブログ	くら寿司：GKE や Edge TPU などを駆使して来店から会計までを完全自動化し、新しい生活様式のためのサービスを提供	https://cloud.google.com/blog/ja/topics/customers/kurasushi-gke-edge-tpu/	すでにを超えるシステムを自社で開発し、その多くがGoogleCloud上で稼働しています。	2022-04-06 01:00:00
北海道	北海道新聞	「信じてサイン出したんだから」　新庄監督、清宮や清水にもどかしさ　采配の思い明かす	https://www.hokkaido-np.co.jp/article/666150/	試合後	2022-04-06 08:08:50
北海道	北海道新聞	オバマ氏、バイデン氏を応援　５年ぶりホワイトハウスに	https://www.hokkaido-np.co.jp/article/666193/	米大統領	2022-04-06 08:06:00
北海道	北海道新聞	機構が電子機器の使用許可へ　大リーグのサイン盗み対策	https://www.hokkaido-np.co.jp/article/666192/	大リーグ	2022-04-06 08:03:00
ビジネス	東洋経済オンライン	国の導入遅い｢子の死因究明｣に山梨が力入れる訳 知事はなぜ｢県の重要政策｣と位置づけたのか | 政策 | 東洋経済オンライン	https://toyokeizai.net/articles/-/541240?utm_source=rss&utm_medium=http&utm_campaign=link_back	小さな命	2022-04-06 08:30:00
GCP	Cloud Blog JA	くら寿司：GKE や Edge TPU などを駆使して来店から会計までを完全自動化し、新しい生活様式のためのサービスを提供	https://cloud.google.com/blog/ja/topics/customers/kurasushi-gke-edge-tpu/	すでにを超えるシステムを自社で開発し、その多くがGoogleCloud上で稼働しています。	2022-04-06 01:00:00