投稿時間:2023-06-18 16:13:39 RSSフィード2023-06-18 16:00 分まとめ(20件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
TECH	Techable（テッカブル）	熱中症リスクにも対応！作業員の異常を検知するウェアラブルデバイス「AAASWatch Pro」発売	https://techable.jp/archives/211420	aaaswatchpro	2023-06-18 06:00:16
python	Pythonタグが付けられた新着投稿 - Qiita	【強化学習】Dreamerを解説・実装	https://qiita.com/pocokhc/items/9d69ab60a97ab73ae18d	plane	2023-06-18 15:26:51
python	Pythonタグが付けられた新着投稿 - Qiita	【Paiza問題集】配列メニュー/フィボナッチ数	https://qiita.com/amron/items/3d2dd8cfdfc2697104a6	paiza	2023-06-18 15:06:12
python	Pythonタグが付けられた新着投稿 - Qiita	ハイエナ階層による自然言語モデルの作成 前編	https://qiita.com/MasahideOkada/items/675decc82709d013d888	selfattention	2023-06-18 15:02:29
js	JavaScriptタグが付けられた新着投稿 - Qiita	ブラウザでお気に入り（ブックマーク）を新しいタブで開く	https://qiita.com/nekotadon/items/129336010ae1a9983dc6	javascriptwindowopen	2023-06-18 15:54:05
js	JavaScriptタグが付けられた新着投稿 - Qiita	URLからホスト名やクエリ文字列を取得する	https://qiita.com/nekotadon/items/dc3905caff5affac4abc	wurlurlindexhtmldampditem	2023-06-18 15:52:56
Ruby	Rubyタグが付けられた新着投稿 - Qiita	if , elseの練習	https://qiita.com/naomit/items/e32afec351851735ce3e	ifelse	2023-06-18 15:12:46
AWS	AWSタグが付けられた新着投稿 - Qiita	オンプレミスから VPN 経由で CloudWatch Agent を使ってログ転送してみた	https://qiita.com/sugimount-a/items/fd86e16a25e3ab16f6e3	cloudwatchagent	2023-06-18 15:57:57
Docker	dockerタグが付けられた新着投稿 - Qiita	LAN内のラズパイからDockerコンテナへsyslog,http通信	https://qiita.com/t13801206/items/b25e478e1df3f2685245	docker	2023-06-18 15:40:00
Ruby	Railsタグが付けられた新着投稿 - Qiita	RailsでAPIを使用した開発の流れとチートシート（個人的なメモ）	https://qiita.com/tomo178/items/d12c45d0d02591b06707	rails	2023-06-18 15:01:24
技術ブログ	Developers.IO	AWS SAMにおけるsamconfig.tomlのオススメ設定をまとめてみた	https://dev.classmethod.jp/articles/recommend-sam-config-toml/	awssam	2023-06-18 06:55:44
技術ブログ	Developers.IO	AWS Clean RoomsのAnalysis Builderを使ってみた	https://dev.classmethod.jp/articles/try-aws-clean-rooms-analysis-builder/	analysisbuilder	2023-06-18 06:27:55
海外TECH	DEV Community	Part 4: Writing Clean and Efficient React Code- Best Practices and Optimization Techniques	https://dev.to/sathishskdev/part-4-writing-clean-and-efficient-react-code-best-practices-and-optimization-techniques-423d	Part Writing Clean and Efficient React Code Best Practices and Optimization TechniquesWelcome to Part of our series on React best practices in In this part we will explore various techniques and strategies to write clean and efficient code in your React applications By following these best practices you can improve the maintainability performance and readability of your codebase Let s dive in and learn how to write clean and efficient React code that not only works well but is also easier to understand maintain and scale Implement error boundaries to handle component errors gracefullyWrap your components or specific sections of your application with error boundaries to catch and handle errors in a controlled manner This prevents the entire application from crashing and provides a fallback UI or error message improving the user experience and making it easier to debug issues Higher Order Component HOC withErrorBoundary HOC for error boundaryconst withErrorBoundary WrappedComponent gt return props gt const hasError setHasError useState false const errorInfo setErrorInfo useState null useEffect gt const handleComponentError error errorInfo gt setHasError true setErrorInfo errorInfo You can also log the error to an error reporting service here window addEventListener error handleComponentError return gt window removeEventListener error handleComponentError if hasError You can customize the fallback UI or error message here return lt div gt Something went wrong Please try again later lt div gt return lt WrappedComponent props gt Usage HOC for error boundaryimport withErrorBoundary from withErrorBoundary const Todo gt Component logic and rendering const WrappedComponent withErrorBoundary Todo Use React memo for functional componentsReact memo is a higher order component that memoizes the result of a functional component preventing unnecessary re renders By wrapping your functional components with React memo you can optimize performance by skipping re renders when the component s props have not changed Here is an example const TodoItem text gt return lt div gt text lt div gt Todoconst Todo gt Component logicreturn lt div gt Other elements lt TodoItem gt lt div gt In this example we have a functional component called TodoItem that receives a name prop and renders a todo text By default the component will re render whenever Todo parent component re render To optimize performance we can wrap TodoItem with React memo creating a memoized version of the component This memoized component will only re render if its props have changed Memoized version of TodoItem using React memoconst TodoItem React memo text gt return lt div gt text lt div gt By using React memo we can prevent unnecessary re renders and optimize the performance of functional components However it s important to note that React memo performs a shallow comparison of props If your component receives complex data structures as props ensure that you handle prop updates appropriately for accurate memoization Use Linting for Code QualityUtilizing a linter tool such as ESLint can greatly improve code quality and consistency in your React projects By using a linter you can Ensure consistent code styleCatch errors and problematic patternsImprove code readability and maintainabilityEnforce coding standards and conventions Avoid default exportThe problem with default exports is that it can make it harder to understand which components are being imported and used in other files It also limits the flexibility of imports as default exports can only have a single default export per file Avoid default exportconst Todo gt component logic export default Todo Instead it s recommended to use named exports in React Use named exportconst Todo gt export Todo Using named exports provides better clarity when importing components making the codebase more organized and easier to navigate Named imports work well with tree shaking Tree shaking is a term commonly used within a JavaScript context to describe the removal of dead code It relies on the import and export statements to detect if code modules are exported and imported for use between JavaScript files Refactoring becomes easier Easier to identify and understand the dependencies of a module Use object destructuringWhen we use direct property access using dot notation for accessing individual properties of an object will work fine for simple cases Avoid direct property access using dot notationconst todo id name Morning Task completed false const id todo id const name todo name const completed todo completed This approach can work fine for simple cases but it can become difficult and repetitive when dealing with larger objects or when only a subset of properties is needed Object destructuring on the other hand provides a more concise and elegant way to extract object properties It allows you to destructure an object in a single line of code and assign multiple properties to variables using a syntax similar to object literal notation Use object destructuringconst id name Task completed todo It reduces the need for repetitive object property access Supports the assignment of default values Allows variable renaming and aliasing Use fragmentsFragments allow for cleaner code by avoiding unnecessary wrapper divs when rendering multiple elements Avoid unnecessary wrapper divconst Todo gt lt div gt lt h gt Title lt h gt lt ul gt lt ul gt lt div gt In the above code Unnecessary wrapper div can add unnecessary complexity to the DOM structure potentially impacting the accessibility of your web page Use fragmentsconst Todo gt lt gt lt h gt Title lt h gt lt ul gt lt ul gt lt gt Prefer passing objects instead of multiple propswhen we use multiple arguments or props are used to pass user related information to component or function it can be challenging to remember the order and purpose of each argument especially when the number of arguments grows Avoid passing multiple argumentsconst updateTodo id name completed gt Avoid passing multiple propsconst TodoItem id name completed gt return When the number of arguments increases it becomes more challenging to maintain and refactor the code There is an increased chance of making mistakes such as omitting an argument or providing incorrect values Use object argumentsconst updateTodo todo gt const todo id name Morning Task completed false updateTodo todo Function becomes more self descriptive and easier to understand Reducing the chances of errors caused by incorrect argument order Easy to add or modify properties without changing the function signature Simplify the process of debugging or testing functions to passing an object as an argument Use arrow functionsArrow functions provide a more concise syntax and lexical scoping eliminating the need for explicit this binding and improving code readability function sum a b return a b Above code can result in verbose code and potentially lead to misunderstandings regarding the context and binding of this Use arrow functionconst sum a b gt a b Arrow functions make the code more compact and expressive It automatically bind the context reducing the chances of this related bugs It improves code maintainability Use enums instead of numbers or strings Avoid Using numbers or stringsswitch status case return case return case return Above code that is harder to understand and maintain as the meaning of numbers may not be immediately clear Use Enumsconst Status NOT STARTED IN PROGRESS COMPLETED const NOT STARTED IN PROGRESS COMPLETED Status switch status case NOT STARTED return case IN PROGRESS return case COMPLETED return Enums have meaningful and self descriptive values Improve code readability Reducing the chances of typos or incorrect values Better type checking editor autocompletion and documentation Use shorthand for boolean props lt Dropdown multiSelect false gt Use shorthand lt Dropdown multiSelect gt Shorthand syntax for boolean props improves code readability by reducing unnecessary verbosity and making the intention clear Avoid using indexes as key props Avoid index as keyconst renderItem todo index gt const name todo return lt li key index gt name lt gt Using indexes as key props can lead to incorrect rendering especially when adding removing or reordering list items It can result in poor performance and incorrect component updates Using unique and stable identifiersconst renderItem todo index gt const id name todo return lt li key id gt name lt gt Efficiently update and reorder components in lists Reducing potential rendering issues Avoids in correct component update Use implicit return in small functions Avoid using explicit returns const square value gt return value value When we use explicit return can make small function definitions unnecessarily longer and harder to read It may result in more cluttered code due to additional curly braces and explicit return statements Use implicit returnconst square value gt value value Implicit return reduces code verbosity Improves code readability It can enhance code maintainability by focusing on the main logic rather than return statements Use PropTypes for type checking Bad Codeconst Button text enabled gt lt button enabled gt text lt button gt Above code can lead to passing incorrect prop types which may result in runtime errors or unexpected behavior Use PropTypesimport PropTypes from prop types const Button enabled text gt lt button enabled gt text lt button gt Button propTypes enabled PropTypes bool text PropTypes string isRequired It helps catch error on compile time It provides better understanding and expected type of the component PropTypes act as a documentation for other developers working with the component Prefer using template literals Bad Codeconst title seriesName gt Welcome to seriesName Above code can result in verbose code and make string interpolation or concatenation more difficult Use template literalsconst title seriesName gt Welcome to seriesName It simplify string manipulation by allowing variable interpolation within the string It makes code more expressive and easier to read It support multi line strings without additional workarounds Improving code formatting Avoid huge componentAvoiding huge components in React is crucial for maintaining clean modular and maintainable code Large components tend to be more complex harder to understand and prone to issues Let s explore an example to illustrate this concept Avoid huge componentconst Todo gt State Management const text setText useState const todos setTodos useState More states Event Handlers const onChangeInput gt Other event handlers return lt div gt lt input gt lt input gt lt button gt lt list gt lt list item gt lt list gt lt div gt export default Todo In the above example we have a component called Todo which contains multiple state variables and event handlers and elements As the component grows it becomes harder to manage debug and understand You can check below blog for to address this it s recommended to break down such huge components into smaller reusable and focused components Part Component Structure Building Reusable and Maintainable Components in React Sathish Kumar N・May ・ min read react bestpractice javascript componentstructure Stay tuned for an upcoming blog dedicated to optimization techniques in React We ll explore additional strategies to enhance performance and efficiency in your components Don t miss out on these valuable insights Happy coding ‍‍	2023-06-18 06:18:39
海外ニュース	Japan Times latest articles	Top U.S. diplomat meets Chinese foreign minister in bid to tamp down soaring tensions	https://www.japantimes.co.jp/news/2023/06/18/asia-pacific/politics-diplomacy-asia-pacific/antony-blinken-china-visit/	Top U S diplomat meets Chinese foreign minister in bid to tamp down soaring tensionsThe bar for a successful two day meeting will be low for both Washington and Beijing as they look to at least prevent ties from bottoming	2023-06-18 15:45:34
海外ニュース	Japan Times latest articles	Former Hiroshima Carp ace Manabu Kitabeppu dies at 65	https://www.japantimes.co.jp/sports/2023/06/18/baseball/japanese-baseball/manabu-kitabeppu-dies-65/	Former Hiroshima Carp ace Manabu Kitabeppu dies at Kitabeppu secured double digit wins for consecutive seasons from thanks to his outstanding control helping the team clinch back to back Japan Series titles in	2023-06-18 15:46:03
海外ニュース	Japan Times latest articles	Rickie Fowler and Wyndham Clark tied atop U.S. Open heading into final round	https://www.japantimes.co.jp/sports/2023/06/18/more-sports/golf/us-open-third-round/	twists	2023-06-18 15:04:12
ニュース	BBC News - Home	David Warburton quits as MP, triggering another by-election	https://www.bbc.co.uk/news/uk-politics-65941710?at_medium=RSS&at_campaign=KARANGA	rishi	2023-06-18 06:22:13
ニュース	BBC News - Home	Glastonbury fashion: Festival fans turn to second-hand outfits	https://www.bbc.co.uk/news/uk-wales-65908821?at_medium=RSS&at_campaign=KARANGA	clothes	2023-06-18 06:11:21
ニュース	BBC News - Home	Sunday's gossip: Pickford, Lukaku, Barella, Cucurella, Gallagher, Caicedo, Veiga, Arteta	https://www.bbc.co.uk/sport/65936698?at_medium=RSS&at_campaign=KARANGA	Sunday x s gossip Pickford Lukaku Barella Cucurella Gallagher Caicedo Veiga ArtetaManchester United to bid for Jordan Pickford Chelsea ask to swap Romelu Lukaku for Nicolo Barella Newcastle target Marc Cucurella plus more	2023-06-18 06:12:29
IT	週刊アスキー	アボカド！アボカド！アボカド！ メキシカンバーガーがファーストキッチンから	https://weekly.ascii.jp/elem/000/004/141/4141264/	夏季限定	2023-06-18 15:30:00