Diego Bevilaqua

Is Node.js still the go-to choice for developers, or is it losing its appeal? This question has sparked quite a discussion lately. I came across an insightful article that really breaks down the current landscape of Node.js and its popularity. It highlights how shifting trends and the emergence of alternative frameworks influence its standing in the developer community. Reflecting on my own experiences, I remember when Node.js was the hot topic in developer circles, with everyone eager to explore its potential. However, as new technologies pop up, it's crucial to stay informed and adaptable. This article tackles the very idea that sometimes, what is widely popular might not be the best fit for every project. The key takeaway here is the importance of evaluating tools based on the specific needs of your project, rather than following trends blindly. Keeping an open mind to alternatives can lead to more effective solutions tailored to business goals. What’s your take on the current standing of Node.js? Let's discuss! https://lnkd.in/gnZCY6Au

1

🤔 How structure Program.cs on ASP.NET Core Minimal API? Guilherme Ferreira gives the answer to this question in his very well crafted video https://lnkd.in/da5d6FFd #verticalslicearchitecture #aspnetcore

8

1 comentário

Do you want to use a framework or to be used by it? Do you want to create a project from a behavior driven development, converting the requirements in tests and generating the features from the tests? Do you also want to do it with PHP? This is the #book: #PHP Web Development with #Laminas: Build a fully #secured and functional e-commerce application with PHP using the Laminas #framework https://lnkd.in/dE9562m3 Packt PHP The Linux Foundation Laminas Project

7

Our own J. Ivan Duarte speaking at Drupal 4 Gov #DrupalGovCon about Single Directory Components (SDC). I liken #SDC to object oriented programming (OOP) for front-end #drupal theming. But, this is a more detailed explanation. Single Directory Components (SDC) is a modern approach to managing frontend assets in Drupal, particularly in the realm of component-based development. This concept revolves around the idea of bundling all the assets required for a specific component—like CSS, JavaScript, and templates—into a single directory. Each component lives in its directory, making the structure more modular, organized, and easier to manage. Benefits: Enhanced Modularity: By grouping all component-related assets together, SDC fosters a modular approach to development. This modularity allows developers to build, test, and maintain components in isolation, leading to cleaner, more manageable code. Improved Maintainability: Since all files related to a component are stored together, understanding and maintaining the codebase becomes easier. Developers can quickly locate the assets they need to modify without sifting through multiple directories. Reusability: Components structured using SDC are more portable and reusable across different parts of a Drupal site or even across different projects. Since each component is self-contained, it can be easily copied or shared without worrying about missing dependencies. Scalability: As a Drupal project grows, the number of components can increase significantly. SDC makes it easier to scale the frontend architecture by keeping the growing number of components organized and encapsulated, preventing the codebase from becoming overwhelming. Consistency: SDC encourages a consistent structure for components across the project. This consistency makes it easier for teams to collaborate, as everyone follows the same patterns and conventions. It also reduces the learning curve for new developers joining the project. Better Collaboration: With SDC, frontend developers can work more independently of backend developers. The clear separation and encapsulation of components allow for more parallel development workflows, improving team efficiency. Easier Debugging and Testing: When all related assets are in one place, identifying and fixing issues becomes more straightforward. Developers can focus on a single directory when debugging, which speeds up the process. Similarly, testing individual components is simplified since all necessary files are readily accessible.

36

1 comentário

🚀 New Article🚀 "Modern Angular State Management with Signals" 🛠️📈. Dive deep into the evolution of state management in Angular, from models and the redux pattern to BehaviorSubject services and the innovative use of signals. State management has always been a hot topic, and in this article, I share: ✅ A comprehensive history of state management in Angular ✅ Best practices and insights from my journey ✅ How to leverage the power of signals for cleaner, more efficient code 🔍 Curious about how signals can simplify your state management? Check out the full article here and transform the way you handle state in your Angular applications! #Angular #StateManagement #WebDevelopmen #FrontendDevelopment #SoftwareEngineering #BestPractices https://lnkd.in/gg2K28HZ

57

1 comentário

