But can't you instead just set a breakpoint next to wherever you are gonna put that print stmt and inspect value once code hits? print stmt seems like extra overhead
Debuggers allow you inspect stuff forward in time, while print statements allow you to debug backwards. (There was a lot of academic work on reversible debuggers at one point; to be honest I haven’t kept up on how that turned out.)
If you can detect a problematic condition and you want to know what will happen next, a debugger is a great tool.
If you can detect a problematic condition and you need to find out what caused it, it’s printf all the way.
My theory is that different types of programming encounter these two types of problems at different relative rates, and that this explains why many people strongly prefer one over the other but don’t agree on which.
While also avoiding having to re-run cases to get new introspection when you forgot to add a print statement.
I tend to do both, print statements when I don't feel I want to be stepping through some cumbersome interplay of calls but diving into the debugger to step through the nitty gritty, even better when I can evaluate code in the debugger to understand the state of the data at precise points.
I don't think there's a better or worse version of doing it, you use the tool that is best for what introspection you need.
> "The loop of prompt->study->prompt->study... is disruptive to my inner loop for several reasons, but a big one is that the machine doesn't "think" like i do. So the solutions it scaffolds commonly make me say "huh?" and i have to change my thought process to interpet them and then study them for mistakes. My intution and iteration is, for the time being, more effective than this machine assisted loop..."
My thoughts exactly as an ADHD dev.
Was having trouble describing my main issue with LLM-assisted development...
Nobody claims the pope. This is a weird take. We are not talking about some sport celebrity.
It’s true that the man was born in the USA and was a bishop in Peru. I wouldn’t be surprised if the Peruvian catholics were happy to have a pope who lived their country.
> The Peruvians definitely seem to be happy about it
I don’t really see that from the articles you linked.
It’s all quotes about how the Pope is Peruvian (definitely true as he indeed has the Peruvian nationality) and how Peruvian people feel blessed in that.
Even your last article reinforces that he is a dual citizen with knowledge of both culture which obviously makes people joyful.
I have yet to see people argue if he is more American or more Peruvian apart from here.
Hey samsepi! Thanks for the interest, the version provided should run fine on Apple Silicon. I'm using an M1 and it's working fine, let me know if you have any issues and we can do a separate build that may address any issues you face.
Sports gambling ads have become so pervasive that it’s hard to watch a game without being bombarded by manipulative promotions that say stuff like "BET $5, GET $200 INSTANTLY"...
I became a recreational sports bettor in college through offshore books. I always felt like I was doing something extremely dangerous and so was very careful - probably in large part because of the societal stigma surrounding sports betting. I feel like I benefited from having instilled in me a greater fear of gambling dangers that I wouldn't have now if I just started gambling after seeing all these prominent sports talking heads discussions, social media influencer promotions, and constant TV advertisements.
Trying stricter regulations feels like a no-brainer before totally reverting to a federal ban.
At a minimum, we should match the intensity of regulations for other legal vices:
- National min. age of 21 for any state that legalizes sports betting, matching drinking regulations that were set 40 years ago.
- Restrict advertising to audiences where you can confidently report that >70% of which are adults >= 21 years old, similar to recreational marijuana advertisement regulations in states like CA.
- More intense warnings should follow each ad, clearly emphasizing the risks of addiction and the likelihood of financial loss, similar to the mandatory disclosures in prescription drug ads.
Additionally, for the unique vice of sports gambling and it's associated societal dangers, there should be:
1. More intense restrictions on ads:
a. Clearly disclose all stipulations. For example, language like ‘BET $5, GET $200’ should be accompanied by fine print explaining that the bonus bet can’t be withdrawn, and any winnings must be wagered multiple times before withdrawal.
b. Transparent statistics of users' outcomes at specific sports book. Something like: "Y% of our customers who have accepted a bonus bet have successfully turned it into real cash in their bank account. The remaining (100-Y)% lose it all."
2. Regulations on sports book's social media accounts promoting individual bettors' winnings - i.e. Sports books shouldn't be able to promote a story about someone winning $100k on a $1 20-team parlay.
3. Roadblocks, at a minimum, on betting losses for vulnerable groups -- e.g. after a bettor has lost X% of their initial deposit/yearly salary/net worth/etc, the bettor's account should be restricted in some way unless they say to a real person on the phone: "YES, I AM AWARE OF HOW MUCH MONEY I'VE LOST. I WISH TO RISK LOSING MORE MONEY."
4. A requirement that all bets be placed with money deposited via debit card/check/cash. A ban on taking on any kind of debt (like using a credit card to deposit funds into betting account) to place a bet seems reasonable.
I found this tool (repo2file) helpful for my workflows - quickly giving context for questions to my local LLM about my working (small) repo in the terminal.
Until I saw this post, I wasn't aware of any of those.
What makes his better? Since you're asking, I tried these and here's my verdict:
- [files-to-prompt](https://github.com/simonw/files-to-prompt) (from the GOAT simonw)
--> There's no option to specify files to include, must work backwards with ignore option
- [1filellm](https://github.com/jimmc414/1filellm)
--> Many dependencies and complicated setup(have to setup GitHub access token which I've never done)
