Oleksandr Yushchak

Use the Toolbox Panel in Visual Studio 2022 The Toolbox panel is well-known to developers who previously worked with WinForms. It was used to hold controls. In modern application development, we can also use this panel to store code snippets that we frequently use across different projects. ✔️ To open the panel, click View -> Toolbox or use the Ctrl+Alt+X shortcut. ✔️ To add a snippet, select the desired lines of code and drag them into the panel. You can then rename the snippet for convenience. ✔️ After that, you can drag and drop the snippet into the relevant parts of your code in other projects and solutions. Make your coding faster with this simple Toolbox tip. If you found this helpful, please repost it 📢 #csharp #dotnet #softwaredevelopment #visualstudio

44

4 Comments

✨ First open source PR in years. First blog post ever. First time adding Cassandra support to Testcontainers-dotnet? Yep, Gavin de Kock just did all three. And it was smooth sailing. 🚢 From spotting a missing module to contributing it with ease, Gavin shares how friendly the Testcontainers OSS community is—and how simple it is to spin up Apache Cassandra for .NET integration testing using Docker. A fun read and a great reminder that open source is open for everyone. 🙌 Check out the post and try it yourself: http://spklr.io/6048APQn #Docker #Testcontainers #OpenSource #DotNet #ApacheCassandra #IntegrationTesting #DeveloperExperience

40

2 Comments

🚀 New episode of the Angular Master Podcast is live! The PRO Way to Use Angular – Learn from Roberto Heckers I had the pleasure of speaking with Roberto Heckers, a Freelance Senior Frontend Engineer from the Netherlands and author of Effective Angular. We explored what it really means to build scalable, maintainable Angular apps — and how tools like Nx, RxJS, NgRx, and Signals can transform your workflow. Here’s what we covered: ✅ Angular architecture patterns that work ✅ State management made simple ✅ Standalone APIs, directives, pipes, and dynamic components ✅ Real-world testing strategies with Cypress and Jest ✅ Performance, accessibility, internationalization ✅ Security and deployment automation tips And beyond code, Roberto shares: • How he stays motivated • What music he listens to while coding • What he’d be doing if not in tech 🎧 Available now on YouTube and all major podcast platforms 🔗 Links and resources are in the pinned comment Let’s talk Angular – the PRO way. #Angular #AngularMasterPodcast #EffectiveAngular #Frontend #WebDev #NgRx #RxJS #Nx #JavaScript #CleanArchitecture #Podcast

38

6 Comments

#ADRs (Architecture decision record) are like event sourcing. ADRs are written down decisions about architecture. Why did you chose React? Why not Angular? What were the Pro and Cons and why was that solution the winner? They make it easy for developers new to the company or new to the team to understand the decisions BEHIND the current tech stack and architecture. So they can make better decisions themselves. A side effect of ADRs is that you do not have the same discussion over and over again. How are they like Event Sourcing? ADRs have not the downside of normal documentation. Normal documentation is hard to keep in sync with reality. It's a tedious process, and nearly impossible if you did not find the right level of documentation (deep enough, but not too deep). ADRs do not change. They are write-one-read-often, they are read only. They don't need to be maintained, they are always correct. In this way they are like events in Event Sourcing. Those also do not change. And ADRs can be seen as an event, and to get an understanding of the current state of your architecture, you need to read and aggregate those ADRs, just like events in event sourcing. https://adr.github.io/

28

2 Comments

🤵 Tech Lead: "We will start using DDD in our project!" 🤔 Me: "Cool! Is it Domain-Driven Design?" 🤵 Tech Lead: "Yes!" 😃 Me: "Nice! What will we do then?" 🤵 Tech Lead: "First, we will extract interfaces from all our DAOs and call them ‘Repositories’. Then, we will create big objects using ‘Factories’ instead of services..." That was a real conversation between my tech lead and me back in 2009. We tried to introduce DDD into a project. It didn’t go well. The codebase became even more complicated. And we concluded that DDD was a waste of time and didn’t work. Years later, I see many developers falling into the same trap - thinking DDD is just about repositories, factories, and aggregates. ❌ DDD is NOT about your code. Just because you have tactical patterns doesn’t mean you’re doing DDD. ✅ DDD is about understanding and structuring complexity: 🔹 Finding the right language to communicate with business. 🔹 Breaking down a complex domain into meaningful parts. 🔹 Understanding relationships between those parts. 🔹 Prioritizing: What’s core? What’s supporting? What can we buy? 🔹 Clarifying who owns and implements each part. 🔹 And only THEN, applying tactical patterns in code. Did anyone else start with “coding” DDD before understanding the strategic part? 😃

