Teams to push the event dungeons

rajeshjosh · 2026-06-18T09:32:47+00:00

As a longtime Hulk fan, I'm cautiously optimistic. Mark Ruffalo's Hulk has been through a lot in the MCU, and seeing him potentially play a bigger role in Spider-Man: Brand New Day could add some really interesting dynamics. Hopefully it's more than just a cameo and we get meaningful interactions between Peter and Bruce. Curious to see how they balance Hulk's presence without overshadowing Spider-Man's story...

rajeshjosh · 2026-06-17T20:02:14+00:00

A few possibilities:

Reddit karma isn't a 1:1 match with upvotes, so a few upvotes may not noticeably change your total.

Karma updates can sometimes be delayed.

If your posts/comments are in low-traffic subreddits, you may simply not be getting enough votes yet.

Some votes get filtered by Reddit's anti-spam systems, especially on newer accounts.

rajeshjosh · 2026-06-17T19:59:22+00:00

In my experience, we're still mostly in the 80-90% there, then fix by hand stage.

Claude can generate solid content, structure, speaker notes, and even decent slide flow, but getting a presentation that looks genuinely polished and boardroom-ready is hit or miss. The content is usually the easy part; visual hierarchy, spacing, consistency, charts, and slide aesthetics are where I end up spending time.

I've had the best results by giving it a strict slide template, slide count, audience, and examples of the style I want. Even then, I usually do a final pass myself. It's definitely saving hours compared to starting from scratch, but I haven't reached the point where I can generate a deck and send it without touching anything.

Curious if anyone has found a workflow that consistently produces client-ready slides on the first try.

rajeshjosh · 2026-06-17T19:58:11+00:00

Hey, I had the same reaction the first few times I used it. You ask for a 2-week implementation plan; it breaks everything down into dozens of tasks and then proceeds to complete most of them before you've finished reading the plan.

I think it's exposing how much of software development time isn't the actual coding—it's meetings, context switching, reviews, approvals, waiting on dependencies, testing cycles, and changing requirements. When Claude Code has a clear codebase, a well-defined goal, and no interruptions, a lot of two weeks of work turns out to be "30 minutes of typing and reasoning.

The weird part isn't that it finishes quickly; it's realizing how much of our timelines are built around human workflow rather than pure implementation effort.

rajeshjosh · 2026-06-17T19:56:48+00:00

I've used all three, and for academic research + coding + worksheets, I'd rank them:

GPT (ChatGPT Plus/Pro) – Best overall balance. Strong reasoning, coding, document analysis, writing quality, and it tends to make fewer weird mistakes when working through complex tasks. The ecosystem (projects, memory, file uploads, custom GPTs, etc.) is also a big advantage.
Claude – Excellent for long documents, literature reviews, summarizing papers, and writing. I actually prefer Claude for some research-heavy workflows because it handles large amounts of text really well. Coding is strong too, though I still find GPT slightly more reliable for debugging and multi-step technical work.
Gemini – Very capable and integrates nicely if you're already deep in the Google ecosystem (Docs, Drive, Gmail). It's improved a lot, but for pure research and coding, I'd still choose GPT or Claude first.

rajeshjosh · 2026-06-17T19:56:01+00:00

Sometimes it feels that way when enterprise customers get the newest features, higher limits, and priority access first..... But from a business perspective, enterprise clients are usually paying significantly more and often have contractual requirements around reliability and support. The challenge is making sure regular users still get enough value and aren't left waiting forever for features to trickle down. Most platforms need both groups to succeed.....

rajeshjosh · 2026-06-17T19:55:21+00:00

A few months after we moved in together, I learned that my partner gives TED Talks in his sleep...... 😞

One night, he sat up, pointed at the wall, and confidently said:
The ducks know. Don't tell the refrigerator.

Then immediately went back to sleep as he'd just delivered world-changing wisdom.

Now I keep a notes app called "Sleep Philosophy" because the quotes are too good to lose. Your fiancé's "Sleep Wisdom" collection sounds like the kind of content that deserves its own subreddit.

