Thiago Colares

We just open-sourced a saga pattern example that doesn't need a saga framework. Book a flight, hotel, and car rental. If the car fails, compensate in reverse — cancel hotel, cancel flight. Each cancellation is checkpointed. Crash mid-compensation? It resumes where it left off. The entire saga is a generator function with try/catch. No compensation tables. No framework. No orchestration DSL. `bun start:fail` and watch it roll back. https://lnkd.in/gJScr_px #DistributedSystems #OpenSource #TypeScript #DurableExecution

2

✨Learn how to make meaningful contributions (not just code!) that maintainers will love. Build your confidence and learn to align with maintainer goals. Catch the talk by Sarah Rainsberger at React Advanced Canada: https://lnkd.in/ek6bbiYB

1

🧠 Frontend Developers: How to Make Every Job Application Count – The ultimate Reactive‑Design checklist Your UI loads fast – but does it respond right? 🎯 Reactive design reveals architecture skills fast. Many developers still treat responsiveness as layout only. But hiring managers want reactivity, not just resolution. 🛑 Most applicants over-index on media queries. 🛑 That screams cookie-cutter portfolio. 🛠️ Here’s how to showcase real reactive design wins: 🔹 Build with real-time interaction in mind Show how the UI updates on state or input. Use signals, props, stores, or observers. 🔹 Explain component reactivity Break down how the DOM updates on change. Mention your use of virtual DOM or direct reactivity. 🔹 Go beyond screen breakpoints Show layout shifts based on data/state – not just size. That’s what senior devs actually get hired for. 🔹 Add motion-based feedback Micro-interactions count. Hover, click, loading. Use Framer Motion or lightweight CSS transitions. 🔹 Logically separate layout vs reactivity Mention your folder/component structure. Explain where you abstract logic from UI. 🔹 Mention your framework’s reactive model React: Hooks/state. Vue: Refs/computed. Svelte: Stores. SolidJS: Signals. ⚡ Modern UIs aren’t just responsive – they react to change. ⚡ That’s what makes users trust the interface. ⚡ And what makes recruiters trust your code. 🔥 STOP applying blindly! Follow us for real job-winning strategies. 🔥 Follow JobLanderz.VIP for daily job hacks & insider tips! 🔥 Tag a friend who's job searching! Help them land their dream job faster. 🔥 Explore more tools at: https://lnkd.in/d9sDiF6E #frontendinterview #reactivedesign #webinteractivity #jobsearchtips #frontenddev 💬 Comment 'REACTIFY' if you want a free reactive-UI checklist!

A founder shared a story about a backend engineer who left for a CTO role at a Canadian company with a reported $20k monthly salary and 20% equity. Many people congratulated the developer at first. But others started questioning whether the numbers actually made sense. The conversation quickly turned into a debate about startup compensation and remote tech salaries. What do you think? #StartupLessons #TechDiscussion #Developers #StartupCommunity #BuildInPublic

9

As our platform scales, we’ve made a habit of asking: is our architecture making change easier or harder? In this piece, two of our Lead Engineers, Humberto Politi de Oliveira and Lucas Borges Moreira de Souza, explain why we adopted Entity Boundary Interactor and how we applied it incrementally. They share what changed in practice, including clearer use cases, better testability and a stronger separation of business rules from infrastructure. Their article is a practical look at architecture as everyday guardrails. Read more on Medium: https://bit.ly/4anA8bW

15

1 Comment

🔐 Single Sign-On (SSO) looks simple to users — but it’s one of the most important trust flows in modern systems. From the user’s perspective, SSO feels like: 👉 log in once 👉 access multiple apps 👉 move faster with less friction But behind that convenience is a carefully orchestrated exchange between: the user the service provider the identity provider This visual explains that flow well: The user requests access The app checks for an active session If none exists, it redirects to the identity provider The user authenticates Credentials are verified A token is issued Access is granted — and reused across connected services Why SSO matters ✅ Better user experience One login can unlock multiple services. ✅ Centralized identity management Authentication is handled in one place, not scattered across apps. ✅ Stronger security controls It becomes much easier to enforce: MFA conditional access centralized session management identity-based monitoring But here’s the tradeoff SSO improves usability and control, but it also makes the identity layer more critical than ever. If the identity provider is weak, everything connected to it inherits that weakness. That’s why SSO should never be treated as just a convenience feature. It’s a security architecture decision. My takeaway SSO is really about balancing two things: less friction for users and stronger trust enforcement for systems When implemented well, it does both. 💬 What do you think is the bigger SSO challenge in practice: integration complexity, token/session security, or identity-provider trust? #SSO #IdentitySecurity #IAM #Authentication #CyberSecurity #ZeroTrust #AccessManagement #SystemDesign #CloudSecurity

70