@SofiaHCBBG Thank you for all the great work that you and your team did in the past years. I follow your weekly threads and learned a lot about what happened in China. They were extremely useful and cover a lot of different topics. Best of luck for your next adventure.
I just took this awesome hands-on course on #kubernetes#cka by @mmumshad @kodekloud1 @udemy https://t.co/cEa6VB2Z7T It's pretty cool to be honest, I learned many new concepts that I didn't have chance to use in my work. Kudos Mumshad
4 ways enterprise architects are using gRPC in the real world https://t.co/nVRHpyQ2x7 by @reselbob , this article covers four aspects of use-cases, including massive-message exchange, polyglot, streaming, and web. Thank you, Bob 😍
🖼️ C4 model diagram types
The https://t.co/xEytYlDQ6o provides four standard diagram types to visualize its abstractions. Each is tailored to a specific audience with varying levels of technical details.
🧵 1/5
Did you ever think about how to describe the software architecture of the system that you are working on? Recently, I discovered the C4 model for visualizing the system at 4 different levels: context, containers, components, and code. It really helps! https://t.co/oEmCRWn7MM
The book @TeamTopologies is one of my favorite, must read books. One of the key ideas is that software development teams should be small, e.g. 5-9 people.
https://t.co/EdjMBvTJmx
Communication is critical for software development because we are building software for people. Talking with others helps you understand their needs, their concerns, align on objectives and priorities. Ultimately, it helps collaboration and making better product.
While the Black Friday deals run through the end of this week, check out the following three brilliant technical books.
If you've read any and liked it, share the book with your network. Let's help people make the right investment at the right time!
🧵(1/4)
The key concepts provided by the OpenAPI Initiative, e.g. OpenAPI spec, code generator, schema, build, api-diff, and how they may be useful for your project.
https://t.co/J9MdzDvTC5
Writing software requires good understanding of your requirement. Think about dimensions: user, timeline, dependency, upstream/downstream, lifecycle, read/write, boundary, concurrency, ... more dimensions you can think of, the further you can go.
How to write technical doc as a software engineer?Define the types of documentation, your audience, improve page content, write less, organize the relationship between pages, and more. https://t.co/DBB3RQlSSR
These days I think I write more docs than code 😂 Become a Confluence Whiz Kid: Organized Spaces and Beautiful Pages - Atl... https://t.co/zFhY1F873K via @YouTube
@cowtowncoder I see, the progress is visible, incremental and impactful. And you can iterate on it. That's very nice. I asked because I sometime cannot find motivation on side project. Thanks for your reply. And also for the great work for Jackson. It is really useful for the community.