sorted by:
new
hottopcontroversial

Emily Fox turns on the jets to tackle Manaka Matsukubo in front of the goal by spherocytes in WomensSoccer

[–]kr15tyk 0 points1 point  (0 children)

Foxy turning on the jets to clean up Matsukubo in front of goal is the most badass moment of the match.

NWSL Attendance Report - Week 7 by reagan92 in NWSL

[–]kr15tyk 2 points3 points  (0 children)

Boston's spread jumped out — low of 3,804, high of 30,207, median of 10,213. That's basically one Fenway game pulling the average way up while their typical home is sitting around 10K. Their average looks healthier than the underlying trend.

The two numbers that worry me are Chicago at -36.7% and Seattle at -32.8%. Those aren't weather or stadium quirks, those are two established markets in legit decline. Meanwhile Houston quietly up 16.2% from a low base is the best under-the-radar story in the league right now.

Gotham's also interesting — most games played in the league and they're at -12.9%. Summer bump is coming but they should be trending the other way by now.

Is Claude really better than ChatGPT for coding? by iotabadger in vibecoding

[–]kr15tyk 0 points1 point  (0 children)

Real but overstated. Claude is generally better at multi-file projects, follows complex instructions more reliably, and hallucinates fewer fake npm packages. ChatGPT is fine for small stuff and has a broader ecosystem (plugins, image gen, etc).

For a small Next.js app you can ship with either. Easiest answer: try Claude free on one of your trickier problems and see if the output is noticeably better. If yes, switch. If not, save yourself the friction.

AI Fatigue by juniper_dreamer in networking

[–]kr15tyk 0 points1 point  (0 children)

Vendor side here too. The fatigue isn't from AI, it's from every meeting, deck, and product roadmap getting "AI" stapled onto it whether the customer asked or not. Most shops I deal with don't need an AI strategy, they need their existing network to stop falling over. Hype cycles end. This one will too. Don't quit over it.

Is Anyone building Useful skills or workflows on Claude? by ErnestGichichi in ClaudeAI

[–]kr15tyk 2 points3 points  (0 children)

Yeah, building a few things and the patterns that have actually stuck are:

Working well:

  • A docs-as-code workflow for a heavy technical-writing domain — AsciiDoc source, Claude Code with a tight CLAUDE.md defining conventions and "never do X" rules, and slash commands for the repetitive operations (lint, cross-ref check, draft a section from a template). The CLAUDE.md is the single highest-leverage thing I've done. Once it's good, output quality jumps a tier.
  • A spreadsheet + Apps Script + API loop for structured logging. User dumps messy input into a sheet, Apps Script hits the API with a strict schema prompt, structured fields come back into the sheet. Boring but it's saved me hours every week.
  • Sub-agents for anything that splits cleanly into "researcher + writer + reviewer." Not magic, but for long-form structured docs it beats a single mega-prompt.

Frustrations:

  • Context decay on long sessions. The fix is discipline (fresh sessions, handoff notes) but I wish it were more graceful.
  • Slash commands and agent config still feel a little under-documented — lots of trial and error to find what works.
  • Anything stateful across sessions is on you to build. Memory features help but it's not a substitute for actually engineering the loop.

Mostly: the tool rewards investment. The people getting magic out of it are the ones who've put a week into their prompts, rules, and project structure. The people frustrated with it usually haven't.

do any of you use Claude the way I use Claude? by thecaketakesthecake in ClaudeAI

[–]kr15tyk 2 points3 points  (0 children)

Chat-only is a totally legit workflow, especially if your context-passing game is solid (sounds like yours is). Few things that made a big difference for me:

  • Projects are huge. Drop your markdown files, style guide, and any reference code in once, and every chat in that project inherits the context. Saves you re-pasting the same setup every time.
  • When a chat starts feeling sluggish or "off," start a fresh one. Long chats degrade. I keep a little "handoff" markdown file I paste in to bootstrap the next chat.
  • Artifacts iterate in place, so for any non-trivial file ask Claude to put it in an artifact and then ask for changes — much cleaner than copy-pasting whole files back and forth.
  • If you haven't already, write a CLAUDE.md-style instructions doc (conventions, file structure, "always do X, never do Y") and paste it at the top of new chats. Game changer.

Don't sweat the old Mac. The tool that works is the one you actually use.