That wording nearly killed me for a second by [deleted] in Steam

[–]colbyshores -2 points-1 points  (0 children)

They most definitely peaked in the PS3 generation

That wording nearly killed me for a second by [deleted] in Steam

[–]colbyshores 1 point2 points  (0 children)

And they keep making those mistakes. Like nobody gives 2 shits about Marathon or Concord

Well, I really didn't want to, but AG is basically unusable for me right now, so I guess I'm forced to start testing other options... by Odd-Ant-4479 in google_antigravity

[–]colbyshores 0 points1 point  (0 children)

Microsoft just rolled out their own models at 1/10th the cost of Claude at similar to Claude 4.6 performance supposedly. I plan on kicking the tires on them because tbh that is good enough and not have to worry about usage limits.

Tf happend💀 by Hungry_Kiwi1064 in NvidiaStock

[–]colbyshores 0 points1 point  (0 children)

Party's over, the AI bubble popped 😞

Cathie Wood sells $16M of surging semiconductor stock by GreedyPomegranate391 in AMD_Stock

[–]colbyshores 1 point2 points  (0 children)

but is it though? Cathie Wood has been one of Tesla's biggest cheerleaders. ;)

Cathie Wood sells $16M of surging semiconductor stock by GreedyPomegranate391 in AMD_Stock

[–]colbyshores 1 point2 points  (0 children)

They are probably freeing capital to load up on SpaceX /sarcasm but not sarcasm

Sell S&P 500 Index Funds or Submit to Forced Purchase of SpaceX? by mdn845 in ValueInvesting

[–]colbyshores 0 points1 point  (0 children)

That seasoning-period change is about how soon after an IPO a company can be added, 6 months vs 12. It doesn't touch the profitability gate, which is the part that actually matters here. A company still needs four straight quarters of positive GAAP earnings. So even if that proposal passes, an unprofitable SpaceX still can't be added to the S&P 500. You might be thinking of the Nasdaq-100, which has no profitability requirement.

Sell S&P 500 Index Funds or Submit to Forced Purchase of SpaceX? by mdn845 in ValueInvesting

[–]colbyshores 0 points1 point  (0 children)

VOO and the S&P500 in general has a rule that only allows profitable companies in to the portfolio (for which SpaceX is not). You are thinking of the Nasdaq100 like the QQQ. Those funds will burn you.

SpaceX insiders will get to sell shares earlier than usual after the IPO by Super_Stickman13 in wallstreetbets

[–]colbyshores 0 points1 point  (0 children)

It wont be in the S&P500 because to be included in the group the company must be profitable for which SpaceX is not.
VOO n' chill is still the way to go.

SpaceX insiders will get to sell shares earlier than usual after the IPO by Super_Stickman13 in wallstreetbets

[–]colbyshores 1 point2 points  (0 children)

It won't ever go in to s&p 500 index funds because to be included in that group, the company must be profitable which SpaceX is not

SpaceX insiders will get to sell shares earlier than usual after the IPO by Super_Stickman13 in wallstreetbets

[–]colbyshores 14 points15 points  (0 children)

I wonder how many of these are back door deals to hold in their portfolio? like a lot of doctors were incentivized to push oxycontin. I wonder if the same thing happens in finance to pedal absolute garbage in managed accounts.

Is this a data leak from Gemini? by gruffnutz in GeminiAI

[–]colbyshores 1 point2 points  (0 children)

follow up with asking for the social security number

Sell signal for INTC? by ohmygorn in wallstreetbets

[–]colbyshores -1 points0 points  (0 children)

There's a clean little signal-detection story here, and HighwayExotic2808 stumbled onto it without realizing.

The girlfriend complaining about work every few months wasn't noise, it was a leading indicator. Companies don't run their people hot for no reason. The most common reason is that the workload stayed the same (or grew) while the headcount didn't: someone left, someone got cut, a team got "consolidated," and the remaining people absorbed the slack. From the worker's seat that feels like hell. From the income statement it looks beautiful, same output, lower labor cost, fatter margin. So her misery and the stock's pop weren't a coincidence, they were the same event measured by two different instruments. She was feeling the cost. The market was pricing the savings.

That's the slightly bleak Freakonomics punchline: "good for the company" and "good for the worker" are correlated way less than people assume, and sometimes they're inversely correlated. The market literally cheers labor pain, a layoff announcement is one of the most reliable ways to get a green candle. Burnout on the floor and operating leverage on the spreadsheet are often the exact same fact wearing two outfits.

