Antônio Falcão Jr

Mastering Next.js: The Ultimate Guide to Structuring Large-Scale Projects in 2024 https://lnkd.in/diu_RbCc

2

1 comentário

For some time I have been collecting resources and different point of view about the practice of #TDD. Sometimes it comes from academia, sometimes from the industry and both add thing to the mix. #TDD is a discipline that interacts with other parts of software development in a gentle manner and the myth of sacrificing it by speed has long been discussed and for some it is debunked already. The context is the one that weights the most. What still remains is the resistance of developers to incorporate the practice. The gentle introduction is not a comprehensive one, and it is not a completed one, it is what it is, just an introduction. https://lnkd.in/dCrM97f6

11

🚀 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝘁𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗼𝗳 .𝗡𝗘𝗧 𝟵 𝗳𝗼𝗿 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 🚀 With .NET 9, we're not just evolving — we're 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗶𝗻𝗴 the way microservices work to be faster, safer, and more efficient! This isn’t just an upgrade; it’s a 𝗴𝗮𝗺𝗲-𝗰𝗵𝗮𝗻𝗴𝗲𝗿 for modern development. ✨ Here’s why .NET 9 is a must-have for microservices: - ⚡ 𝗕𝗹𝗮𝘇𝗶𝗻𝗴 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 𝘄𝗶𝘁𝗵 𝗡𝗮𝘁𝗶𝘃𝗲 𝗔𝗢𝗧: Reduce startup times and boost responsiveness. - 🔗𝗦𝗲𝗮𝗺𝗹𝗲𝘀𝘀 𝗴𝗥𝗣𝗖 𝗖𝗼𝗺𝗺𝘂𝗻𝗶𝗰𝗮𝘁𝗶𝗼𝗻: Smooth and secure service interactions. - 🛠 𝗘𝗻𝗵𝗮𝗻𝗰𝗲𝗱 𝗠𝗼𝗻𝗶𝘁𝗼𝗿𝗶𝗻𝗴 𝘃𝗶𝗮 𝗢𝗽𝗲𝗻𝗧𝗲𝗹𝗲𝗺𝗲𝘁𝗿𝘆: Proactive monitoring for early issue detection. - 🌐 𝗟𝗶𝗴𝗵𝘁𝘄𝗲𝗶𝗴𝗵𝘁 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀:Optimized deployments with lower cloud costs. - 🛡 𝗦𝘁𝗿𝗼𝗻𝗴𝗲𝗿 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆: Built-in TLS and API security for peace of mind. - 🔄 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝗶𝗲𝗱 𝗠𝗮𝗶𝗻𝘁𝗲𝗻𝗮𝗻𝗰𝗲:Faster upgrades and cleaner code. 💡 Ready to unlock new possibilities? 👉 Check out our upcoming FREE Master Class by Shailendra Chauhan: Building .NET Microservices with Kafka at ScholarHat Register Now: https://bit.ly/48HUH09 Don't miss this opportunity to learn from an expert! #Microservices #DotNet9 #CloudDevelopment

7

4 comentários

Finish the Guess-Who Scrap CLI project written in Golang. Now, I can download and extract data on famous Brazilian people from Wikipedia, including specific states and cities. The data is saved in either Postgres or an in-memory SQLite database. In this project, I used Go as the programming language, GORM as the ORM, Cobra for the CLI, and Viper for the properties file. You can see more at https://lnkd.in/dvtTPi8R. Now, the next step is to work on the API project (https://lnkd.in/dUFwuXS8), using Quarkus, Langchain4J, Instruct Labs, etc to get the clues based on the data collected before, by the scrap project.

4

💡 Did you know? Named arguments in C# can make your code more readable and maintainable… …by letting you specify arguments by name, rather than relying on their order. Perfect for methods with many parameters or optional ones! 🙌 Instead of guessing the parameter order, you explicitly tell the compiler what each value is for! This is especially handy when you want to skip some parameters or improve code readability. 🧐 — Join 10.000+ subscribers! Stay in the loop with everything you need to know about .NET and Software Development ✉️ https://lnkd.in/dqrz6Tke 🛟 If you like this content, please, subscribe, comment and share — 💬 Question for you: Have you used named arguments in your projects? → Yes! They’ve saved my life. 😅 → Nope! I still use positional arguments. 🤔Drop your thoughts in the comments and share how you’d use them in your code! ⬇️ #dev #developer #programming #programmer #microsoft #csharp #dotnet #aspnet #blazor #razor #mvc #webapi #api #vs #vscode #ef #efcore

100

3 comentários

🤔 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

