Abdelrahman
417 posts

Abdelrahman
@a_aMatrix
🕋 | 🇪🇬 | 👨💻 | ✨️ | Like/RTs ≠ Endorsement | Views my own


لسه فاكرة البنت اللي كانت بتعملي ديكوريشنز الخطوبة فالبيت لما قولتلها هو حابب اسمي يتكتب قبل اسمه قعدت تتشنج وتقولي مينفعش (معرفش دخلها ايه الحقيقة) و هقول للناس إيه أنا فاهمة شغلي، بعدين قالتلي بحقد كده يلا افرحيلك يومين كله بعد الجواز هيتبخر!!

كان في حد بعتلي سؤال عن ال تيك Roles اللي شايف الطلب عالي عليها دلوقتي بس المنشن تاه مني وفكرت أن جاوبت ونسيت طبعا الإجابة هي Forward Deployment Engineer وهي تسمية جديدة لل integration engineers بس فيها تويست


Working code beats perfect code. Almost every time. Early in your career, you think great engineers write flawless code. They don’t. They ship things that work. I’ve seen teams spend weeks polishing “perfect” solutions… while users were blocked by something basic not working. That’s not craftsmanship. That’s procrastination dressed up as standards. Working code does a few important things: • It proves the idea has value • It creates feedback you can’t get in theory • It moves the business forward • It gives you something real to improve Perfect code that never ships does none of that. Yes, bad code causes problems later. But no code causes problems immediately. The real skill isn’t writing perfect code. It’s knowing when “good enough” is good enough. Ship. Learn. Refactor with intent. Most engineers don’t stall because they lack ability. They stall because they’re scared to show unfinished work. That fear costs more than technical debt ever will. Working code is how momentum is built. Perfect code is how momentum gets killed. —— ♻ Repost to help others learn that. ➕ Follow @petarivanovv9 + turn on notifications.

JUST IN: Sam Altman says AI is unlikely to cause a jobs apocalypse

mfs in europe complaining about 20 celcius Bro 😭😭😭😭














