Ahmed I. Khalil

Most #gradle projects need to upgrade their dependency handling. The first step is to take advantage of version catalogs and Maven BOMs. I am here to show you how. Do your team a favor and upgrade today. https://lnkd.in/gqwGqRa4 #kotlin #java #maven #micronaut 

9

May be some real-time exp with latest AI tools..

2

Why I Broke Up with NavigationView for NavigationStack 💔 Me to NavigationView: "It’s not you, it’s me... Actually, no, it is you. You’re just too... outdated." 😬 💡 NavigationStack slides in: "I heard you like clean, predictable navigation. Let’s make your app drama-free." 🎉 Now, with NavigationStack, navigating between views is so smooth, it feels like I’m swiping on a dating app. No weird reloads, no confusion—just one view at a time. 📱 My app: "Finally, I can stop seeing my views fight each other for attention like it's the Hunger Games." 👀 PSA: If you’re still using NavigationView, it’s like using dial-up internet at a fiber-optic party. Time to upgrade before your code ghosts you! 😂 https://lnkd.in/err3bdJQ #iOSGlowUp #NavigationStackForever #NoMoreViewDrama #SwipeRightOnBetterNavigation

3

Creating good easily understandable names for tables and schemas is hard There are many ways that this can go wrong which will make your life much harder let’s talk about 7 of them 1. Using way too many abbreviations makes interpreting what’s in the table very difficult. No one wants to figure out what dim_sno_ord_spec_tab means. I get the appeal of this: it's quicker to type then having everything spelled out but it makes search almost impossible. 2. Using version numbers for tables usually it’s better to use dates to make it clear what the history is. This especially goes if you decide to do the excel thing where the table name looks like v1_final. Please don’t do that 3. Inconsistent naming I’m not going to wade into the debate about whether your tables should be named as a singular or a plural or into camelCase vs snake_case but whatever you decide on do the same thing for all your tables. 4. Don’t put tables or tbl in front of each table name. It's not necessary and it adds noise back in the day. It could be helpful but most modern tools split up your tables and views anyways. 5. Don’t use spaces in table name. Yes you can query it with back ticks but having to add the backticks to every query is pretty annoying and will slow you down over time. 6. Do spend time on your naming conventions early on. The work you do hear will pay dividends down the road since it can prevent many future messes 7. Do make sure your naming conventions are well documented and widely shared. New people will get onboarded and create tables. You want it to be obvious what they should do. There we have seven rules to help your database stay easy to work with. I’ll admit to having broken everyone of those rules at some point, many of them as just a temporary thing of some sort. Usually I’ve gone on to regret it since temporary fixes have a way of living a long time.

4

Most developers aren’t fans of TDD (Test Driven Development)—in fact, many dislike writing tests altogether. Imagine a world where you didn't have to write tests anymore? With the new age of AI-powered DevTools, the landscape of TDD is changing quickly. Discover how TDD can be MADE EASY in our latest blog post by Early's CTO Lior Froimovich. * Engineers simply write the method signatures, document what the method does, and optionally, define desired tests in a comment above the method name. * AI DevTools generate the unit tests with a click. All tests will initially fail because there’s no implementation yet. * Next, engineers implement the methods. * Red tests turn green. * happy engineers deliver quality code—faster. Learn how this can be done today. Link to the blog on the first comment. Enjoy reading it.

19

1 Kommentar

