Mykhailo Faraponov

I can’t stress this enough: To become a Senior engineer you don’t need to complicate things. What you need is to focus your efforts on being pragmatic, business-oriented, and solution-oriented. I’ve seen too many talented mid-level devs shooting themselves in the foot by: 👉🏻Adding unnecessary abstraction layers “for future flexibility” 🤦‍♂️ 👉🏻Implementing design patterns that solve problems that don’t exist 👉🏻Building “elegant” solutions that take 3x longer to ship. Meanwhile, senior devs are out there asking the right questions: 👉🏻”Whats the simplest solution that works?” 👉🏻”What are we actually optimizing for?” 👉🏻”Will this help the business or just my ego?” Your promotion isn’t blocked by lack of complexity, actually it’s blocked by too much of it. Save your creative energy for problems that actually need complex solutions.

679

46 Comments

🤵 Tech Lead: "We will start using DDD in our project!" 🤔 Me: "Cool! Is it Domain-Driven Design?" 🤵 Tech Lead: "Yes!" 😃 Me: "Nice! What will we do then?" 🤵 Tech Lead: "First, we will extract interfaces from all our DAOs and call them ‘Repositories’. Then, we will create big objects using ‘Factories’ instead of services..." That was a real conversation between my tech lead and me back in 2009. We tried to introduce DDD into a project. It didn’t go well. The codebase became even more complicated. And we concluded that DDD was a waste of time and didn’t work. Years later, I see many developers falling into the same trap - thinking DDD is just about repositories, factories, and aggregates. ❌ DDD is NOT about your code. Just because you have tactical patterns doesn’t mean you’re doing DDD. ✅ DDD is about understanding and structuring complexity: 🔹 Finding the right language to communicate with business. 🔹 Breaking down a complex domain into meaningful parts. 🔹 Understanding relationships between those parts. 🔹 Prioritizing: What’s core? What’s supporting? What can we buy? 🔹 Clarifying who owns and implements each part. 🔹 And only THEN, applying tactical patterns in code. Did anyone else start with “coding” DDD before understanding the strategic part? 😃

437

66 Comments

When adding caching to your application, your strategy determines how reads and writes happen. Of course, different approaches have various trade-offs. Pekka Enberg, Founder and CTO of Turso, looks at six latency vs. complexity strategies and the pros/cons of each via The New Stack > https://lnkd.in/ePPgR9Q6 #ScyllaDB

22

EKS (Kubernetes) or ECS 🤔 Here's the problem: Many engineers are slightly confused to make a choice. It's not their fault. It's not an easy choice 💯 Especially when the requirements are not very clear. Which is usually the case with the customer anyways 😁 But generally speaking. If you see high scaling, portability demands and complex compliance requirements, then EKS is a good choice 😃 For teams new to K8s, its a tough choice. ECS on the other hand can also handle scale. Its easy to manage. Aligns very well with smaller teams, teams with less devops experience. But portability and fulfilling compliance requirements can be challenging. You are free to make your choice, but you are not free from the consequences of your choice. So ask right questions, it will help you make the right choice 🤠 Thats it for today. Hope this is useful. A repost helps ♻️ P.S. What are you using right now? And are you happy with your choice?

65

12 Comments

"I was juggling multiple test frameworks, environment conflicts, and the dreaded 'it works on my machine' fiasco." 😱 In today's development world, Vladimir Mikhalev explains that containerization and reliable end-to-end testing have become "practically mandatory if you want to keep up with lightning-fast release cycles." Vladimir shares how he perfected his E2E testing setup for consistency, scalability, and security: ✅ Upgrade to Node 22.x (or newer) ✅ Optimize your Dockerfile ✅ Parallelize using Docker Compose scaling or the Cypress Dashboard ✅ Harden your containers ✅ Implement a Healthcheck Read our #CypressAmbassador's full piece: https://lnkd.in/eZVS5qmW

36

1 Comment