Gabriel Adomnicai

💡 AI doesn’t just change how code is written – it changes expectations and outcomes. In the final section of Jellyfish’s AI Adoption Guide, we explore how expectations for engineering leaders are evolving as AI becomes embedded across the SDLC. Because the organizations pulling ahead are treating AI as a transformation, not a tooling upgrade. Inside, you’ll explore: - Why AI adoption is quickly becoming a leadership mandate, not an option - How to balance ambitious goals with realistic expectations - What cultural investments are required to sustain long-term gains - How data can be used to align executives and engineering teams The teams that win in the AI era won’t just have better tools – they’ll have leaders who know how to guide change. Download today: https://lnkd.in/dut_6WpQ

20

Exciting Update for Adobe Commerce Merchants! Starting January 2026, Adobe Commerce will adopt a monthly patch release schedule to enhance security for all supported release lines. Here’s what you can expect: ✅ Monthly isolated security fixes for all supported versions ✅ Annual security patches every May (with possible additional patches in November) ✅ Full patch for Adobe Commerce 2.4.x LTS annually in May ✅ Beta patches twice per year (March & November) This change ensures a predictable, proactive, and simple approach to keeping your commerce platform secure and up to date. For more details, check out the official documentation: https://lnkd.in/gGHB_Zbm

5

At Paddle, we're setting a new standard for developer-first infrastructure. Our API-first transformation with Paddle Billing has delivered significant wins, and our partnership with Postman is a testament to our engineering excellence. Here's a look at the outcomes: - 50% faster onboarding: We've reduced the time to first call by half. - 4x growth in engagement: Our API discoverability has quadrupled. - Shortened sales cycles: An improved developer experience is accelerating sales. Our API-first approach has also greatly improved internal collaboration, with shared workspaces and clear documentation providing instant context for our teams. Read the full Postman case study here: https://lnkd.in/g3K4bvHu

37

Commerce & Revenue Optimization ​ Today, recommendations are the default in commerce—guests expect relevant options, not generic offers. Onboard is no different. ​ ​ Ascendion helps cruise lines use AI-driven personalization to make it easy for guests to discover, explore, and buy—whether it’s dining, retail, or excursions. With predictive offers and tailored recommendations, every interaction has the potential to increase spend and satisfaction. ​ ​ When commerce feels natural and helpful, it becomes part of the experience, rather than a distraction. ​ ​ Learn more: https://lnkd.in/guDUnmNc ​ ​ #CruiseLine #Ascendion #FutureOfWork #EngineeringAI #DigitalCommerce ​

23

1 Comment

Several folks in my group are celebrating their anniversaries this week — many with 7+ years at Airbnb — and multiple are entering or able to enter the Decade Club (10 years!). That’s an incredible milestone. It got me thinking: how do people stay at one place for so long and still feel like they’re growing? Especially in Silicon Valley, where it’s common for people to switch jobs every 3–4 years (or even sooner). I’m personally also staying at Airbnb for many years. Staying doesn’t have to mean standing still. In fact, some of the most meaningful growth comes from evolving inside a familiar environment. I’ve been reflecting on this lately a lot and summarized four ideas that I hope will inspire you: ☀️ Iteration, not repetition Repetition keeps you steady, but iteration keeps you moving forward. Growth comes from improving what you already know — whether that’s experimenting with a new approach, improving existing system, or setting stretch goals with your manager that push you just beyond your comfort zone. Iteration is what turns experience into momentum. ("Iteration, not repetition" is from Naval Ravikant, https://amzn.to/3JtJQhU) ☀️ Build systems, not emotions Motivation alone can feel like a rollercoaster. Some days you’re inspired, other days you’re not. Instead, create systems that compound over time: operating procedures, checklists, or workflows that make progress repeatable. When challenges come up (and they always do), use them as signals to strengthen your system instead of letting them drain you. The system evolves - and you grow with it. ☀️ Embrace AI One of the best ways to keep growing is to stay curious about how new tools can reshape your industry. For example, AI is opening up opportunities to solve problems in entirely new ways — from tackling hard security challenges to rethinking old workflows. Learning how AI (and other emerging technologies) can apply to your work keeps you not only relevant, but ahead of the curve. ☀️ Practice gratitude — and make your work visible Taking the time to express gratitude to teamates, peers, managers, builds stronger connections and creates a culture where everyone can thrive. At the same time, don’t let your own work go unseen. Share your impact, collaborate openly, and invite feedback. Recognition isn’t about ego — it’s about making sure your contributions set you up for the next cycle of growth. This week, seeing colleagues approach the 10-year milestone reminded me: growth doesn’t always come from changing companies. Sometimes, it comes from changing how you show up. 👉 If you liked this post, please follow me, hit “like,” and leave a comment — I’d love to hear how you stay in growth mode while staying at the same company. More importantly, stay connected as Airbnb is hiring!!! #GrowthMindset #CareerDevelopment #Leadership #ProfessionalGrowth #IterationNotRepetition #SystemsThinking #AI #WorkplaceCulture #GratitudeAtWork #DecadeClub #SiliconValley #Airbnb

25

2 Comments

I’ve been writing a series of posts on the design principles behind Looping, a product I’m building to help teams run and evolve software over time. These principles shape the architecture underneath and have helped me prioritize clarity, composability, and long-term maintainability from the start. The latest post in the series is about Composable Services. In Looping, every service follows the same interface: it takes a hash of input and returns either Success() or Failure(). That consistency makes services easy to test, reuse, and chain together without resorting to sprawling conditionals or unpredictable side effects. The post walks through the structure, shows real examples, and touches on how it tracks source chains for observability and event logging. https://lnkd.in/ePkn-pF6 #ruby #rails #softwarearchitecture #buildinpublic

7

2 Comments

In a new blog post, Marc Bowes looks at how updates work in Aurora DSQL, and what it means for scalable schema design. Read it here: https://lnkd.in/gmGEK8Dv A couple take-aways for application builders: - You mostly don't have to worry about hot read keys in DSQL, even in read-write transactions. DSQL can scale out per-key read throughput, and the design requires no co-ordination between transactions reading the same key. (Thank you, MVCC and Time Sync!) - Scalable applications do need to avoid high-contention write keys when doing updates. Writes need to be coordinated and ordered (to implement the I in ACID), which limits per-key throughput. - Most applications can avoid hot write keys with the right schema design. Most applications have already been written this way, because high-contention keys perform poorly on relational databases of all kinds.

240

11 Comments