投稿時間:2021-08-03 07:13:07 RSSフィード2021-08-03 07:00 分まとめ(16件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia Mobile] Google、次期フラグシップ「Pixel 6／6 Pro」予告　オリジナルSoC「Tensor」搭載	https://www.itmedia.co.jp/mobile/articles/2108/03/news055.html	google	2021-08-03 06:29:00
Google	カグア！Google Analytics 活用塾:事例や使い方	Audiostockで買ったYouTube安心利用曲でも著作権侵害の申し立てを受けることがある	https://www.kagua.biz/social/youtube/20210803a1.html	audiostock	2021-08-02 21:00:44
AWS	AWS Machine Learning Blog	Simplify and automate anomaly detection in streaming data with Amazon Lookout for Metrics	https://aws.amazon.com/blogs/machine-learning/simplify-and-automate-anomaly-detection-in-streaming-data-with-amazon-lookout-for-metrics/	Simplify and automate anomaly detection in streaming data with Amazon Lookout for MetricsDo you want to monitor your business metrics and detect anomalies in your existing streaming data pipelines Amazon Lookout for Metrics is a service that uses machine learning ML to detect anomalies in your time series data The service goes beyond simple anomaly detection It allows developers to set up autonomous monitoring for important metrics …	2021-08-02 21:28:05
python	Pythonタグが付けられた新着投稿 - Qiita	独学プログラマーのまとめ　その6	https://qiita.com/m_sano0426/items/42dc63b430b0a27859ae	残り割が果てし無いforループforループは、イテラブルを繰り返し処理するために使われ、反復処理と言う。	2021-08-03 06:45:24
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	【Vue.js】フォームをコンポーネント化したら表示されなくなった	https://teratail.com/questions/352480?rss=all	【Vuejs】フォームをコンポーネント化したら表示されなくなった概要現在、作成したnewvueとeditvueでフォームの部分が似ているので、共通化して、コンポーネントかしたいと考えています。	2021-08-03 06:59:01
海外TECH	Ars Technica	Post Mortem is the Norwegian vampire procedural dramedy we need right now	https://arstechnica.com/?p=1784530	funeral	2021-08-02 21:37:01
海外TECH	DEV Community	This is How To Make JS Promises [From Scratch]	https://dev.to/cleancodestudio/this-is-how-to-implement-javascript-promises-from-scratch-357k	This is How To Make JS Promises From Scratch ltag user id follow action button background color d important color ffffff important border color d important Clean Code StudioFollow Clean Code Clean Life Simplify Today we create our own JavaScript Promise implementation From Scratch Promises under the hoodTo create a new promise we simply use new Promise like so new Promise resolve reject gt resolve someValue We pass a callback that defines the specific behavior of the promise A promise is a container Giving us an API to manage and transform a valueThat lets us manage and transform values that are not actually there yet Using containers to wrap values is common practice in the functional programming paradigm There are different kinds of containers in functional programming The most famous being Functors and Monads Implementing a promise to understand its internals The then methodclass Promise constructor then this then then const getItems new Promise resolve reject gt HTTP get items err body gt if err return reject err resolve body getItems then renderItems console error Pretty straight forward this implementation so far doesn t do anything more than any function with a success resolve and an error reject callback So check it when we re making a promise from the ground up we have an extra normally non revealed step to implement MappingCurrently our Promise implementation won t work it s over simplified and doesn t contain all of the required behavior needed to properly work What is one of the features and or behaviors our implementation is currently missing For starters we re not able to chain then calls Promises can chain several then methods and should return a new Promise each time when the result from anyone of these then statements is resolved This is one of the primary feature that makes promises so powerful They help us escape callback hell This is also the part of our Promise implementation we are not currently implementing It can get a bit messy combining all of the functionalities needed to make this Promise chain work properly in our implementation but we got this Let s dive in simplify and set up our implementation of a JavaScript Promise to always return or resolve an additional Promise from a then statement To start with we want a method that will transform the value contained by the promise and give us back a new Promise Hmmm doesn t this sound oddly familiar Let s take a closer look Aha this sounds exactly like how Array prototype map implements pretty to the mark doesn t it map s type signature is map a gt b gt Array a gt Array bSimplified this means that map takes a function and transforms type a to a type b This could be a String to a Boolean then it would take an Array of a string and return an Array of b Boolean We can build a Promise prototype map function with a very similar signature to that of Array prototype map which would allow us to map our resolved promise result into another proceeding Promise This is how we are able to chain our then s that have callback functions that return any random result but then seem to magically somehow return Promises without us needing to instantiate any new promises map a gt b gt Promise a gt Promise bHere s how we implement this magic behind the scenes class Promise constructor then this then then map mapper return new Promise resolve reject gt this then x gt resolve mapper x reject What d we just do Okay so let s break this down When we create or instanciate a Promise we are defining a callback that is our then callback aka used when we successfully resolve a result We create a map function that accepts a mapper function This map function returns a new promise Before it returns a new promise it attempts to resolve the results from the prior promise using We map the results from the prior Promise into a new Promise and then we are back out within the scope of the newly created promise instantiated within our our map method We can continue this pattern appending as many then callbacks as we need to and always returning a new Promise without us needing to externally instantiate any new promises outside of our map method resolve reject gt this then What is happening is that we are calling this then right away the this refers to our current promise so this then will give us the current inner value of our promise or the current error if our Promise is failing We now need to give it a resolve and a reject callback next resolve x gt resolve mapper x next reject rejectThis is the most important part of our map function First we are feeding our mapper function with our current value x promise map x gt x The mapper is actuallyx gt x so when we domapper it returns And we directly pass this new value in the example to the resolve function of the new Promise we are creating If the Promise is rejected we simply pass our new reject method without any modification to the value map mapper return new Promise resolve reject gt this then x gt resolve mapper x reject const promise new Promise resolve reject gt setTimeout gt resolve promise map x gt x gt Promise then x gt console log x err gt console error err gt it s going to log To sum it up what we are doing here is pretty simple we are just overriding our resolve function with a compositon of our mapper function and the next resolve This is going to pass our x value to the mapper and resolve the returned value Using a bit more of our Promise Implementation const getItems new Promise resolve reject gt HTTP get items err body gt if err return reject err resolve body getItems map JSON parse map json gt json data map items gt items filter isEven map items gt items sort priceAsc then renderPrices console error And like that we re chaining Each callback we chain in is a little dead and simple function This is why we love currying in functional programming Now we can write the following code getItems map JSON parse map prop data map filter isEven map sort priceAsc then renderPrices console error Arguably you could say this code is cleaner given you are more familiar with functional syntax On the other hand if you re not familiar with functional syntax then this code made be extremely confusing So to better understand exactly what we re doing let s explicitly define how our then method will get transformed at each map call Step new Promise resolve reject gt HTTP get items err body gt if err return reject err resolve body Step then is now then resolve reject gt HTTP get items err body gt if err return reject err resolve body map JSON parse then is now then resolve reject gt HTTP get items err body gt if err return reject err resolve JSON parse body Step map x gt x data then is now then resolve reject gt HTTP get items err body gt if err return reject err resolve JSON parse body data Step map items gt items filter isEven then is now then resolve reject gt HTTP get items err body gt if err return reject err resolve JSON parse body data filter isEven Step map items gt items sort priceAsc then is now then resolve reject gt HTTP get items err body gt if err return reject err resolve JSON parse body data filter isEven sort priceAsc Step then renderPrices console error then is called The code we execute looks like this HTTP get items err body gt if err return console error err renderMales JSON parse body data filter isEven sort priceAsc Chaining and flatMap Our Promise implementation is still missing something chaining When you return another promise within the then method it waits for it to resolve and passes the resolved value to the next then inner function How s this work In a Promise then is also flattening this promise container An Array analogy would be flatMap map x gt x x gt flatMap x gt x x gt getPerson flatMap person gt getFriends person gt Promise Promise Person getPerson flatMap person gt getFriends person gt Promise Person This is our signature breakdown but if it s tough to follow I d recommend trying to track down the logic tail a few more times and if it doesn t click then attempt diving into the direct implementation below We re pretty deep and without experience in functional programming this syntax can be tricky to track but give it your best go and let s go on in below class Promise constructor then this then then map mapper return new Promise resolve reject gt this then x gt resolve mapper x reject flatMap mapper return new Promise resolve reject gt this then x gt mapper x then resolve reject reject We know that flatMap s mapper function will return a Promise When we get our value x we call the mapper and then we forward our resolve and reject functions by calling then on the returned Promise getPerson map JSON parse map x gt x data flatMap person gt getFriends person map json gt json data map friends gt friends filter isMale map friends gt friends sort ageAsc then renderMaleFriends console error How bout that What we actually did here by separating the differing behaviors of a promise was create a Monad Simply a monad is a container that implements a map and a flatMap method with these type signatures map a gt b gt Monad a gt Monad bflatMap a gt Monad b gt Monad a gt Monad bThe flatMap method is also referred as chain or bind What we just built is actually called a Task and the then method is usually named fork class Task constructor fork this fork fork map mapper return new Task resolve reject gt this fork x gt resolve mapper x reject chain mapper return new Task resolve reject gt this fork x gt mapper x fork resolve reject reject The main difference between a Task and a Promise is that a Task is lazy and a Promise is not What s this mean Since a Task is lazy our program won t really execute anything until you call the fork then method On a promise since it is not lazy even when instantiated without its then method never being called the inner function will still be executed immediately By separating the three behaviors characterized by then making it lazy just by separating the three behaviors of then and by making it lazy we have actually implemented in lines of code a lines polyfill Not bad right Summing things upPromises are containers holding values just like arrays then has three behaviors characterizing it which is why it can be confusing then executes the inner callback of the promise immediately then composes a function which takes the future value of the Promises and transforms so that a new Promise containing the transformed value is returnedIf you return a Promise within a then method it will treat this similarly to an array within an array and resolve this nesting conflict by flattening the Promises so we no longer have a Promise within a Promise and remove nesting Why is this the behavior we want why is it good Promises compose your functions for youComposition properly separates concerns It encourages you to code small functions that do only one thing similarly to the Single Responsibility Principle Therefore these functions are easy to understand and reuse and can be composed together to make more complex things happen without creating high dependency individual functions Promises abstract away the fact that you are dealing with asynchronous values A Promise is just an object that you can pass around in your code just like a regular value This concept of turning a concept in our case the asynchrony a computation that can either fail or succeed into an object is called reification It s also a common pattern in functional programming Monads are actually a reification of some computational context ltag user id follow action button background color d important color ffffff important border color d important Clean Code StudioFollow Clean Code Clean Life Simplify Clean Code StudioClean Code	2021-08-02 21:35:29
海外TECH	DEV Community	Myth: DSA is Required Only To Crack Interviews #Busted | Netlist Generation	https://dev.to/kaustuv942/myth-dsa-is-required-only-to-crack-interviews-busted-netlist-generation-14ji	Myth DSA is Required Only To Crack Interviews Busted Netlist GenerationConfused why every SDE SWE role requires DSA when day to day mundane work might not even need it You are on the right article In this article we will take a look at particularly interesting instance of web dev where DFS a well known graph algorithm fit the problem just too well Although day to day activities usually doesn t require such knowledge of graph algorithms however once in a blue moon comes about a problem which demands an efficient solution which is next to impossible without graph theory Problem StatementGiven a electrical circuit annotate its nodes Rules Equipotential points must given same names No two nodes having different potential must have same names A node is an endpoint of an circuit element For e g each resistor has nodes marked and in Fig N nodes are given to you The graph is given to you in terms of edges u v in a graph G where u and v are the nodes Fig Voltage Divider AnalysisWe know points not having a potential drop between them must lie at the same potential Naming nodes is very easy when you have two nodes in the picture joined by a single edge One can simply name both the nodes node and go about their day No worries Yay Right Wrong Only if it was that simple sighs Presenting Fig where it is clearly visible that a single node might be connected to another node but also multiple such nodes Fig Astable MultivibratorTherefore we must be able to figure out a way to first find all nodes connected to a particular node Then give all these nodes the same name People familiar with graph theory and algorithms might be getting ideas by now So lets look at the solution now SolutionA straight out of the wardrobe solution is Depth First Search a k a DFS on each unvisited node finding out the the connected nodes recursively and naming them with node x for each connected segment And just like that a complex problem turns into a trivial application of DSA Tada Here is a piece of related code from the repo The piece of code below creates separate sets of nodes which are at the same potential The circuit s graphical representation is made using mxgraph var NODE SETS console log dfs init var ptr var mp Array fill NODE SETS new Set Defining ground for var property in list if list property Component true amp amp list property symbol PWR mxCell prototype ConnectedNode null var component list property if component children null pins for var child in component children var pin component children child if pin null amp amp pin vertex true amp amp pin connectable if pin edges null pin edges length if mp pin id continue var stk new Stack var cur node var cur set var contains gnd stk push pin console log exploring connected nodes of pin while stk isEmpty cur node stk peek stk pop mp cur node id cur set push cur node stk print for var wire in cur node edges console log cur node edges wire if cur node edges wire source null amp amp cur node edges wire target null if cur node edges wire target ParentComponent null if cur node edges wire target ParentComponent symbol PWR contains gnd if cur node edges wire target vertex true if mp cur node edges wire target id amp amp cur node edges wire target id cur node id stk push cur node edges wire target if cur node edges wire source vertex true if mp cur node edges wire source id amp amp cur node edges wire source id cur node id stk push cur node edges wire source Checking for wires which are connected to another wire s Comment out the if conditions below if edge connections malfunction var conn vertices if cur node edges wire edges amp amp cur node edges wire edges length gt for const ed in cur node edges wire edges if mp cur node edges wire edges ed id conn vertices conn vertices concat traverseWire cur node edges wire edges ed mp if cur node edges wire source edge true if mp cur node edges wire source id amp amp cur node edges wire source id cur node id conn vertices conn vertices concat traverseWire cur node edges wire source mp if cur node edges wire target edge true if mp cur node edges wire target id amp amp cur node edges wire target id cur node id conn vertices conn vertices concat traverseWire cur node edges wire target mp console log CONN EDGES conn vertices conn vertices forEach elem gt stk push elem if contains gnd for var x in cur set NODE SETS add cur set x console log Set of nodes at same pot cur set if contains gnd NODE SETS push new Set cur set This wouldn t have been possible without the help of kumanik A big shoutout to him Frontend is usually not associated with data processing However the fact that this algorithm was run in the front end really changed my notions on that Frontend devs Beware P S Feel free to visit the project repo at Project Name eSim Cloud	2021-08-02 21:03:47
Apple	AppleInsider - Frontpage News	New Apple Store App Clip surfaces self-checkout options	https://appleinsider.com/articles/21/08/02/new-apple-store-app-clip-surfaces-self-checkout-options?utm_medium=rss	New Apple Store App Clip surfaces self checkout optionsA new App Clip for the Apple Store app allows customers to quickly scan a barcode to purchase select accessories without interacting with store staff Available now at a limited number of Apple Store locations the new self checkout App Clip streamlines contactless shopping at the company s brick and mortar locations As reported by toMac App Clips codes are displayed on placards next to certain accessories like iPhone cases Scanning the code opens the new Apple Store Scan Pay Go App Clip which subsequently launches the app s barcode scanner Read more	2021-08-02 21:57:56
海外TECH	Engadget	Twitter partners with Reuters and AP to boost curation efforts	https://www.engadget.com/twitter-associated-press-reuters-curation-partnership-213918911.html?src=rss	Twitter partners with Reuters and AP to boost curation effortsTwitter is partnering with The Associated Press and Reuters to help its curation team put credible information in front of users Made up of employees who work together to contextualize some of the most popular topics people are discussing on Twitter the curation team oversees some of the platform s more visible and sometimes controversial features including Trends and the Explore tab As a Twitter user the company says you can expect to see it work faster to ensure there s more and better contextual information to see as people discuss things on the service As a starting point on that front the company says Trends will include contextual descriptions and links to reporting from reputable publications more frequently Additionally the company says the program will help it proactively identify topics that could become a wellspring of misinformation “Rather than waiting until something goes viral Twitter will contextualize developing discourse at pace with or in anticipation of the public conversation the company said Twitter also expects the partnership will help some features where context is vitally important work better Here the company points to tools like Birdwatch Initially The Associated Press and Reuters will focus on helping the company with English language content but it s worth noting the curation team contextualizes Japanese Arabic Spanish and Portuguese content as well In trying to support its curation team better Twitter wants to avoid a repeat of a situation like the one it found itself in last year following the death of Jeffrey Epstein The social media network was overrun with conspiracy theories about Epstein s suicide and the company was seemingly unable to stop hashtags like ClintonBodyCount from trending Even when you take blatant disinformation out of the picture Twitter trends are frequently easy bait for trolling as was on display when US gymnast Simone Biles withdrew from the Tokyo Olympics While trolls are likely to continue trying to game the service enlisting the help of The Associated Press and Reuters could make those efforts less visible	2021-08-02 21:39:18
ニュース	BBC News - Home	Afghanistan: Street fighting rages as Taliban attack key city	https://www.bbc.co.uk/news/world-asia-58051481	capital	2021-08-02 21:02:31
ニュース	BBC News - Home	The Hundred - Oval Invincibles v Welsh Fire: Juggling catches & whipped sixes - best of Monday's action	https://www.bbc.co.uk/sport/av/cricket/58064562	The Hundred Oval Invincibles v Welsh Fire Juggling catches amp whipped sixes best of Monday x s actionWatch the best moments from Monday s action in the men s and women s Hundred as Oval Invincibles took on Welsh Fire at the Oval	2021-08-02 21:10:22
ニュース	BBC News - Home	VAR 'won't penalise trivial things' in Premier League	https://www.bbc.co.uk/sport/football/58064333	VAR x won x t penalise trivial things x in Premier LeagueThe use of video assistant referees will be dialled back in the Premier League with officials told not to penalise trivial things	2021-08-02 21:35:07
LifeHuck	ライフハッカー［日本版］	つい悲観的になりがちな人が、すぐ身につけたい簡単な習慣	https://www.lifehacker.jp/2021/08/239553book_to_read-809.html	佐々木常夫	2021-08-03 07:00:00
北海道	北海道新聞	ＥＵ委、ＦＢ買収計画で本格調査　競争減少を懸念	https://www.hokkaido-np.co.jp/article/574231/	欧州委員会	2021-08-03 06:13:00
北海道	北海道新聞	ＮＹ株続落、９７ドル安　コロナ変異株の感染拡大で	https://www.hokkaido-np.co.jp/article/574230/	感染拡大	2021-08-03 06:03:00