Mohammed Lazhari

#software #refactor #technique #code 💡 What is Refactoring? 💡 When Should you Refactor? Refactoring is not : ⛔ Rewrite some classes or components that change the external behaviors. Refactoring is : ✅ a disciplined technique for restructuring an existing body of code, altering its internal structure without changing its external behavior. When : ✅ Duplication ✅ Nonorthogonal design ✅ Outdated knowledge ✅ Performance ✅ The tests pass 💡Before begin refactoring make sure you have solid and enough tests about business and what do you want in result. 💡After each small refactoring run tests as often as possible.

24

2 Comments

𝗔𝗣𝗜 𝗣𝗿𝗼𝘁𝗼𝗰𝗼𝗹𝘀 𝗳𝗼𝗿 𝗠𝗼𝗱𝗲𝗿𝗻 𝗔𝗽𝗽𝗹𝗶𝗰𝗮𝘁𝗶𝗼𝗻𝘀 REST 🌍: Popular architectural style for stateless, HTTP-based API communication. Webhooks 🔔: Real-time HTTP callbacks for event-driven notifications. GraphQL 🕸️: Flexible query language allowing clients to request only the data they need. SOAP 📜: XML-based protocol for structured data exchange. WebSockets 🔗: Enables full-duplex communication for real-time data transfer. EDA (Event-Driven Architecture) 🔄: Supports asynchronous data flows, ideal for modern microservices. EDI 📑: Standardized data exchange for automated B2B transactions. SSE (Server-Sent Events) 🔄: Efficient server-push notifications over HTTP. AMQP 📨: Protocol for reliable, message-oriented middleware communication. MQTT 📶: Lightweight protocol for IoT, optimized for low-bandwidth networks. gRPC 🚀: High-performance RPC framework using Protocol Buffers. Choosing the right API protocol enhances communication efficiency, scalability, and system resilience! Benny Xavier Neeraj Manoharan John Mathew Manuprasad B S Ajimsha M Sahad P Basil Arackal Ribson Roy Aswin CJ Aravind Jayan

23

#Git #Gitlab tips Problem: I have a file that I don't want to commit or lose, but when I try to checkout to another branch or pull changes, Git Bash tells me that I should commit them. Solution : 1- Stash your changes in the file: git stash push -- <file_path> 2- Switch to the other branch: git checkout <branch_name> or : git pull 3- Apply the changes from the stash: git stash apply This way, you can switch branches without committing the changes in the file, and then reapply them once you've switched to the desired branch.

11

🧩 Master class Middle to Senior in 2024 Rethinking GRASP, SOLID, and GoF patterns for Frontend & Backend Начало: 17 августа в 15:00 👉 Регистрация: https://lnkd.in/emiBFkSg #JavaScript #TypeScript #NodeJS #Backend #Frontend #Patterns #SOLID #GOF #GRASP #DDD #Refactoring #Architecture #Async #Programming

27

2 Comments

Coding schools: why does everyone bash on #PHP ? Also coding schools:  $user = mysql_query(“SELECT * FROM user WHERE id=“.$_GET[‘id’]);

1

