Mykhailo Faraponov

10 lines of code. 400MB of node_modules. 4,000 dependencies. Wednesday truth: Modern JavaScript is importing the entire internet to center a div. That's not a project. That's a dependency hostage situation. 💀

1,539

104 Comments

You don’t need DDD on day one. I see devs overbuilding their domain models way too early. Trying to impress someone, maybe? When I built a fitness tracking app, we started with simple transaction scripts. Just one procedure per user action. It was fast, easy to reason about, and worked great. As the app grew and logic got more complex, we gradually moved to a richer domain model. That’s the key: Transaction scripts aren’t a stepping stone. They’re often the right choice for simple use cases. Start simple. When complexity shows up, then reach for DDD. What am I actually trying to say? Software engineering is about understanding the tools and patterns you're using. They all work - given the right context. It's your responsibility to understand that context. Now, this takes some experience and trial and error. --- Do you want to simplify your development process? I created a free Clean Architecture template to help you. Get it here: https://lnkd.in/eBbQcsCY

111

21 Comments

🚀 Let's Talk: Gradle Dependency Configurations in Android If you’ve ever written implementation, api, or compileOnly in your build.gradle, but weren’t exactly sure what’s happening behind the scenes — you’re not alone! 👀   Let’s break it down: 🔹 implementation Most commonly used. Adds the dependency to your module, but hides it from other modules that depend on your module. Helps keep build times fast and dependencies encapsulated. 🔹 api Used when you want to expose a dependency to other modules that depend on your module. Useful for creating shared libraries or SDKs. 🔹 compileOnly Adds the dependency at compile-time only. It's not bundled with the final APK. Great for annotations or compile-time libraries like Lombok. 🔹 runtimeOnly Used for dependencies needed only at runtime—not at compile time. 🔹 testImplementation / androidTestImplementation Used to add dependencies for unit tests or Android instrumented tests respectively. Keeps test dependencies separate from production code.   🔍 Why does it matter? Understanding and using these configurations correctly improves build performance, promotes clean architecture, and avoids bloated APKs.   💬 How do you organize your Gradle dependencies? Share your thoughts or best practices below!    #Android #JetpackCompose #KMP #CMP #Kotlin #kotlinMultiplatform #ComposeMultiplatform #ChainTech #MobileInnvoationNetwork

91

22 Comments

🚀 Java 25 LTS is here! (Released Sept 16, 2025) Think back for a moment… Do you remember the first time you wrote this? 👇 public static void main(String[] args) { System.out.println("Hello, World!"); } Most of us didn’t really understand what public, static, or String[] meant. We just trusted the magic. ✨ Now fast forward to Java 25 → that same magic feels simpler, cleaner, more approachable: void main() { System.out.println("Hello, World!"); } ✅ Streamlined syntax ✅ Beginner-friendly ✅ Still enterprise-grade at its core Java 25 shows us that a language can be: 👉 Elegant enough for beginners 👉 Robust enough for the enterprise It’s a reminder: great design is both powerful and approachable. 👀 Curious—when was the first time you wrote your “Hello, World!” in Java? (And do you still remember how confused you were by that method signature? 😅) #Java #Java25 #LTS #DeveloperExperience #Coding #HelloWorld #JavaCommunity

397

24 Comments

#ADRs (Architecture decision record) are like event sourcing. ADRs are written down decisions about architecture. Why did you chose React? Why not Angular? What were the Pro and Cons and why was that solution the winner? They make it easy for developers new to the company or new to the team to understand the decisions BEHIND the current tech stack and architecture. So they can make better decisions themselves. A side effect of ADRs is that you do not have the same discussion over and over again. How are they like Event Sourcing? ADRs have not the downside of normal documentation. Normal documentation is hard to keep in sync with reality. It's a tedious process, and nearly impossible if you did not find the right level of documentation (deep enough, but not too deep). ADRs do not change. They are write-one-read-often, they are read only. They don't need to be maintained, they are always correct. In this way they are like events in Event Sourcing. Those also do not change. And ADRs can be seen as an event, and to get an understanding of the current state of your architecture, you need to read and aggregate those ADRs, just like events in event sourcing. https://adr.github.io/

28

4 Comments

"So we have automation classes where people need to test, students need to write automation scripts and that's how they got introduced to what is a test case. And you would have to automate it." - Dmitrij Nikolajev In this episode, I talk with Dmitrij Nikolajev about teaching software testing to the next generation. Dmitrij, who balances roles at InSoft and Vilnius University, shares his approach to making software testing engaging for students. He focuses on practical, hands-on experience, using tools like Postman and Selenium to teach automation and performance testing. Dmitrij redesigned his course to appeal to both new learners and those already in the industry. He leverages real-world examples to highlight the importance of testing, encouraging students to understand the consequences of failures. We also discuss the role of AI tools like ChatGPT in the learning process and their impact on student progress. What do you mean? What do you think of the approach to first teach test automation instead of test theory? Write in the comments. #softwaretesting #career #quality ISTQB® - International Software Testing Qualifications Board