StructuralComparisons The `StructuralComparisons` class in .NET is part of the `System.Collections` namespace and is used to provide comparison services for collections that do not have a specific order, such as arrays. It offers two properties - `StructuralEqualityComparer` and `StructuralComparer` - that can be used to compare arrays and other collections based on their structure rather than their reference. Advantages 1.Structural Comparison: It allows for comparing the contents of two arrays or collections, treating them as equal if their structure and content are equivalent, rather than their references. 2.Ease of Use: The class provides a straightforward way to perform deep comparisons without needing to implement custom comparison logic. 3.Flexibility: It can be used with different data types, including nested collections, making it versatile for a variety of use cases. 4.Standard Implementation: By using StructuralComparisons, developers leverage a standardized implementation which can reduce potential bugs compared to custom comparison logic. 5.Support for Multiple Types: It can handle comparing arrays containing different types of elements, which can be helpful in dynamic programming situations. Disadvantages 1.Performance Overhead: Structural comparison may introduce performance overhead, especially for large collections, since it checks each element recursively. 2.Limitation to Arrays: Designed primarily for comparing arrays and flat collections, it may not be effective for more complex types or needs that require specialized comparison logic. 3.Implicit Dependencies: If the structures being compared contain nested objects that do not implement the appropriate equality members, the comparison might yield misleading results. 4.Use in .NET Core: As it is part of .NET Framework, usage in .NET Core and .NET 5+ may be limited or require a different approach. Users transitioning from .NET Framework to .NET Core should be mindful of this. 5.Lack of Advanced Features: It may not support advanced comparison features like filtering or custom sorting, requiring additional code to extend functionality. In this example, two integer arrays (array1 and array2) that contain the same elements in the same order are compared using StructuralComparisons.StructuralEqualityComparer, resulting in `true`. Conversely, array1 and array3,which contain the same elements but in different orders, are compared and yield `false`. The `StructuralComparisons` class provides functionality for comparing collections based on their structure and contents, making it suitable for scenarios where deep comparisons are necessary. However, developers should be aware of its performance implications, limitations in complex data types, and the potential need to implement custom logic for specific use cases, especially when transitioning to .NET Core. Want to know more? Follow me or connect🥂 Please don't forget to like❤️ and comment💭 and repost♻️, thank you🌹🙏

94

15 comentários

You probably know this, but you probably still don't do it enough 🤓 Keep your components small!🚀 This is one of the slides of my new #Angular Architectural patterns course that is filled with best-practices I've acquired from being involved in over 150 Angular projects. The course isn't ready yet, so stay tuned or subscribe on the simplified courses website.

13

1 comentário

New Post: Fixing the “Could Not Determine Recommended JdbcType for Class” Error in JPA

6

