投稿時間:2023-07-27 19:23:51 RSSフィード2023-07-27 19:00 分まとめ(32件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
IT	InfoQ	Presentation: The Endgame of SRE	https://www.infoq.com/presentations/sre-scale-sociotechnical/?utm_campaign=infoq_content&utm_source=infoq&utm_medium=feed&utm_term=global	Presentation The Endgame of SREAmy Tobey discusses sociotechnical thinking exploring ways SREs can impact reliability at scale By Amy Tobey	2023-07-27 09:27:00
IT	ITmedia 総合記事一覧	[ITmedia News] ゲームブランド「Key」のビジュアルアーツ、中国Tencent子会社に　社長が歳を取ったため	https://www.itmedia.co.jp/news/articles/2307/27/news169.html	itmedia	2023-07-27 18:20:00
IT	ITmedia 総合記事一覧	[ITmedia News] サントリー、生成AIで「Ｃ．Ｃ．レモン」を擬人化　期間限定でプロモーションに利用	https://www.itmedia.co.jp/news/articles/2307/27/news165.html	itmedia	2023-07-27 18:01:00
TECH	Techable（テッカブル）	CS・マーケ・会計などの業務を自動化する“LLMアプリ”を自社環境でノーコード開発できる「Alli for LLM」	https://techable.jp/archives/214160	専門知識	2023-07-27 09:00:37
python	Pythonタグが付けられた新着投稿 - Qiita	画像の差分取得	https://qiita.com/katsudon_qiita/items/db2de2f0df58b7ed6027	portcvimshowdefimagedif	2023-07-27 18:16:30
AWS	AWSタグが付けられた新着投稿 - Qiita	Athena で S3 Glacier で復元されたデータのクエリを実行する	https://qiita.com/leomaro7/items/a36138c6098c4239c97e	athena	2023-07-27 18:21:18
AWS	AWSタグが付けられた新着投稿 - Qiita	[AWS Q&A 365][AppSync]AWSのよくある問題の毎日5選 #99	https://qiita.com/shinonome_taku/items/edbc5b3a6e9eb56e8573	awsappsync	2023-07-27 18:14:12
AWS	AWSタグが付けられた新着投稿 - Qiita	[AWS Q&A 365][AppSync]Daily Five Common Questions #99	https://qiita.com/shinonome_taku/items/fa498a3d8129eba3e35a	appsync	2023-07-27 18:13:43
Azure	Azureタグが付けられた新着投稿 - Qiita	[Azure Databricks] データガバナンスのベストプラクティス（翻訳）	https://qiita.com/akihiro_suto/items/0c27eada48bd0feeb1f5	azuredatabricks	2023-07-27 18:19:41
Azure	Azureタグが付けられた新着投稿 - Qiita	[Azure Databricks] セキュリティのベストプラクティス（翻訳）	https://qiita.com/akihiro_suto/items/7fe6918af0cdd0c79fdd	azuredatabricks	2023-07-27 18:15:35
Git	Gitタグが付けられた新着投稿 - Qiita	git コマンドメモ	https://qiita.com/xriux/items/2401b86cdc56fe0cd0a5	gitconfigglobalusere	2023-07-27 18:43:58
技術ブログ	Developers.IO	「AWS CloudFormationの組み込み関数を使って柔軟なCFnテンプレートを作成しよう」というビデオセッションで話しました #devio2023	https://dev.classmethod.jp/articles/devio2023-video-114-aws-cloudformation_intrinsic-function/	awscloudformation	2023-07-27 09:18:48
技術ブログ	Developers.IO	メモを DynamoDB へ保存する LINE ボットを作ってみた	https://dev.classmethod.jp/articles/linebot-for-saving-memo-to-dynamodb/	dynamodb	2023-07-27 09:16:48
海外TECH	DEV Community	The Magic of Ephemeral Preview Environments	https://dev.to/livecycle/the-magic-of-ephemeral-preview-environments-49pb	The Magic of Ephemeral Preview Environments The magic of ephemeral preview environments This article was originally written by Kunal Kushwaha and published here on the We Make Devs blog In traditional monolithic systems reviewing code was a relatively simple process As the entire application is bundled as just one single component building the entire project either locally or in an online coding environment such as Replit or GitHub codespaces is all you needed to do to view the changes and see how they would work However the story changes as we move to a microservice based architecture In a microservice architecture the entire application is broken down into many small components which are designed to be their own self contained applications This means that these small components can run without depending on the other components in the architecture Perhaps you can already see the problems that arise while reviewing changes to such codebases Since every application is a self contained app in order to review some code changes and see the impact of the change across the entire application i e when all the microservices are running and working together you would need to build each and every microservice While this type of architecture has benefits in a production system it does make it difficult to review code and see the impact of changes across the entire application This is where we can leverage the power of preview environments Why do we have so many environments Before the look at preview environments let s try to understand why we have multiple different environments By understanding this we will be able to appreciate the benefits of preview environments even more In a system that runs on Kubernetes i e an application or multiple applications that use a microservice architecture we have many different environments These environments all have different functions and use cases Some of the common environments include a production environment a staging environment a QA environment a local development environment etc Each of these environments has a different use case For example the main use case for a local development environment would be to write code for the application We talked about the complexities of building a microservice application earlier You would need to build up many individual services and connect them to see the full extent of the code changes In a local environment this can be done either by using a docker compose service or a local Kubernetes cluster such as Kind or Minikube The QA environment would be concerned with making sure that all the components are working correctly or not The staging environment would be used to test the features before they are added to production As you can see there are tons of different environments for applications There might be even more environments depending on the needs of the applications As such it can be difficult to efficiently manage so many different environments The environments might not all be the same either which can lead to some problems For example a local development environment runs at a much smaller scale than a production environment While the production environment might be using microservices due to scaling a local environment would have only a fraction of that number As such it can be difficult to anticipate problems that might arise in the production environment Why consider using preview environments We already talked about so many different kinds of environments Now let us talk about one more environment called preview or ephemeral environments These are temporary environments that live for a short period of time before getting destroyed Why would we want to have these kinds of environments Let s first try and understand the entire workflow without using preview environments The first step in the entire process to add a new feature or existing one would be to write the code for the application This would be done by a developer someone who understands how to read and write code After doing a bit of local testing they will push the code to their git repository whether it s GitHub or GitLab and then open a PR MR to merge the code for the new feature to the upstream repository Assuming that the best practices for git workflows are being followed this feature would be opened in a new branch in the upstream repository This is where other developers will be able to review the code for this new feature point out bugs and suggest some improvements However the main point to note is that the code review is being done by other developers who also understand how to read and write code Product teams designers or other stakeholders will not be able to make sense of this code Once other developers review the code it would get merged into the new branch and this new branch would be visible in one of your test environments such as the staging environment At this stage the product managers designers and other non technical teams would be able to view all the changes to the application use it and make sure all the functionality works as expected etc Now let s say that the designer finds something that is wrong with the design or the product manager finds that certain functionality isn t working as expected Now it is back to the developers to update the code to make sure the problems are fixed However developers will need to do the entire process all over again They will need to make a new branch open a new PR get it reviewed once more and then push it to staging again This is quite a tedious process and wastes a lot of time as well as resources It can also be an expensive process as your preview environments which are running in Kubernetes would use up more resources Imagine the benefit if the product and other non technical teams were able to preview the application in the PR itself before it gets pushed to staging This not only can save time and energy but can also save money in the long run This is the entire idea behind a preview environment These environments are automatically created when you open a PR and get destroyed once your code is merged into the main branch Thanks to these preview environments other stakeholders of the product are able to view the changes and provide feedback just as developers would provide code reviews Preview environments are not beneficial only to non technical teams Oftentimes when developers are asked to provide code reviews they might be working on some other features In order to provide a review they would need to clone the changed code and run it locally which would disrupt their own development tasks With the help of preview environments they wouldn t need to go through the additional steps of cloning and building the project They can simply use the same preview environment to see the changes and the code at the same time and make live changes as required What are some preview environments that can be used One of the most simple use cases for preview environments is for previewing front end applications This is easy to do by using services such as Netlify and Vercel These services let you preview your code changes even before you push the code into your branch This lets you create changes to the front end and view it in real time However a front end is just a monolith The process of creating these preview environments gets difficult as the application gets distributed between multiple microservices It might even be distributed over s of microservers which makes it increasingly difficult to create preview environments for them The problem of creating a preview environment is theoretically solved for a local computer On your local system you can very easily create a docker compose file and use docker compose to deploy all the components of the application locally However this is limited to your local environment which means you are the only one who is able to preview the application A proper solution would be if these local implementations can somehow be used on the cloud This is exactly what Preevy by Livecycle does in order to create some preview environments Preevy is able to take your Docker Compose files and instead of running it on a local system it runs it in a VM on the cloud Preevy can also create its own HTTPS links which allows anyone from your team to access the preview website after authenticating If your Docker Composer environment is configured correctly in a local environment using Preevy is as simple as running a simple preevy up command instead of running docker compose up as you would for a local environment Preevy can also run on your Kubernetes cluster and create environments inside your cluster itself Some challenges with setting up preview environmentsThe main problem with adopting preview environments in your entire development workflow would just be to solve the same issues that you face while setting up local environments While creating a local docker compose environment there are a few challenges you might run into These challenges can range from incorrect container build instructions to configuration issues or even an issue with how the containers talk with each other Another challenge lies in working with data As we know containers are ephemeral which means they don t work very well for storing data This can lead to a few challenges while working with databases and applications that rely on data In a nutshell the only challenges that you will face while setting up a preview environment are the same ones you face while setting up a local environment If your docker compose environment works without any issues then your preview environment which is created by Preevy will work in the exact same way Another challenge with preview environments arises if your microservices are in different repositories Let s say that your front end exists in one repository and your back end is in another repository This poses a challenge while connecting the two separate environments This is a little easier to solve if all the different microservices exist within the same repository You also need to make sure that your preview environments are performant while also not increasing costs Since the preview environments use VMs it s easy to potentially create s of preview environments which might increase the costs exponentially In this case it is important to create and destroy these preview environments quickly and not let them live for too long ConclusionIn order to optimize your development workflows and allow other stakeholders to review changes to the application before pushing your code to a staging environment it s important to use preview environments They help reduce the time and effort needed to make a change and changes can be made instantly within the PR itself Instead of pushing the changes to a staging environment and then getting the changes reviewed you can simply review them inside the PR itself This saves both time and energy and if done right can save costs as well Try setting up some staging environments for your repositories using Preevy You can also check out the documentation to help you get started	2023-07-27 09:55:06
海外TECH	DEV Community	Announcing the Launch of Godot Community Website: Embracing an Open and Diverse Ecosystem!	https://dev.to/godot/announcing-the-launch-of-godot-community-website-embracing-an-open-and-diverse-ecosystem-43n0	Announcing the Launch of Godot Community Website Embracing an Open and Diverse Ecosystem Hello fellow Godot enthusiasts and developers I m thrilled to announce the official launch of the Godot Community website at This community driven platform aims to bring together Godot users from all corners of the world to foster collaboration knowledge sharing and a sense of belonging in the open source game development community Embracing Diversity and DecentralizationFor open source communities like Godot diversity and decentralization are key strengths that empower community members to freely contribute engage and take ownership Instead of centralizing everything and smacking them all into an official channel our goal is to embrace a more open and decentralized approach allowing for a richer and more diverse ecosystem A Community Driven Godot HubGodot stands out as an open source project with a passionate community that doesn t rely on corporate backing The everyone can take part of it and be part of it philosophy lies at the heart of Godot s success and drives our community The Godot Community website is a hub where you can connect with fellow enthusiasts participate in discussions and share your projects and ideas Diverse Communication ChannelsWhile an official forum has its merits we believe that maintaining a diverse array of communication channels is crucial for the long term growth and vibrancy of the Godot ecosystem In addition to our website s forum we encourage community members to interact through platforms like Reddit social media groups and more This approach allows for different perspectives and enables everyone to find their preferred space within the community Community Focused and RunOur website is entirely community based and community run designed to complement the official channels while focusing on the passionate community around Godot While the official channel primarily addresses the Godot project itself our website takes pride in nurturing and supporting the people who make up this wonderful community Join us now and be a part of this growing community dedicated to learning sharing and fostering a supportive environment for Godot users worldwide Website Let s embark on this exciting journey together and make Godot Community the go to place for all things Godot Happy Game Development	2023-07-27 09:37:00
海外TECH	DEV Community	Next Js Vs Nuxt Js 🔥	https://dev.to/bindupatidar/next-js-vs-nuxt-js-2gck	Next Js Vs Nuxt Js Next js and Nuxt js are both popular frameworks for building server side rendered SSR or statically generated SSG web applications using React and Vue js respectively Let s compare the two frameworks Language and Ecosystem Next js Built on top of React which is a widely used JavaScript library for building user interfaces It benefits from the vast React ecosystem and community support Nuxt js Built on top of Vue js a progressive JavaScript framework for building user interfaces It leverages the Vue js ecosystem and its plugins SSR and SSG Support Next js Provides support for both Server Side Rendering SSR and Static Site Generation SSG You can choose between these rendering methods depending on your application s needs Nuxt js Also supports both SSR and SSG Like Next js you can choose the rendering method that suits your project requirements Data Fetching Next js Offers various data fetching methods including getServerSideProps getStaticProps and getInitialProps to fetch data during server side rendering or static generation Nuxt js Provides fetch asyncData and other lifecycle hooks for data fetching during server side rendering and static site generation Routing Next js Uses a file based routing system where each page is represented by a corresponding file in the pages directory This makes it straightforward to organize routes Nuxt js Employs a similar file based routing system as Next js making it easy to manage routes by creating files inside the pages directory Configuration Next js Follows a convention over configuration approach making it easy to get started without much configuration However you can customize the behavior by modifying the next config js file Nuxt js Provides a configuration file called nuxt config js allowing you to customize various aspects of your application easily Plugins and Modules Next js Utilizes a plugin system that allows you to extend the functionality of your application easily Nuxt js Uses a module system that provides a wide range of pre built modules to add extra features to your application Community and Documentation Next js Backed by a large community and offers extensive documentation making it easy to find solutions to common problems Nuxt js Also has a vibrant community and comprehensive documentation to help developers at all skill levels Choosing between Next js and Nuxt js largely depends on your familiarity with React or Vue js and your project requirements Both frameworks are powerful and offer excellent SSR and SSG capabilities so you can t go wrong with either choice Pick the one that aligns better with your existing knowledge and project needs	2023-07-27 09:24:41
海外TECH	DEV Community	“Top Frontend Interview Questions : (Part 1) — Boost Your Knowledge and Ace Your Next Job Interview!”	https://dev.to/blackhorse0101/top-frontend-interview-questions-part-1-boost-your-knowledge-and-ace-your-next-job-interview-3b39	“Top Frontend Interview Questions Part ーBoost Your Knowledge and Ace Your Next Job Interview Hey there Are you excited about your upcoming job interview in the field of frontend development and so am I And I ve got some exciting news for you ーI m also preparing for interviews and I ll be sharing all the interview questions I learn each day with you This way we can both learn together and be better prepared for our interviews Now I know that preparing for interviews can be a bit daunting but don t worry ーwe ll make it easy We ll break down each question into simple terms that anyone can understand and we ll have a blast doing it So what are we waiting for let s get started What are the Semantic elements in HTML Semantic elements in HTML are simply tags that have meaningful names which tells about what type of content it stores For example header footer table nav …etc HTML introduces many semantic elements which make the code easier to write and understand for the developer as well as instructs the browser on how to treat them Difference between position relative and position absolute Relative Position For relative positioned elements the origin is their original position in the normal flow of the document If you apply top px to it it will move px down from it s original position not affecting the normal flow of the document Absolute Position However for absolute positioned elements the origin is it s first parent which has a relative absolute or fixed position If you apply top px to it it will move px down from it s parent s top So it goes out of the normal document flow affecting the other elements location Fixed Position position fixed property applied to an element will cause it to always stay in the same place even if the page is scrolled To position the element we use top right bottom left properties relative vs absolute positioningWhat is flexbox CSS Flexbox is a one dimentional CSS layout module that is used to arrange and organize items on web pages in one direction i e horizontally and vertically row or column and control how they stretch shrink or wrap The Flexible Box Layout Module makes it easier to design flexible responsive layout structure without using float or positioning What is Box model in CSS In CSS the term “box model is used when talking about design and layout The CSS box model is essentially a box that wraps around every HTML element It consists of margins borders padding and the actual content The content is what s inside the box like text or an image The padding is the space between the content and the border The border is the line that surrounds the box and the margin is the space between the border and other elements on the page CSS Box ModelCSS Box ModelWhat is Event Loop The Event Loop is a key concept in JavaScript that helps with handling asynchronous code In simple terms it s a loop that constantly checks if any code needs to be executed and if so it executes that code Here s how it works when you run a piece of code that takes some time to complete like fetching data from a server or waiting for a user s input JavaScript doesn t just stop and wait for that code to finish Instead it moves on to the next line of code and checks back later to see if the previous code has finished executing This checking process is done by the Event Loop It constantly checks the queue of tasks that need to be executed and when it finds one it puts it in the Call Stack which is a data structure that keeps track of all the code being executed The Call Stack then executes that code and once it s done it removes it from the stack and moves on to the next task In summary the Event Loop is what allows JavaScript to handle asynchronous code by constantly checking for tasks that need to be executed and executing them in the right order Now within the event loop there are two types of tasks ーmicrotasks and macrotasks Microtasks are small high priority tasks that need to be executed immediately Examples of microtasks include promise callbacks mutation observers and queueMicrotask While macrotasks are larger lower priority tasks that can be executed later These tasks include things like setTimeout setInterval and requestAnimationFrame Understanding the difference between these two types of tasks is important for writing efficient performant JavaScript code What is DOM The Document Object Model or DOM for short is like a tree structure that represents the content of a webpage in code This structure includes all the elements like headings and paragraphs and allows developers to access and modify them using JavaScript The DOM helps to create dynamic and interactive webpages without having to reload the entire page Think of it as a way for developers to talk to a webpage and make changes to it in real time What is Hoisting in JavaScript Hoisting is a concept which enables us to extract values of variables and functions even before initialising assigning value without getting error and this is happening due to the st phase memory creation phase of the Execution Context The execution context gets created in two phase so even before code execution memory is created so in case of variable it will be initialized as undefined while in case of function the whole function code is placed in the memory What is Closures Function bundled along with it s lexical scope is closure JavaScript has a lexical scope environment If a function needs to access a variable it first goes to its local memory When it does not find it there it goes to the memory of its lexical parent See Below code Over here function y along with its lexical scope i e function x would be called a closure A closure is a function that has access to its outer function scope even after the function has returned Meaning A closure can remember and access variables and arguments reference of its outer function even after the function has returned See Below code Over here function y along with its lexical scope i e function x would be called a closure function x var a function y console log a return y var z x console log z value of z is entire code of function y In above code When y is returned not only is the function returned but the entire closure fun y its lexical scope is returned and put inside z So when z is used somewhere else in program it still remembers var a inside x What is Callback Hell Callback Hell is a situation that can occur in JavaScript programming when there are too many nested callbacks It can happen when you have to execute multiple asynchronous functions one after another and each function depends on the result of the previous function To avoid Callback Hell we can use promises async await or other techniques to make the code more readable and manageable Difference between map filter and reduce Map filter amp reducer are Higher Order Functions Map The map function takes an array and creates a new array with each element transformed based on a function provided For example if you had an array of numbers you could use map to create a new array with each number multiplied by Filter The filter function takes an array and creates a new array with only the elements that pass a test based on a function provided For example if you had an array of numbers you could use filter to create a new array with only the even numbers Reduce The reduce function takes an array and returns a single value by performing a specified operation on each element of the array For example if you had an array of numbers you could use reduce to find the sum of all the numbers in the array	2023-07-27 09:07:26
医療系	医療介護 CBnews	認知症疾患センター、愛知県が新たに1カ所指定へ-東三河南部医療圏で2カ所目	https://www.cbnews.jp/news/entry/20230727180642	認知症疾患医療センター	2023-07-27 18:16:00
金融	金融庁ホームページ	金融庁の災害用備蓄食品において提供可能となる食品に関する情報を公表しました。	https://www.fsa.go.jp/choutatu/choutatu_j/choutatsu_saigaisyokuhin.html	食品	2023-07-27 10:00:00
金融	金融庁ホームページ	「ESG評価・データ提供機関に係る行動規範」の受入れを表明した評価機関等リストについて公表しました。	https://www.fsa.go.jp/news/r5/singi/20230727.html	評価	2023-07-27 10:00:00
ニュース	BBC News - Home	British Gas: Anger as energy bill change leads to record profits	https://www.bbc.co.uk/news/business-66315117?at_medium=RSS&at_campaign=KARANGA	bills	2023-07-27 09:50:38
ニュース	BBC News - Home	Prince Harry set for court showdown with Sun publisher	https://www.bbc.co.uk/news/uk-66322279?at_medium=RSS&at_campaign=KARANGA	breach	2023-07-27 09:30:20
ニュース	BBC News - Home	Man wrongly jailed for 17 years says 'world finally knows truth'	https://www.bbc.co.uk/news/uk-england-manchester-66323436?at_medium=RSS&at_campaign=KARANGA	justice	2023-07-27 09:43:02
ニュース	BBC News - Home	Co-op warns rising crime could create 'no-go' areas for shops	https://www.bbc.co.uk/news/business-66323140?at_medium=RSS&at_campaign=KARANGA	areas	2023-07-27 09:09:50
ニュース	BBC News - Home	Greece fires in maps and satellite images show extent of damage	https://www.bbc.co.uk/news/world-europe-66295972?at_medium=RSS&at_campaign=KARANGA	greece	2023-07-27 09:48:39
ニュース	BBC News - Home	Niger soldiers declare coup on national TV	https://www.bbc.co.uk/news/world-africa-66320895?at_medium=RSS&at_campaign=KARANGA	country	2023-07-27 09:53:24
ニュース	BBC News - Home	Wizz Air passengers may get refunds as claims reopened	https://www.bbc.co.uk/news/business-66322764?at_medium=RSS&at_campaign=KARANGA	aviation	2023-07-27 09:48:38
ニュース	BBC News - Home	Portugal 2-0 Vietnam: World Cup debutants set up USA showdown with victory	https://www.bbc.co.uk/sport/football/66290732?at_medium=RSS&at_campaign=KARANGA	Portugal Vietnam World Cup debutants set up USA showdown with victoryPortugal earn a face off with reigning champions United States for a place in the last of the Women s World Cup with an impressive win over Vietnam	2023-07-27 09:44:57
ニュース	Newsweek	ワニの腹から行方不明男性の遺体...衝撃の解剖シーン	https://www.newsweekjapan.jp/stories/world/2023/07/post-102286.php		2023-07-27 18:30:00
IT	週刊アスキー	「MSN-04FF サザビー」と「RX-93ff νガンダム」が『SDガンダムオペレーションズ』に参戦！	https://weekly.ascii.jp/elem/000/004/147/4147212/	総力戦	2023-07-27 18:55:00
IT	週刊アスキー	変装探偵のデスヒコが主人公！Switch『超探偵事件簿 レインコード』の追加コンテンツ第1弾が本日配信	https://weekly.ascii.jp/elem/000/004/147/4147206/	nintendo	2023-07-27 18:25:00
IT	週刊アスキー	話題のかき氷店が週替わりで登場！ そごう横浜店「アイスを愛す会」	https://weekly.ascii.jp/elem/000/004/147/4147194/	話題	2023-07-27 18:15:00