Magid Mroueh

Developing "Travel Agency OS" with Notion for Travel with Saad Zakaria ! Can't imagine Notion not only ✅ all the requirements, but provides much better experience & productivity. Some outlines: 1. Intuitive UI / UX 2. Automation Triggers on Slack 3. Alerts / Reminders for important moments. 4. Modular 5. Very much extensible It's just like LEGOs, you play around, and build some amazing Workspaces with flows of your choice. If you want to manage your business or org the way you want, feel free to connect.

59

1 Kommentar

Any folks from the React team/community who can help shed some light on this issue? I am not sure if you are aware, but the latest React documentation on react.dev is currently inaccessible from within Iraq. This barrier is forcing our developers there to either use outdated documentation or turn to VPNs. While VPNs are a workaround, they introduce several issues such as reduced internet speed, increased latency, less reliable connections with frequent drops, added complexity in setup and management, and potential security risks due to misconfigurations. Currently, the only documentation available without a VPN is from legacy.reactjs.org, which is far from adequate for devs trying to stay up to date. Relying on these older resources further exacerbates the digital divide and prevents our developers from keeping up with the latest advancements in React. It is unclear whether this blockage originates from the React team’s hosting configurations or from regulatory actions by the Iraqi government. Is there a way to determine the source of this issue? Understanding this could help us find the most effective approach to address the problem. I know that as a tech community, we believe in the power of technology to transcend borders and foster an inclusive environment where everyone has the tools they need to succeed. Therefore, I ask the React team/community for support here: I am not sure of the reasons for which react.dev is not accessible from Iraq, but could there be another way to provide these vital resources for the developers of your community? Your support and suggestions would be invaluable as we seek to ensure that all developers - regardless of their location - have equal opportunities for learning and growth.

24

4 Kommentare

Think you’re unqualified for the work you do? It’s called #imposter #syndrome and we are here to help you UAE | MENA Software Engineers & QA Telegram Link: https://lnkd.in/e4twPVff To be honest, you never really will be an expert in software development. There will always be more to learn. There will always be new #languages, or #processes, or #technologies to learn. There will always be someone who knows something you don’t. There will always be someone who knows more than you do. There will always be someone who’s a better developer. That thought may be depressing right now, but I feel it’s actually liberating. You can focus on getting better and growing. Focus on what you can control: your #skills and your #knowledge. Accept that there will never be a point where you’ll feel completely knowledgeable and completely comfortable. Embrace your ignorance and use that to fuel your growth #impostersyndrome #wecanhelp #readytohelp #letstalk #askmehow #icanhelp #letsworktogether #areyouready

6

RabbitMQ vs. Kafka: In the world of microservices, efficient communication is key. But when it comes to choosing the right messaging champion, two contenders stand out: RabbitMQ and Kafka. Both are powerhouses, but their strengths differ. RabbitMQ: The Agile Champion RabbitMQ is a message broker, excelling in complex routing and reliable delivery for smaller datasets. Its AMQP protocol ensures clear communication, and its flexible plugins allow customization. Ideal for transactional tasks like order confirmations, user actions, and internal messaging within your application. Kafka: The Scalable Streamer Kafka is a distributed streaming platform, built for real-time data processing of massive datasets. Its append-only log allows efficient access to historical data, and its horizontal scaling ensures smooth handling of high traffic. Ideal for real-time data processing, event-driven architectures, and processing large datasets for insights. Who is best in scenarios - - Message volume: If you deal with massive data streams, Kafka should get priority. - Message complexity: For complex routing and diverse message types, RabbitMQ shines. - Scalability needs: If you anticipate rapid growth, Kafka's horizontal scaling is unbeatable. - Real-time requirements: For real-time data processing, Kafka delivers. - Ease of use: For simpler deployments, RabbitMQ's lighter weight might be better. Feel free to share your views.

7

