Mustafa Abdelmogoud

Embedded developers with niche skills are like gold dust. If you find one, don’t hesitate... hire them quickly. I see over and over that these specialists are often snapped up by companies that understand their value. That means your hiring process needs to be not just fast, but also enticing. Competitive salaries, interesting projects, and a clear path for career growth are essential if you want to attract and retain this top talent. Speed and flexibility in hiring can make all the difference 🙏 The companies that adapt their recruitment strategies to move quickly are the ones that will come out on top.

3

Returning to Java from Kotlin has me thinking again about nulls and null-safety. Kotlin has softened me somewhat on the subject of nulls, because its handling of them is safe and elegant: declaring a type as T? is more or less equivalent to declaring it as Maybe T in Haskell, and null is just a compact representation of None in that case. The compiler will simply reject anything that tries to pass null, or the unchecked value of a variable of nullable type, to a non-nullable receiver. It's one of the two things about the language I'm really going to miss (the other being the Ruby-like block syntax). After a phase of thinking Optional<T> should be used to do the same thing in Java, I'm actually swinging back more towards annotating optional fields and parameters as @Nullable, and relying on tooling (the IDE, build-time linting) to enforce Kotlin-like null-discipline. But there's a skeleton in the closet: older (pre-record-type) Java often has a lot of POJOs with default no-argument constructors lying around. You construct one, everything's null, you set fields one by one with the setters. It's much harder to impose null-discipline of any kind in this scenario. People depend on this behaviour, too - they create test value objects by newing up instances of POJOs and setting only the fields the code under test is interested in, and everything works. You can say "you should make it impossible to construct an object in an invalid state" all you like, but you're going to break all those tests if you actually take the ability to partially populate a value type away from them. Lombok doesn't help, either - there's no way to compile-time check that all the mandatory fields have been added to a builder before calling build(). And even with record types, the ability to use builders to supply field values by name, rather than relying on their order in the constructor signature, is going to be hard to take away from people working with value types with a dozen or more fields. Java is just an ever-burning tire fire around these issues, and always has been, and it's a major reason why "legacy" code tends to suck so much. At the moment the best I think I can do is try to promote a general pattern: if you can't ensure correctness on construction, validate correctness immediately after construction (and prevent illegal mutation after that). At least then you can eliminate ad hoc null checks downstream of validation, and be clear about when missing values are actually to be expected.

84

34 Kommentare

🚀 **Building Scalable Enterprise Applications in C#? Let’s Talk Best Practices!** 🧑‍💻 👩‍💼 Imagine this: Your C# application is handling 10 users effortlessly, but can it handle 10,000? 100,000? Scalability is the superpower that ensures your enterprise applications grow with your business — without breaking a sweat. Here’s what makes a difference: ✅ **Asynchronous Programming** – Optimize performance and reduce bottlenecks with async/await. ✅ **Dependency Injection (DI)** – Keep code clean, testable, and decoupled to handle future complexities like a pro. ✅ **Caching Strategies** – Slash response times by implementing efficient memory or distributed caching solutions. ✅ **Microservices Architecture** – Scale services independently instead of rebuilding the monolith. ✅ **Profiling & Optimization** – Regularly review your code for hotspots and optimize for long-term efficiency. 💡 By mastering these practices, you’ll equip your applications to thrive under high demand while delivering smooth user experiences. 📣 *Your turn*: Have you implemented these strategies in your own work? What challenges did you overcome when scaling C# applications? Share your insights or drop your questions in the comments! Let’s collaborate and grow together. #CSharp #EnterpriseDevelopment #Scalability #CodingBestPractices #moa7amed #moa7amed_com

1

Incorrect Generalizations with Amitai: einfach = simple vielfach = complicated nullfach = impossible

9

1 Kommentar