🌟 𝗠𝗮𝘀𝘁𝗲𝗿 𝗝𝗪𝗧 (𝗝𝗦𝗢𝗡 𝗪𝗲𝗯 𝗧𝗼𝗸𝗲𝗻) 𝘄𝗶𝘁𝗵 𝗧𝗵𝗶𝘀 𝗖𝗼𝗺𝗽𝗿𝗲𝗵𝗲𝗻𝘀𝗶𝘃𝗲 𝗚𝘂𝗶𝗱𝗲! 🔐 Looking to understand how JWT works for secure authentication? Check out this in-depth guide by 👋 Volodymyr Code_Pro 🚀 It’s perfect for beginners and developers aiming to level up their security knowledge. 𝗪𝗵𝘆 𝗟𝗲𝗮𝗿𝗻 𝗝𝗪𝗧? 🔸 𝗦𝗲𝗰𝘂𝗿𝗲 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Widely used in web apps for verifying users. 🔸 𝗦𝘁𝗮𝘁𝗲𝗹𝗲𝘀𝘀: No need to store sessions on the server. 🔸 𝗩𝗲𝗿𝘀𝗮𝘁𝗶𝗹𝗲: Ideal for API authorization in modern apps. 💡 𝗞𝗲𝘆 𝗖𝗼𝗻𝗰𝗲𝗽𝘁𝘀 𝗖𝗼𝘃𝗲𝗿𝗲𝗱: 𝗪𝗵𝗮𝘁 𝗝𝗪𝗧 𝗶𝘀 𝗮𝗻𝗱 𝗵𝗼𝘄 𝗶𝘁 𝘄𝗼𝗿𝗸𝘀. 𝗦𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝗮𝗻𝗱 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 𝗼𝗳 𝗮 𝘁𝗼𝗸𝗲𝗻. 𝗕𝗲𝘀𝘁 𝗽𝗿𝗮𝗰𝘁𝗶𝗰𝗲𝘀 𝗳𝗼𝗿 𝗶𝗺𝗽𝗹𝗲𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻. 🔗 𝗥𝗲𝘀𝗼𝘂𝗿𝗰𝗲𝘀: • Start your web development journey with W3Schools.com. • Enhance your JavaScript skills with JavaScript Mastery. 🚀 Follow Rahul Jangid for more top-notch programming and web development content! #JWT #WebSecurity #ProgrammingTips #WebDevelopment #LearnToCode #Authentication

73

7 Comments

Best Practices for Improving Performance of ASP.NET Core Applications: Use caching: HTTP-based response caching Set by the Cache-Control header Distributed cache Use a distributed cache to store data that needs fast access. Caching with third-party libraries For example, Redis Cache In-memory caching In-memory caching uses the server's memory to store cached data. This type of caching is suitable for one or more servers.  Cache Tag Helper Use cache tag helper in MVC applications, for example: <cache expires-after="@TimeSpan.FromSeconds(120)"> Current Time Inside Cache Tag Helper: @DateTime.Now </cache> Always use asynchronous programming and avoid blocking requests: Recommendations: X  Do not use: Method calls that can block asynchronous calls by exiting Task.Wait orTask.Result. Avoid blocking at all stages of application development. ASP.NET Core is designed to run everything asynchronously. ✔  Use  Make 'hot code path' locations asynchronous. Make requests to the Data access layer and long API operations asynchronously. Make Controller methods asynchronous. The entire call stack is asynchronous, allowing you to take advantage of async/await patterns. Minimize large object allocations: Recommendations: X  Don't create  many large short-lived objects in the 'hot code path. ✔  Use  caching of large objects that are frequently used. Caching of large objects prevents expensive allocations. You can also use one of the classic  Flyweight patterns to work with such objects. ✔  Use ArrayPool<T>  for storing large arrays. Using a class ArrayPool<T> to "rent" and "return" buffers (using the Rent and Return methods) can improve performance in situations where arrays are frequently created and destroyed, resulting in significant memory pressure on the garbage collector. Optimizing Data Access Layer Efficient reading and writing of data is essential for good performance. Recommendations: ✔  Use  asynchronous requests to the Data access layer. ✔  Use  caching of frequently used data retrieved from a database or remote service (if business logic allows it). Depending on the scenario, use MemoryCache or DistributedCache. For more information, see Use Caching . ✔  Minimize  the number of requests to get data (the goal is to get data in one request, without making multiple requests) ✔  Use  LINQ query filtering and aggregation (for example, using .Where, .Select, or .Sum operators) to let the database do the filtering. X  Don't request  more data than necessary. Your requests should return only the data that is needed for the current HTTP request. X  Avoid  more than N + 1 problems

3

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

2

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

3

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

3

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