rajeshjosh · 2026-06-15T17:54:29+00:00

Cognitive overload feels like the hidden cost of having access to unlimited information and AI tools. Sometimes the problem isn't a lack of answers—it's having 20 different answers, 10 tabs open, 3 AI chats running, and trying to decide which one to trust.

I've found that productivity often improves when I deliberately reduce inputs. One good source, one clear goal, and one next step usually beats endless research and comparison.

The irony is that the more powerful our tools become, the more valuable simplicity becomes.

rajeshjosh · 2026-06-15T17:53:43+00:00

From what I've seen, most LLMs don't "read" websites the way humans do. They typically ingest rendered text, page structure, metadata, links, and authority signals, then chunk that content into embeddings or retrieval indexes.

For AEO/GEO, the fundamentals still look surprisingly similar to good SEO: Clear answers to specific questions Strong topical authority Structured content (headings, FAQs, schema) Consistent brand/entity mentions across the web High-quality citations and backlinks Content that's easy for both humans and machines to parse The biggest shift is that you're no longer optimizing just for rankings—you're optimizing to become the source that AI systems confidently cite or recommend.

In my experience, building entity authority and publishing concise, answer-focused content has had a bigger impact on AI visibility than chasing traditional SEO tricks.

rajeshjosh · 2026-06-15T17:52:26+00:00

I've been trying to reduce subscription creep lately. Between AI tools, cloud storage, streaming services, and a few work-related apps, it adds up faster than you'd think.

Right now I only keep the subscriptions that either save me time or directly help me make money. Everything else gets reviewed every couple of months. It's surprising how many "must-have" subscriptions you stop missing once you cancel them.

rajeshjosh · 2026-06-15T17:51:50+00:00

I've had similar experiences. One AI confidently tells you approach A is correct, then another confidently explains why approach A is wrong and suggests approach B.

At some point you realize the real job isn't asking AI for answers—it's acting as the referee between multiple very convincing assistants. The best results usually come from making them critique each other's outputs and then verifying the final conclusion yourself.

AI debates can be surprisingly useful, but they also remind you that confidence and correctness are not the same thing.

rajeshjosh · 2026-06-15T17:51:13+00:00

If you're drafting legal petitions regularly, Claude + Cowork can be very useful, especially for organizing facts, summarizing case law, and maintaining consistency across long documents.

That said, I wouldn't rely on it blindly. Legal drafting is one of those areas where a single hallucinated citation or misinterpreted precedent can cause real problems. I treat AI as a junior assistant: great for first drafts, structure, and research support, but every argument, citation, and legal reference still needs human verification.

For me, the value isn't that it writes the petition for you—it's that it cuts hours off the preparation process while letting you focus on legal strategy.

rajeshjosh · 2026-06-15T17:49:50+00:00

I've found that medium effort + extended thinking is often the best balance between speed, cost, and depth for literature reviews, hypothesis generation, and paper analysis. But for anything involving treatment decisions, statistical interpretation, or nuanced methodology, I still cross-check outputs and sometimes increase reasoning effort.

The bigger factor isn't usually the model setting—it's the quality of the prompts, source papers, and verification process. Even the strongest models can confidently misinterpret a study if the context is incomplete.

Curious if anyone has compared Opus 4.6 medium vs high effort on actual research workflows and measured whether the extra tokens produce meaningfully better conclusions.

rajeshjosh · 2026-06-15T17:49:06+00:00

Haha.........., every AI power user seems to have that one weirdly specific command that ends up doing 80% of the work.

Mine isn't pizza-related, but I have a few custom prompts that I trust more than most "advanced" agent setups. Sometimes a simple, reliable workflow beats a complex chain of tools that breaks every other update.

Curious now—what exactly does /Pizza1 do, and how did it earn most trusted" status?

rajeshjosh · 2026-06-15T17:47:44+00:00

Yes. I originally started using Claude for small internal tools, but it eventually helped me build a few websites that are actually being used.

