Nick Blokhin

Stop just "logging" and start observing. As your Symfony applications scale—handling payments, async workers and high-concurrency—the standard dev.log tail quickly becomes a liability. A Senior Developer knows how to log. A Lead Engineer knows how to design a logging infrastructure that saves hours of forensic work during an outage. I just published a new article - 10 Advanced Logging Patterns for Symfony 7.4 using Monolog 3 and modern PHP features. We cover: ✅ The "Black Box" Recorder - Using FingersCrossed to capture debug logs only when a crash occurs. ✅ GDPR Compliance - Automatically redacting sensitive data (PII) at the processor level. ✅ ChatOps - Bridging Monolog with Symfony Notifier for instant Slack alerts. ✅ Structured Observability - Native JSON formatting for ELK and Datadog. Logging isn't a byproduct of code - it’s a feature of your infrastructure. Read the full guide and GitHub repo: 👉 [https://lnkd.in/dT-MbGHT] 👉 [https://lnkd.in/dGWM6RHf] #Symfony #PHP #WebDevelopment #SoftwareArchitecture #Monolog #Observability

9

Our PHP Team Lead, Volodymyr Vovnenko, recently raised a question about long-running processes and orchestration in FinTech systems. Within one of our PHP + Symfony projects, our engineering team started evaluating Temporal.io as a way to orchestrate long-running workflows (KYC/AML, payout confirmations, PSP callbacks) with stronger guarantees, better traceability, and a clearer execution flow. Today, our architecture relies on a classic event-driven approach: — Outbox pattern — persisting events in DB and publishing them to a broker — Event choreography — services reacting to each other’s events — Retries & DLQ — handling failures and delayed recoveries While this approach works, it becomes increasingly difficult to maintain transparency, traceability, and guaranteed execution in workflows that may run for hours or even days. Temporal.io, in contrast, offers several potential benefits: — Orchestration instead of choreography — clearer control, versioning, and less event chaos — Built-in retries, timers, and deadlines for long-running processes — Execution history out of the box — always knowing where a workflow got stuck — Native SAGA pattern support with compensation logic We’re curious to hear from the community: 👉 Have you used Temporal.io for orchestration in PHP/Symfony or other ecosystems, and what challenges and results have you seen in production? #PHP #Symfony #Temporal #Saga #Orchestration #FinTech

11

At adaptTo() 2025, our Tooling track highlights how automation can streamline AEM operations. In this session, you'll see how the ACM Tool enables permissions and content updates as code—making repeatable tasks faster, safer, and more reliable.    Krystian Panek & Tomasz Sobczyk (VML) introduce ACM (AEM Content Manager), a powerful open-source tool designed to automate content migrations and permission management across all AEM environments. Built with modern technologies like React Spectrum and Sling jobs, ACM offers a stable, developer-friendly experience that replaces tools like Groovy Console and AECU with a unified, scriptable interface for managing large-scale tasks efficiently.    Join us at adaptTo() 👉

44

1 Comment

Third-party code can slow down your website. Jakub Andrzejewski explains how to optimize it in Nuxt 🙈 Adding scripts with useHead 🔧 Get more control with Nuxt Scripts 🎉 Combine Nuxt Scripts and Partytown https://lnkd.in/ekTEr5kP

4

Tracing React Native internals has always been possible - but never this flexible. At React Universe Conf 2025, Callstack’s Artur Morys-Magiera and Dominik Dolny introduced Ottrelite, a unified and extensible tracing framework for React Native. Built on Nitro Modules, Ottrelite re-enables the Systrace JS API and adds a plugin system for any native backend - Tracy, Android ATrace, iOS os_signpost, or custom implementations. ▶️ https://lnkd.in/ds4ZwWba

7

𝗪𝗵𝗮𝘁 𝗺𝗮𝗸𝗲𝘀 𝘁𝗵𝗶𝘀 𝘁𝗲𝗮𝗺 𝘀𝗽𝗲𝗰𝗶𝗮𝗹: 32 releases, zero major incidents in 2+ years since the team's inception. We engineer with intention—the right amount of rigor for each problem, no over-engineering, no shortcuts. 𝗥𝗲𝗰𝗲𝗻𝘁 𝘄𝗼𝗿𝗸: Our team was entrusted with six mission-critical initiatives that would directly impact how thousands of clients manage their workforce data. From integrating Airbase acquisitions to building sophisticated security group assignments driven by position data, each feature required deep technical expertise and cross-functional collaboration. What stands out most isn't just what we built, but how we built it – with attention to quality, security, and scalability. Features like Employee Position Data Inheritance and Multiple Positions fundamentally change how our platform handles complex organizational structures. 𝗡𝗼𝘁 𝗖𝗥𝗨𝗗 𝘄𝗼𝗿𝗸: Real distributed systems. Acquisition integrations. Architecture decisions with business impact. 𝗖𝘂𝗹𝘁𝘂𝗿𝗲: Blame-free (incidents → learning docs), evidence-based decisions, sustainable pace. Engineers promoted through real mentorship, zero regrettable attrition. 𝗡𝗲𝗲𝗱: Someone excited by complex distributed systems, real trade-offs, and owning your domain end-to-end. Questions welcome. 🚀

