投稿時間:2023-02-05 13:05:32 RSSフィード2023-02-05 13:00 分まとめ(7件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	気になる、記になる…	Twitter、企業向けの金色認証バッジの料金を月額1,000ドルに設定か ｰ 関連アカウントは月額50ドル/個に	https://taisy0.com/2023/02/05/168110.html	twitter	2023-02-05 03:16:00
TECH	Techable（テッカブル）	電源なしでも同時に3本のマイクを接続可能！音楽と音声を同時に流せる拡声器スピーカー発売	https://techable.jp/archives/194913	mmspamp	2023-02-05 03:00:55
python	Pythonタグが付けられた新着投稿 - Qiita	指定したTrelloボード上にあるカード情報をCSVへ定期的にエクスポートしたい	https://qiita.com/The-town/items/f3694e48709fdfceb30a	trello	2023-02-05 12:01:49
python	Pythonタグが付けられた新着投稿 - Qiita	pylintをLinter, BlackをFormatterとして導入する [VSCode]	https://qiita.com/yuuki-h/items/639355b7ab73371c7855	black	2023-02-05 12:01:46
AWS	AWSタグが付けられた新着投稿 - Qiita	AWSクラウドプラクティショナー受験記録　~AWS歴2年半でも油断できなかった~	https://qiita.com/naganagu/items/00c95370f0753e04dc95	lambda	2023-02-05 12:22:05
Git	Gitタグが付けられた新着投稿 - Qiita	VisualStudioで.gitignoreを自動で作成する	https://qiita.com/YoshijiGates/items/025285276865f95d40b6	powersh	2023-02-05 12:04:08
海外TECH	DEV Community	Things you should look for in a Code Review	https://dev.to/leduc1901/things-you-should-look-for-in-a-code-review-ll2	Things you should look for in a Code ReviewCode review or you can call it Peer review is an activity for Software Quality assurance which one or several people involve to check parts of the code This article is sort of a guide on what to look for in a code review so the code base can have better quality reviewers and the author can learn from it FunctionalityThe first thing to look for in a code review is the functionality For a feature reviewers can look for edge cases potential problems to make sure no obvious bugs are visible just by looking at the code You can have a validation on the changes Try the feature or run a demo to see if there is any bugs for performance issues ComplexityHave you ever seen a function or a component that is too complex to even understand it in a quick look Even though the code can run fine but reviewers can t understand it quick enough might be a logic problem There would be potential bugs if a piece of code is too complex too and debug it will be even more painful We can call it Over engineering when a piece of code has things that isn t presently needed by the system engineers should be focused on things that they need to do at the moment first not problems that might be needed to solve in the future NamingDid the variables name are good Did functions name are good Did classes name are good A good name is long enough to fully communicate what the code is or does without being so long that it becomes hard to read CommentsIn my opinion comments are commonly bad So whenever I see comments while doing code review I often have a lot of question for the existence of it I wrote an article about it right hereIn short did the developer write clear comments without errors Are all of the comments actually necessary If the code isn t clear enough to explain itself then the code should be made simpler There are some exceptions regular expressions and complex algorithms often benefit greatly from comments that explain what they re doing for example but mostly comments are for information that the code itself can t possibly contain like the reasoning behind a decision StylingCoding conventions are a set of guidelines for a specific programming language with recommended programming style and practice Reviewers need to make sure the changes follows the appropriate style guides TestsUnless the changes are hot fixes reviewers should ask for unit or integration or end to end tests Reviewers need to make sure the tests are useful clear and correct Don t forget that tests are also code we should look for all of the things above when review tests ComplimentsIf the code looks good don t be shy we can tell the author about it This can encourage the developers to continue doing good stuffs	2023-02-05 03:51:39