Mohamed Sakher Sawan

Join us and #contribute to a #safer job market: https://lnkd.in/e4twPVff or simply search for "uaesoftwareengineers" on #Telegram. We're thrilled to introduce our comprehensive drive aimed at addressing various needs within the #software #industry in the #UAE. Here’s how we're supporting our members: #Awareness about #UAE #Labour #Laws: Educating members on their rights and responsibilities under UAE labour laws through workshops and informational resources. #Industry #Connections: Facilitating webinars, Q&A sessions, and forums with industry experts. #Talent #Pool Maintenance: Developing a database of professionals, hosting virtual job fairs, and offering resume workshops. #Job #Scam #Reporting: Setting up reporting mechanisms, publishing verified scam alerts, and collaborating with authorities. #Market #Guidance for #Freshers: Providing career counseling, market trend analysis, and mentorship programs. #Event and #Meetup #Information: Creating a centralized calendar, sending newsletters, and promoting local events. Join us in enhancing #professional #growth and ensuring a safer job-seeking environment! 🚀 #UAESoftwareIndustry #CareerGrowth #JobScamPrevention #TechConnections #TalentPool #FreshGradGuidance #IndustryEvents #ProfessionalDevelopment #Uae

9

🚀 **Building Scalable Enterprise Applications in C#? Let’s Talk Best Practices!** 🧑‍💻 👩‍💼 Imagine this: Your C# application is handling 10 users effortlessly, but can it handle 10,000? 100,000? Scalability is the superpower that ensures your enterprise applications grow with your business — without breaking a sweat. Here’s what makes a difference: ✅ **Asynchronous Programming** – Optimize performance and reduce bottlenecks with async/await. ✅ **Dependency Injection (DI)** – Keep code clean, testable, and decoupled to handle future complexities like a pro. ✅ **Caching Strategies** – Slash response times by implementing efficient memory or distributed caching solutions. ✅ **Microservices Architecture** – Scale services independently instead of rebuilding the monolith. ✅ **Profiling & Optimization** – Regularly review your code for hotspots and optimize for long-term efficiency. 💡 By mastering these practices, you’ll equip your applications to thrive under high demand while delivering smooth user experiences. 📣 *Your turn*: Have you implemented these strategies in your own work? What challenges did you overcome when scaling C# applications? Share your insights or drop your questions in the comments! Let’s collaborate and grow together. #CSharp #EnterpriseDevelopment #Scalability #CodingBestPractices #moa7amed #moa7amed_com

1

🚀 **Why DevOps is the Superpower Your Team Needs in Modern Software Development** Imagine delivering high-quality software faster, with fewer bugs, and happy teams that actually enjoy collaborating. That’s not a dream—it’s the reality DevOps brings to the table. By bridging the gap between development and operations, DevOps enables: ✨ **Faster delivery**: Automate repetitive tasks and streamline workflows. ✨ **Higher quality**: Test continuously to catch issues early. ✨ **Team alignment**: Improve collaboration by breaking silos. ✨ **Scalability**: Handle growth seamlessly with cloud and CI/CD tools. DevOps isn’t just a practice—it’s a mindset that changes the way software gets built and delivered in today’s fast-paced tech world. Want to empower your team to innovate faster and smarter? Start by embracing DevOps. #DevOps #SoftwareDevelopment #TechInnovation #Automation #CI_CD #Agile #moa7amed #Kaggle #Teamwork

1

Our APIs no longer redirects from http to https. At DinnerBooking we have a lot of APIs so restaurants can get all kind of data about their bookings. We used to redirect any http request automatically over to https for security, but we have now stopped doing that. Why you may ask. I was reading this article about "Your API Shouldn't Redirect HTTP to HTTPS" from https://lnkd.in/dvD3MYuh Here they suggest to apply to the Fail-fast Principle, which makes a lot of sense. So now our APIs responses with a 403 error saying "The DinnerBooking API is only accessible over HTTPS"

