Ahmed Ali

𝗖# 𝗦𝗲𝗿𝗶𝗮𝗹𝗶𝘇𝗲𝗿 𝗯𝗲𝗻𝗰𝗵𝗺𝗮𝗿𝗸 👀 This benchmark was added to dotnetbenchmarks .com by Saeed Esmaeelinejad recently and looks at serialization times across a number of different libraries commonly used in .NET. If we are in a closed loop app environment where we control the senders and receivers and need the absolute best performance MessagePack looks awesome. Link below in comments. Please add your benchmarks.

203

37 Comments

It would be very great to see all software projects meet at least the following minimal success-criteria: - Developers make daily commits to origin (i.e. to Github) - Minimal PR review process through which code changes take place - Issues are managed as issues (i.e. on the Github repository) - Work specification lives on Github - Engineering milestones / release calendar lives on Github - Secrets are managed as secrets on Github (i.e can only access as code) - 2FA is enabled and required - Branches are protected - Minimal development environment - There is minimal developer documentation (not just auto-gen template) - There is a semantic versioning of changes - There is a semantic naming convention (i.e. the name says exactly what it does e.g. Application-Frontend) This is as much as it can be brought down to a minimal common sense level. Minimally, from the onset, do all these things, for all software projects. Think about it like locking your car door when you leave it for parking, or like using the turning signal when you take a turn or change lane.

3

Two identical components: client-rendered (1st one), 2nd one is server-rendered. Can you see the difference? #nextjs #server_component #client_component

11

4 Comments

📺 On May 9, I am hosting a free online Ask Me Anything webinar. Join me and ask all your questions to fast-track your progress in your software development career. https://lnkd.in/dZPc-4H8 🏆 There will be incredible opportunities and prizes only available to people attending live. You don't want to miss this! 📌 Please like and repost with your network so your colleagues and friends who are interested can join this event. #csharp #dotnet #career #softwaredevelopment #leadership #management

10

𝗥𝗲𝗮𝗰𝘁 𝟭𝟵 𝗖𝗼𝗺𝗽𝗶𝗹𝗲𝗿 𝗶𝗻 𝗮𝗰𝘁𝗶𝗼𝗻. Welcome to my first practical video! Please bear with me as I work on improving my voice and flow. I appreciate your understanding and support! I will be showing a practical example of the new compiler by comparing react 18 & react 19. We will be taking example of 𝗥𝗲𝗮𝗰𝘁.𝗺𝗲𝗺𝗼 usage in react 18 or previous versions. Please play the attached video to see in the action. Before going in to Practical, let's understand it briefly. 𝗧𝗵𝗲 𝗥𝗲𝗮𝗰𝘁 𝗖𝗼𝗺𝗽𝗶𝗹𝗲𝗿 is an experimental tool designed to optimize React applications by automatically applying memoization. It works with plain JavaScript and adheres to React's rules without requiring code changes. The compiler also includes an eslint plugin that highlights optimization opportunities. It's compatible with React 19 RC and can be integrated into various build systems like Babel, Vite, and Next.js. 𝗣𝘂𝗿𝗽𝗼𝘀𝗲 𝗢𝗽𝘁𝗶𝗺𝗶𝘇𝗮𝘁𝗶𝗼𝗻: Enhances performance by automatically memoizing React components. 𝗘𝗮𝘀𝗲 𝗼𝗳 𝗨𝘀𝗲: Works with plain JavaScript without requiring changes to the codebase. 𝗙𝗲𝗮𝘁𝘂𝗿𝗲𝘀 𝗠𝗲𝗺𝗼𝗶𝘇𝗮𝘁𝗶𝗼𝗻 Automatically memoizes components to improve efficiency. 𝗟𝗶𝗻𝘁𝗶𝗻𝗴 𝗦𝘂𝗽𝗽𝗼𝗿𝘁: Includes an eslint plugin to highlight optimization opportunities. 𝗖𝗼𝗺𝗽𝗮𝘁𝗶𝗯𝗶𝗹𝗶𝘁𝘆: Works with React 19 RC and integrates with build systems like Babel, Vite, and Next.js. 𝗨𝘀𝗮𝗴𝗲 𝗘𝘅𝗽𝗲𝗿𝗶𝗺𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻: Encouraged for testing and providing feedback. 𝗣𝗿𝗼𝗱𝘂𝗰𝘁𝗶𝗼𝗻: Not yet recommended for production environments. 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗕𝘂𝗶𝗹𝗱 𝗦𝘆𝘀𝘁𝗲𝗺𝘀: Can be integrated into various build tools and frameworks. 𝗥𝗲𝗮𝗰𝘁 𝗥𝘂𝗹𝗲𝘀 𝗖𝗼𝗺𝗽𝗹𝗶𝗮𝗻𝗰𝗲: Adheres to React's best practices and rules. #React18 #React19 #ReactCompiler #ReactNewCompiler #ReactNative #ReactJS #Hybrid

