投稿時間:2022-01-11 02:23:45 RSSフィード2022-01-11 02:00 分まとめ(24件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	データ移行のためFormRequestをシーダーに適用したい	https://teratail.com/questions/377547?rss=all	データ移行のためFormRequestをシーダーに適用したいオーダーのデータ移行の際、OrderRequestにかけて紐づいたジョブが見つからなければrequestgtjobidnbspnbspとなるようにしたいのですが、バリデーションを行ってくれません。	2022-01-11 01:56:20
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Visual Studioで単体で動作するexeファイルの作成方法	https://teratail.com/questions/377546?rss=all	VisualStudioで単体で動作するexeファイルの作成方法前提・実現したいこと以前、こちらの質問で、VisualnbspStudionbspCodeのCの扱いで、dotnetnbspnewnbspconsoleで作成したプロジェクトで、単体で動作するexeファイルの生成方法をご教示いただき解決したのですが、今回は、VisualnbspStudioのCで単体で動作するexeファイルの生成方法のご教示をお願いいたします。	2022-01-11 01:26:36
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Wordpress 特定のカテゴリに記事がない場合、ある範囲を非表示にしたい	https://teratail.com/questions/377545?rss=all	Wordpress特定のカテゴリに記事がない場合、ある範囲を非表示にしたいwordpress初心者です。	2022-01-11 01:14:47
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	SpreadSheetLightで上書き保存しようとすると出るエラーの解決法に関して	https://teratail.com/questions/377544?rss=all	SpreadSheetLightで上書き保存しようとすると出るエラーの解決法に関してLibraOfficenbspCalcを読み取り上書き保存をしたいと考えているのですが。	2022-01-11 01:04:09
Git	Gitタグが付けられた新着投稿 - Qiita	[git blame] ファイルを誰がいつ更新したか調べる	https://qiita.com/jeronimo34/items/c55b18be0e8909a9b17e	xtfefjeronimogreatfeature	2022-01-11 01:37:45
海外TECH	MakeUseOf	How to Make a DIY Light Box for Just a Few Dollars	https://www.makeuseof.com/how-to-make-a-diy-light-box-for-just-a-few-dollars/	household	2022-01-10 16:30:12
海外TECH	DEV Community	Writing User Stories	https://dev.to/david_whitney/writing-user-stories-1dml	Writing User StoriesSoftware development transforms human requirements repeatedly until software is eventually produced We transform things we d like into feature requests Which are subsequently decomposed into designs Which are eventually transformed into working software At each step in this process the information becomes denser more concrete more specific In agile software development user stories are a brief statement of what a user wants a piece of software to do User stories are meant to represent a small atomic valuable change to a software system Sounds simple right But they re more than that user stories are artifacts in agile planning games they re triggers that start conversations tools used to track progress and often the place that a lot of product thinking ends up distilled User stories end up as the single source of truth of pending changes to software Because they re so critically important to getting work done it s important to understand them so we re going to walk through what exactly user stories are where they came from and why we use them The time before user storiesBefore agile reached critical mass the source of change for software systems was often a large specification that was often the result of a lengthy requirements engineering process In traditional waterfall processes the requirements gathering portion of software development generally happened at the start of the process and resulted in a set of designs for software that would be written at a later point Over time weaknesses in this very linear think gt plan gt do approach to change became obvious The specifications that were created ended up in systems that often took a long time to build didn t finish and full of defects that were only discovered way way too late The truth was that the systems as they were specified were often not actually what people wanted By disconnecting the design and development of complicated pieces of software frequently design decisions were misinterpreted as requirements and user feedback was hardly ever solicited until the very end of the process This is about as perfect a storm as can exist for requirements long laborious requirement capturing processes resulting in the wrong thing being built To make matters worse because so much thought work was put into crafting the specifications at the beginning of the process they often brought out the worst in people specs became unchangeable locked down binding things where so much work was done to them that if that work was ever invalidated the authors would often fall foul of the sunk cost fallacy and just continue down the path anyway because it was part of the design The specifications never met their goals They isolated software development from it s users both with layers of people and management They bound developers to decisions made during times of speculation And they charmed people with the security of having done some work when no software was being produced They provided a feedback less illusion of progress But not my specifications I hear you cry No not all specifications but most of them There had to be a better way to capture requirements that Was open to change to match the changing nature of softwareCould operate at the pace of the internetDidn t divorce the authors of work from the users of the systems they were designingWere based in real measurable progress The humble user story emerged as the format to tackle this problem What is a user storyA user story is a short structured statement of a change to a system They should be outcome focused precise and non exhaustive Stories originated as part of physical work tracking systems in early agile methods they were handwritten on the front of index cards with acceptance criteria written on the reverse of the card The physical format added constraints to user stories that are still useful today Their job is to describe an outcome and not an implementation They re used as artefacts in planning activities and they re specifically designed to be non exhaustive containing only the information absolutely required as part of a change to a product It s the responsibility of the whole team to make sure our stories are high enough quality to work from and to verify the outcomes of our work Furthermore user stories are an exercise in restraint They do not exist to replace documentation They do not exist to replace conversation and collaboration The job is to decompose large tough intractable problems into small articulated well considered changes User stories are meant to represent a small atomic valuable change to a software system and have mostly replaced traditional requirements engineering from the mid s onwards The user story contentsThe most common user story format and generally the one that should be followed by default was popularised by the XP team at Connextra in It looks like this As a lt persona gt I want lt business focused outcome gt So that lt reason driving the change gt Accept List of…Acceptance criteria…Notes Any notesThis particular format is popular because it considers both the desired outcome from a user s perspective the persona and also includes the product thinking or justification for the change as part of the So that clause By adhering to the constraint of being concise the story format forces us to decompose our work into small deliverable chunks It doesn t prevent us from writing build the whole solution but it illuminates poorly written stories very quickly Finally the user story contains a concise non exhaustive list of acceptance criteria Acceptance criteria list the essential qualities of the implemented work Until all of them are met the work isn t finished Acceptance criteria aren t an excuse to write a specification by stealth They not the output format of response documents when you re building APIs or snippets of HTML for web interfaces They re conversation points to verify and later accept the user story as completed Good acceptance criteria are precise and unambiguous anything else isn t an acceptance criteria As an example must work in IE is better than must work in legacy browsers equally must be accessible is worse than must adhere to all WCAG recommendations Who and what is a valid persona Personas represent the users of the software that you are building This is often mistaken to mean the customers of the business and this fundamental misunderstanding leads to lots of unnatural user stories being rendered into reality Your software has multiple different types of users even users you don t expect If you re writing a web application you might have personas that represent your end user business to business customers or other customer architypes In addition to this however you ll often have personas like the on call engineer supporting this application first line support or the back office user who configures this application While they might not be your paying customers they re all valid user personas and users of your software API teams often fall into the trap of trying to write user stories from the perspective of the customer of the software that is making use of their API This is a mistake and it s important that if you re building APIs you write user stories from the perspective of your customers the developers and clients that make use of your APIs to build consumer facing functionality What makes a good user story While the vast majority of teams use digital tracking systems today we should pay mind to the constraints placed upon user stories by physical cards and not over write our stories It s important to remember that user stories are meant to contain distilled information for people to work from As the author of a user story you need to be the world s most aggressive editor removing words that introduce ambiguity removing any and all repetition and making sure the content is precise Every single word you write in your user story should be vital and convey new and distinct information to the reader It s easy to misinterpret this as user stories must be exhaustive but that isn t the case Keep it tight don t waffle but don t try and reproduce every piece of auxiliary documentation about the feature or the context inside every story For example As a Back Office ManagerI want business events to be created that describe changes to or events happening to customer accounts that are of relevance to back office managementSo that those events may be used to prompt automated decisions on changing the treatment of accounts based on back office strategies that I have configured Could be re written As a Back Office ManagerI want an event published when a customer account is changedSo that downstream systems can subscribe to make decisionsAccept Event contains kind of change Event contains account identifiers External systems can subscribeIn this example edited precise language makes the content of the story easier to read and moving some of the nuance to clearly articulated acceptance criteria prevent the reader having to guess what is expected Bill West put together the mnemonic device INVEST standing for Independent Negotiable Verifiable Estimable Small and Testable to describe characteristics of a good user story but in most cases these qualities can be met by remembering the constraints of physical cards If in doubt remember the words of Ernest Hemingway If I started to write elaborately or like someone introducing or presenting something I found that I could cut that scrollwork or ornament out and throw it away and start with the first true simple declarative sentence I had written Write less The joy of physical limitationsDespite the inevitability of a digital and remote first world it s easy to be wistful for the days of user stories in their physical form with their associated physical constraints and limitations Stories written on physical index cards are constrained by the size of the cards this provides the wonderful side effect of keeping stories succinct they cannot possibly bloat or become secret specifications because the cards literally are not big enough The scrappy nature of index cards and handwritten stories also comes with the additional psychological benefit of making them feel like impermanent transitory artefacts that can be torn up and rewritten at will re negotiated and refined without ceremony or loss By contrast teams can often become attached to tickets in digital systems valuing the audit log of stories moved back and forth and back and forth from column to column as if it s more important than the work it s meant to inspire and represent Subtasks attached to the index card stories on post it notes become heavy and start falling apart items get lost and the cards sag prompting and encouraging teams to divide bloated stories into smaller more granular increments Again the physicality of the artefact bringing its own benefit Physical walls of stories are ever present tactile and real Surrounding your teams with their progress helps build a kind of total immersion that digital tools struggle to replicate Columns on a wall can be physical constrained reconfigured in the space and visual workspaces built around the way work and tasks flow rather than how a developer at a work tracking firm models how they presume you work There s a joy in physical real artefacts of production that we have entirely struggled to replicate digitally But the world has changed and our digital workflows can be enough but it takes work to not become so enamoured and obsessed with the instrumentation the progress reports and the roll up statistics and lose sight of the fact that user stories and work tracking systems were meant to help you complete some work to remember that they are the map and not the destination All the best digital workflows succeed by following the same kinds of disciplines and following the same constraints as physical boards have Digital workflows where team members feel empowered to delete and reform stories and tickets at any point Where team members can move refine and relabel the work as they learn And where teams do what s right for their project and worry about how to report on it afterwards find the most success with digital tools It s always worth acknowledging that those constraints helped give teams focus and are worth replicating What needs to be expressed as a user story Lots of teams get lost in the weeds when they try to understand what s a user story vs what s a technical task vs what s a technical debt card Looking backwards towards the original physical origin of these artefacts it s obvious all these things are the same thing Expressing changes as user stories with personas and articulated outcomes is valuable whatever the kind of change It s a way to communicate with your team that everyone understands and it s a good way to keep your work honest However don t fall into the trap of user story theatre for small pieces of work that need to happen anyway I d not expect a programmer to see a missing unit test and write a user story to fix it I d expect them to fix it I d not expect a developer to write a user story to fix a build they just watched break This is essential non negotiable work As a rule of thumb technical things that take less time to solve than write up should just be fixed rather than fudging language to artificially legitimise the work it s already legitimate work Every functional change should be expressed as a user story just make sure you know who the change is for If you can t articulate who you re doing some work for it is often a symptom of not understanding the audience of your changes at best or at worst trying to do work that needn t be done at all The relationship between user stories commits and pull requestsPull request driven workflows can suffer from the unfortunate side effect of encouraging deferred integration and driving folks towards one user story one pull request working patterns While this may work fine for some categories of change it can be problematic for larger user stories It s worth remembering when you establish your own working patterns that there is absolutely nothing wrong with multiple sets of changes contributing to the completion of a single user story Committing the smallest pieces of work that doesn t break your system is safer by default The sooner you re integrating your code the better regardless of story writing technique What makes a bad user story There are plenty of ways to write poor quality user stories but here are a few favourites Decomposed specifications Design by stealth prescriptive user stories that exhaustively list outputs or specifications as their acceptance criteria are low quality They constrain your teams to one fixed solution and in most cases don t result in high quality work from teams Word Salad user stories that grow longer than a paragraph or two almost always lead to repetition or interpretation of their intent They create work rather than remove it Repetition or boiler plate copy paste Obvious repetition and copy paste content in user stories invents work and burdens the readers with interpretation It s the exact opposite of the intention of a user story which is to enhance clarity The moment you reach for CTRL V C while writing a story you re making a mistake Given Then When or test script syntax in stories user stories do not have to be all things to all people Test scripts specifications or context documents have no place in stories they don t add clarity they increase the time it takes to comprehend requirements While valuable those assets should live in wikis and test tools respectively Help All my stories are too big Sequencing and splitting stories Driving changes through user stories becomes trickier when the stories require design exercises or the solution in mind has some pre requirements standing up new infrastructure for the first time etc It s useful to split and sequence stories to make larger pieces of technical work easier while still being deliverable in small chunks Imagine for example a user story that looked like this As a customerI want to call a customer APITo retrieve the data stored about me my order history and my account expiry dateOn the surface the story might sound reasonable but if this were a story for a brand new API your development team would soon start to spiral out asking questions like how does the customer authenticate what data should we return by default how do we handle pagination of the order history and lots of other valid questions that soon represent quite a lot of hidden complexity in the work In the above example you d probably split that work down into several smaller stories starting with the smallest possible story you can that forms a tracer bullet through the process that you can build on top of Perhaps it d be this list of stories A story to retrieve the user s public data over an API Create the API A story to add their account expiry to that response if they authenticate Introduce auth A story to add the top level order summary totals number of previous orders A story to add pagination and past orders to the responseThis is just illustrative and the exact way you slice your stories depends heavily on context but the themes are clear split your larger stories into smaller useful shippable parts that prove and add functionality piece by piece Slicing like this removes risk from your delivery allows you to introduce technical work carried by the story that needs it first and keeps progress visible Occasionally you ll stumble up against a story that feels intractable and inestimable First don t panic it happens to everyone breathe Then write down the questions you have on a card These questions form the basis of a spike a small Q amp A focused time boxed story that doesn t deliver user facing value Spikes exist to help you remove ambiguity to do some quick prototyping to learn whatever you need to learn so that you can come back and work on the story that got blocked Spikes should always pose a question and have a defined outcome be it example code or documentation explaining what was learnt They re the trick to help you when you don t seem to be able to split and sequence your work because there are too many unknowns Getting it rightYou won t get your user stories right first time but much in the spirit of other agile processes you ll get better at writing and refining user stories by doing it Hopefully this primer will help you avoid trying to boil the ocean and lead to you building small things safely If you re still feeling nervous about writing high quality user stories with your teams Henrik Kniberg and Alistair Cockburn published a workshop they called The Elephant Carpaccio Exercise in which will help you practice in a safe environment You can download the worksheet here Elephant Carpaccio facilitation guide google com	2022-01-10 16:29:13
海外TECH	DEV Community	How we reduced our nodejs monorepo build time by 70%	https://dev.to/scopsy/how-we-reduced-our-nodejs-monorepo-build-time-by-70-3oma	How we reduced our nodejs monorepo build time by How we reduced our nodejs monorepo build time by At Notifire we use a monorepo to manage our libraries and apps There are many debates over whether you should use a monorepo or a poly repo For us visibility code sharing standardization easier refactoring and a few other reasons were the critical factors for choosing this approach for our open source notification infrastructure project TLDR We migrated from yarn workspaces amp lerna to PNPM and nx dev The bigger the slowerWith all the advantages there are a few drawbacks to using monorepos We noticed a particular drawback when scaling the number of packages and amount of code in each one The time it takes to bootstrap the project and then build any packages within So a typical GitHub action for a service would run anywhere between to minutes And that s for each time a PR was created or a code was pushed to remote More than that installing a package locally with yarn install could take around minutes to install and build all the dependencies This amount of time spent bootstrapping and building reduced the developer experience and wasted collectively so much talented people s time Being an open source project with a growing number of contributors this was unacceptable Debugging the slowest tasksInspecting a typical minutes GitHub action it was clear that two specific steps took almost of the overall time yarn install takes minutesyarn build package could take from minutes to build the selected package and its dependencies Migrating from yarn workspaces to PNPMPNPM is a fast disk space efficient package manager as stated on their website and from some of the benchmarks there was a massive improvement in install time against yarn workspaces Moving from yarn install that took around minutes the migration to pnpm was effortless Just adding a pnpm workspace yaml to the project s root and running pnpm install that s all The symlinks and dependencies for each package we re efficiently installed in wait for it just minutes And that s without any cache at all After PNPM caches the majority of the dependencies it takes less than seconds to build and install the dependencies from the cached store Reducing minutes from the bootstrap time for every CI run and locally for first time contributors is a HUGE win But wait we can do even better From Lerna to NX devAfter seeing the Turborepo demo by vercel I was intrigued by their distributed caching mechanism With such a mechanism we can reuse the already built packages by other maintainers and download the dist assets instead of rebuilding them each time turborepo vs nx dev After brief research we decided to go with nx dev for multiple reasons Maturity nx was in the market for a while now and they have a pretty big community around them Performance Seeing some of the benchmarks nx looks like a faster build system overall Our community member nishit g took over the open GitHub issue and quickly after we had a PR open the results astonished us seconds the building step Instead of the previous minutes building a specific set of packages After implementing the nx cloud for distributed caching the entire packages take less than seconds when fully cached building But even without being fully cached due to the intelligent parallelism nx performs and builds our target package in less than seconds SummaryReducing our build times from minutes to around minutes significantly impacts the developer experience of our maintainers It also reduces the feedback loop from creating a PR to running our test suite to merging the feature You can check the final configuration on our GitHub repository HUGE Kudos to nishit g for migrating us from Lerna to NX Check him out on his Twitter as well	2022-01-10 16:13:26
海外TECH	DEV Community	Perulangan Di Vue Js	https://dev.to/medan_in_code/perulangan-di-vue-js-1j0a	Perulangan Di Vue JsTutorial kali ini akan membahas bagaimana menggunakan perulangan di vue Untuk melakukan ini di vue kita menggunakan directive v for Menampilkan data arrayMisalnya kita punya data array nama nama siswasiswa budi andi caca atau jika menggunakan struktur vue akan seperti ini export default name App data gt return siswa budi andi caca Data tersebut akan kita tampilkan menggunakan v for Maka template vue nya akan menjadi seperti ini lt ul gt lt li v for nama in siswa gt nama lt li gt lt ul gt Kita menggunakan html list untuk menampilkan nama siswa Bisa dilihat kita melakukan perulangan dengan variable siswa dan nama sebagai alias untuk item satuan Kemudian karena ini hanya array kita langsung mencetak dengan seperti dibawah ini nama Kita juga bisa menampilkan index dari masing masing data tersebut dengan menambahkan kode seperti dibawah lt ul gt lt li v for nama index in siswa gt index nama lt li gt lt ul gt Index diawali dari jadi kita menambah ketika mencetak Maka akan keluar hasil seperti dibawah ini Menampilkan data objectSebenarnya cara sama saja menampilkan data object ataupun array dengan v forJika kita punya data seperti dibawah ini siswa nama budi kelas XII A jurusan RPL Kode template sama saja lt ul gt lt li v for value in siswa gt value lt li gt lt ul gt Kita juga bisa menampilkan key dari object sebagimana index dari array sebelumnya lt ul gt lt li v for value key in siswa gt key value lt li gt lt ul gt Maka akan mendapatkan hasil seperti dibawah ini Di object kita bisa menambahkan satu parameter lagi yaitu index sehingga menjadi seperti ini lt ul gt lt li v for value key index in siswa gt index key value lt li gt lt ul gt Menampilkan Data CollectionJika kita mendapatkan data dari api backend seringkali data yang didapatkan berbentuk collection atau array object atau berformat data JSON Misalnya seperti data dibawah siswa nama budi kelas XII A jurusan RPL nama andi kelas XII B jurusan TKJ nama caca kelas XII A jurusan RPL Kita akan menampilkan kedalam html tabel Maka kode v for untuk table kurang lebih seperti dibawah ini lt table border gt lt tr gt lt th gt No lt th gt lt th gt Nama lt th gt lt th gt Kelas lt th gt lt th gt Jurusan lt th gt lt tr gt lt tr v for data index in siswa gt lt td gt index lt td gt lt td gt data nama lt td gt lt td gt data kelas lt td gt lt td gt data jurusan lt td gt lt tr gt lt table gt Kenapa kita meletakkan v for di tr karena tr lah yang akan kita looping sebanyak data siswa data nama berarti kita memanggil key nama dari variabel data yang sudah jadi objek dari perulangan siswa Attribut v bind keyAttribut ini bisa juga dipanggil hanya dengan key Jika kita menggunakan v for maka vue menyarankan kita harus menggunakan attribute ini di IDE apalagi yang menggunakan syntax linter akan menunjukan warning di baris kodenya jika kita tidak menambahkan key saat pakai v for Attribute ini berperan sebagai penanda unik kayak primary key lah kalau di database agar vue bisa melakukan tracking perubahan setiap tag html saat dirender Asal dari key ini bisa dari index dari array key atau properti dari object Contohnya lt ul gt lt li v for value index in siswa v bind key index gt index value lt li gt lt ul gt atau jika kita punya object yang memiliki attribute unik siswa id nama budi id nama andi Maka kode htmlnya bisa seperti dibawah ini lt ul gt lt li v for data index in siswa v bind key data id gt index data nama lt li gt lt ul gt Sampai sini dulu pembahasan mengenai penggunaan v for silahkan bertanya dibawah jika ada yang kurang dimengerti	2022-01-10 16:07:21
Cisco	Cisco Blog	Logicalis and Cisco Delivering Business Outcome-led Solutions for the Digital Era	https://blogs.cisco.com/partner/logicalis-and-cisco-delivering-business-outcome-led-solutions-for-the-digital-era	Logicalis and Cisco Delivering Business Outcome led Solutions for the Digital EraTo help highlight the value customers gain from working with Logicalis and Cisco this blog describes two example use cases in high demand by businesses today workplace transformation and end to end security	2022-01-10 16:00:42
海外科学	NYT > Science	How European Royals Once Shared Their Most Important Secrets	https://www.nytimes.com/2022/01/10/science/european-royals-letterlocking.html	catherine	2022-01-10 16:56:53
海外科学	NYT > Science	‘People Need to Be Reminded About Flu’	https://www.nytimes.com/2022/01/10/health/influenza-vaccines-elderly.html	rates	2022-01-10 16:38:11
海外科学	NYT > Science	At-Home Coronavirus Tests Are Inaccessible to Blind People	https://www.nytimes.com/2022/01/10/health/covid-tests-blind-people.html	At Home Coronavirus Tests Are Inaccessible to Blind PeopleWith visual cues and complex steps at home coronavirus tests are often inaccessible to blind people But some low and high tech workarounds could help	2022-01-10 16:09:30
海外科学	BBC News - Science & Environment	Veg diet plus re-wilding gives 'double climate dividend'	https://www.bbc.co.uk/news/science-environment-59941016?at_medium=RSS&at_campaign=KARANGA	experts	2022-01-10 16:16:00
金融	◇◇　保険デイリーニュース　◇◇（損保担当者必携！）	保険デイリーニュース(01/11)	http://www.yanaharu.com/ins/?p=4803	情報流出	2022-01-10 16:31:13
ニュース	BBC News - Home	Developers told to remove unsafe cladding on low buildings	https://www.bbc.co.uk/news/business-59935333?at_medium=RSS&at_campaign=KARANGA	dangerous	2022-01-10 16:48:10
ニュース	BBC News - Home	Barry Bennell: Men lose case against Manchester City over abuse	https://www.bbc.co.uk/news/uk-england-manchester-59934051?at_medium=RSS&at_campaign=KARANGA	scout	2022-01-10 16:10:09
ニュース	BBC News - Home	Anglesey crossbow murder victim 'defrauded' of £200,000	https://www.bbc.co.uk/news/uk-wales-59936183?at_medium=RSS&at_campaign=KARANGA	court	2022-01-10 16:28:26
ニュース	BBC News - Home	Djokovic Covid timeline: Did he break rules after testing positive?	https://www.bbc.co.uk/news/59939122?at_medium=RSS&at_campaign=KARANGA	positive	2022-01-10 16:28:42
ニュース	BBC News - Home	Cladding: Why is it unsafe and what money has the government promised?	https://www.bbc.co.uk/news/explainers-56015129?at_medium=RSS&at_campaign=KARANGA	building	2022-01-10 16:01:19
ニュース	BBC News - Home	Superb Higgins sweeps Zhao aside to reach quarter-finals	https://www.bbc.co.uk/sport/snooker/59942746?at_medium=RSS&at_campaign=KARANGA	alexandra	2022-01-10 16:33:21
ニュース	BBC News - Home	Cooper Kupp, Rashaad Penny & Justin Herbert in NFL plays of the week	https://www.bbc.co.uk/sport/av/american-football/59940698?at_medium=RSS&at_campaign=KARANGA	Cooper Kupp Rashaad Penny amp Justin Herbert in NFL plays of the weekCooper Kupp stars as the NFL goes trick play crazy in the final weekend of the regular season before the playoffs begin next week	2022-01-10 16:26:43
北海道	北海道新聞	イスラム武装勢力の幹部殺害　パキスタンから逃亡	https://www.hokkaido-np.co.jp/article/631901/	武装勢力	2022-01-11 01:01:00
海外TECH	reddit	WARM UP // Episode 4 Cinematic	https://www.reddit.com/r/VALORANT/comments/s0ngcr/warm_up_episode_4_cinematic/	WARM UP Episode Cinematic submitted by u TheAjwinner to r VALORANT link comments	2022-01-10 16:06:58