投稿時間:2023-04-06 03:24:47 RSSフィード2023-04-06 03:00 分まとめ(29件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
AWS	AWS Open Source Blog	Behind the Scenes on AWS Contributions to Cloud Native Open Source Projects	https://aws.amazon.com/blogs/opensource/behind-the-scenes-on-aws-contributions-to-cloud-native-open-source-projects/	Behind the Scenes on AWS Contributions to Cloud Native Open Source ProjectsIn the past year alone AWS contributed significantly to containerd Cortex etcd Fluentd nerdctl Notary OpenTelemetry Thanos and Tinkerbell	2023-04-05 17:34:43
python	Pythonタグが付けられた新着投稿 - Qiita	【PyTorch】RBMを自動微分で実装する	https://qiita.com/ryo_he_0/items/dcef05f930095cc8e038	pytorch	2023-04-06 02:46:55
GCP	gcpタグが付けられた新着投稿 - Qiita	Firebase Authentication でログインしようとしたらThe requested action is invalid.と出てしまう件についての解決策	https://qiita.com/motsu/items/0f9b3c59a85f003f0c35	firebaseauthentication	2023-04-06 02:40:59
Azure	Azureタグが付けられた新着投稿 - Qiita	Microsoft 認定:Azure Administrator Associate (AZ-104) 取得までやったこと	https://qiita.com/ykeiko/items/272463032d2f4cf4f4ba	administrator	2023-04-06 02:11:12
海外TECH	Ars Technica	A New Zealand company has started flying a rocket-powered spaceplane	https://arstechnica.com/?p=1929210	zealand	2023-04-05 17:30:36
海外TECH	MakeUseOf	9 Different Kinds of Servers You Can Host on a Raspberry Pi	https://www.makeuseof.com/9-different-kinds-of-servers-you-can-host-on-a-raspberry-pi/	ideal	2023-04-05 17:30:21
海外TECH	MakeUseOf	How to Enable Auto Color Management for Apps in Windows 11	https://www.makeuseof.com/enable-auto-color-management-windows-11/	color	2023-04-05 17:15:19
海外TECH	DEV Community	Modernizing Legacy Applications in PHP: Challenges and Approaches	https://dev.to/antonlogvinenko/modernizing-legacy-applications-in-php-challenges-and-approaches-2h15	Modernizing Legacy Applications in PHP Challenges and ApproachesThe fact that PHP projects can run for many years is one of the most awesome strengths of this technology But at the same time outdated versions of PHP with unsupported frameworks and libraries cause a lot of problems for product owners Your system may still work but have some issues preventing it from adding new features and scaling Still the main challenge of modernization is to update without harming the current product which may lead to losing customers and money If you are among those who experience difficulties in finding PHP developers able to scale hours immediately to modernize your app or your previous developers have not lived up to their commitments and left you with nothing right before the deadline this article is for you As a PHP DevOps Group Leader at MobiDev I have worked on dozens of PHP projects and would like to share our approach to modernizing legacy applications to help you tackle this task in the most efficient way Signs Your PHP Application Needs ModernizationFirst of all let s start with a quick diagnostic process to find out if your PHP app really needs to be modernized There are certain signs which can tell you that something is wrong FROM A BUSINESS POINT OF VIEWUnpredictable behavior of the application causes poor UXThe price of infrastructure support is too highSecurity breaches cause a bad reputationYou lose your clients because your application is too slowFROM A TECH POINT OF VIEWUnstable work of the application errors outages long downtimeSecurity issues caused by an outdated tech stack and or vulnerable codeThe current tech stack no longer meets your business needs There are better technical alternatives Hard to add new features because of messy source code and complex business logicThere are unsupported or unmaintained libraries technologiesIf you come across the above mentioned issues your app really needs to be updated to stay competitive in the market The more points that are true for you the sooner you should start reviving your PHP project Why You Should Use Supported PHP VersionsAt the time of writing this article the officially supported versions of PHP are and But according to statistics about of PHP users are still on PHP and lower PHP has been out since November but only of websites have made the switch to it SourceThere are many reasons to stay on the supported version of PHP and keep your product updated The most preferable option is to stay on the latest stable version since it provides you with better UX and improved application performance Among other reasons you should consider the following Security Most of the security issues in PHP apps are related to outdated versions of PHP Security vulnerabilities can cause data loss data leaks outages etc Support of modern libraries Outdated versions of PHP may cause issues with updates to newer versions of libraries frameworks Libraries and frameworks can also be vulnerable and sometimes you may be unable to update separate libraries without PHP update Integrations To speed up development you often need to use third party services that can provide libraries clients and SDKs integrations You may not be able to use such services until you update to newer versions of PHP Same story with PHP frameworks There is a higher chance to find integrations for modern frameworks than for outdated ones Adding new features Newer versions of PHP provide a variety of capabilities to speed up the development of new features and improve the readability of the code That means you can easily expand your team with new developers Also many engineers prefer to work with modern tech stack rather than with legacy applications This is also a reason to think about regular updates and stay on a stable modern version Performance Core PHP developers are constantly working on improving PHP performance For example JIT compilation has been added since PHP which opened the door for enhanced data processing Challenges of Migrating Legacy PHP Applications To Migrate or Not to Migrate Modernization of outdated code is crucial but it comes with some risks Migrating a legacy PHP application presents challenges for both a development team and the product owner Let s imagine how developers and product owners see the same situation And they are both right They have to find some kind of compromise so that the project effort is justified In most cases it is possible to support current applications and do updates step by step while also adding new features The development speed would not be so great in this case though The main point is that developers need to do extra steps before starting the migration process or adding new features such as understand legacy logic laid by previous developersdo refactoring in case of dirty codeprepare code for adding new features Only after this work is done will PHP developers be able to add new functionality Product owners will benefit from such work in the long run After some time the speed of the app will increase and the stability and security will also grow This is a kind of investment in the future of your application Two Approaches to PHP App ModernizationWhen it comes to PHP app modernization there is one difficult question should you continue using the existing application after updates or should you rewrite everything from scratch on a modern tech stack Answering this question gives us two main approaches to PHP app updates APPROACH REWRITE EVERYTHING FROM SCRATCH Rewriting your app from scratch is the most guaranteed way to achieve quality and stability of the application But a lot depends on the state of the current software product Sometimes it is really better to rewrite everything from scratch because it will take less time than fixing and updating legacy code In this case a development team can start working on a new application with modern technologies using the old app as a reference to business logic The newest versions of PHP or some alternatives like Node js or Ruby can be used here This will provide a better understanding of the business needs taking into account previous user experience parts of the application that work well for users and parts that can be improved As a result of this work you will get a beautiful modern application based on your legacy one Let me answer the questions that you may have at this stage Is it an expensive approach Yes Such work will consume a lot of time and money Should I do a feature freeze Probably yes You would pay twice if you create new features on a legacy application and after that you need to create the same features on a modern application again APPROACH STAY WITH A CURRENT APPLICATIONThe previous approach will not work for most businesses In most cases a business needs new features to live Using the current application is possible in cases when the approximate time for an upgrade will take less time than rewriting everything from scratch A lot depends on the current technology stack and the technical state of the system What parts are most critical to update Are there any security vulnerabilities Are there any libraries that are not supported anymore Only after analysis can technical experts suggest an upgrade plan The most valuable activities will be done first During the upgrade process PHP developers can add new features to the current application as well What issues can bring such an approach Potential non obvious bugs Fixing one bug may bring on another bug because of the level of complexity and quality of the legacy code Difficulties with compatibility You can update the version of PHP and some parts will work well but some parts will not work because of breaking changes Complex logic If you have a complex application with a huge code base then upgrades should be done step by step That means there would be part of logic with updates and part of logic without updates These may bring some temporary dirty hacks extra levels of complexity and cause some difficulties in the onboarding of new developers who are not familiar with the project Workflow for PHP App ModernizationRegardless of which of the above mentioned approaches you choose the process of PHP app modernization will look almost the same Based on our experience with many legacy applications I can say that this workflow is the most efficient for both the product owner and the development team It consists of steps Step The client sends a request for a project review to a technical expert Step The technical expert analyzes the project and discusses with the client the possible ways of modernization and estimated timelines Step The client requests a development team that will start working on a selected approach Step Containerize the application Docker will help with this This allows for adding an extra isolation layer for the parts of the app With Docker we can easily manipulate any version of the service that we need for application functionality Step Deploy everything in a sandbox environment for testing and development Step Involve the QA engineer Start testing the application to find the most critical issues Step Prioritize the list of issues and start working on them Step Work on updates and fixes iteration by iteration Step optional After the stabilization of the application new features can be added as a priority to updates Step Your software is upgraded and ready to go Our Case Studies for PHP Legacy Software ModernizationLet s go through some cases from our experience that will illustrate the solution of business challenges with the modernization of legacy PHP applications These cases include comments from project developers that will help you better understand why a specific solution was chosen CASE STUDY UPDATING LEGACY LARAVEL BASED SUBSCRIPTION PLATFORMThe client came to us with a request for the modernization of the PHP platform in a critically short time frame Since the previous developers of the project failed and didn t do what they promised the client needed a reliable team that would take up the challenge and meet the deadlines Main challenges Build the back end for the existing front end Find and fix issues preventing the system from working correctlyPrepare the product for adding new featuresSolutionThe initial request was to rebuild the platform but after code assessment and analysis of the client s business needs our PHP development team suggested improving the existing system instead of rewriting the product from scratch Such a decision was influenced by the following factors The platform was already in production and had an active user base It was crucial for the business to keep the product running Our client had a limited budget and timelines to make the system stable and prepare it for adding new features Build the back end for the existing front endWhen we delved into the project we found out that its deployment including the assembly of the front end took place directly on the server which required routine manual work and significantly increased the time and cost required for debugging We ve integrated Ansible a software provisioning and configuration management system and added rules to automatically build deploy and update the software This helped the client to save on servers since the assembly of the front end on the server required quite large capacities which was unreasonable for everyday tasks Find and fix issues preventing the system from working correctlyThe fact that the platform was written on an outdated version of the Lavarel framework led to unstable operation of the entire system unpredictable errors inability to use stable modern libraries slow response from the server etc Moreover the PHP version also needed an update Bugs in the framework plus PHP bugs were superimposed on project code bugs that created a danger to the security of customer data So our PHP team decided to update Laravel to LTS and PHP version to on all servers as the latest versions at that time This made it possible to eliminate system vulnerabilities and fix critical bugs Prepare the product for adding new featuresThe poor quality of the code was a real challenge for the team as a large part of the code needed refactoring Plus the project had no documentation which complicated the process Also in order to use a third party payment system it was necessary to update the SDK since its version conflicted with the modules used by the project So code refactoring and regression work was done After that we were able to continue adding new features with modern technologies and an up to date version of our built in and external modules We created tech documentation that will allow the client to significantly save on onboarding new developers and adding new functionality in the future It was really challenging to update the framework version by version gt gt gt because all of them were not backward compatible and each subsequent version radically changed either the architecture or the logic or even the names of the framework functions It was also important for the client to implement full GDPR compliance at that time there was little information about it and it required additional research from the team Overcoming these challenges assured the client that we have great expertise in PHP app development and they still trust us to introduce new features into the platform Oleh SichevskyiPHP Team LeaderCASE STUDY MODERNIZING A LEGACY APP ON CODEIGNITER FRAMEWORK Our communication with the customer started with the request to solve problems with the current API for CRM and mobile app with legacy code Codeigniter PHP The client had tight deadlines the software had to be updated within a month It is difficult to complete refactoring of the entire system in such a short period of time so we decided to approach the improvement of the code very selectively and gradually We drew up a plan with the most critical issues and started working on it Main challenges Update the highly outdated version of the framework to improve system performanceImprove code quality under tight deadlinesConfiguring the mechanism of code delivery to the serverBuild new scaling infrastructureSolution Update the highly outdated version of the frameworkAs the Codeigniter version of the framework was no longer supported our PHP developers suggested gradually migrating the entire application to a newer version The team created a plan with prioritization and division of all functionality into modules Each module is a fully isolated functionality in a new project with up to date versions of dependencies and environments Improve code quality under tight deadlinesThe poor quality of the code caused additional problems We had to spend more time studying the logic of each method even for the smallest changes At the same time there was no way to fix everything at once due to the large size of the project and the large amount of functionality Each change required a full understanding of the requirements for a specific feature which could take a very long time and thus delay the release date The solution was to refactor only those places whose functionality we were currently working on and proceed to other parts gradually It made it possible to meet the deadline and save the client s money Within six months about percent of the code was already covered Configuring the mechanism of code delivery to the serverAt the start of the project we had only one production environment available Making edits to the code was very time consuming and involved the risk of human error which put the seamless operation of the application under attack To mitigate these risks we needed to prepare a separate environment for testing and development This was done with an automated code delivery process with Docker Stack Ansible Jenkins CI CD first for the test environment and then for the production environment Building new scalable infrastructureThe old system was a monolithic server with a database and a folder to store all uploaded files This architecture makes server load scaling very difficult and is obsolete in mostly suitable only for CMS out of the box solutions but not for frameworks Deploying new code to the server was only possible via FTP and had to be done manually To resolve these issues first of all we moved the database and file storage from the server to remote services AWS RDS AWS S Third party services are more stable and already have a backup mechanism that is more secure and helps to prevent data leakage The next step was to wrap architecture with Docker and isolate each service NGINX PHP and Socket into containers This made it possible to configure a stable automatic code delivery to the server CI CD and also added opportunities for the optimization of the server resources Finally we gradually moved the code to a newer framework Codeigniter For this purpose a separate Docker container with a newer version of PHP was prepared Our team also created API Documentation Postman Collection with sample requests responses from the server to help front end and back end developers easily communicate about the nuances of the API Initially the project only had a month s work to do It was difficult to fit all the necessary improvements into such a limited period of time and it was a really interesting challenge for us to choose what was the most critical It s important to find ways to communicate the need for some code changes to the customer even if the end user won t see a clear benefit from it but it s crucial for functionality in the future You need to have the trust of the customer and provide transparency in your decisions As a result of a month s work the client decided to continue cooperation with our team and it made it possible to improve the code according to the plan prepared earlier without stopping the delivery of new functionality Georgii MirgorodPHP Team LeaderCASE STUDY REWRITING A LEGACY PHP COMMUNICATION APPLICATION FROM SCRATCHThe client s request was to add an iOS app to the existing website as well as improve the overall stability and maintainability of the system In the process of the initial investigation our team discovered that it was quite difficult to do this with the current architecture which presented us with the following challenges Bad app performance because of poor source code organization and qualityData split across several data storages made the support of the system complicated and time consumingMultiple bugs and errors prevented the system from adding new featuresSolutionOur PHP experts suggested rewriting the app from scratch since Working with the existing code base and infrastructure would take more time than rewriting the applicationThe client was not limited in time and was focused on maximum improvementThe product was not used actively in the production environment Fixing bad app performance because of poor source code organization During the analysis stage our team discovered that the current application architecture was quite difficult to maintain and it did not allow for the easy addition of an iOS API The project included pieces of code written in different languages ​​and pieces of data stored on different platforms such as MySQL Neoj and Google Cloud storage amp Firebase The logic was mostly client side with the notifications system being the only server side asset So we set about creating a new version from scratch moving the logic to the server side and consolidating the existing data into a single database The existing legacy project helped us define the ultimate vision for the new app We chose a new technology stack with a modern PHP framework and created an effective and scalable architecture The iOS app and its API were the main development focus and in the later stages we recreated the existing website as a SPA using the same API This approach was intended to provide easier iOS app integration improve stability and performance and provide opportunities for potential future improvements Consolidating data into a single databaseThe existing MySQL database was taken as the basis of development as it contained the most data however we made improvements to its structure and indexes to provide better performance and data consistency We also added a migration tool Since then the old version of the project has not been used for reference instead the functionality was rebuilt based on the customers current vision and ideas The development and testing servers were created on Amazon Cloud We also added an admin panel to simplify user data management and an automatic documentation page for the API that updates in real time and provides the ability to test API functionality for client side developers Adding new features to the systemAfter the successful launch we continued to improve the project A cache was added and the database was moved to RDS to improve performance Websocket notification was implemented to provide real time chat We ve also updated the notification system to be easily configurable and include email and SMS notifications The admin panel receives constant quality of life updates including the ability to communicate directly with users through the associated account After about a year of cooperation the new project branched off from the existing one taking its data as a basis This new project was later successfully migrated to another cloud service due to a number of legal and geographic reasons and now it s in constant development alongside the original one Currently both projects are still actively used and allow users around the world to connect and share their experiences Dmytro LisovinPHP Developer Why PHP is Still Good in If you have concerns about whether you should stay with PHP and opt for modernization or better migrate to another tech stack let me dispel your doubts and tell you why PHP is still in demand in Being an open source PHP has a great development community that constantly improves this programming language New frameworks and tools open the door for new opportunities and help PHP stay competitive in the market Low cost for development and maintenance with very high performance and reliability made it the main choice for of all the websites according to WTech PHP is used by both enterprises and startups It is a great option for long term projects that want to grow since PHP is scalable by design Also it has a good loading speed even on slow Internet connections Since PHP its performance has increased almost two times over In our experience PHP is a great tool for the following types of projects Server side rendering SSR websitesRESTful web services API Social applications that require scalable architecture and specific features like likes dislikes messaging comments Server less applicationsComplex systems with great functionality like ERP and CRM platformsE commerce marketplace booking platformsMobile Device Management MDM systemsHealthcare projects that focus on securityOf course PHP is not a silver bullet and it has certain drawbacks For example it s not the best choice for CPU consuming tasks If you need to run heavy tasks with the best possible performance then it s better to use other compiled languages like Golang C or C	2023-04-05 17:37:24
Apple	AppleInsider - Frontpage News	Keanu Reeves & Jonah Hill coming to Apple TV+ in 'Outcome'	https://appleinsider.com/articles/23/04/05/keanu-reeves-jonah-hill-coming-to-apple-tv-in-outcome?utm_medium=rss	Keanu Reeves amp Jonah Hill coming to Apple TV in x Outcome x Keanu Reeves is starring in writer and director Jonah Hill s comedy Outcome comedy coming soon to Apple TV More Jonah Hill content coming to Apple TV Apple Original Films has picked up the dark comedy that Hill will direct and has co written with Ezra Woods Reeves and Hill are said to star in the film although Reeves is currently in negotiations Read more	2023-04-05 17:52:01
Apple	AppleInsider - Frontpage News	Apple users race to replace their iPhones more quickly than an iPad or Mac	https://appleinsider.com/articles/23/04/05/apple-users-race-to-replace-their-iphones-more-quickly-than-their-ipad-mac?utm_medium=rss	Apple users race to replace their iPhones more quickly than an iPad or MacUnsurprisingly a survey demonstrates that the iPhone is more critical in Apple users lives than an iPad or Mac leading to faster replacements iPhone users quickly replace devicesAll three devices are essential enough to warrant quick repairs or replacements if needed and people tend to repair or replace their iPhones more quickly than their iPad or Macs Consumer Intelligence Research Partners surveyed Apple customers on their preferences Read more	2023-04-05 17:17:31
海外TECH	Engadget	Two alcohol recovery startups just got caught sharing private user data	https://www.engadget.com/two-alcohol-recovery-startups-just-got-caught-sharing-private-user-data-171504445.html?src=rss	Two alcohol recovery startups just got caught sharing private user dataOnline alcohol recovery startups Monument and Tempest got caught sharing confidential user data with advertisers without their consent as originally reported by TechCrunch Everything came to light after an internal review revealed a data breach impacting users forcing the companies to issue a formal disclosure to the user base The violations started in and were ongoing until last month s review Monument and Tempest started as two entirely different platforms but the former acquired the latter several months back Parent company Monument confirmed not only the data breach but that the companies shared private information with advertisers via a notification filed with California s attorney general Data shared with advertisers without user consent includes patient names dates of birth email addresses postal addresses phone numbers insurance information and more Unfortunately that is just the beginning In a cruel insult to those seeking recovery the companies also shared data related to appointment information assessment information and survey responses which includes alcohol consumption data Monument continues to tout its commitment to privacy on its website saying that survey responses are “protected quot despite the recent disclosureThe companies blame third party tracking systems for the issue stating that they have removed the offending tracking codes from their websites The companies do not admit to sharing this information on purpose to increase profits indicating that the tracking pixels provided by third parties did the deed all on their own Though this is an especially egregious example it is important to remember that most companies have a less than pristine record regarding data privacy even in the case of medical records There is a near endless list of similar violations like the time a mental health startup shared patient information without consent and when Meta was caught with its own hand in the digital cookie jar Be careful out there folks This article originally appeared on Engadget at	2023-04-05 17:15:04
海外TECH	Engadget	Google will require that Android apps let you delete your account and data	https://www.engadget.com/google-will-require-that-android-apps-let-you-delete-your-account-and-data-170618841.html?src=rss	Google will require that Android apps let you delete your account and dataGoogle wants to make it as easy to scrub an app account as it is to create one The company has announced that Android apps on the Play Store will soon have to let you delete an account and its data both inside the app and on the web Developers will also have to wipe data for an account when users ask to delete the account entirely The move is meant to quot better educate quot users on the control they have over their data and to foster trust in both apps and the Play Store at large It also provides more flexibility You can delete certain data such as your uploaded content without having to completely erase your account Google says The web requirement also ensures that you won t have to reinstall an app just to purge your info The policy is taking effect in stages Creators have until December th to answer questions about data deletion in their app s safety form Store listings will start showing the changes in early Developers can file for an extension until May st of next year The changes come several months after Apple instituted a similar rule for App Store software In both cases the companies are concerned about privacy violations and the ensuing fallout ーthey don t want users to fall prey to data breaches because they couldn t easily delete accounts or sensitive info when they stop using an app This also follows growing efforts by regulators to demand more control over services The Federal Trade Commission FTC recently proposed rule changes requiring easy ways to cancel subscriptions and memberships While the FTC is focused more on unwanted charges than privacy the message to app makers is clear provide more control of accounts or face repercussions This article originally appeared on Engadget at	2023-04-05 17:06:18
Cisco	Cisco Blog	Cisco Catalyst IE3100 Rugged Series switches: Big benefits, small footprint	https://feedpress.me/link/23532/16058538/cisco-catalyst-ie3100-rugged-series-switches-big-benefits-small-footprint	extreme	2023-04-05 17:29:32
金融	金融庁ホームページ	鈴木財務大臣兼内閣府特命担当大臣閣議後記者会見の概要（令和５年４月４日）を掲載しました。	https://www.fsa.go.jp/common/conference/minister/2023a/20230404-1.html	内閣府特命担当大臣	2023-04-05 17:58:00
ニュース	BBC News - Home	Barge to house 500 male migrants off Dorset coast, says government	https://www.bbc.co.uk/news/uk-65193446?at_medium=RSS&at_campaign=KARANGA	groups	2023-04-05 17:25:26
ニュース	BBC News - Home	Nicola Sturgeon's husband Peter Murrell arrested in SNP finance probe	https://www.bbc.co.uk/news/uk-scotland-65187823?at_medium=RSS&at_campaign=KARANGA	headquarters	2023-04-05 17:52:19
ニュース	BBC News - Home	Tory MP Scott Benton filmed offering to lobby ministers	https://www.bbc.co.uk/news/uk-politics-65193097?at_medium=RSS&at_campaign=KARANGA	reporters	2023-04-05 17:14:49
ニュース	BBC News - Home	Ukraine war: Poland pledges more jets to Ukraine as Zelensky visits	https://www.bbc.co.uk/news/world-europe-65194094?at_medium=RSS&at_campaign=KARANGA	poland	2023-04-05 17:18:11
ニュース	BBC News - Home	Cash App founder dead: Bob Lee dies after San Francisco stabbing	https://www.bbc.co.uk/news/world-us-canada-65191466?at_medium=RSS&at_campaign=KARANGA	francisco	2023-04-05 17:01:49
ニュース	BBC News - Home	Dover to stagger coaches to avoid Easter delays	https://www.bbc.co.uk/news/business-65187441?at_medium=RSS&at_campaign=KARANGA	border	2023-04-05 17:01:37
ニュース	BBC News - Home	Daniel Podence: Wolves winger charged by the Football Association after allegedly spitting	https://www.bbc.co.uk/sport/football/65196238?at_medium=RSS&at_campaign=KARANGA	Daniel Podence Wolves winger charged by the Football Association after allegedly spittingWolves winger Daniel Podence has been charged by the Football Association after he allegedly spat at Brennan Johnson during Saturday s draw with Nottingham Forest	2023-04-05 17:44:50
ビジネス	ダイヤモンド・オンライン - 新着記事	精神科医が「絶対にやるべきだ」と断言する朝のベスト習慣――ストレスフリーに生きる方法【書籍オンライン編集部セレクション】 - ストレスフリー超大全	https://diamond.jp/articles/-/320412	精神科医が「絶対にやるべきだ」と断言する朝のベスト習慣ーストレスフリーに生きる方法【書籍オンライン編集部セレクション】ストレスフリー超大全コロナ禍や自粛生活などの「環境の変化」により、多くの人が将来への不安を抱え、「大きなストレス」を感じています。	2023-04-06 02:50:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【レシピあり】豚こまとじゃがいもだけで4種類の料理を作る！ - てんきち母ちゃんの はじめての自炊 練習帖	https://diamond.jp/articles/-/320199	【レシピあり】豚こまとじゃがいもだけで種類の料理を作るてんきち母ちゃんのはじめての自炊練習帖お子さんの初めてのひとり暮らし、ご自身の転勤、単身赴任など‥‥。	2023-04-06 02:45:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「雑談上手な人」がやっている、たった1つの考え方 - 99％はバイアス	https://diamond.jp/articles/-/320431	雑談	2023-04-06 02:40:00
ビジネス	ダイヤモンド・オンライン - 新着記事	【精神科医が教える】 話し方・書き方…伝え方が上手な人が“密かにやっている”たった1つのこと - 精神科医Tomyが教える 心の執着の手放し方	https://diamond.jp/articles/-/318905	【精神科医が教える】話し方・書き方…伝え方が上手な人が“密かにやっているたったつのこと精神科医Tomyが教える心の執着の手放し方【大好評シリーズ万部突破】誰しも悩みや不安は尽きない。	2023-04-06 02:35:00
ビジネス	ダイヤモンド・オンライン - 新着記事	気づいた時はもう遅い…「40代後半」転職したくてもできない人の末路 - 定番読書	https://diamond.jp/articles/-/320311	判断基準	2023-04-06 02:30:00
ビジネス	ダイヤモンド・オンライン - 新着記事	若手もベテラン社員も「絶対に身につけたい」能力 - 20代が仕事で大切にしたいこと	https://diamond.jp/articles/-/320396	飯塚	2023-04-06 02:25:00
ビジネス	ダイヤモンド・オンライン - 新着記事	「もし何かあったら、電話をください」を英語でどう言う？ - 5分間英単語	https://diamond.jp/articles/-/320613	「もし何かあったら、電話をください」を英語でどう言う分間英単語「たくさん勉強したのに英語を話せない……」。	2023-04-06 02:15:00
Azure	Azure の更新情報	Generally available: Large disk support for disaster recovery of Hyper-V VMs using Site Recovery	https://azure.microsoft.com/ja-jp/updates/large-disk-hyperv-dr/	disaster	2023-04-05 18:00:04