home.social

Search

46 results for “mortylen”

  1. In industrial software, one thing is often handled with great precision: what the operator should see on the screen. Alarms, trends, graphs—everything is neatly defined.

    But the longer I work on such systems, the more I see that the real problems aren’t there. They lie in the tools used in the background for maintenance, diagnostics, configuration, and system expansion.

    And that’s exactly where precise requirements are often missing. Not because anyone has failed, but because these things can’t be designed perfectly in advance. Many only become apparent during actual operation. I described this briefly in my article; I hope it inspires you 😉

    🔹 mortylen.hashnode.dev/when-a-p

    #softwaredevelopment #programming #softwarearchitecture #requirements #industrial

  2. In industrial software, one thing is often handled with great precision: what the operator should see on the screen. Alarms, trends, graphs—everything is neatly defined.

    But the longer I work on such systems, the more I see that the real problems aren’t there. They lie in the tools used in the background for maintenance, diagnostics, configuration, and system expansion.

    And that’s exactly where precise requirements are often missing. Not because anyone has failed, but because these things can’t be designed perfectly in advance. Many only become apparent during actual operation. I described this briefly in my article; I hope it inspires you 😉

    🔹 mortylen.hashnode.dev/when-a-p

  3. How to react to SQL Server data change notifications in real time using SqlDependency and Service Broker — no polling, no timers, just push notifications sent directly from the database to your .NET application.

    I hope this helps and inspires you 😉

    Code: github.com/mortylen/sql-depend

    #sql #sqlserver #database #programming #csharp #dotnet #sqldependency

  4. The fourth article in the Architectural Decisions series is out now ✅

    This time, it’s about why simplicity often wins over unnecessarily complex architecture in practice. Why it’s better to start simple, avoid premature optimization, and when it actually makes sense to introduce complexity.

    If you’re dealing with system architecture or thinking about better technical decisions, it might give you a new perspective, maybe help, maybe inspire. 😉

    🔹 mortylen.hashnode.dev/why-simp

    #programming #cleancode #softwarearchitecture #softwaredevelopment #decision #refactoring #devops

  5. Have you ever found yourself in a situation where you wanted to do things “the right way”… only to end up complicating your life? 🤔

    In a new article from the Architectural Decisions series, I explore how good intentions lead to overengineering.

    If you’re building things “just in case,” you might be creating problems that don’t even exist yet.

    I hope this article helps and inspires you.

    🔹 mortylen.hashnode.dev/when-goo

    #programming #cleancode #softwarearchitecture #softwaredevelopment #decision #overengineering

  6. I’ve written a new article about software anti-patterns.

    I focused on why they happen and how to recognize common ones like God Object, Spaghetti Code, and tight coupling.

    If you’ve ever felt like code is getting harder to change for no obvious reason, this might resonate 🧐

    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/when-cod

    #cleancode #architecture #programming #refactoring #softwaredevelopement

  7. I’ve written a new article about software anti-patterns.

    I focused on why they happen and how to recognize common ones like God Object, Spaghetti Code, and tight coupling.

    If you’ve ever felt like code is getting harder to change for no obvious reason, this might resonate 🧐

    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/when-cod

    #cleancode #architecture #programming #refactoring #softwaredevelopement

  8. I’ve written a new article about software anti-patterns.

    I focused on why they happen and how to recognize common ones like God Object, Spaghetti Code, and tight coupling.

    If you’ve ever felt like code is getting harder to change for no obvious reason, this might resonate 🧐

    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/when-cod

    #cleancode #architecture #programming #refactoring #softwaredevelopement

  9. I’ve written a new article about software anti-patterns.

    I focused on why they happen and how to recognize common ones like God Object, Spaghetti Code, and tight coupling.

    If you’ve ever felt like code is getting harder to change for no obvious reason, this might resonate 🧐

    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/when-cod

    #cleancode #architecture #programming #refactoring #softwaredevelopement

  10. I’ve written a new article about software anti-patterns.

    I focused on why they happen and how to recognize common ones like God Object, Spaghetti Code, and tight coupling.

    If you’ve ever felt like code is getting harder to change for no obvious reason, this might resonate 🧐

    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/when-cod

  11. I’ve written a new article about software architecture. Focusing on why most decisions aren’t about finding the “best” solution, but about understanding trade-offs.

    I tried to keep it practical and easy to follow, so it can help with real-world decision-making.

    If you’re dealing with architecture, it might offer a slightly different perspective 🧐
    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/most-sof

    #architecture #systemdesign #SoftwareDevelopement #decision #software #programming

  12. I’ve written a new article about software architecture. Focusing on why most decisions aren’t about finding the “best” solution, but about understanding trade-offs.

    I tried to keep it practical and easy to follow, so it can help with real-world decision-making.

    If you’re dealing with architecture, it might offer a slightly different perspective 🧐
    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/most-sof

    #architecture #systemdesign #SoftwareDevelopement #decision #software #programming

  13. I’ve written a new article about software architecture. Focusing on why most decisions aren’t about finding the “best” solution, but about understanding trade-offs.

    I tried to keep it practical and easy to follow, so it can help with real-world decision-making.

    If you’re dealing with architecture, it might offer a slightly different perspective 🧐
    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/most-sof

    #architecture #systemdesign #SoftwareDevelopement #decision #software #programming

  14. I’ve written a new article about software architecture. Focusing on why most decisions aren’t about finding the “best” solution, but about understanding trade-offs.

    I tried to keep it practical and easy to follow, so it can help with real-world decision-making.

    If you’re dealing with architecture, it might offer a slightly different perspective 🧐
    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/most-sof

    #architecture #systemdesign #SoftwareDevelopement #decision #software #programming

  15. I’ve written a new article about software architecture. Focusing on why most decisions aren’t about finding the “best” solution, but about understanding trade-offs.

    I tried to keep it practical and easy to follow, so it can help with real-world decision-making.

    If you’re dealing with architecture, it might offer a slightly different perspective 🧐
    I’d really appreciate any feedback.

    🔹 mortylen.hashnode.dev/most-sof

  16. Last year, I wrote two articles about self-hosted Git systems, specifically Gitea. One covers the installation on your own server, while the other expands on it with workflow actions and CI. Maybe this will be helpful to someone. You can check them out below:

    🔹 mortylen.hashnode.dev/easy-sel
    🔹 mortylen.hashnode.dev/gitea-se

    #git #gitea #ci #CI_CD #continious_integration #ubuntu #selfhosted #Csharp

  17. Today, a lot of technology and architecture decisions start with “let’s ask AI”.

    That’s why I added a new feature to my side project, Stack Compass Guide. Every recommendation now also includes an AI prompt for a second opinion.

    The goal is simple: not only provide guidance for topics like “Monolith vs. Microservices”, but also make it easy to challenge and validate the result using your own AI workflow.

    Still just a simple static website, but hopefully useful for making more informed engineering decisions.

    Hope it helps someone make better tech decisions.

    🔹 stackcompassguide.dev/

    #ai #webdev #programming #softwaredevelopment #softwarearchitecture

  18. Software Deployment Lifecycle 🎭

    Act 1: FAT (Factory Acceptance Test)
    - Duration: 1 week
    - Developers: “Everything works!”
    - Customer: “Great, I’m satisfied!”

    Act 2: SAT (Site Acceptance Test)
    - Duration: 1 week
    - Developers: “Now everything really works!”
    - Customer: “Perfect, still satisfied!”

    Act 3: Production
    - Duration: 1 week
    - Developers: “Wait… what? Why do you need to change what we approved a month ago?”
    - Customer: “Well, I can only see it now that it’s live!” 😅

    👉 Have you had a similar experience?

    #deployment #programming #it #devlife #softwaredevelopment

  19. A new Blog section is now live on:

    🔹 stackcompassguide.dev/blog.html

    It contains articles about keeping architecture simple, avoiding overengineering, and recognizing common software anti patterns, based on real world decisions and tradeoffs. I will keep adding more over time.

    If you are figuring out what to use and why, this might help or maybe even inspire you. 😉
    I would really appreciate any feedback.

    #programming #softwaredevelopment #cleancode #softwarearchitecture #devops #refactoring

  20. Built a small side project: Stack Compass Guide, a static website that helps developers make architecture decisions faster.

    It works as guided decision flows (e.g. Monolith vs Microservices, SQL vs NoSQL, REST vs GraphQL). You answer focused questions, get a recommendation, then jump to a result page with: when to use it, when not to, pros/cons, common mistakes, and best practices.

    No backend, no auth, no tracking.

    I hope you find this useful. The project is still evolving, and feedback is always appreciated. Feel free to share any ideas, suggestions, or improvements.

    🔹 stackcompassguide.dev/

    #architecture #softwaredeveloper #devops #techlead #education #programming

  21. Love anyone talking about my fav books of all time.

    The Apocalyptic History of Mortal Engines by Exits Examined
    youtube.com/watch?v=4MchClUce1Y

    #mortalEngines

  22. Just started watching #MortalEngines on Netflix. Pretty early in the movie, but it already had an amazing joke about current pop culture, and incredible VFX (a chase on foot across a small city that gets cut apart by the giant machinery of a larger city).

    But all the outdoor scenes have this super weird studio lighting on the actors. Maybe the backgrounds were not ready yet or were revised a lot? (those huge full-CG vistas were probably no easy feat).