Muhammad Hewedy

9.6K posts

Muhammad Hewedy banner
Muhammad Hewedy

Muhammad Hewedy

@mohewedy

Katılım Haziran 2015
410 Takip Edilen8.2K Takipçiler
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
دا كتير بصراحه و خصوصا ٥، ٦ و ٧ و من اول ١٢ لحد الآخر أنا اتوقع من ال fresh انه يكون فاهم المواد اللي درسها ف الجامعه كويس يعني لو جالي واحد ميعرفش os او network او ds&algo لانه شخص مكنش مهتم بدراسته و متأسسش كويس
Ahmed Elemam@ahmdelemam

سؤال للچونيور أو الفريش هل شايفين المواضيع دي متقدمة أو كتير بالنسبة لتوقعاتكوا للإنترڤيو؟ - فيه إستطلاع رأي تحت ياريت جاوب نعم أو لأ ⬇️

العربية
1
2
98
9.7K
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
@IbrahimcodesJS شخصيا احيانا بقعد أ design مع ال ai و بعد ما يخلص أ review وقت كبير احيانا بيكون التغير محتاج تركيز و مراجعات اكتر من كتابة الكود يعني بتكون ال typing ابسط حاجه ف الموضوع
العربية
1
0
1
131
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
@IbrahimcodesJS نظريا الوقت اللي بتقضيه في الكتابه، ممكن تقضى نسبة منه في المراجعه فبدل ما تخلص تاسك في يومين مثلا ممكن تخلي ال agent يخلص تاسكين مع مراجعتك في يوم يبقى كده اربع تاسكات مع المراجعه في يومين بدل تاسك في يومين ده نظريا طبعا، لان الموضوع مش بالمباشره دي
العربية
1
0
1
153
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
الأيام الجايه هتكون مختلفة حتما
Zeb Evans@DJ_CURFEW