💡 Mapping Fields from Different Structures in a Collection – A Liferay Trick Recently, I had an insightful conversation with Daniel Dias that reminded me of a handy Liferay trick I picked up from Anderson Souza a while back. Now, I’m sharing it with you! Liferay's no-code functionalities allow us to create collections of specific structures to display content dynamically. You can configure the order, filters, and other settings easily using the Display Collection feature. (By the way, I posted a YouTube video about this https://lnkd.in/et848ES7. Let me know if you'd like it in English! 🎥) But here’s the question: Can we map fields from different structures into one collection? For example, can I create a banner fragment for my homepage that showcases featured news, events, and blogs, all from different structures—without using FreeMarker, just with simple drag and drop? At first, I thought it wasn’t possible. But guess what? It is! Here’s the trick: 1. Create the collection using a single structure. 2. Add your banner fragment to the page and configure it with the Display Collection, mapping the fields as needed (as shown in the YouTube video). 3.Once everything is set up, switch the collection to multiple structures and add your other content types. 4. Now, if you go back to the page, you’ll see two things: - All content from the different structures will be displayed. - However, if you try to check the mapping again, it will appear as unmapped and the structure fields won’t show as options. That’s why it’s crucial to configure the fields first before switching to multiple structures. ❗ Important: Ensure the fields you're using have the same field references across all structures. This is essential for everything to work properly. To guarantee this, use the structure fieldset. By the end of the process, you’ll have a dynamic display collection pulling content from different structures without writing a single line of code! If this wasn’t possible, we’d have to manually code it using FreeMarker to fetch the articles, extract the fields, and parse everything—along with all the other dev work that comes with it. Did you know this trick? #liferay #liferayDXP #noCode #dxp #fragments #collections

28

4 comentários

Is always a good ideia review some basic concepts mainly when you are thinking in a microservices architecture, this course does this very well, during the course I reviewed some important concepts that you need to take into consideration to build applications in a microservices architecture. #microservices #Hexagonal archicteture #gRPC #Service discovery #API gateway #Oauth #CQRS #BFF #Saga pattern #Health Check #Kubernetes #APM #Azure Devops

15

1 comentário

Hello guys, TomeTracker is a simple API made with C# and ASP.NET Core to manage book circulation from a library, it was a challenge made by Luis Felipe from LuisDev Consultoria e Treinamentos em Tecnologia on our mentoring program. I built it with C# and ASP.NET Core, implementing Clean Architecture and Unit Tests using xUnit, Moq and Bogus to generate mocking testing data. Also, I've used FluentValidation to validate fields when inserting. EntityFramework was used for persistence with SQL Server Database, using the Code-First approach to manage database creation. MediatR was used to handle the uses for this project using CQRS. There is more room for improvement, and I'm already planning the next features I will post here as I finish implementing them. #csharp #asp.net #dotnet #dotnetcore #microsoft

40

1 comentário

Start your journey to become a skilled Node.js developer with our detailed guide! This roadmap is designed to take you from the basics to advanced topics, making sure you’re ready for the fast-paced world of server-side JavaScript development. We begin with a strong foundation, introducing you to Node.js and npm (Node Package Manager). You’ll learn how to use Node.js’s event-driven, non-blocking I/O model and manage project dependencies with npm. Next, we cover important skills for Node.js developers. You’ll learn error handling to build strong applications and dive into asynchronous programming to make the most of Node.js’s performance. The roadmap then teaches you practical skills. You’ll work with file systems, create and use APIs, and interact with different databases. These are essential for building real-world applications that handle data well and connect with external services. We also explore command-line applications, expanding your skills beyond web development and opening new opportunities for automation and system-level programming. To complete your skill set, we cover testing to ensure your code is reliable, logging techniques for debugging and monitoring, and modular development practices for creating scalable applications. Whether you’re new to coding or looking to improve your skills, this roadmap is designed to help you progress. By the end, you’ll be ready to take on complex Node.js projects and stand out in backend development. Ready to boost your career as a Node.js developer? Start our roadmap and transform your coding future today! #NodeJS #WebDevelopment #JavaScript #BackendDevelopment #CodingSkills #TechCareers #SoftwareEngineering #FullStackDevelopment #ProgrammingTips #LearnToCode #DevOps #API #DatabaseManagement #ContinuousLearning #TechSkills #CodeNewbie #JavaScriptFrameworks #ServerSideProgramming #NPM #AsyncProgramming

286

18 comentários

New video published about Standalone Components in Angular - in Portuguese. I'm starting a new playlist showcasing Modern Angular. - Nova playlist no canal sobre Angular Moderno! Aprenda sobre standalone components no angular, e como migrar uma aplicação com angular clássico para angular moderno. https://lnkd.in/eXd-JFxq #angular #angularModerno #modernAngular