17

Mermaid diagrams are now available in Notion, Obsidian and VS Code. It's fast becoming the default Markdown format for diagrams. Mermaid is great for quick flowcharts, but the real power is that the format is fairly straightforwards to populate from dynamic data (such as a spreadsheet or database). We have a lot of complex business logic and process flows in the Icehouse Ventures investment app, so we threw together a quick open source package for using Mermaid in Laravel: https://lnkd.in/dda6tBag

16

4 Comments

I keep hearing the idea that pull requests are bad and that developers shouldn't do them. Well, to me, most of these arguments are somewhat of a straw man variety and they encourage throwing the baby out with the bathwater. Pull requests aren't the problem. Pull requests won't prevent you from doing continuous delivery. The problem is pull requests that take a long time to review and approve. This is the thing that will prevent you from doing continuous delivery. But this is a very avoidable problem. It doesn't have to be this way. In our team, PRs don't normally take long to review and things in the trunk are being updated regularly. So it was in my previous team in my previous place of work. I worked in at least three different teams where we would try to get rid of PRs to see what will happen. In all of those cases, we had to get back to doing PRs because removing them caused more problems that we were trying to solve by removing them. I get it. It may work for some teams that do pair programming all the time, which I see as the only way to keep the code quality up without the PRs. However, this approach will not suit every company and every developer. Many developers I know will find it exhausting having to pair-program all the time. Even when you pair program, PRs still have their use. Just before you push all those commits you created, you can create a PR to view all the challenges to make sure you haven't missed anything. You will not only be able to verify that no temporary code changes go in, but you will also create a nice audit trail of who made the change and who reviewed it. I even sometimes create a PR for my own changes because because it's a tool that makes a pre-push verification very convenient. PRs are just a tool. Just like any other tool, it can either be used or misused. It only causes problems when it's misused and not when it's used properly. This tool may not be useful to you, in which case you may discard it. But you may also find out that it's not as useless as some people say it is and it won't stop you from doing continuous delivery, as these people say.

38

26 Comments

Here is the very useful repo for #remote job finders. list of active remote first companies available and well maintained in the repo. https://lnkd.in/dB-3dsXz Further you can subscribe to any company for regularly getting active positions in email from this link 👇 https://lnkd.in/dFAE4dzz #remotejob Thank you so much Yanir Seroussi for making this repo. This post is Inspired by the mission of Wajahat Karim 🇵🇰 . #remotekaro #remotejobs #remotelifestyle

112

5 Comments

Most companies struggle to hire killer senior engineers. So what should the ideal interview process for finding this talent look like? Whenever I advise early-stage tech startups, I tell them to include the following questions and steps in their interview process for senior engineers: 1. Have them interact with stakeholders in the company You need proof that a senior engineer can work well with stakeholders. They must be able to delegate and empower engineers to make various decisions. Any engineer who can communicate well and work with stakeholders is a solid hire. 2. Have them speak to a designer or product manager Senior engineers will be speaking to designers and product managers frequently. If you can get a designer or product manager involved in the interview process, you want your colleague to assess whether that engineer is someone they can work with. Some questions they can think about include: - Can I have a conversation about what’s valuable to the business with this engineer? - Can this engineer communicate well? Do they complicate things? Do they oversimplify? - How do they react if there’s an ask from design or marketing? What is their thought process? 3. Figure out their attitude toward junior engineers A senior engineer’s attitude toward junior engineers is a good bellwether of their attitude toward communication and documentation. One sign of a poor senior engineer is someone who can’t explain their work — or doesn’t feel like they have to. They feel no need to document what they’re doing and they assume everyone around them, like their junior engineers, will just get it. If you ask an engineer, “How do you communicate your work to others?”, and they say “I don’t really see the value in that,” that’s not someone you want to hire. It’s incredibly important to an early-stage organization to prioritize clear documentation and communication. I’ve advised too many companies that did this too late and had to waste time parsing the code of engineers who didn’t bother to document anything. Any startup can avoid this fate by hiring good senior engineers who explain their work every step of the way. 4. Figure out how they plan for the future Developing a good product isn’t just about good design or code. It’s also about future-proofing your code. I think a big thing about seniority is balancing making good decisions quickly while not shooting yourself in the foot. It means seeing beyond the future and recognizing the implications of their decisions, such as: - Is this code future-proofed or not? Am I creating technical debt? - Has this particular solution created any new problems for the team? Who knows how to solve them? Am I the only one who knows? You especially don’t want your company to deal with technical problems that can only be solved and documented by one person on the team. That can lead to a crisis if that person ends up leaving. cont. 👇