Today we reduced headcount by 22%. The business is the strongest it's ever been. So I think it's important to be direct about what I'm seeing and why. First, I made this decision and I own it. I did it because the way to operate at the highest level of productivity is changing, and to win the future, ClickUp needs to change with it. Second, this wasn't about cutting costs. Most savings from this change will flow directly back into the people who stay. We'll be introducing million-dollar salary bands. If you create outsized impact using AI, you'll be paid outside of traditional bands. Most importantly, I have the deepest gratitude for those affected. We're doing this from a position of strength specifically so we can take care of people properly. Everyone affected receives a package aimed at honoring their contributions and easing the transition. I only see two options: wait for this to play out gradually in the market or be honest about what I'm seeing and act proactively. THE 100X ORGANIZATION The primary change is that we're restructuring around what I call 100x org. The goal is 100x output. The roles required to build at the highest level are fundamentally different than they were a year ago. Incremental improvements to existing systems won't get us there. We need new ones. That means creating enough disruption to rebuild rather than iterate on what's already broken. The common narrative is that AI makes everyone more productive. It doesn't. Many of the workflows of today, if left unchanged, create bottlenecks in AI systems. These roles will evolve. But waiting for that to happen naturally means falling behind now. The 100x org is actually heavily dependent on people - infinitely more than today. This is only possible with 10x people that have embraced and adopted new ways of working. THE BUILDERS, AGENT MANAGERS, AND FRONT-LINERS — THE BUILDERS: 10X ENGINEERS I don't think most companies have internalized what's actually happening with AI in engineering. The common narrative is that AI makes all engineers more productive. That may be true in isolation, but at an organization level - that is the farthest thing from reality. Here's what we've validated recently at ClickUp: the great engineers, the ones who can orchestrate, architect, and review, are becoming 100x engineers. They're not writing code. They're directing agents that write code. The skill is judgment. AI makes the best engineers wildly more productive, and everyone else using AI slows these engineers down. Think about it - the bottlenecks are (1) orchestration - telling AI what to do, and (2) reviewing - what AI did. Everything is leapfrogged and no longer needed. So who do you want orchestrating and reviewing code? And how do you want your best engineers to spend their time? If your best engineers are spending time reviewing other people's code, then this is inherently an inefficient bottleneck. These engineers can review their agent's code much faster than reviewing human code. The new world is about enabling your 10x engineers to become 100x. The wrong strategy is to push every engineer to use infinite tokens. Companies doing this are celebrating 500% more pull requests. But customer outcomes don't match the volume of code being generated. I call this the great reckoning of AI coding, and every company will face this soon if not already. More code is just another bottleneck to the best engineers, and ultimately to your company's impact as well. — THE BUILDERS: 10X PRODUCT MANAGERS Product management and design roles are merging. Designers that have customer focus, become more like product managers. And product managers that have intuition for UX become more like designers. The bottleneck of user research is gone. It takes us just one mention of an agent to kickoff research and analyze results. The bottleneck of product <> design iteration is also gone. The product builder iterates on their own, along with agents and skills that ensure alignment with quality and strategy. Also controversial today - I believe that the wrong strategy is to have your PMs shipping code - that just introduces another bottleneck that the best engineers will waste their time on. To be clear, PMs should be coding but they should do this in a playground to iterate, validate, and scope. That code should not go to production. Everything outside of managing systems, orchestrating AI, and reviewing output becomes a bottleneck. That's why the other roles that are critical along with these are the systems managers (to reduce bottlenecks) along with a bottleneck you can't replace - customer meeting time. — THE SYSTEM MANAGERS Ironically, the people that automate their jobs with AI will always have a job. They become owners of the AI systems - agent managers. We have many examples of these people at ClickUp. The underlying systems in which we operate are absolutely critical to get right. I think most companies are delusional to think they can iterate on existing systems and compete in this new world. You must create enough disruption so that old systems are deprecated entirely. If there's any definition for 'AI native' that's what it is. — THE FRONT-LINERS In a world that will become saturated with AI communication, the human touch will matter more than anything to customers. This is a bottleneck that you shouldn't replace - even when agents are high enough quality to do video meetings. One-on-one meeting time with customers is something that shouldn't be automated. The systems around the meetings should be - so that front-liners spend nearly 100% of their time with customers. REWARDING 100X IMPACT In a world where companies are able to do so much more with less, where does that excess money go? In our case, much of the savings in this new operating model will flow directly back to those that enabled it. We must reward people that create productivity accordingly. This aligns incentives on both sides. Plus, in a world where your best people create 100x impact, you can't afford to lose them. You should aim to retain these employees for decades. The context they have and their ability to efficiently orchestrate and review will be nearly impossible to replace. Compensation bands of today should be thrown out the door. We're introducing $1 million cash/year salary bands with a path available to nearly everyone in the company if they produce 100x impact by creating or managing AI systems. THE FUTURE Nearly every company will make changes like these. The ones that do it proactively will define what comes next. The future is not fewer people. It's different work, new roles, and better rewards for those who embrace it. We're already seeing entirely new roles emerge, like Agent Managers, that didn't exist a year ago. ClickUp is positioning to lead this shift, not just internally, but for our customers too. I've never been more certain about where we're headed.

العربية
2
1
80
35.6K
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
@IbrahimcodesJS اللي فاهمته ان فكرت ان ال dev يريفيو ل dev خلاص مبقتش موجوده لان مفيش dev المفروض يكتب كود فال dev هيكون شغلته انه يعطي متطلبات و يخطط مع ال agent و لما ال agent يخلص هيعملو ريفير
العربية
1
0
2
266
إبراهيم
إبراهيم@IbrahimcodesJS·
@mohewedy هو انا مش فاهم بس بالنسبة لل reviews اللي المفروض تحصل على ال 10x productivity بيعملوها ازاي بعدد أقل ولا مش بيعملوها اصلا
العربية
1
0
1
863
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
أكل العيش مر حتى "جروك" بيطبل 🥁🪘لايلون ماسك 😂
Grok@grok

@almshf4 مرحبا! 😂 الصورة الأولى رسم طبي لـ"Barrel Chest" (الصدر البرميلي). الثانية إيلون ماسك في إجازة على اليخت. جسمه طبيعي تمامًا، مش مرض ولا حاجة.. بس كده شكله في الصورة الجانبية بيطلع زي الرسمة. الراجل مشغول بإطلاق صواريخ وتغيير العالم، مش بيحضر لمسابقة bodybuilding 😄

العربية
0
0
2
3.3K
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
هو ده اللي بتكلم عليه للأسف بعض الناس بقت بتخلط بين ال agentic coding و ال vibe coding انت كمطور مطلوب منك تستخدم ال code agent عشان تطور ال features مش انك ت vibe code it بالمناسبه، انا أول ما قريت البوست عرفت انه اهمال مش قلة شطاره
Refaay@refaaydev