𝗧𝗵𝗲 𝗦𝗶𝗹𝗲𝗻𝘁 𝗜𝘀𝘀𝘂𝗲 𝗧𝗵𝗮𝘁 𝗖𝗮𝗻 𝗕𝗿𝗲𝗮𝗸 𝗬𝗼𝘂𝗿 𝗣𝗿𝗼𝗱𝘂𝗰𝘁 𝗮𝗻𝗱 𝗪𝗵𝘆 𝗗𝗼𝗰𝗸𝗲𝗿 𝗶𝘀 𝗘𝘀𝘀𝗲𝗻𝘁𝗶𝗮𝗹 your team has just launched a healthcare platform designed to help patients schedule appointments, track medications, and log symptoms. Everything is going great—patients love the user-friendly interface, and doctors are impressed by the detailed reports. But then, reports start rolling in. Some patients can’t log their symptoms. Others are unable to book appointments. Your customer support team is overwhelmed, and doctors are growing frustrated. You investigate, only to discover the root of the issue: your application is behaving inconsistently between environments. 𝗧𝗵𝗲 𝗣𝗿𝗼𝗯𝗹𝗲𝗺🛑 Your developers are all using slightly different setups—one uses Python 3.9, another uses Python 3.10. The production server is running Linux, while most developers work on macOS. To make matters worse, a key Python library your app depends on has subtle compatibility issues across versions. These environment mismatches are causing bugs that only show up in production. Every missed appointment or error is more than an inconvenience—𝗶𝘁’𝘀 𝗮 𝗽𝗼𝘁𝗲𝗻𝘁𝗶𝗮𝗹 𝗿𝗶𝘀𝗸 𝘁𝗼 𝗽𝗮𝘁𝗶𝗲𝗻𝘁 𝗰𝗮𝗿𝗲. 𝗘𝗻𝘁𝗲𝗿 𝗗𝗼𝗰𝗸𝗲𝗿 This is where Docker can transform your development process and prevent these issues from spiraling out of control. With Docker, you: 🌟Create containers that package your application with its exact dependencies and configurations, ensuring it runs identically everywhere. 🌟Run your app, database (like Postgres), and other services (like Celery or Redis) in isolated, reproducible environments. 🌟 Deploy the same container you tested locally to production, eliminating the risk of environment-specific bugs. 𝗧𝗵𝗲 𝗦𝗼𝗹𝘂𝘁𝗶𝗼𝗻 𝗶𝗻 𝗔𝗰𝘁𝗶𝗼𝗻⚙️ By introducing Docker into your workflow, you eliminate inconsistencies. Every developer, tester, and server now uses the same containerized version of your healthcare platform. Bugs that once took days to track down are found and fixed in hours because your test environment mirrors production exactly. 𝗧𝗵𝗲 𝗥𝗲𝘀𝘂𝗹𝘁 When the next wave of users logs in to your platform, they can schedule appointments, log their symptoms, and access reliable medication trackers. Doctors can trust the reports, and your team can focus on building new features. 𝗪𝗵𝘆 𝗧𝗵𝗶𝘀 𝗠𝗮𝘁𝘁𝗲𝗿𝘀 When your product impacts lives, there’s no room for "it works on my machine." Docker ensures your application is robust, reliable, and consistent—whether in development, testing, or production. If you’re managing complex applications in industries like healthcare, finance, or logistics, Docker isn’t just helpful—it’s essential. #Docker #Healthcare #SoftwareDevelopment #Python

18

3 Kommentare

Have you had enough Hexagonal Architecture yet? No? Well, have I got a podcast for you! In this episode, me and Fito von Zastrow talk about our early experiences using the Ports & Adapters pattern with Rails. Let us know your thoughts! #ruby #rails #ruby_on_rails #hexagonal_architecture #ports_and_adapters

15

9 Kommentare

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

9

1 Kommentar

🔒 Immutable. Efficient. Compile-time validated. Meet "const" in Rust the unsung hero of clean, reliable code. Why should constants matter in your Rust projects? ✅ No runtime overhead ✅ Enforced safety ✅ Readability & maintainability Why settle for magic numbers when you can code with clarity? 🌟 Dive in and write smarter code! 💻✨ #RustLang #DevTips Rustaceans Nigeria

3

1 Kommentar