4

Ondro Mihályi 's talk at JCON Europe 2025 showing not only the paths for migrating old #javaee applications, but also the strategic options to protect your code and your developers' skills from vendor lock-in.

13

Thirty years ago, Java made a bold promise: "write once, run anywhere." But what does it really mean to be a Java developer today? 🤔 Maria Kucharczyk (CMO at SoftwareMill) sat down with four of our senior engineers: Sebastian Rabiej, Emil Bartnik, Darek Broda, and Jacek Kunicki, and asked them what lessons 💡 they’d pass on to the next generation of devs. 📍 Read what our engineers have learned from decades in the trenches, and how their insights can help you write better code: https://lnkd.in/dY5pVMES #Java #Coding #SoftwareDevelopment

9

One of the biggest mistakes in software development is starting with code too early. It feels efficient, but often leads to fragmented systems, constant rework, and growing complexity. At QuartSoft, we’ve learned that sustainable software starts before development: 🔹 With discovery. 🔹 With process mapping. 🔹 With clear system logic. Because if workflows are unclear, code will only scale the chaos. 🔍 Curious how your current processes would look after proper structuring?

9

How do you stay consistent without losing your spark? ✨ Lenka Pejchalová, one of our QA teammates, shares a glimpse into her daily flow. Spoiler: being “too organized” at work might be her secret superpower. 🧠 Swipe through her micro-story and if you’re curious to see what a full day in her (QA) life looks like, read the full article on our blog 👉 https://lnkd.in/eRZD-DnB

11

They’re not looking for “something new.” They’re looking for a safe harbor. This sentence perfectly captures what’s happening right now on the Kraków IT scene. I see it in almost every recruitment process we lead at itMatch. Just a few years ago, developers were eager to "hop" into new projects, lured by the latest tech stacks or "Fruit Thursdays." Today, the tide has turned. Voluntary attrition in Kraków has dropped to around 6%. What does this mean for you as an employer? Candidates are no longer looking for an adventure. They are looking for stability and peace of mind. If you want a top-tier Senior to leave their secure position for your offer, you have to prove that you are a safe harbor. And you don’t prove it with words- you prove it through your hiring process: 💡 Your process is your "stability" business card If your recruitment drags on for a month, spans five stages, and lacks concrete feedback, you’re sending a clear signal: “There’s chaos inside.” For a candidate seeking stability, that’s a massive red flag. A lean, 2-stage process shows that the company knows where it’s going and can make firm decisions. 💡 Transparency over empty promises In 2026, a “cool project” isn't enough to close a deal. Candidates want to know: Your growth strategy. The company’s financial health. The long-term product vision. If you can't answer these questions during the interview, the candidate will view your "port" as too risky and will choose to stay exactly where they are. 💡 Flexibility as the foundation of trust A rigid "back to the office" mandate is now perceived as a lack of trust. It’s hard to feel safe in a place that doesn't trust your competence or your way of working. Local talent still prioritizes hybrid or remote models- giving them that choice proves you actually care about their work-life balance. The Bottom Line? Your offer doesn't necessarily have to be the most expensive on the market. It has to be the most trustworthy. Don’t just benchmark salaries; benchmark the entire Candidate Experience. Does your process feel like an invitation to a safe harbor, or a leap into deep water without a life jacket? When was the last time you looked at your company through the eyes of a candidate who doesn’t need to change jobs?

6

Server issues shouldn’t steal developer time. When weekends turn into firefights and dev teams are stuck fixing infrastructure, it’s time to rethink who’s handling your hosting. Just like Jobiqo did over ten years ago. We caught up with them at DrupalCon Vienna 2025 to learn more. > Listen to some of their story here: https://lnkd.in/ejqh82XR

5

