It’s an honor! 🥹 @TIME's Best Inventions of 2023 recognizes some of our favorite features. We dedicate this to you, our community of customers and creators. Thanks for loving @Photoshop Generative Fill/Expand and @Acrobat Liquid Mode as much as we do! https://t.co/EaGXiUIhMP
Excited to work with @Google Bard and integrate #AdobeFirefly - hope to have many users enjoy our image generation and editing capabilities and our integration with @AdobeExpress !
https://t.co/PkXfCDkNho
40 years of incredible innovation @Adobe with our customers and partners. The announcements today on Content Supply Chain, Firefly GenAI, Next Gen #AEM composable services and Product Analytics sets the stage for the next decades of accelerating innovations #AdobeSummit
Working in a large tech company, one thing I wish every team had (but barely any have it):
A “map” of the teams that you depend on, that depend on you, and ones that are coupled to your work in one way or the other.
One map for engineering teams; another for non-eng ones.
When considering IT costs, there are three costs that should guide you: cost of delay, opportunity cost, marginal cost
( #architectelevator mini thread )
If you’re wondering why communication & people skills are becoming very important to get to senior engineer and above levels at Big Tech: it’s because of this.
Coding is the trivial part at many of these places. Working with so many other engineering teams is the real challenge.
I was able to access thousands of companies’ passwords on #Azure and run code on their VMs.
This includes access to Microsoft’s own credentials… 💣
Here’s HOW I did it.
This is the story of #SynLapse. (1/11)
Evolution of the Netflix API architecture.
The Netflix API architecture went through 4 main stages.
𝐌𝐨𝐧𝐨𝐥𝐢𝐭𝐡. The application is packaged and deployed as a monolith, such as a single Java WAR file, Rails app, etc. Most startups begin with a monolith architecture.
The primary function of code review is not quality assurance, but rather knowledge transfer
So you do want at least one approval, not to verify that the code works, but rather to ensure that at least one other person understands how to maintain the code
I can't speak for Ron, but to me, fixing tech debt is just part of programming. When I see something wrong, I fix it. If you're hoarding it up so that you can fix it some day, that day will never come & the debt will swallow you up. If you can measure it, you're hoarding.
@gavinclark66@allenholub@meetvashek Isn’t it responsibility of another service? Building a materialized view of this aggregate persisted in another database if durability is a concern
I've been teaching a college-level Software Architecture class this semester, and the long-form has made one thing about Microservices abundantly clear—they are not really an architecture at all. 1/3
@schneider_chris@housecor But also depending on the change, having more people reviewing it would be preferable and result in higher quality code. Therefore Code Review would be more suitable.
@schneider_chris@housecor I would say because the conversation happens before the code is written, resulting in higher chance to integrate both developer's perspectives in the final design.