3

1 Comment

🚀 GPT-4 Breaks AI Barrier: Passes Turing Test! Researchers claim GPT-4, the AI behind ChatGPT, has achieved a historic milestone by becoming the first to pass the iconic Turing test. 🎓 📜 The Turing Test, proposed by Alan Turing in 1950, evaluates whether an AI's responses are indistinguishable from a human's during conversation. 🔬 In the study, 500 participants conversed with a human, ELIZA (a 1960s AI), GPT-3.5, and GPT-4 for 5 minutes each. They then judged whether each was human or AI. 📊 Results: GPT-4 was judged human 54% of the time, outperforming ELIZA (22%) but trailing actual humans (67%). GPT-3.5 scored 50%. 🌍 This suggests GPT-4's responses often can't be distinguished from humans - a significant AI milestone. But it also raises concerns about AI deception. 😮 Share your thoughts in the comments below! 👇 https://lnkd.in/eQvFMaA9

6

What I will remember from 2 days of Tech Open Air: 1- If you do not understand the concepts of LLM and GPT by now you are well on your way to making yourself redundant in the workplace. 2- Developing your own language models is a nonsensical activity. Use the existing resources, adapt them with existing tools and inlay the focus on your own process and the ux. 3 - Web3 with crypto, blockchain, ... is beyond the hype and becoming a mature, parallel universe. But with the overload of meaningless terminology, the movement seems to be getting in the way of its own success. 4 - Quantum computing seems as promising as it was a few years ago but the road is still long. As for the speakers: The tech scene also has super stars. Man of the day was Colin Jarvis, the chierf architect of open AI Most insights I got during the talk of Joanna Bryson about new de AI act. Very clear and at the same time nuanced. Of the sattelite events I especially remember the Deep Tech Night of Fraunhofer Heinrich Hertz Institute HHI and Silicon Allee ; nice place, nice organization, nice people and catering that was 2/3 vegan. Merci toa and merci Bart Wolfs for joining me.

14

3 Comments

🚀 Looking to build scalable enterprise applications with C#? Mastering best practices isn't just a suggestion—it's the key to creating efficient, maintainable, and future-ready systems. ✅ **Here’s Why It Matters:** - **Performance Boost:** Applying tried-and-true patterns ensures your code runs like a well-oiled machine, even under heavy loads. - **Cleaner Architecture:** Dependency Injection, CQRS, and SOLID principles keep your codebase organized and maintainable. - **Seamless Scaling:** From caching strategies to asynchronous programming, harness techniques that grow as your application scales. - **Teamwork Made Easy:** Standardized practices mean fewer headaches during code reviews and faster onboarding of new developers. 💡 Whether you're leveraging .NET 6's latest features, optimizing LINQ queries, or embracing asynchronous APIs, always measure and refine. Small tweaks today can save days—if not weeks—of work tomorrow. What’s your go-to best practice in C#?👇 #CSharp #EnterpriseDevelopment #CodeBetter #Moa7amed #Kaggle #ProgrammingTips #DotNETDevelopment

1

