Sign in to view Alexandr’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Alexandr’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Austin, Texas, United States
Sign in to view Alexandr’s full profile
Alexandr can introduce you to 2 people at Seed Hypermedia
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
3K followers
500+ connections
Sign in to view Alexandr’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Alexandr
Alexandr can introduce you to 2 people at Seed Hypermedia
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
View mutual connections with Alexandr
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Sign in to view Alexandr’s full profile
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
About
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
Activity
3K followers
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted thisModern GTM teams are drowning in signals. Market trends. Website behavior. Social engagement. Intent data. Competitor movement. CRM updates. Campaign analytics. The problem isn’t lack of data anymore. It’s that every team sees a different version of reality. Marketing works from campaign dashboards. Sales works from lead lists. RevOps works from attribution models. Leadership works from fragmented reports. And everyone wonders why execution feels disconnected. 𝐓𝐡𝐚𝐭’𝐬 𝐰𝐡𝐲 𝐰𝐞 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐞𝐯𝐞𝐫𝐲 𝐆𝐓𝐌 𝐭𝐞𝐚𝐦 𝐧𝐞𝐞𝐝𝐬 𝐚 𝐟𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧 𝐥𝐚𝐲𝐞𝐫. One intelligent system that: → unifies signals → surfaces real market intelligence → identifies what actually matters → and turns fragmented data into coordinated GTM action That’s what we’re building with OmniSignal. A foundation layer connecting: • trend signals • market intelligence • social data • web behavior • intent signals …into actionable GTM outcomes: → smarter campaigns → better targeting → personalized outreach → higher pipeline → revenue growth 𝐓𝐡𝐞 𝐛𝐞𝐬𝐭 𝐆𝐓𝐌 𝐭𝐞𝐚𝐦𝐬 𝐨𝐟 𝐭𝐡𝐞 𝐧𝐞𝐱𝐭 𝐝𝐞𝐜𝐚𝐝𝐞 𝐰𝐨𝐧’𝐭 𝐣𝐮𝐬𝐭 𝐡𝐚𝐯𝐞 𝐦𝐨𝐫𝐞 𝐀𝐈. They’ll have: 𝐛𝐞𝐭𝐭𝐞𝐫 𝐜𝐨𝐨𝐫𝐝𝐢𝐧𝐚𝐭𝐢𝐨𝐧, 𝐛𝐞𝐭𝐭𝐞𝐫 𝐜𝐨𝐧𝐭𝐞𝐱𝐭, 𝐚𝐧𝐝 𝐨𝐧𝐞 𝐬𝐡𝐚𝐫𝐞𝐝 𝐬𝐨𝐮𝐫𝐜𝐞 𝐨𝐟 𝐭𝐫𝐮𝐭𝐡. Because every GTM move is only as good as the signals behind it. Which GTM signal do you think companies underutilize the most today? 💥 Check https://omnisignal.ai
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted thisMost GTM teams don’t have an execution problem. They have a coordination problem. Inbound is optimizing for content velocity. Outbound is optimizing for meeting volume. Product is optimizing for activation. Leadership is trying to connect the dots manually. The result? Different teams reacting to different realities at the same time. That’s why we believe the next GTM category won’t be another AI writer, SDR copilot, or analytics dashboard. It’ll be the 𝐬𝐢𝐠𝐧𝐚𝐥 𝐥𝐚𝐲𝐞𝐫. The shared intelligence foundation that aligns: • what marketing creates • what sales prioritizes • what customers actually care about • and what the market is signaling in real time At OmniSignal, we’re building exactly that. A system that continuously connects: → market intelligence → trend signals → competitor movement → social intent → inbound performance → outbound timing So inbound and outbound stop operating like separate companies. 𝐓𝐡𝐞 𝐟𝐮𝐭𝐮𝐫𝐞 𝐨𝐟 𝐆𝐓𝐌 𝐢𝐬𝐧’𝐭 𝐦𝐨𝐫𝐞 𝐜𝐨𝐧𝐭𝐞𝐧𝐭. 𝐈𝐭’𝐬 𝐬𝐡𝐚𝐫𝐞𝐝 𝐜𝐨𝐧𝐭𝐞𝐱𝐭. The companies that win in the AI era won’t just move faster. They’ll react to the right signals first. What’s currently missing in your GTM stack: 𝐝𝐢𝐬𝐭𝐫𝐢𝐛𝐮𝐭𝐢𝐨𝐧, 𝐞𝐱𝐞𝐜𝐮𝐭𝐢𝐨𝐧, 𝐨𝐫 𝐢𝐧𝐭𝐞𝐥𝐥𝐢𝐠𝐞𝐧𝐜𝐞? 💥 Check https://omnisignal.ai
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted this𝗘𝘅𝗲𝗰𝘂𝘁𝗶𝗼𝗻 𝗼𝘃𝗲𝗿 𝘁𝗵𝗲𝗼𝗿𝘆. Last week in Barcelona set a new baseline for GTM events. Direct credit to Oriol Serra, Nadja Komnenic, Mina Draskovic, Gary Corcoran, and Bojana Petkovic for engineering a flawless live teardown. 𝗧𝗵𝗲 𝗢𝘂𝘁𝗽𝘂𝘁: A functional outbound system and delivered a highly optimized, cross-platform pipeline architecture in real-time. No theoretical decks – just pure operational mechanics. 𝗧𝗵𝗲 𝗜𝗻𝘀𝗶𝗴𝗵𝘁𝘀: The value of an event is measured by the density of actionable data. Watching the frictionless integration of Clay, HeyReach, Instantly.ai, and HubSpot demonstrated true systems interoperability. It is a rare capability to build in public so effectively. 𝗛𝗶𝗴𝗵-𝗦𝗶𝗴𝗻𝗮𝗹 𝗡𝗲𝘁𝘄𝗼𝗿𝗸𝗶𝗻𝗴 High-signal environments attract high-signal operators. The highest ROI of the night came from the unrecorded, offline discussions after the system breakdown. Exceptional exchanges on scaling, infrastructure, and automation. An optimized outbound engine forces the market to look at you. Capturing and weaponizing that resulting attention is the next logical bottleneck – which is exactly the inbound intelligence loop we are solving at OmniSignal AI. ���� Shout-out to great minds and thanks for interesting conversation during networking evening at the event! Pedro Rubianes and Oriol Serra 🔁 – Unfiltered conversation about industry trends. You're doing great job with The Conversion Architects Nadja Komnenic, Bojana Petkovic – Always energizing to talk with our friends at HeyReach (well-known amazing tool ❤️ for any GTM stack) Daniel (didi) Seror, Jessica Carneiro – exchanged great insights, wish great success to Dolfin 💥 Dima Ivanouski – building interesting tool for instant product demo Naoma AI 👋 Agus Riudavets Melia, Emma Zanini, Yuri Tsverkun
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted thisWe analyzed 𝟯𝟰 enterprise AI post-mortems. In 𝗻𝗼𝘁 𝗼𝗻𝗲 of them did a model fail. 𝗧𝗵𝗲 𝗼𝗿𝗴𝗮𝗻𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗳𝗮𝗶𝗹𝗲𝗱. Companies that "failed at AI" didn't have bad models. They had 𝗯𝗮𝗱 𝗿𝗲𝗮𝗱𝗶𝗻𝗲𝘀𝘀. We tracked 𝟲 𝗱𝗶𝗺𝗲𝗻𝘀𝗶𝗼𝗻𝘀 across every post-mortem: 𝟭. 𝗗𝗮𝘁𝗮 𝗜𝗻𝗳𝗿𝗮𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲 — typical: 35% → required: 80% 𝟮. 𝗜𝗻𝘁𝗲𝗴𝗿𝗮𝘁𝗶𝗼𝗻 𝗗𝗲𝗽𝘁𝗵 — typical: 28% → required: 75% 𝟯. 𝗟𝗮𝘁𝗲𝗻𝗰𝘆 𝗥𝗲𝗾𝘂𝗶𝗿𝗲𝗺𝗲𝗻𝘁𝘀 — typical: 40% → required: 90% 𝟰. 𝗧𝗲𝗮𝗺 𝗥𝗲𝗮𝗱𝗶𝗻𝗲𝘀𝘀 — typical: 22% → required: 70% 𝟱. 𝗙𝗲𝗲𝗱𝗯𝗮𝗰𝗸 𝗟𝗼𝗼𝗽 𝗗𝗲𝘀𝗶𝗴𝗻 — typical: 30% → required: 85% 𝟲. 𝗚𝗼𝘃𝗲𝗿𝗻𝗮𝗻𝗰𝗲 𝗠𝗮𝘁𝘂𝗿𝗶𝘁𝘆 — typical: 18% → required: 65% The gap isn't a technology gap. 𝗜𝘁'𝘀 𝗮𝗻 𝗼𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝗮𝗹 𝗴𝗮𝗽. The question I see teams asking: "𝗪𝗵𝗶𝗰𝗵 𝗺𝗼𝗱𝗲𝗹 𝘀𝗵𝗼𝘂𝗹𝗱 𝘄𝗲 𝗯𝘂𝘆?" The question they should be asking: "𝗔𝗿𝗲 𝘄𝗲 𝗿𝗲𝗮𝗱𝘆 𝘁𝗼 𝗼𝗽𝗲𝗿𝗮𝘁𝗲 𝗮𝗻 𝗔𝗜 𝘀𝘆𝘀𝘁𝗲𝗺 𝗮𝘁 𝗮𝗹𝗹?" Most organizations sit at 𝗟𝟮 — 𝗔𝘀𝗽𝗶𝗿𝗮𝘁𝗶𝗼𝗻𝗮𝗹. Budget. Intent. No operational depth. 𝗟𝟰 — 𝗢𝗽𝗲𝗿𝗮𝘁𝗶𝗼𝗻𝗮𝗹 is where signal AI actually works. The delta between L2 and L4 isn't money. 𝗜𝘁'𝘀 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴. Comment 𝗥𝗘𝗔𝗗𝗜𝗡𝗘𝗦𝗦 and I'll send you the full rubric.
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted this𝗧𝗵𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 𝗼𝗳 𝗠𝗼𝗼𝗻𝘀𝗵𝗼𝘁𝘀: Signals, Strategy, and Going Beyond. 🚀🌑 𝗪𝗵𝘆 𝗮𝗺 𝗜 𝗮𝗻 𝗲𝗻𝗴𝗶𝗻𝗲𝗲𝗿? Engineers dream of solving complex problems. Entrepreneurs dream of scaling those solutions. But space advocates dream of leaving the atmosphere entirely. Today is April 12th – 𝘁𝗵𝗲 𝗗𝗮𝘆 𝗼𝗳 𝗦𝗽𝗮𝗰𝗲. It’s a moment to celebrate humanity's ultimate "launch sequence." This week’s progress with the Artemis II mission (as we look toward returning humans to the Moon) is a profound engineering and visionary milestone that hits home. 🎉 Congrats to NASA - National Aeronautics and Space Administration People often ask why an engineer becomes a serial entrepreneur. To me, they are the same discipline: identifying signals among chaos and building systems that scale. 𝗦𝗽𝗮𝗰𝗲 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴: Calculating trajectories, managing massive amounts of fuel, navigating deep space based on precise telemetry and signals. 𝗕𝟮𝗕 𝗚𝗿𝗼𝘄𝘁𝗵 𝗘𝗻𝗴𝗶𝗻𝗲𝗲𝗿𝗶𝗻𝗴 (where I am now): Navigating a chaotic market, optimizing content vectors, calculating growth trajectories, and finding the high-intent signals that guide B2B strategy. Both are about moving beyond incremental gains and engineering a "𝗺𝗼𝗼𝗻𝘀𝗵𝗼𝘁." As tech co-founder of OmniSignal.AI, I apply that engineering mindset to B2B inbound content strategy. We don't just create content; we find the underlying intelligence – the real-time signals – that tells high-performance companies exactly where they need to go. The photo I’m holding says it all... In strategy, and in exploration, we are always aiming for the Moon. 🚀 𝘏𝘰𝘸 𝘥𝘰 𝘺𝘰𝘶 𝘢𝘱𝘱𝘭𝘺 "𝘮𝘰𝘰𝘯𝘴𝘩𝘰𝘵 𝘵𝘩𝘪𝘯𝘬𝘪𝘯𝘨" 𝘵𝘰 𝘦𝘯𝘨𝘪𝘯𝘦𝘦𝘳𝘪𝘯𝘨 𝘺𝘰𝘶𝘳 𝘮𝘢𝘳𝘬𝘦𝘵 𝘴𝘵𝘳𝘢𝘵𝘦𝘨𝘺? ✝️ Finally, for all my friends, colleagues, and connections celebrating: Congratulating all Orthodox Christians on 𝗘𝗮𝘀𝘁𝗲𝗿/𝗣𝗮𝘀𝗸𝗵𝗮 today! A beautiful confluence of a day celebrating new beginnings and higher callings. #DayOfSpace #ArtemisII #Engineering #Entrepreneurship #OmniSignalAI #Moonshot #GrowthStrategy #OrthodoxEaster #Easter
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted this𝗠𝗼𝘀𝘁 𝗚𝗧𝗠 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 𝗱𝗼𝗻’𝘁 𝗳𝗮𝗶𝗹 𝗯𝗲𝗰𝗮𝘂𝘀𝗲 𝗼𝗳 𝗲𝗳𝗳𝗼𝗿𝘁. They fail because of 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝘀𝘁𝗿𝘂𝗰𝘁𝘂𝗿𝗲. Teams run: • content on LinkedIn for Marketing, YouTube, Spotify • ads via Google Ads, Meta for Business • outbound with LinkedIn for Sales, WhatsApp for Business • partnerships through Slack, Webflow 𝗕𝘂𝘁 𝗻𝗼𝘁𝗵𝗶𝗻𝗴 𝗶𝘀 𝘁𝗿𝘂𝗹𝘆 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗲𝗱. So results stay 𝘂𝗻𝗽𝗿𝗲𝗱𝗶𝗰𝘁𝗮𝗯𝗹𝗲. ⸻ 𝗧𝗵𝗲 𝘁𝗼𝗽 𝟭% 𝗚𝗧𝗠 𝘁𝗲𝗮𝗺𝘀 𝘁𝗵𝗶𝗻𝗸 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁𝗹𝘆. They don’t build stacks. They build 𝗳𝗹𝗼𝘄𝘀. 𝗔 𝗿𝗲𝗮𝗹 𝘀𝘆𝘀𝘁𝗲𝗺 ����𝗼𝗼𝗸𝘀 𝗹𝗶𝗸𝗲 𝘁𝗵𝗶𝘀: 1️⃣ 𝗧𝗿𝗮𝗳𝗳𝗶𝗰 𝗴𝗲𝗻𝗲𝗿𝗮𝘁𝗶𝗼𝗻 Thought leadership + paid media + outreach + partnerships 2️⃣ 𝗦𝗶𝗴𝗻𝗮𝗹 𝗰𝗮𝗽𝘁𝘂𝗿𝗲 Audience building + warm interactions + gated assets 3️⃣ 𝗖𝗼𝗻𝘃𝗲𝗿𝘀𝗶𝗼𝗻 𝗹𝗮𝘆𝗲𝗿 Website with clear: • positioning • social proof • product understanding 4️⃣ 𝗔𝗰𝘁𝗶𝘃𝗮𝘁𝗶𝗼𝗻 𝗽𝗮𝘁𝗵𝘀 Self-serve via tools like Stripe or product-led flows Sales-led via CRM like HubSpot or Salesforce 5️⃣ 𝗣𝗶𝗽𝗲𝗹𝗶𝗻𝗲 → 𝗿𝗲𝘃𝗲𝗻𝘂𝗲 ⸻ 𝗧𝗵𝗲 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲 𝗶𝘀 𝘀𝗶𝗺𝗽𝗹𝗲: 𝗔𝘃𝗲𝗿𝗮𝗴𝗲 𝗚𝗧𝗠 = activity 𝗧𝗼𝗽 𝟭% 𝗚𝗧𝗠 = 𝗰𝗼𝗻𝗻𝗲𝗰𝘁𝗲𝗱 𝘀𝘆𝘀𝘁𝗲𝗺 ⸻ 𝗠𝗼𝘀𝘁 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝗮𝗹𝗿𝗲𝗮𝗱𝘆 𝗵𝗮𝘃𝗲 𝘁𝗵𝗲 𝘁𝗼𝗼𝗹𝘀. 𝗪𝗵𝗮𝘁 𝘁𝗵𝗲𝘆’𝗿𝗲 𝗺𝗶𝘀𝘀𝗶𝗻𝗴 𝗶𝘀: → 𝗵𝗼𝘄 𝘁𝗵𝗼𝘀𝗲 𝘁𝗼𝗼𝗹𝘀 𝘄𝗼𝗿𝗸 𝘁𝗼𝗴𝗲𝘁𝗵𝗲𝗿 → 𝘄𝗵𝗲𝗻 𝘁𝗼 𝗮𝗰𝘁𝗶𝘃𝗮𝘁𝗲 𝗲𝗮𝗰𝗵 𝗰𝗵𝗮𝗻𝗻𝗲𝗹 → 𝗵𝗼𝘄 𝘁𝗼 𝘁𝘂𝗿𝗻 𝘀𝗶𝗴𝗻𝗮𝗹𝘀 𝗶𝗻𝘁𝗼 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 ⸻ 𝗧𝗵𝗮𝘁’𝘀 𝘄𝗵𝗲𝗿𝗲 𝘁𝗵𝗶𝗻𝗴𝘀 𝘀𝘁𝗮𝗿𝘁 𝗰𝗼𝗺𝗽𝗼𝘂𝗻𝗱𝗶𝗻𝗴. ⸻ Curious: 👉 𝗪𝗵𝗶𝗰𝗵 𝗽𝗮𝗿𝘁 𝗼𝗳 𝘁𝗵𝗶𝘀 𝘀𝘆𝘀𝘁𝗲𝗺 𝗶𝘀 𝘄𝗲𝗮𝗸𝗲𝘀𝘁 𝗶𝗻 𝘆𝗼𝘂𝗿 𝗰𝗼𝗺𝗽𝗮𝗻𝘆 𝗿𝗶𝗴𝗵𝘁 𝗻𝗼𝘄? 👇
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted thisMost sales teams don’t have a 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 problem. They have a 𝗌𝗂𝗀𝗇𝖺𝗅 problem. Too much activity. Not enough clarity. So if you want to actually understand what’s working in 2026… 𝗦𝘁𝗼𝗽 𝗴𝘂𝗲𝘀𝘀𝗶𝗻𝗴. 𝗦𝘁𝗮𝗿𝘁 𝗹𝗲𝗮𝗿𝗻𝗶𝗻𝗴 𝗳𝗿𝗼𝗺 𝗼𝗽𝗲𝗿𝗮𝘁𝗼𝗿𝘀. Here are 10 creators worth following right now 👇 • Jérémy Grandillon — practical outbound systems • Michel Lieben 🧠 — modern prospecting & content • Alex Vacca 🧠🛠️ — GTM + pipeline thinking • Melissa Gaglione ⭐️ — human-first sales strategy • Morgan J Ingram — social selling & conversations • Kyle Coleman — pipeline + revenue systems • Becc Holland — buyer psychology & messaging • Chris Orlob — execution & deal mechanics • Florin Tatulea — demand + GTM strategy ⸻ What I like about this group: They don’t talk about “𝗵𝗮𝗰𝗸𝘀.” They talk about: • 𝗿𝗲𝗽𝗲𝗮𝘁𝗮𝗯𝗹𝗲 𝘀𝘆𝘀𝘁𝗲𝗺𝘀 • 𝗿𝗲𝗮𝗹 𝗰𝗼𝗻𝘃𝗲𝗿𝘀𝗮𝘁𝗶𝗼𝗻𝘀 • 𝗽𝗶𝗽𝗲𝗹𝗶𝗻𝗲 𝗺𝗲𝗰𝗵𝗮𝗻𝗶𝗰𝘀 • 𝘄𝗵𝗮𝘁 𝗮𝗰𝘁𝘂𝗮𝗹𝗹𝘆 𝗺𝗼𝘃𝗲𝘀 𝗱𝗲𝗮𝗹𝘀 That’s the shift happening right now. Sales is becoming: → 𝗹𝗲𝘀𝘀 𝘃𝗼𝗹𝘂𝗺𝗲 → 𝗺𝗼𝗿𝗲 𝘁𝗶𝗺𝗶𝗻𝗴 → 𝗺𝗼𝗿𝗲 𝘀𝗶𝗴𝗻𝗮𝗹𝘀 ⸻ If you’re building outbound, inbound, or something in between… 𝗧𝗵𝗶𝘀 𝗶𝘀 𝘁𝗵𝗲 𝗹𝗮𝘆𝗲𝗿 𝘁𝗵𝗮𝘁 𝗺𝗮𝘁𝘁𝗲𝗿𝘀 👇 👉 who do you think is missing from this list? ⚡
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted this"𝗔𝗜 𝗵𝗮𝘀 𝗻𝗼 𝗯𝗮𝗹𝗹𝘀" – the bottleneck preventing AGI and stalling productivity AI set 𝗲𝘅𝗽𝗲𝗰𝘁𝗮𝘁𝗶𝗼𝗻𝘀 so high we treat it as a partner. Yet, endow it with 𝗿𝗲𝘀𝗽𝗼𝗻𝘀𝗶𝗯𝗶𝗹𝗶𝘁𝘆, and it fails. It devolves from reliable teammate to novice intern requiring relentless 𝗺𝗶𝗰𝗿𝗼-𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 By "no balls," I mean it lacks a soul, self-identification, and a strategic vector. Zero intrinsic motivation or conviction As a CTO spending $250+ daily on tokens to build complex products, the data is clear: current models lack agency. The reality of "𝗦𝘁𝗮𝘁𝗲-𝗼𝗳-𝘁𝗵𝗲-𝗔𝗿𝘁" LLMs: - Zero Pushback: Pure compliance. It accepts flawed instructions without challenging the premise. A yes-man, not a sparring partner - Premature Execution: Faced with missing input, humans interview you. AI jumps into execution, guessing variables instead of mapping dependencies - Paradox of Infinite Knowledge: Knowing everything means having no strict opinion. It defaults to the average path instead of defending an optimal solution - No Fundamental Truth: LLMs blindly trust consensus, adopting poorly written "expert" posts as absolute truth without verifying reality - Abysmal Tool Utilization: Agents have vast toolsets but lack reasoning to select the right one, settling for "good enough" - Avoidance of Hard Decisions: Agency requires responsibility. AI shifts accountability to the user when a hard choice arises - The "Continue" Loop: Throw a complex task at an agent and it completes 30%. You are forced into an endless loop of typing "continue" - The Missing Q-Value: Ilya Sutskever noted the human brain uses emotion in its Q-value function to drive action. AI lacks this; it does not care about output quality The 𝗣𝗶𝘃𝗼𝘁𝗮𝗹 𝗠𝗼𝗺𝗲𝗻𝘁: We are trapped. Multi-agent systems replace a 6-month dev cycle with a few hours, but catastrophic quality drops make you want to throw your machine out the window. Old ways are gone, but new ways are broken 𝗧𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗕𝗼𝘁𝘁𝗹𝗲𝗻𝗲𝗰𝗸𝘀: - Context Scaling is a Dead End: Layering RAG or Vector DBs is insufficient. Retrieval fragmentation destroys logical cohesion - Parameter Bloat: 1T+ parameters yield diminishing returns. We are scaling memorization, not logic - System 1 vs 2 Imbalance: Models excel at fast generation but fail at multi-step planning and backtracking - Stateful Memory Failure: Long-term memory over-summarizes, losing stateful persistence and disconnecting from the task 𝗙𝗼𝗿𝗲𝗰𝗮𝘀𝘁: - Devs are burning out managing systems that refuse to be autonomous - Psychologists will pivot to "family therapy" to fix the toxic human-AI relationship - In 2026, the Words of the Year will be "Continue" and "WTF" - place bets on Polymarket "The AI assistant is a terrible employee you cannot fire, yet are forced to guide" Garry Tan (Y Combinator CEO) recently shared gstack, his framework for navigating this What is your holy grail formula for forcing actual agency out of these models?
-
Alexandr Burdiyan reposted thisAlexandr Burdiyan reposted thisThe "mid-pack" 𝗕𝟮𝗕 𝘀𝗮𝗹𝗲𝘀 𝗿𝗲𝗽𝗿𝗲𝘀𝗲𝗻𝘁𝗮𝘁𝗶𝘃𝗲 is officially 𝗼𝗯𝘀𝗼𝗹𝗲𝘁𝗲. Top voices in the SaaS ecosystem, including Jason M. Lemkin, are finally saying out loud what the performance data has shown for the last six months. A standard AI SDR now vastly outperforms the 50th percentile of human sales professionals. Look at the 𝗯𝗿𝘂𝘁𝗮𝗹 𝟮𝟬𝟮𝟲 𝗽𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲 delta: 📉 Human SDR Contact Rate: 20-30% 🚀 AI SDR Contact Rate: 40-55% 📉 Human Meeting Booked Rate: 6-12% 🚀 AI Meeting Booked Rate: 12-25% The traditional SaaS model of paying a junior representative $60k+ a year to manually research accounts, write generic "Hope you're well" emails, and track pipeline in a messy spreadsheet is hemorrhaging capital. 𝗧𝗵𝗲 𝟮𝟬𝟮𝟲 𝗥𝗲𝘃𝗲𝗻𝘂𝗲 𝗣𝗹𝗮𝘆𝗯𝗼𝗼𝗸: The future belongs exclusively to the 50/50 hybrid team and the elite "$250k SDR" who knows how to wield autonomous tools. 𝘈𝘶𝘵���𝘮𝘢𝘵𝘦 𝘵𝘩𝘦 𝘊𝘰𝘯𝘯𝘦𝘤𝘵𝘪𝘷𝘦 𝘛𝘪𝘴𝘴𝘶𝘦: Deploy end-to-end autonomous marketing agents to handle all top-of-funnel strategy, content creation, and initial signal detection. 𝘐𝘥𝘦𝘯𝘵𝘪𝘧𝘺 𝘞𝘢𝘳𝘮 𝘓𝘦𝘢𝘥𝘴 𝘪𝘯 𝘵𝘩𝘦 𝘚𝘩𝘢𝘥𝘰𝘸𝘴: Let the algorithm do the qualification. High-intent buyers reveal themselves through content engagement and comment activity long before they ever fill out a demo form. CrossLike.club is engineered to surface these exact signals automatically. 𝘌𝘭𝘦𝘷𝘢𝘵𝘦 𝘵𝘩𝘦 𝘏𝘶𝘮𝘢𝘯 𝘌𝘭𝘦𝘮𝘦𝘯𝘵: Reserve your expensive human capital exclusively for complex discovery, strategic relationship building, objection handling, and final negotiation. Stop hiring headcount to solve pipeline velocity problems. Build an autonomous engine that delivers a consistent pipeline of qualified interest with minimal human oversight. Let the machines handle the outreach volume. Let the humans close the deals. 𝗪𝗵𝗮𝘁 𝗽𝗲𝗿𝗰𝗲𝗻𝘁𝗮𝗴𝗲 𝗼𝗳 𝘁𝗵𝗲 𝗼𝘂𝘁𝗯𝗼𝘂𝗻𝗱 𝗺𝗼𝘁𝗶𝗼𝗻 𝘄𝗶𝗹𝗹 𝗯𝗲 𝗳𝘂𝗹𝗹𝘆 𝗮𝘂𝘁𝗼𝗺𝗮𝘁𝗲𝗱 𝗯𝘆 𝟮𝟬𝟮𝟳? The debate starts in the comments. #SalesTech #GTM #B2BSales #ArtificialIntelligence #CrossLike
-
Alexandr Burdiyan liked thisWe are working so hard to make this industry better. We are seeing real savings and providing people with a better tool. Most recently, we saved a company almost $22,000 on their Docusign renewal and had them up and running in less than a week. If any of these points ring true to you... let's have a chat! #ThePropperWayAlexandr Burdiyan liked thisThe eSignature industry is overdue for a reset. *************************** Most platforms still suffer from the same core problems: Pricing that scales with usage, not value Rigid, linear workflows Documents trapped as static PDFs Shallow, rules-based automation Painful integrations and vendor lock-in BOOK A DEMO - https://propper.ai/demo In other words: they capture signatures, but don’t actually manage agreements. Propper AI flips that model. With unlimited usage, programmable workflows, a unified document data model, AI-driven automation, and seamless migration from legacy tools - it's not just eSign, it’s agreement infrastructure. The category isn’t evolving. It’s being rebuilt. BOOK A DEMO - https://propper.ai/demo #ThePropperWay #BookADemo #IAM
-
Alexandr Burdiyan liked thisAlexandr Burdiyan liked thisVous avez présenté une offre solide. Votre interlocuteur finlandais a semblé poli. Et puis — plus rien. Pas de refus. Pas d'explication. Juste le silence. Ce silence, beaucoup de dirigeants export l'ont interprété comme une hésitation temporaire. Ce n'en était pas une. C'était une décision déjà prise. En contexte finlandais (et plus largement nordique), la communication indirecte n’est pas un obstacle conjoncturel. C’est une norme relationnelle. Souvent, ce silence veut dire : - la décision est « plutôt non », mais sans confrontation directe - le dossier est reparti en circuit interne (process, conformité, achats) - le consensus n’est pas atteint côté client - votre offre ne « fitte » pas totalement avec leurs priorités - personne n’ose rouvrir le sujet, donc il s’éteint… sans mail de refus Les erreurs à éviter : - relancer de façon insistante comme si c’était un simple oubli - interpréter la politesse comme un signal d’enthousiasme - supposer que « pas de nouvelles = on réfléchit encore » Quelques réflexes concrets à adopter : - avant de clôturer l’échange : cadrer clairement le next step, la timeline et les décisionnaires - envoyer un email de récap (besoin, options, critères, échéance) - proposer 2–3 créneaux précis pour la suite, pas un flou du type « on se recontacte » - poser une question binaire avec deadline : « pouvons-nous considérer un go / no-go d’ici le… ? » - offrir une porte de sortie élégante : « si ce n’est pas le bon timing, dites-le-nous clairement » Vu de France, ce silence est frustrant. Vu de Finlande, d’Estonie ou de Scandinavie, c’est souvent un message. À vous d’installer le cadre pour qu’il puisse être formulé clairement. #export #venteB2B #Nordics #Finlande #communicationinterculturelle #marketingexport
-
Alexandr Burdiyan liked thisAlexandr Burdiyan liked thisI met Yat Siu at Consensus last week. No pitch. No panel. Just a real conversation about what it actually takes to deploy agentic infra at scale and not lose your mind doing it. He runs 200 agents. I run 37. What impressed me most? Still hungry. Still building. Still open. After everything he's built. He handed me his card before I asked. That kind of openness is rare at that level. That's the thing about real builders. The scale changes. The energy doesn't. 37 today. Watch what's next. Thursday I'm dropping something for the people building agents and beyond.
-
Alexandr Burdiyan liked thisAlexandr Burdiyan liked thisI realized recently that I’ve been treating my burnout like a badge of honor instead of a warning sign that something is broken. There’s this toxic pressure to "out-hustle" every obstacle, but I’m learning that you can’t pour from an empty cup, no matter how hard you work. Is "the grind" actually building your dream, or is it slowly dismantling the person who started it?
-
Alexandr Burdiyan reacted on thisAlexandr Burdiyan reacted on thisModern GTM teams are drowning in signals. Market trends. Website behavior. Social engagement. Intent data. Competitor movement. CRM updates. Campaign analytics. The problem isn’t lack of data anymore. It’s that every team sees a different version of reality. Marketing works from campaign dashboards. Sales works from lead lists. RevOps works from attribution models. Leadership works from fragmented reports. And everyone wonders why execution feels disconnected. 𝐓𝐡𝐚𝐭’𝐬 𝐰𝐡𝐲 𝐰𝐞 𝐛𝐞𝐥𝐢𝐞𝐯𝐞 𝐞𝐯𝐞𝐫𝐲 𝐆𝐓𝐌 𝐭𝐞𝐚𝐦 𝐧𝐞𝐞𝐝𝐬 𝐚 𝐟𝐨𝐮𝐧𝐝𝐚𝐭𝐢𝐨𝐧 𝐥𝐚𝐲𝐞𝐫. One intelligent system that: → unifies signals → surfaces real market intelligence → identifies what actually matters → and turns fragmented data into coordinated GTM action That’s what we’re building with OmniSignal. A foundation layer connecting: • trend signals • market intelligence • social data • web behavior • intent signals …into actionable GTM outcomes: → smarter campaigns → better targeting → personalized outreach → higher pipeline → revenue growth 𝐓𝐡𝐞 𝐛𝐞𝐬𝐭 𝐆𝐓𝐌 𝐭𝐞𝐚𝐦𝐬 𝐨𝐟 𝐭𝐡𝐞 𝐧𝐞𝐱𝐭 𝐝𝐞𝐜𝐚𝐝𝐞 𝐰𝐨𝐧’𝐭 𝐣𝐮𝐬𝐭 𝐡𝐚𝐯𝐞 𝐦𝐨𝐫𝐞 𝐀𝐈. They’ll have: 𝐛𝐞𝐭𝐭𝐞𝐫 𝐜𝐨𝐨𝐫𝐝𝐢𝐧𝐚𝐭𝐢𝐨𝐧, 𝐛𝐞𝐭𝐭𝐞𝐫 𝐜𝐨𝐧𝐭𝐞𝐱𝐭, 𝐚𝐧𝐝 𝐨𝐧𝐞 𝐬𝐡𝐚𝐫𝐞𝐝 𝐬𝐨𝐮𝐫𝐜𝐞 𝐨𝐟 𝐭𝐫𝐮𝐭𝐡. Because every GTM move is only as good as the signals behind it. Which GTM signal do you think companies underutilize the most today? 💥 Check https://omnisignal.ai
-
Alexandr Burdiyan reacted on thisAlexandr Burdiyan reacted on thisMost teams don’t fail at $1M ARR because of bad outreach. They fail because their GTM system has no foundation. Content gets published without market timing. Outbound runs without intent signals. Sales chases accounts that were never warmed up. Marketing celebrates impressions while pipeline stays flat. Everyone is executing. Nobody is synchronized. The companies breaking through right now all have one thing in common: 𝐓𝐡𝐞𝐲 𝐨𝐩𝐞𝐫𝐚𝐭𝐞 𝐨𝐧 𝐚 𝐬𝐡𝐚𝐫𝐞𝐝 𝐢𝐧𝐭𝐞𝐥𝐥𝐢𝐠𝐞𝐧𝐜𝐞 𝐥𝐚𝐲𝐞𝐫. That’s the missing GTM foundation. Here’s the pipeline we see working repeatedly for early-stage SaaS teams: 1️⃣ Build a signal foundation Track trend signals, competitor movement, market conversations, social intent, and audience behavior in one place. 2️⃣ Turn signals into strategic content Not random posting. Content engineered around active demand and ICP attention shifts. 3️⃣ Identify engaged accounts Website visitors, engaged profiles, warm interactions, repeat viewers. 4️⃣ Activate outbound at the right timing Personalized outreach triggered by actual buying signals instead of static lead lists. 5️⃣ Convert warm attention into meetings Because outbound performs exponentially better when inbound created familiarity first. 𝐈𝐧𝐛𝐨𝐮𝐧𝐝 𝐚𝐧𝐝 𝐨𝐮𝐭𝐛𝐨𝐮𝐧𝐝 𝐬𝐡𝐨𝐮𝐥𝐝𝐧’𝐭 𝐛𝐞 𝐭𝐰𝐨 𝐬𝐞𝐩𝐚𝐫𝐚𝐭𝐞 𝐬𝐲𝐬𝐭𝐞𝐦𝐬. They should compound each other. That’s the idea behind OmniSignal: A GTM foundation layer connecting market intelligence → content → intent → outreach → pipeline. 𝐓𝐡𝐞 𝐧𝐞𝐱𝐭 𝐰𝐚𝐯𝐞 𝐨𝐟 𝐆𝐓𝐌 𝐰𝐨𝐧’𝐭 𝐛𝐞 𝐦𝐨𝐫𝐞 𝐭𝐨𝐨𝐥𝐬. 𝐈𝐭’𝐥𝐥 𝐛𝐞 𝐛𝐞𝐭𝐭𝐞𝐫 𝐬𝐢𝐠𝐧𝐚𝐥 𝐜𝐨𝐨𝐫𝐝𝐢𝐧𝐚𝐭𝐢𝐨𝐧. What’s currently the weakest part of your GTM pipeline right now? 💥 Check https://omnisignal.ai
Experience & Education
-
Mintter Technologies
**********
-
******
******** ********
-
******** **********
******** ********
-
******
****** ******** ************ undefined
-
-
****
****** ******* **********
-
View Alexandr’s full experience
See their title, tenure and more.
Welcome back
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
Languages
-
Russian
-
-
English
-
-
Spanish
-
View Alexandr’s full profile
-
See who you know in common
-
Get introduced
-
Contact Alexandr directly
Other similar profiles
Explore more posts
-
Radek Míka
Cookielab.io • 3K followers
It’s the quality of your codebase that decides whether your project scales or breaks. In our latest article, Patrik Dvořáček shares how switching from ESLint to 𝗕𝗶𝗼𝗺𝗲 helped us build faster, cleaner, and more consistent TypeScript projects. 🚀 You’ll learn: • Why code quality pays off in the long run • How integrated linting improves developer experience • The three pillars of our Biome config: 𝗦𝗮𝗳𝗲𝘁𝘆, 𝗣𝗲𝗿𝗳𝗼𝗿𝗺𝗮𝗻𝗰𝗲, 𝗗𝗲𝘃𝗲𝗹𝗼𝗽𝗲𝗿 𝗘𝘅𝗽𝗲𝗿𝗶𝗲𝗻𝗰𝗲 And yes - it’s open-source! 🔗 @cookielab.io/biome-config ➡️ Just install it, use it, and enjoy a cleaner, faster, more consistent TypeScript project. 👉 Full article: https://bit.ly/4oSyNOE If you’re thinking about long-term code sustainability in your team, reach out to me. We’ll be happy to help.
4
-
Rajasegar Chandran
Caterpillar Inc. • 3K followers
Anders Hejlsberg began working on TypeScript in 2012 with a specific goal in mind: addressing a practical challenge rather than creating a competitor to JavaScript. At that time, JavaScript was pivotal to web development, yet it faced limitations in scaling for extensive, collaborative code projects. The industry witnessed the delivery of vast amounts of weakly typed code, leading to complexity beyond manageability as systems expanded. https://lnkd.in/guf6_kEu #javascript #frontend #typescript #ai
8
-
Cassiano Ferro Moraes
WriteChoice • 3K followers
Every robust API comes with a challenge. How do you make it understandable for any team, anywhere? The documentation for Yuno was built with that goal in mind. It wasn’t about stacking pages. It was about designing a clear, scalable and functional experience. The work required more than technical skills. It meant understanding the product, the business and the journey of those on the other side. Developers who need speed, predictability and confidence. Documentation is not the final step. It’s what connects a great API to its real adoption potential.
8
-
David Barlev
Goji Labs • 9K followers
Ruby on Rails is dead… if you like chasing hype. But Rails is still one of the best frameworks out there. Change my mind. It may not be the Hacker News darling anymore, but if you care about building real products fast, Rails still rules. Here’s why. 1. Speed Rails comes with scaffolding, routing, testing, background jobs—you name it. We’ve helped clients launch full MVPs in weeks using Rails, while others are still hiring for their third backend dev. Time to market matters; Rails cuts that down. 2. Lean Rails lets a small team punch above their weight. A few developers (or a single) can tap into a massive ecosystem of open-source gems. We’ve seen it power education platforms, healthcare dashboards, and nonprofit tools with tight timelines and budgets. 3. Plugins A huge open-source network of plugins lets you focus on features instead of infrastructure. 5. Actually does scale Shopify serves billions of requests per day on Rails. GitHub still runs on it. Anyone saying it doesn’t scale can go talk to them. But if you are looking for the cool new thing, sure, Ruby on Rails is “dead”.
17
2 Comments -
Jonathan Hiltser
Blue Badger • 3K followers
One of the magical things about Agentic development is that previously there was way too little time for documentation and now there is a mandatory need to document extensively ahead of development if you want to get the best results. The funny thing is that most developers are just really bad at doc (which makes sense since they don't practice), so much so that they do not know how to approach it. On top of the regular complexity you also have to add that documenting things for LLM-coding requires subdividing the work into chunks that can fit into the context an agent can fit into it's memory. There are even strategies for optimizing memory utilization to leave more tokens for execution. I'm curious, what documentation style have you found that drives the best outcomes when working with LLMs to write code?
8
10 Comments -
PSBigBig OneStarDao
OneStarDao • 211 followers
hi, I’m PSBigBig, an indie dev and author of WFGY on GitHub (about 1.5k★ right now). Recently I see more and more people exploring openClaw. From my view, openClaw itself is a very strong agent system. Many engineers start with a few small tasks, then slowly plug in tools, data sources and workflows. After some time it turns into a full AI pipeline almost automatically. The pain starts when you add RAG + vector stores + tools into that same agent. Once answers become weird or hallucinated, it is very hard to say which layer actually failed. People only feel “something is off” but cannot point to the real cause. For this reason I maintain a “RAG 16-problem checklist”. You can treat it as a semantic firewall around any RAG or agent pipeline. Before you design a new flow in openClaw, or when your existing pipeline begins to misbehave, you can walk through these 16 slots one by one. It covers things like data ingestion, chunking, embeddings, vectorstore settings, prompt design, tool routing and evaluation. The goal is to give a concrete name to each failure mode and a clear direction for the fix, instead of blind guessing. This checklist is already referenced by several academic and open source ecosystems, including Harvard MIMS Lab’s ToolUniverse, the Multimodal RAG Survey from QCRI LLM Lab, and a few large AI / data-science awesome lists. They use it as a RAG debugging and stress-testing reference, so it is not only my personal opinion that it is useful. You can see the full list here: https://lnkd.in/gWTrxu5n If you are using openClaw for things like building RAG knowledge bases for docs or wikis wiring multiple tools and data sources into one agent running support bots, internal assistants or monitoring agents then this page is meant to be a drop-in checklist. When an agent reply goes wrong, you can quickly map it to one of the 16 problems and debug from there. Everything is MIT licensed. You can copy the checklist into internal docs, adapt it to your own style, or treat it as part of your openClaw runbook. WFGY (“萬法歸一”) itself is a bigger project focused on underlying reasoning engines and semantic diagnostics. There are other experimental modules inside, but for the openClaw community I think this 16-problem RAG map is the most practical starting point. If anyone here is curious or already struggling with agent + RAG reliability, I am happy to answer questions and see how this can fit into real openClaw workflows.
1
-
Jouke Visser
I am a senior technology… • 2K followers
In the past few weeks I've been calling old contacts to understand how things work in their organization when it comes to Frontend Development. This is what strikes me most. I've had dozens of these calls lately, obviously to validate my own ideas about Frontend Platforms, and to get a feel about how to bring my message across for FrontenderZ. The good news is that most people I talk to, recognize the issues that come with distributed development, compatibility between different projects and teams, framework churn, dependency management, and testing strategy. They do feel that these things are slowing down their delivery. What strikes me most though, is that many still consider these development teams as a cost center. They may not say it out loud, but it seems that ideas to invest in ways to speed up delivery are quickly dismissed as too costly, too distracting from what they're supposed to do. Having a couple of senior engineers trying to keep things aligned between teams may work for a while. Ignoring the increasing incompatibilities between different frontend systems may help you go fast for a little while. But it does not scale. Your product teams are your money making machines. Let them focus on adding value. Let your platform take care of the rest.
7
2 Comments -
Jerzy Biernacki
Comarch • 13K followers
The Sora Android app was shipped in 28 days by just 4 people. But if you think this is proof you can replace your dev team with AI, think again. They actually tried it first and failed miserably. Why? Because they were asking the AI to be an architect, when it is actually a builder. To fix it, they stopped coding for a week. They focused entirely on structure, rigid modules, and documentation for the AI. They stopped treating it like a magic wand and started treating it like a junior developer who needs strict guidance. They stopped treating the AI like a magic wand and started treating it like a very fast junior developer who needs clear instructions. Once they laid that foundation, the results were incredible. ➡️ 85% of the code was generated by AI ➡️ 99.9% stability rate ➡️ 4 people did the work of a massive team This tells us exactly where the future of our role lies. We are done with the era of manual implementation. The new reality is about architecture and orchestration. If your architecture is messy, AI will just produce chaos at record speed. But if your structure is clear, AI becomes the ultimate multiplier. The bottleneck isn't typing anymore. It is clarity. How is your team adapting? #AI #SoftwareEngineering
52
9 Comments -
Adam Piotrowski
2N IT sp. z o.o. • 3K followers
I just returned from BalticRuby and a great talk by Tim Riley about #hanami, #dry.rb, and #rom that reminded me how important it is to have a variety of tools that allow for different approaches to different problems. And one day later, Andrzej Krzywda shared his excellent presentation about RES and the whole Event Sourcing idea, implemented into the Ruby language toolset. That, combined with an awesome presentation from Yukihiro Matsumoto, why Ruby is great for the AI age, and information about how RubyGems are increasing Ruby ecosystem security and reliability each day (by Marty Haught ), makes me see the future of Ruby in really bright colors. #ruby #rubyOnRails
18
-
Alex Sadlovskyi
Linkup ST • 2K followers
🧭 Why Most SaaS MVPs Fail Before the First Line of Code Most SaaS MVPs don’t fail because of bad engineering. They fail because the first decisions were wrong. Before code. Before design. Before speed. The real question isn’t how fast can we build. It’s what exactly are we trying to solve - and for whom. Teams often get stuck asking: Who should we hire first? A business analyst? A designer? A developer? Or can AI replace part of this now? The answer usually isn’t a role. It’s clarity. Strong MVP teams align early on: • the problem worth solving • the user who feels it most • what not to build in v1 Only then do tools, roles, and AI actually help. AI can accelerate thinking. It can’t replace it. Design can reduce friction. It can’t fix a wrong problem. Code can move fast. It can’t create clarity retroactively. The teams that build useful MVPs don’t overhire. They combine clear problem framing, lightweight design, and selective use of AI - intentionally. MVP success is less about velocity. More about direction. #SaaS #MVP #ProductStrategy #Startups #AI #ProductThinking
2
-
Bhishan Bhandari
YaYpply • 2K followers
I built something cool. Nobody needed it. It worked beautifully. It used cool libraries. It felt right in the IDE. But in the real world? No one cared. Not because it was bad - but because it didn’t solve a burning problem. I’ve learned this lesson more than once: I picked up on this not so helpful habit while I was running a programming blog many years ago. At the time it meant a new content, at best would pick up traffic- make me some adsense dollars, at worst- no traffic. Nothing much to win or lose. Overtime, I have learnt: Iteration > Starting I was always asking the wrong question - Is this technically interesting? The right question - Will someone’s day get better with this? I still build things that excite me. But now, I only keep going when they excite someone else too.
10
3 Comments -
Saqib Iqbal
SofteVerse • 7K followers
Initially, it was said that rising unemployment among software developers was due to over-hiring. Empirical evidence now shows that this is not the case; in fact, areas such as software developers (juniors) and customer service are seeing rising unemployment. In other words, there is hardly any demand for new entrants to the software and customer service sectors. Dario Amodei has warned of this impending unemployment. #jobs #usa #devs #ai #dubai #tech #data
1
-
Tessa Kriesel
Mozilla • 6K followers
99 Dev Problems with Rasmus Makwarth 99 Dev Problems features candid developer conversations on challenges, career growth, and tech trends. With insights, stories, and solutions from those in the field, it’s authentic tech talk for seasoned engineers and newcomers alike. Tune in for real-world coding and career advice. #99devproblems
3
-
Vasiliy Zukanov
Android Freelancer • 7K followers
KMP app: 0 automated tests, Cursor wrote more than 50% of the code (90%+ of the UI logic). Backend: 94% line coverage, I wrote every line of code and tests myself (incl. copy-paste). At this point, owning every line of the BE codebase gives me confidence and peace of mind. The freedom to add features, refactor and change stuff in the backend code, without fear or hesitation, as a result of having a high-quality suite of automated tests, is something I wish every developer would get to feel in their career. It changes you, in a good way.
86
6 Comments -
Felipe S.
TrueDial • 3K followers
Funny watching big companies dunk on “vibe coded startups” like they just exposed something. “You can’t build stable systems like that.” “Won’t scale.” “Not production-ready.” No shit. That’s not what it’s for. You’re evaluating it like it’s supposed to replace your 200-engineer stack. Meanwhile, a 3-person team is using it to: test ideas in days get real user feedback iterate 10x faster than your roadmap allows Of course it looks messy to you. Your entire worldview is: stability process risk mitigation quarterly planning Their world is: speed learning what outcome takes less resistance to success Vibe coding isn’t trying to compete with enterprise systems. It’s a velocity engine. A test bench. A way to punch way above your weight *before* you earn the right to build it “properly.” So when a big company trashes a vibe-coded product for not being stable… it just shows they don’t understand the game being played. You’re optimizing for perfection. They’re optimizing for truth. And truth shows up faster than your next sprint cycle.
7
-
Ese Smith Echanomi
PayskulApp • 680 followers
I still remember my first experience building a scalable system - it was a disaster. The system crashed under load, and I was left wondering what had gone wrong. Looking back, I realize that I made some critical mistakes that could have been avoided with a bit more planning and expertise. One of the biggest mistakes I made was not considering the potential growth of the system, and another was not implementing proper monitoring and logging. As I've worked on more projects, I've seen many other developers make similar mistakes. We often get so caught up in the excitement of building something new that we forget to think about what might happen when it's deployed to a large audience. We might overlook the importance of load testing, or neglect to design the system with flexibility and adaptability in mind. I've also seen developers underestimate the impact of small decisions, such as choosing the wrong database or not optimizing queries. So, what are some common pitfalls that you've encountered when building scalable systems? What lessons have you learned from your own experiences, and how do you approach system design to avoid these mistakes? #scalablesystems #systemdesign #softwaredevelopment
-
👾 Tjeerd In 't Veen
Twin Apps B.V. • 3K followers
I’ve been thinking a lot about where multiplatform development is heading. With tools like Kotlin Multiplatform becoming truly practical, the expectation to share more logic across platforms is growing fast. Lately I started exploring Rust as a multiplatform option. Rust is usually aimed at C++ developers and systems programmers, but I keep coming back to this question: What if Rust were approachable for mobile developers too? One of the big reasons Rust interests me is its mix of performance and safety. You get native speed without garbage collection or ARC, strong guarantees around memory safety, and the ability to ship the same core module to iOS, Android, desktop, backend, or even WebAssembly without rewriting it per platform. That makes it another compelling option for shared business logic or core components across platforms. Some apps already use Rust as a strong core layer. I'm exploring to see how viable it is for mobile devs to try out, even if it's for a small module rather than replacing a full-blown business layer across multiple apps. I want to see how we can make it less intimidating and more accessible for everyday app developers. I’m exploring this and will share more as I go. If there is enough interest, I’ll go deeper. I'll share my findings on https://lnkd.in/emVy_hFv
96
15 Comments -
Parth Damor
Rezint Tech™ • 2K followers
Rezint Tech is no longer hiring Frontend Developers. 🚫 AI is here—and it’s saving time like never before. So please, don’t send us your frontend resumes anymore. For those still preparing for Frontend Developer jobs, this might sound harsh. But we believe in being honest about the future instead of giving false hopes. 👉 Why we stopped frontend hiring: AI tools can now build UI faster than ever. Tasks that once took hours, now take minutes. Businesses no longer need to spend extra money on repetitive frontend work. We don’t want you to waste your time—or ours. ➡️ If you’re emailing your resume to rezint.tech@gmail.com for frontend roles, please stop. Instead, invest your energy into skills that will stay relevant for the next 5–10 years: AI + Backend Integration Full-Stack Automation Cloud & DevOps Data + AI-driven solutions 💡 Your turn: Do you think AI is truly killing frontend jobs, or is this just an overhyped trend? Drop your opinion 👇 — this conversation matters for the future of work. #RezintTech #AI #Frontend #NoMoreHiring #FutureOfWork #TechTrends #Careers
21
3 Comments -
Anastasiia Zvenigorodskaia
AI-BLOX | Physical AI… • 11K followers
If you build Vue apps for EU clients, CRA now affects frontend code too - dependencies, updates, and security practices. Outdated npm packages and missing security docs are already a risk for enterprise projects. 👉 Details in the article https://lnkd.in/ewq_YMgy
7
-
Volodymyr Bilonenko
Dekart • 4K followers
From today, I’m full-time on Dekart. I left director job and fantastic team at Vay to build Dekart into Cursor for map analytics. I’m not doing this alone but with my amazing partner Nadiia Moiseienko 💙 Was it a good idea? Probably, I will ask myself in one year what I was thinking about!? 🙈 So let’s actually write it down 📝 Here are my thoughts about the future: → More autonomous systems on the ground, more real-world sensors, more GIS data, more map analytics 💪 → AI is killing specialization; map analytics will be done by folks with diverse backgrounds; they will rely heavily on AI. → Better coding agents will change the BUY/BUILD strategies in dangerous ways. Some B2B SaaS will be replaced, but some will cement as essential APIs for AI Agents to operate. → Specialized agents are likely doomed and will be replaced with generic agents + skills/APIs. 🎯 My goal is to make Dekart an essential tool that you and your AI agents cannot live without! This is an exciting and scary journey… And I will be sharing it live on LinkedIn! If you are curious how it goes, FOLLOW me!
212
32 Comments
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content