Sebastiano Lanza

The true measure of a software developer is being able to deliver value in the simplest possible way. It isn't knowing the latest languages, frameworks, or techniques; it's knowing when not to use them. It isn't delivering lots of sparkly new features; it's delivering the one feature that gives its users leverage they need. It isn't sitting behind a screen 16 hours a day; it's knowing who to talk to and building relationships. It isn't being right; it's being an inspiration.

221

10 Comments

Developers think Software Architects have the easiest highly paid job. Well... not quite 👇 Here's what devs imagine an Architect does: - Doesn't write code - Draws diagrams all day - Just makes decisions in meetings - Gets to choose the "cool" tech stack - Always says "yes" or "no" with confidence - Doesn't have to deal with bugs - Works only 4 hours a day - Has a high salary But here's what actually happens: - Writes the core code everyone else will build on - Spends hours reviewing pull requests for critical changes - Explains the same architecture to 5 different teams - Balances business needs with technical debt - Makes trade-offs nobody will be happy about - Deals with production issues at 2 AM - Handles conflicting opinions from stakeholders - Documents decisions so future devs understand why - Manages tech stack upgrades without breaking things - Tracks performance, security, and scalability risks - Mentors developers while staying hands-on - Negotiates scope and timelines under pressure - Reads endless RFCs and framework updates - Constantly defends architecture choices with data - Stays accountable when things go wrong - Learning new things each week to keep up with changing technology Being a Software Architect is rewarding — but it's far from easy. It's not just about drawing boxes; it's about owning the outcomes. What's the biggest misconception you've heard about Software Architects? — ♻️ Repost to help others learn about Software Architect role ➕ Follow me ( Anton Martyniuk ) for more

3,490

266 Comments

𝘞𝘩𝘺 𝘠𝘖𝘜𝘙 Automation 𝘧𝘳𝘢𝘮𝘦𝘸𝘰𝘳𝘬 𝘸𝘪𝘭𝘭 𝘍𝘈𝘐𝘓 𝘪𝘯 6 𝘮𝘰𝘯𝘵𝘩𝘴 (𝘢𝘯𝘥 𝘩𝘰𝘸 𝘵𝘰 𝘧𝘪𝘹 𝘪𝘵) I just audited a $50M company's automation framework. Result? 73% of their tests were failing randomly. Their CTO asked me one question: "How did we go from 10 passing tests to complete chaos?" The Brutal Truth: 85% of Selenium Projects Die the Same Death Month 1: "Our automation is amazing!" Month 6: "Why does everything break when we deploy?" Here's what kills every framework (and the fix): 1️⃣ The "Everything in One Folder" Disaster ❌ Death pattern: UI, API, utils all mixed together ✅ Fix: Dedicated packages → UI, API, POJO, services separated Reality check: Good teams onboard new devs in 2 hours, not 2 weeks. 2️⃣ The "Hardcoded Hell" Problem ❌ Death pattern: URLs, data, timeouts scattered everywhere ✅ Fix: Environment property files + externalized test data Game changer: Switch DEV→QA→PROD with one command. 3️⃣ The "No POJO = No Scale" Trap ❌ Death pattern: Raw JSON strings, manual API payloads ✅ Fix: Request/Response POJOs + schema validation Impact: API tests become 10x more maintainable. 4️⃣ The "Debug Nightmare" Issue ❌ Death pattern: "Test failed" with zero context ✅ Fix: Extent Reports + screenshots + API logs Truth: Debug time drops from 2 hours → 5 minutes The Framework That Actually Scales I've built a production-ready structure that includes: 🏗️ Proper separation of UI/API/POJO layers 🔧 External configurations for all environments 📊 Rich reporting with screenshots & metrics 🚀 CI/CD ready with Docker & Jenkins support 🎯 BDD structure that business teams understand The Bottom Line: Stop building "quick automation scripts." Start building software systems that scale. Your framework should work at test #10 AND test #1000. Want the complete folder structure? 👇 Comment "𝑭𝑹𝑨𝑴𝑬𝑾𝑶𝑹𝑲" and I'll send it to your inbox! Found this helpful? Share with someone struggling with flaky tests! 🚀 -x-x- Full Stack QA & Automation Framework Course with Clearing SDET Coding Rounds: https://lnkd.in/g7tn6Uif #japneetsachdeva

