Dan B. Daneshgar

Mentoring on the Mainframe Your junior or midlevel systems programmer knows there is a problem. They are “pretty sure” they know what they need to do, but they want to make sure they don’t make a mistake. They spend several hours looking through Redbooks.   Look through system documentation trying to determine if the fix they have in mind is the correct one. Is this PTF going to impact production? They are talking to IBM support to verify that what they are about to implement won’t impact production. But they still have doubts. Your sys progs wish that they could talk with someone that can look at the problem they are facing and let them know if they are doing the right thing. Let them know they won’t cause a Sev1. If your systems programmers are struggling a bit and need a little support, reach out to me. I know a lot of “Semi-retired” systems programmers that can help you out. #Mentor #Mainframe #ZOS #CICS #IMS #DB2 #Commserver #Sev1 

53

2 Comments

Most people see .NET as an enterprise-safe choice. But its real power shows up in places teams rarely talk about. Here are a few quiet truths most engineers realize late: .NET Optimizes for Long-Term Thinking The framework subtly pushes teams toward clearer contracts, predictable behavior, and fewer “clever shortcuts” — which matters more after year 3 than week 3. Failures Are Easier to Reason About When things break in production, .NET’s runtime diagnostics often tell why, not just that something failed. That reduces panic-driven fixes. Boring by Design Is a Feature .NET avoids frequent paradigm shifts. This stability lowers cognitive churn — teams spend more time solving business problems, not relearning patterns. Scalability Is Cultural, Not Just Technical The ecosystem encourages conventions that scale people and processes, not just servers. The hidden value of .NET isn’t speed or syntax. It’s decision confidence over time. Sometimes, the most valuable frameworks aren’t exciting — they’re dependable when complexity grows. 👇 What’s one thing you appreciated about .NET only after using it in production? #DotNet #SoftwareEngineering #BackendDevelopment #TechInsights #EngineeringMaturity #SystemDesign #Bairacorp

4

4 Comments

APIs break more often than you think, but not when they're built like this. High-traffic. High-stakes. High expectations. If your API can’t scale, secure, and sustain itself, your entire product might stall. That’s why every layer matters: ✅ Controller structuring ✅ Middleware setup ✅ Dependency injection ✅ Clean versioning and more This isn’t just a best-practices list; it’s a blueprint for building robust APIs with .NET Core and C#. 🔗 Read the full guide by Khurram Minhas, Principal SE at Arbisoft: https://lnkd.in/ddbyRbVC #DotNetCore #CSharp #APIdevelopment #ArbisoftBlogs

7

Career transitions in .NET are rarely about one missing skill. They usually fail because preparation is scattered not structured. In 2026, strong fundamentals alone are not enough. Hiring panels expect clarity across core development. This roadmap is a practical way to think about your preparation. Not everything needs to be mastered at once, what matters is WHAT to learn first and WHY ? If you are planning a role change or aiming for senior interviews this year, this free session will help you build that clarity. 👉 This Saturday, Join the FREE .NET Learning Roadmap session here: https://luma.com/l8bapn2e Happy Learning !

126

3 Comments

Debugging is a critical part of development, but it shouldn’t slow you down. If you're working with .NET Core in VS Code, knowing how to efficiently run and debug your applications can significantly improve your productivity. This article walks through a clean and effective approach to setting up and debugging your .NET Core apps in VS Code, perfect for developers looking to streamline their workflow. 👉 Read here: https://lnkd.in/g_ZutGfr #DotNet #VSCode #SoftwareDevelopment #Debugging #Developers

17

Learn what Playwright is, why teams use it, how it compares with other E2E tools, and how to scale tests with parallel execution.

2

Unify your .NET document workflows—no more juggling libraries or patching brittle code. With Xceed Words and Xceed Workbooks for .NET, you can automate Word and Excel output from a single, modern codebase. Build branded Word summaries and data-rich Excel reports in parallel, then merge them for seamless, multi-format reporting. Ready to streamline your reporting and boost reliability? Discover how unified document automation accelerates your workflow: https://zurl.co/0rahB #dotnet #developer #automation #reporting #Xceed #Word #Excel #productivity

8

I'm in agreement here, but partially because what I found over time is that people are so keyed up to tell you that they've memorized what the SOLID acronym is. If SOLID came up in an interview, I'd try to go Bloom's Taxonomy and get them to explain how to apply any of that or how they used those principles to evaluate code, but the memorization and jargon was all many candidates could regurgitate. Anyway, as much as I've written about SOLID over the past 20 years myself, I don't think it's actually useful as a heuristic tool for many developers these days.

25

2 Comments