Simplifying Cross-Platform Development with Kotlin Multiplatform I recently tackled a thrilling challenge: sharing code seamlessly across multiple platforms. My journey led me to discover the power of Kotlin Multiplatform. To pay it forward, I've written a concise article to help others navigating this space. If you're exploring Kotlin Multiplatform, this resource is for you. Check it out and let's connect! Part 1 https://lnkd.in/gD-cZrj7 Part 2 https://lnkd.in/g_UUTuKz #KotlinMultiplatform #CrossPlatformDevelopment #SoftwareEngineering #CodeSharing #ProblemSolving

23

🎯 Ever wonder why that "2-day task" took 2 weeks to complete? I've just published an article about Parkinson's Law in software development - "Work expands to fill the time available for its completion." What you'll learn: ✨ How to identify time-expansion traps in your development process ⚡ Real-world strategies from successful projects 🚀 Practical time management techniques that actually work 💡 Ways to maintain productivity without sacrificing quality The article includes a case study of how a team can deliver a 6-week project in just 4 weeks using these principles. Perfect for: Tech Leaders, Developers, Project Managers, and anyone involved in software delivery, or someone like me who is simply interested in stuff like this. Let's discuss: What's your experience with time estimation in software projects? Share your thoughts below! 👇 #softwaredevelopment #productivity #programming #agile #projectmanagement #technology #developers #engineering

3

1 Kommentar

WARNING ⚠ : Are you about to design or work on a microservices project? If so, you really need to read this first. I will be publishing a series of articles about the dark side of microservices projects, and how some tiny design mistakes can grow into huge problems 🌋. My point of views are up for debate. I'm not saying I'm right, rather I'm showcasing some of the problems I went through. If you have an opposing opinion please share it with me as these discussions can help both of us learn more 📚.

6

2024 saw a surge of text-based AI chat assistants appearing on almost every website. What's next? Voice-based AI assistants are poised to dominate the internet in 2025. They will likely be integrated seamlessly with existing chatbots, becoming increasingly commonplace. I tried an open-source WebRTC toolkit known as Livekit. This can help developers build the next-gen voice based AI assistants. https://lnkd.in/dGqZaPqj #ai #artificialintelligence #assistants #voiceagents #aiagent

10

1 Kommentar

Next week, I will be in #Berlin at LeadDev, speaking about #NeurodiversityInTech which is a topic I care deeply about. I will also attend many other great talks, so I am giving a shoutout to some of the talks I am most excited to see. Ice, confusion, and the 38,000ft crash - Nickolas Means Level up the whole party, not just the hero - Denise Yu How to talk to everyone: Connecting with your reporting chain - Najla Elmachtoub

16

1 Kommentar

🚀 Day 5 Update: Optimizing and Streamlining! 🚀 Today’s focus on my Hospital & Pharmacy Management System project was all about efficiency and optimization. 🎯 What I accomplished: ✅ Optimized Code: Refactored and cleaned up the codebase for better performance and maintainability. ✅ Unified Pages: Combined the Create Patient and Create Doctor pages into a single Create Profile page, making the system more intuitive and reducing redundancy. Efficiency is the key to scaling this system, and I’m excited about the progress so far. Looking forward to adding even more functionality in the coming days! #Day5 #HospitalManagementSystem #PharmacyManagementSystem #MERNStack #WebDevelopment #Optimization #NodeJS #ReactJS #ExpressJS #MongoDB #ProjectJourney

9

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

Why Ruby on Rails for Back-end Development? ✅ Ruby on Rails' convention-based approach speeds up development, allowing for rapid deployment of back-end systems. ✅ It's proven in handling large-scale applications, ensuring smooth performance as your project grows. ✅ With a wealth of gems and plugins, Ruby on Rails simplifies complex tasks and integrates seamlessly with other technologies. ✅ Tap into a thriving community for guidance, updates, and solutions, ensuring your backend stays up-to-date and secure. If you're looking for a reliable, scalable, and efficient back-end framework, Ruby on Rails is the go-to choice 🚀🚀 #RubyOnRails #softwaredevelopment #technology #webdevelopment

7