🚀 **Want to Take Your JavaScript Skills to the Next Level?** Clean and maintainable code isn’t just a "nice-to-have"—it's a *must* for writing effective JavaScript in today’s fast-paced development landscape. Whether you’re collaborating with a team or revisiting your own code months later, following clean coding principles makes a world of difference. Here’s how you can start writing cleaner, more maintainable JavaScript today: ✅ **Use Meaningful Variable and Function Names** - Avoid generic names like `x` or `data`. Instead, opt for descriptive names like `userEmail` or `fetchUserData()`. Clarity > Brevity. ✅ **Keep Functions Simple** - Stick to the Single Responsibility Principle: each function should do *one thing* and do it well. If a function grows too complex, break it down into smaller, reusable ones. ✅ **Consistent Formatting Is Non-Negotiable** - Adhere to a style guide like Airbnb or Google for consistent naming conventions, indentation, and spacing. Tools like Prettier and ESLint can help you automate this. ✅ **Avoid "Magic Numbers"** - Don’t hardcode values like `3600` directly into your code. Instead, use constants with descriptive names: `const SECONDS_IN_AN_HOUR = 3600;`. ✅ **Comment with Purpose** - Comments should *explain the why*, not the what. If you need to explain *what* your code does in detail, it’s likely time to refactor. ✅ **Think In Terms of Reusability** - Avoid duplication by abstracting recurring logic into helper functions or modules. Reusable code is more efficient and easier to maintain. 💡 **Pro Tip:** Write tests. It’s not just about spotting bugs—it’s also a great way to ensure that your code is doing exactly what it’s supposed to, every time. Clean JavaScript isn't just a mark of professionalism—it's how you future-proof your skillset and contribute to scalable, sustainable projects. #JavaScript #CleanCode #WebDevelopment #CodingTips

1

I just published my newest post - starting an introduction to #Kafka and how it can be used in #Kotlin. https://lnkd.in/eD3THjGw

20

🚀 Looking to build scalable enterprise applications with C#? Mastering best practices isn't just a suggestion—it's the key to creating efficient, maintainable, and future-ready systems. ✅ **Here’s Why It Matters:** - **Performance Boost:** Applying tried-and-true patterns ensures your code runs like a well-oiled machine, even under heavy loads. - **Cleaner Architecture:** Dependency Injection, CQRS, and SOLID principles keep your codebase organized and maintainable. - **Seamless Scaling:** From caching strategies to asynchronous programming, harness techniques that grow as your application scales. - **Teamwork Made Easy:** Standardized practices mean fewer headaches during code reviews and faster onboarding of new developers. 💡 Whether you're leveraging .NET 6's latest features, optimizing LINQ queries, or embracing asynchronous APIs, always measure and refine. Small tweaks today can save days—if not weeks—of work tomorrow. What’s your go-to best practice in C#?👇 #CSharp #EnterpriseDevelopment #CodeBetter #Moa7amed #Kaggle #ProgrammingTips #DotNETDevelopment

1

During lunch a few weeks ago, someone asked one of the developers in my team how long it would take to write one of our internal-facing systems from scratch. He looked at me and said: "Something like 3 months, right Anton?" And I replied: "Closer to 6. And then 3 more years to add all the edge cases". The longer the code exists - the more stable it is. When I started leading my team 2.5 years ago, I was given a legacy system to support, that nobody really knew. So far, it had maybe 2 small problems due to external API changes, and is just working flawlessly… 𝗖𝗼𝗱𝗲 𝗶𝘀 𝗹𝗶𝗸𝗲 𝘄𝗶𝗻𝗲 - 𝗶𝘁 𝗮𝗴𝗲𝘀 𝘄𝗲𝗹𝗹. Vadim Kravcenko wrote a great article about it: https://lnkd.in/dCC8QcTe P.S. Who do you think will win the fight in the image? :) Join 12,700+ engineering leaders for weekly articles on leading software teams: https://lnkd.in/dmvYbssM

13

3 Kommentare