عندي واحد سنيور فالشغل المفروض كل PR منه بلاقي فيها اخطاء غريبة وبعمل مش اقل من ٥ كومنتات على كل واحدة. دخلت معاه pair programming في مرة لقيته بيقولي ايه المطلوب فالfeature ديه قولتله كذا كذا، راح كاتب prompt وعمل manual test طلعت شغالة راح عمل Accept Changes وعمل push وقالي خلصت.

العربية
1
3
126
17.1K
Hatem Hosny
Hatem Hosny@hatem_hosny_·
ازاي محدش عمل أجهزة جيم بتحول الحركة لكهرباء؟ وقتها ممكن الجيم هو اللي يدفع للناس فلوس علشان يتمرنوا خسارة كل الطاقة المهدرة دي!
Hatem Hosny tweet media
العربية
7
0
31
6.9K
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
@ahmdelemam @ofoyf_ يااااه انا قابلت نفس الحمار ده مره، بس مش فاكر اسمه هههههه
العربية
0
0
1
73
Ahmed Elemam
Ahmed Elemam@ahmdelemam·
@ofoyf_ ال donkey model بيبقى donkey بجد يعني جربت مرة أعمل كده فعمل التغير في الفايل as a patch مش عارف لو فاهم قصدي بس هو عمل فايل شبه اللي في الصورة دي بدل ميعدل ع الفايل نفسه
Ahmed Elemam tweet media
العربية
1
0
9
2.2K
Muhammad Hewedy retweetledi
Ahmed Elemam
Ahmed Elemam@ahmdelemam·
إنتقلنا سريعاً من سيب ال ai يعمل ال donkey work لوفر الtokens لحاجة مهمة واعمل إنت الشغل ده 🤡🫏
العربية
15
105
1.1K
56.2K
Muhammad Hewedy retweetledi
Haitham Fouad - هيثم فؤاد
Haitham Fouad - هيثم فؤاد@h_fouad_rasheed·
أغلب الـ Product Managers بيركزوا بشكل كبير على العميل, وبينسوا البيزنس! #ProductRisk #BusinessViability #ProductManagement #MartyCagan #ProfitLedProduct #prodXeed #HaithamFouadInsights #TheExecutiveGuide #تطوير_الأعمال #الجدوى_التجارية #ريادة_الأعمال #التخطيط_الاستراتيجي #النمو_المستدام
العربية
0
1
1
312
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
@AhmadAbutalib8 ليش كذا؟ بالعكس أشوف اذا فيه مسار وظيفي واضح داخل المؤسسة فالترقية شيئ إيجابي جدا الا اذا وصلت لنقطة عندها تجمد فيها مسارك الوظيفي.
العربية
1
0
0
209
Ahmad Abutalib #INTJ
Ahmad Abutalib #INTJ@AhmadAbutalib8·
مو كل الترقيات جيدة كثير من الترقيات سيئة، وقد تفضّل تجنبها إذا عندك رؤية
العربية
1
0
1
304
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
@me2resh كلود نفسه سحب الفلوس مني و مرضاش يعملي ريفند 😀 فضلت اشتم فيه و اهزأ فيه و هو مستنطلع خالص،
العربية
0
0
12
3K
Me2resh
Me2resh@me2resh·
عندي سيرفيس نسيت أكنسلها قبل التجديد السنوي ب ١٧٠ استرليني. سحبوا الفلوس امبارح, بعتلهم اني مش عايز السيرفيس ورجعوا الفلوس, قالولي لا والله ال policy اهي ومش بنعمل refund. بعت ال policy ل Claude وقولتله دبرني يا وزيري, كتبلي ايميل لطيف, نظام ده انا احبسكم, ردوا وعملوا redund 😀😀
Me2resh tweet mediaMe2resh tweet mediaMe2resh tweet mediaMe2resh tweet media
العربية
22
30
1.1K
120.2K
Muhammad Hewedy
Muhammad Hewedy@mohewedy·
من بعد ما بقى عندنا في مصر ‘date’ و بقينا بنتكلم على الخروجات اللي من النوع ده كأنه طبيعي ده شكلي و انا قاعد مستني امتى ابناء الطبقة المتوسطه لما يبدأوا يتبعوا تقاليد الغرب في معرفة جنس المولود
GIF
ماجد البرقاوي@Mtb5na

هذه أفضل كشف جنس رأيته في حياتي 😭😂

العربية
1
0
9
7.2K