💡 It took me 4 years to reach the Senior Engineer level. Here are 5 key skills that got me there: 1. Mastering ASP.NET Core 🔹 Creating a RESTful API is a great starting point, but as a Senior Developer, I learned to leverage the many advanced features the platform offers to build robust applications. 2. Design Principles and Patterns 🔹 Writing maintainable and scalable code comes down to understanding design principles and patterns. Mastering when and how to apply these makes a big difference in developing high-quality software. 3. Cloud Computing and Azure 🔹 The cloud is integral to modern software infrastructure. Familiarity with essential Azure services is a must for designing scalable, efficient solutions. 4. DevOps Practices and CI/CD Pipelines 🔹 Seamless software delivery hinges on strong DevOps practices. Building and maintaining effective CI/CD pipelines is a core skill for ensuring continuous integration and deployment. 5. Microservices and Containerization 🔹 Building scalable, cloud-ready .NET systems involves understanding microservices architecture and how to leverage containerization effectively to manage them. These five areas have been crucial in my journey to becoming a Senior Developer. Master them, and you'll be well on your way to advancing your career! Follow: Hamza Ali Khalid #CareerGrowth #SeniorDeveloper #ASPNetCore #CloudComputing #DevOps #Microservices #SoftwareEngineering

5

A proposal for a new architectural design pattern for structuring backends and microservices. Your feedback is highly appreciated 🙏 #design_pattern #proposal #backend #mvc

9

4 Kommentare

How to fix NPM issue that results in "Unsupported engine" #javascript #npm #nodejs

8

One important part of development is getting the architecture right. 😎 💪 I've put together a little demo on how to work with angular workspace for a scalable and sustainable architecture on Tech Stack Nation. 💯 🔥 The best thing about Tech Stack Nation is that we can share all these cool demos with others like Ibrahim Sefer and others to get more confidence on architecture and public speaking. Join Tech Stack Nation to learn with us 🤗 Thanks AG Grid for sponsoring communities like this! 😍 #TechStackNation #AngularWorkspace #Architecture

28

🚀 𝐀𝐧𝐠𝐮𝐥𝐚𝐫 𝟏𝟗: New Features to Boost Your Development Workflow Angular 19 is set to launch with exciting updates that promise to make your development process smoother and more efficient. Two standout features—𝐋𝐢𝐧𝐤𝐞𝐝𝐒𝐢𝐠𝐧𝐚𝐥 and the 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞 𝐀𝐏𝐈—are here to enhance state management and data fetching in Angular apps. 1️⃣ 𝐋𝐢𝐧𝐤𝐞𝐝𝐒𝐢𝐠𝐧𝐚𝐥: 𝐒𝐢𝐦𝐩𝐥𝐢𝐟𝐢𝐞𝐝 𝐒𝐭𝐚𝐭𝐞 𝐌𝐚𝐧𝐚𝐠𝐞𝐦𝐞𝐧𝐭 🔗 LinkedSignal allows you to track local state that depends on other signals. It automatically resets based on changes in related signals, making it easier to manage the state without manual intervention. 2️⃣ 𝐑𝐞𝐬𝐨𝐮𝐫𝐜𝐞 𝐀𝐏𝐈: 𝐒𝐭𝐫𝐞𝐚𝐦𝐥𝐢𝐧𝐞𝐝 𝐃𝐚𝐭𝐚 𝐅𝐞𝐭𝐜𝐡𝐢𝐧𝐠 🌐 The new Resource API simplifies how you fetch and manage asynchronous data. It leverages Angular's Signals for a reactive, efficient approach to handling external data sources, from loading to caching. 𝐂𝐨𝐧𝐜𝐥𝐮𝐬𝐢𝐨𝐧 ✨ With LinkedSignal and the Resource API, Angular 19 is set to make state management and data fetching simpler, cleaner, and more efficient. If you’re working on Angular applications, these features are definitely worth exploring. For more details, check out these helpful resources: https://lnkd.in/djBZuTrJ https://lnkd.in/dzBYKqwq https://lnkd.in/dA5rmxGs