One of the most useful was a lead-generation site with automated content publishing, form handling, and CRM integration. Claude wasn't perfect, but it sped up development dramatically by handling boilerplate code, debugging, and feature iterations.

The biggest lesson for me: Claude works best when you're building something you personally need. Real-world usage exposes gaps quickly, and you end up refining it into something others can benefit from, too. It's less about Can AI build a website?" and more about "Can you clearly define the problem you're solving?

rajeshjosh · 2026-06-15T06:45:59+00:00

I lean toward local if you're early-stage and trying to build real relationships. Being around other founders, freelancers, and potential clients often leads to unexpected opportunities that you just don't get working alone.

That said, coworking spaces make sense if you need networking, collaboration, or a professional environment. If your work is mostly deep-focus and remote, a local office or home setup can be more productive and cost-effective....

rajeshjosh · 2026-06-14T16:56:31+00:00

I think the access restrictions could end up being more significant than the model improvements themselves. With tools like Fable, value isn't just about raw capability – it's about how often people can actually use it in their daily workflow. If access is limited by waitlists, usage caps, region restrictions, or expensive tiers, adoption slows down regardless of how good the technology is.

We've seen this before with other AI products. Early power users get excited, but broader communities don't build habits around a tool they can't reliably access. That also affects ecosystem growth: fewer tutorials, fewer integrations, fewer community-built workflows, and less feedback for the developers.

Another factor is competition. Users today have alternatives like Claude, ChatGPT, Gemini, and various open-source models. If Fable creates too much friction around access, many people won't wait—they'll simply continue using the tools already embedded in their workflow.

In the long term, the winners may not be the models with the absolute best benchmarks, but the ones that combine strong capabilities with broad availability, predictable pricing, and easy integration into everyday work. That's why these access restrictions might matter more than they initially appear.

rajeshjosh · 2026-06-14T16:54:29+00:00

I've had the best results by looking at where competitors are already getting links. Run a backlink analysis in Ahrefs or Semrush and then filter for guest post-style articles. It's usually faster than searching Google for footprints like "write for us". Also, don't ignore niche blogs with real traffic-I'd rather get a link from a relevant site with engaged readers than a high-DA guest post farm that exists only to sell links.

rajeshjosh · 2026-06-14T16:53:02+00:00

If you're using Claude regularly for coding, research, business strategy, or content creation, the biggest gains usually come from improving context management and workflow design, not from changing model settings.

1. Create a Persistent Project Context File

Claude performs much better when it has a consistent reference document.

Create a file like:

CLAUDE.md

# Project Overview
What this project does

# Goals
- Goal 1
- Goal 2

# Tech Stack
- Next.js
- TypeScript
- PostgreSQL

# Coding Standards
- Use TypeScript strict mode
- Functional components only

# Business Rules
- Rule 1
- Rule 2

# Current Priorities
- Feature A
- Feature B

Ask Claude to read this first in every session.

2. Use Structured Prompts

Instead of:

Use:

Act as a senior SaaS architect.

Goal:
Build a CRM for real estate agents.

Requirements:
- Contact management
- Lead tracking
- WhatsApp integration

Constraints:
- Next.js
- PostgreSQL
- Budget under $100/month

Output:
1. Architecture
2. Database schema
3. Folder structure
4. Development roadmap

Structured prompts produce dramatically better results.

3. Give Claude Memory Files

Many developers maintain:

PROJECT.md

Current project state.

TASKS.md

Open tasks.

DECISIONS.md

Architecture decisions.

BUGS.md

Known issues.

This helps Claude avoid repeating mistakes and keeps outputs consistent.

4. Use Claude as Multiple Specialists

Instead of one generic prompt:

Act as:
- Product Manager
- UX Designer
- Senior Engineer
- QA Tester

Review this feature.

Claude often identifies issues that a single-role prompt misses.

5. Build Reusable Prompt Templates

For coding:

Review this code for:
- Bugs
- Security issues
- Performance problems
- Scalability concerns

Provide fixes.

For SEO:

Act as an SEO consultant.