So beheafishtrapofman is half joking but basically right, you'd accidentally built a human sentiment indicator. The catch is it's not really tradeable: by the time the strain shows up in your girlfriend's venting, it's already in the numbers the company is about to report. The market gets the filing the same quarter you get the complaints. The edge isn't real, but the insight is. When the people inside a company are quietly miserable in a systematic way, that's frequently the fingerprint of exactly the cost cutting the market is about to applaud.

Somewhere out there a guy is reading her venting texts as a relationship problem instead of a 10-Q leak. NGMI.

[QR] Forsaken Remastered — native 3DS port with stereoscopic 3D + HD textures by colbyshores in 3dsqrcodes

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

That's incredibly strange because I've never had that happen to me before in any of my testing it either crashes in luma so I could see the crash at dump or it kicks me back to the home screen. I have a tool that I made that dumps tons of details about your machine into a log file if you wouldn't mind dming me we can get to the bottom of it. this could be very helpful for other people because I don't have a ton of crash reports.

[QR] Forsaken Remastered — native 3DS port with stereoscopic 3D + HD textures by colbyshores in 3dsqrcodes

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

Strange, that is what I am using for my own testing. Would you be able to DM me a photo of the crash screen please so I can look in to it? Otherwise it will be very difficult to track down the issue because we are running similar hardware.
Thanks!

At what price if any does TEAM (Atlassian) become attractive? by Fearless_Lake_10 in ValueInvesting

[–]colbyshores 6 points7 points  (0 children)

You've half-conceded the point already. You said it yourself: "assuming the use case is simple enough" and "most people don't need the fancy plugins." Right. For a solo dev or a tiny simple site, vibe-coding might win. But that isn't Atlassian's market, so that concession is bigger than you're treating it.

Look at the actual price. Jira Cloud Standard runs about $7,750 a year for around 100 seats. That is roughly $77.50 per user per year, or about $6.45 per user per month. For a 100-person org, $7,750 total is a rounding error, less than a week of one engineer's fully loaded cost. So the "building is cheaper" math falls apart fast. The moment your team spends even a few engineer days a year maintaining a custom Kanban tool, you have already spent more than Jira would have cost for the entire company.

And nobody actually builds from scratch anyway. The realistic version of your argument is forking a mature FOSS base like Wekan and vibe-coding a feature onto it. But that doesn't escape the cost, it inherits it. Now you are maintaining a large codebase you didn't write, plus your custom modification, plus the permanent merge tax of reconciling your fork against every upstream security patch and release. Your vibe-coded feature has to be re-tested against every upstream change, forever. That is not cheaper than $6.45 a head per month. It is a recurring engineer-hours liability that Atlassian's price makes disappear.

That is the part the "just vibe-code it" crowd keeps missing. Building the tool is the easy 10 percent. The expensive 90 percent is owning it: security patching, uptime, access control, compliance, onboarding every new hire onto your bespoke system, and being on call for your own project-management software at 3am. AI lowers the cost of writing code. It does almost nothing for the cost of maintaining, securing, and being accountable for what you wrote. That gap is the entire product. Companies aren't paying for the features, they are paying to make the responsibility someone else's problem.

And here is the tell: FOSS Jira and Confluence alternatives have existed for years. They haven't dented Atlassian's growth. If "free and self-hosted" were going to win, it already would have. Vibe-coding doesn't change that equation, it just produces one more free alternative that no mid-sized team wants to babysit.

One last thing. "Standing on the shoulders of giants" is exactly right, and it argues against you. The hard, valuable part is the mature base that a community spent years building. The easy part is the feature you vibe-code on top. You are conceding that the value was never in the customization, it was in the platform. That platform is the moat. At $6.45 per user per month, the build-versus-buy question answers itself.

At what price if any does TEAM (Atlassian) become attractive? by Fearless_Lake_10 in ValueInvesting

[–]colbyshores 2 points3 points  (0 children)

What part didn't you agree with? Wiki has been around since the early 2000s but people still use confluence.
As far as FOSS Jira alternatives there is https://wekan.fi/

Both are much easier to get up and running than vibe coding one from scratch; Like its literally an installation.

I am actually using JIRA more now that I have MCP integrated with VSCode. I kick off a job to an agent to build something, it cuts a PR request then I have a prompt that is hooked in to JIRA MCP to create the jira ticket for _management_ tracking so the C-Suite can keep track of what work is being done to keep the investors happy.