wario @ZVbytes

🚀 Just launched my new @FrontendMasters course: Complete Go for Professional Developers - 8 hours of real-world content - Uses Postgres, psql, Postman, migration libraries + more - Actually write unit + integration tests Learn Go by building a real application from scratch! Create scalable APIs, connect to Postgres with Docker, implement authentication, and build a production-ready backend with Go’s most powerful features. This is the most complete course i've ever created, and I truly think its the best way to start if you want to build with Go. 🫡 link below - I hope you all enjoy

FFmpeg makes extensive use of hand-written assembly code for huge (10-50x) speed increases and so we are providing assembly lessons to teach a new generation of assembly language programmers. Learn more here: github.com/FFmpeg/asm-les…

Doom now runs in @typescript types. What a journey this one's been.

🚀 useReducer > useState? When managing complex state logic in React, useReducer is your best friend! 💪 ✅ Better for state transitions ✅ Helps with performance optimizations ✅ Keeps logic structured & scalable Use it when useState gets messy! 🔥 #React #useReducer

The next version of Claude Engineer will come as a VS Code extension, get ready! 🔥 It has replaced all other AI tools for me. It's sooo good. Came up with lots of new ideas to improve coding capabilities.

i have 10,000 hours building todo lists i think i am finally ready for this job market

Ain't no way... #F1 #CanadianGP

Once upon a time.

🔥 Angular v18 is now available Excited to share the next milestone in the evolution of Angular: ‣ Experimental zoneless ‣ New home for developers on Angular.dev ‣ Material 3, deferrable views, built-in control flow are now stable ‣ More! blog.angular.io/angular-v18-is…

Cookies vs sessions for managing user session Cookies and sessions are both used to carry user login credentials and permissions over HTTP requests. 🔹 Cookies - Cookies typically have size limits of 4KB - Used to store user login credentials or permissions - Sent with each subsequent request by logged in user - Users can disable cookies in their browser, which may log them out 🔹 Sessions - Created and stored on the server-side - Server generates a unique session ID - Session ID links to a specific user session - Session ID can be sent back to client in a cookie, URL parameters, or HTTP headers - Can hold more data than cookies - Offer more security than cookies because session data is not directly accessed by the client – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/496keA7

𝗧𝗵𝗲 𝗗𝗼𝗺𝗮𝗶𝗻 𝗹𝗮𝘆𝗲𝗿 𝗳𝗼𝗹𝗱𝗲𝗿 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 𝘀𝗵𝗼𝘂𝗹𝗱 𝗲𝘅𝗽𝗿𝗲𝘀𝘀 𝗶𝗻𝘁𝗲𝗻𝘁. This is one of the essential concepts of screaming architecture. The Domain sits at the core of Clean Architecture. It's where you define your entities and the most important business logic. A few weeks ago, I was looking at a project I built many moons ago. The folder structure in the Domain layer bothered me. It was grouping classes by technical concerns instead of features. The symptoms of this are folders like: - Entities - Enumerations - Exceptions - Repositories - ValueObjects I'm sure you've done (or seen) this at some point. What's the problem with grouping by technical concerns? This folder structure doesn't tell you anything about the Domain. So, I reorganized the folders by grouping them by feature (or vertical slice). When you do this, domain concepts start appearing in the folder structure. The benefits of the new approach are: - Better cohesion - High coupling for a single feature - Low coupling between unrelated features If you've heard of Vertical Slice Architecture, this idea is similar. 𝗣.𝗦. If you liked this, you will love The .NET Weekly newsletter. Join 49,000+ engineers to improve your .NET and software architecture skills. Subscribe here → milanjovanovic.tech/?utm_source=Tw… What do you think about this approach?

keyboard_arrow_left Previous keyboard_arrow_right Next