17

2 Comments

Learn about the benefits of #TDD, and the way I do it: leveraging "prediction", by playing JitterTed's TDD Game: https://tdd.cards/ Soon to be an online game! Buyers of the physical version will get early access to the online game. If you'd like to watch me code the online game live, make sure to follow me on Twitch (https://jitterted.stream), Mastodon (https://lnkd.in/gXTfr37G), where I pre-announce all streams (), or my Discord (https://ted.dev/discord) where you can also discuss the development. (I don't announce here on LinkedIn, because you wouldn't get it in a timely manner.)

8

In order to achieve efficient utilization of cloud resources you need to do two things. First distribute your application into as much microservices as you can. 2nd deploy all those microservices to kubernetes cluster. Kubernetes will take care of pod replicas, based on traffic towards each microservice.

7

1 Comment

🚀 Excited to Share My Experience: Leveraging RabbitMQ for Queuing HTTP Requests 🐇 In the world of session management in an LLM, sometimes unconventional solutions pave the way for seamless operations. Recently, I embarked on an intriguing journey to ensure session persistence by implementing a novel approach - queuing HTTP requests in a RabbitMQ queue. RabbitMQ, renowned for its prowess in queuing tasks and messages, isn't your typical HTTP handler. However, by creatively utilizing its capabilities, I unlocked a realm of asynchronous processing and scalability for our system. Here's a glimpse into my innovative implementation process: 🎯 Defined Task Message: Crafted a comprehensive message format encompassing HTTP request specifics such as URL, method, headers, and body data. 🌐 Web Server (Producer): Engineered our web server to seamlessly publish messages to a designated RabbitMQ queue whenever an HTTP request required asynchronous processing. 🔨 Worker Service (Consumer): Developed a dedicated worker service to consume queued messages, extract request details, and execute HTTP requests utilizing an HTTP client library. 🌟 Benefits Galore:  - Asynchronous Processing: Enhanced performance by decoupling request handling from the web server.  - Load Balancing: Achieving concurrency by deploying multiple workers, optimizing response times.  - Fault Tolerance: Leveraged RabbitMQ features for retries and message persistence, ensuring robust message processing. Amidst this groundbreaking implementation, a few key considerations stood out: 🔒 Security: Prioritized authentication mechanisms for resource access through queued requests. ❗️ Error Handling: Implemented robust error management to gracefully address potential hiccups. 🔍 Monitoring: Ensured seamless operation by monitoring RabbitMQ queues and worker services for bottlenecks. By embracing RabbitMQ in this unique fashion, I orchestrated a symphony of asynchronous HTTP request processing, amplifying the responsiveness and scalability of our web application. Let's embrace innovation, defy conventions, and unlock new dimensions of efficiency together! 💡 #RabbitMQ #HTTPRequests #InnovationAtWork #AsynchronousProcessing Your thoughts and insights are welcome! 🚀🔗 #LinkedInPost #TechInnovations #SessionManagementInLLM #LLM #GenerativeAI 

1

🚀 TypeSafe Navigation in Jetpack Compose vs. Traditional Intent Passing: Which One is Better? Navigating between screens is a crucial aspect of mobile app development. In the Android ecosystem, we have two primary methods: Traditional Intent Passing and TypeSafe Navigation in Jetpack Compose. 🤔 Learn here: https://ylnk.xyz/@WjkyMk #android #kotlin #compose #jetpack #jetpackcompose #datapassing #typesafe #navigation #typesafenavigation #techarticles #goodcode #cleancode #rommansabbir

22

