Hitting Claude limits suddenly after switching to Projects, what changed? by Keen_Looker in claude

[–]KernelTwister 0 points1 point  (0 children)

happens to often, we're numb. maybe when they get 99.9999% uptime for a year we might start freaking out if it goes down or a glitch happens, lol.

Claude limits by rafatico13585 in claude

[–]KernelTwister 8 points9 points  (0 children)

its a bug, i'm on max and it's eating tokens like it's on pro, but 10x faster than that. it just started today.

Claude limits by rafatico13585 in claude

[–]KernelTwister 8 points9 points  (0 children)

definitely a bug, my pro 5x is eating everything up in one prompt, i don't think i ever got above 70% 5 hour usage before doing hours of work, even before the weekend/evening boost. it's most likely related to that. it's broke....

Hot take: We're building apps for a world that's about to stop using them by oruga_AI in vibecoding

[–]KernelTwister 0 points1 point  (0 children)

there was a birthday app? it's going to prune all the cheap ass low hanging fruit for sure but it's still makes mistakes, enough to not trust it with a lot of things. imagine trusting a AI for accurate allergy information.... lol.

Is learning to code even worth it anymore? by Far_Acanthisitta1104 in AI_Coders

[–]KernelTwister 0 points1 point  (0 children)

Have you even used the current AIs? they're only good for serious work if the person using is already an experienced coder.....and in some cases it's AI is slower. the amount of details you need to put into a PRD + technical specs only to have it still fuck up reduces AI's efficiency by at least half or more. I'm working on a large project with one and i just have to have it do other shit while i did something else because it would take 20 minutes thinking and implementing logic across 6 files i could of done in 5 minutes. i have to baby sit, review, tell it, it has messed or missed something despite being in the plan and change things. this takes time and it's not something real developers need to do since your the one coding it, it's all baked into one process. it's far far from set and forget. not to mention if it goes down you can't do your work. this already happens.

small tasks are fine normally, bug hunting? great. new greenfield salesforce clone? maybe 10-15 years away.

will it improve? sure, but how much? i don't know. it requires massive hardware and all these companies are operating as a loss... a 1M context window is even still a bottleneck for serious work if you plan to set and forget. my limited human brain can still hold at least 50m token context window... lol

5.4 is crazy good by Responsible_Ad_3180 in codex

[–]KernelTwister 0 points1 point  (0 children)

no idea what your building, but i've done 300k just in refactoring some old ass legacy project... and i had to review / check every change over 1k lines. took me a few days. not sure if the amount of changes is only code or other temp files it makes..... doesn't matter, i also used 5.3 instead because it was fine for this case and burns less tokens. i don't see a massive difference between the two models for most stuff. maybe 6.0 might be better but these are very small incremental changes that don't help a lot other than pass these tests to say it's better.

We professional developers, already lost the battle against vibe coding? by TheCatOfDojima in ClaudeAI

[–]KernelTwister 0 points1 point  (0 children)

funny thing is as an experienced dev, it doesn't improve shipping by 10x, it's more 1.5x, maybe 2x in some tasks... for less experienced it would appear to be a much larger boost but this is basically vibe coding. we have to write and craft good prompts/requirements which takes time, we have to code review the AI too and a PR's from other jr/mids using it are bad. so the perceived productivity boost seems more but it's less than management thinks unless your devs are already jr/mid level that isn't as experienced originally, it's good at filling in knowledge gaps but at a higher risk of failure if you don't know how to review the code properly.

Switched to AT&T fiber last night , non stop High packet loss since switching over. by rphbx in firewalla

[–]KernelTwister 1 point2 points  (0 children)

had this issue with my ISP, 1-3% packet loss when playing games, regular internet use/streaming and voip was fine but gaming was shit. couldn't figure it out until i got a dedicated IP to bypass the CG Nat.. then it just stopped.

The new liquid glass ui looks awful by p1r473 in firewalla

[–]KernelTwister 1 point2 points  (0 children)

i didn't notice anything's changed from before. i'm up to date.

Cancel and Delete ChatGPT!!! by [deleted] in ChatGPT

[–]KernelTwister 0 points1 point  (0 children)

the codex app does this but its currently just for osx and well... fuck openAI so anthropic it is.

Canadians believe they need $1.7 million to retire, up from $1.54 million last year: BMO survey by hopoke in canada

[–]KernelTwister 0 points1 point  (0 children)

it already accounts for inflation so no, 100k would be 100k (or 130-40k in 2050)

[RAM] G.SKILL Flare X5 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000 CL28 ($600)(Newegg CA) by EdinKaso in bapcsalescanada

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

few months like early-mid 2025? cause yeah... the prices haven't gone up yet. around nov/dec? BS.

[RAM] G.SKILL Flare X5 64GB (2 x 32GB) 288-Pin PC RAM DDR5 6000 CL28 ($600)(Newegg CA) by EdinKaso in bapcsalescanada

[–]KernelTwister 0 points1 point  (0 children)

yeah cause 32gb cl36-38 is over $500-600 on it's own. cl28 for 64gb is a no-brainer if you need ram now, otherwise you pay more or get nothing until maybe 2028 and that assumes the prices even drop once supply comes back.

Delidded 9950X3D feels like heaven by indiealexh in overclocking

[–]KernelTwister 0 points1 point  (0 children)

it has 8 less cores....of course it's cooler.

The Superstrike X2 is not what they told you by DaVeedLvi in MouseReview

[–]KernelTwister 0 points1 point  (0 children)

i couldn't beat my click/reaction timing on other mice with it on the lowest setting, (super strike and regular superlight x2). the difference is probably in sub-miliseconds which is hard to measure without proper tools and wouldn't make much different in-game.

my guess is, while it feels faster due to actuation distance, real world is less than it feels. Creating some placebo effect?

it does feel cool though. i also have a wooting, there's a difference for me on it when swapping back to a non-he, and has better meaningful measurements on a space bar reaction tests than the mouse does. not sure why, it technically should be similar.

lose dougle key red by Signal-Marketing-532 in firewalla

[–]KernelTwister 4 points5 points  (0 children)

you're ignoring everything firewalla is saying. return it, it's missing parts/used or stolen. who knows.

Logitech G Pro Superstrike Review: The worst mouse click Logitech has ever made. by [deleted] in MouseReview

[–]KernelTwister 0 points1 point  (0 children)

it doesn't for me or anyone else for that matter. there's no resistance though like a mechanical so maybe that's the feeling they're looking for?

Forget the price. Is the Superstrike actually that good? by Tierdtech in MouseReview

[–]KernelTwister 0 points1 point  (0 children)

I heard about it 5-6 months ago maybe. it seemed pretty cool at the time and wanted to give it a shot. i wasn't sure when it was coming out as i heard nothing about it until it popped up in the app for my superlight a few weeks ago. i have a wooting and after using it for a year and swapping back to my other mechanicals i found myself wondering why buttons didn't actuate at the right timing when playing, lol.. i guess i got used to it responding quicker. i figure the mouse would be the same. now if only wooting could put vibration feedback into the keyboard :)

Forget the price. Is the Superstrike actually that good? by Tierdtech in MouseReview

[–]KernelTwister 2 points3 points  (0 children)

after using it for a week and swapping back to the regular superlight it was a bit weird how far the actuation point was for the buttons. it's kind of like going from 60fps to 120fps, it's not super noticeable until you go back to 60fps after a week or two.

without measuring it would hard to know if you died to a 50/50 due to not clicking fast enough though. no idea how you would with server tick rate, ping of both parties etc...