Discards "Discards" in .NET (specifically from C# 7.0 and onward) are a feature that allows you to specify that you want to ignore a value that would otherwise be returned or produced by an operation, such as a method call, tuple deconstruction, or pattern matching. The discard symbol is represented by an underscore (`_`). Advantages of Discards 1. Code Clarity: Discards indicate that you explicitly do not care about a value being returned. This can enhance readability, signaling to other developers that certain values are intentionally ignored. 2. Reduction of Unused Variables: When a method returns multiple values (such as in a tuple), using a discard allows you to ignore unwanted variables without the clutter of unused local variables and warnings. 3. Pattern Matching: In pattern matching scenarios, discards can simplify the code by avoiding the need to create unnecessary variables for types you don't care about. 4. Improved Performance: By not creating unused variables, your code could potentially allocate less memory, although the performance difference is usually negligible. 5. Clean Syntax: Discard syntax is straightforward and less verbose compared to declaring variables that you'll not be using. Disadvantages of Discards 1. Loss of Information: By using a discard, you may miss important information that could be useful for debugging or understanding the code. This is especially true if the discarded value might have been useful later. 2. Overuse Leading to Poor Practices: If not used judiciously, reliance on discards might lead to code that is hard to maintain or understand, as developers might ignore important return values too frequently. 3. Lack of Reflexivity: If you use discards in scenarios where one might reasonably expect to use those values later, it could lead to confusion or bugs in your code. 4. IntelliSense Limitations: In some IDEs or editors, you may not receive useful IntelliSense recommendations when using discards since they do not hold any values. 5. Potential for Bugs in Future Refactoring: Changes in method signatures might lead to a situation where previously discarded values are now important, which may not be immediately obvious to someone unfamiliar with the history of the code. Discards provide a useful and expressive way to cleanly handle cases where certain values are not needed. However, like any feature, they should be used thoughtfully to ensure code remains understandable and maintainable. Want to know more? Follow me or connect🥂 Please don't forget to like❤️ and comment💭 and repost♻️, thank you🌹🙏 #backend #fullStack #developer #Csharp #github #EFCore #dotnet #dotnetCore #programmer

90

22 comentários

Have you already tried DevExpress .NET MAUI components? Feel free to share your feedback in the comments Big thanks to, Javier Suárez Ruiz for a great overview! #maui #dotnetmaui #android #ios #devexpress #mobile

39

5 comentários

> When using Clean Architecture and DDD paradigms, separation of the persistence layer and the domain model layer is a primordial one. Primordial? Like, existing at or from the beginning of time; primeval? Who said so? Why? Is it because you don't know how to write SQL and program databases so you just have to download everything to memory objects? Oh, I think it is. https://lnkd.in/dy_GdZ4u

14

5 comentários

🚀 Exciting News for New Developers! 🚀 I'm very happy to share my new GitHub repository: https://lnkd.in/dMiwj-t2 This project is designed to help new developers understand data algorithms through a functional programming approach using Elixir. 🌟 To kick things off, I've implemented the classic Bubble Sort algorithm. This is a great starting point for anyone looking to grasp the fundamentals of sorting algorithms while learning Elixir's functional style. Feel free to check it out, contribute, and let me know your thoughts! Happy coding! 💻✨ #Elixir #DataStructures #Algorithms #OpenSource #Programming

43

1 comentário

Implementing custom dependency properties in WPF (+example). https://buff.ly/4g4IIfx #wpf #dotnet #mvvm #xaml #csharp #designpatterns #ui #windowsdev

2

🚀 Override Equals and GetHashCode in Records for custom comparisons 🚀 Did you know? In C#, records provide value-based equality out of the box! 🙌 But sometimes, you may need to compare records based on only specific properties. That’s where customizing Equals and GetHashCode comes into play. 🎛️ 💡 Why do this? Customizing these methods allows for partial comparisons in scenarios where only a subset of properties should determine equality. Perfect for when you only care about a few key details and want efficient comparisons! 🔍 In this example, two Product records are equal if they share the same Name—ignoring the Price property. Handy, right? — Join 9000+ subscribers! Stay in the loop with everything you need to know about .NET and Software Development ✉️ https://lnkd.in/dqrz6Tke 🛟 If you like this content, please, subscribe, comment and share — 💬 What’s a scenario where you’d need custom comparison logic? Drop your thoughts below! 👇 Let's chat about it! #dev #developer #programming #programmer #microsoft #csharp #dotnet #aspnet #blazor #razor #mvc #webapi #api #vs #vscode #ef #efcore

43

6 comentários

This Microservices bad, Microservices good, Microservices bad, Microservices good wheel is getting tiresome. What is the latest solution? Of course, DDD, I might have guessed. After all, DDD makes everything gooder 🙄 Here is what I do (and you, dear reader, can do whatever you want): - Stop calling them microservices. They are just *services* or, most likely, web services. - Apply a separate service when a separate service is needed to solve a problem that only a separate service can solve. That's it. But I'll give you an example: Example 1: Imagine you have an application with, well, users. And then you have an admin section that does the administration of and for that users. Obviously, the application and admin parts are updated for different reasons at different times and thus deployed separately. So you improve the admin part, but you obviously don't want to deploy the core app just for that. Obviously. In my mind, it makes perfect sense to have a separate application or separate service. I know, I know, you have your Kubernetes pods these days that make that invisible deployment magic, but still... Example 2: Export to PDF/Excel service. This is a running process that has chances to hang or run out of memory. You don't want to have this service as part of the core app because 1) deployment might kill this long-running process, 2) if it hangs, you don't want to take the rest of the application along, 3) you want to be able to scale it separately since it is infrastructure intensive operation, 4) you might want to change formatting in export, and that really has nothing to do with the app, so it is separate deployment axis, etc, etc. And so on. However, the article gives an example of inventory and stock: "If the inventory service changes its API or internal logic, the payment service might break. " Well, who's to say that you won't have any changes that go beyond just inventory and stock and touch on many other business entities you might have in your database? It's remarkable how DDD has become a solution to every problem, almost like a silver bullet. In my opinion, it's just a lame excuse not to think about the database in your system 🤫 Have a nice weekend everyone, this was my rant for today. https://lnkd.in/eS4au9QY

39

1 comentário

When DDD meets reality. Now imagine if you didn't even had to map onto objects at all, and just you know, use SQL for your business everything. Quote: In one of my first DDD projects, we’ve decided that we will follow the rule of — “Each architecture layer being fully decoupled”. Following this rule made us spend enormous amount of time on doing transformation between layers. That time was not invested into understanding the business better, that time was invested in following “the rule”. At the end everyone who was involved in the projected agreed, that this way of doing things was complicating our lives with little benefit. It simply did not worked in our context.

27

3 comentários