Recent submissions

Comment · 4 years ago
In this thread, people making all sorts of claims about print() debugging being better because of speed, efficiency, less overheard, “debuggers are too hard”, etc. on and on, but not actually providing evidence for their claim. For example, how do you know it’s faster for you? Less overheard by what comparison? Like did you give a debugger an equal and fair shot for some appreciable amount of time? I routinely probe these type of assertions from my coworkers about print()’s superiority and find that ~75% of the time, they’ve never given the debugger a fair trial or invested in understanding all it’s strengths and capabilities. ~25% of the time they’ve done a fair comparison and print() debugging is indeed the right choice for their context. Fine. Good for them! Every now and then someone takes me up on teaching them how to use a debugger effectively though and they are almost without exception, albeit begrudgingly, astounded at what they’ve been missing out on only using print().
Comment · 4 years ago
Build a shadow ban mode and assign them to it :)
Comment · 5 years ago
Obviously it’s not useless if people find it useful such as the people who compete. By some metric you care about it may be “useless”, but who made you the arbiter of metrics? Competitive programming may or may not correlate with success at say software engineering, but that isn’t grounds to say it’s useless. An Olympic archer may or may not be a terrible bow hunter in the wilderness but they still have a clear skill that is useful by metrics such as people want to watch it, practice it, and compete in it. Dualist thinking like this where things are strictly good/bad, useful/useless, etc. is a really limiting thought pattern. How about instead of “is this thing useful OR useless?” we ask “in what ways is this thing useful? In what ways is this thing not useful? How can we best leverage these properties?”
Comment · 5 years ago
A lot of overlap with Knime and Rapidminer. Why approach it with visual programming vs the direct execution graph approach like they do?
Comment · 6 years ago
If they aren’t “fastidious about truth” probably. If they are, and they know you are being “curious”, you will likely have a cool, engaging conversation on your hands.
Comment · 6 years ago
Hey, nice comment! Please do this please.
Comment · 6 years ago
Comment · 6 years ago
Comment · 6 years ago
He's says "you've got to dominate them" like 5 times in the first 10 minutes of the call and he's not distinguishing or nuancing between the different types of protesters or allowing for a range of response. It's all "radical left" and "ANTIFA" to hear him tell it. He doesn't given a single acknowledgment in the whole call that these protests are happening directly because of systemic, pervasive police brutality and therefore some sensitivity and humbleness might also be in order here in responding to the situation. So yeah, chilling.
Comment · 6 years ago
Absolutely chilling.
Comment · 6 years ago
Looked up “HOPS (for Heuristic Optimized Processing System)” but didn’t find any good direct hits. Can you point me to some good starting points?
Comment · 6 years ago
Please don’t make it infinite scroll instead. Begging you. Please.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton