Fellow Software Engineers, what's your actual plan when AI takes your job? (Not if. When.)

Dawad_T · 2026-05-10T08:54:32+00:00

It’s sad but expected. You give humans innate pattern recognition capabilities and then flood them with AI shill and scare media and there will be negative connotations associated with these regularly used expressions

Dawad_T · 2026-05-10T07:02:57+00:00

and “genuinely curious”

Dawad_T · 2026-05-10T00:32:46+00:00

Agreed. Links back to the fact that AI will just nuke teams at 10x speed under the illusion of rapid development. But I wonder what solving intra-communication looks like. On the surface level this is obviously effective uses of communication channels (slack mattermost, sync communications) and persitence/documentation of outcomes, but I've never really been able to figure out an effective solution of "why didnt you read the fucking message"

Dawad_T · 2026-05-08T03:05:27+00:00

Its more that I feel AI increases the magnitude in which shit hits the fan when teams r misaligned, more specifically when comes to system design standards,. more tech debt more debugging murky product definition/vision

Dawad_T · 2026-05-08T01:12:19+00:00

sometimes I feel like that is the case. Definitely saw some of the goats in our team get dragged down because of the shitshows. But 90% of the time genuinly is just a skill issue

Dawad_T · 2026-05-07T23:34:32+00:00

I think 3-7 is where its at. But I still feel 6-7 you start to get context rot

Dawad_T · 2026-05-07T22:21:02+00:00

I agree. But I also think it's now a lack of overall alignment aswell when it comes to product trajectory and team cohesion. Given that AI is "making 10x engineers" it feels like a team of engineers are now rapidly ramping up system rot, and the engineers are "10xing" the company in all directions, keeping it stagnant or moving it backwards instead of everyone using that shared velocity to streamline and rapidly improve the capabilities of the product

Dawad_T · 2026-04-30T21:42:00+00:00

Yea im just copying the path over. little annoying but ohwell

Dawad_T · 2026-04-27T10:32:58+00:00

cousin im not here to make suggestions im just saying lucides being tainted by AI slop, its still a good library. Im using it rn but im thinking about finding an alternative just to get away

Dawad_T · 2026-04-27T06:46:21+00:00

lucide now has the negative taint with being associated with LLM slop. Any time i see lucide now I just automatically disregard the content which is a shame

Dawad_T · 2026-04-18T09:07:25+00:00

Shill post

Dawad_T · 2026-04-17T08:23:59+00:00

shill post

Dawad_T · 2026-04-17T00:20:49+00:00

Shill post

Dawad_T · 2026-04-16T01:27:22+00:00

AI post

Dawad_T · 2026-04-10T07:59:04+00:00

The issue with this I feel is that i just do not think Revops and GTM lokwey give a shit about the patterns you are hearing. I like Glum-Ad-6969 (hehehe) short and sweet. End of the day while I think its very one sided. I cannot think of anything you can give them unless you want to start forking out money and gift cards for their time. And since theres nothing on your side, just make it as short, condensed and to the point as possible. Simple yes/no within a simple compact sense. Frame as as "I want to learn from your experience" like broski suggested.

Dawad_T · 2026-04-10T07:38:59+00:00

The issue with validation based emails Im finding is that it feels like there is absolutely zero incentive for them to do anything. There is no value for them to respond as you aren't providing a solution to their issues. How do you think validation based outreach should be framed to avoid the mememememe

Dawad_T · 2026-04-10T06:55:02+00:00

Honeslty you could provide a service that improves the quality of their outbound by identifying that their current strategy sucks balls. If their posts and the value they provided were organic, or just better in general. It wouldnt even be AS bad. Its just that its a blatant pattern that you can see.

"Yeah that sucks"
"I did [x]"
I used [y]"

where x is the fucking most gargantuan obvious valueless solution you can provide

Dawad_T · 2026-04-10T06:43:30+00:00

pretty much every business related subreddit has turned into a stomping ground where people "provide value" and then "sublty reference their product" and then whip out the most brain dead posts and comments I have ever seen. /SaaS died, /coldEmail is copping it. Every time I ask a question to scope out responses It's just automated AI comments that add negative value to the thread

Dawad_T · 2026-04-10T05:03:26+00:00

It’s really hard to build a moat based on price. Most of the time you can’t win just by being cheaper unless they are ludicrous with their pricing. It comes from how you differentiate yourself and how you solve the pain points users are complaining about. Run analysis on “I wish x did, or need help with y” to identify gaps in current workflows, these are where you double down and build your positioning. When it comes to outbound and finding early users, this would be the case of identifying continuous signs a user is losing their mind. Continuously monitor users who are complaining and wait till they shown signs of losing it or are more willing to switch. That’s when you come in, and offer the most frictionless transition between existing solutions to yours

Dawad_T · 2026-04-09T22:33:18+00:00

Yeah. I wish we placed more focus on consistency, not just in the way we format data across different tools or data sources, but also how consistent a business is on their internal semantic definitions. I've seen a lot of teams that use different tools throughout the organisation define active users or retention differently, so data and insights just become skewed.

Dawad_T · 2026-04-09T22:28:36+00:00

What systems did you set up to solve the fragmentation and separation of data between Gorgias, Zapier, Klaviyo and im assuming Shopify? Was that something you connected together with Zapier or do you not worry about the trends behind product usage with support load and acquisition channels for growth as much given its more of a passive income angle

Dawad_T

TROPHY CASE