What are the things no one tells you about being a software developer? 🧠 Marko Brankovic, CEO of Puzzle Software, reflects on key insights from his experience - useful not just for those starting out, but for anyone growing in this field. At Puzzle Software, we understand that the road to becoming a developer isn’t always straightforward. That’s why we’re committed to supporting growth, curiosity, and a culture where developers can truly thrive.

12

The Compliance Judge: Meet Themis Are Appstore rejections slowing you down? Been there. It's horrible. Hi, I'm Wisdom, a fullstack dev and sometimes I build really silly things because i have the superpower of coding. I meannnnn... why not? But this is not one of those silly projects that i'll dump after 2 weeks. During the last four (hectic and sleepless 🫩) weeks of the #Codematic_io X #GoogleCloud hackathon—on top of that Cortex 3.0 drilling, which is a story for another day 😭—I built something focused entirely on speed and foundational reliability: Themis, the Hybrid Compliance Checker! Themis is my answer to the misery of rejections from @GooglePlay and @AppStore. It automates pre-submission validation aiming to reduce back and forth, and wait times by up to 85%. That manual auditing—checking complex, frequently updated policies line by line—is a roadblock that costs developers time-to-market. The power of Themis isn't just checking boxes; it's in the intelligence and the precision:  It uses a fast Deterministic Rules Engine for non-negotiable checks (like verifying SDK targets) and leverages Google Cloud AI/ML (Gemini/VertexAI) for the complex policy compliance checking. It pinpoints fixes to the exact line numbers and suggests code snippets. No more guessing games. I built this using foundational Google Cloud Technologies like CloudSQL for data reliability. Our job is to deliver reliable systems; Themis is my tool for delivering reliable deployment. If you are a builder who has lost two weeks of your life waiting for a re-review because of a single, missed manifest field, Themis is coming to save you! #Themis #DevTools #buildwithcodematic #buildwithgoogle #FullStackDeveloper #AI

19

5 Comments

Is thirty years a lot for a mainstream programming language? Check out our take on how Java has evolved over such time.

3

Frontend isn’t just building components - it’s having a Driver’s Gaze. When you drive, you don`t stare at the car in front of you. You read the whole road: lanes, signs, markings, the next intersection, and everyone around you - drivers, pedestrians, kids, cyclists, scooters, buses. You spot risks and opportunities early, before they force a hard brake. Great frontend work is the same. It’s seeing the full picture: user intent, UI states, performance, accessibility, network reality, edge cases, and what the product is trying to become next. If you only watch your lane (your component), surprises happen. If you keep the whole scene in view, you build calmer, safer, more reliable UIs. What`s the biggest "blind spot" you`ve learned to watch for in frontend?

12

7 Comments

I recently spoke with a few developers about building the first version of a product - and something they said really made me think. Very often, teams try to pack everything at once into "v1": every possible feature, multiple languages, all integrations - basically "let’s make it look solid" and be ready for every scenario. I get why this happens: you want to build "like the big players", cover all edge cases, and avoid revisiting architecture later. But in practice, the first version can turn into a mini-monster that: - takes forever to build (too many unknowns at once); - is expensive to maintain (every feature creates new dependencies); - is hard to test (too many combinations); - and most importantly - still doesn’t guarantee anyone actually needs it. That’s why I’m a fan of MVP. An MVP isn’t "doing it poorly". It’s a deliberate choice to build the smallest set of core functionality that already delivers value - and lets you validate the essentials: - is there real demand? - does it create value for users? - will people pay / return / adopt? And this is where the magic happens: once you have something working, reality becomes clearer. Some "must-have" features suddenly aren’t that critical. And users often ask for things the team didn’t even expect. From there, you iterate based on real usage, feedback, and data - not assumptions. It’s a much more honest way to spend time and budget. For me, MVP isn’t about "less". It’s about being smarter: prove value first, then scale. #MVP #ProductDevelopment #Startups

57

13 Comments

What if your developers could spend more time building great products—and less time on repetitive, boring tasks? Too often, engineering teams get stuck fixing bugs, converting designs into code, and cleaning up messy files, work that slows innovation and burns valuable hours. At Planto AI, we’re changing that. Think of it as having a tireless “super-engineer” working alongside your team, 24/7—automating the repetitive stuff and speeding up the entire development process. No extra tools to learn. No complicated setup. Just faster, smarter building. When your developers aren’t bogged down with repetitive work, they can focus on creating features that actually make your product shine. This is the future of software development and we’re here to make it real. #PlantoAI #Productivity #Innovation #BuildBetter #TechLeadership #FutureOfWork #B2B #agenticai #copilot #tech #leadership #entrepreneur #ai #AI

116

13 Comments