755

11 comentários

Ever written Node.js code that feels like it's stuck in a loop? You send an API request and wait for a response, but your program just keeps running along without a clear end in sight. This asynchronous dance can be a real head-scratcher, especially when you need tasks to finish within a specific timeframe. Before jumping on solutions let's understand "Why do we need tasks to finish within a specific timeframe?" 𝗣𝗿𝗲𝘃𝗲𝗻𝘁 𝗕𝗹𝗼𝗰𝗸𝗶𝗻𝗴: Without deadlines, your program might wait indefinitely for a slow response, blocking other tasks from executing. 𝗨𝘀𝗲𝗿 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲: If responses take too long, users experience delays and frustration. Setting deadlines ensures a more responsive application. 𝗘𝗿𝗿𝗼𝗿 𝗛𝗮𝗻𝗱𝗹𝗶𝗻𝗴: Timeouts can trigger errors, alerting you to potential issues with external services like APIs. 𝗣𝗿𝗲𝗱𝗶𝗰𝘁𝗮𝗯𝗶𝗹𝗶𝘁𝘆: Deadlines help maintain control over your code's execution flow, making it easier to predict behaviour and troubleshoot problems. Node.js shines with its asynchronous nature, handling multiple tasks concurrently for optimal efficiency. But when dealing with external services like APIs, we often need to guarantee a response within a certain time limit. Think of fetching user data – you need that information before proceeding, but the API might take its sweet time responding. Feeling stuck in coding limbo? Not anymore! Here are some proven tools you can rely on in Node.js to establish order in the chaos of asynchronous tasks: 𝟭. 𝗣𝗿𝗼𝗺𝗶𝘀𝗲𝘀 𝘄𝗶𝘁𝗵 𝗧𝗶𝗺𝗲𝗼𝘂𝘁𝘀: Promises allow you to chain asynchronous operations, but what happens if one gets hung up? We can leverage timeouts within promises. If the operation doesn't complete within the set timeframe, an error is thrown, preventing your code from getting stuck. 𝟮. 𝗔𝘀𝘆𝗻𝗰/𝗔𝘄𝗮𝗶𝘁 𝘄𝗶𝘁𝗵 𝗧𝗶𝗺𝗲𝗼𝘂𝘁𝘀: Similar to promises, you can pair setTimeout with async/await functions to define a maximum wait time for asynchronous operations. 𝟯. 𝗧𝗵𝗶𝗿𝗱-𝗣𝗮𝗿𝘁𝘆 𝗟𝗶𝗯𝗿𝗮𝗿𝗶𝗲𝘀: Libraries like bluebird or async offer even more control over asynchronous operations. These tools provide functionalities like timeouts and cancellation capabilities, allowing for fine-tuned management. By implementing deadlines for asynchronous operations, you ensure your Node.js applications run smoothly and avoid unexpected delays. See the attached code snippet of Promises with Timeouts. #javascript #NodeJS #AsynchronousProgramming #APIs #codingtips

18

🔍 Exploring Node.js: Small Steps, Big Impact 🔍 In today's fast-paced tech landscape, continuous learning is key. That's why I've dedicated myself to practicing Node.js, honing my skills in backend development through incremental progress. Here's how I'm approaching it: 🔹 **Daily Dives into Code**: Every day, I carve out time to immerse myself in Node.js, exploring its functionalities, and tackling coding challenges. By committing to regular practice, I'm steadily building my proficiency and confidence. Though my journey with Node.js may be in its early stages, the impact of these small steps is already tangible. With each line of code written and every challenge overcome, I'm inching closer to mastery. Join me in embracing the power of small steps in our pursuit of excellence in Node.js and beyond! #NodeJS #BackendDevelopment #ProgrammingJourney #ContinuousLearning #TechCommunity #CodeNewbie Let's connect on LinkedIn and embark on this journey together:

2

1 comentário

Moving My Blazor WebAssembly Blog to Hashnode Headless CMS #dotnet #blazor #hashnode

7

2 comentários

From time to time there are people who question the norm, and go against what we believe, and that is okay. By all means always be ready to question what we do, that is how we grow, but... Here is the thing: TDD does work. It doesn't just work, it is the only thing that works well for complex enough systems. The problem with the Hill Climbing algorithm analogy is that TDD isn't blindly optimising and isn't starting from a random point. When you do TDD you are very deliberate with your next moves, and the reason it is better than up front designing, is because it adds information through the iterative process, but also keeps the information we get by thinking ahead of time. It's not instead of, rather along with.