.𝗡𝗘𝗧 𝗯𝗲𝗻𝗰𝗵𝗺𝗮𝗿𝗸 𝗱𝗶𝗿𝗲𝗰𝘁𝗼𝗿𝘆 𝗹𝗮𝘂𝗻𝗰𝗵𝗲𝗱 ⏲️ https://lnkd.in/eC37dJ_y is a 𝗕𝗲𝗻𝗰𝗵𝗺𝗮𝗿𝗸𝗗𝗼𝘁𝗻𝗲𝘁 𝗹𝗶𝘀𝘁𝗶𝗻𝗴 𝘀𝗶𝘁𝗲. Once you login with GH you can add a benchmark by importing a Gist or just pasting the code in directly. It's 𝗶𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗲𝗱 𝘄𝗶𝘁𝗵 𝗦𝗵𝗮𝗿𝗽𝗟𝗮𝗯 so the lowered code and Jit ASM should be available too for built in assemblies. It's very initial version for the moment but I'll invest more time on the UI, UX, features etc. once I get a little feedback that this could be something devs would like. It would be amazing 𝗶𝗳 𝘆𝗼𝘂 𝗰𝗼𝘂𝗹𝗱 𝗮𝗱𝗱 𝗯𝗲𝗻𝗰𝗵𝗺𝗮𝗿𝗸𝘀, 𝘀𝘁𝗮𝗿 𝗯𝗲𝗻𝗰𝗵𝗺𝗮𝗿𝗸𝘀 𝗮𝗻𝗱 𝗮𝗱𝗱 𝗰𝗼𝗺𝗺𝗲𝗻𝘁𝘀 etc. I'd like this to be a community site so your contributions are vital. I think a centralized place for devs to discuss and learn from benchmarks would be amazing. There's 60 or so benchmarks now, but potentially we could have hundreds or thousands up there which would make it a great learning resource for devs. What do you think? Thanks to everyone who has given feedback and particularly those who have already added content.

310

48 Comments

Your messages include important data and must not get lost. Discover the features of RabbitMQ and never lose a message again! Learn how to implement alternate exchanges and the BasicReturn event handler, ensuring no message goes unrouted. Dive into my guide and transform your message handling today! https://lnkd.in/dsAWAnVE

8

2 Comments

I've recently explored Zustand and Redux for state management in React applications. Both Zustand and Redux have their strengths, and the choice between them depends on the specific requirements of your project. For complex applications with extensive middleware needs, Redux is a solid choice. For simpler projects or when seeking a more straightforward state management solution, Zustand offers a compelling alternative. Happy Coding 😄 Master Redux from JavaScript Mastery #coding #programming #redux #zustand #react #statemanagement #javascript

8

3 Comments

🔔 Introduction to Message Brokers 🔔 Message brokers are essential for modern distributed systems, facilitating communication between applications by translating messages between protocols. They improve scalability, reliability, and message routing. Two popular brokers are RabbitMQ and Apache Kafka. RabbitMQ excels in task queues, real-time messaging, and RPC with support for multiple protocols and flexible routing. Kafka is ideal for high-volume, real-time data streaming, event sourcing, and log aggregation, offering horizontal scalability and low latency. Choose the right broker based on your application's specific needs for a robust, scalable messaging system. 🚀 #MessageBrokers #DistributedSystems #RabbitMQ #ApacheKafka #Messaging #Scalability #Reliability #Flexibility #Decoupling #RealTimeData #EventSourcing #LogAggregation #Middleware #TechTalk #SoftwareDevelopment #Microservices #DataStreaming #HighThroughput #FaultTolerance #SystemArchitecture #StreamProcessing #DataIntegration #RealTimeAnalytics #Clustering #HighAvailability #ProtocolSupport #ManagementTools #ScalableSystems #BigData #LowLatency #MessageRouting #LoadBalancing #MessageTranslation #TechInsights #SoftwareEngineering

5

Backend projects will take you to a Senior position. Design and Improve a Relational Database - Design a Database - Apply Normalization - Improve Indexing - Do Query optimization Build a REST-style API with Authentication & Authorization - HTTP Methods (GET, POST, PUT, and DELETE) - System modeling and design - Data Protection - User management - Tests with Postman Implement a Caching Layer Caching helps reduce the load on databases and improves response times. The cache will show how you optimize performance and handle high-traffic loads. Microservices Architecture If you land in a large company, you must deal with Microservices. - Design a Distributed System - Handle communication between services - Learn about Fault Tolerance DevOps and Infrastructure Understanding how to deploy applications: - CI/CD - Docker - Kubernetes - IaC tools like Terraform or CloudFormation, ARM Also, technical expertise is only part of the equation. A Senior role demands: - Leadership - Mentorship - Effective communication The theory will help, but what will make the difference is the hands-on experience.