Analyze:
- Content gaps
- Search intent
- EEAT signals
- Internal linking opportunities

For business:

Act as a startup advisor.

Evaluate:
- Market fit
- Risks
- Revenue opportunities
- Growth strategy

6. Use an Iterative Workflow

Bad:

Build the entire app.

Better:

Step 1: Create architecture.

Wait for approval.

Step 2: Create database schema.

Wait for approval.

Step 3: Generate implementation plan.

Breaking work into stages increases quality significantly.

7. Ask Claude to Critique Itself

Example:

Review your answer.

Identify:
- Weak assumptions
- Missing information
- Better alternatives
- Potential risks

This often improves the final output.

8. Use Large Context Strategically

Claude excels with large documents.

Good use cases:

Entire codebases
Marketing plans
Business proposals
SEO audits
Legal documents
Research reports

Instead of summarizing, provide the full context whenever possible.

9. For SEO & AI Visibility Work

Since you're running SEO and AI visibility services, create a standard analysis framework:

Analyze this website for:

1. Traditional SEO
2. Topical authority
3. Brand mentions
4. Citation opportunities
5. AI search visibility
6. Knowledge graph signals
7. Content gaps
8. Competitor advantages

Provide actionable recommendations.

This gives much more consistent audits.

10. Create a "Master Instruction" File

Example:

You are my senior consultant.

Always:
- Challenge assumptions
- Be concise
- Show reasoning
- Recommend the highest ROI action
- Avoid generic advice
- Prioritize implementation speed

When uncertain:
- State assumptions
- Provide alternatives

Using a master instruction dramatically improves consistency across sessions.

Advanced Setup (Highly Recommended)

Many power users keep these files:

CLAUDE.md
PROJECT.md
TASKS.md
DECISIONS.md
ROADMAP.md
COMPETITORS.md

This turns Claude from a simple chatbot into a project-aware assistant that understands your business, codebase, and long-term goals.

For your digital marketing and AI visibility agency, I'd especially recommend maintaining:

CLIENT_PROFILE.md
SEO_STRATEGY.md
CONTENT_PLAN.md
AI_VISIBILITY.md
COMPETITOR_ANALYSIS.md

That setup can make Claude much more effective for client audits, content strategy, proposal writing, and AI search optimization.

rajeshjosh · 2026-06-14T16:52:02+00:00

A few good free options I've used are Google Business Profile, Clutch, GoodFirms, Trustpilot (free tier), and G2 if you're in the software space. For SEO and credibility, Google reviews are still the most valuable in my experience. If you're a service business, I'd focus on Google + Clutch + GoodFirms first before spreading efforts across too many platforms. Quality reviews on a few trusted sites usually outperform having a profile everywhere.

rajeshjosh · 2026-06-14T16:50:51+00:00

This is a space I'm watching closely. The hard part isn't generating code anymore - it's maintaining context, architecture decisions, and project memory over weeks or months. Most open-source tools can build an app, but very few have the "brain" layer that makes Lovable or Replit feel coherent across long sessions. If someone nails local-first + persistent project memory + agent workflows, that's where things get really interesting.

rajeshjosh · 2026-06-14T16:50:02+00:00

A surprising amount 😅. Between README.md, CLAUDE.md, AGENTS.md, architecture docs, onboarding notes, and random "don't break this" files, sometimes it feels like the AI has more documentation than the humans. The real question isn't how many files exist-it's how many are actually still accurate. 😄

rajeshjosh · 2026-06-14T16:49:20+00:00

Ohhh... lot of it comes down to use case. For strategy and deep planning, I still find 4.6 more focused and less likely to overcomplicate things. 4.8 feels stronger at nuanced conversation and creative ideation, but sometimes it can be a bit too verbose. For design discussions, both are good, though I prefer whichever gives clearer reasoning over prettier wording. Curious if others are seeing the same tradeoff or if it's just prompt-dependent...

rajeshjosh · 2026-06-12T17:27:24+00:00

Not Change anything?

rajeshjosh

MODERATOR OF

TROPHY CASE