rglynn
Joined 2 years ago
Joined 2 years ago
Now, as far as I can tell, we are quite a way away from actually having most/all professions replaced, so for now the answer is rather clear: pick another boulder.
Their perspective is "Rails? Isn't that like, super old??"
I audibly went "ah!", as if in pain from a muscle twinge and immediately came back to the thread to find this comment.
Ain't no way I'm gonna spend my free time reading Claude-isms.
The times that I "Claude said:" are almost always a case where Claude gave the correct answer.
The real problem is if you paste "Claude said:" without reading what Claude said. Have seen this happen and goes something like:
Sr Engineer: "Claude said:"
Me: "But that doesn't make sense because of X"
Sr Engineer: (having actually engaged thinking effort: human) "Oh yeah, not sure why Claude said that, I think we should do Y instead"
Yes, in an ideal world, PRs read well, are a joy to review, reflect what you discussed etc etc. We have to be real; there is only so much we can do to that end.
I'm not sure how the best teams do PR review, from my perspective it sucks. I'm talking specifically about the UX. I've always hated Github's PR page, so I typically reviewed by pulling down the branch and opening the diff with $EDITOR.
These days I think there's really no excuse for the awful UX. Linear (a company that isn't even in the domain of code review) put out a basic PR review feature[0] that is already better than what GH offers. It's simple: point a small model at the PR, group file changes together based on theme, add some commentary and sort by importance (schema changes > openapi spec).
Immediately, so much mental load has been reduced without the reviewer or the requester doing anything. This feature is pretty damn basic, and I think there are obvious next steps like generating visualisations which a dedicated product could find the time to implement.
Keen to hear others thoughts on why this is the wrong approach, or if there are tools in wide use that solve for this, or why this isnt the right problem to focus on.
Can speak to my experience that if you are a senior engineer in London the market is relatively easy at the moment (or was at the beginning of the year) even with no connections.
I think this is often difficult for people who treat films as logical instead of experiential.
Nonetheless, it is inaccurate to characterise it as poorly mixed, since the goal was for the score to somewhat drown out the dialogue, and the mixing achieves that goal. You can disagree that this is a desirable outcome for the viewer, but art is ultimately subjective.
0 - https://www.reddit.com/r/IAmA/comments/cjtlzp/comment/evg2js...
There is perhaps some relevance to the analogy however, because the US is designed in such a way that makes walking difficult to impossible. I am already seeing this pattern in vibe-coded areas where engineers will just use AI because it's too difficult to parse and edit by hand.
We have some responsibility as candidates to tell HR departments and recruiters that some stuff doesn't fly.
Interests: Programming, Remote Work
Email: [email protected]
---