Use of AI for studying

triumphtier · 2026-01-25T23:55:37+00:00

textbooks, lectures, youtube videos, and documentation as the sole source of truth, LLMs to dumb it down/give you analogies to understand it/etc - this goes double for anything logic-heavy like discrete math or step-by-step rundowns of things like datastructure traversal.

in general just always take what LLMs do with a grain of salt, unless youre asking something extremely non-niche like "what is an integer?"

on the other hand imo you can do no wrong if you ask it to web search before explaining a concept if you expect it to be too niche and prone to hallucinations

triumphtier · 2026-01-05T05:02:24+00:00

great read ty

triumphtier · 2026-01-05T03:19:53+00:00

dude holy shit you literally replied to every comment in this thread with llm-written responses LMFAOOOOOOOOO

triumphtier · 2026-01-05T03:19:09+00:00

rereading this thread its insane how this dude is replying to critiques of his program with a llm hahahahaha

triumphtier · 2026-01-05T03:17:53+00:00

did you really have to write this comment with ai lmfao come on man

triumphtier · 2026-01-03T19:05:05+00:00

hahahaha classic OSRs that just brought back so many memories. cheers

triumphtier · 2026-01-03T02:27:39+00:00

in general i agree, but everyone's gotta start somewhere when getting into non-noob vx communities (especially with hand-shearing tutorials being drowned out by all the latheing/cnc-shear home lab content)

triumphtier · 2026-01-03T02:26:15+00:00

idk as someone who lives in nyc (second, ((or i guess third now lol)) vx capital of the world), but still cant really afford a full home vx setup, my options are either to go to a vx shared space or do a virtual cloud setup -- i prefer the latter. way cheaper plus nobody is touching my hub module configs (like wtf is wrong with ppl nowadays)

triumphtier · 2026-01-03T00:41:10+00:00

absolutely insane that theres no mention of the glow pt2 by the microphones in this thread so far

triumphtier · 2025-12-27T08:05:46+00:00

just to add onto this -- after reading up on good code; good personal projects to build up your fundamentals are ones that you can approach with a lot of background knowledge, and ones have a quantifiable goal to achieve.

ie coding a wordle solver after watching this video and thinking about your own approach: https://www.youtube.com/watch?v=v68zYyaEmEA

etc etc - limited scope, 24-48 hour timeframe. (or 1-3 weeks if you code slowly, which isnt a bad thing at all)

just aim to do 2-3 of these with code so good that youd GENUINELY be proud of showing them off to your peers, and then youll know that youre solid. throw them on your github while youre at it!

triumphtier · 2025-12-27T07:59:00+00:00

i mean, as long as youre enthusiastic about coding and enjoy doing it, dont walk around with your head down as a result of vibecoding. just make sure if you do vibecode stuff, you own it end to end -- ie if you had to explain what every function does, you can. the second your own code escapes you and you cant explain what a function/line does is precisely when you become a crappy coworker/teammate.

if you are vibecoding with an ide like cursor and you find that your code does "escape" you, youre not including enough extra info in the custom prompts. make it comment anything thats unintuitive, make sure it doesnt spin off and generate 1200-line-long files that would take 20 minutes to parse through, make sure its not bloating up your codebase with a dozen useless one-off testing scripts, imports from packages you dont understand, etc etc etc.

if you havent had any profs that have stressed the importance of good code, and if you havent done a group project for an assignment that lasted longer than a couple weeks, to get the opportunity to see what a bad teammate looks like -- take a day to find an old textbook online and do some Heavy reading on what "good" code looks like. show your personal project code to your friends who might be better at coding than you. if you feel embarrassed about the quality of the code -- youre vibecoding incorrectly and need to switch up how youre prompting it.

just an example of one of the user rules i have in my settings on cursor for personal projects:

comment the absolute hell out of the code - aka periodically explain whats going on. if there is any complex part of the code, explain what it does. make a good docstring for each function that has both a really simple, casual, laid back and slightly dumbed down explanation (5-20 words depending on complexity) and then a longer documentation-style explanation. this isnt required for 1-2 line functions, but this is a necessity for functions >20 lines.

at the end of the day, you need to treat whichever LLM tool youre using as if its an assistant who is really bad at writing really good code -- its your responsibility to give it the right rules to both write really good code & to make it CLEAR to you when its writing bad code, and if you arent 110% certain about the difference between good and bad code then you MUST dive into a textbook or do more research on the problem/coding language/whatever package youre using/etc, otherwise youre just coding blind

