投稿時間:2021-07-15 06:25:04 RSSフィード2021-07-15 06:00 分まとめ(29件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
TECH	Engadget Japanese	1983年7月15日、家庭用ゲーム機「ファミリーコンピュータ」が発売されました：今日は何の日？	https://japanese.engadget.com/today-203033774.html	発売	2021-07-14 20:30:33
python	Pythonタグが付けられた新着投稿 - Qiita	Djangoに０から入門	https://qiita.com/kaoru_engineer/items/fd9727423a5e48a0e9c7	djangoadminstartprojecthelloappプロジェクト名PyCharmの設定をする次にPyCharmを開いて、作成したプロジェクトディレクトリ仮想環境ディレクトリ直下のhelloappを開き、以下の手順で設定する。	2021-07-15 05:34:12
python	Pythonタグが付けられた新着投稿 - Qiita	初期化済みの配列を用意する	https://qiita.com/izmktr/items/41d781a3a1cf72aeb359		2021-07-15 05:32:38
js	JavaScriptタグが付けられた新着投稿 - Qiita	対戦ゲームを作る。 その5	https://qiita.com/ohisama@github/items/b1063b5ce80eb153ef67	対戦ゲームを作る。	2021-07-15 05:58:06
海外TECH	Ars Technica	iOS zero-day let SolarWinds hackers compromise fully updated iPhones	https://arstechnica.com/?p=1780318	linkedin	2021-07-14 20:04:09
海外TECH	DEV Community	Incident Retro: Failing Comment Creation + Erroneous Push Notifications	https://dev.to/devteam/incident-retro-failing-comment-creation-erroneous-push-notifications-55dj	Incident Retro Failing Comment Creation Erroneous Push NotificationsThis incident retro was tougher than most to share because despite the seriousness of the issue it affected only a very small percentage of our user base However we learned some incredibly valuable lessons and I think it s only right that I give others the chance to learn from our mistake as well ContextOn Thursday July th we merged a very large PR that updated our code to start using our new User Settings instead of the deprecated fields on users The goal of moving these fields to user settings is to lighten up the user model and make these types of settings more configurable on a per Forem basis ProblemOn July th around midday it was brought to our attention through a bug report that the comment creation experience on the frontend seemed to be broken At this point folks on the team started looking into the problem Using Honeycomb we were able to confirm that the problem started when the User Settings PR was deployed which made it the prime suspect I immediately dove into the PR and quickly found the line of code that had been broken We had incorrectly removed the user ids scope from the filtering used to collect user IDs for sending mobile push notifications This was causing us to attempt to grab notification settings and IDs for all users with mobile notifications turned on which was often timing out These timeouts would occur after a comment was created so the comment in most cases still existed but we never returned a success response to the frontend This caused the frontend to freeze creating a bad experience for the user FixIn order to remedy this situation we quickly added back the scope and deployed Immediately the errors and timeouts went away and things returned to normal for comment creation At this point we concluded that possibly some extra notifications had been sent but that the majority of these requests had timed out so we assumed we were in a good state now I looked for some sort of push notification model in our app where we might have stored unsent notifications but upon not finding one figured we were clear More ProblemsJuly th pm EDT Unfortunately the above assumption was incorrect Just before midnight eastern a team member reported she was getting random notifications on her phone At this point our mobile engineer jumped in to investigate and found that we had a ton of push notifications enqueued in Redis July th am EDT Mobile engineer posts about the issue in our emergency Slack channel July th am EDT On call engineer wakes up and sees the emergency Slack message and jumps in to help investigate and try to resolve the issue Shortly after I also jumped in It was at this point that I learned all about how our push notification system worked We use RPush for communicating with various push notification services RPush stores the data about the push notifications in Redis for quick insertion and removal times We quickly assessed that we had a large number of push notifications enqueued in Redis waiting to be sent despite the solution deployed the day before Fix Upon realizing we had all of these records in Redis we took the following steps to resolve the issue Removal of the iOS cert from Heroku to prevent sending any notifications Without this cert we could ensure we would not send anymore bad notifications and that would give us time to fix the data in Redis To be safe we removed all of the PushNotifications DeliveryWorker jobs from Sidekiq so as not to be pinging Redis for the keys causing our key collection to slow down At the same time we looped through all of the keys in Redis and collected all of the rpush ones These included all delivered and undelivered keys There were million rpush keys so this process took about mins We used the below script redis Rails cache redisstart total key collection index keys redis scan start while index start index total keys count keys each do key key collection lt lt key if key include rpush notifications end index keys redis scan start endOnce we had the keys collected we double checked that they were the keys we wanted and then we deleted them ALL in batches of using this code key collection each slice s puts redis del s Once the keys were gone we double checked the count and then added back the iOS cert to Heroku After Heroku restarted we ran a test to confirm that the notifications were back to sending and that we were recording delivered notifications correctly again in Redis Impact Comment CreationThe comment creation flow on the frontend was broken for hours after the UserSettings PR was deployed on July th However comment creation levels remained steady irb main gt Comment where created at hours ago Time now count gt irb main gt Comment where created at hours ago hours ago count gt irb main gt Comment where created at hours ago hours ago count gt irb main gt Comment where created at hours ago hours ago count gt irb main gt Comment where created at hours ago hours ago count gt In total there were comments that were affected by the broken frontend interface Push NotificationsGiven DEV is early on in its mobile journey only of our users have registered devices that are able to receive push notifications This means that only of our users were affected by this incident We consider ourselves lucky that we were able to expose some of these issues and have this incident remain very contained Since the numbers of users affected was small we decide to proactively reach out to all of those folks via email to apologize and explain why they might have received erroneous notifications Learnings Large PRsLarge PRs naturally come with more risk The bug that kicked off this stream of events was a small change in a very large PR that got missed by multiple folks For starters the diff for the line was not particularly helpful in recognizing the change that caused the issue In addition there were so many lines that it was easy to overlook Breaking down PRs is one way to prevent this However there are times when large wide spread changes need to be made and in those cases you have to rely on your test suite Missing testsThe feature that broke was completely untested Had we been testing that feature properly I think there is a good chance the bug could have been caught Immediately after pushing the hotfix I added a test to ensure this never happens again Technical feature educationAfter fixing the bug none of us working on the problem were well educated about how our Push Notification systems worked Being late on a Friday we skimmed the code and concluded we would be good to go This ended up being the wrong assumption as we later learned Saturday that push notifications unlike app ones are stored and enqueued via Redis I think it s more important than ever that we are somehow sharing and educating each other about some of these larger features as we roll them out Thankfully we do have some great Push Notification documentation but it was never sought out during the incident Is there a way we can make docs like this more visible During the incident we were all heads down in the code should we maybe have some sort of URL link in the code to the docs Being more intentionalI could have very easily reached out to our mobile team on Friday evening to double check that we were in a good state for Push Notifications Once again the whole Friday evening and wanting to be done caused me to accept my assumptions rather than challenge and check them One easy way to prevent something like this is to use a checklist A checklist heavily used in aviation because it has been shown to be key in preventing incidents is an easy way to make sure you never miss something and are deliberate and intentional with your decisions We have great checklists for handling Heroku incidents in our internal Gitbook However we don t have a general incident on call checklist which we plan to add Incident ResponseBefore I dive into specifics I want to point out that this is the first larger incident we have had in a while Incidents being rare is GREAT But it also means that our incident response was a bit rusty and our documented incident processes were a bit out of date to handle this situation Going forward we will be taking a closer look at all of these things to ensure we are keeping them relevant and useful based on the current state of our application and team Broken Comment Creation Reporting FlowThe initial comment creation problem was reported by a DEV user via a GitHub issue and seen about hours later by our internal engineering team GitHub Issues are naturally not a very urgent form of reporting for us since they are handled during working hours One way we could improve this flow would be to further communicate that urgent support issues need to be emailed to yo forem com Our customer success team is always monitoring these channels diligently and could more quickly triage and escalate an issue to the team Manual reporting aside ideally we should have caught this programmatically with our monitoring by alerting on the increased HTTP request errors that were detected Going forward we plan to set up a monitor to alert us for these changes so that we are the first to find out rather than relying on users reporting the issue to us With the proper monitor in place we could have caught this within a couple of hours instead of over a day Broken Push Notifications Reporting FlowWe responded to the broken comment creation issue immediately when it was surfaced however the followup push notification issues were not Our engineer correctly pinged the emergency channel when he realized that we were having problems with notifications but did not escalate the issue and wake up the on call dev via PagerDuty One way we could streamline this process would be to see if we could set up our emergency Slack channel to automatically ping PageDuty when a message is posted Another option is address some of our incident response rustiness by better educating the team on our desired incident response flows This probably needs to be a reoccurring training that happens periodically so as to prevent processes and knowledge from getting stale as our systems evolve Technical RemediationOne delay we encountered when trying to fix this issue was that the Rpush keys were stored in the same Redis instance as our Rails cache Given our Rails cache is massive and contains million keys looping through all of them to find only the Rpush keys was tedious and took a while That cache is also very active which caused us to hit some timeouts when we were trying to perform heavier operations on it We could have mitigated this friction by having either a separate Redis instance for Rpush OR by having those keys in a separate database away from our Rails cache keys Going forward as we grow our mobile platforms I think we should make one of the above changes to ensure that we have easy access to these keys and records It will also ensure that as we grow and scale push notifications we don t have to worry about impacting other systems like our core Rails app Thanks Everyone A lot of people gave up their personal time to come together on Friday and Saturday to mitigate and fix these issues I truly appreciate the amazing team we have at Forem and their dedication to this software We learned a lot about our systems in the process which ensures that this incident will not go to waste I hope others can learn from this as well	2021-07-14 20:53:41
海外TECH	DEV Community	Why Coding Is Crucial To The Future Of Business	https://dev.to/codecast/why-coding-is-crucial-to-the-future-of-business-59gn	Why Coding Is Crucial To The Future Of BusinessKnowing how to understand even basic code can seem foreign and confusing to someone who has never approached it before Programming as a whole can be intimidating to approach because it s vast and varies greatly from industry to industry As we move forward the need for people who can code continues to increase in demand But what makes it such a critical part of business Gone are the days of paper and pen Even if you re a small business and you prefer more traditional approaches to some aspects it s impossible to avoid doing something online But for the most part almost every technical aspect of business is now done online or via technology and more specifically through different kinds of software Of course this means that most businesses need to have a developer at some point But how does coding fit into this picture outside of requiring developers Knowing The What s and The Why sEven if your business doesn t have any developers permanently employed knowing how to communicate what you need from developers is incredibly important While you don t need to know how to code knowing how the moving parts of development works will greatly impact your ability to ask for what you want Additionally being able to have a solid understanding of what is going on on the development side of your business will make the communication between yourself and your team s way more fluid In the current climate it s nearly impossible to have an effective business without an online presence and the demand for a solid online presence is only likely to increase Understanding the behind the scenes will not only aid in communication within large companies but allow smaller businesses to be able to take advantage of the online market effectively Even basic coding courses can allow you to work effectively with low code platforms to be able to create the necessary pieces for your business Small things like being able to update your own website as needed without having to outsource or rely on external help will impact the efficiency of your business as well as frankly make you appear way more professional Realistic Timelines and GoalsComing up with ideas for your business and goals for your company s growth is an essential part of running a good business However often there can be a strong disconnect between what someone wants done and how to get it done This issue is usually seen by looking at projected timelines Perhaps you have a new idea for your business that you want to be able to get out by the end of summer and you approach the developers with that information The developers then respond telling you that with the current workload that deadline is unrealistic Being able to have a sense of what goes into developing something will allow you to create more realistic timelines and allow you to better communicate with your developers to create a timeline that works for both them and the business There are a lot of industries that are known for putting a lot of pressure on their developers to meet set deadlines that sometimes are just not possible If you re familiar with the launch of Cyberpunk you are aware of the type of issues that development timelines can create Cyberpunk was delayed a total of three times with the launch initially anticipated in April of and was eventually released on December th While developmental delays are nothing new in the gaming industry the reason this specific game caught so much attention for its delays was that the game was being advertised and hyped way before it was ready to do so Some developers even came forward to explain what they believed went wrong The greater the people in charge s ability to understand what goes into developing something the greater the chance of your timelines being more accurate for the company as a whole Cyberpunk was unfortunately released with a lot of issues that they are still fixing today In addition they were forced to drop features that had previously been heavily advertised upsetting a lot of people who had pre ordered the game While this is a debated topic in the gaming industry and there is a lot of speculation around what went wrong I chose to use this example because it showcases the importance of good communication and understanding of the moving parts of the business in all aspects Problem Solving SkillsKnowing how to solve problems effectively is an important skill and one that isn t as common as people might think While we have an entire blog coming up about how to think like a programmer for now know that coding teaches you how to problem solve effectively Once you get past learning the language an incredibly large volume of writing code is just solving the how and the why You need to figure out how to make something work despite not having any pieces or perhaps only broken pieces Taking some basic coding courses can help sharpen your brain into learning to think in different ways when looking at a problem It ll train you to break things down and view things from different perspectives Considering a lot of businesses exist to help people overcome a problem or fill in a need it s easy to understand why business and problem solving go hand in hand Coding is also a much more creative field than people think Often you re presented with an idea but how you get from point a to point b is entirely up to you You can give a large group of developers the exact same problem and most of them would solve it differently from one another Learning to approach things in a creative way to come up with solutions is what developers succeed at Patience and ResilienceIf you re going to code you re going to need patience and to be very comfortable with being stuck Even the most senior developers get stuck on problems for days on end completely unsure of how to proceed This was personally one of the most difficult things I had to learn to adjust to when I began to code Learning how to separate being stuck and being “bad at something is a difficult skill to master Coding can have a way of making you feel incredibly dumb But the more you do it the more you realise that you learn a lot in those moments you feel like you know nothing And beyond the actual code you learn how to be patient and push through those moments This is a skill that will help anyone in any aspect of their life but in the ever changing world of business it can be invaluable Regardless of what business or industry you belong to knowing even basic coding skills can make you that much more valuable The online world is only growing as time goes on and with it the need for developers	2021-07-14 20:24:23
Apple	AppleInsider - Frontpage News	Apple becomes first public US company to hit $2.5T market capitalization	https://appleinsider.com/articles/21/07/14/apple-becomes-first-public-us-company-to-hit-25t-market-capitalization?utm_medium=rss	Apple becomes first public US company to hit T market capitalizationAfter a two day rally Apple has hit a new record high stock price and market capitalization of trillion in intraday trading on Wednesday Apple has reached a market capitalisation of trilionShares of the Cupertino tech giant were up more than in trading on Wednesday leading to a market valuation above the trillion threshold for the first time The new high comes a little less than a year after Apple hit trillion Read more	2021-07-14 20:52:19
Apple	AppleInsider - Frontpage News	Apple walks back macOS Monterey tab changes, refines search in iOS	https://appleinsider.com/articles/21/07/14/apple-walks-back-macos-monterey-tab-changes-refines-search-in-ios?utm_medium=rss	Apple walks back macOS Monterey tab changes refines search in iOSApple has made a major change to Safari tabs in the latest macOS Monterey beta reverting the design back to a more familiar layout after receiving feedback from beta testers Credit AppleIn macOS Monterey Apple introduced a new tab system that allowed each individual tab to act as a search and URL field It also nixed the standard URL and search bar that s long been a part of Safari Read more	2021-07-14 20:40:27
Apple	AppleInsider - Frontpage News	Linksys AX4200 Wi-Fi 6 mesh routers gain support for Apple HomeKit	https://appleinsider.com/articles/21/07/14/linksys-ax4200-wi-fi-6-mesh-routers-gain-support-for-apple-homekit?utm_medium=rss	Linksys AX Wi Fi mesh routers gain support for Apple HomeKitLinksys on Wednesday rolled out a firmware update to its affordable Wi Fi routers that delivers support for Apple s HomeKit smart home platform Linksys AX mesh routerAfter a debut in October of the AX ーalso known as the Linksys Atlas Pro Tri band ーhas gained support for HomeKit which brings an additional layer of protection for smart home accessories Read more	2021-07-14 20:32:07
Apple	AppleInsider - Frontpage News	AT&T shows new applications of 5G, from gaming to 'Space Jam'	https://appleinsider.com/articles/21/07/14/att-shows-new-applications-of-5g-from-gaming-to-space-jam?utm_medium=rss	AT amp T shows new applications of G from gaming to x Space Jam x Following a panel with company executives and Ashton Kutcher the telecom giant unveiled a series of partnerships featuring the likes of Harry Potter and the Looney Tunes characters AT amp T s The Future of Today event on July in New York About a year after it first announced that it had deployed its G network to nationwide coverage in the U S AT amp T on Wednesday held an event at the WarnerMedia Innovation Lab to conduct an industry panel and announce and demo a series of new partnerships meant to showcase the maturation of its G network The event one of the first in person press events held by the tech industry in the pandemic era was titled The Future of G Starts Today Read more	2021-07-14 20:19:59
海外科学	NYT > Science	The Space Race for Insurers	https://www.nytimes.com/2021/07/09/business/dealbook/branson-bezos-space-race-insurance.html	demand	2021-07-14 20:40:26
海外ニュース	Japan Times latest articles	COVID-19 cluster emerges at Olympic hotel as delta infections rise	https://www.japantimes.co.jp/news/2021/07/15/national/covid-19-cluster-emerges-olympic-hotel/	COVID cluster emerges at Olympic hotel as delta infections riseJapan confirms new cases of infection with the delta variant in the week ending Monday logging a fold rise from new cases in	2021-07-15 05:53:05
海外ニュース	Japan Times latest articles	Japan will welcome South Korea’s Moon for Olympics visit, ruling party says	https://www.japantimes.co.jp/news/2021/07/15/national/moon-olympics-visit-ldp/	Japan will welcome South Korea s Moon for Olympics visit ruling party saysSouth Korean lawmakers and members of Japan s counterpart group also discussed ways to cooperate for the Tokyo Olympics and Paralympics and improve bilateral relations	2021-07-15 05:09:19
ニュース	BBC News - Home	Covid-19: Ibiza, Majorca and Menorca moved to amber travel list	https://www.bbc.co.uk/news/uk-57839184	amber	2021-07-14 20:08:01
ニュース	BBC News - Home	England political leaders ask for masks to remain on public transport	https://www.bbc.co.uk/news/uk-england-57840575	england	2021-07-14 20:40:13
ニュース	BBC News - Home	Brazil's Bolsonaro in hospital amid concern over chronic hiccups	https://www.bbc.co.uk/news/world-latin-america-57839717	paolo	2021-07-14 20:52:29
ニュース	BBC News - Home	Online racists face football ban of up to 10 years, vows Boris Johnson	https://www.bbc.co.uk/news/uk-politics-57837003	behaviour	2021-07-14 20:50:05
ニュース	BBC News - Home	South Africa A inflict Lions' first loss	https://www.bbc.co.uk/sport/rugby-union/57841466	africa	2021-07-14 20:24:38
ビジネス	ダイヤモンド・オンライン - 新着記事	「郵便局2万4000局vs農協」5番勝負、限界集落“最後の生活インフラ”対決の軍配は？ - 郵政消滅	https://diamond.jp/articles/-/276335	「郵便局万局vs農協」番勝負、限界集落“最後の生活インフラ対決の軍配は郵政消滅郵便局と農業協同組合農協は、共に地方の金融や保険といった社会インフラを支える「最後のとりで」となっている。	2021-07-15 05:25:00
ビジネス	ダイヤモンド・オンライン - 新着記事	日本郵政マル秘名簿で暴く「特定郵便局長ネットワーク」、腐っても鯛の60万集票マシンの内幕 - 郵政消滅	https://diamond.jp/articles/-/276334	浮き彫り	2021-07-15 05:20:00
ビジネス	ダイヤモンド・オンライン - 新着記事	任天堂最高益のカラクリ、今後の注目指標は「デジタル販売」と「有料会員数」 - 決算書100本ノック！ 2021夏	https://diamond.jp/articles/-/276234	需要	2021-07-15 05:15:00
ビジネス	ダイヤモンド・オンライン - 新着記事	武田薬品が「大借金王」の批判を受けても平気な理由 - 決算書100本ノック！ 2021夏	https://diamond.jp/articles/-/276233	有利子負債	2021-07-15 05:10:00
ビジネス	ダイヤモンド・オンライン - 新着記事	“ダメ社労士”の特徴がわかる「6タイプ別・社労士図鑑」、あなたの会社は大丈夫？ - 弁護士 司法書士 社労士　序列激変	https://diamond.jp/articles/-/275542	“ダメ社労士の特徴がわかる「タイプ別・社労士図鑑」、あなたの会社は大丈夫弁護士司法書士社労士序列激変複雑な人事・労務体制を構築する上で、企業の“救世主となるのが社労士だ。	2021-07-15 05:05:00
ビジネス	電通報 | 広告業界動向とマーケティングのコラム・ニュース	テレビCMとTwitterが連動しないなんて、もったいない！	https://dentsu-ho.com/articles/7835	japan	2021-07-15 06:00:00
北海道	北海道新聞	コロナ対策迷走　政権の機能不全　顕著だ	https://www.hokkaido-np.co.jp/article/567190/	新型コロナウイルス	2021-07-15 05:05:00
北海道	北海道新聞	ワクチン接種「自由を」　仏政府の強硬策に抗議デモ	https://www.hokkaido-np.co.jp/article/567248/	抗議デモ	2021-07-15 05:02:55
ビジネス	東洋経済オンライン	任天堂Switch｢5年目の刷新｣に透ける自信と悩み 売れ行きはなお絶好調､ゆえに難しい｢見極め｣ | ゲーム・エンタメ | 東洋経済オンライン	https://toyokeizai.net/articles/-/440819?utm_source=rss&utm_medium=http&utm_campaign=link_back	switch	2021-07-15 05:40:00
ビジネス	東洋経済オンライン	日産が｢背水の勝負｣､電動化で試される存在価値 連続大赤字から｢2つの柱｣で反転攻勢に挑む | 経営 | 東洋経済オンライン	https://toyokeizai.net/articles/-/441005?utm_source=rss&utm_medium=http&utm_campaign=link_back	存在価値	2021-07-15 05:20:00