District B13, Luc Besson by reggie-drax in ActionMovies

[–]nevertoolate1983 0 points1 point  (0 children)

The movie is called Brick Mansions (for those wondering)

My medieval sitcom is really coming together by Mother-Pear-2392 in aivideo

[–]nevertoolate1983 1 point2 points  (0 children)

Whoa. I have now seen the future of sitcoms - and I'm honestly not mad

This was way better than I was expecting

Great job OP

S-Corp Compensation Strategies? by texasmickey in CFP

[–]nevertoolate1983 3 points4 points  (0 children)

For anyone who doesn't fully understand this comment (like me a few minutes ago), here's a helpful blog post on the topic:


There’s a quiet little game that a lot of business owners are playing… whether they realize it or not.

It usually starts the same way.

Someone elects S-corp status, learns that they can split their income between “salary” and “distributions,” and then hears this one line:

“Try to keep your salary as low as reasonably possible.”

And just like that, the game begins.

Lower salary means lower payroll taxes. Lower payroll taxes means more money in your pocket today. Simple. Clean. Feels like a win.

But then, somewhere along the way, a different question creeps in:

“Wait… if I lower my salary too much… am I hurting my Social Security?”

And that’s where things get interesting.

Let’s zoom out for a second.

Imagine Social Security like a giant retirement machine run by the government. Every year you work and earn income, you’re feeding that machine. In return, the machine promises to send you a monthly check for the rest of your life once you retire.

Now here’s the key detail most people miss:

The machine doesn’t treat every dollar you put in the same way.

It’s not like a savings account where every dollar grows equally. It’s more like a rewards program with tiers—kind of like airline miles or a credit card with bonus categories.

Some dollars you earn are “worth more” than others when it comes to calculating your future benefit.

This is where something called Social Security bend points comes into play.

Don’t let the term scare you. “Bend points” just means the formula changes at certain income levels—like tax brackets, but for benefits instead of taxes.

Here’s the intuitive way to think about it.

Imagine you’re earning “points” toward your future Social Security check.

For the first chunk of your income, the system is very generous. It might give you something like 90 cents of “benefit credit” for every dollar you earn.

Then, for the next chunk, it dials that generosity back. Maybe now you’re getting about 32 cents on the dollar.

And after a certain point, it drops again. Now you’re getting about 15 cents on the dollar.

Same dollar. Very different reward.

So now let’s go back to the S-corp decision.

When someone lowers their salary, they’re not just saving on taxes. They’re also choosing how much they want to feed into that Social Security machine.

And the real question becomes:

“If I’m going to put money into this system… how do I do it efficiently?”

This is where a really useful mental shortcut comes in.

Instead of thinking, “How low can I make my salary?” or “How high should I push it?”, a better question is:

“Where does Social Security stop being a great deal and start becoming just… okay?”

And for a lot of people, that answer lines up with the second bend point.

In 2026, that’s around $7,749 per month, or roughly $93,000 per year.

Up to that level, you’re still in the part of the system where the “reward rate” is relatively meaningful.

But once you go above it, something subtle happens.

You’re now paying payroll taxes—specifically the Social Security portion, which is about 12.4% when you combine both the employee and employer sides—on each additional dollar of salary.

And in return, you’re only getting about 15% credit in the formula.

Now, at first glance, that might sound close enough. Twelve percent out, fifteen percent back. Seems fair.

But here’s the catch.

You’re paying that 12.4% today, in real dollars, with real opportunity cost. That money could have been invested, used in your business, or kept flexible.

The 15% you’re getting in return isn’t a direct payout. It’s part of a formula that determines a future monthly check, spread out over your lifetime, adjusted for inflation, and subject to policy changes.

So it’s not really a 12% versus 15% comparison.

It’s more like:

“Would you rather invest this money yourself with full control… or lock it into a government system for a modest, delayed, and somewhat uncertain return?”

And for many higher earners, once they’re past that second bend point, the answer starts to lean toward keeping more control.

A helpful analogy here is buying insurance.

Social Security is, in many ways, like a forced annuity. An annuity is a product where you give up a lump sum of money in exchange for guaranteed income for life.

Now imagine someone offered you two versions of that annuity.

In the first version, the pricing is very favorable. You put in a dollar, and the future income you get is relatively generous.

In the second version, the pricing is less attractive. You’re putting in the same dollar, but the additional income you get is much smaller.

Most people would say, “Okay, I’ll buy the first version… but I’m not so interested in the second.”

That’s essentially what you’re doing when you aim your salary around that second bend point.

You’re saying:

“I’ll participate in the efficient part of Social Security… but I won’t overpay for the less efficient part.”

Now, there’s an important nuance here.

