Summary #
Your best, your worst and the basics.
Limited to the 1000 most recent submissions and comments.
redditor since
Apr 15, 2011
14 years, 11 months ago
data available from
Jan 22, 2026
longest period between two consecutive posts
2 weeks
Jan 22, 2026 to Feb 09, 2026
gilded
0 submissions and 0 times from comments
submission karma
373 from 2 submissions
186.5 average karma per submission
212 total submission karma reported by reddit
comment karma
8334 from 892 comments
9.34 average karma per comment
7217 total comment karma reported by reddit
best comment
They actually do slip sometimes! Trains have sand dispensers that drop sand onto the rails when the wheels start to lose grip, especially in wet or icy conditions. You can sometimes hear a hissing sound from a locomotive as it pulls away from a station -- that is the sander. The reason they mostly grip fine is weight. A locomotive weighs 100+ tons, and all that weight pushes down through a contact patch roughly the size of a coin on each wheel. Friction force depends on both the coefficient of friction AND the force pressing the surfaces together. Steel on steel has a lower friction coefficient than rubber on road (roughly 0.3 vs 0.7), but the train is so absurdly heavy that the total friction force is still enormous. Think of it like this: try sliding a heavy cast iron pan across a steel countertop. The surfaces are both smooth and hard, but it still takes real effort because the weight creates a lot of friction. The low friction coefficient is actually a feature, not a bug. It means once the train is moving it takes very little energy to keep it rolling, which is why trains are incredibly fuel efficient compared to trucks hauling the same freight. (permalink)
worst comment
Great breakdown, especially the point about bridges adding debugging complexity. Went through a similar journey. One thing I landed on after testing different approaches: for native iOS apps specifically, Claude Code turned out to be surprisingly effective. The key insight is that Claude actually writes solid Swift/SwiftUI when you give it the right context. You can iterate much faster than with visual builders because youre working directly with the source code. The workflow I settled on: describe what I want, let it scaffold the screens, then refine. No export step, no code translation, just actual Xcode-ready Swift files from the start. For the backend guy who needs mobile apps angle you mentioned - if you already know how to work with APIs and understand data flows, Claude Code closes the gap faster than learning FlutterFlow or Sketchflow IMO. The mental model transfer is more direct. One tip: if you want to iterate on mobile stuff from your phone (like reviewing what the AI did while commuting), theres an app called Moshi that gives you terminal access to Claude Code sessions over SSH. Useful for kicking off changes or reviewing code when away from your desk. (permalink)
best submission
Claude made me an ASCII art cat that follows your mouse cursor (permalink)
worst submission
I Asked Claude to Compare My Setup to Ralph Loops. It Picked Mine. (permalink)
Synopsis #
Accuracy or making sense not guaranteed. Results may be incorrect or misleading.
Uncertain data is in orange. Follow # links for sources.
entrepreneurship
dev #
conversational ai
programming
saas businesses
software development and career ad…
large language models
in terminal-first workflows #
phone # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
desk # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
machine # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
workflow # # # # # # # # # # # # # # # # # # # # # # # # #
laptop # # # # # # # # # # # # # # # # # #
experience # # # # # # # # # # # #
claude code session # # # # # #
spec #
camera #
background #
voice #
target user #
app solves #
library #
thought #
side project backlog #
niche #
partner #
answer #
database transaction #
forehead #
experience udp hole #
result #
session cost #
post #
day #
brain #
work day #
everything #
number #
water #
launch #
deck #
bounce rate #
storage #
regret #
quality level #
bandwidth #
logic #
question #
pipeline overnight #
growth strategy automation #
head #
desktop #
flow #
photo #
motivation #
app moshi #
ssh session #
couch #
claude code agent #
input #
limit #
frontend rule #
session time #
target audience #
rec #
core feature #
io app #
code agent #
home dev machine #
coding #
iteration #
coderabbit trial #
process #
drift issue #
filter #
pick #
skill #
craft #
split #
cap #
point #
claude code config #
constraint #
side project metric #
rotation #
tmux session #
dev machine + moshi #
denial #
phone sleep #
screen #
computer #
coding hour #
attention drop #
iphone #
ipad #
assumption #
mcp setup #
color palette #
rule #
path #
note #
consistency issue #
tool #
spreadsheet #
company #
phone/ipad #
perspective #
team #
phone/tablet/anywhere #
home server #
dev environment #
overhead #
driver #
desk codex #
summary #
opportunity #
github #
project doc #
experiment #
experience vibe coding tool #
theory #
ps5 hdmi cable #