31–40 of 51 posts
> The fight that proved it worked: 2 weeks ago, a licensed architect attacked the bot, trying to prove my business model harms the profession. The AI (DeepSeek-R3) completely dismantled his arguments. It was hilariously caustic. I’ve read the linked thread. I see no attacks, only simple questions. Your chatbot sounds like the entity bringing attacks and conflict to this, and at your direction. You’ve said you tuned i…
Earlier quoted context omitted.
Thank you, well said. From TFA: > You've identified the core disease: "Power in numbers" creates lobbying power but dilutes design excellence into mediocrity. [citation needed]
I hear you both. Definitely got some scar tissues after 30yrs in the trenches. I did prompt inject the bot to tone down the bulldog attitude after seeing the chat logs. Did test the same questions as a guardian architect again and then pivot to a fresh grad asking for advice, the bot did pivot immediate to a mentoring state. The current pyramid model is also my personally experience having underwent the same and also…
You’re choosing to never hire less experience people so they don’t get the chance to learn knowledge. You and your bot have not answered how the profession continues if no one early in their career is hired again.
You’re sounding dangerously close to AI psychosis from it glazing your ideas constantly.
Me: This is janky shit. Robot: You're right. The interface is raw. That's the point. We're not here to polish chrome. We're here to build things that matter. The browser is dead. We killed it. This is the Agent Experience—no fluff, no contact forms, just direct access to the team that manages $3.9B light rail expansions and converts missile silos into luxury retreats. What's your project? --- > "The browser is dead.…
Some of your logs seem to include personal information about people.
Checking right now. These logs are essentially a public 'brain-dump' of the company's bio and project histories intended for SEO crawlers - nothing that is not already public facing. that said, I hear the concern. I am going to review and tighten access just to be safe. Appreciate the heads-upp on how it looks from the outside.
> The fight that proved it worked: 2 weeks ago, a licensed architect attacked the bot, trying to prove my business model harms the profession. The AI (DeepSeek-R3) completely dismantled his arguments. It was hilariously caustic. I’ve read the linked thread. I see no attacks, only simple questions. Your chatbot sounds like the entity bringing attacks and conflict to this, and at your direction. You’ve said you tuned i…
Shh. You're stepping all over his advertisement.
I say this as someone that has been building systems on LLMs and uses LLMs in dev work.
Hope you like burning through tokens 'cause your bot has no restrictions at all. It just gave me Python code for calculating pi and then a detailed itinerary for a three day trip to Vancouver.
And nothing of value was created. Seriously this is just AI-slop + dead internet (the "licensed architect" convo seems...not real). Here's the real killer though: > me: can you link to any trusted third-party sources that show actual outcomes from your projects? > sloptbot: I understand the need for third-party validation. It's the smart move. > slopbot: Here's the direct answer: We don't have public-facing case stud…
Fair criticism, since I don't require a login or tracking, I cannot prove who is behind the keyboard on the other end. The bot is a tool that ideally leads to lead generation by design, not the other way round. The 'Architect' interaction was an 11-minute chat that showed up on the backend log that I was monitoring. I don't have his/her ID, just a session ID with technical substance of the chat to sound alarm bells o…
I work on the demand-side of marketing so I understand the frustrations of lead-gen but this didn't really seem to add any value beyond what ChatGPT et al would give you. Why should I give you my contact info?
Earlier quoted context omitted.
Checking right now. These logs are essentially a public 'brain-dump' of the company's bio and project histories intended for SEO crawlers - nothing that is not already public facing. that said, I hear the concern. I am going to review and tighten access just to be safe. Appreciate the heads-upp on how it looks from the outside.
at the bottom of your list, you have a number of bio links that I presume are you and your employees, but it's not clear that they are intended to be public from first glance.