437

66 Comments

🔥 ANGULAR DEVS — THIS WILL CHANGE HOW YOU USE OPENAPI 🔥 I have worked with many OpenAPI Client generators for years now. But unfortunately none of them fulfill all my needs. So I did what any sane person would do... I built my own. Tailored only for Angular. Packed with the features I always wished existed. And now — it’s open source 🚀 WHY YOU MIGHT WANT THIS: • Angular-first – NATIVE Angular code. Up to date with Angular coding standards • Actual Enums that actually make sense – no cryptic int objects or locked-in string objects • Clean method names – no more "ControllerNameMethodName" clutter • Multiple clients – each with its own HTTP interceptors and much more! Most TypeScript OpenAPI clients can work with Angular… …but ng-openapi was born inside Angular. That’s the difference. 📦 npm: https://lnkd.in/eaiT5piZ 🌐 Docs: https://ng-openapi.dev 💻 GitHub: https://lnkd.in/eWRz3H7h If you build Angular apps and touch OpenAPI, give it a spin. Break it. Improve it. Let’s make OpenAPI feel native in Angular. ng-openapi – Made with ❤️ by Angular Devs for Angular Devs #Angular #OpenAPI #TypeScript #Software #OpenSource #API

61

17 Comments

Is a .NET Developer the Most Important Part of a Team? 🤔💡 In the world of software development, every role plays a crucial part in building a successful product. But let’s talk about .NET developers specifically, are they the backbone of the team? ✅ .NET developers are often responsible for creating the core functionality of an application, ensuring scalability, security, and performance. ✅ They bridge the gap between front-end experiences and back-end logic, making sure everything runs smoothly. ✅ With the power of C#, ASP.NET, and cloud integrations, they enable businesses to build robust and scalable solutions. But here’s the reality: a team’s success isn’t about one role it’s about collaboration. 🚀 UI/UX designers create intuitive interfaces that keep users engaged. 🔗 DevOps engineers ensure smooth deployment and scalability. 🔍 QA testers catch bugs before they impact users. 📈 Project managers & product owners align technical work with business goals. So, while .NET developers are critical, no single role is the "most important." Instead, the best teams thrive when each member brings their expertise and works together toward a shared vision. What do you think? Is there a "most important" role in development teams, or is it all about teamwork? #DotNet #SoftwareDevelopment #TechTeams #Collaboration

21

8 Comments

Are Blazor developers really out there? Absolutely — but sometimes recruiters and teams are looking in the wrong place. I recently saw a discussion where people suggested hiring Angular or React developers for Blazor projects. On the surface, it makes sense: JavaScript frameworks share concepts like components, Shadow DOM, and state management. But here’s the twist, bringing habits from other frameworks can be just as much a challenge as a benefit. Back when .NET first launched, a colleague gave me advice that stuck with me for life: 👉 Don’t just carry old habits into a new technology. Learn it the right way from the ground up. That’s why I believe the strongest Blazor developers are often ASP.NET and C# developers, those already familiar with Razor, HTML, and CSS. Everything else is a bonus (and sometimes baggage). In this video, I share stories from my own journey, lessons from recruiters, and even how a seasoned React developer chose Blazor simply because it was faster to get the job done. 🎥 Watch the full video here: https://lnkd.in/dgZKFZUh 👉 Do you think JavaScript framework knowledge is a must for Blazor, or can it sometimes get in the way? I’d love to hear your take! #Blazor #dotnet #CSharp #WebDevelopment #Recruiting

48

14 Comments

