投稿時間:2023-03-27 16:20:53 RSSフィード2023-03-27 16:00 分まとめ(28件)

カテゴリー等	サイト名等	記事タイトル・トレンドワード等	リンクURL	頻出ワード・要約等/検索ボリューム	登録日
ROBOT	ロボスタ	立命館大学がマイクロデバイス内の電場や静電エネルギー分布の可視化に成功　マイクロマシンの性能向上に期待	https://robotstart.info/2023/03/27/ritsumeikan_microdevice_visualization.html		2023-03-27 06:07:14
IT	ITmedia 総合記事一覧	[ITmedia エンタープライズ] サプライチェーンは回復したのに「50％引きで販売」　アンダーアーマーの利益が減少する理由	https://www.itmedia.co.jp/enterprise/articles/2303/27/news059.html	itmedia	2023-03-27 15:45:00
IT	ITmedia 総合記事一覧	[ITmedia ビジネスオンライン] 結局トヨタが正しかったのか　EUが35年までのエンジン車禁止を断念	https://www.itmedia.co.jp/business/articles/2303/27/news145.html	itmedia	2023-03-27 15:34:00
IT	ITmedia 総合記事一覧	[ITmedia News] JALの「6600円セール」、3月31日に再開決定　2日間限定で	https://www.itmedia.co.jp/news/articles/2303/27/news142.html	itmedianewsjal	2023-03-27 15:30:00
IT	ITmedia 総合記事一覧	[ITmedia PC USER] PFU、ScanSnap用アプリ「ScanSnap Home」のライセンス制限を緩和	https://www.itmedia.co.jp/pcuser/articles/2303/27/news138.html	itmediapcuserpfu	2023-03-27 15:06:00
TECH	Techable（テッカブル）	勝って生き残れ！ 人狼ゲームモチーフADV「カテゴリー I ～死線上のサバイバー～」配信中	https://techable.jp/archives/201094	android	2023-03-27 06:00:40
AWS	AWS Japan Blog	メディアアセット管理ゲームのルールを変える PGA TOUR のアプローチ	https://aws.amazon.com/jp/blogs/news/jpmne-how-the-pga-tour-is-changing-the-media-asset-management-game/	pgatour	2023-03-27 06:13:04
python	Pythonタグが付けられた新着投稿 - Qiita	scipy.stats.truncnorm.rvs の高速化	https://qiita.com/RDProm/items/9f3a1629c331207d654f	scipystatstruncnormrvs	2023-03-27 15:44:33
python	Pythonタグが付けられた新着投稿 - Qiita	【Python】楽天商品検索APIと楽天RMS(Rakuten Merchant Server)APIの始め方	https://qiita.com/grapefruit1030/items/8d80bc8df7d5c13de3e2	newapp	2023-03-27 15:16:26
python	Pythonタグが付けられた新着投稿 - Qiita	DockerでNginx+uWSGI+Flask環境を作る	https://qiita.com/egcmrsk/items/e7e36770a31f0e1e1805	fromflask	2023-03-27 15:02:36
AWS	AWSタグが付けられた新着投稿 - Qiita	2023 AWS Top Engineers を申請する方法メモ	https://qiita.com/taro-yamada/items/8726af61b0e9ebf7b4d8	https	2023-03-27 15:19:44
Docker	dockerタグが付けられた新着投稿 - Qiita	Red Hat OpenShift on IBM Cloudで、内部レジストリ「OpenShift Container Registry（OCR）」にビルドされたイメージをローカルPCにpullする	https://qiita.com/ken-davidson/items/12ae2848d54952b64903	containerregistryocr	2023-03-27 15:20:30
Docker	dockerタグが付けられた新着投稿 - Qiita	DockerでNginx+uWSGI+Flask環境を作る	https://qiita.com/egcmrsk/items/e7e36770a31f0e1e1805	fromflask	2023-03-27 15:02:36
技術ブログ	Developers.IO	AWS Systems Manager高速セットアップで組織をパッチ管理する設計ポイント	https://dev.classmethod.jp/articles/how-to-deploy-ssm-patch-manager-quick-setup/	awsorganizations	2023-03-27 06:38:13
技術ブログ	Developers.IO	[マルチアカウントTIPS]IAM Identity Center の許可セットは「管理アカウント用」と「それ以外用」で分けて使おう	https://dev.classmethod.jp/articles/multi-account-tips-ps-for-management-account/	awsiamidentitycenter	2023-03-27 06:27:49
技術ブログ	Developers.IO	ChatGPTでS3のファイルを検索するコマンドを作ってみた	https://dev.classmethod.jp/articles/chatgpt-s3-search-file-command/	chatgpt	2023-03-27 06:00:25
海外TECH	DEV Community	Guide to Serverless & Lambda Testing — Part 3 — Advanced Asynchronous Flows	https://dev.to/aws-builders/guide-to-serverless-lambda-testing-part-3-advanced-asynchronous-flows-3gk6	Guide to Serverless amp Lambda Testing ーPart ーAdvanced Asynchronous FlowsSoftware testing increases application quality and reliability It allows developers to find and fix software bugs mitigate security issues and simulate real user use cases It is an essential part of any application development Serverless is an amazing technology almost magic like Serverless applications like any other applications require testing However testing Serverless applications differs from traditional testing and introduces new challenges In this post you will learn to test asynchronous event driven flows that may or may not contain Lambda functions Previous posts in the series Part ーyou learned why Serverless services introduce new testing challenges and my practical guidelines for testing Serverless services and AWS Lambda functions that mitigate these challenges Part ーyou learned to write tests for your Serverless service We focused on Lambda functions and provided tips amp tricks and code examples by writing tests for a real Serverless application In addition you learned my Serverless adaptation to the testing pyramid and implemented it A complimentary Serverless service project that utilizes Serverless testing best practices can be found here This blog was originally published on my website “Ran The Builder Serverless Testing Pyramid Re capIn the first post in the series I presented the Serverless testing pyramid This post assumes you are familiar with the testing pyramid and understand its principals We defined the following test stages Unit tests for our Lambda function business domain code ーtest input validation schemas and test isolated functions Infrastructure tests for our AWS CDK code that assert security best practices Integration tests that run post service deployment to AWS The tests run in the IDE call the Lambda handler entry function with a generated event and simulate happy flows and edge cases edge cases are simulated with mocks End to end tests that trigger the entire service on AWS with a customer input event My Testing MethodologyIn this section I will present my approach to Serverless testing and how I design the required tests for Serverless microservices based on the Serverless testing pyramid I base my approach on whether Lambda functions are present in the flow I d like to test Lambda Functions are IncludedWe learned how to test Lambda functions in the previous post We follow the testing pyramid guidelines and add a unit integration and end to end tests to our Lambda function For the integration tests we must generate the proper input event according to the asynchronous Lambda trigger it may be an SQS list of events a batch an EventBridge event a DynamoDB streams event etc For end to end tests we must trigger the chain of events that will eventually trigger the Lambda function on our AWS account Lambda Functions are Not IncludedLet s discuss use cases where there are no Lambda functions in your microservice Some examples come to mind a Step Function state machine with intrinsic functions and EventBridge pipes that conduct an ETL process and send an event forward to an EventBridge bus How do you test them You can t write unit or integration tests as you did for your Lambda functions there s no code and entry point to trigger locally it s all infrastructure configuration You should ask yourself SHOULD I test these AWS managed services or focus on the bigger picture the event destination and side effects My answer is Yes all we can and SHOULD do is an end to end test We will write end to end tests trigger the chain of events validate its side effects and ensure that the event reaches the end of the road properly as expected Let s look at some examples and see how to test the service Testing Asynchronous Messaging FlowsA pure asynchronous event driven flow A Lambda function is involved so we will write unit and integration tests The integration tests will generate a List of records see AWS SQS event example call the lambda handler and validate its side effects The Lambda function s side effects might include writing to a DynamoDB table calling an API etc In integration tests you can mock the calls to these side effects locally and assert that they are called and called with the correct parameters It s also crucial in this case to make sure the Lambda function which receives an SQS input event in the form of a list of events a batch does not raise an uncaught exception which causes the entire batch of events to get returned to the queue Be advised that in this case we can t simulate any SQS related side effects locally such as Verify proper handling of partial failures Validate we properly configured an SQS dead letter queue So these side effects will be tested only by EE tests For EE happy flow publish an SNS message to the SNS topic via AWS SDK and validate the function side effects put item to a DynamoDB table etc Another option is to poll the function log group filter by the expected log timestamp and verify that the function has reached a specific log message that asserts the action has occurred For EE failures make sure to read every managed service related documentation Amazon SQS has very informative documentation regarding handling partial failures and dead letter queue integration You can publish malformed events to the SNS topic and make sure they are sent to the preconfigured dead letters queue by waiting and fetching with a timeout messages from the dead letters SQS queue until the expected event is found test passes or a timeout occurs test fails Testing Synchronous amp Asynchronous FlowsThis use case contains synchronous and asynchronous flows the first two being synchronous and the last being asynchronous An API Gateway gets a POST request and writes to a DynamoDB table without a Lambda function involved uses an AWS Service proxy The DynamoDB table change triggers a DynamoDB streams event that triggers a Lambda function You cannot test locally in the IDE that the API Gateway and verify it writes to DynamoDB You can only test with an end to end test that will send the required POST request and validate the side effect that happened and the item was written You can do that by directly checking the DynamoDB table or by calling a GET item REST API on the API Gateway assuming there is such an API Now let s test the asynchronous flow A Lambda function is involved so we can write unit and integration tests The integrations test will generate an input event based on the DynamoDB stream event schema For errors simulation you can inject an invalid input event data call the Lambda function handler in the IDE and ensure it handles it correctly You can do that by mocking a specific error handling function and asserting that it was called and was called with the correct parameters For the end to end tests we will use the test for the synchronous part Now this is where it gets tricky We need to understand what is the side effect of Lambda We cannot use its return code as it triggered asynchronously and does not return a response we can get We will need to verify its side effect If the function writes to the DynamoDB table we will use a polling mechanism within the limits of reason and set a short timeout and a few retries and check the DynamoDB entry by calling the get API if there s no API we will use AWS SDK to look at the DynamoDB table directly This method applies to any other side effects it does Another option is to poll the function log group as done in the previous example and validate it has processed the event properly Please note that if the side effect is tricky to validate in EE flow it must at least get validated in the integration tests Once the integration test flow validates it the log group assertion can be good enough Testing Non Lambda Based Asynchronous FlowsThe EventBridge pipe definition In this case we have a non Lambda based EventBridge pipe Sets source event from an SQS queue Filters the event according to a predefined configuration Enriches the event with a Step Function state machine that contains only intrinsic functions no Lambda functions involved and returns an enriched event Sends the enriched event to an SNS topic In this case we use an AWS managed Serverless service and write ZERO Lambda function code Our “code is the infrastructure configuration code that builds these resources on AWS The Step Function states machineThe SQS queueThe SNS topicThe EventBridge pipe itselfAll the required roles and the configuration that ties the resources togetherSince no Lambda function is involved we can only write end to end tests We will need to write a test that puts a message in the entry SQS queue that matches the pipe filter and look at the end of the chain the SNS topic In our test environment account not production we will add a test only SQS queue to subscribe to the destination SNS topic We will not add this SQS in production environments In our test we will fetch messages from the test destination SQS until a message is received or a timeout is reached The test will fail if we encounter a timeout on our polling meaning the SNS message was not sent or if we get a malformed SQS message that does not match the entire enriched message schema the EventBridge pipe was supposed to produce Another option for EE tests is to individually test the Step Function state machine trigger it with an input wait for it to finish its run and validate its output via AWS SDK API whether it enriched the input event properly or not You should also test use cases where invalid inputs get to a fail state in the state machine A few observations While we didn t write ANY line of Lambda function code we did write parts of logic in the infrastructure configuration code whether the step function intrinsic steps or the EventBridge pipe filter part contains business domain schema logic We require fewer tests no integration or unit but I think the tests are less intuitive to write We can write only EE tests that trigger AWS resources and run on our AWS account	2023-03-27 06:15:24
海外TECH	DEV Community	What It Was Like To Code For Amazon (Conclusion)	https://dev.to/bytebodger/what-it-was-like-to-code-for-amazon-conclusion-3468	What It Was Like To Code For Amazon Conclusion You can read Part of this article here And Part here If you ve read any of the first two articles from this series you already know that my Amazon experience was suboptimal But the first thing I have to acknowledge is that I don t actually know what it s like to code for Amazon in general In fact even if you ve coded for Amazon in the past or even if you re coding for them now you don t know what it s like to code for them in general The company s far too big and there are far too many devs strewn across myriad teams and locations for any single person to say with authority exactly what the overall dev experience is like In a company that large all you can really do is assess your own experience Some people may have had experiences similar to mine or worse even But I m also certain that some Amazon coders are perfectly happy there It all depends to some extent on exactly which team group you worked within who exactly you worked for with and of course what you brought to the experience But while I can t paint a broad definitive picture of exactly what it s like for anyone in any Amazon team group I did see enough to draw some curious conclusions Lip Service To Principles Amazon constantly touts their Leadership Principles They ask you about them when you re interviewing They talk about them in company meetings On the surface at least they pour a lot of effort into these principles If you re curious you can see them all here Unfortunately a lot of this emphasis is empty talk I know I know A megacorporation that doesn t always live up to its own stated ideals SHOCKING I could go through them one by one and nitpick them based upon my short tenure there And my perspective is undoubtedly biased by my own negative experiences and my own admittedly brief tenure But in my experience the most glaring example of a completely failed principle is this Have Backbone Disagree and CommitLeaders are obligated to respectfully challenge decisions when they disagree even when doing so is uncomfortable or exhausting Leaders have conviction and are tenacious They do not compromise for the sake of social cohesion Once a decision is determined they commit wholly I saw so many examples that made this principle an outright joke that I can t even list them all here And I m not just talking about my experience I m talking about things I witnessed in other areas of the organization and things I was told directly by other employees I witnessed so many instances where people were simply afraid to speak up I sat in meetings where no one but the talking head dared utter any kind of objection And when they did bother to raise concerns I also saw where those concerns were bulldozed because there was no alternative that pleased management A Telling ObservationWhen I wrote this article about working at Amazon a senior dev from an entirely different part of the company reached out to me on Slack He praised the article thanked me for writing it and said he was glad to see that I was getting along nicely I thanked him for his feedback But I also told him that in the time since I wrote the article I d run into some very difficult situations I didn t deluge him with the full insanely long story of everything that had happened I just gave him the high level bullet points His response was very telling He was Australian He told me that in his previous job there were many times when the dev team would be discussing some particular bit of an application that had already been built And frequently they would find themselves saying to each other Yeah this is all a bit crap isn t it But he also told me that when he came onboard at Amazon he had very similar problems Because for a good bit after he was hired no one wanted to hear any kinda dissenting opinions even if they were only dissenting as a means to talk out the problem and to hopefully come to a better solution His specific advice was to lay low for a good while Don t say much Just kinda go along with whatever was being dictated to you And then only after you ve been onboard for a good bit maybe possibly speak up about a few targeted things To be clear I get this I d be the first one to tell you that no one wants the Brand New Guy to show up on Day and immediately tell everyone that they ve been doing crappy work And that the legacy app is shite And that all of their current practices should be thrown out the window But there s a difference between being an arrogant know it all versus just being a humble but confident member of the team Sometimes some of the best suggestions come from the new guys Because everyone else has grown accustomed to everything as the way it s always been done As long as the New Guy isn t a cocky jerk there s a lot of value in seeing how someone views the situation with a fresh set of eyes That s what Have Backbone Disagree and Commit is supposed to be about If you see something that seems off say something Talk about it with your colleagues Or your manager Or your stakeholders Sometimes when you raise those concerns you ll be voted down And that s fine Other times you may find that people actually agree with you but there are other practical reasons why it will continue to be done that way And again that s fine But it s far healthier to at least have those conversations rather than being afraid that you ll be labeled as a malcontent merely because you raised reasonable concerns A Big Brother MentalityHere s something that I encountered multiple times at Amazon And I found it to be a bit disturbing I d be chatting with someone on Slack about something that seemed off Maybe it was about a project Or about a particular person Or even about the company in general And in these scenarios with multiple different people the Slack conversation would end when the other person typed this Maybe we should delete this Slack conversation Now to be clear we weren t talking about bombing the CEO s house We weren t calling anyone an asshole In fact we weren t discussing anything in those Slack threads that I woulda been afraid to say to anyone else directly to their face We were just discussing problems that we d run into and potentially how to fix them And yet on numerous occasions my Slack counterpart would close the conversation by suggesting that we delete the thread Think about that Honestly every time I encountered it it felt rather chilling Blatant BackstabbingAfter coding for a quarter century I ve lost track of the number of coworkers who simply didn t like me Work at enough companies with enough colleagues and it s inevitable that some people simply won t take to you But that s not what I m talking about here Despite all the interpersonal conflicts I ve navigated throughout my career there is only one company where I ve experienced open backstabbing And of course that company was Amazon When I say backstabbing I m not referring to someone saying that I m a jerk take a number it s a long line Nor am I referring to someone badmouthing my code or my deliverables or anything about my work effort I m specifically talking about someone saying to my face that I m doing great work Then turning around whenever a project suffers from any kinda setback and telling everyone else that I ve screwed everything up I ve had people tell me to my face that they thought I really screwed something up To be honest once you get past the raw emotions of those moments sometimes those interactions can end on an extremely positive note But I ve never been anywhere else where someone told me one extremely supportive thing to my face and then told someone else in senior management the exact opposite when I wasn t there Frontend MyopiaThe vast majority of Amazon s software engineers specialize in backend development Specifically Java And there s nothing wrong with that But the company s overall view on frontend development seems to be mired in As a frequent Amazon customer I d noticed long before I ever worked there that their UX was pretty well lacking Now I know why To be fair they successfully drive billions in revenue through their website So I m not gonna claim that their frontend interfaces are somehow broken And whenever you re operating a site that runs on that kinda epic scale there are bound to be many considerations that simply don t apply to of the other websites that are out there I ll also acknowledge that there are some teams in Amazon doing frontend work that utilizes modern standards But it s kinda disturbing to see how many teams are oblivious to modern frontend capabilities Heck I even witnessed teams that were hostile toward any kinda modern frontend approaches In Amazon s internal knowledgebase some lifelong Java coder wrote a long screed talking about how frontend apps and modern frameworks like React were simply unmanageable and unscalable It s quite a long read Shortly after I came onboard I was asking one of our Java devs why we were doing things a certain way His response was to send me that internal article Nevermind the fact that the article in question was written in And nevermind the fact that on the article itself there s long been a disclaimer right at the top of the article stating that most of its contentions are now in doubt None of that mattered All that mattered was that JS frameworks were bad mmmkay and old skool client server architecture was good A Silver LiningMy last observation comes with a bit of a silver lining for me at least We all know that Amazon is just one of many Big Tech companies that s jettisoned scores of people in the last six months While I understand that layoffs are in a macro sense a sad reality of corporate life Amazon did everything they could to ensure that their internal and external communications around the matter were absolutely clumsy and quite frankly unprofessional I m not gonna go through all of that in detail here I m sure you ve read the articles in the tech business news Last month a new bit of ugliness came from Andy Jassy Effective May st they re requiring everyone to be in the office at least three days per week I m sure that in the final analysis there will be some people who manage to get excused from this edict But every indication so far is that there will be few exceptions In a sick sort of way this actually made me feel kinda relieved You see I live in Florida I m a remote worker When I was hired my offer specifically stated that I would be a remote worker There were others on my team working under the same pretenses And even if all the crap of the last year hadn t happened to me and even if I was never laid off in January I d now be stressed and infuriated by the whole situation So I guess that in the final analysis the last year of hell wasn t gonna turn out any better for me even if I never had any problems on my team and even if I was never booted under any of their layoffs As odd as it sounds that actually makes me feel somewhat better about the whole experience I m not gonna make any attempt to sugarcoat this What Amazon s doing now is an outright betrayal to the scores of people they hired over the last couple of years with the express understanding that they would be remote It s also a betrayal to so many of their Seattle workers who made significant life changes like moving away from Seattle to other parts of the country because they were given repeated assurances that they would not be forced to come back to the office Moving On I ve put articles on this site so far I wrote all of the others to hopefully spread knowledge learn from the Dev to community and foster discussion This little series of my life at Amazon articles was the first time that I ever wrote anything here that was not for those purposes I wrote these last three articles for me As I stated in Part this has basically been my self administered therapy a way for me to yell into the void about crap that I experienced over the last year That being said this not so little tale is not a tragedy Far from it I m currently evaluating one very solid offer from a potential employer I expect to receive a few other solid offers in the next coupla days The simple fact is that regardless of where I m working next month and regardless of what anyone on here thinks about my Amazon tale I ll be fine Beyond fine in fact As you ve no doubt surmised from these three articles there are absolutely some aspects of my Amazon experience that still feel crappy as hell And there was a period mostly from November through January that all of this took a serious toll on my mental and physical health But you know what That passes Life goes on And I ll be pissing people off at some new company before you know it Take care	2023-03-27 06:01:46
金融	ニッセイ基礎研究所	金融システム不安の台頭で不透明感が強まる円相場～マーケット・カルテ４月号	https://www.nli-research.co.jp/topics_detail1/id=74308?site=nli	しかし、その後は米銀の破綻を発端に欧米の金融システム不安が台頭したことで米利上げ観測が後退し、円高ドル安が進行。	2023-03-27 15:17:41
ニュース	BBC News - Home	Antonio Conte: Tottenham manager leaves after 16 months in charge	https://www.bbc.co.uk/sport/football/64168691?at_medium=RSS&at_campaign=KARANGA	spurs	2023-03-27 06:19:50
ニュース	BBC News - Home	Silicon Valley Bank: Collapsed US lender bought by rival	https://www.bbc.co.uk/news/business-65084248?at_medium=RSS&at_campaign=KARANGA	regulators	2023-03-27 06:50:01
ニュース	BBC News - Home	The Papers: 'Crunch vote on small boats' and laughing gas ban	https://www.bbc.co.uk/news/blogs-the-papers-65083908?at_medium=RSS&at_campaign=KARANGA	government	2023-03-27 06:32:15
ニュース	BBC News - Home	1Xtra: Reece Parkinson leaves BBC radio station after six years	https://www.bbc.co.uk/news/newsbeat-64978263?at_medium=RSS&at_campaign=KARANGA	drive	2023-03-27 06:06:31
ニュース	BBC News - Home	Antonio Conte: Nagelsmann, Pochettino, Enrique - who should be Tottenham's long-term successor?	https://www.bbc.co.uk/sport/football/65037269?at_medium=RSS&at_campaign=KARANGA	Antonio Conte Nagelsmann Pochettino Enrique who should be Tottenham x s long term successor Tottenham will be looking for a new manager this summer after the departure of Antonio Conte but who do you think they should appoint	2023-03-27 06:08:06
IT	週刊アスキー	都バスのマスコット「みんくる」がスマホリングになって登場！	https://weekly.ascii.jp/elem/000/004/130/4130210/	都バス	2023-03-27 15:45:00
IT	週刊アスキー	『機動戦士ガンダムUCE』の今がわかる公式生番組第15回が本日19時より配信！	https://weekly.ascii.jp/elem/000/004/130/4130217/	ucengage	2023-03-27 15:45:00
IT	週刊アスキー	JR東海、2028年までに東海道新幹線を自動運転化すると発表	https://weekly.ascii.jp/elem/000/004/130/4130184/	完全自動運転	2023-03-27 15:30:00
IT	週刊アスキー	『Winning Post 10』の公式生放送が3月31日に配信決定！	https://weekly.ascii.jp/elem/000/004/130/4130216/	発売予定	2023-03-27 15:20:00