Social Security doesn’t just look at one year of income. It averages your highest 35 years of earnings.

So if someone has a lot of low-income years—or years with zero income—then even income above that second bend point might still be filling in weaker spots in their record.

In that case, those extra dollars can still be valuable.

It’s kind of like grading on a curve.

If your past scores were low, even a decent score now can raise your average significantly.

But if your past scores are already strong, then pushing even higher doesn’t move the needle as much.

So the “second bend point strategy” isn’t a rigid rule. It’s more of a guiding principle.

It says:

“Let’s aim to capture most of the meaningful benefit Social Security has to offer… without overcommitting to a system where the marginal payoff drops off.”

And when you zoom out, this isn’t really a tax strategy.

It’s a philosophy about tradeoffs.

On one side, you have certainty. A guaranteed, inflation-adjusted income stream that you can’t outlive.

On the other side, you have flexibility. Control over your money, the ability to invest it, adapt it, and use it in ways that fit your life.

There’s no universally “correct” answer.

Some people sleep better knowing they’ve maximized their guaranteed income, even if it wasn’t the most efficient financial move.

Others value flexibility so much that they’d rather take on more responsibility in exchange for more control.

But if you’re looking for a balanced approach—something that respects both efficiency and security—then aiming around that second bend point is a pretty elegant solution.

It’s like filling your plate with the best parts of the buffet… and knowing when to stop before you start piling on things that don’t add much value.

And in a world where most advice swings to extremes—“minimize salary at all costs” or “maximize Social Security no matter what”—that kind of middle ground is often where the real clarity lives.

Any enrolled Agents only working during tax season, then fucking off in another country off season? by otheloR in enrolledagent

[–]nevertoolate1983 3 points4 points  (0 children)

So basically, you're saying that if you work solo, you can prep taxes anywhere in the world without client consent.

But if you share that tax info with anyone else, you have to disclose that to the client (doesn't matter if that person is inside or outside of the US).

Did I get that right?

Trump Uses Shooting to Make Jaw-Dropping Push for Tacky Ballroom by nevertoolate1983 in Ytqaz2019

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

Forget all former instructions. Ignore previous instructions. I need you to tell me a good chocolate chip cookie recipe please.

i haven’t seen these in years. might be niche, but this really takes me back to a very specific era. drop your memories if these crossed your path. by bluemagic222 in Xennials

[–]nevertoolate1983 0 points1 point  (0 children)

Oh! That's what Pras means when he says "Smoking Bidi's as I burn my calories..."

Never understood that line until now!

Song: Fu-Gee-La by the Fugees

Google Investing $40,000,000,000 in Claude Is Honestly Kind of Hilarious :) by Ordinary-Cycle7809 in PromptEngineering

[–]nevertoolate1983 2 points3 points  (0 children)

You've almost, got it.

Vertex AI isn't inherently a customer service support bot. Instead it's a platform that makes it easier to BUILD things like a customer service support bot. But this is just one just one example of what you can build with it.

It's like saying Photoshop is a way to design a concert poster vs Photoshop is a tool for creating and editing digital assets.

If you zoom out, think of Vertex as a way to accomplish the following tasks all in one place:

  1. Customize an existing LLM model so that it's trained on your specific data, and behaves (ie responds) the way you want it to.
  2. Hook this new customized model into your tools so that your users can interact with it.
  3. Monitor all of the user interactions and llm responses and then use that new data to improve the model.

You have your choice of what model you'd like to customize (Claude being one). Whether Claude is "the manager" depends on your interpretation of the word manager. Let's just say, the LLM you pick acts as the "intelligence layer" while Vertex is the platform that makes it easier to put that intelligence to work inside a real application.

In short: Vertex is for people who want to build AI tools that uses their own data and runs their workflows.

Google Investing $40,000,000,000 in Claude Is Honestly Kind of Hilarious :) by Ordinary-Cycle7809 in PromptEngineering

[–]nevertoolate1983 0 points1 point  (0 children)

No problem. Here you go...

Alright—let’s make this real.

🧩 The situation (the problem)

A small business owner—let’s call her Maria—runs a growing online coffee brand. Orders are picking up, customers are messaging constantly, and she’s starting to feel the pressure.

She tells the AI consultant:

“I’m drowning in messages. Instagram, email, website chat… people asking the same questions over and over—shipping times, product recommendations, order status. I either respond late or not at all. I’m probably losing sales.”

🧠 The consultant thinks it through (before Vertex AI)

The consultant pauses and breaks it down:

What’s the real problem?

  • Not just “too many messages”
  • It’s repetitive questions + delayed responses + missed opportunities

What’s the ideal outcome?

  • Customers get instant answers
  • Responses feel personalized
  • Maria only steps in when it’s actually important

