Mohammed Chabab

In this Inside #Java Newscast you'll get a look at the goals and history of Project Leyden, and how to evaluate Project Leyden in your projects. https://lnkd.in/gu6EAUz7

1

DuckDB is a powerful tool for working with data. Everyone should have this in their data toolbox.

1

What?!? You haven't submitted your session proposals to Azure Fest NL already? Be sure to submit your #Azure-related sessions to the open CFP https://lnkd.in/etkqrcXk We'll be selecting sessions in about a month from now, so make the reviewing hard on us. While I'm not an official attendee, I'd love to see some sessions on: - event-driven solutions on Azure - Handle and consume big data - Real GenAI solutions on Azure - Scaling multi-region - Secure your Azure environment - Assume breach solutions - ..and of course, many more topics because I have a wide interest in tech #containers #azure #genai #networking #data #paas #saas #iaas #security

10

2 commentaren

In this Inside #Java Newscast you'll get a look at the goals and history of Project Leyden, and how to evaluate Project Leyden in your projects. https://lnkd.in/edDYwDMF

1

In this Inside #Java Newscast you'll get a look at the goals and history of Project Leyden, and how to evaluate Project Leyden in your projects. https://lnkd.in/eu55R8wU

1

It takes time to learn how to talk to Copilot (how to prompt actually). Here is an example: https://lnkd.in/eycbuMJc

3

1 commentaar

I often have this question during my Copilot engagements: can we use Copilot for Microsoft 365 to help developers. The answer is yes and no. When to Use Each Use Copilot for Microsoft 365 when your development tasks involve a lot of documentation, data analysis, project management, or collaboration within the Microsoft 365 ecosystem. Use GitHub Copilot when you need direct assistance with coding, debugging, learning new programming languages, or managing code repositories. If you are looking for simple assistance to write a PowerShell or a SQL query you could use Copilot for M365, but the best place for developers is GitHub Copilot: https://lnkd.in/epmuYaD3

5

Some useful Copilot tips to prompt efficiently https://lnkd.in/emtWywP6

6

🚀 DE Interview 📢 Serverless Architecture ⌛ 1-Min-Read Benefits of Migrating to Serverless 👉🏽 🧔🏽‍♂️Interviewer: Can you explain the benefits of migrating to a serverless architecture? 👨‍🦰Candidate: Migrating to a serverless architecture eliminates the need for managing servers and infrastructure, allowing developers to focus on writing code. This shift not only reduces operational overhead but also enhances scalability, as serverless architectures automatically scale based on demand. Additionally, with a pay-as-you-go model, costs are optimized since you only pay for the resources you actually use. Serverless architectures also improve deployment speed, allowing for quicker releases and iterations. 🧔🏽‍♂️Interviewer: Could you elaborate on how operational overhead is reduced and how that impacts development? 👨‍🦰Candidate: In a serverless architecture, the cloud provider takes care of the underlying infrastructure, including server provisioning, patching, and scaling. This reduces the burden on the operations team, freeing them to focus on other tasks. For developers, this means they can spend more time on coding and innovation, rather than on infrastructure management. It also reduces the risk of downtime or performance issues related to server management, improving overall system reliability. 🧔🏽‍♂️Interviewer: How does serverless architecture enhance scalability? 👨‍🦰Candidate: Serverless architectures are inherently scalable. The platform automatically adjusts resources in response to traffic, scaling up during peak times and scaling down when demand decreases. This elasticity ensures that applications can handle varying loads without manual intervention, making it ideal for applications with unpredictable or fluctuating traffic patterns. 🧔🏽‍♂️Interviewer: Can you explain the cost benefits of the pay-as-you-go model in serverless? 👨‍🦰Candidate: With serverless, you only pay for the compute time you consume, unlike traditional architectures where you pay for pre-provisioned resources regardless of usage. This model is especially cost-effective for applications with variable workloads, as it eliminates the need to over-provision resources for peak usage. It also reduces waste, as you're not paying for idle servers. Summary: 1️⃣ Problem: Managing infrastructure and scaling resources efficiently. 2️⃣ Solution: Migrated to a serverless architecture, which automates infrastructure management, enhances scalability, and optimizes costs. 3️⃣ Impact: Reduced operational overhead, improved scalability, lower costs, and accelerated deployment cycles. #Serverless #CloudComputing #Scalability #CostOptimization #DevOps #AgileDevelopment #TechInnovation #AWSLambda #AzureFunctions #Efficiency