🔹 Blazor – The Game-Changer for .NET Developers? 🔹 Ever wished for a JavaScript-free approach to building dynamic web apps? Blazor makes it happen! Imagine writing C# everywhere in the frontend & backend without switching contexts. Less complexity, more productivity. 💡 Why Blazor is Winning Hearts? » WebAssembly Power – Run .NET code directly in the browser. » Code Reusability – Share logic across web & desktop apps. » No More JS Fatigue – Focus on C# and .NET without juggling JavaScript frameworks. Blazor isn't just an alternative, but it’s a paradigm shift. 🚀 Thinking of switching to Blazor? Let’s discuss how it can scale your web applications at The One Technologies #Blazor #DotNet #WebApps #CSharp #TechTrends

20

🚨 𝗦𝗵𝗼𝗽𝗶𝗳𝘆 𝗷𝘂𝘀𝘁 𝗱𝗿𝗼𝗽𝗽𝗲𝗱 𝗮 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 𝘄𝗲’𝘃𝗲 𝗮𝗹𝗹 𝗯𝗲𝗲𝗻 𝗵𝗮𝗰𝗸𝗶𝗻𝗴 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿 𝗳𝗼𝗿 𝘆𝗲𝗮𝗿𝘀: 𝗔𝗱𝗱-𝘁𝗼-𝗖𝗮𝗿𝘁 𝗟𝗶𝗺𝗶𝘁𝘀 — 𝗮𝗻𝗱 𝗶𝘁’𝘀 𝗳𝗶𝗻𝗮𝗹𝗹𝘆 𝗻𝗮𝘁𝗶𝘃𝗲. Up until now? You had three bad options:  • Write fragile JavaScript that breaks every time the wind changes  • Use line item scripts (only on Shopify Plus)  • Or duct-tape it together with a third-party app Now? It’s built in. You can limit how many items customers add to their cart. Per product or across your entire store, with zero hacks and no extra tools. ✅ Works out of the box ✅ Works for everyone (not just Plus) ✅ Works like it always should have Why this actually solves real problems:  • Blocks bots and resellers from wiping you out during a drop  • Hides your real inventory from people who love to snoop  • Reduces over-ordering and return risks, before checkout even happens 🎁 𝗕𝗼𝗻𝘂𝘀 𝘁𝗶𝗽: Some stores already have this enabled by default. If you’ve suddenly noticed a “20 per item” cap, it’s not a bug. It’s Shopify quietly protecting your store based on past order data. Smart move. So? 👀 Are bots snapping up your stock during drops? 🛑 Tired of customers over-ordering and returning half of it? 🤖 Not sure if this setting’s already live on your store? Go check it out: 👉 Shopify Admin → Settings → Checkout → Add-to-cart limit Shopify might’ve already flipped the switch for you. No scripts. No hacks. No extra apps. #shopify #ecommerce #productupdate #cartlimits #ux #leaddeveloper #growthtools

64

3 Comments

The last five recommendations in the Angular performance series are out! 🤩 This is the part that I initially thought would be straightforward, but ended up taking me longer to write. I hope you enjoy the read and find some valuable insights to apply to your Angular projects! The article covers: ✔️ Switching to the new Vite + esbuild build system ✔️ Optimizing build configurations ✔️ Keeping Angular dependencies healthy and up-to-date ✔️ Profiling apps with Angular DevTools and browser DevTools ✔️ Measuring real-user performance with Core Web Vitals and CrUX 🔗 Read Part 4: https://lnkd.in/eWJPkdWw 🌎 Lee la versión en español en el primer comentario

51

2 Comments

How you can get some Async in PHP using Symfony HTTP Client or Guzzle: I published a video on a small refactoring on our own Tideways GmbH codebase to use parallel HTTP requests to reduce time spent talking to a microservice. https://lnkd.in/eAEsmtB7 #php #symfony

21

3 Comments

Angular released v20.0.0-next.6 version on April 9th, pushing more stable Signal APIs! It means the whole rxjs-interop package is no longer in developer preview! While not merged yet, we can expect afterNextRender changes to be merged too, while afterRender will be removed.

938

28 Comments