8

53 comentários

You might be missing this awesome pattern in your Node.js applications... Hey fellow devs! 👋 Today I want to share a cool pattern we're using at iprep.ai that's making our code so much cleaner and more scalable: Event Emitters in Node.js. Here's the scenario: We needed a way to trigger various actions after an interview ends, without cluttering our main interview logic. Enter event emitters! Why is this awesome? 🚀 1/ Separation of Concerns:- Your main code just emits an event. It doesn't need to know or care about what happens next. 2/ Scalability:- Need to add more post-interview actions? Just update the event handler without touching the main code. 3/ Testability: It's super easy to test your event handlers in isolation. Event emitters are like a secret weapon for building maintainable Node.js apps. They've been a game-changer for us at iprep.ai, especially as our app grows more complex. Have you used event emitters in your projects? What's your favorite Node.js pattern for handling such complex workflows? Let's chat in the comments below 👇🏾 #NodeJS #JavaScript #WebDevelopment #CodingTips #iprepai #codersgyan

58

3 comentários

NestJs Microservices I tell my colleagues why I love #nestjs, it is because it makes really complex stuff really easy! Like I so much love the way the encapsulate things, e.g., with the modules, apps, lib, microservices, etc. Today, I will be discussing nestjs Microservices. As a distributed systems developer, I should get introduced to a lot of technology and their associated mindset. To take the learning home I usually find some handson so that it sticks. To see it quickly work I use the language I am most conversant with, #Javascript, using the #Nodejs runtime. Thus, I decided to look at how nestjs does microservices, and I found out that they create a very beautiful abstraction that enables you to communicate between microservices using the concept of #transporters. These transporters support both form of message styles: #request-response and #event-based. With this, you can switch from one transporter to the other. Okay, what are these transporters? A transporter is a medium via which our microservices communicate with each other. Example of such a medium can be a Queue, an event broker, or TCP. Basically the transporter fall in two categories: #point-to-point and #broker-based. Examples of point-to-point transporters is gRPC and TCP. While for broker-based, are the Kafka, Redis, RabbitMQ, NATS, etc. To understand the nestjs Microservices, we have to understand that there are two sides to every communication: The requestor/publisher and the responder/subscriber. To be a subcriber/responder, the microservice must setup connection before starting up, which again nestjs provides a simple Api, the #createMicroservice method of the #NestFactory. Similarly, to be a publisher/requestor, the microservice uses the #ClientProxy interface, which enables it to publish messages. This interface provides these two methods: #send() (for request-response messaging) and #emit() ( for event-driven messaging) which enables us to communicate with a remote microservice. One beautiful thing I like about the nestjs Microservices abstraction is that, it is not limited to working with only nestjs or even nodejs application, i.e., it is technology agnostic, but it can work with any other microservices by using the Serialization and Deserialization Api it provides, making communication very transparent! Another side points it helps take care of the robustness of your application. As always happy learning 😊. #microservices #ddd #softwareengineering #software #nestjs #nodejs #development #softwarearchitecture

3

🚀 My First Node.js Script: Hello World! 🚀 When I first started exploring Node.js, I wanted to see how it works, so I decided to create the classic "Hello World" script. It was a simple start, but it helped me understand how JavaScript runs on the server side. Here’s how I did it: 1. Installing Node.js I downloaded Node.js from nodejs.org and got it set up on my system. Creating the script I opened my code editor and created a file named app.js. I added this line of code: console.log('Hello, World!'); 2. Running it in the terminal In the terminal, I navigated to the folder where I saved app.js and ran: bash node app.js And there it was – Hello, World! printed in my terminal! 🎉 Even though it’s a simple script, seeing it work gave me a sense of how powerful Node.js is. It’s fast, non-blocking, and ideal for building scalable applications. This small experiment marked the beginning of my journey into server-side JavaScript, and I’m excited to dive deeper into it. If you're just starting, this is a great way to get your feet wet. Let me know if you’ve tried it or if you have any tips for working with Node.js! 😊 #Nodejs #WebDevelopment #JavaScript #Coding #HelloWorld #LearningJourney

11

3 comentários