cdruc

@dhh some mfs simply have more horsepower

Hilarious how we used to earnestly discuss whether the 10x programmer was real.

@func25 The only way I see around this is either a higher types package, or somewhat duplicating the types. post has an posts.Author type, not user.User media has a media.Owner, not user.User user has []user.Post isolated but kind of duplicated? :(

@func25 Thanks for the article! I read it, but there are still many scenarios... - relationships are hard. Example: posts, users, and media. // building the full representation (not just referencing IDs) posts has an author and []media users have posts and media media has user

If you are building a Go API and you are stuck on folder structure, then structure your code around features, not around technical layers. Many beginners copy a layout like project/ │── cmd/ │ └── api/ │── internal/ │ │── handlers/ │ │── services/ │ │── repository/ │ │── models/ │ │── middleware/ │ │── database/ │ └── migrations/ and put all user files in each of those folders. It looks professional. But as the app grows, one feature gets scattered across many places. A single change to "users" can require jumping through 5 folders. That makes ownership unclear and slows debugging. --- A more scalable solution is feature-first. Put related code together: - a users package can contain what users need, - a posts package can contain what posts need, and - shared code can live in a small shared package only when truly needed. Inside each feature, you can still separate files by role if necessary. This gives better locality: when you modify a feature, most of the code you need is close together. project/ │── cmd/ │ └── api/ │── internal/ │ │── users/ │ │ │── handler.go │ │ │── service.go │ │ │── repository.go │ │ │── types.go │ │ └── routes.go │ |── posts/ │ |── invoice/ --- Do not over-design too early. A lot of teams start with fewer packages than they think they need. Sometimes one package is enough for a while. Then split when pain appears, not before. Go style generally favors practical simplicity over big upfront structure plans. --- A related point is naming noise. - File names do not need to repeat the package name, - object names do not need to repeat the package name, and - method names do not need to repeat the type name. If the package/type already tells the story, shorten the inner names. It improves readability fast. --- Keep types near where they are used, instead of creating a giant global “models.go” bucket. And if two features start depending on each other, do not let them import each other directly, define smaller interfaces at the consumer side and keep dependency direction one-way. --- So the real goal is simple: when you add or change one business capability, you should mostly work in one place. - If a package has too many unrelated reasons to change, it’s mixed. - If every small change forces edits across many packages, boundaries are wrong.

these ais are making me smarter and dumber at the same time smarter = better at design because i get to iterate quickly and many more times almost for free dumber = barely write any code by hand

@jeffrey_way my workflow is… open a new chat tab when i think whatever i want do next won’t touch the same files the current clanker is touching

I'm pretty convinced that very very few developers are actually doing these super-sophisticated workflows that involve a dozen agents working concurrently in their own respective worktrees. Twitter/X would have us believe the opposite is true, weirdly.

war should be illegal

Iraqi prisoner of war comforting his 4-year-old son in Najaf, Iraq, March 31, 2003

@_sn_n she was. pick a better candidate next time.

@Mmonkoaa that kimmich incident should've followed with a two footer or an elbow in the face.

Yes this is the vinicius “they” hate on 😂😂

@wesbos @trashh_dev I had the above problem with the diffs lingering around, but more recently I had an even worse one: *not* showing *all* the diffs i swear i'm so close to becoming a vim nerd

@cdruc @trashh_dev Lol I was just going to say this has been fixed!

Does cursor have some sort of "keep things I already comitted" I keep finding these things from many days and branches ago because I forgot to click them

@wesbos @trashh_dev I take this back. this thing is broken...

@cdruc @trashh_dev are you comitting inside cursor with their UI?

@StephenKing release the tooth fairy and santa claus

Release the Epstein files. UNREDACTED.

@wesbos @trashh_dev Version: 2.4.23 (Universal) VSCode Version: 1.105.1 Commit: 379934e04d2b3290cf... Date: 2026-01-29T21:24:23.350Z Build Type: Stable Release Track: Default Electron: 39.2.7 Chromium: 142.0.7444.235 Node.js: 22.21.1 V8: 14.2.231.21-electron.0 OS: Darwin arm64 24.6.0

@wesbos @trashh_dev from the terminal

@trashh_dev @wesbos you guys must be on an older version or smth. works fine as long as you have that “auto accept on commit” toggle on 😬

@wesbos this is one of my pain points. idk how to fix

@SpencerHakimian can you guys make *this* guy president?

🚨WOW Jerome Powell MOGS Scott Bessent MIC DROP!

@realstewpeters negative percent

There’s a zero percent chance that was written by Ye.

@BillAckman yes. this totally looks like something kanye would write

A powerful apology from Ye. An important read.

“ I am not Iranian and I don’t have any ties to Iran, but I care enormously about humanity. ” oh boy, we know exactly what you are.