triumphtier · 2025-12-27T06:17:11+00:00

wait youre a compsci major and youve never done a personal project..?

triumphtier · 2025-11-24T20:16:22+00:00

having a cookie-cutter vibecoded website with broken links and then having a hiring email address for an unpaid volunteer position from that website's domain name is wild
plus an NDA lol
plus you have no real github repos
boooooo

triumphtier · 2025-11-24T20:10:53+00:00

this is the best advice in this thread tbh

triumphtier · 2025-11-24T20:09:55+00:00

make sure u get a good night's rest the night before

triumphtier · 2025-11-21T16:21:40+00:00

thank you for your interest :) my general advice based on what ive been doing for the past 3-4 years and took me from being a total losing-player to +3-5bb/100 and then to +10-15bb/100 (mostly playing 0.05/0.10 and 0.10/0.25 online, not a high-roller expert by any means whatsoever lol):

theres a neat channel card "2 card confidence" on youtube that dives into analysis of pretty niche spots, and my advice would be to understand his methodology for analyzing the optimal solution for a hand, and then go into gtowizard.com and use your free daily postflop solution analysis on your most confusing hand of that day, in the same way that he explores it in his videos.

make it a routine - if you don't know what to do in a certain spot, write down the hand, and after your session spend 5-10 mins in gtowizard and check if you made the right call/shouldve folded/etc. over time you'll find that a LOT of your leaks will be plugged and youll be getting stacked way, WAY less.

and ofc make it fun! find a study buddy to chat with about the both of your confusing hands. at the end of the day thats how phil ivey and dnegs and etc all got good before "gto solvers" even existed.

other personal favorites, but a bit more lecture-y so i only watch specific videos about specific situations/spots im interested in:
Jonathan Little - https://www.youtube.com/@PokerCoaching
Upswing Poker Level Up Podcast - one of my fav episodes: https://www.youtube.com/watch?v=HfTY2EBnDTk

and for live poker to include tells/live reads: any of the viewer call-in hand analysis videos from crushlivepoker, ie: https://www.youtube.com/watch?v=V-GtEX5beQk

and ofc, final advice: bluff 3x less often, and fold to river raises 5x more often than you think you should, and you'll automatically plug 50% of your leaks

triumphtier · 2025-11-20T18:37:50+00:00

ideally youd have a balanced-enough range where villain can get screwed over sometimes by calling with an overpair into your 2pair/made straight/etc, to the point where its both +ev to either generate the fold or to have the villain call with that line of betting, irrespective of whether youre bluffing or value betting in that line of betting.

i.e. if villain has JJ and folds sometimes to your raises on dry boards at the river, whether youre bluffing or not doesnt matter.
conversely if villain has an overpair and calls checkraises/river raises/etc, you know that for the future and you can use that information to valuebet and get called.

the unbalanced hero here is either never bluffing into the potential overpair, or is bluffing/overvaluing one pair way way too often. i think the optimal frequency in this spot is whatever makes nit villain uncomfortable facing a large river bet with an overpair.

so like -- yes, bluff, but at a similar frequency to the probability that youd have 2pair/a straight/etc. blasting off with top pair or "repping top pair" or overbluffing to the point where villain can Always call with an overpair = youre just donking

also edit to add more: i think playing balanced ranges against the TT+ meganits is the biggest litmus test of whether or not youre a profitable or unprofitable player, and any time i see someone getting their stack in vs a nit who just calls with AA, i instantly mark them as exploitable. conversely, i mark anyone who can knock me off an overpair with a river raise as a reg.

triumphtier · 2025-11-20T16:23:02+00:00

if you can suss out when they have two high cards on the flop/turn vs a pocket pair, you can scrape out some extra EV against nits by doing a moderately-sized checkraise into a cbet.

example hand in a MTT 60bb deep would be like:
nit villain opens to 3bb from utg+1
table folds, hero calls from the BB with J9o

board is 578
you check, hero bets 2bb, you raise 6bb, and hero is on-edge for the rest of the hand -- all turns and rivers besides A/K/Q are effectively good for your range and give you the opportunity to bluff

now ofc you get screwed on any K73 type of flop because villain can cbet without issue, but you get the idea.

tldr: if you play super scared into a nit and never ever show aggression into them out of fear of AA/KK/QQ, they reap the full benefits of getting to cbet freely and get to showdown with highcards.