🌍 **Diversity: The Secret Ingredient for Outstanding Software Teams** 🌟 Have you ever wondered why some software teams thrive while others struggle—despite having similar resources? One often-overlooked factor is **cross-cultural collaboration**. When done right, it’s not just about reducing friction—it’s about sparking innovation. In my experience building software teams across borders, here’s what stands out: ✅ A mix of cultural perspectives leads to better problem-solving and creativity. ✅ High-performing teams don’t eliminate differences; they harness them through empathy, clear communication, and shared goals. ✅ Inclusive environments create a stronger sense of connection, ownership, and motivation. Success lies in understanding **HOW** to bridge cultural gaps and foster collaboration. From defining shared values to adapting feedback styles, every step matters. (Spoiler: It's not just about team-building exercises!) 💡 Are you leading—or dreaming of building—a global software team? Let’s share insights! 🔁 What challenges have you faced working in cross-cultural teams? 💬 How do you approach collaboration with colleagues from different cultures? Drop your thoughts below; let’s learn from each other! 🚀 #SoftwareTeams #Leadership #DiversityInTech #CrossCulturalCollaboration #Innovation #TechLeaders #moa7amed #moa7amed_com

1

3 top tips for Junior Software Developers: 1. Never let a mentor touch your keyboard: If you can't find something or don't know what to search for, have them guide you, not do it for you. Embrace the struggle. 2. Present solutions, not just problems: As a junior engineer there will be a lot you don't know, can't do or haven't experienced. Communicate how you think you might be able to overcome them, or what you might need to help solve it. Go beyond 'I don't know'. 3. Get involved with other areas of the business: One way to really stand out is to have domain knowledge deeper than code. Ask to spend a week answering calls with Customer Service, take a day to learn how Marketing does outreach, and walk through your Client archetype with the Sales team. I bitterly miss the feeling of unending learning and wonder that comes with being a Junior Software Engineer.

245

31 Kommentare

3 top tips for Junior Software Developers: 1. Never let a mentor touch your keyboard: If you can't find something or don't know what to search for, have them guide you, not do it for you. Embrace the struggle. 2. Present solutions, not just problems: As a junior engineer there will be a lot you don't know, can't do or haven't experienced. Communicate how you think you might be able to overcome them, or what you might need to help solve it. Go beyond 'I don't know'. 3. Get involved with other areas of the business: One way to really stand out is to have domain knowledge deeper than code. Ask to spend a week answering calls with Customer Service, take a day to learn how Marketing does outreach, and walk through your Client archetype with the Sales team. I bitterly miss the feeling of unending learning and wonder that comes with being a Junior Software Engineer.

368

41 Kommentare

The software development world sometimes presents interesting and conflicting challenges: while some of the most important OOP languages have adopted null-safety as a standard (Kotlin, Dart, Swift...), we still rely on JSON to exchange data over the wire, which is not null-safe and unstructured. While there are alternatives to JSON, it is present in the majority of APIs available. In my experience, many of the quality problems apps experience these days are related to a misunderstood API contract with JSON as a guilty actor. JSON is great for flexibility, but the languages mentioned above are going in a different direction. Will we ever see an alternative to JSON that is structured, null-safe, and mainstream? Is someone already working on such a project? I would love to hear your thoughts!

26

11 Kommentare

Here are the slides for my GopherCon.EU talk: How to Win Frames and Influence Pointers https://lnkd.in/d7byRQfu #gopherconEU #golang

72

4 Kommentare

Edition #60 of the DevNewsletter: DevTool Weekly Roundup has just been published on Linkedin and our website (link below in the comments). Here's the TL;DR 🏆 Funding Wins Supabase Soars with $80M Series C to Simplify Postgres for Developers Platformatic Raises $4.3M Seed to Supercharge Node.js Development Raycast Secures $30M Series B to Tackle Workplace Context Switching 🚀 3, 2, 1 … Launches MindsDB Launches Minds AI to Simplify Data Querying Kurve Emerges from Stealth with AI-Powered Data Discovery Tool Stytch Unveils Fraud & Risk Prevention Solution to Combat Advanced Threats Sieve Unveils SieveSync to Advance Lip Sync Pipelines Airbyte 1.0 Launches, Setting a New Standard for Data Movement Harness Introduces AI-Powered DevOps Tools 🔦 DevTools of the Week streamvisor: Boosting Pulsar Management with v3.1.0 Release ServBay: Redefining Localized Web Development for Modern Teams #DevTools #Develocity #DeveloperTools

5

2 Kommentare