1,025

84 Comments

Using Florence2 model by Microsoft--a good small model for various visual tasks. Running it on a MacBook Pro using the transformers library requires some tweaking--ignoring the flash_attn dependency because it does not support Apple Silicon.

5

Understanding Message Rate in RabbitMQ In the world of messaging brokers, RabbitMQ stands out for its robustness and versatility. One of the key metrics for assessing and optimizing RabbitMQ performance is the message rate. This rate measures the number of messages published and consumed per second and is critical for ensuring your system handles the required load efficiently. Why Message Rate Matters: The message rate directly impacts the throughput and latency of your applications. A high message rate indicates a capable system, but it also requires careful tuning to prevent bottlenecks and ensure reliability. Strategies to Optimize Message Rate: 1. Efficient Load Balancing:   Distribute the message load evenly across consumers to prevent any single consumer from becoming a bottleneck. Tools like HAProxy and Kubernetes can help achieve effective load balancing. 2. Rate Limiting:   Implement rate limiting to control the flow of messages and avoid overwhelming your consumers. This can be managed within RabbitMQ or at the application level. 3. Monitoring and Alerts:   Use monitoring tools like RabbitMQ Management Plugin, Prometheus, and Grafana to track message rates. Set up alerts to notify you of any anomalies or spikes in message traffic. 4. Consumer Optimization:   Ensure your consumers are optimized for performance. This includes tuning the prefetch count, using efficient data processing techniques, and scaling consumers horizontally as needed. 5. Cluster Deployment:   Deploy RabbitMQ in a clustered environment to distribute the load across multiple nodes, improving fault tolerance and scalability. 6. Configuration Tuning:   Adjust RabbitMQ configurations to better handle high message rates. Key settings include message TTL (Time-To-Live), queue length limits, and connection parameters. Best Practices: - Regularly Monitor Performance: Consistent monitoring helps in quickly identifying and resolving issues that impact message rate. - Scale Appropriately: Use both vertical and horizontal scaling strategies to manage increased loads. - Optimize Network and Hardware: Ensure that your network infrastructure and hardware are optimized to support high throughput. By focusing on these strategies, you can ensure that your RabbitMQ setup is capable of handling high message rates, leading to more efficient and reliable messaging within your distributed systems. #RabbitMQ #MessageRate #MessagingBroker #LoadBalancing #RateLimiting #Monitoring #Scalability #PerformanceOptimization #DevOps #Tech #Technology #CloudComputing #SoftwareEngineering #SystemArchitecture

17

Email is an essential and widely used technology, but it has significant issues on the backend. For example👇 𝟭. 𝗟𝗮𝗰𝗸 𝗼𝗳 𝗦𝘁𝗮𝗻𝗱𝗮𝗿𝗱𝗶𝘇𝗮𝘁𝗶𝗼𝗻: 👉Reply placement (top or bottom) is inconsistent and subjective. 👉HTML compatibility varies; some clients (like Microsoft Outlook) use different HTML renderers, leading to inconsistencies. 👉Email encryption (like OpenPGP) is rarely used and flawed. 𝟮. 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 𝗮𝗻𝗱 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗣𝗿𝗼𝗯𝗹𝗲𝗺𝘀: 👉SPF, DKIM, and DMARC were developed to ensure email authenticity, but each has limitations and can be bypassed. 👉Only a small percentage of domains enforce strict policies (p=reject) for DMARC, leading to ineffective security. 𝟯. 𝗦𝗲𝗹𝗳-𝗛𝗼𝘀𝘁𝗶𝗻𝗴 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲𝘀: 👉Running an email server is complicated due to anti-spam measures and IP reputation management. 👉Shared IP systems can result in legitimate emails being marked as spam. I write one post for software engineers everyday at 10. Follow Pratik Daga so that you don't miss them.

43

2 Comments

Check my article on Deep Linking in Android with App Links and Install Referrer API

5

Mastering the Unit of Work Pattern in C# for Modern Applications Should we use UOW always? Well.. we should in my project now, but actually, it's not always the best way to go. In this post I've analyzed the pros and cons of using the UOW to get to that conclusion. Interesting approaches that say to remove the UOW especially if using EF and why should we keep it, nevertheless.. like and follow :) #SoftwareDesign #Arhcitecture #BestPractise

2