157

10 Comments

Tonight I will be joining a session with the Chrome DevTools team to talk about the network debugging experience in DevTools. Thanks Barry Pollard for connecting me 🙌 One of my own feedback points: 👉 It’s difficult to capture and share request + response details. When a network error happens, developers often need both the request info (URL, headers, params) and the response (body, status code) in one place. Right now, DevTools doesn’t have an easy one-click export or screenshot for this, which would be super useful for bug reports and troubleshooting. --- The team is also focusing on challenges developers face when debugging network issues end-to-end (from back-end to front-end), such as: - Working with / integrating between multiple disjointed systems - State management challenges that make it hard to reproduce bugs reliably - Difficulty understanding the payload of large requests, or dealing with 100s of network requests on a single page (noise, latency, etc.) - The complexity and limitations of end-to-end tracing across deeper back-end components or distributed systems - Difficulty reproducing real-world conditions (e.g. prod vs. dev, latency and bandwidth inconsistencies) - Not being able to inspect network activity due to security constraints 💬 If you’ve got your own pain points with the Network tab, please drop them in the comments and I’ll pass them along! Thanks for your input, everyone 💛

50

3 Comments

A common mistake I see: People treat message queues and streams as if they’re interchangeable. They’re not. Here’s the difference 👇 Message Queue (MQ) - Designed for delivery guarantees (at-least-once, exactly-once). - Great for sporadic workloads and asynchronous tasks. - Messages are consumed and removed. Once acknowledged, they’re gone. - Think: order processing, background jobs, retry logic. Stream - Designed for real-time, high-throughput, continuous data. - Data is append-only and replayable. - Multiple consumers can read the same stream independently. - Think: real-time analytics dashboards, fraud detection, monitoring pipelines. Why Streams fit Aaron’s case (real-time analytics for e-commerce): - Freshness matters → Streams process events as they arrive, with low latency. - Replayability matters → If a consumer goes down, it can re-read from the offset. - Scale matters → Streams partition data for massive parallel consumption. A message queue here would introduce unnecessary latency and discard historical events that analytics needs to stay accurate. Rule of thumb: - If you care about delivery → Message Queue. - If you care about freshness & scale → Stream. That’s why the right answer here is: Streams for real-time analytics.

964

69 Comments

Most junior engineers think they’ll be rewarded if they: → close lots of tickets → stay late and jump on every bug → write clever code and push big PRs But you’re rewarded for being the person who: → ships predictable outcomes, not surprises → prevents incidents before they happen with tests, alerts, and runbooks → makes the team faster with clear docs, small PRs, and crisp reviews → understands the user and ties work to a metric the business cares about → reduces cost and risk: cleaner designs, fewer moving parts, simpler ops Hard fact: believing “more hours + more tickets = growth” is a recipe for burnout and stalled careers. You’ll feel busy, but you won’t be valuable. Do this instead: → Pick one metric to move this quarter: p95 latency, crash rate, signup conversion, cloud spend. → Own one thing end to end: read code paths, write a tiny RFC, add dashboards, add alerts, add tests. → Kill recurring pain: automate a flaky deploy step, fix a flaky test, script a one-click local setup. → Review like a pro: spot risk, ask for data, suggest simpler designs, add examples to docs. → Learn the domain: sit with PM, Support, or Data weekly; collect real user stories. → Teach one person: pair once a week, share your notes, leave the project better than you found it. Yes, work hard. Give it your all. But keep asking, “What action creates the most impact for my team and our users today?” It may not feel like much each day. Some days it is just one small improvement. Stack those improvements for 90 days and you become the person people rely on. Stack them for a year and you become the person they plan around. You’re not paid for sweating more. You’re paid for being hard to replace.

