投稿時間:2023-03-02 20:22:49 RSSフィード2023-03-02 20:00 分まとめ(27件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	ITmedia 総合記事一覧	[ITmedia News] 定期券買うと20GBもらえる、povoとモバイルSuicaがコラボ　抽選で13万人にもう20GB	https://www.itmedia.co.jp/news/articles/2303/02/news172.html	gbkddi	2023-03-02 19:50:00
TECH	Techable（テッカブル）	不動産AI査定「HowMa」で確実に売れる価格・相場より高く売れやすい価格が表示可能に	https://techable.jp/archives/198322	howma	2023-03-02 10:00:24
python	Pythonタグが付けられた新着投稿 - Qiita	【AWS Lambda定期実行】Part2! LambdaとPythonを使った定期実行をわかりやすく解説【Python, AWS Lambda, Twitter API】	https://qiita.com/keiichileograph/items/54e6709965b0c3ea1e90	awslambda	2023-03-02 19:22:48
python	Pythonタグが付けられた新着投稿 - Qiita	ChatGPTのAPIを使って記憶（過去の会話をある程度覚えている）のあるAIキャラクターを作ってみる	https://qiita.com/3dy3day/items/e399e53af04d5ba151a1	chatgpt	2023-03-02 19:05:03
AWS	AWSタグが付けられた新着投稿 - Qiita	【AWS Lambda定期実行】Part2! LambdaとPythonを使った定期実行をわかりやすく解説【Python, AWS Lambda, Twitter API】	https://qiita.com/keiichileograph/items/54e6709965b0c3ea1e90	awslambda	2023-03-02 19:22:48
AWS	AWSタグが付けられた新着投稿 - Qiita	Amazon BraketのHybrid JobsとPennyLane Lightningについて調べてみた	https://qiita.com/mountrock/items/bd20a17cf9ba7cf81a55	embeddedsimulators	2023-03-02 19:14:31
技術ブログ	Developers.IO	ChatGPT APIリリースに伴ってOpenAIのAPIデータ利用ポリシーが改定されたので読んでみた	https://dev.classmethod.jp/articles/openai-data-usage-policy/	chatgptapi	2023-03-02 10:53:06
技術ブログ	Developers.IO	チャットAI上でシステムが完結する未来は来るのか。ChatGPTと飲食店シミュレーションをして考えてみた	https://dev.classmethod.jp/articles/chatai-system-chatgpt-restaurant/	chatgpt	2023-03-02 10:16:54
海外TECH	DEV Community	Server-render your SPA in CI at deploy time 📸	https://dev.to/bryce/server-render-your-spa-in-ci-at-deploy-time-2798	Server render your SPA in CI at deploy time If you deploy your SPA using GitHub Actions you can add this new action to your workflow to have it build server rendered HTML Server side rendering SSR is great for SEO and performance I use it for projects that have an expensive initial render or have links that I want to be discoverable react snap is a tool to help with SSR a while ago I wrote about it Perform a React disappearing act with react snap Bryce Dorn・Jan ・ min read javascript react webdev I ve been using it as a postbuild script but it recently broke in CI The fix for it became rather complex so rather than include this in each project that I use it for I decided to bundle everything into a standalone action This also significantly reduced the number of per project dependencies as it prevents installing big ones like puppeteer Though react is in the name this will work for any framework that supports hydration In Svelte for example this just means switching the hydrate flag import App from App svelte const app new App target document querySelector server rendered html hydrate true Once your app is hydratable replacing your build step with this action will run npm build followed by react snap jobs prerender runs on ubuntu latest steps name Checkout ️ uses actions checkout v name Server side render uses brycedorn react snap action v You can then deploy this to GitHub Pages or wherever Give it a try and let me know if it helps simplify your workflow brycedorn react snap action Github Action for pre rendering via react snap	2023-03-02 10:47:36
海外TECH	DEV Community	Why i have grown to hate css libaries	https://dev.to/mudakikwa/fuck-css-libraries-gpd	Why i have grown to hate css libariesWhen it comes to building UI designs CSS libraries can be a double edged sword While they promise to make styling faster and more efficient they can actually hinder your ability to integrate your finished design into your frontend As UI designers we strive to create pixel perfect designs that are visually stunning and functionally seamless However translating these designs from software like Figma or Adobe XD to a production site requires flexibility with spacing and responsiveness across multiple devices Unfortunately using Tailwind to model complex UI designs can quickly become a nightmare In order to achieve the desired design users must write a laundry list of CSS classes leading to a cluttered and difficult to maintain codebase Additionally debugging your Tailwind CSS can be a frustrating experience especially when it comes to responsive design Debugging is crucial to ensuring your UI functions as intended and any friction in this process can significantly slow down development time So what s the solution While Tailwind may still have a place in your UI design toolkit it s best to limit its use to layout design All other design elements should be handled using Sass files Sass has a multitude of advanced features that make it a superior choice for styling including the ability to create functions that scale your fonts according to screen sizes Using Sass you can easily define your CSS and make it more modular and easily debuggable You won t need to dive deep into a sea of classes to figure out why your design isn t rendering correctly In conclusion while CSS libraries have their advantages it s important to use them judiciously when it comes to complex UI designs By limiting your use of Tailwind to layouts and utilizing Sass for all other design elements you can achieve a more flexible and efficient workflow resulting in stunning and functional UI designs that are sure to impress your users Here is an example of modular sass codes that can be used function pxToVh element return element vh function pxToVw element return element vw function pxToEm element return element em mixin scaleFont font size monitor include mq xxlg ont size pxToVw font size below px screen include mq xlg font size pxToEm font size include mq xls font size font size text style example include scaleFont with this simple change i won t need to worry about font responsivenes for the entire project and this save me a lot crappy tailwind classesfor guys who are new to sass this just the top of the iceberg of what sass can do here is other sass featuresVariables Sass allows you to define variables for commonly used values such as colors fonts and spacing This makes it easier to update your styles across multiple components without having to change each individual value Nesting Sass allows you to nest selectors within one another making it easier to read and write your code This helps you avoid the need to write long repetitive selectors Mixins Sass mixins allow you to define groups of styles that you can reuse throughout your code This helps you keep your code DRY Don t Repeat Yourself and more maintainable Functions Sass functions allow you to write complex operations that can be reused throughout your code For example you can write a function that scales font sizes based on screen size Partials Sass allows you to break your styles into smaller modular files called partials This makes it easier to organize your code and keep related styles together Import Sass allows you to import styles from other Sass files making it easier to reuse code and keep your code organized Operators Sass supports a variety of mathematical operators including addition subtraction multiplication and division This makes it easier to perform complex calculations within your styles Control Directives Sass offers control directives such as if for and each that allow you to write more advanced logic in your styles This gives you greater control over how your styles are rendered and that guys was my take on tailwind and other css libaries	2023-03-02 10:41:53
海外TECH	DEV Community	Understanding Technical Debt in Software Development	https://dev.to/timonwa/understanding-technical-debt-in-software-development-2cga	Understanding Technical Debt in Software DevelopmentTechnical debt is a term that describes the cost associated with using quick and dirty solutions in software development It is a consequence of prioritizing short term gains over long term technical excellence Such costs include time money and resources When a team of developers is under pressure to meet deadlines they may choose to take shortcuts in their code to get the job done quickly While these shortcuts might help the team meet its immediate goals they can also introduce additional complexity and risk into the codebase This might involve using hacks or workarounds skipping proper testing or failing to follow best practices Over time this technical debt accumulates and can lead to many problems A code that is difficult to understand or maintain is more likely to have bugs which can cause user issues and require even more time and resources In addition the need to constantly work around the shortcomings of the initial quick and dirty solutions can slow down future development and make it more challenging to add new features or make changes to the code Technical debt is neither bad nor good because of the different instances in which we can acquire it Technical debt is just debt Think of it like a financial debt Sometimes taking out a financial loan is necessary We might use that loan to start a business or pay for hospital bills And at the end of the day we either pay back the loan on time or suffer the consequences of late payment or lack of payment And just like financial loans the cost of technical debt can be a trade off for faster shipping times What matters is that we accumulate debt prudently manage it properly and have the plan to pay it back Managing technical debtManaging technical debt is a balancing act On the one hand it s important to avoid accumulating too much technical debt as this can lead to significant problems down the road On the other hand it s also important to recognize that sometimes taking on a certain amount of technical debt can be a necessary trade off to meet business goals or respond to changing circumstances One way to manage technical debt is to establish a formal process for tracking and addressing it This might involve setting up a system for identifying and prioritizing technical debt and implementing regular code reviews and refactoring sessions to address the most pressing issues Another critical aspect of managing technical debt is communication It s essential for everyone on the team from the developers to the product managers and executives to be aware of the technical debt that exists and to discuss the trade offs involved in taking on additional debt This can help ensure that the team makes informed decisions and works together to find the right balance between short term gains and long term technical excellence To effectively tackle technical debt it s crucial to have a clear understanding of its causes and potential solutions This way you can proactively prevent and manage technical debt effectively Causes of technical debtThere are many causes of technical debt some of which are preventable and others simply an inherent part of the software development process Lack of planning and designOne of the most common causes of technical debt is the lack of proper planning and design during the early stages of software development When developers do not take the time to plan and design the architecture of a software application carefully it leads to a lack of modularity flexibility and scalability This can result in a codebase that is difficult to maintain and update leading to a build up of technical debt over time Unclear requirements and scopeAnother common cause of technical debt is unclear or incomplete requirements and scope during the development process When developers do not have a clear understanding of the goals and objectives of a software application it can lead to a lack of direction and focus This results in a codebase that aligns differently from the application s intended purpose leading to technical debt Poor coding practicesDevelopers who do not follow best practices and coding standards can create a codebase that is difficult to read understand and maintain This can lead to a higher likelihood of bugs and vulnerabilities as well as increased time and effort required for code maintenance and updates Poor coding practices can also cause technical debt Legacy code and technical debtTechnical debt can also be caused by using legacy code in software development Legacy code refers to outdated or deprecated code that has been inherited from previous versions of a software application Using legacy code can be problematic as it may not be aligned with current best practices and standards This can result in a codebase that is difficult to maintain and update leading to technical debt Lack of code review and testingAnother common cause of technical debt is the lack of code review and testing during the development process Developers who do not regularly review and test their code can create a codebase prone to bugs and vulnerabilities This can lead to technical debt as it may require more time and effort to fix these issues in the future Lack of team collaborationA lack of collaboration and communication within a development team can cause technical debt If team members are not working together effectively it can lead to a lack of consistency in the codebase making it difficult to maintain and improve the software system Pressure to meet deadlinesIn today s fast paced world there is often pressure to meet tight deadlines and deliver software applications quickly While this can be necessary in some cases it can also lead to shortcuts and compromises in the development process This can result in technical debt as developers may prioritize speed over quality and long term maintainability Lack of resourcesDeveloping a software system requires significant time money and expertise A lack of resources can also lead to technical debt If a company does not have the necessary resources to develop a software system it may be forced to take shortcuts or make compromises that result in technical debt Lack of focus on long term maintenance and improvementIn addition technical debt can be caused by a lack of focus on long term maintenance and improvement Many companies focus on getting a software system up and running as quickly as possible without considering the long term implications of their decisions This can result in a system that is difficult to maintain and improve over time leading to technical debt Solutions to technical debtFortunately there are several steps that developers and organizations can take to reduce or limit technical debt Plan and design carefullyOne of the most effective ways to prevent technical debt is to carefully plan and design the architecture of a software application during the early stages of development This involves creating a detailed roadmap for the development process including the application s goals objectives and requirements This helps ensure that the codebase is modular flexible and scalable making it easier to maintain and update over time Follow best practices and standards for codingAnother critical step in preventing technical debt is following best coding practices and standards This involves using consistent coding conventions such as naming conventions and coding styles and following established design patterns and frameworks This helps ensure that the codebase is easy to read understand and maintain which will reduce the likelihood of bugs and vulnerabilities Clearly define requirements and scopeTo prevent technical debt it is also essential to clearly define the requirements and scope of a software application during the development process This involves creating detailed specifications and requirements documents and establishing clear milestones and deadlines This helps ensure that the development team has a clear understanding of the goals and objectives of the application which will prevent the codebase from becoming misaligned with the intended purpose of the application Prioritize quality over speedWhile prioritizing speed over quality can be necessary in some cases to meet tight deadlines and deliver software applications quickly it is important to prioritize quality over speed to prevent technical debt This means taking the time to carefully plan and design the application s architecture and following best practices and standards for coding It also involves regularly reviewing and testing the codebase to ensure it is free of bugs and vulnerabilities Refactor legacy codeIt is vital to regularly refactor legacy code to align it with current best practices and standards to prevent technical debt This can involve updating the codebase to use more modern programming languages frameworks and libraries and reorganizing and modularizing the code to improve maintainability Regularly review and test the codebaseAnother effective way to prevent technical debt is regularly reviewing and regularly testing the codebase throughout the development process This involves using code review tools and processes to ensure that the code is consistent maintainable and free of bugs and vulnerabilities It also involves conducting regular testing such as unit testing integration testing and end to end testing to ensure that the application is functioning as intended Foster collaboration and communication within the development teamTo prevent technical debt fostering collaboration and communication within the development team is essential This involves establishing clear roles and responsibilities and providing opportunities for team members to share their knowledge and expertise It also involves using tools and processes to ensure that all team members work together and are on the same page throughout the development process SummaryIn summary technical debt is a common and often inevitable part of software development By understanding the costs and risks associated with technical debt and implementing strategies for managing it effectively teams can avoid letting it become a significant hindrance to their success Learn more about technical debtWhat is Technical Debt How to Identify Technical Debt in Your SoftwareThe main types of technical debtThe Engineers Complete Guide to Technical Debt Connect with me onTwitter LinkedIn Instagram If you like my notes and would like to support me you can buy me a coffee on ByMeACoffee or GetFidia I love the taste of coffee	2023-03-02 10:22:19
海外TECH	DEV Community	A Quick Guide to Riverpod Data Caching and Provider Lifecycles	https://dev.to/kuldeeptarapara/a-quick-guide-to-riverpod-data-caching-and-provider-lifecycles-5enf	A Quick Guide to Riverpod Data Caching and Provider LifecyclesRiverpod involves reactive caching along with the data binding framework These have widely evolved from the provider packages Normally the Riverpod is the rewrite for the Provider package These are suitable options for making improvements that are quite impossible to access Most people want to view the state management framework which involves extensive Reactive Caching and Data binding Framework Riverpod has been enabled from the valuable concepts of the React Query These provide better accessibility from Flutter world to high excellence Flutter Riverpod Normally the Provider package involves improvements on InheritedWidget These extensively depend on a complete widget tree that can be easily enabled Riverpod is also the compile safer option as most providers have been using them worldwide Riverpod could be easily accessed from anywhere even without any hassle Provider package involves the easy to use package wrapped across InheritedWidgets These make it a convenient option for using and managing them accordingly Versatile and used for most featureHelpful to create and combine providersPerforms reactive cachingEasily fetchCatches programming errors at compile timeDisposes state of a providerDepends on asynchronousUpdates data from a remote sourceWrites testable codeKeep your logic outside the widget treeThe method would provide the Flutter app state management technique suitable for data management Riverpod Data Caching is an advanced technique from the provider package and is assured of giving better stability even without any hassle Below are the steps for providing full accessibility such as final counterProvider StateNotifierProvider lt counter int gt ref return Counter Class Counter extends StateNotifier lt int gt Counter super void increment gt state lt int gt lt counter gt To consume the provider you can follow the below steps class Home extends ConsumerWidget override Widget build BuildContext context WidgetRef ref final count ref watch counterProvider return Text count Riverpod implements the complete range of patterns These are helpful for retrieving and caching the data There is no need to reimplement them for the accessibility feature These are quite efficient options for establishing good app architecture These can also be suitable for focusing on building the feature with minimal friction Explore The Main Riverpod APIsIn the modern day the new riverpod generator package has been published as the biggest part of Riverpod Apart from these it also introduces a new riverpod annotation API You can also easily use them automatically to generate the providers for the Methods and Classes in the codes Compile safe feature is also added in the process So there are also no requirements for the ProviderNotFoundException or even forgetting the handle loading state It extensively adds the providers anytime and anywhere without any hassle The method is the perfect option for declaring the shared state from anywhere There is no need to jump from the main dart and UI files anymore You can easily place the code of the shared state where it belongs These can be enabled with a separate package or even added next to the Flutter widget final countProvider StateProvider ref gt Consumes the shared stateclass Title extends ConsumerWidget overrideWidget build BuildContext context WidgetRef ref final count ref watch countProvider return Text count The method involves the stale while revalidate pattern having the complete riverpod You can also extensively look at the query provider package The backend class could be easily made using the ghibli api The Tested Provider family is a significant option in easily checking whether the state is persistent with memory How Does The Provider Package Start Normally the Provider package starts with the two possible attributes such asIf we call runApp inside main for attaining the top level ProviderScopeIf we call the CounterWidget widget mounted and call the ref watch in the build methodBased on the different criteria changing the print statements on the code will be efficient void main print Inside main runApp ProviderScope child MaterialApp home CounterWidget final counterStateProvider StateProvider lt int gt ref print counterStateProvider initialized return lt int gt counterStateProvider involves the complete initialization when they are called as ref watch counterStateProvider The main reason is that the Riverpod providers can save more time due to the app development process even without hassle Print statements along with the debug breakpoints are some of the amazing ways to explore the app s runtime behavior These could be easily diagnosed and fixed with countless bugs to high excellence A method is a suitable option for running Flutter smoothly with these tools How To Register Listeners In Riverpod Data Caching For registering the Listener in Riverpod Data Caching as well as Providers Lifecycle you can follow the below stepsclass CounterWidget extends ConsumerWidget override Widget build BuildContext context WidgetRef ref watch the provider final counter ref watch counterStateProvider return ElevatedButton use the value child Text Value counter increment the counter when the button is pressed onPressed gt ref read counterStateProvider notifier state Call ref watch counterStateProvider inside the build methodThese involve the processes in the end results even without any hassle You can get the provider s state or counter value so these show the UI accordingly CounterWidget is an amazing listener on counterStateProvider These can be extensively built with the provider state changes These methods also affect the results of the Provider such as Provider s state can be easily initialized with the first listenerListeners are notified when the state changesListeners are updated rebuild themselvesProviders can have better than one listenerThe counter app had one provider as well as a listener widgetObservable Pattern Providers also listen to other providers Riverpod builds upon observable patternBoth ref watch and ref listen are used to register listener to providerOne time read featureDoes not register a listenerProvider maintains state and keeps memory until enclosing ProviderScope is eliminated These can access the user to kill apps enabled with level ProviderScope ConclusionRiverpod enables the complete aspects of code to compile attributes The Provider package has widely inspired Riverpod These are also suitable options for solving key issues like supporting multiple providers of the same type These also await asynchronous providers If you are thinking of developing medium to large size business applications this information about Riverpod will be helpful to you Frequently Asked Questions FAQs Is Riverpod better than the Provider To understand let s see the major drawback of the provider package By designing Provider is the improvement over the inherited widget and it depends on the widget tree On the other hand Riverod is the compile safe since all the providers are declared globally and it is accessible from anywhere What does future Provider mean with Riverpod FutureProvider is a simple and convenient method to expose the configuration object build by just reading the JSON file It will automatically rebuild UI when the future completes At the same time if various widgets want configuration then the asset is decoded only once What is the ephemeral state of Riverpod The state local to any widget is known as an ephemeral state The state is contained within the single widget and there is no requirement for the complicated state management technique of just using a Stateful widget to rebuild a UI	2023-03-02 10:09:40
海外TECH	CodeProject Latest Articles	Kigs Framework Introduction (8/8) - Data Driven Application	https://www.codeproject.com/Articles/5271431/Kigs-Framework-Introduction-8-8-Data-Driven-Applic	application	2023-03-02 10:12:00
医療系	医療介護 CBnews	A.5の割合が低下、亜系統への置き換わり進む-東京都がゲノム解析の結果公表	https://www.cbnews.jp/news/entry/20230302172459	新型コロナウイルス	2023-03-02 19:05:00
金融	RSS FILE - 日本証券業協会	採用情報	https://www.jsda.or.jp/about/recruit/index.html	採用情報	2023-03-02 10:08:00
金融	金融庁ホームページ	入札公告等を更新しました。	https://www.fsa.go.jp/choutatu/choutatu_j/nyusatu_menu.html	公告	2023-03-02 11:00:00
ニュース	BBC News - Home	Matt Hancock: Leaked messages reveal battle over Covid and schools	https://www.bbc.co.uk/news/uk-politics-64819241?at_medium=RSS&at_campaign=KARANGA	teachers	2023-03-02 10:48:03
ニュース	BBC News - Home	Epsom College head and daughter died of shotgun wounds	https://www.bbc.co.uk/news/uk-england-surrey-64813551?at_medium=RSS&at_campaign=KARANGA	lettie	2023-03-02 10:55:21
ニュース	BBC News - Home	WH Smith staff data hit by cyber attack	https://www.bbc.co.uk/news/business-64823923?at_medium=RSS&at_campaign=KARANGA	accounts	2023-03-02 10:47:51
ニュース	BBC News - Home	Woman completes 10-year National Trust scone-eating project	https://www.bbc.co.uk/news/uk-england-london-64822669?at_medium=RSS&at_campaign=KARANGA	perfect	2023-03-02 10:12:29
ニュース	BBC News - Home	Constance Marten arrest: Police continue questioning after baby found	https://www.bbc.co.uk/news/uk-64815323?at_medium=RSS&at_campaign=KARANGA	gross	2023-03-02 10:54:53
ニュース	BBC News - Home	Former top Met officer's 'regretful sex' rape comment investigated	https://www.bbc.co.uk/news/uk-england-london-64815863?at_medium=RSS&at_campaign=KARANGA	january	2023-03-02 10:55:28
ニュース	BBC News - Home	Newcastle United: Premier League 'must re-examine' takeover after chairman described as Saudi minister	https://www.bbc.co.uk/sport/football/64821422?at_medium=RSS&at_campaign=KARANGA	Newcastle United Premier League x must re examine x takeover after chairman described as Saudi ministerThe Premier League must re examine the assurances it was given about potential Saudi state control of Newcastle says human rights group Amnesty International	2023-03-02 10:26:36
ニュース	BBC News - Home	Who is Isabel Oakeshott, the journalist behind Matt Hancock Covid messages leak?	https://www.bbc.co.uk/news/uk-politics-64821983?at_medium=RSS&at_campaign=KARANGA	political	2023-03-02 10:16:37
IT	週刊アスキー	Switch版『レイズ アーケード クロノロジー』が本日よりニンテンドーeショップで予約購入開始！	https://weekly.ascii.jp/elem/000/004/127/4127124/	nintendo	2023-03-02 19:55:00
IT	週刊アスキー	フリューの新作ゲーム『クライマキナ／CRYMACHINA』の公式生放送が3月3日20時より配信！	https://weekly.ascii.jp/elem/000/004/127/4127114/	crymachina	2023-03-02 19:30:00
IT	週刊アスキー	PS5／PS4『バトオペ2』で「機動戦士ガンダムNT」TV公開記念キャンペーンを開催！	https://weekly.ascii.jp/elem/000/004/127/4127113/	playstation	2023-03-02 19:20:00