Sometime the only thing you need to start reading is another set of articles:
- Software Architecture
- 5 Benefits of an API-driven Approach in Microservices Architecture
API-driven development is essential in microservices architecture, especially for efficiency and consistency. It simplifies the complexities of service integrations and reduces code redundancy. - The False Dichotomy of Monolith vs. Microservices #PickOfTheWeek
There is no such thing as monolith vs. microservices. There is actually a spectrum of possibilities between them. If you have pegged yourself at either extreme of the spectrum, you are missing out on the wide variety of architectures in the middle. - API versioning
In this post, you will learn about the three options for versioning HTTP APIs: path-based, query-based, and header-based. - Anti-patterns in event modelling - Clickbait event #PickOfTheWeek
What to do with the events that are notifying us that something has happened but are not giving any context?
- 5 Benefits of an API-driven Approach in Microservices Architecture
- Software Development
- Headless Component: a pattern for composing React UIs
As React UI controls become more sophisticated, complex logic can get intertwined with the visual representation. A Headless Component extracts all non-visual logic and state management, separating the brain of a component from its looks. - Functional event sourcing example in Kotlin #PickOfTheWeek
In this article the author discusses a functional modeling approach to event sourcing and presents an implementation example in Kotlin. - Habits of great software engineers
The difference between a developer and a great developer is the breadth and depth of their approach in delivering value. What are the habits of highly effective developers?
- Headless Component: a pattern for composing React UIs
- Clean Code
- TDD Prerequisites
Under what conditions can TDD work? - Write Clean Code to Reduce Cognitive Load
Learn what the cognitive load is and how to reduce it by writing clean code.
- TDD Prerequisites
- Agile
- Backlog Refinement: What is small enough? #PickOfTheWeek
How small does a backlog item (“story”) need to be “ready” for the sprint? As with nearly all coaching questions, the correct answer is, it depends! - Five Steps to Estimate Your Backlog
Story points are a popular method for estimating but you can always try something different. Use this 5-step approach instead to estimate your backlog.
- Backlog Refinement: What is small enough? #PickOfTheWeek
- Project Management
- Project Managers, Focus on Outcomes — Not Deliverables
Shift the focus from “what” you’re building (the deliverables) to “why” you’re building it (the outcomes). In this article, you will learn how you can keep your team’s efforts aligned with the genuine needs of your audience. - Look Again at the Decisions
As the manager, it’s not your job to motivate, you are supposed to create an environment. So, what does that mean?
- Project Managers, Focus on Outcomes — Not Deliverables
- Leadership
- Setting expectations #PickOfTheWeek
We need to be clear on what’s expected and when – and you’ll be more influential…today.
- Setting expectations #PickOfTheWeek
Would like to get link dump on your email? Just subscribe.
No comments:
Post a Comment