Masoud Salehi Alamdari

I'm happy to share that PHP Magazin published my article on PHP Best Practices for Production! Over the years, I've seen countless PHP projects slow down or fail due to avoidable architectural and operational decisions. In this piece, I share: - Practical advice for scaling PHP applications - Common pitfalls I see in real-world audits - A modern checklist for running PHP in production efficiently It’s based on lessons learned from profiling hundreds of apps, and it’s aimed at helping teams avoid performance traps early. Read the full article (in German): https://lnkd.in/e7u5K7aa Would love to hear your thoughts or feedback!

34

3 Kommentare

At yesterdays Vienna Engineering Management Meetup had the honor of speaking about building an ownership-driven engineering culture! Thanks Josip Saban and Igor P. for the invite and the great location at Erste Digital Most engineering teams optimize for output: story points, velocity, lines of code. But output isn't outcomes, you can have high velocity and still ship products nobody uses. The key principles of extreme ownership are: 1. Leaders own everything - no excuses, no blaming external factors 2. No bad teams, only bad leaders - if ownership is missing, look in the mirror 3. Believe in the mission - teams can't own what they don't understand 4. Decentralized command - push decisions down, trust your people These aren't just principles on a slide. In the deck I share real examples of what happened when I applied them with my teams: • One team went from 40% → 85% delivery predictability in 6 weeks by assigning clear topic owners - same people, different structure • A live production dashboard reduced incidents 60% - engineers saw real users affected in real-time and quality became personal • Support developer rotation cut defects 40% - when you might debug your own code next week, your standards change today The shift in every case was the same: stop measuring output, start measuring outcomes. Stop tracking velocity, start tracking what your customers would actually put in a quarterly business review. Ownership isn't demanded. It's built - one practice at a time. #EngineeringManagement #EngineeringLeadership #TechCommunity #ViennaTech #LeadershipInTech

72

7 Kommentare

🚀 Freelance vs Full-time Software Development in Germany - When to choose what In Germany's technology market, both freelance developers and permanent employees play important roles. The right choice depends on your business needs. ✅ Freelancers are the better choice when ⚡You need very specific expertise for a clearly defined project or technology stack ⚡Speed is important, since freelancers can usually start quickly without long hiring processes ⚡Your workload is project-based and does not justify a permanent hire ⚡You want flexibility to scale teams up or down without long-term obligations 👩‍💻 Permanent employees are the better choice when ⚡You want to build long-term product knowledge and strong company culture ⚡Continuity in core systems is essential ⚡The role requires deep integration with the business and its processes In short: 👉 Choose a freelancer for focus, speed, and flexibility 👉 Choose a permanent employee for stability, culture, and continuity The value lies in knowing which model fits your current challenge. #Freelance #SoftwareDevelopment #TechHiring #ITFreelance

38

How you can get some Async in PHP using Symfony HTTP Client or Guzzle: I published a video on a small refactoring on our own Tideways GmbH codebase to use parallel HTTP requests to reduce time spent talking to a microservice. https://lnkd.in/eAEsmtB7 #php #symfony

21

3 Kommentare

