←back to thread

Big Book of R

(www.bigbookofr.com)
288 points sebg | 2 comments | | HN request time: 0s | source
Show context
cye131 ◴[] No.43649039[source]
R especially dplyr/tidyverse is so underrated. Working in ML engineering, I see a lot of my coworkers suffering through pandas (or occasionally polars or even base Python without dataframes) to do basic analytics or debugging, it takes eons and gets complex so quickly that only the most rudimentary checks get done. Anyone working in data-adjacent engineering work would benefit from R/dplyr in their toolkit.
replies(6): >>43649143 #>>43649208 #>>43649881 #>>43650319 #>>43650677 #>>43683325 #
kasperset ◴[] No.43649143[source]
I love R and dplyr. It is very readable and easy to explain to non-programmers. I use it almost everyday. Not exactly on the topic,I am having difficulties debugging it. May be I need to brush up on debugging R. Not sure if there is a easy way to add breakpoint when using vscode.
replies(2): >>43649189 #>>43651350 #
JackeJR ◴[] No.43649189[source]
browser() ?
replies(1): >>43651046 #
disgruntledphd2 ◴[] No.43651046[source]
trace subsumes browser, it's much more flexible and can be applied to library code without editing it.
replies(2): >>43653795 #>>43657274 #
1. tylermw ◴[] No.43653795[source]
trace is great for shimming in your own code to an existing function, but it’s not an interactive debugging tool.
replies(1): >>43655610 #
2. disgruntledphd2 ◴[] No.43655610[source]
It sure is. If you set the second argument to browser you can step through any function.