投稿時間:2022-05-09 17:38:54 RSSフィード2022-05-09 17:00 分まとめ(46件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	住信SBIネット銀行、Apple Payで対象のデビットカード利用で500円相当のポイントを贈呈するキャンペーンを開始	https://taisy0.com/2022/05/09/156711.html	applepay	2022-05-09 07:52:34
IT	気になる、記になる…	Amazon、ahamo・LINEMO・povo2.0を取扱開始	https://taisy0.com/2022/05/09/156708.html	ahamo	2022-05-09 07:43:52
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] ポッカサッポロ、沖縄のアイスとコラボした「がぶ飲みブルーウェーブフロート」発売	https://www.itmedia.co.jp/business/articles/2205/09/news133.html	itmedia	2022-05-09 16:50:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] TourBox、左手操作向け多機能デバイス「TourBox Elite」の国内販売を発表	https://www.itmedia.co.jp/pcuser/articles/2205/09/news141.html	bluetooth	2022-05-09 16:44:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] ローソン、店内キッチンで調理をする「まちかど厨房」好調　前年同期比で4割伸長	https://www.itmedia.co.jp/business/articles/2205/09/news134.html	itmedia	2022-05-09 16:16:00
IT	ITmedia 総合記事一覧	[ITmedia News] 映画「シン・ウルトラマン」とコラボしたソニーのスマートウォッチ、1000台限定で販売	https://www.itmedia.co.jp/news/articles/2205/09/news131.html	itmedia	2022-05-09 16:11:00
python	Pythonタグが付けられた新着投稿 - Qiita	Python学習記録_6日目.統計学入門・matplotlib・決定木	https://qiita.com/kou6064/items/2a8a6a1752811a3fe2de	kaggle	2022-05-09 16:22:49
python	Pythonタグが付けられた新着投稿 - Qiita	local環境でPyodideから自作のPython Packageを使う	https://qiita.com/pycetra/items/5123a2992697a8de53cf	cpython	2022-05-09 16:03:25
Ruby	Rubyタグが付けられた新着投稿 - Qiita	【Rails】actionmeilerのsubjectをi18nで日本語化する	https://qiita.com/tomoronn3/items/ad8a33aac08010768dbe	actionmeiler	2022-05-09 16:33:55
Azure	Azureタグが付けられた新着投稿 - Qiita	Azure Blob Storage ユーザー委任SASを使う	https://qiita.com/shingo_kawahara/items/6752a89ad814f47e318e	azureblobstorage	2022-05-09 16:10:55
Ruby	Railsタグが付けられた新着投稿 - Qiita	【Rails】actionmeilerのsubjectをi18nで日本語化する	https://qiita.com/tomoronn3/items/ad8a33aac08010768dbe	actionmeiler	2022-05-09 16:33:55
技術ブログ	Developers.IO	Amazon EFS のスループットモードを変更した際にダウンタイムは発生しますか？	https://dev.classmethod.jp/articles/tsnote-efs-throughputmode-downtime-001/	amazonefs	2022-05-09 07:39:51
技術ブログ	Developers.IO	TerraformでAWSアカウントを作るのは簡単だけど削除はひと手間かかったのは昔の話	https://dev.classmethod.jp/articles/now-you-can-close-accounts-easily-with-terraform/	awsorganizations	2022-05-09 07:08:11
技術ブログ	Developers.IO	Lambda から Transcribe の StartCallAnalyticsJob を実行する際に必要な IAM ロールについて	https://dev.classmethod.jp/articles/about-the-iam-role-required-to-execute-transcribes-startcallanalyticsjob-from-lambda/	lambda	2022-05-09 07:03:32
海外TECH	DEV Community	Building a GraphQL API with Graphene, Flask And SQLAlchemy	https://dev.to/jod35/building-a-graphql-api-with-graphene-flask-and-sqlalchemy-4c5p	sqlalchemy	2022-05-09 07:40:42
海外TECH	DEV Community	Modernize Legacy Code in Production – Rebuild your Airplane Midflight without Crashing	https://dev.to/codenameone/modernize-legacy-code-in-production-rebuild-your-airplane-midflight-without-crashing-49ka	Modernize Legacy Code in Production Rebuild your Airplane Midflight without CrashingI spent over a decade as a consultant working for dozens of companies in many fields and pursuits The diversity of each code base is tremendous This article will try to define general rules for modernizing legacy code that would hopefully apply to all But it comes from the angle of a Java developer When writing this my primary focus is on updating an old Java era style JEE code to the more modern Spring Boot Jakarta EE code However I don t want to go into the code and try to keep this generic I discuss COBOL and similar legacy systems too Most of the overarching guidelines should work for migrating any other type of codebase too Rewriting a project isn t an immense challenge mostly however doing it while users are actively banging against the existing system without service disruption That requires a lot of planning and coordination Why Modernize I don t think we should update projects for the sake of the “latest and greatest There s a reason common legacy systems like COBOL are still used Valuable code doesn t lose its shine just because of age There s a lot to be said for “code that works Especially if it was built by hundreds of developers decades ago There s a lot of hidden business logic model knowledge in there…However maintenance can often become the bottleneck You might need to add features making the process untenable It s hard to find something in millions of lines of code The ability to leverage newer capabilities might be the final deciding factor It might be possible to create a similar project without the same complexities thanks to newer frameworks and tools We shouldn t take a decision to overhaul existing code that s in production lightly You need to create a plan evaluate the risks and have a way to back out Other reasons include security scalability end of life to systems we rely on lack of skilled engineers etc You usually shouldn t migrate for better tooling but better observability orchestration etc Are a tremendous benefit Modernization gives you the opportunity to rethink the original system design However this is a risky proposition as it makes it pretty easy to introduce subtle behavioral differences ChallengesBefore we head to preparations there are several deep challenges we need to review and mitigate Access to Legacy Source CodeSometimes the source code of the legacy codebase is no longer workable This might mean we can t add even basic features functionality to the original project This can happen because of many reasons legal or technical and would make migration harder Unfamiliar code is an immense problem and would make the migration challenging although possible It s very common to expose internal calls in the legacy system to enable smooth migration E g we can provide fallback capabilities by checking against the legacy system An old product I worked on had a custom in house authentication To keep compatibility during migration we used a dedicated web service If user authentication failed on the current server the system checked against the old server to provide a “seamless experience This is important during the migration phase but can t always work If we don t have access to the legacy code tools such as scraping might be the only recourse to get perfect backwards compatibility during the migration period Sometimes the source is no longer available or was lost This makes preparation harder Inability to Isolate Legacy SystemIn order to analyze the legacy system we need the ability to run it in isolation so we can test it and verify its behaviors This is a common and important practice but isn t always possible E g a COBOL codebase running on dedicated hardware or operating system It might be difficult to isolate such an environment This is probably the biggest problem challenge you can face Sometimes an external contractor with domain expertise can help here If this is the case it s worth every penny Another workaround is to set up a tenant for testing E g if a system manages payroll set up a fake employee for testing and perform the tasks discussed below against production This is an enormous danger and a problem so this situation is far from ideal and we should take it only if no other option exists Odd Formats and Custom StoresSome legacy systems might rely on deeply historical approaches to coding A great example is COBOL In it they stored numbers based on their form and are closer to BCD Java s BigDecimal is the closest example This isn t bad For financial systems this is actually the right way to go But it might introduce incompatibilities when processing numeric data that might prevent the systems from running in parallel Worse COBOL has a complex file storage solution that isn t a standard SQL database Moving away from something like that or even some niche newer systems can be challenging Thankfully there are solutions but they might limit the practicality of running both the legacy and new product in parallel PreparationBefore we need to even consider an endeavor of this type we need to evaluate and prepare for the migration The migration will be painful regardless of what you do but this stage lets you shrink the size of the band aid you need to pull off There are many general rules and setups you need to follow before undergoing a code migration Each one of these is something you need to be deeply familiar with Feature ExtractionWhen we have a long running legacy system it s almost impossible to keep track of every feature it has and the role it plays in the final product There are documents but they are hard to read and go through when reviewing Issue trackers are great for followup but they aren t great maps Discovering the features in the system and the ones that are “actually used is problematic Especially when we want to focus on minutiae We want every small detail This isn t always possible but if you can use observability tools to indicate what s used it would help very much Migrating something that isn t used is frustrating and we d want to avoid it if possible This isn t always practical as most observability tools that provide very fine grained details are designed for newer platforms e g Java Python Node etc But if you have such a platform such as an old JEE project Using a tool like Lightrun and placing a counter on a specific line can tell you what s used and what probably isn t I discuss this further below I often use a spreadsheet where we list each feature and minor behavior These spreadsheets can be huge and we might divide them based on sub modules This is a process that can take weeks Going over the code documentation and usage Then iterating with users of the application to verify that we didn t miss an important feature Cutting corners is easy at this stage You might pay for them later There were times I assigned this requirement to a junior software developer without properly reviewing the output I ended up regretting that as there were cases where we missed nuances within the documentation or code Compliance TestsThis is the most important aspect for a migration process While unit tests are good compliance and integration tests are crucial for a migration process We need feature extraction for compliance We need to go over every feature and behavior of the legacy system and write a generic test that verifies this behavior This is important both to verify our understanding of the code and that the documentation is indeed correct Once we have compliance tests that verify the existing legacy system we can use them to test the compatibility of the new codebase The fundamental challenge is writing code that you can run against two completely different systems E g If you intend to change the user interface adapting these tests would be challenging I would recommend writing the tests using an external tool maybe even using different programming languages This encourages you to think of external interfaces instead of language platform specific issues It also helps in discovering “weird issues E g We had some incompatibilities because of minute differences in the HTTP protocol implementation between a new and legacy system I also suggest using a completely separate “thin adapter for the UI differences The tests themselves must be identical when running against the legacy and the current codebase The process we take for test authoring is to open an issue within the issue tracker for every feature behavior in the spreadsheet from the previous step Once this is done we color the spreadsheet row in yellow Once we integrate a test and the issue is closed we color the row green Notice that we still need to test elements in isolation with unit tests The compliance tests help verify compatibility Unit tests check quality and also complete much faster which is important to productivity Code CoverageCode coverage tools might not be available for your legacy system However if they are you need to use them One of the best ways to verify that your compliance tests are extensive enough is through these tools You need to do code reviews on every coverage report We should validate every line or statement that isn t covered to make sure there s no hidden functionality that we missed Recording and BackupIf it s possible record network requests to the current server for testing You can use a backup of the current database and the recorded requests to create an integration test of “real world usage for the new version Use live data as much as possible during development to prevent surprises in production This might not be tenable Your live database might be access restricted or it might be too big for usage during development There s obviously privacy and security issues related to recording network traffic so this is only applicable when it can actually be done ScaleOne of the great things about migrating an existing project is that we have a perfect sense of scale We know the traffic We know the amount of data and we understand the business constraints What we don t know is whether the new system can handle the peak load througput we require We need to extract these details and create stress tests for the critical portions of the system We need to verify performance ideally compare it to the legacy to make sure we aren t going back in terms of performance TargetsWhich parts should we migrate and in what way What should we target first and how should we prioritize this work Authentication and AuthorizationMany older systems embed the authorization modules as part of a monolith process This will make your migration challenging regardless of the strategy you take Migration is also a great opportunity to refresh these old concepts and introduce a more secure scalable approach for authorization A common strategy in cases like this is to send a user to “sign up again or “migrate their accounts when they need to use the new system This is a tedious process for users and will trigger a lot of support issues e g “I tried password reset and it didn t work These sorts of failures can happen when a user in the old system didn t perform the migration and tries to reset the password on the new system There are workarounds such as explicitly detecting a specific case such as this and redirecting to the “migration process seamlessly But friction is to be expected at this point However the benefit of separating authentication and authorization will help in future migrations and modularity User details in the shared database is normally one of the hardest things to migrate DatabaseWhen dealing with the legacy system we can implement the new version on top of the existing database This is a common approach and has some advantages Instant migration this is probably the biggest advantage All the data is already in the new system with zero downtimeSimple this is probably one of the easiest approaches to migration and you can use existing “real world data to test the new system before going liveThere are also a few serious disadvantages Data pollution the new system might insert problematic data and break the legacy system making reverting impossible If you intend to provide a staged migration where both the old and new systems are running in parallel this might be an issueCache issues if both systems run in parallel caching might cause them to behave inconsistentlyPersisting limits this carries over limitations of the old system into the new systemIf the storage system is modern enough and powerful enough the approach of migrating the data in this way makes sense It removes or at least postpones a problematic part of the migration process CachingThe following three tips are at the root of application performance If you get them right your apps will be fast CachingCachingCachingThat s it Yet very few developers use enough caching That s because proper caching can be very complicated and can break the single source of knowledge principle It also makes migrations challenging as mentioned in the above section Disabling caching during migration might not be a realistic option but reducing retention might mitigate some issues StrategyThere are several ways we can address a large scale migration We can look at the “big picture in a migration e g Monolith to Microservices But more often than not there are more nuanced distinctions during the process I ll skip the obvious “complete rewrite where we instantly replace the old product with the new one I think it s pretty obvious and we all understand the risks implications Module by ModuleIf you can pick this strategy and slowly replace individual pieces of the legacy code with new modules then this is the ideal way to go This is also one of the biggest selling points behind microservices This approach can work well if there s still a team that manages and updates the legacy code If one doesn t exist you might have a serious problem with this approach Concurrent DeploymentThis can work for a shared database deployment We can deploy the new product to a separate server with both products using the same database as mentioned above There are many challenges with this approach but I picked it often as it s probably the simplest one to start with Since the old product is still available there s a mitigation workaround for existing users It s often recommended to plan downtime for the legacy servers to force existing users to migrate Otherwise in this scenario you might end up with users who refuse to move to the new product Hidden DeploymentIn this strategy we hide the existing product from the public and set up the new system in its place In order to ease migration the new product queries the old product for missing information E g if a user tried to login and didn t register in the system the code can query the legacy system to migrate the user seamlessly This is challenging and ideally requires some changes to the legacy code The enormous benefit is that we can migrate the database while keeping compatibility and without migrating all the data in one fell swoop A major downside is that this might perpetuate the legacy code s existence It might work against our development goals as a result of that ImplementationYou finished writing the code We re ready to pull the trigger and do the migration…Now we need to update the users that the migration is going to take place You don t want an angry customer complaining that something suddenly stopped working RehearsalIf possible perform a dry run and prepare a script for the migration process When I say script I don t mean code I mean a script of responsibilities and tasks that need to be performed We need to verify that everything works as the migration completes If something is broken there needs to be a script to undo everything You re better off retreating to redeploy another day I d rather have a migration that fails early that we can “walk back from than having something “half baked in production Who In my opinion you should use a smaller team for the actual deployment of the migrated software Too many people can create confusion You need the following personnel on board IT OPS to handle the deployment and reverting if necessarySupport to field user questions and issues Raise flags in case a user reports a critical errorDevelopers to figure out if there are deployment issues related to the codeManager we need someone with instant decision making authority No one wants to pull a deployment We need someone who understands what s at stake for the companyThere s a tendency to make a code fix to get the migration through This works OK for smaller startups and I m pretty guilty of that myself But if you re working at scale there s no way to do it A code change done “on the spot can t pass the tests and might introduce terrible problems It s probably a bad idea When The axiom “don t deploy on a Friday might be a mistake for this case I find Fridays are a great migration period when I m willing to sacrifice a weekend Obviously I m not advocating forcing people to work the weekend But if there s interest in doing this in exchange for vacation time then low traffic days are the ideal time for making major changes If you work in multiple time zones developers in the least active time zone might be best to handle the migration I would suggest having teams in all time zones to keep track of any possible fallout Agility in these situations is crucial Responding to changes quickly can make the difference between reverting a deployment and soldering on Staged RolloutWith small updates we can stage our releases and push the update to a subset of users Unfortunately when we do a major change I find it more of a hindrance The source of errors becomes harder to distinguish if you have both systems running Both systems need to run concurrently and it might cause additional friction Post MigrationA couple of weeks had passed things calmed down and the migration worked Eventually Now what Retirement PlanAs part of the migration we brought with us a large set of features from legacy We probably need some of them while some others might not be necessary After finishing the deployment we need to decide on the retirement plan Which features that came from legacy should be retired and how We can easily see if we use a specific method or if it s unused in the code But are the users using a specific line of code A specific feature For that we have observability We can go back to the feature extraction spreadsheet and review every potential feature Then use observability systems to see how many users invoke a feature We can easily do that with tools like Lightrun by placing a counter metric in the code you can download it for free here According to that information we can start narrowing the scope of features used by the product I discussed this before so it might not be as applicable if this functionality worked in the legacy system Even more important is the retirement of the running legacy If you chose a migration path in which the legacy implementation is still running this is the time to decide when to pull the plug Besides costs the security and maintenance problems make this impractical for the long run A common strategy is to shut down the legacy system periodically for an hour to detect dependencies usage we might not be aware of Tools such as network monitors can also help gauge the level of usage If you have the ability to edit the legacy or a proxy into the legacy this is the time to collect data about the usage Detect the users that still depend on that and plan the email campaign process for moving them on Use Tooling to Avoid Future LegacyA modern system can enjoy many of the newer capabilities at our disposal CI CD processes include sophisticated linters that detect security issues bugs and perform reviews that are far superior to their human counterparts A code quality tool can make a vast difference to the maintainability of a project Your product needs to leverage these new tools so it won t deteriorate back to legacy code status Security patches get delivered “seamlessly as pull requests Changes get implicit reviews to eliminate common mistakes This enables easier long term maintenance Maintaining the Compliance TestingAfter the migration process people often discard the compliance tests It makes sense to convert them to integration tests if possible necessary but if you already have integration tests it might be redundant and harder to maintain than your standard testing The same is true for the feature extraction spreadsheet It s not something that s maintainable and is only a tool for the migration period Once we re done with that we should discard it and we shouldn t consider it as authoritative FinallyMigrating old code is always a challenge as agile practices are crucial when taking on this endeavor There are so many pitfalls in the process and so many points of failure This is especially true when that system is in production and the migration is significant I hope this list of tips and approaches will help guide your development efforts I think pain in this process is unavoidable So is some failure Our engineering teams must be agile and responsive to such cases Detect potential issues and address them quickly during the process There s a lot more I could say about this but I want to keep it general enough so it will apply to wider cases If you have thoughts on this reach out to me on twitter to let me know	2022-05-09 07:36:20
海外TECH	DEV Community	Why you should not use pixels(px) in CSS	https://dev.to/freebeliever/why-you-should-not-use-pixelspx-in-css-2342	Why you should not use pixels px in CSSDid someone ever tell you to code like this something width px height px I can tell you straight on unless completely necessary do not code like that In a hypothetical situation I might be a user with a phone that does not have a width of px guess what happens then The hypothetical user get s an ugly looking side scrolling bar Even worse the user might not get some of the content A suggestionA better approach is to use view height vh Which basically displays content based on the screen size Here is another version of the code written previously something width vw height vh Now for a user with a device of a height of px the user would be shown an object of px	2022-05-09 07:07:08
海外TECH	DEV Community	Which functions/methods do you...	https://dev.to/joelbonetr/which-functionsmethods-do-you-484m	utils	2022-05-09 07:06:19
海外TECH	DEV Community	Creating Queues Using JavaScript	https://dev.to/deyemiobaa/creating-queues-using-javascript-lb4	Creating Queues Using JavaScript IntroductionDuring conversations about data structures in the programming world the term queue is heard quite often A queue is a linear data structure that follows the first in first out FIFO pattern i e removal takes place at the front and addition takes place at the end Think of it as the checkout point at a grocery store Customers who get to the checkout counter first get attended to first They can only join the queue from the back of the line and after they get attended to they leave from the front of the line Linear data structuresLinear data structures are types of data structures in which elements are stored sequentially The elements are organized in such a way that each element is directly linked to its previous and next element However the first element is only linked to its previous element and the last element is only linked to the next element Queues follow this arrangement pattern and we can see that by referring to our grocery store checkout counter analogy Each customer that walks to the checkout counter represents an element The first customer has a link to the previous customer the last customer has a link to the next customer and every other customer in between has a link to a previous and next customer Use cases for queuesThere are several use cases for queues in the programming and real world Some of them include A desk printer When you send documents to the printer they are printed in the same order in which they are sent and this is very useful when you re trying to print documents that follow a specific order The printer makes sure the pages don t get mixed up Adding songs to a queue in your music player Sometimes while we are working on a task we have our go to songs to keep the momentum going The queue function of the music player makes sure you listen to your song selections just the way it is arranged Customer service wait lines If you go to a bank to file a complaint they make you wait in lines and the next person in line won t be called unless the issue of the current customer has been resolved File sharing data transfer between two processes When transferring files from one device to another the files are received on the other end in the same order they were sent irrespective of the time it takes for any of them to get completed Queues can be implemented in any programming language but our focus is on how to create them using JavaScript In JavaScript it can also be implemented in two ways arrays and linked lists For this article we will implement queues using arrays Operations in queuesThese are some basic operations that are performed on queues EnqueueDequeuePeekReversing a queueFor the implementation of the above operations we d use an ES class and have the various operations as methods Creating a queue with its operationsThe first step is to initialize our class with its own storage an array where our queue elements would be stored class Queue constructor this queue The code block above represents the creation of a class named Queue The constructor method is a special method of a class that is used to create an object instance of that class It can be used to initialize any object that would be used across the class methods The this keyword serves as a regular object within this context It can be used to initialize any value Next up we add each queue operation as a method of the class EnqueueThis term refers to adding a new element to the queue Since we re implementing our queue with an array we can use the push array method to add new elements to the queue class Queue constructor this queue enqueue element this queue push element The added lines to our code block represent a method of class Queue It handles one operation which adds a new item to the array object that is initialized using the constructor method The enqueue method accepts one argument element and then adds it to this queue using the push array method DequeueThis term refers to removing a new element from the queue Again the shift array method takes care of this for us easily class Queue constructor this queue enqueue element this queue push element dequeue return this queue shift We added a new method dequeue This method deoesn t accept any arguments unlike the previous method It returns an element from the front of the queue and also removes it using the shift array method PeekWe use the peek method to check for the element at the front of the queue without removing it class Queue constructor this queue enqueue element this queue push element dequeue return this queue shift peek return this queue The peek method checks for the value at the front of the queue by accessing the first index of the queue Reversing a QueueAs the title implies we are simply trying to change the order of the queue from back to front The reverse method is handled using a while loop class Queue constructor this queue enqueue element this queue push element return this queue dequeue return this queue shift peek return this queue reverse Declare an empty array const reversed Iterate through the array using a while loop while this queue length gt reversed push this queue pop Set queue using the new array this queue reversed return this queue UsageTo see how our code works we are going to test out each method of our class First we need to create a new instance of our class then use that instance to access our methods const result new Queue Creating a new instance of our class Adding elementsresult enqueue Returns result enqueue Returns result enqueue Returns result enqueue Returns Removing an elementresult dequeue Returns Checking the first element in the queueresult peek Returns Reversing the queueresult reverse Returns ConclusionSummary We explained the concept of queues FIFO and how they are applied in the real world We created a class and performed various queue operations enqueue dequeue peek reverse That s it folks We ve successfully implemented a queue and its basic operations using JavaScript	2022-05-09 07:01:24
金融	ニッセイ基礎研究所	霧の中のGDP～経済ショック時のGDP速報をどう捉えるか～	https://www.nli-research.co.jp/topics_detail1/id=71045?site=nli	過去の経済ショック時のGDPの動きから、経済ショック時の動向を確認すると、nbsp経済ショック時の状況をみると、経済ショック時に実際の意思決定に利用されたGDP速報リアルタイムベースが示すより、最新値年月日公表でみればショックからの回復が弱く、遅れていることを示している。	2022-05-09 16:33:08
海外ニュース	Japan Times latest articles	Putin’s Red Square parade is chance to show gains in Ukraine war	https://www.japantimes.co.jp/news/2022/05/09/world/russia-victory-day-parade-2/	victory	2022-05-09 16:21:14
ニュース	BBC News - Home	NI secretary to meet Stormont political leaders	https://www.bbc.co.uk/news/uk-northern-ireland-61373504?at_medium=RSS&at_campaign=KARANGA	stormont	2022-05-09 07:49:50
ニュース	BBC News - Home	Covid: The struggle to get a dentist and the reality of living with Covid	https://www.bbc.co.uk/news/uk-61376764?at_medium=RSS&at_campaign=KARANGA	coronavirus	2022-05-09 07:06:42
ニュース	BBC News - Home	Philippines election: Marcos family eye return to power as country votes	https://www.bbc.co.uk/news/world-asia-61344609?at_medium=RSS&at_campaign=KARANGA	sweep	2022-05-09 07:56:08
北海道	北海道新聞	ロッテ佐々木朗「先頭に集中」　１３日オリックス戦で登板	https://www.hokkaido-np.co.jp/article/678432/	集中	2022-05-09 16:14:23
北海道	北海道新聞	スシロー１皿１００円終了へ　１０月から値上げ、調達費増	https://www.hokkaido-np.co.jp/article/678445/	回転ずし	2022-05-09 16:26:49
北海道	北海道新聞	春の高校野球支部予選・５月９日の試合結果	https://www.hokkaido-np.co.jp/article/678293/	春の高校野球	2022-05-09 16:15:02
北海道	北海道新聞	「天ぷら粉黄金」やパスタ値上げ　昭和産業６４品目、２～７％	https://www.hokkaido-np.co.jp/article/678452/	天ぷら粉	2022-05-09 16:23:00
北海道	北海道新聞	東証大幅反落、終値は６８４円安　２カ月ぶり安値	https://www.hokkaido-np.co.jp/article/678417/	日経平均株価	2022-05-09 16:08:52
北海道	北海道新聞	ブリヂストン３億の申告漏れ　タックスヘイブン対策税制を適用	https://www.hokkaido-np.co.jp/article/678438/	税務調査	2022-05-09 16:08:31
北海道	北海道新聞	スノボ冨田せ、競技出場に前向き　竹内「生涯現役」	https://www.hokkaido-np.co.jp/article/678451/	北京冬季五輪	2022-05-09 16:23:00
北海道	北海道新聞	どんな子も遊べる施設開館、山形　多様性認める社会に	https://www.hokkaido-np.co.jp/article/678450/	障害	2022-05-09 16:23:00
北海道	北海道新聞	バス、タクシーに１９歳運転手も　雇用増期待、待遇改善に課題	https://www.hokkaido-np.co.jp/article/678446/	待遇改善	2022-05-09 16:14:00
北海道	北海道新聞	大坂なおみは３８位に後退　女子テニス世界ランク	https://www.hokkaido-np.co.jp/article/678441/	世界ランキング	2022-05-09 16:12:00
北海道	北海道新聞	北海道２５５６人コロナ感染、６人死亡　２日ぶり３千人下回る	https://www.hokkaido-np.co.jp/article/678418/	新型コロナウイルス	2022-05-09 16:02:28
北海道	北海道新聞	釧路管内で８９人感染、根室管内２１人　新型コロナ	https://www.hokkaido-np.co.jp/article/678439/	根室管内	2022-05-09 16:01:00
ビジネス	プレジデントオンライン	海底には巨大な油田が眠っている…中国共産党が台湾侵攻を絶対に諦めない2大理由 - 国家のメンツ以上に大事なのは｢資源｣	https://president.jp/articles/-/56851	中国共産党	2022-05-09 17:00:00
マーケティング	MarkeZine	ソトコトが東京メトロ銀座線をジャック、設置したビーコンとアプリ連携でOOH連動プッシュ広告配信も実施	http://markezine.jp/article/detail/38932	東京メトロ	2022-05-09 16:30:00
IT	週刊アスキー	店舗のキャッシュレス決済サービス「STORES 決済」、クレジットカードの「タッチ決済」に対応	https://weekly.ascii.jp/elem/000/004/090/4090969/	stores	2022-05-09 16:40:00
IT	週刊アスキー	ひとり用の辛～い「ピザセット」登場！ ピザハットに「HOT MY BOX」5種	https://weekly.ascii.jp/elem/000/004/090/4090931/	hotmybox	2022-05-09 16:30:00
IT	週刊アスキー	東芝デジタルソリューションズ、ブロックチェーンネットワークのマネージドサービス「DNCWARE Blockchain＋」を提供開始	https://weekly.ascii.jp/elem/000/004/090/4090967/	dncwareblockchain	2022-05-09 16:30:00
IT	週刊アスキー	ソニー、「wena 3」と映画「シン・ウルトラマン」がコラボしたスマートウォッチを予約販売開始	https://weekly.ascii.jp/elem/000/004/090/4090986/	予約販売	2022-05-09 16:20:00
IT	週刊アスキー	約1万人限定のβテスターへ！新作ゲーム『SAO ヴァリアント・ショウダウン』クローズドβテスト参加者募集を開始	https://weekly.ascii.jp/elem/000/004/090/4090989/	参加者募集	2022-05-09 16:20:00
IT	週刊アスキー	アイスの「ピノ」が45年の歴史で初ドリンクに！「ピノ やみつきアーモンド味 ドリンク」	https://weekly.ascii.jp/elem/000/004/090/4090915/	森永乳業	2022-05-09 16:15:00
マーケティング	AdverTimes	姫路セントラルパークが「日本一過小評価されているサファリパーク」として、３年ぶりに自虐ＣＭを再開	https://www.advertimes.com/20220509/article383375/		2022-05-09 08:00:45
マーケティング	AdverTimes	書店で訳あり食品を販売　日販とクラダシ、年内に50店舗	https://www.advertimes.com/20220509/article383470/	books	2022-05-09 07:20:08