Exploring the Culinary Techniques Behind Software Platform Architectures... Platform-based businesses have flourished over the years (Airbnb, Facebook, Uber, Grab, Spotify, etc.). They have one thing is common; they are architected for massive scale: Uber 150 millions monthly active users (MAU), Grab 35m MAU, Amazon 200m MAU, Shopify 2.1m DAU. The design principles of a platform help identify the underlying infrastructure components and core functions needed to support one or multiple user workflow(s) (eg. the job to be done). User workflows are encapsulated into applications. Applications are the interface that users interact with and the vehicle that generates the revenue streams. When it comes to platform architecture design, I often use the analogy of opening a restaurant. It sounds obvious, but you can’t open a restaurant without a menu, can you? Just like a list of ingredients does not make it a meal, a collection of features does not make a product! In the product development world, we tend to focus on building the platform components that will make the applications sitting on top more scalable, more robust, more secure, easier to maintain and configure. But once we have spent all this time building a beautiful kitchen, we forget we did not spend enough time in designing a menu for our customers... Choosing the right location, building the right kitchen, getting the right ingredients, picking the right team are to restaurants what a technology stack, infrastructure, data, SDK, API and development teams are to software development... Let's dive in, shall we? Read story here: https://lnkd.in/g6K23aCg #productmanagement #innovation #technology #personalgrowth __________________ P.S. for more of these check out ‼️ https://koncentrik.co ‼️, THE newsletter you need to follow Technology-led Innovations. For tech builders and business leaders.

16

1 Comment

What is Anti-Corruption Layer (ACL) Pattern? Imagine this scenario: You have two different software systems, like two different computer programs, that need to talk to each other. But, they speak different "languages" or formats. The Anti-Corruption Layer (ACL) is like a translator that stands in between these systems and makes sure that when one system says something, the other can understand it without any confusion or "corruption" of the information. Key Points of Anti-Corruption Layer Façade or Adapter Layer: Think of this layer like a translator who understands both languages and translates requests from one system to the other. Different Subsystems: The systems or subsystems don't share the same language or way of understanding things. Translation of Requests: When one subsystem makes a request, the ACL translates it into a form that the other subsystem can understand. Independence in Design: This pattern helps keep the design of your application clean and not heavily dependent on the way outside systems work. It keeps the core of your application safe from getting messy due to outside influences. Origin: The idea was first described by Eric Evans in his book on Domain-Driven Design. Example Real-world Example: Imagine you are in a multi-national company where the headquarters speak English, but a branch in Japan speaks Japanese. To communicate effectively, the company hires translators (this is your ACL). When the headquarters (System A) sends instructions in English, the translator (ACL) converts them into Japanese so the branch in Japan (System B) can understand. When the branch in Japan sends feedback in Japanese, the translator converts it back into English for the headquarters. This way, both sides can communicate effectively without learning each other’s languages, and no message gets lost or misinterpreted. Using in Azure Logic Apps In Azure Logic Apps (a cloud service that helps automate tasks and workflows), the ACL pattern can be implemented to ensure that different services (like databases, APIs, or other systems) communicate smoothly even if they speak different "languages." Simplified Steps: Set up your Logic App: Create workflows that you want to automate. Create the ACL: Add a layer in the workflow that will act as the translator between different systems. Define Translations: Specify how data from one system should be converted for another system. Run and Test: Ensure everything works seamlessly, with your ACL handling all translations in the background. Use this pattern when: 1) A migration is planned to happen over multiple stages, but integration between new and legacy systems needs to be maintained. 2) Two or more subsystems have different semantics, but still need to communicate.

4

Key challenges in implementing a RAG system: * Fabricating answers (missing content). * Missing key info (suboptimal responses). * Making sense of retrieved info (context issues). * Handling massive data (data ingestion). * Extracting complex answers (structured data QA). https://lnkd.in/erhbDVXs #AI #LLM #Technology #Innovation #NLP #TechChallenges #MachineLearning

4