12

🚀 DE Interview 📢 Serverless Architecture ⌛ 1-Min-Read Benefits of Migrating to Serverless 👉🏽 🧔🏽‍♂️Interviewer: Can you explain the benefits of migrating to a serverless architecture? 👨‍🦰Candidate: Migrating to a serverless architecture eliminates the need for managing servers and infrastructure, allowing developers to focus on writing code. This shift not only reduces operational overhead but also enhances scalability, as serverless architectures automatically scale based on demand. Additionally, with a pay-as-you-go model, costs are optimized since you only pay for the resources you actually use. Serverless architectures also improve deployment speed, allowing for quicker releases and iterations. 🧔🏽‍♂️Interviewer: Could you elaborate on how operational overhead is reduced and how that impacts development? 👨‍🦰Candidate: In a serverless architecture, the cloud provider takes care of the underlying infrastructure, including server provisioning, patching, and scaling. This reduces the burden on the operations team, freeing them to focus on other tasks. For developers, this means they can spend more time on coding and innovation, rather than on infrastructure management. It also reduces the risk of downtime or performance issues related to server management, improving overall system reliability. 🧔🏽‍♂️Interviewer: How does serverless architecture enhance scalability? 👨‍🦰Candidate: Serverless architectures are inherently scalable. The platform automatically adjusts resources in response to traffic, scaling up during peak times and scaling down when demand decreases. This elasticity ensures that applications can handle varying loads without manual intervention, making it ideal for applications with unpredictable or fluctuating traffic patterns. 🧔🏽‍♂️Interviewer: Can you explain the cost benefits of the pay-as-you-go model in serverless? 👨‍🦰Candidate: With serverless, you only pay for the compute time you consume, unlike traditional architectures where you pay for pre-provisioned resources regardless of usage. This model is especially cost-effective for applications with variable workloads, as it eliminates the need to over-provision resources for peak usage. It also reduces waste, as you're not paying for idle servers. Summary:  1️⃣ Problem: Managing infrastructure and scaling resources efficiently.  2️⃣ Solution: Migrated to a serverless architecture, which automates infrastructure management, enhances scalability, and optimizes costs. 3️⃣ Impact: Reduced operational overhead, improved scalability, lower costs, and accelerated deployment cycles. #Serverless #CloudComputing #Scalability #CostOptimization #DevOps #AgileDevelopment #TechInnovation #AWSLambda #AzureFunctions #Efficiency

11

To (unit) test a microflow or not? Or, What (unit) test coverage of a Mendix app do you really need? Two weeks ago I wrote a post on how to make a microflow more testable. In this post we address criteria for which microflows you need to make a unit test. It doesn't make too much sense to test all microflows in your app. Of course, if you want you can, but to me that sounds similar as to waiting until new years eve to test a year change. If we want to select a subset of microflows that need unit testing we need to define criteria. Let us also agree that a good unit test of a microflow covers all possible outcomes. Many people use the complexity of a microflow as a selection criterium. At first sight this makes sense, because they are typically more risky. However, complex microflows are often long microflows. This means that they are hard to unit test (too many possible outcomes). As stated in my previous post, splitting them in submicroflows makes them easier to unittest. As a result, the complexity per microflow is then reduced as well. So, based on the above criterium you don't need to test these (simple) sub microflows anymore! Therefore my conclusion is that complexity is not always a very helpful criterium for unit testing. So what else can we use? In my conversation with developers and testers I noticed that the domain model is often overlooked as an important factor. Every domain model of a Mendix app has entities and attributes that are more important than others. If you look to the domain model from a testing perspective you can easily identify the most risky attributes and entities in your app. Even a simple microflow that changes an important attribute can contain an error that might lead to erronuous, important data in production. This type of errors can be prevented by writing and executing the appropriate unittests. In Mendix Studio Pro it is really easy to find all the microflows that use an entity or an attribute with the "find usage" function. So, my recommendation is to start identifying risky entities and attributes. Find then the microflows that act on this data and use this as a starting point to define a coverage goal of your unit tests. If you want more of these posts on LinkedIn. Please feel free to reach out to me if you want to discuss a particular question or topic related to (unit) testing a Mendix app.