𝗛𝗼𝘄 𝘁𝗼 𝗩𝗶𝘀𝘂𝗮𝗹𝗶𝘇𝗲 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲? When developing software, it is important to have a clear plan and understand how different system components will work together. Documentation and diagramming help us to achieve this by providing a 𝘃𝗶𝘀𝘂𝗮𝗹 𝗿𝗲𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗮𝘁𝗶𝗼𝗻 𝗼𝗳 𝘁𝗵𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗮𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁𝘂𝗿𝗲. This enables different stakeholders, like developers, testers, and clients, to have a common understanding of the software design. One of the preferred ways to visualize the software architecture is 𝘁𝗵𝗲 𝗖𝟰 𝗺𝗼𝗱𝗲𝗹, developed by @simonbrown, a software architect and author. The C4 model examines a software system's static structures, containers, components, and code. And individuals use the software programs we create. The C4 model consists of 𝗳𝗼𝘂𝗿 𝗹𝗲𝘃𝗲𝗹𝘀 𝗼𝗳 𝗮𝗯𝘀𝘁𝗿𝗮𝗰𝘁𝗶𝗼𝗻, which are represented by four different types of diagrams: 🔹 𝗖𝗼𝗻𝘁𝗲𝘅𝘁 (𝗟𝗲𝘃𝗲𝗹 𝟭): System Context diagram - This diagram shows the system in context, providing an overview of the system and its environment. The system here has the highest level of abstraction, and it shows the system under consideration as a box in the center, surrounded by its users and other systems that interact with it. These diagrams help provide a big-picture overview. 🔹 𝗖𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿𝘀 (𝗟𝗲𝘃𝗲𝗹 𝟮): Container diagram - This diagram shows the high-level components or services within the system and how they are connected. It shows each component as a box with its internal details abstracted away, separately deployable or executable. Containers can represent APIs, databases, file systems, etc. 🔹 𝗖𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 (𝗟𝗲𝘃𝗲𝗹 𝟯): Component diagram - This diagram shows the internal components of a container and how they interact with each other. Here, we can visualize abstractions in our codebase. For example, C # is an implementation class behind some interface. 🔹 𝗖𝗼𝗱𝗲 (𝗟𝗲𝘃𝗲𝗹 𝟰): Code diagram - This diagram shows the detailed structure of a single component or module, including its classes and their relationships. Most teams should, at the very least, produce and keep up-to-date 𝗰𝗼𝗻𝘁𝗲𝘅𝘁 𝗮𝗻𝗱 𝗰𝗼𝗻𝘁𝗮𝗶𝗻𝗲𝗿 𝗱𝗶𝗮𝗴𝗿𝗮𝗺𝘀 for their software system. If they are helpful, component diagrams can be made, but you'll need to figure out how to automate changes to these diagrams for long-term documentation needs. Image source: c4model #softwarearchitecture

Do you want to learn Domain-Driven Design? Here are 21 free resources to fast-track your journey. 🔥 1. What is an Entity - youtu.be/00tCda35Bvk 2. What is a Value Object - youtu.be/P5CRea21R2E 3. What is an Aggregate Root - youtu.be/0D3EB2jvQ44 4. Domain validation approaches - youtu.be/KgfzM0QWHrQ 5. Domain Events pattern - youtu.be/BimfDeDV4yU 6. The DDD Trilemma - youtu.be/eC7GMGIR4Gw 7. Repository pattern - youtu.be/h4KIngWVpfU 8. Specification pattern - youtu.be/rdY5ElleWKY 9. Unit of Work pattern - youtu.be/vN_j1Bs0ALU 10. Design a Rich Domain Model - youtu.be/1Lcr2c3MVF4 11. Smart Enums in C# - youtu.be/v6cYTcEfZ8A 12. Snapshot Pattern - youtu.be/HhZ4DtON404 13. Design a Rich Domain Model V2 - youtu.be/fO2T5tRu3DE 14. Strongly Typed IDs - youtu.be/LdrMdIabE1o 15. Fix Anemic Domain Model - youtu.be/6gwIDiUk2h4 16. Map DDD to Database - youtu.be/IlXnIe6p_Uk 17. Incomplete Aggregates? - youtu.be/cCnZJE0wEjY 18. Double Dispatch Pattern - youtu.be/wi_wsw5Gp6Q 19. Fix Broken Aggregates - youtu.be/BY8DHD6LitU 20. Organizing Domain Folders - youtu.be/R-XODYF2iBQ 21. DDD - Getting started - youtu.be/q74saF54w8I Hope these are helpful. Have an awesome day! --- P.S. Want to become a better software engineer? Each week, I send one piece of practical advice about .NET and software architecture. Join 49,000+ engineers: milanjovanovic.tech/?utm_source=Tw…

@abdallah_wario

This is what caused the chaotic and anticlimactic end to the event in Nyahururu. @THEJERE rightly left the line but somehow Boss didn’t. He then ‘demanded’ an official re-run. How now when this was technically a loss?

#angular #rxjs

Subaru boiz amejaribu kukimbisa vijana ya Golf akaua radiator, Wueh!

Karibu @Rupal_Racing waonyeshe BossTTRS bird of kangethe 😂😂😂😂 Subaru juu 🔥🔥🔥🔥 With a difference of 0.04 seconds gaddemit 🔥🔥🔥🔥 Send it if it dies it dies 🔥🔥🔥🔥🔥 Mc wa magari

Kamakosa kamefanyika.... Our very own Audi TT RS by aminzo takes it... Over and out.... Blessed week ahead Mc wa magari

🗣️ Lunin: “We had to take a risk with a player in the penalty shootout and we chose Bernardo Silva.”