IT |
ITmedia 総合記事一覧 |
[ITmedia ビジネスオンライン] 小中高生が選ぶ今年の漢字 3位「推」2位「恋」、1位は? |
https://www.itmedia.co.jp/business/articles/2212/10/news033.html
|
itmedia |
2022-12-10 08:15:00 |
AWS |
AWSタグが付けられた新着投稿 - Qiita |
re:Invent 2022 コンピューティング関連の新サービス、アップデートまとめ |
https://qiita.com/nidcode/items/c69aaa33f78e41efe348
|
amazonecawsnitrov |
2022-12-10 08:43:47 |
海外TECH |
DEV Community |
Has a Company Ever Rescinded Your Offer Letter? |
https://dev.to/sloan/has-a-company-ever-rescinded-your-offer-letter-12mn
|
Has a Company Ever Rescinded Your Offer Letter This is an anonymous post sent in by a member who does not want their name disclosed Please be thoughtful with your responses as these are usually tough posts to write Email sloan dev to if you d like to leave an anonymous comment or if you want to ask your own anonymous question So I was contacted by PandaDoc because they were to expand their software team Since they don t have offices on my country They used a third party deel for managing the legal aspect On Monday I received the offer letter through this third party But didn t receive email from the recruiter I pinged her and we scheduled a meeting on Thursday In the meantime I booked train tickets My manager lives in a different city h by train and I wanted to give him the letter personally Love the details The meeting with PandaDoc s HR she told me that despite of they were extremely happy with my selection process nothing but positive feedback they were cancelling the offer She explained that they were entering in hiring freeze I wasn t supposed to receive the offer letter I m sorry Since Monday I ve already changed job I mean mentally This is the worst part I m not focused on my current job at all Cancelling an offer once I ve received the letter is the most dirty thing I ve suffered in a selection process Has anyone else experienced something similar If so would you be willing to share your experience Thanks for reading |
2022-12-09 23:17:01 |
海外TECH |
DEV Community |
What is Continuous Merge? |
https://dev.to/linearb/what-is-continuous-merge-3m5h
|
What is Continuous Merge Despite the workflow improvements that have been made with CI CD there are huge bottlenecks found in the pull request and code review process These bottlenecks can be removed with continuous merge a set of processes that make pull requests easier to pick up and code reviews quicker to merge Let s look deeper into what continuous merge is why it s needed and how to implement it with automation tools like gitStream The State of CI CDPlain and simple Continuous integration continuous delivery CI CD has become standard practice for rapidly delivering new software features bug fixes and enhancements Continuous integration CI is where developers merge individual code contributions into a central repository where automated tests and builds are executed Continuous delivery CD automates code change deployment to testing and production environments Continuous deployment ーa term often confused with continuous delivery ーis the final step of the DevOps pipeline where all changes that successfully pass the production pipeline are released to customers CI CD automates every step of the development process ensuring products and features are shipped to users almost as fast as they re developed But it does have drawbacks Where CI CD Can Be ImprovedMany branches often extend from the central repository when multiple software developers work simultaneously on a large codebase Branches with long lifetimes the period between review and merging impede the performance improvement that agile practices like CI CD seek to achieve Inefficiencies in the pull request PR process create bottlenecks in the delivery pipeline especially when code reviews take days to complete For optimum CI CD performance there should be at most three branches with lifetimes no longer than a day before merging with the trunk But in most software development environments this is virtually unheard of Pull request reviews that take days or weeks have significant cost implications Besides work backlogs delayed reviews can trigger complex merge conflicts Even worse pull requests come before integrated testing in the CI CD pipeline so a successful review doesn t guarantee a similar outcome later The solution to these bottlenecks in the pipeline is continuous merge Continuous Merge DefinitionContinuous merge is a set of processes that help eliminate the bottlenecks plaguing pull requests and code reviews The standard practice for engineering projects is to manage the code base through a version control system VCS where developers and contributors can collaborate It s common for VCS repositories to have one or more branches and in traditional PR reviews changes to the code require manual checking before merging into the main branch Understanding Why Continuous Merge is NeededA typical code review involves a contributor or developer opening a pull request and informing other collaborators that code changes have been pushed to a branch and require reviewing and subsequent approval before merging into the main branch PRs enable collaborators typically lead or senior developers to check the changes for quality adherence and then take one of these three actions Comment on the proposed changes Approve the changes Request further changes before merging the branch Many many inefficiencies characterize this process often resulting in PRs taking longer than is ideal For example The collaborator may begin reviewing the PR only to pause prematurely to attend to other responsibilities The process freezes because developers don t get feedback nor is the merge executed If the repository has many branches with multiple contributors the entire CI CD pipeline may be affected introducing the risk of merge conflicts and reduction of developer productivity Other issues that slow down traditional reviews include PRs being too long Overwhelmed teams Diversion of collaborators to other tasks orSub optimal assignment of PRs to people such that the desired outcome is not achieved in the initial request Many gaps in this process necessitate re engineering the PR review process to eliminate such inefficiencies How Continuous Merge Creates Frictionless Code ReviewA pull request also known as a merge request is where developers or contributors indicate that code changes are ready for merging into the project s main repository It is an industry standard practice for other developers team leads and other parties to review code changes before merging human input into this process is inevitable Historically this pull request process has caused inefficiencies particularly review delays as the process is not automated so speed depends on the availability of the right code reviewer Continuous merge seeks to improve the pull request review process by introducing a layer of automation that enables automatic approval and efficient routing of complex pull requests to relevant reviewers Continuous merge considers the unique characteristics of individual pull requests and routes them appropriately on a risk based model ensuring process optimization and bottleneck reduction Continuous merge categorizes pull requests and code reviews according to their characteristics ーtype code complexity and size This creates automatic pull request lanes that boost merge speed and efficiency The Crucial Steps to Continuous Merge Step Provide Context to Pull Requests that Make Them Easier to Pick UpThe first step is to understand the context of the pull request Pull requests are treated equally by most version control systems which provide the same information for each one ーnot enough for a reviewer to assess their size or complexity Continuous merge adds a contextual layer with more information like the estimated review time the concerned project component and the pull request owner Step Treat Pull Requests Differently Depending on Their Size and CharacteristicsThe second step involves classifying pull requests according to this contextual information This process acknowledges that pull requests vary in size ーsome are just a few lines of code and others are chunky Despite this pull requests go through a similar process and even those that could be completed quickly may extend for days before the review The routing step of continuous merge seeks to remedy such inefficiencies by relying on PR classification to send pull requests with a few lines of code for near instantaneous reviews and approval The WorkerB Chrome extension for pull requests simplifies creating and delivering context enriched pull requests to code reviewers Step Streamline Pull Requests with Low RiskThe third and final step of continuous merge is to apply rule based automation and tooling to achieve automatic approvals and merges for low risk pull requests while optimizing the routing of others based on their level of risk Why Continuous Merge Beats Traditional MergeThe traditional merge workflow involves strictly defined steps with all pull requests ーwhether five lines or a critical change of lines ーprocessed the same way Similarly changes to static files which can be approved and merged automatically are processed through the same pipeline When code reviews are delayed for days there s a greater risk of merge conflicts and idle time between pull request reviews can lead to a drop in developer productivity Continuous merge in contrast addresses these CI CD pipeline bottlenecks by contextualizing PR requests and classifying them via a model that has been defined by the team And following standard DevOps practices pull requests are placed in appropriate lanes for continuous merge through automated tools How to Easily Implement Continuous Merge on Your TeamNew tools are emerging to support continuous merge and combat CI CD bottlenecks gitStream helps you implement continuous merge gitStream deviates from the standard code review process by automating merge approvals for small low risk pull requests and routing other types of code change to appropriate reviewers The tool uses a rule based automation model that empowers both developers and reviewers Continuous merge also tries to ensure that the reviews go to the most appropriate people so there needs to be thought given to the type of code and who is assigned to review it You can create automation rules in a cm file to provide parameters and constraints that dictate how code is reviewed and subsequently merged This file improves PR classification allowing reviewers to gain more context on the PR request so they can prioritize reviews according to characteristics like complexity and size Here s an overview of how gitStream delivers continuous merging through the rules specified in the cm file Auto approval of pull requests containing small code changes that have passed unit testing successfullyAutomatic assignment of pull requests to appropriate individual reviewers according to code complexity estimated review time and reviewer expertiseAutomatic assignment of pull requests containing critical changes to the ideal review teams through the codification of custom rulesGetting started with gitStream is straightforward because the tool integrates seamlessly with your remote repositories To set up gitStream on GitHub for example you can follow these three simple steps The cm cm gitstream cm file enables custom automation constructs including defining context variables filter functions that can be called on the context variables and automation actions triggered when all conditions rules are satisfied The gitStream engine runs the custom automation defined in the cm file The engine supports some common actions including add comment add label add reviewers approve merge set required approvals and require reviewers Continuous Merge Completes the Promise of CI CDTraditional PR reviews and merge workflows tend to create bottlenecks in the CI CD process Code reviews and approvals can cause delays for days even when some are low risk and could be resolved quickly Because all pull requests are processed the same way improvements to the efficiency of this process have yet to be made Continuous merge is a promising solution to these challenges With continuous merge developers can create custom rules to accompany their pull requests optimizing the review process Check out this talk from our Director of Developer Experience Luke Kilpatrick to learn more about continuous merge and and gitStream Want to cut code review time by up to Add estimated review time to pull requests automatically gitStream is the free dev tool from LinearB that eliminates the No bottleneck in your team s workflow pull requests and code reviews After reviewing the work of dev teams LinearB s engineers and data scientists found that pickup times and code review were lasting to days longer than they should be The good news is that they found these delays could be eliminated largely by adding estimated review time to pull requests Learn more about how gitStream is making coding better HERE |
2022-12-09 23:01:39 |
海外科学 |
NYT > Science |
Winter Weather Havoc Is Expected to Make a Cross-Country Run |
https://www.nytimes.com/article/winter-storm-snow-west-northern-plains.html
|
Winter Weather Havoc Is Expected to Make a Cross Country RunA “major storm system approaching the Pacific Coast is forecast to rumble across the U S dealing feet of snow in the West blizzard conditions in the Northern Plains and tornadoes across the South forecasters say |
2022-12-09 23:35:06 |
金融 |
金融総合:経済レポート一覧 |
FX Daily(12月8日)~137円台前半で上値が重い |
http://www3.keizaireport.com/report.php/RID/519441/?rss
|
fxdaily |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
米長期金利低下の背景整理 中国のゼロコロナ戦略見直しなら金利上昇も:Market Flash |
http://www3.keizaireport.com/report.php/RID/519445/?rss
|
marketflash |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
暗号資産ウォレットの衝撃~暗号資産取引所の破綻への備え:Watching |
http://www3.keizaireport.com/report.php/RID/519447/?rss
|
watching |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
FTXのずさんな経営実態がより明らかにされることが、暗号資産市場全体の信頼回復の足掛かりとなるか:木内登英のGlobal Economy & Policy Insight |
http://www3.keizaireport.com/report.php/RID/519449/?rss
|
lobaleconomypolicyinsight |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
つみたてNISAの買付は計画的に~2022年11月の投信動向:研究員の眼 |
http://www3.keizaireport.com/report.php/RID/519452/?rss
|
買付 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
内外経済とマーケットの注目点(2022/12/9)~米国では景気後退懸念が高まり、中国は「ゼロコロナ」政策を緩和:金融・証券市場・資金調達 |
http://www3.keizaireport.com/report.php/RID/519458/?rss
|
大和総研 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
フォースタートアップス(東証グロース)~スタートアップ企業を人材資源の側面から支援するための様々なサービスを展開。23年3月期は積極的な人材採用に伴う費用増により小幅な営業減益見込み:アナリストレポート |
http://www3.keizaireport.com/report.php/RID/519482/?rss
|
資源 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
AIAIグループ(東証グロース)~認可保育園や小規模保育施設などの運営を行うチャイルドケア事業が主力。既存施設の園児数増加により24年3月期の営業黒字化を見込む:アナリストレポート |
http://www3.keizaireport.com/report.php/RID/519483/?rss
|
小規模保育 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
トレンドを知る:メタバースにおけるペイメントの検討 |
http://www3.keizaireport.com/report.php/RID/519487/?rss
|
発表 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
教育資金をどのように準備すればよいのでしょうか? |
http://www3.keizaireport.com/report.php/RID/519500/?rss
|
教育資金 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
リテール証券業は成長する~証券会社経営の未来(8)・最終回 |
http://www3.keizaireport.com/report.php/RID/519504/?rss
|
証券会社 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
FRBのタカ派的金融政策:1970年代の失敗と代償の回避が指針に |
http://www3.keizaireport.com/report.php/RID/519506/?rss
|
資本市場 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
最後に残った有望リスク資産、日本株式 |
http://www3.keizaireport.com/report.php/RID/519508/?rss
|
資本市場 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
From the Corner of Wall Street(第41回)米国取引所の排出量取引に関する取組み状況 |
http://www3.keizaireport.com/report.php/RID/519510/?rss
|
fromthecornerofwallstreet |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
店頭デリバティブ取引等の規制に関する内閣府令第4条第1項で定める作成・保存・報告事項ガイドライン(案) |
http://www3.keizaireport.com/report.php/RID/519512/?rss
|
内閣府令 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
ベトNow!vol.1~世界的な株安の中で、バリュエーションが魅力的なベトナム株式 |
http://www3.keizaireport.com/report.php/RID/519514/?rss
|
nowvol |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
マーケットフォーカス(米ドル建債券市場)2022年12月号 |
http://www3.keizaireport.com/report.php/RID/519516/?rss
|
三井住友トラスト |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
投資INSIDE-OUT vol.224「若年層の証券取引の特徴とは~変化する資産形成(1)~」 |
http://www3.keizaireport.com/report.php/RID/519517/?rss
|
insideoutvol |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
歴史的な下落局面と似た動きが続く米国株:市川レポート |
http://www3.keizaireport.com/report.php/RID/519518/?rss
|
三井住友 |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
フェア・ディスクロージャーとは何か:米国の最新事例から:大崎貞和のPoint of グローバル金融市場 |
http://www3.keizaireport.com/report.php/RID/519525/?rss
|
pointof |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
【注目検索キーワード】トップマネジメント |
http://search.keizaireport.com/search.php/-/keyword=トップマネジメント/?rss
|
検索キーワード |
2022-12-10 00:00:00 |
金融 |
金融総合:経済レポート一覧 |
【お薦め書籍】世界2.0 メタバースの歩き方と創り方 |
https://www.amazon.co.jp/exec/obidos/ASIN/4344039548/keizaireport-22/
|
宇宙開発 |
2022-12-10 00:00:00 |
ニュース |
BBC News - Home |
Prince Harry and Meghan say they didn't step back over privacy concerns |
https://www.bbc.co.uk/news/uk-63922657?at_medium=RSS&at_campaign=KARANGA
|
royal |
2022-12-09 23:29:23 |
ニュース |
BBC News - Home |
Ukraine war: US says Russia and Iran in full defence partnership |
https://www.bbc.co.uk/news/world-europe-63921007?at_medium=RSS&at_campaign=KARANGA
|
joint |
2022-12-09 23:09:52 |
ニュース |
BBC News - Home |
The Papers: UK 'hostage' to strikes and 'World Cup le crunch' |
https://www.bbc.co.uk/news/blogs-the-papers-63925018?at_medium=RSS&at_campaign=KARANGA
|
The Papers UK x hostage x to strikes and x World Cup le crunch x Saturday s front pages focus on the potential impact of upcoming strikes and England s World Cup quarter final match against France |
2022-12-09 23:20:54 |
ニュース |
BBC News - Home |
Biodiversity: What is a mass extinction and are we causing one? |
https://www.bbc.co.uk/news/science-environment-63875331?at_medium=RSS&at_campaign=KARANGA
|
biodiversity |
2022-12-09 23:38:19 |
ニュース |
BBC News - Home |
How to be a former prime minister |
https://www.bbc.co.uk/news/uk-politics-63791816?at_medium=RSS&at_campaign=KARANGA
|
ministertwo |
2022-12-09 23:49:32 |
ニュース |
BBC News - Home |
World Cup 2022: Watch every penalty as Argentina beat the Netherlands to reach semi-finals |
https://www.bbc.co.uk/sport/av/football/63925149?at_medium=RSS&at_campaign=KARANGA
|
finals |
2022-12-09 23:24:36 |
ビジネス |
ダイヤモンド・オンライン - 新着記事 |
アップル元幹部、TikTok発言での解雇に反論 - WSJ発 |
https://diamond.jp/articles/-/314311
|
tiktok |
2022-12-10 08:19:00 |
ビジネス |
不景気.com |
大和ハウスがリゾートホテル事業から撤退、子会社を売却 - 不景気com |
https://www.fukeiki.com/2022/12/daiwa-house-royal-hotel.html
|
大和ハウス |
2022-12-09 23:16:22 |
Azure |
Azure の更新情報 |
Public preview: Processor diagram in Physical Job Diagram for Stream Analytics job troubleshooting |
https://azure.microsoft.com/ja-jp/updates/public-preview-processor-diagram-in-physical-job-diagram-for-stream-analytics-job-troubleshooting/
|
Public preview Processor diagram in Physical Job Diagram for Stream Analytics job troubleshootingThe processor diagram in physical job diagram provides you further insights within the streaming nodes of your stream analytics jobs |
2022-12-09 23:53:31 |
ニュース |
THE BRIDGE |
バーチャルヒューマンを世界で量産するDeepBrain AI、時価総額は1.8億米ドルに到達(2/2) |
https://thebridge.jp/2022/12/howie-mandel-gets-a-digital-twin-from-deepbrain-ai-2
|
バーチャルヒューマンを世界で量産するDeepBrainAI、時価総額は億米ドルに到達前半からのつづきScripttoVideo機能に加えて、同社はAIHumanソフトウェアで完全な会話体験を提供している。 |
2022-12-09 23:01:17 |
コメント
コメントを投稿