投稿時間:2021-06-24 23:35:50 RSSフィード2021-06-24 23:00 分まとめ(45件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
Google	Official Google Blog	An updated timeline for Privacy Sandbox milestones	http://feedproxy.google.com/~r/blogspot/MKuf/~3/xf_ku8F0Yhk/	An updated timeline for Privacy Sandbox milestonesToday we re sharing the latest on the Privacy Sandbox initiative including a timeline for Chrome s plan to phase out support for third party cookies While there s considerable progress with this initiative it s become clear that more time is needed across the ecosystem to get this right The Privacy Sandbox initiative aims to create web technologies that both protect people s privacy online and give companies and developers the tools to build thriving digital businesses to keep the web open and accessible to everyone now and for the future To make this happen we believe the web community needs to come together to develop a set of open standards to fundamentally enhance privacy on the web giving people more transparency and greater control over how their data is used  In order to do this we need to move at a responsible pace This will allow sufficient time for public discussion on the right solutions continued engagement with regulators and for publishers and the advertising industry to migrate their services This is important to avoid jeopardizing the business models of many web publishers which support freely available content And by providing privacy preserving technology we as an industry can help ensure that cookies are not replaced with alternative forms of individual tracking and discourage the rise of covert approaches like fingerprinting We plan to continue to work with the web community to create more private approaches to key areas including ad measurement delivering relevant ads and content and fraud detection Today Chrome and others have offered more than proposals and four of those proposals are available in origin trials For Chrome specifically our goal is to have the key technologies deployed by late for the developer community to start adopting them Subject to our engagement with the United Kingdom s Competition and Markets Authority CMA and in line with the commitments we have offered Chrome could then phase out third party cookies over a three month period starting in mid and ending in late  Each proposal goes through a rigorous multi phased public development process including extensive discussion and testing periods This is consistent with how other open APIs and web technologies get developed Discussion The technologies and their prototypes are discussed in forums like GitHub or WC groups Testing The technologies are rigorously tested in Chrome through potentially numerous origin trials allowing for transparency and feedback throughout For example we received substantial feedback from the web community during the origin trial for the first version of FLoC We plan to conclude this origin trial in the coming weeks and incorporate input before advancing to further ecosystem testing Ready for adoption Once the development process is complete the successful technologies are ready to be used at scale They will be launched in Chrome and ready for scaled use across the web After this public development process and subject to our engagement with the CMA our plan for Chrome is to phase out support for third party cookies in two stages Stage Starting late Once testing is complete and APIs are launched in Chrome we will announce the start of stage During stage publishers and the advertising industry will have time to migrate their services We expect this stage to last for nine months and we will monitor adoption and feedback carefully before moving to stage Stage Starting mid Chrome will phase out support for third party cookies over a three month period finishing in late Soon we will provide a more detailed schedule on privacysandbox com where it will be updated regularly to provide greater clarity and ensure that developers and publishers can plan their testing and migration schedules  Along with progress on developing alternatives to third party cookies we continue to advance another key Privacy Sandbox goal to combat covert tracking like device fingerprinting For instance last month we published an update on our plans for User Agent string reduction a project which aims to reduce the possibility of using this data to fingerprint and track users across the web  We believe that the Privacy Sandbox will provide the best privacy protections for everyone By ensuring that the ecosystem can support their businesses without tracking individuals across the web we can all ensure that free access to content continues And because of the importance of this mission we must take time to evaluate the new technologies gather feedback and iterate to ensure they meet our goals for both privacy and performance and give all developers time to follow the best path for privacy	2021-06-24 13:30:00
python	Pythonタグが付けられた新着投稿 - Qiita	自然言語処理のチュートリアル　〜BoWからWord2Vecの理論から自前実装まで〜	https://qiita.com/kuroitu/items/c18129bcdd0c343d16ba	また、dhiddennptiledhiddenxshapereshapexshapeの処理についてですが、順伝播の際に平均を取った部分があったと思いますが、その処理のために行列のサイズが変更されてしまったためコピーするような形で形状を復元しています。	2021-06-24 22:54:14
python	Pythonタグが付けられた新着投稿 - Qiita	【Selenium】PythonでSeleniumを使う際に役に立つ(かも)Tips	https://qiita.com/rk0ym/items/207f33d8e4f7dc610c38	要素をリストで取得する存在しない場合はリストの長さがになるelementsdriverfindelementsbyxpath有無を確認したい要素要素が存在しない場合iflenelements要素が存在しない場合の処理else要素が存在する場合の処理ファイルの保存先を指定するSeleniumを使用してデータを保存したい場合に使用します。	2021-06-24 22:39:34
python	Pythonタグが付けられた新着投稿 - Qiita	Pythone リスト内包表記	https://qiita.com/White_y/items/a502db6d8b6b055759cf	axforxinrangeprinta	2021-06-24 22:37:09
python	Pythonタグが付けられた新着投稿 - Qiita	20代ならIT未経験者がエンジニア転職するのは別に難しくないよという話	https://qiita.com/ykimura517/items/cad1ccee690d92508d01	代ならIT未経験者がエンジニア転職するのは別に難しくないよという話年収アップの為にエンジニアに転職したいけど、IT未経験だから相手にされるか不安専門スキルが高められるIT職を目指したいけど、最初に何をすればいいのかわからないこういった不安を持つ方に向けて記事を書いていきます。	2021-06-24 22:32:49
python	Pythonタグが付けられた新着投稿 - Qiita	Python Psd-Tools	https://qiita.com/sin_hosaki/items/41606c235637b02916a1	PythonPsdTools今回は趣味で製作しているNscripterを使ったゲーム制作をする際に立ち絵が必要だったので立ち絵を用意するためにいろいろ調べたので備忘録として残しておきます使用するファイルは事前にPhotshopで開き名前を付けて保存この際に互換性を優先するのチェックを外した状態で上書きしますこうしないとナゼカうまくいきませんでした調査中ファイルの準備ができたら早速モジュールをインストールpipinstallpsdtools環境の使用準備がこちらpsdexporterpy必要モジュールをインポート画像出力するファイルをオープンfrompsdtoolsimportPSDImagefilepath任意のファイルpsdpsdPSDImageopenfilepath以上で画像出力の準備が完了しました。	2021-06-24 22:24:02
python	Pythonタグが付けられた新着投稿 - Qiita	[kaggle / python] 回帰問題（house prices）の超初歩（４）~数値変数のカテゴリ変数化~	https://qiita.com/siruku6/items/7f3dc5a9932cd82ab860	やったことscore前回今回一部数値特徴量のカテゴリ化Why最初この操作を本やネット上で見かけたとき、なぜ数値を文字列化するのか、なぜこれが効果があるのかわかっていませんでしたが、自分なりに考えた意味合いを記載しておきます。	2021-06-24 22:16:40
js	JavaScriptタグが付けられた新着投稿 - Qiita	都道府県連動の市区町村セレクトボックス	https://qiita.com/fakefurcoronet/items/8984bc078b2511f60cd7	その場合、当然ながら都道府県と市区町村は連動していて欲しい・・・昔から変わらず在る要望なので巷にはサンプルソースが溢れているのですが、HTMLとJavaScriptでなるべく手軽に仕上げたいただしフレームワークはPHPだしかも都道府県だけはDBから書き出したいとは言え選択のたびにサーバーと通信したくはないのでAjaxは嫌だちなみにこの実装にかけられる工数予算はほとんどないといった事を考えていった結果、気軽に流用できずにカスタマイズを行った挙句、工数がかさんでしまっているので、ここに備忘録として残したいと思います。	2021-06-24 22:52:08
js	JavaScriptタグが付けられた新着投稿 - Qiita	javascriptで取得した売り上げデータの重複月を合計する	https://qiita.com/t1k2a/items/5aa946cbfce4eefc6604	javascriptで取得した売り上げデータの重複月を合計する背景売り上げデータをまとめたいが、SQLが得意でない私は上手くGROUPBYできず、サーバー側の権限で設定の変更もできない。	2021-06-24 22:42:46
js	JavaScriptタグが付けられた新着投稿 - Qiita	【Vue.js】トランジション(アニメーション)の使い方	https://qiita.com/yuta-katayama-23/items/287b740aadd15ac1085e	実際にどういう仕組みでVuejsがトランジションを実現しているかについてだが、Vuejsが、暗黙的にlttransitiongtのname属性にenterenteractiveentertoleaveleaveactiveleavetoという接尾辞を付けたのつのクラスを定義し、そのクラス属性をDOMに追加する事でアニメーションが機能するようにしている。	2021-06-24 22:16:55
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	比率を保ったまま収縮するtableを作りたい	https://teratail.com/questions/345933?rss=all	比率を保ったまま収縮するtableを作りたい添付のサイトのように、ビューポートの幅を変えても、正方形の比率を保ったままビューポートに付随するtableとdivを作りたいのですが、どのようなコードを書いたらいいか分かりません。	2021-06-24 22:56:46
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	テキストフィールドに入力された文章を次ページで表示したい。	https://teratail.com/questions/345932?rss=all	テキストフィールドに入力された文章を次ページで表示したい。	2021-06-24 22:53:51
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	指定した複数セルが更新された時にSlackにセルの内容を投稿する	https://teratail.com/questions/345931?rss=all	指定した複数セルが更新された時にSlackにセルの内容を投稿する前提・実現したいことスプレッドシートでしてした複数セル別シートから自動更新されますが更新された時にSlackにその内容を投稿したいのですがうまくいきません、、、。	2021-06-24 22:48:04
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	リストでコードを書いてシンプルにしたいです。	https://teratail.com/questions/345930?rss=all	それぞれの画像を保存する。	2021-06-24 22:41:01
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	【PHP】プルダウンの選択情報をDBから取得したい	https://teratail.com/questions/345929?rss=all	【PHP】プルダウンの選択情報をDBから取得したい前提・実現したいことデータベースのclientsテーブルに登録してある店舗名shopnameをselectタグから選択できるようにし、inputで店舗IDを送信する仕組みを作りたいです。	2021-06-24 22:33:04
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	共有オブジェクトの設計	https://teratail.com/questions/345928?rss=all	オブジェクトは通信している一つ機器の状態を保持しています。	2021-06-24 22:31:50
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	MIPSアセンブリ言語を使ったコンビネーションの計算	https://teratail.com/questions/345927?rss=all	MIPSアセンブリ言語を使ったコンビネーションの計算前提・実現したいことMIPSのアセンブリ言語を使ってコンビネーションnCrの計算を行うプログラムを作成したいです。	2021-06-24 22:24:14
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Swiftで、URLSessionを用いたHTTP通信がうまくいかない	https://teratail.com/questions/345926?rss=all	Swiftで、URLSessionを用いたHTTP通信がうまくいかない前提・実現したいことURLSessionを使ってホットペッパーAPIから店舗情報をJSON形式で取得し、デコードしてインスタンスに入れたい。	2021-06-24 22:23:07
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	最下層のフォルダを上の階層に移動したい	https://teratail.com/questions/345925?rss=all	最下層のフォルダを上の階層に移動したいお世話になっております。	2021-06-24 22:20:42
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	Laravel 多言語対応方法について	https://teratail.com/questions/345924?rss=all	Laravel多言語対応方法について前提・実現したいこと多言語の際にユーザーごとに表示させたい言語を変える方法を探しています。	2021-06-24 22:13:45
Program	[全てのタグ]の新着質問一覧｜teratail（テラテイル）	M5StickCでmillis()を用いて時間計測	https://teratail.com/questions/345923?rss=all	MStickCでmillisを用いて時間計測前提・実現したいことMStick温度センサを用いて℃以上で秒経過するとLED点滅黄色文字警告℃以上で秒経過するとLED点灯赤文警告というプログラムを書きたいのですがうまくカウントが進んでくれません。	2021-06-24 22:07:13
AWS	AWSタグが付けられた新着投稿 - Qiita	Amazon DLMを使ってみた	https://qiita.com/yes_dog/items/3768663c7ba440f015e8	ENABLEDorDISABLEDexecutionrolearn対象のarnを指定policydetailsライフサイクルポリシーの構成を設定最後に所感バックアップスケジュールを作成する際に、タグ名の指定を間違えるとバックアップの処理に失敗するのだが、エラーメッセージなどは特に表示されなかったので、実施後は目視確認が必要だと感じた。	2021-06-24 22:59:45
Docker	dockerタグが付けられた新着投稿 - Qiita	日本語名のディレクトリ内でdocker-compose buildすると失敗する	https://qiita.com/kawaidbz/items/0d26336eeebb719bc43b	ディレクトリ名を「️」とした場合は、buildが失敗した。	2021-06-24 22:30:38
Ruby	Railsタグが付けられた新着投稿 - Qiita	bulk_insertより高速！？postgres-copyで大量データinsertしてみた	https://qiita.com/kk-icare/items/6ece0e23f03bc6a771b9	値が不正なデータinsertallもcopyfromも、Railsのモデルにvalidationを設定していてもバリデーションがスキップされます。	2021-06-24 22:09:32
海外TECH	DEV Community	How to wrap a Preact component into a Stimulus controller	https://dev.to/devteam/how-to-wrap-a-preact-component-into-a-stimulus-controller-1bd0	How to wrap a Preact component into a Stimulus controllerIn this post I m going to illustrate the following wrapping a Preact component inside a Stimulus controllerloading Preact and the component asynchronously on demandcommunicating with the wrapped component via JavaScript custom eventsThis is partly based on work s aitchison did last February on Forem Forem s public website uses Preact and vanilla JavaScript Some of Forem s Admin views are using Stimulus This is an example of how to recycle frontend components from one framework to another I m also assuming the reader has some familiarity with both Preact and Stimulus Wrapping the componentYesterday I was working on some Admin interactions and I wanted to reuse Forem s Snackbar component How it is implemented inside Preact is not important for our purposes and I haven t checked either I just know its module exports Snackbar and a function addSnackbarItem to operate it As the screenshot shows it is similar to Material s Snackbar component as it provides brief messages about app processes at the bottom of the screen With that in mind and with the groundwork laid by Suzanne Aitchison on a different component I wrote the following code import Controller from stimulus Wraps the Preact Snackbar component into a Stimulus controllerexport default class SnackbarController extends Controller static targets snackZone async connect const h render Snackbar await Promise all eslint disable next line import no unresolved import preact import Snackbar render lt Snackbar lifespan gt this snackZoneTarget async disconnect const render await import preact render null this snackZoneTarget Any controller or vanilla JS can add an item to the Snackbar by dispatching a custom event Stimulus needs to listen via this HTML s attribute data action snackbar add document gt snackbar addItem async addItem event const message addCloseButton false event detail const addSnackbarItem await import Snackbar addSnackbarItem message addCloseButton Let s go over it piece by piece Defining a containerstatic targets snackZone Most Preact components need a container to render in In Stimulus lingo we need to define a target which is how the framework calls important HTML elements referenced inside its controller the main class to organize code in This is defined as a regular HTML lt div gt in the page lt div data snackbar target snackZone gt lt div gt Inside the controller this element can be accessed as this snackZoneTarget Stimulus documentation has more information on targets snackZone is just how the Snackbar s container is called inside Forem s frontend code I kept the name D Mounting and unmounting the componentThe Snackbar component when initialized doesn t render anything visible to the user It waits for a message to be added to the stack of disappearing messages that are shown to the user after an action is performed For this reason we can use Stimulus lifecycle callbacks to mount it and unmount it Stimulus provides two aptly named callbacks connect and disconnect that we can use to initialize and cleanup our Preact component When the Stimulus controller is attached to the page it will call the connect method in our case we take advantage of this by loading Preact and the Snackbar component async connect const h render Snackbar await Promise all import preact import Snackbar render lt Snackbar lifespan gt this snackZoneTarget Here we accomplish the following asynchronously load Preact importing its renderer functionasynchronously load Forem s Snackbar componentrendering the component inside the containerTo be good citizens we also want to clean up when the controller is disconnected async disconnect const render await import preact render null this snackZoneTarget This destroys Preact s component whenever Stimulus unloads its controller from the page Communicating with the componentNow that we know how to embed Preact into Stimulus how do we send messages This is where the JavaScript magic lies Generally good software design teaches us to avoid coupling components of any type regardless if we re talking about JavaScript modules Ruby classes entire software subsystems and so on JavaScript s CustomEvent Web API comes to the rescue With it it s possible to lean in the standard pub sub architecture that JavaScript developers are familiar with an element listens to an event handles it with a handler and an action on another element triggers an event The first element is the subscriber the element triggering the event is the publisher With this is mind what are Stimulus controllers if not also global event subscribers reacting to changes First we need to tell Stimulus to listen to a custom event lt body data controller snackbar data action snackbar add document gt snackbar addItem gt data controller snackbar attaches Stimulus SnackbarController defined in the first section of this post to the lt body gt of the page data action snackbar add document gt snackbar addItem instructs the framework to listen to the custom event snackbar add on window document and when received to send it to the SnackbarController by invoking its addItem method acting as en event handler addItem is defined as async addItem event const message addCloseButton false event detail const addSnackbarItem await import Snackbar addSnackbarItem message addCloseButton The handler extracts from the event custom payload the message and a boolean that if true will display a button to dismiss the message It then imports the method addSnackbarItem and invokes it with the correct arguments to display a message to the user The missing piece in our pub sub architecture is the published that is given us for free via the Web API EventTarget dispatchEvent method document dispatchEvent new CustomEvent snackbar add detail message MESSAGE document dispatchEvent new CustomEvent snackbar add detail message MESSAGE addCloseButton false document dispatchEvent new CustomEvent snackbar add detail message MESSAGE addCloseButton true The great advantage is that the publisher doesn t need to inside Stimulus at all it can be any JavaScript function reacting to an action the network the user or any DOM event The CustomEvent interface is straightforward and flexible enough that can be used to create more advanced patterns like the now defunct Vue Events API which provided a global event bus in the page out of scope for this post Demo ConclusionI hope this showed you a strategy of reuse when you re presented with multiple frameworks that have to interact with each other on a page	2021-06-24 13:51:54
海外TECH	DEV Community	How To make your css text look impressive	https://dev.to/orange_abstrakt/how-to-make-your-css-text-look-impressive-1p3l	How To make your css text look impressiveHeadings titles subheadings etc tell the user about your website They also take up a lot of the space So naturally to attract more people and to make your website much more aesthetically beautiful and impressive you can style your text Now which style should you choose This totally depends on your likes and dislikes Try a few and see which one goes best with your site Now without any further ado lets see some simple yet amazing ways of styling your html text Gradient TextGradients add a certain feel to your website that really makes your site stand out Now changing the background to a gradient is fairly simple and common knowledge Text Gradients can be slightly trickier but they are totally worth it Once you have picked the font and set the size you can start coding your gradient text The background property can be set to linear gradient color color Then we clip the gradient to the text The “background clip text is supported in all main browsers with the Webkit prefix it allows a background image to be clipped by a text element Finally you remove the text fill color by setting it to transparent LED textThis gives the element an Led like feel and really helps bring your site to life Set the size for your text and select a font I usually use Brush Script mt for this style as it really adds to the LED theme Once done set the color white looks the best Now comes the interesting part Using the text shadow property we can very easily Make our LED text Now the text shadow takes in maximum values the first is the x offset second is the y offset rd is the blur radius and finally the color For this effect we want the shadow to be at the same position as the text therefore the first values are px Then we add a blur radius of px px and px and set the color to white This makes the center bright Now we add a shadow of a color of our choice with larger blur radii That is all for today Let me know if you want more text designs This is my first post on this website so I wanted to keep it short and see the feedback	2021-06-24 13:45:43
海外TECH	DEV Community	Databunker - a new vault project	https://dev.to/stremovsky/databunker-a-new-vault-project-30pc	Databunker a new vault projectToday I m really excited to share the opensource project we ve been working on at Privacybunker io for a while Databunker Databunker is a special secure vault for customer records It is easy to integrate with the existing code And it matches the needs of privacy by design compliance It can be easily integrated with existing CRMs email marketing services e commerce web sites HR systems and Node js applications It allows following Seamless encryption of customer data You can easily lookup user records by the field email phone token custom index without exposing customer PII data in clear text Automatic privacy compliance in accordance with GDPR CPRA requirements To provide secure storage for personal data Developing a new project Want to target European customers Look no further Our product solves compliance in the most cost effective way We would really appreciate your reviews and will be happy to assist with any questions by mail office privacybunker io	2021-06-24 13:19:42
海外TECH	DEV Community	3 Most Important Metrics For Engineering Team Performance	https://dev.to/alexomeyer/3-most-important-metrics-for-engineering-team-performance-3743	Most Important Metrics For Engineering Team PerformanceCapturing different metrics will help you to measure and visualise your engineering team s performance This article discusses three different metrics you can measure to detect problems like lack of ownership during code reviews technical debt or choking points with key team members Therefore let s look at how we can improve your team s performance Three Important Metrics to Measure Engineering Team PerformanceHere are three important metrics you can measure to understand your engineering team s current performance On top of that these metrics form an excellent basis for further improving your engineering team s performance by continuously measuring their performance Lead TimeLead time refers to the time needed from feature description to feature implementation in the production environment It s a great metric to evaluate the smoothness of your engineering processes For instance processes that cause a lot of friction lack ownership or don t have a clear description will negatively affect the lead time The level of automation is another crucial element that determines your engineering team s lead time For that reason it s a must have metric to track your overall performance On top of that your lead time can help your product team plan new features and their capacity It helps them to make realistic feature roadmaps and allows for clear communication to your clients Also a realistic roadmap puts less pressure on your developers which is good for the overall mood and retention High developer stress is one of the primary reasons why developers decide to look for an alternative job Number of Pull Requests PRs vs Story PointsSome teams prefer to count the number of PRs developers complete per sprint However it s not a great metric to measure because it doesn t represent your team s actual velocity On top of that it s not a fair metric as some developers prefer to create smaller PRs and senior developers will often complete more PRs The same is valid for counting the number of commits per sprint It s not a metric that you can easily compare week by week Therefore it s better to assign story points to each issue so you can measure the total number of story points you complete per sprint You can then map this number week by week to get a graph Story points provide an effective way to detect technical debt In other words measuring sprint velocity is a great strategy to make technical debt more visible It s important to quickly detect the on ramp of technical debt as it has a significant impact on your team s performance in the long run To make technical debt visible add bookmarks and TODOs to your code and collaborate with your team on maintenance work try out Stepsize VS Code and JetBrains extensions Time to Complete a Code ReviewYou may have many automated processes to deploy your code to a test environment and run tests against it However code reviews can still slow you down Therefore you should measure the time needed to complete a code review Often pull requests lack clear ownership or the process lacks clear acceptance criteria In these situations teams don t know when a pull request is ready to be accepted or not This uncertainty will slow down the review process Also many teams have more experienced developers who take care of most code reviews They can easily get overwhelmed by all the pull requests they have to review besides their work It s a major blocker for development teams who put too much stress on their senior developers For that reason it s important to diversify the knowledge across multiple developers so not only your senior developers are responsible for accepting pull requests In short track who s doing code reviews and how long it takes to accept pull requests into your codebase It will help you to understand choking points that slow down your team s code review completion time How to Improve Your Engineering Team s Productivity Here is a list of items to take note of to improve your engineering team s productivity Clear OwnershipWhen doing a code review it s essential to tag the right people to review your code As a best practice you want to tag at least one person that has a good understanding of the part of the codebase you re working on Moreover you should tag at least one other developer who knows less about this specific code so they can review if the code meets the style guide and acceptance criteria This approach makes sure that at least one other developer learns about a specific part of the code to avoid technical debt Many teams lack clear ownership for code reviews because they don t know who to tag for their review Avoid this at all costs Internal DocumentationInternal documentation explains key concepts like your project s architecture tools and technologies On top of that it should be a living document that reflects the current state of your codebase Documentation helps your team to make better strategic decisions about your code and improve your code quality Retrospective Meetings to Boost Knowledge SharingWeekly or bi weekly retrospective meetings allow your team to share progress updates and technical knowledge Often teams will pick one or multiple developers to showcase important code snippets or architectural design decisions that affect all developers in your team It s a great moment to actively share knowledge in an informal setting Often junior developers perceive a barrier in regards to asking for additional explanations from senior developers Therefore a retrospective meeting can remove this barrier and boost knowledge sharing across your team Lastly retrospective meetings help teams to discuss problems and propose solutions For instance a particular pull request took seven days to merge instead of the maximum three day rule You try to reason what went wrong and draw conclusions from the mistake Each meeting should have a couple of working points for the team to review during the next meeting to see if the problem has been resolved and the team improved its performance How to Get Started Don t expect immediate results from measuring several metrics related to your team s performance It s important to consistently measure these metrics and plot them on a graph to get better insights You ll only be able to draw conclusions after a couple of weeks of collecting data It s a big mistake to give up early on measuring team performance data because you don t see immediate results or can t conclude If you want to improve your personal productivity I highly recommend checking out these VS Code extensions that my engineering team is using	2021-06-24 13:04:14
海外TECH	DEV Community	Software Engineers Need to Know DevOps Too, and That Starts with CI/CD	https://dev.to/thawkin3/software-engineers-need-to-know-devops-too-and-that-starts-with-ci-cd-47n8	Software Engineers Need to Know DevOps Too and That Starts with CI CDDevOps is hot right now It seems like every software engineering job posting requires DevOps experience and expertise regardless of the actual job title When a tech company breaks up its monolith into microservices each of its engineering teams now owns their portion of the application from start to finish Software engineers no longer just build the application they also own repo maintenance set up continuous integration configure build pipelines and deploy their application In this world of cross functional teams and microservice architecture DevOps skills become increasingly important and that starts with understanding CI CD continuous integration continuous delivery and continuous deployment In this article we ll talk about best practices for CI CD and how platforms like Armory can help manage some of the complexity involved Continuous Integration CI Continuous integration CI is the “practice of automating the integration of code changes from multiple contributors into a single software project As multiple developers are merging code into the master branch daily it s important to have automated checks in place to ensure that the code is always in a good working state This means that code formatters code linters and unit tests should be run prior to merging new code Rather than relying on developers to remember to use these tools locally CI pipelines help automate running each required job preventing bad code from being merged into the master branch Good CI pipelines should be fast That means running pipeline jobs in parallel when possible and having a fast test suite Good CI pipelines should also be reliable If the build is broken engineers should work to fix it immediately as a build failure would block all open merge requests from being merged If a test is flaky it should be temporarily disabled and fixed as soon as possible The app should be built once near the beginning of the CI pipeline after any formatters linters and unit tests are run This way the build artifact is ready to be used anywhere in subsequent stages of the pipeline The build artifact can then be deployed in a containerized environment and used as a review app for code reviewers to quickly validate changes when needed When CI pipelines are successfully set up for a code repo developers can commit to the master branch daily or even several times per day No more long running feature branches that live for months waiting for the day that they can finally be merged Following these CI practices helps keep everything in the master branch clean and in a deployable state at all times which leads us to the second half of the CI CD acronym Continuous Delivery and Continuous Deployment CD As a brief aside let s talk about the differences between “continuous delivery and “continuous deployment Continuous delivery is a natural result of generating a build artifact as part of continuous integration This build artifact is a working copy of the app that can be deployed to an environment That means you re ready to deploy to production anytime As an engineering organization you can decide whether to deploy daily weekly every two weeks and so on In continuous delivery while you re prepared to deploy your app at any moment a human still needs to kick off the process to start the deployment Continuous deployment however goes a step further than continuous delivery in that every change that gets merged into the master branch will immediately begin the deployment process without any further human interaction This is exciting because developers can see their code in production just minutes after they ve merged it Assuming of course that the deployment isn t blocked by any failing automated checks which would prevent the new build from being released into the production environment Whether your organization chooses continuous delivery or continuous deployment the intent of both practices is the same deliver value to your customers as quickly and as frequently as possible No more big quarterly releases This is what being agile is all about One of the most important things to get right with continuous delivery is that the app should be able to be deployed with the click of a single button In other words the deployment process should be automated If this practice isn t followed and there are multiple complicated steps in the deployment process that must be carried out by a human the deployment process becomes more prone to error After all we are human and humans make mistakes Another key principle of both continuous delivery and continuous deployment is that you should use multiple levels of environments in which the app can run For instance you might have a development environment a staging environment and a production environment The build artifact can then be promoted from one environment to the next during the deployment process The infrastructure in these various environments should be as similar as possible so that you don t run into major surprises once the app gets into production Deployment StrategiesDeployment strategies can vary but some commonly used techniques are canary deployments blue green deployments and rolling blue green deployments In a canary deployment you first release the new version of your app to a small subset of users Once you are comfortable that the changes work properly for those users you release the changes to the rest of your users as well This is considered a cautious way to release code as you don t initially apply the changes for everyone all at once In a blue green deployment you use two production grade environments One environment is actively used in production and contains the current version of the app The second environment is on standby and has no traffic routed to it You deploy the new version of your app to the standby environment and then route all traffic to this environment which makes it the new production environment The old production environment then no longer receives traffic and becomes the standby environment This makes it very easy both to deploy a new release and also to rollback a release when needed because both processes are as simple as redirecting where the user traffic goes A rolling blue green deployment can be used when you have multiple instances of your application all running in the same environment For example if you have six nodes used in production swap out the first node with another node that is running the new version of the application So now you have five nodes running the old version of the app and one node running the new version of the app Then you do it again so that the ratio becomes four old and two new After four more node replacements now all six of your nodes are running the new version of the application The rolling nature of the deployment is both a pro and a con The deployment is less risky as you don t deploy everything at once but it also takes more time to complete the full release since it s done one node at a time Various deployment strategies Source How Tools Can Help with CI CDNow that we understand best practices for CI CD what tools can we use to help us For CI there are many good open source options like Travis CI or CircleCI You can even use the built in features of GitHub with GitHub Actions or GitLab with GitLab CI Most of these tools specialize in the CI part of CI CD but also include some features for CD With these CI tools you can create pipelines that take care of running your linters and tests on every new merge request When it comes to CD one of the most popular open source tools that helps automate deployments is Spinnaker Spinnaker was originally developed internally by Netflix before it was released to the broader developer community One of the best things about Spinnaker is its flexibility in supporting just about every cloud provider from AWS to Azure to GCP Spinnaker can be integrated with your CI tool of choice and can deploy your app using your chosen deployment strategy I already mentioned that it s flexible right An example pipeline for a canary deployment using Spinnaker might look a little something like this Canary deployment strategy pipeline Source In this workflow we see the build artifact deployed to a small cluster of server groups for the initial canary deployment After the functionality changes in the canary deployment have been manually reviewed and approved a blue green deployment is done or red black deployment as Netflix calls it by deploying a new prod cluster and using the load balancer to direct traffic to this new group The canary cluster is then torn down and ーafter everyone is comfortable that the new prod cluster is working well ーthe old prod cluster is destroyed too Armory is a platform that takes this idea one step further by providing an enterprise grade offering of Spinnaker for better visibility developer empowerment and resilience Armory s dashboards logging and live metrics help give developers more visibility into their app deployments With much of the complexity abstracted away into a nice GUI deployments and rollbacks can be executed with the click of a button This enables even those developers without much DevOps experience to own their app from start to finish And just to give you an added measure of confidence Armory s Policy Engine allows you to configure guardrails to ensure that every deployment follows your company s best practices and agreed upon rules ConclusionSo what have we learned First developers need to be acquainted with CI CD best practices Second engineering organizations need to provide their developers with the right tools to help increase productivity and reduce errors As we ve seen one of the best tools used for CD is Spinnaker now enhanced by Armory By working together to implement these DevOps principles engineering teams will have greater confidence in their code and will be enabled to deliver value to their customers faster	2021-06-24 13:00:55
Apple	AppleInsider - Frontpage News	Apple begins crackdown on leakers from China	https://appleinsider.com/articles/21/06/24/apple-begins-crackdown-on-leakers-from-china?utm_medium=rss	Apple begins crackdown on leakers from ChinaKnown leakers Kang and Duan Rui both say that Apple has sent letters demanding that they stop revealing details of future products and warning of legal action in China if they don t Apple begins crackdown on leakers in ChinaAccording to social media posts Apple s letters demand that the leakers can t disclose information about unreleased products since this may mislead potential customers and give competitors an advantage Apple has also reportedly demanded that leakers must refrain from posting any images and cannot refer to posts as dreams or riddles since these are still seen as leaks Read more	2021-06-24 13:33:11
Apple	AppleInsider - Frontpage News	Andreessen Horowitz launches $2.2 billion crypto fund	https://appleinsider.com/articles/21/06/24/andreessen-horowitz-launches-22-billion-crypto-fund?utm_medium=rss	Andreessen Horowitz launches billion crypto fundVenture Capital firm Andreessen Horowitz is launching a new billion fund to invest in cryptocurrency stating that they are radically optimistic about crypto s potential The firm founded by Marc Andreessen and Ben Horowitz is known for being an early investor in companies such as Facebook and Instagram It now plans on investing in cryptocurrency which it sees as the future of finance and a highly influential technology We believe that the next wave of computing innovation will be driven by crypto firm partners Katie Haun Ali Yahoo and Chris Dixon wrote in a blog post Read more	2021-06-24 13:30:45
海外TECH	Engadget	Google delays the rollout of its third-party cookie replacement to mid-2023	https://www.engadget.com/google-delay-third-party-cookie-150034054.html?src=rss_b2c	changes	2021-06-24 13:37:09
海外TECH	Engadget	What Neuralink and other BCIs can and can't do	https://www.engadget.com/what-neuralink-and-other-bc-is-can-and-cant-do-140014162.html?src=rss_b2c	What Neuralink and other BCIs can and can x t doElon Musk s BCI startup wants to make people more than human by putting computers in their heads but a number of neurology researchers aren t quite so bullish on these fantastical promises	2021-06-24 13:30:14
ニュース	BBC News - Home	Woman dies after Scottish cancer screening error	https://www.bbc.co.uk/news/uk-scotland-57596250	cervical	2021-06-24 13:42:29
ニュース	BBC News - Home	Dalian Atkinson: Jury fails to reach decision about second officer	https://www.bbc.co.uk/news/uk-england-shropshire-57595434	atkinson	2021-06-24 13:57:36
ニュース	BBC News - Home	Kent all-rounder, 45, signs new contract	https://www.bbc.co.uk/sport/cricket/57598307	class	2021-06-24 13:16:18
ニュース	BBC News - Home	Silverstone to be allowed 140,000 capacity crowd for British Grand Prix	https://www.bbc.co.uk/sport/formula1/57598221	Silverstone to be allowed capacity crowd for British Grand PrixA capacity crowd will be allowed to attend the British Grand Prix at Silverstone on July after the race was added to the UK government s Events Research Programme	2021-06-24 13:43:37
ニュース	BBC News - Home	Uefa scraps away goals rule in European club ties	https://www.bbc.co.uk/sport/football/57599780	european	2021-06-24 13:49:31
ニュース	BBC News - Home	Tokyo Olympic Games: When are they and will they go ahead despite Covid?	https://www.bbc.co.uk/news/world-asia-57240044	japan	2021-06-24 13:06:09
ビジネス	ダイヤモンド・オンライン - 新着記事	アスカ(7227)、｢増配｣を発表し、配当利回り2.4％⇒ 3.1％に！ 年間配当は1年で1.8倍にアップ、2021年 11月期は前期比14円増の｢1株あたり30円｣に増額へ！ - 配当【増配・減配】最新ニュース！	https://diamond.jp/articles/-/275043	アスカ、「増配」を発表し、配当利回り⇒に年間配当は年で倍にアップ、年月期は前期比円増の「株あたり円」に増額へ配当【増配・減配】最新ニュースアスカが、年月期の配当予想の修正増配を発表し、配当利回りがにアスカは、年月期の年間配当を前回予想比で「円」の増配、前期比では「円」の増配となる「株あたり円」に修正すると発表した。	2021-06-24 22:02:00
LifeHuck	ライフハッカー［日本版］	犯した過ちで自分を責めてはいけない理由	https://www.lifehacker.jp/2021/06/how-to-separate-your-identity-from-your-behavior-and-w.html	過ち	2021-06-24 22:05:00
北海道	北海道新聞	西川氏に出馬要請で調整　立憲道６区総支部　引退の佐々木氏後任	https://www.hokkaido-np.co.jp/article/559487/	佐々木氏	2021-06-24 22:19:36
北海道	北海道新聞	国内で１６７６人感染　４２人死亡、新型コロナ	https://www.hokkaido-np.co.jp/article/559488/	新型コロナウイルス	2021-06-24 22:09:00
北海道	北海道新聞	小此木公安委員長、２５日に辞任　五輪警備担当閣僚が直前交代	https://www.hokkaido-np.co.jp/article/559425/	神奈川区	2021-06-24 22:08:57
ビジネス	東洋経済オンライン	豊田章男社長が未来への投資に｢私財50億円｣ トヨタ自動車の変革に異例のコミットメント | 経営 | 東洋経済オンライン	https://toyokeizai.net/articles/-/436758?utm_source=rss&utm_medium=http&utm_campaign=link_back	東洋経済オンライン	2021-06-24 22:30:00