Two major events today: 1️⃣ Launch of the yearly SPS in Germany 🏭 2️⃣ Release of Claude Code Opus 4.5 ✨ This morning I am keeping half an eye on my LinkedIn feed showing posts from SPS, while I test the capabilities of Opus 4.5. Such a crazy time to live in, where every x months coding models become y % better. And there are no signs that things are slowing down. But industrial automation is stuck. We can't use the modern coding workflows with the 'legacy' automation IDE's. Yes during SPS multiple vendors are presenting some kind of solutions. But here are the problems: ❌ Coding agents have no direct access to the code, everything runs through API's/MCP/... ❌ No git for tracking the agents. (Or worse: broken git) No granular commits and reviews for what the agents are doing. No diffs. No SDLC. ❌ No or limited BYOM (Bring your own Model). ❌ Separate licensing for the coding agents WITHOUT the model. ❌ ... ? The root causes are: 1️⃣ Legacy IDE's that shield the code from direct access 2️⃣ No CLI commands for things like code compiling (coding agents need feedback loops) 2️⃣ Fragmented IEC-61131 dialects (yes most automation engineers stayed in a single vendor ecosystem, but agents are general, and will be massively confused by this) But at least there's good news: next-gen IDE's are coming! This is what has already been announced/released: - Simatic AX - Beckhoff PLC++ - Codesys Go! - B&R Automation Studio Code ... and more coming that are not announced yet. My recommendation? Stop putting effort in legacy IDE's. We'll need to transform our coding workflows. It will take effort. Using coding agents with legacy IDE's will be almost impossible to control. Spend the effort by taking the opportunity to switch to a next-gen IDE. Talk to your vendor. Don't take 'not ready' for an answer. (Send me a DM if you don't know which person(s) to talk to) And if you're one of the automation vendors? Well we have been asking to fix the IDE's and toolchains since many years. At least some of you realized the need and took action a while ago. But there is no way to hold this back. We are losing competitiveness, speed and talent. Things still feel like they are moving relatively slowly. Yet soon it will be suddenly. How about the DCS system? Well ... you all know that I live and breathe process automation. There also is a viable path forward there. But no vendor seems to see the path through the trees yet ... 🤷‍♂️. I am not at SPS, so add a comment if I missed something ... 🫵 👇

28

2 Kommentare

Your CI/CD bill is not exploding because of “expensive runners,” it is bleeding out through flaky tests, over-parallelized jobs, and slow feedback loops that quietly tax every deploy This piece shows you how to redesign pipelines so you cut compute waste, shrink queues, and speed up developer flow without adding yet another approval gate or YAML religion Full breakdown in the comments. #DevOps #CICD #PlatformEngineering

8

1 Kommentar

Developer in Germany vs Developer in UAE — Part 2 1) Engineering culture and development practices When I worked in Germany, I saw many different engineering principles, patterns, and design approaches such as DDD, TDD, SOLID, CQRS, microservices, and others. In the UAE, most companies focus mainly on timelines and the number of features a team can deliver per sprint. My opinion: When you are constantly in a hurry or under pressure, you cannot produce high-quality code. And one day, working with such legacy code becomes much slower than writing high-quality code with a more thoughtful approach from the beginning. 2) Hybrid/remote work in Germany vs full on-site work in the UAE When I worked in Germany, it was a hybrid model, and many of my friends worked fully remote. In the UAE, it is usually full on-site work. At the same time, this is not always productive: when you work in an office where many people talk loudly, it becomes very hard to focus on complex tasks with very short deadlines. 3) Three things the UAE does better than Germany: Tax-free, tax-free, and once again — tax-free. And yes, it's extremely important. I spent 2 years in Germany and 2 years in the UAE.  In Germany, I mostly spent money.  In the UAE, I save money — and not because there’s nothing to do here. Actually, there are tons of events: Formula 1, concerts of big artists, festivals, and more. Local companies often provide tickets for important events. Even if you buy your own subscriptions, you still spend much less than going once at full price. Prices overall are lower than in Germany. Only rent is higher — roughly 2× higher in the UAE compared to Germany. Perhaps you’ll never see me again — follow me to get more. #SystemDesign #FAANG #MAANG #Netflix #Apple #Amazon #Google #Facebook #Twitter #DesignPatterns #Uber #LeetCode #LiveCoding

62

1 Kommentar

Do you know how often developers commit tokens and secret keys to public and private repositories? Even then, they think that if they remove them in the next commit, they will be gone forever. But they will continue to appear in git logs and will be totally reachable. Sometimes creating a lot of branches confuses people even more and they might believe that the exposed secret will be hidden deep within the repository. But believe me my friends there are automated bots digging through GitHub every second to exploit your mistakes. You can test this by creating a public repository and making a dummy commit on it and then checking the traffic tab on your repository. You will be surprised. In seconds you will see your repository has already been cloned. So any mistake = no turning back.

19