Zoran Horvat

🚀 𝗘𝗺𝗯𝗿𝗮𝗰𝗲 𝘁𝗵𝗲 𝗣𝗼𝘄𝗲𝗿 𝗼𝗳 .𝗡𝗘𝗧 𝟵 𝗳𝗼𝗿 𝗠𝗶𝗰𝗿𝗼𝘀𝗲𝗿𝘃𝗶𝗰𝗲𝘀 🚀 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 Comments

Business Requirements are the most important part of software development. I'm not sure which is 2nd: UX or Database... I always emphasize how important database structure is, and programming logic. But on days like yesterday, sometimes I think that User Experience might be the 2nd most important. I have an auto appraiser running through TRUEclaims - I think he's between 60-70 years old. I was running through it with him over the phone. (I obviously know the flow in detail - I designed it) He got to a part where most people have no trouble. But he was getting stuck when he was clicking a button. I think he hadn't scrolled down enough on the page and wasn't seeing the alert message pop up below when the button is clicked. I knew exactly where he was and I was visualizing what the problem could have been. That was the only possibility that made sense to me. So I verbally guided him through the process, while making a note down in Trello about the issue. There are an infinite number of ways of addressing User Experience problems. Most are time-consuming, expensive, unnecessary, and even NOT problem-solving. A former partner of mine probably would have freaked out and hired a UI designer to redo the whole design (notice I wrote "UI" designer, which is NOT the same as UX - completely different expertise). Why do I think he would have done that? Because for the software I worked with him on, he DID that. And others do that too. Later, I made an adjustment that when someone clicks it, it would scroll the user down on the page to ensure that the alert can be seen, regardless of where they were when clicking it. I knew this would solve the problem. Over a decade of intuition of UX optimization will do that. Simple solution that took me 1 minute. Problem solved. So many companies will adopt the mindset "well it only happened once" or "it's because of how he was using it" or "because he was older". I don't care why it happened. I don't want another person to have that same issue. Every time someone does, it creates confusion and the potential for them to stop using it after getting frustrated. Not worth it. Especially not worth it because I can usually figure out UX solutions FAST - easy ones. As evidenced by the fact that I ALWAYS get compliments of how easy to use the software I build is. So although Database is massively important - and your whole system will be a mess and clunky if it's not done well - I think UX, being the thing that can ruin a customer experience... might be more important.

6

9 Comments

Event Sourcing is still a relatively recent technique, and the "book" on best modeling practices isn't completely written. For what we know so far though, you do want to try to model such that your streams are short for a whole host of reasons. See https://lnkd.in/gTKXKCSh for more information on the "why", and also check out the "Closing the Books" pattern as a way to segment huge streams: https://lnkd.in/gm6NAkNz

19

8 Comments

Having some fun this weekend, while I recover from the flu :) First time trying TDD methodology with the well-known FizzBuzz Kata. Having to change traditional development mindset has been interesting and challenging. More to come.. Go check my Github, any feedback will be appreciated: https://lnkd.in/dEaEfxiE I left here a very interesting article about how to solve this Kata using TDD, from Codurance https://lnkd.in/drHJvCEE #TDD #improvement #testing #Kata #Codurance #motivation #challengeaccepted #selfdevelopment #helpfulBoyfriend Oscar Vidal Salazar ;)

8

This https://lnkd.in/eRUbTHYU thread makes me so sad. Without pointing fingers, this is a summary of the software development in most of the Italian companies - especially biggest - where development is just a cost center and there is zero culture about development. The few people who push for improving things are often isolated or surely not supported. We can certainly laugh about rutto.mp3 (burp.mp3) or the model picture released with the app but instead you can imagine if this is the overall quality, how secure can be a fintech app like this? What a waste of resources that could instead used to lead the country to be a better place instead. #bancaintesa #rutto #softwaredevelopment

14

4 Comments

Fundamentals of software architecture! Every decision in software architecture is a trade-off. If you think you found a solution that isn't a trade-off - it just mean you haven't identified what that trade-off is yet! https://buff.ly/3Mr50LT #saas #webdev #SoftwareArchitecture #ProductDevelopment

4

🚀 Say Goodbye to Null Checks with the Null-Conditional Operator (?.)! 👋 We’ve all been there—writing those endless if statements just to avoid a dreaded NullReferenceException! 😱 But guess what? C# has our back with the Null-Conditional Operator! 🎉 ✨ With this little gem, you can access nested properties without worrying about null values. If any part is null, the whole expression just evaluates to null—no more exceptions! 🔥 — 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 — 👉 Have you already used this operator in your projects? Let me know in the comments how it has improved your code!👇 #dev #developer #programming #programmer #microsoft #csharp #dotnet #aspnet #blazor #razor #mvc #webapi #api #vs #vscode #ef #efcore

169

7 Comments

I was curious about which countries in #EU plus #UK have the most #dotnet developing vacancies and how much are those, then asked #chatgpt and asked it to plot it as a 2d graph for me, this is the result! First of all, the ChatGPT job is fascinating, even it gives you the #python code of its plot, and on the other hand, seems #uk is the heaven 🙂 of #dotnet developers (based on ChatGPT statistics). It could be more interesting if we added other programming languages' statistics besides it, but my free GPT-4o has been finished 🥲 #microsoft #programmer

2

Episode 430 - How Short String Optimizations Work https://lnkd.in/ga5AkNvJ

72