30

3 commentaren

𝗗𝗼 𝘆𝗼𝘂 𝗳𝗶𝗻𝗱 𝗶𝘁 𝗵𝗮𝗿𝗱 𝘁𝗼 𝘀𝗽𝗶𝗰𝗲 𝘂𝗽 𝘆𝗼𝘂𝗿 𝗦𝗵𝗮𝗿𝗲𝗣𝗼𝗶𝗻𝘁 𝗣𝗮𝗴𝗲 𝘁𝗲𝘅𝘁 𝗶𝗻 𝘁𝗵𝗲 𝗿𝗶𝗰𝗵 𝘁𝗲𝘅𝘁 𝗲𝗱𝗶𝘁𝗼𝗿? Well these days are gone in a few weeks. Why? Microsoft is rolling out a update for SharePoint making it possible to use Copilot to help you. It will be possible to Rewrite text, Change tone of voice, Condense and Elaborate the text that you already have. I think Copilot for text can be useful but always make sure it is not only Copilot which is creating the text and check your text after it was created for false information. This update is coming people with a Copilot license in July 2024. Is your SharePoint fully structured? Do you want to automate the creation of sites so they’re all set up the same way, providing your users with a structured flow of information? If not, feel free to book an appointment with me, so we can discuss what is needed for your company. All the best, Paul Keijzers [MVP] #SharePoint #TextEditing #MicrosoftUpdate #AIWriting #CopilotUpdate

32

6 commentaren

I just published my first Medium post about integrating profile pictures from Azure Directory into Mendix! 🙂 📢 In this article, I covered: - The step-by-step process to fetch and display profile pictures from Azure Directory in a Mendix application. - Tips and best practices for seamless integration. Whether you're a Mendix developer or just curious about Azure Directory integrations, this post has something for you! I'd love to hear your thoughts and feedback. Feel free to connect and share your experiences with similar integrations. #Lantiqx #Mendix #AzureDirectory #Lowcode

34

5 commentaren

A short update on MendixCLIExtension: - We had to abandon the challenge to build this on OSX due to bugs in Studio Pro Mac version - Basic integration with Mendix-CLI to export and lint model - Basic UX ; the policies list is dynamically loaded; others are just stub - Renamed the extension and therefore the new location is at: https://lnkd.in/eCUxu3wn ; star it to follow its progress UX suggestions are more than welcome! #mendixcli #linting #mendix #extension

40

5 commentaren

Come to the book club! lets explore Facilitating Software Architecture Chapter 3: Decision processes at Scale https://lnkd.in/eNWRcP3q #SoftwareArchitecture #Decisions #powerBalance

5

Scheduling appointments is hard, so why not automate it with Wouter Penris? This week Wouter shares his ultimate hack for downloading .ics files in Native apps, using a combination of nanoflows and the new Microflow URLs feature, he gives a simple 4-step process that is easy to understand. In his piece, he demonstrates how his solutions can be adapted to securely implement downloads for any file type in a Native Mobile app. All done using a combination of standard microflow and nanoflow features - no custom JavaScript needed! Wouter is a Mendix Expert, MVP, and a senior principal expert at Ordina. A thought-provoking and insightful piece, Wouter has outdone himself again! #mendix #lowcode #lowcodeplatform #calandarfile #ics #scheduling #nativeapp #nativemobile #files #download #webdeveloper #webdev #appdeveloper #appdev #developercommunity #blog #howto

32

3 commentaren

What can you do with Copilot in classic Outlook: https://lnkd.in/egaJunEr

5

Doing a Copilot red review is probably one of the first step you want to do. Here is a good video that explains a few things you could do. https://lnkd.in/ePGNcy_8

1

1 commentaar