32

1 Comment

RabbitMQ is a message broker. Think of it like a reliable postal service for your software. Whether you're building microservices or want to offload work from your main app, RabbitMQ is one of the best tools to help you get there. Instead of one system directly calling another (which creates tight coupling), RabbitMQ acts as the middleman: • One part of your app sends a message. • Another part receives and processes it when it's ready. This is known as asynchronous communication, and it’s particularly beneficial for performance, reliability, and scalability. Key Components: • Producer: The one who sends the messages. • Consumer: The one who receives the messages. • Queue: Where the messages wait until they are processed. • Exchange: The "dispatcher" that directs the messages to the appropriate queues. • Binding: The rules that connect exchanges with queues. You can easily set it up using Docker. Read full implementation: https://lnkd.in/dTeRjEA8

416

23 Comments

Is NGINX + PHP-FPM becoming obsolete? 🚀 The "Worker Mode" revolution is here and the performance gains are impossible to ignore. I just dropped a deep-dive benchmark pitting the two heavyweights of the modern PHP ecosystem against each other: FrankenPHP vs. RoadRunner, running on Symfony 8 and PHP 8.4. We didn't just test "Hello World." We pushed them through real-world scenarios: ✅ Database Writes & Doctrine ORM ✅ Heavy Serialization (API Platform style) ✅ CPU-bound Matrix Multiplication ✅ Memory Leak & Restart Stability The Results? Both runtimes decimated the traditional FPM setup, offering 3x-4x throughput gains in database scenarios. 🔹 RoadRunner proved to be a beast in raw stability and ecosystem maturity (Queues, gRPC). 🔹 FrankenPHP shone with its incredible simplicity (single binary!) and winning Time-To-First-Byte on heavy serialization tasks. If you are building high-performance Symfony applications in 2026, you need to understand these architectures. 👇 Read the full benchmark analysis and GitHub repo: [https://lnkd.in/daCmrwDj] [https://lnkd.in/dbunCVbS] Which runtime are you betting on? Let's discuss in the comments! 💬 #Symfony #PHP #FrankenPHP #RoadRunner #WebDevelopment #Backend #Performance #TechLeads

76

9 Comments

Party Objects are here on Sui mainnet! Think of them as a new type of object that blends: 🔒 Control of owned objects 📑 Consensus versioning of shared objects That means objects you can move between fastpath & consensus, with built-in versioning - and soon, multi-owner + granular permissions. Learn more 👇 https://lnkd.in/eVZn8ZMJ

75

2 Comments

After months of testing (both professionally and as hobby) AI tools for Angular development, here are my findings: Most models struggle with Angular 18+ features without proper pre-prompting (I am looking at you Google). Claude 3.5/3.7 handles modern Angular best, but you need to guide it (Kudos Anthropic). Local models? Skip them unless you have 24GB+ RAM to spare. VSCode Copilot works great for large codebases (I think this is worth the $100), Cline is fun for smaller projects (I will be trying this on larger codebases soon, so stay tuned). Tools like Bolt.new (I had faith bolt.new...) keep trying to revert to Angular 16 - frustrating. More honest insights: https://lnkd.in/d7Ek2cSE Bonus: This is my basic to-go pre-promo (copilot-instructions.md / .clinerules / .cursorrules) # Angular Modern Development Guidelines & Single File Component Example This document outlines best practices for building modern Angular applications using: - **Signals & Computed Properties** for reactive state - New **output** instead of @Output - The **`inject()` function** for dependency injection - **Signal queries** (as available even if not stable) instead of decorators like `@ViewChild` - Angular's **new control flow syntax** - **OnPush change detection** for performance - **Strict TypeScript** (with no non-null assertions) - **Single File Components** (all template, style, and logic in one file) - **Tailwind CSS** for styling - **Tailwind Animations** when necessary - **Light and Darkmode** Always make colors compatible with light and dark mode > **Note:** Adjust any experimental API (e.g., signal queries) as the Angular framework evolves. ## 1. Prerequisites - **Angular Version:** 18+ (supporting signals, computed properties, and the new APIs) - **Project Structure:** Using an Nx monorepo (if applicable) - **TypeScript:** Strict mode enabled (avoid using `!` for possible null values) - **Tailwind CSS:** Properly integrated in your project build - **Animations:** Use tailwind animations module if animations are used ## 2. Comprehensive Single File Component Example IOU - will add it to a section on the guide. ## 3. Additional Guidelines - **Single File Components:** Encapsulate component's template, styles, and logic within one file - **OnPush Change Detection:** Use for performance and future-proofing - **Strict TypeScript:** Avoid non-null assertions and leverage strict mode - **Tailwind CSS:** Use utility classes directly in templates - **Animations:** Use Tailwind. Keep subtle and performant - **New Control Flow Syntax:** Use Angular's improved flow control instead of structural directives - **Dependency Injection:** Prefer the `inject()` function in standalone components - **Indentation** Use tabs and set them as 3 spaces #Angular #WebDev #AI

29

2 Comments