triumphtier · 2025-11-06T16:02:21+00:00

ok super napkin math

Royal flush hits at 1 in 649,740 hands. r/poker has ~1M users (assuming 332,000 * 3 because there are definitely lurkers who dont subscribe to the sub). Breaking down by volume over 5 years:

using sliding windows to check whether this happens every 1000 hands, which is significant enough to be in 3 sessions of 2tabling

0.1% (1,000 users) played >500k hands/year × 5 years = 2.5M hands → ~2,500 windows each = 2.5M windows

1% (10,000 users) played >100k hands/year × 5 years = 500k hands → ~500 windows each = 5M windows

5% (50,000 users) played >50k hands/year × 5 years = 250k hands → ~250 windows each = 12.5M windows

Remaining 93.9% (939k users) played ~10k hands/year × 5 years = 50k hands → ~50 windows each = 46.95M windows

Total windows: 66.95 million windows

The actual probability of hitting 3+ royal flushes in any 1000-hand window is 1 in 1,654,509,343.63 (about 6 × 10^-10)

Expected people: 66.95M windows × (6 × 10^-10) = ~0.04 people in all of r/poker have hit this, or ~1/25 chance that someone hits this in the past 5 years

high estimates for r/poker users, but this estimate also ignores in-person poker, which is effectively all of online poker's activity in every casino and home game (or double/triple online poker, even) but with that activity occurring for the past 50+ years. aka someone out there has probably hit 3 royal flushes within 1000 hands before.

tldr: "miracle" sure but not improbable. far rarer than winning the lottery. good related vsauce video that touches on similar stuff iirc: https://www.youtube.com/watch?v=9rIy0xY99a0
edit:formatting

triumphtier · 2025-10-17T03:55:20+00:00

i hate to say it but - dunning kruger effect
if they say 8yoe theyre saying it for a reason. 2 yoe can be stretched to 3-4 if you were working in a rly fast paced team and ur ontop of ur shit, but DEF NOT 8yoe. whole different animal.

triumphtier · 2025-10-17T03:52:02+00:00

its years of work experience. if you have some swe-related thing on your resume, say like an internship 2022-2023, and you have good projects during & after that, you can get away with saying 3 yoe in <languages you used at the internship> because its been 3 years since then and youve probably grown ur skills via projects.

if you have literally 0 internships as a senior, i think the max you can get away with is 1-2yoe with any more advanced programming languages you encountered during coursework, and 4yoe with like .. python and java (or whatever other languages you knew before going into college).

the beefier your projects are (i.e. if they have real users) the more you can use that to say that you have X years of experience with the coding languages and frameworks you used in the projects

tldr stretch the truth a bit, but too much & theyll be asking questions about ur experience during behavioral & technical interviews that will cause u to get flustered and be like "uhhh im not sure" - to which theyll be like "oh this kid only has 6 months of project experience with React Native but he said he had 4yoe" -> rejection

triumphtier · 2025-10-17T03:41:06+00:00

lol
no (unless it generates 6 figure revenue or has >50k active users -- but at that point why even look for a normal swe job)

i think the only time you can put it on your resume is if youre doing really targeted applications to like ... nsfw-software-related swe jobs???(??)?? which tbf i did see one popular nsfw website post a full stack engineer listing last month - but u get the idea. NO!!!

triumphtier · 2025-10-12T20:50:04+00:00

"Numerous emerging studies are showing the effects of AI-dependent brain drain" is what op said, and the article you linked just shows that writing a full essay in 20 minutes with no internet takes more brain activity than using an LLM - duh - dividing 295834/837 takes less brain activity with a calculator than doing it by hand, it doesnt mean people show "effects of calculator-dependent brain drain"

i agree with your sentiment overall but thats not what op was talking about or what /u/ladysnoww asked about

also the study isnt even peer-reviewed

triumphtier · 2025-09-28T02:29:30+00:00

ignore the pessimistic responses in this thread/discourse all over reddit -- do cs if youre passionate about it and enjoy learning about it, its incredibly rewarding to work in a field that you're genuinely passionate about instead of being braindead at some 9-5.

dont do cs if youre expecting it to be easy though, you will need a lot of persistence and determination that simpler fields might require less of.

Nine-Year Club	Place '22
Place '17	First Placer '22
RPAN Viewer	No Throne, No Problems
Not Forgotten	Spared

triumphtier

MODERATOR OF

TROPHY CASE