Complementing the last post about .NET versions, here is a summary that works for any framework, language, etc. Don't get carried away by fads! Do you know what type of version to choose? Let's find out! LTS stands for Long-Term Support, while STS stands for Short-Term Support.  The main difference between them is the duration of support. 1) LTS versions are normally released in odd years and have free support and patches for 3 years. They are more stable and extensively tested, making them ideal for long-term projects that require stability and less frequent updates. You should choose a version, LTS if: - Need long-term stability and support. - Unwilling or unable to update the software frequently.    2) STS versions are typically released in even years and receive free support and patches for 18 months.  They include the latest features and improvements and are updated more frequently, which is great for those who want to access new technologies and tools quickly. Choose a version, STS if: - Want to use the latest features and are willing to update the software more frequently. - You are developing a project that can benefit from the latest innovations and improvements, even if this means a need for more regular updates. The choice between LTS and STS will depend on the specific needs of your project and your preference for stability or access to new features. If you have any questions or need any help to understand better, contact me privately.

1

Enea Jahollari presents a session titled “Migrating to Modern Angular” at #ngPolandConf. This talk focuses on practical steps and best practices for updating older Angular projects to the latest versions, covering key challenges and solutions encountered during the migration process. Enea will walk through important considerations such as handling deprecated dependencies, upgrading RxJS, implementing Angular’s latest features, and ensuring smooth transitions between Angular versions to maintain application stability and performance.

49

2 Comments

Spring cache providers: In the last post we learnt about how spring uses caffeine library to support caching. But why couldn't we just use hashmap. We could with limitations, that's exactly what "Simple" cache provider does Spring supports the following providers: JCache (JSR-107) (EhCache 3, Hazelcast, Infinispan, and others) Hazelcast Infinispan Couchbase Redis Caffeine Cache2k Simple This article is a 3 part series which digs deep into spring caching. Article link : https://lnkd.in/emskbmda #spring #caches

10

1 Comment

How can a software development agency bring most value to their client? It's simple. It's not easy, though: 1. Understand the client's pain point. Every client has an idea what they need. But this is not where you should start from. We need to start by understanding what is it that creates pain for our client. How to do this? Ask questions. A LOT of questions! 2. Understand the client's budget and timeline. Not all clients will be upfront about this. But through open communication you can explain that the reason you need this is to see what best you can do to eliminate their pain point and remain within the budget and timeline. Sometimes the best outcome can be that you eliminate 80% of the pain while remaining within the timeline and budget. Sometimes it will be to remove 100% of the pain, but exceed the budget by 50%. But the software development agency and the client need to have an open and direct conversation about this. 3. Cure the pain point within time and budget as agreed. If you've done the first two steps correctly, this one is simple - it is something the software agency does on a daily basis and really shouldn't have any problems with. #softwaredevelopment

5

🎯 Looking to Modernize or Build Software with .NET? 🚀 Let’s turn your vision into reality! 👨‍💻 With over 15 years of professional experience, I specialize in .NET software development—helping businesses reduce costs, modernize existing apps, and transition seamlessly to modern frameworks like Blazor and .NET Core. Whether you're dealing with outdated technology or looking to build high-quality, enterprise-grade applications from scratch, I’m here to help! Services I Offer: ✅ Custom Software Development ✅ Modernization of Existing Applications ✅ Migration to .NET Core and Blazor ✅ Cost Optimization through Efficient Development 💡 By leveraging my expertise and the FairPlayCombined framework—built on years of experience and real-world apps—you’ll get scalable, adaptable solutions that accelerate your time-to-market. 👉 Learn more about the FairPlay platform and its capabilities here: https://lnkd.in/eka-cN-w 🎯 Let’s work together to bring cutting-edge technology to your business! 📩 DM me to schedule a consultation and discuss how I can help. 🔗 Feel free to re-share this post with your network—it might help someone looking for modern software solutions! #Founders #Startups #Freelancing #OpenForBusiness

8

9 Comments

When a friend told me in 2012 that you could make an Android AND iPhone app in C#, and share 60% of the code, I thought he was just being silly: #Xamarin? 😆 😂 🤣 Then I tried it. And "it just worked" 🤯 6 years later, you could "nearly" share ALL the code 👇 https://lnkd.in/dRfKNAS It created a heated debate on hacker news proving the framework was now mature: https://lnkd.in/dcJttaU4 I began creating custom components to deliver apps for my clients. And then I decided to share them through github so everyone could create real apps with #XamarinForms 👇 https://lnkd.in/dQ-enMPM https://www.sharpnado.com/ Now it is still going strong as #dotnetmaui thanks to a compact MS team of talented people like Javier Suárez Ruiz, Shane Neuville, Gerald Versluis, Stéphane Delcroix, David Ortinau, Rui Marinho, Matthew Leibowitz, 🌶 Jonathan Peppers, ... BUT it also succeeded thanks to incredible open source projects and their dedicated maintainers like 👇 https://lnkd.in/dfbVnvsU (Tomasz Cielecki "the cheese baron") https://lnkd.in/dvnphvvN (Dan Siegel, Brian Lagunas) https://lnkd.in/dCzhmAAf (too much :) https://lnkd.in/drGKzFNG (Anais Betts) https://lnkd.in/dEhN8Sm2 (amazing touch effects by Vladislav Zhukov) https://lnkd.in/dmscE_Wz (@amay077) https://lnkd.in/dRaNMR5d (Claire Novotny) https://lnkd.in/dTePhsFH (Mihhail Maslakov) https://lnkd.in/dx75XQs2 (well it's not a project but it blew my mind when it came out, by Frank Krueger) And on top of all of that (more like under all of that :) thanks to the https://lnkd.in/dQCRrspH project! Special thanks to Miguel De Icaza and all the people that contributed and are still contributing to this day to such an incredible achievement❤️ So long #Xamarin, you silly monkey.

92

5 Comments

respond_to? in Ruby only includes public methods by default. You can pass true as the second argument to include private and protected methods. Also, what do you think about the one-line methods in #Ruby 3?

230

14 Comments