811

40 Comments

Waiting half an hour for your tests to finish? That’s not feedback - that’s punishment 🧪 You might have been there: Every new integration test adds another minute to your overall build time. Twenty minutes turn to thirty. CI times explode. Developers stop writing integration tests and become unhappy. Flaky tests appear. Bugs slip through. Releases slow down. But what if you could slash that time, without deleting a single test? With Spring Test, that's possible. It's a hidden gem called Spring TestContext Context Caching 🏆 So, how do you know how many contexts are spinning up? More importantly, how do you figure out why they aren’t being reused? That’s why I built Spring Test Profiler ⏱️ Meet Spring Test Profiler - the free, open-source x-ray for your test suite. Integration is as simple as this three-step process: 1. Add the dependency (Maven/Gradle snippets appear on screen). 2. Run your tests. 3. Open the report at: target/spring-test-profiler/report.html. Within the report, you’ll see: • How many contexts started, and why. • Which tests are sharing configs versus starting their own. • Exact diffs: profiles, properties, or annotations blocking cache reuse. The overall goal is to help identify cache misses and align your tests to reuse contexts for faster feedback 🚤 Spring Test Profiler: Profile. Optimize. Deliver. Try it yourself: https://lnkd.in/djXVJiNE Below is a demo of a section in the report to analyze and compare two contexts 🆚

49

5 Comments

"Shift left” sounds good on paper. Faster feedback. Earlier testing. Cost savings. But here’s the uncomfortable truth: shifting left won’t save you if your culture stays stuck. You can throw tests into CI pipelines, automate early, and chant DevTestOps until the walls echo. But if your teams still treat testing as a phase, quality as someone else’s job, or feedback as a nuisance, all you’ve done is moved broken thinking upstream. I’ve seen companies install shiny new tooling with zero conversation about shared ownership. I’ve seen developers resist writing tests because “that’s not what we do.” I’ve seen testers struggle to add value early because they’re still expected to “verify the build” instead of shape the build. Shifting left without shifting culture is like moving the finish line but refusing to train differently. You don’t get better outcomes. You just get earlier dysfunction. If you’re serious about building quality in, here’s what needs to shift first: - The belief that quality is everyone’s job, not just the testers’. - The space for testers to be part of discovery, not just delivery. -The trust that cross-functional collaboration is not optional, it’s foundational. True shift left starts with mindset, not tooling. With conversations, not compliance. With people, not processes. If your culture still rewards speed over safety, delivery over discovery, and blame over learning, no amount of leftward motion will get you where you want to go. I help companies get this right not by selling buzzwords, but by rebuilding how teams think, act, and deliver together. If that’s the kind of change you’re ready for, I’d love to talk. #softwaretesting #softwareengineering #qualityleadership #teststrategy #brijeshsays

173

27 Comments

'We only hire senior developers' Congrats! You're building a time bomb. Here's why: Senior-only teams create: • Echo chambers of outdated practices • Zero knowledge transfer • Expensive solutions to simple problems • 10 architects, no builders What you're really missing: • Fresh perspectives • Hunger to learn • Questions that challenge assumptions • Future leaders The brutal truth: • Your 'senior' requirements are fear-based • Your '10 years experience' is arbitrary • Your 'no junior devs' policy is expensive technical debt Why this matters: • Innovation needs new eyes • Growth requires teaching • Sustainability demands succession • AI is leveling the experience gap anyway How to fix it: 1. Hire for potential, not just experience 2. Create mentorship structures 3. Balance your team pyramid 4. Accept that juniors today code better than seniors did 5 years ago Remember: Today's 'risky' junior is tomorrow's 'savior'. What's your take on the senior-only trend? Drop your thoughts below 👇 *** P.S. If your entire team is senior developers, who's asking the 'stupid' questions that prevent stupid mistakes?

93

23 Comments