16

Interesting article about TDD helps to write more better code, but it might take time to find the right path to have the most benefits from a TDD approach  https://lnkd.in/eFDdFqrj 

2

Deleting code can feel like an unnecessary risk but it's crucial for maintaining a healthy code base. 💡 Pro Tip: To avoid surprises, use the "Find All References" feature in VSCode and post in your team's group chat what you're removing. This will encourage everyone to "clean as they go". I love seeing more red then green when reviewing PRs, how about you? Need a one-liner? Every line of code is a liability, not an asset! #Technology #SoftwareDevelopment #Coding #Innovation #CleanCode

10

Master C# for SaaS Development! Discover why C# is your ticket to modern SaaS glory. It's easy to learn, super powerful, and perfect for scalable cloud apps. Set Up Your Environment: Use Visual Studio or Rider. Create a New Project: Use the terminal to get started. Build Your API: Minimal code, maximum efficiency. Database Management: Use Entity Framework or Dapper. Add Authentication: Implement with Identity. Deploy on Azure: Enjoy scalability features. And BAM! You’re all set to impress your users.

2

An opinionated dev setup In this blog post and video, I walk you through the development setup for my projects. Devbox, process-compose, tmux, gh, gh-dash, nvim (your editor of choice). Regardless of which project I work on, the terminal layout and tools I use are always the same. This means, instead of remember the unique workflows and scripts for each project, I remember how to work once and it applies to any project. https://lnkd.in/gzsTZVUv

2

As a former architect .. I find system designing and architecture in software world very interesting and challenging. A nice path to consider. #design #architecture #software #systems

2

𝗛𝗼𝘄 𝗜 𝘀𝘁𝗼𝗽𝗽𝗲𝗱 𝘀𝘁𝗿𝘂𝗴𝗴𝗹𝗶𝗻𝗴 𝘄𝗶𝘁𝗵 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝘁𝗼𝗼𝗹𝘀—𝗺𝘆 𝗷𝗼𝘂𝗿𝗻𝗲𝘆. I still remember the time when I felt like I was drowning in automation tools. My team was working on a critical project, and we kept switching between Selenium, Appium, and Rest Assured. Every time we switched, it felt like we were starting from scratch. I’ll never forget the day we were under a tight deadline, and I had just spent hours trying to get a Selenium test suite to work properly. Then, out of nowhere, my manager asked if we could switch to Playwright for a cross-browser test. I panicked. I knew nothing about Playwright at that time, and learning a new tool on the fly felt impossible. That day, I felt defeated. I realized that unless I found a way to quickly adapt to new tools, I’d keep facing the same struggle. So, I made a decision—I started learning how to seamlessly switch between tools. I focused on building skills that allowed me to pick up any automation tool and get started without wasting time. Over the next few months, I mastered the art of choosing the right tool for each task and became confident in my ability to adapt quickly. That shift changed everything. Now, I can confidently switch between Selenium, Appium, Rest Assured, and Playwright based on the project’s needs. If you’ve ever felt overwhelmed by automation tools like I did, just know there’s a way out. You can make switching tools a painless part of your process. To discuss the Automation tools switching strategy in detail, 𝗥𝗲𝗴𝗶𝘀𝘁𝗲𝗿 𝗳𝗼𝗿 𝟮 𝗗𝗮𝘆𝘀 𝗔𝘂𝘁𝗼𝗺𝗮𝘁𝗶𝗼𝗻 𝗧𝗲𝘀𝘁𝗶𝗻𝗴 𝗙𝗥𝗘𝗘 𝗪𝗼𝗿𝗸𝘀𝗵𝗼𝗽, Simply by joining the WhatsApp group - https://lnkd.in/dpnq7v-A #bymatautomation #rahulganjare #automationtesting #automationtraining #myjourney

3