7

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

3

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

1

1️⃣2️⃣ Clean Code Series: Functions📒🧑💻 ☑️ Avoid type-checking (part 1) 🔹Consider using consistent APIs. 🐘 #PHP #Laravel #Symfony

3

[𝟏/𝟓] 𝐔𝐧𝐝𝐞𝐫𝐬𝐭𝐚𝐧𝐝𝐢𝐧𝐠 𝐒𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 If you ask 100 developers, “𝑾𝒉𝒂𝒕 𝒊𝒔 𝒔𝒐𝒇𝒕𝒘𝒂𝒓𝒆 𝒂𝒓𝒄𝒉𝒊𝒕𝒆𝒄𝒕𝒖𝒓𝒆?” you’ll likely get 100 different answers. Why? Because architecture means something different for every project, depending on factors like: - Project size and domain, - Technical and non-technical requirements, and - Various constraints. In essence, architecture can be: - The big picture - A system overview - A plan to implement solutions - An abstract view of a system - The vision and strategy for software projects …and much more. But even though “architecture” is hard to define, it helps to think of it in two ways: as a 𝒏𝒐𝒖𝒏 and as a 𝒗𝒆𝒓𝒃. - 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐚𝐬 𝐚 𝐧𝐨𝐮𝐧: It’s the structure of a system. This includes software elements, their externally visible properties, and the relationships between them. - 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞 𝐚𝐬 𝐚 𝐯𝐞𝐫𝐛: It’s about translating functional requirements, non-functional requirements, and constraints into a technical solution. Even though I’m a .NET developer, not an architect, I’ve spent a lot of time learning about architecture. You might wonder, “𝑾𝒉𝒚 𝒔𝒉𝒐𝒖𝒍𝒅 𝑰 𝒍𝒆𝒂𝒓𝒏 𝒂𝒃𝒐𝒖𝒕 𝒔𝒐𝒇𝒕𝒘𝒂𝒓𝒆 𝒂𝒓𝒄𝒉𝒊𝒕𝒆𝒄𝒕𝒖𝒓𝒆 𝒂𝒔 𝒂 𝒅𝒆𝒗𝒆𝒍𝒐𝒑𝒆𝒓?” Well, if you’re like me, you might find yourself needing to think about the bigger picture for two reasons: 1. As a senior developer (or the person making these decisions in your project) 2. If your team doesn’t have a dedicated architect. 𝐼𝑛 𝑡ℎ𝑖𝑠 𝑝𝑜𝑠𝑡 𝑠𝑒𝑟𝑖𝑒𝑠, 𝐼’𝑙𝑙 𝑔𝑢𝑖𝑑𝑒 𝑦𝑜𝑢 𝑡ℎ𝑟𝑜𝑢𝑔ℎ 𝑘𝑒𝑦 𝑠𝑜𝑓𝑡𝑤𝑎𝑟𝑒 𝑎𝑟𝑐ℎ𝑖𝑡𝑒𝑐𝑡𝑢𝑟𝑒 𝑐𝑜𝑛𝑐𝑒𝑝𝑡𝑠. Over the next four posts, we’ll cover: 1. Deciding which non-functional requirements (like scalability and performance) are essential based on business needs 2. Understanding the most popular architectural styles (clean architecture, vertical slice, microservices) and their differences 3. How to document tech decisions for your team simply, quickly, and effectively 4. A list of 16 of my favorite architecture resources for .NET developers (books, GitHub repos, fully developed apps, and more!) Each post includes visuals and practical examples to make these concepts clear and applicable. Stay tuned to dive deeper into software architecture! #SoftwareArchitecture #DotNetDeveloper #BackendDevelopment #SystemDesign #ArchitectureNounVsVerb #TechStrategy #Scalability #CleanArchitecture #Microservices #TechDocumentation #SoftwareEngineering #LearningJourney #CareerGrowth #DeveloperCommunity #DotNetCommunity

6