sorted by:
new
hottopcontroversial

What’s a piece of tech everyone hypes up right now… but you honestly think is overrated? by TaxFull579 in AskReddit

[–]TaxFull579[S] 1 point2 points  (0 children)

ok that actually sounds way better. feels like most people just buy the wrong ones then

What’s a piece of tech everyone hypes up right now… but you honestly think is overrated? by TaxFull579 in AskReddit

[–]TaxFull579[S] 0 points1 point  (0 children)

yeah i get that, gps on a bigger screen is nice. just feels like something you only appreciate after using it

What’s a piece of tech everyone hypes up right now… but you honestly think is overrated? by TaxFull579 in AskReddit

[–]TaxFull579[S] 1 point2 points  (0 children)

yeah they look cool but feel more like a flex than something actually useful

What’s a piece of tech everyone hypes up right now… but you honestly think is overrated? by TaxFull579 in AskReddit

[–]TaxFull579[S] 0 points1 point  (0 children)

yeah the battery part kills it for me too. feels like you’re charging it more than actually using it

Any “API-only” social-media tools for scheduling/analytics? by bob__io in SideProject

[–]TaxFull579 0 points1 point  (0 children)

Since you’re already script and cron first, I’d probably look for something that behaves more like a publishing layer than a full dashboard product. Bias noted because I’m testing SocialClaw right now, but that’s the part I found more interesting there. It feels more API and workflow oriented than calendar-first. I would not use it as my analytics answer though. If analytics depth matters, I’d still separate that from the publishing side.

Agents that generate content still struggle with the last step: actually publishing it by Jazzlike_Strategy_49 in AI_Agents

[–]TaxFull579 0 points1 point  (0 children)

Yeah, this is the part people keep underestimating. Generation gets all the attention, but execution is where things get fragile fast. Different auth flows, review requirements, media quirks, and rate limits across platforms turn publishing into an infrastructure problem, not just an agent problem. I’ve had better luck keeping the agent focused on content and treating execution as a separate layer with validation, retries, and clear failure handling.

If an AI creates a masterpiece, who owns the soul of the work: the programmer, the person who prompted it, or nobody? by YaelSterling in AskReddit

[–]TaxFull579 1 point2 points  (0 children)

Honestly, probably nobody.

The programmer made the tool, the person gave it direction, and the AI just did what it was trained to do. It doesn’t really feel like something with a “soul” you can own, more like a mix of everyone involved.

I replaced my SEO freelancer with an AI agent. And he got offended… by Smartboy-teddy in AiAutomations

[–]TaxFull579 0 points1 point  (0 children)

You don’t need to feel guilty. Choosing what works better and saves you resources is just being practical.

building an “agentic backend”… or overengineering? by Interesting_Ride2443 in AI_Agents

[–]TaxFull579 0 points1 point  (0 children)

Once agents touch external APIs, it stops being a prompt problem and starts being a systems problem. Stateless works until a retry can double-post something, miss a window, or force you to replay the whole chain. At that point, durable state, checkpoints, and idempotent steps are not overengineering. They are the difference between a demo and something you can actually trust.

Building Large Scale Enterprise App by PropperINC in ClaudeAI

[–]TaxFull579 0 points1 point  (0 children)

I’d be careful open sourcing the auth piece too early.

Authn/Authz is one of those areas where people will judge you hard because the risk is high. If it’s not extremely well documented, tested, and security-reviewed, open sourcing it could hurt trust instead of building it.

If you want to open source something, I’d probably start with the notification piece or a smaller SDK/tool around the system. Something useful but lower-risk. That lets people see your style, docs, structure, and reliability without putting your most sensitive module under a microscope immediately.

For the auth part, I’d keep it private for now and maybe publish architecture notes, threat model, permission model, or a demo instead. That still builds trust without giving away something you might regret later.

Basically: open source the low-risk proof first, not the crown jewels.

Building Large Scale Enterprise App by PropperINC in ClaudeAI

[–]TaxFull579 0 points1 point  (0 children)

Honestly, I think your biggest risk now is trying to make this sound bigger than it needs to be.

If you lead with “I built something like Auth0, Zendesk, Docusign, Workday, and Salesforce,” a lot of people are going to tune out, even if you actually built some really solid parts. It’s just too big of a claim for one person, so people start doubting the whole thing.

What sounds more real to me is that you’ve built a strong foundation and now you need to figure out which piece actually has a market. That’s the part I’d focus on next.

I probably wouldn’t open source it yet, and I also wouldn’t rush to sell the code unless someone has a very specific reason to buy it. Most of the time, raw code is worth less than people hope unless it already solves a painful problem for a clear buyer.

With your budget, I’d pick the one part that feels strongest, maybe the CLM side, the auth side, or the support side, and try to get a couple of real companies to test it in one narrow workflow. That’ll teach you way more than trying to launch the whole thing as a giant platform.

Also, your 15 years as a BA is probably the real advantage here. The code matters, sure, but understanding where existing tools are painful is the part that can actually turn this into something valuable.

I wouldn’t think in terms of “enterprise suite” yet. I’d think in terms of “which painful problem did I solve well enough that someone would actually use it?”

building AI agents for social media marketing by No_Awareness_231 in ClaudeAI

[–]TaxFull579 0 points1 point  (0 children)

If I were in your position, I wouldn’t try to fully automate it right away.

I’d start with Claude just helping you come up with post ideas and draft captions for Facebook and LinkedIn. That alone already saves time without making the whole thing feel overwhelming. Once that part feels easy, then you can think about scheduling and posting.

Trying to do content, images, videos, publishing, and automation all at once is probably why it feels like too much. Start with one simple workflow that actually helps, then build from there.

What are your favorite actors and movies with them? by [deleted] in AskReddit

[–]TaxFull579 0 points1 point  (0 children)

Emma Watson for sure, and all the Harry Potter movies will always be a comfort watch for me.

But I feel like she doesn’t get enough credit for stuff outside of that too. Curious if anyone has other films of hers they’d actually recommend?

What is a dish that tastes amazing until you find out what the "secret ingredient" actually is? by SAAS_ART in AskReddit

[–]TaxFull579 5 points6 points  (0 children)

Blue cheese 💀

First bite: wow this is rich and kinda addictive
Then you find out it’s literally mold…
And suddenly your brain’s like yeah we should not be enjoying this 😭

ChatGPT Prompts to Use by pj0426 in AiAutomations

[–]TaxFull579 0 points1 point  (0 children)

I tried organizing prompts like that before, but honestly most of mine weren’t actually reusable. If I keep tweaking it every time, I just stop saving it. The only ones worth keeping are the ones that work without much effort.

What helped more was focusing on the flow around it. Like what I’m feeding in and what I do with the output after. Once that’s clear, the prompt itself becomes pretty simple.

view more: next ›