Notch’s Post

A few days ago, I hit a wall in my code. Not just any wall—the kind that makes you rethink everything. I was building a dynamic form feature for a web application. Simple on paper, but integrating real-time validation and ensuring seamless backend communication turned into a maze. My usual approaches weren’t cutting it. Debugging became a spiral of trial and error, and the frustration was real. I almost gave up. But something clicked when I started breaking the problem into smaller chunks. One function. One test case. One fix at a time. Slowly, the chaos untangled, and the feature worked better than I’d planned. This experience reminded me that complexity is only overwhelming until we simplify it. What’s a technical challenge that taught you something about persistence? #TechChallenges #JavaFullStack #LearningInCode

This had to be done quickly... Link to work Landing section webpage : https://lnkd.in/d2K--yMH (Only desktop responsive upto 4K screen) Learnings ✅ During LeetCode : Challenging easy problem, learned to solve topics that cover multiple data structure. (Will share the Snapshot sometime later) ✅ Frontend Practice : Had to quickly spin up a web responsive site, past experience helped a lot to accomplish this. Trust the process. Thanks for all your support, do give feedback I appreciate that. Day 34 of #Super99 done PS : Will be sharing small bytes of progress from hereon, going on an exciting adventure. #coding #consistency #challenge

Here it is! Version one of the blog is available! This is for the software engineers out there! Any feedback or questions welcomed! https://lnkd.in/etTKSvt4 Still editing and improving the content so you might find mistakes here and there! hashtag #DETL hashtag #SOFTWAREENGINEERING hashtag #REALTIMESOCKET

A common problem I notice among new developers is not using descriptive names for variables or components. For example, naming a dropdown component "MyDropdown" is inappropriate, unprofessional, and doesn't follow best practices. Always consider the use case when naming variables, components etc. If you create a drop-down menu for selecting users A better name is "UserDropDown" This immediately communicates the component's purpose. Using meaningful names for variables, functions, , components etc. It greatly improves code readability, making it easier for others (and you) to understand and maintain the code. 𝗧𝗵𝗼𝘂𝗴𝗵𝘁𝗳𝘂𝗹 𝗻𝗮𝗺𝗶𝗻𝗴 𝗶𝘀 𝗮 𝘀𝗺𝗮𝗹𝗹 𝗵𝗮𝗯𝗶𝘁 𝘁𝗵𝗮𝘁 𝗹𝗲𝗮𝗱𝘀 𝘁𝗼 𝗰𝗹𝗲𝗮𝗻𝗲𝗿, 𝗺𝗼𝗿𝗲 𝗽𝗿𝗼𝗳𝗲𝘀𝘀𝗶𝗼𝗻𝗮𝗹 𝗰𝗼𝗱𝗲 𝗶𝗻 𝘁𝗵𝗲 𝗹𝗼𝗻𝗴 𝗿𝘂𝗻.

I've recently started exploring the Spring Framework, and one topic that's really caught my attention is Dependency Injection (DI). It's like having a friend hand you exactly what you need while building a puzzle, making our applications work together seamlessly.Here's what makes DI in Spring so cool: Flexibility: Choose how to inject dependencies (constructors, setters, or fields) to fit your project's needs. Simplicity: With annotations like @Autowired, Spring automatically gives our components the things they need. It's like telling Spring, "Hey, please make sure this piece has what it needs," and Spring takes care of it. Power: DI not only connects app components but also enhances testability and maintenance, allowing for easy updates without overhauling your project. I'm still at the beginning of my journey with Spring and DI, but I'm already seeing how powerful it can be in creating organized and flexible software. I'm really excited to learn more and I’d love to hear from you! How has DI improved your projects? #SpringFramework #DependencyInjection #SoftwareDevelopment

We've just published our @prezly/react-promise-modal library v2.0 🎉 This is the most convenient way of spawning modals in React. Period. Read the cover blog post: https://lnkd.in/dumJ5smp Check the code: https://lnkd.in/dBdUhmQE Cheers! 🖖 #react #modals #prezly #opensource #blog

What is a Lazy Variable? A lazy variable is a property whose initial value is not calculated until the first time it is used. This is particularly useful for properties that require complex or resource-intensive setup. Benefits of Using Lazy Variables 1. Performance Optimization: Initialization is deferred until the variable is actually needed, which can save resources. 2. Memory Management: Resources are used only if necessary, potentially reducing the app’s memory footprint. 3, Simplified Code: You can group complex initialization logic within the lazy block, keeping your initialization code cleaner. Use Cases for Lazy Variables 1. Expensive Computations: When initializing a variable involves time-consuming computations or network requests. 2. Conditional Initialization: When a variable might not be used in every instance of a class. 3. Circular References: When two properties of different classes reference each other, lazy initialization can help avoid circular dependencies. Important Considerations 1. Thread Safety: Lazy properties are not thread-safe by default. If multiple threads might access a lazy property, ensure you handle synchronization. 2. Value Types: Lazy properties cannot be used with value types that require an initializer (e.g., structs without a default value). Conclusion Lazy variables are a powerful feature in Swift that can help optimize performance and memory usage. By delaying the initialization of a variable until it is needed, you can make your code more efficient and potentially simplify initialization logic. #iosdeveloper #100daysofcode #codingdays #backenddeveloper #appdeveloper

Learn how to map over async/await operations in three different approaches. Have you recently run into the issue where you expected the result of your map function to return a resolved/awaited value, but it returned a list of promises. This article could be useful if work some processes that require multiple asynchronous requests at the same time or with one action https://lnkd.in/dxWsBV2Z

Testing Image uploaded from backend

The importance of having tests in place is undeniable. However, the importance of having a fast feedback loop from your tests is usually neglected. A fast feedback loop from tests helps developers quickly identify and fix issues. It improves the overall throughput of a developer. I wrote an article where I shared 4 tools to supercharge your Jest Testing and increase your productivity while testing. You can read for FREE here: https://bit.ly/3B4bPjZ ------ 👋 Join 17,344+ software engineers learning React, Node, and Software Architecture: https://bit.ly/3SOu2ZK ------ P.S. Repost this ♻️ Someone out there might need it!