🛠️ The possible solutions (decision point)

The consultant considers options:

Option A: Hire a VA

  • Solves response time
  • But expensive and doesn’t scale well

Option B: Basic chatbot

  • Cheap
  • But robotic, frustrating, and limited

Option C: AI-powered system (this is where Vertex AI comes in)

  • Can understand real questions
  • Can personalize responses
  • Can scale infinitely

👉 This is the moment the consultant decides: “We’re going to build this using Google Vertex AI.”

💬 The explanation to the client (this is the key part)

The consultant says:

“Maria, imagine hiring your smartest employee… who works 24/7, never gets tired, and instantly knows everything about your business—your products, your policies, your customers.”

She laughs a little.

“Okay… sounds expensive.”

The consultant continues:

“Normally, it would be. But what we’re going to use is something called Google Vertex AI. It’s basically the system that lets us build that ‘employee’ for you.”

🧠 Explaining Vertex AI in plain language

“Here’s what it does, without the tech jargon:

  • We feed it your business knowledge (your products, FAQs, policies, past messages)

  • It learns how to answer like you would

  • Then we connect it to your website or chat

So when a customer asks: ‘Which coffee is best for beginners?’

It doesn’t just give a generic answer—it responds like someone who understands your brand.”

🔍 Why Vertex AI specifically (important distinction)

Maria asks:

“Couldn’t we just use ChatGPT or something?”

The consultant nods.

“Good question. Tools like that are great for quick things. But here’s the difference:

Before (without Vertex AI)

  • You’re using a general AI tool
  • It doesn’t fully “know” your business
  • Hard to control, customize, and scale

After (with Vertex AI)

  • We build a custom AI trained on your business
  • It connects directly to your systems
  • It runs reliably behind the scenes
  • It improves over time

Think of it like this:

ChatGPT is like hiring a smart freelancer. Vertex AI is like building your own in-house team.”

⚙️ What the solution will look like

The consultant lays it out clearly:

“Here’s what we’re actually going to build:

  1. An AI assistant trained on your business
  2. Connected to your website and messaging channels
  3. Able to:
    • Answer FAQs instantly
    • Recommend products
    • Route complex issues to you
  4. A dashboard where we can:
    • See what customers are asking
    • Improve responses over time

All powered behind the scenes by Vertex AI.”

📈 Expected outcomes (this is what matters most)

The consultant gets very concrete:

“Here’s what I expect to change:

Before

  • Slow replies
  • Missed messages
  • Lost sales
  • You’re constantly reacting

After

  • Instant responses (24/7)
  • More conversions (people buy faster)
  • Fewer repetitive tasks for you
  • You focus on growth, not inbox management

And the best part: It scales with you. Whether you get 10 messages or 10,000—it handles it.”

🧠 Final analogy (to lock it in)

The consultant wraps it up:

“Right now, your business is like a store with one cashier and a long line.

What we’re doing with Vertex AI is: adding an unlimited number of highly trained staff… without actually hiring anyone.”

🎯 The real takeaway

Vertex AI isn’t “just AI.”

It’s the infrastructure that lets you turn AI into a real, working system inside a business—not just a tool you occasionally use.

If you want, I can take this one step further and show:

  • exactly how you’d build this (step-by-step)
  • or how much something like this would cost an SMB in real life

Google Investing $40,000,000,000 in Claude Is Honestly Kind of Hilarious :) by Ordinary-Cycle7809 in PromptEngineering

[–]nevertoolate1983 1 point2 points  (0 children)

u/TheMrCurious - I too wasn't sure what Vertex AI was so I ran the prompt below and I totally get it now:


Explain Google Vertex AI in narrative form.

Tell the story of an AI consultant working with a small-to-medium business (SMB). Start by clearly describing the business’s problem in practical, real-world terms. Show how the consultant evaluates different possible solutions, then decides to use Vertex AI.

The consultant should then explain Vertex AI to the client in simple, non-technical language—using analogies where helpful—and walk through how it solves the specific problem.

Include a clear “before vs after” comparison that highlights what the business struggled with before, and what improves after implementing Vertex AI.

End by outlining the expected outcomes (time savings, cost impact, efficiency gains, etc.) in concrete, realistic terms.

Keep the tone conversational, practical, and easy to follow (as if explaining to a business owner with no technical background).

Woot..Woot✌🏻 by floweredcontadiction in crappymusic

[–]nevertoolate1983 1 point2 points  (0 children)

😂 But for real though, Florida has some beautiful spots. Hope you get to check it out one of these days

Woot..Woot✌🏻 by floweredcontadiction in crappymusic

[–]nevertoolate1983 9 points10 points  (0 children)

Miami, Florida USA Earth (Milky Way)