@sumanthraman Pay should be based on the role’s market value and the candidate’s skills, not their current CTC. That’s why places like California made it illegal for employers to ask about salary history it perpetuates underpayment and unfairness.
@addyosmani Excellent article @addyosmani I’m doing a lot of this in my day-to-day work. One thing that’s helped a lot is asking Claude to generate a clean Feynman-style HTML walkthrough after a task explaining what changed and how to understand it.
If you're stuck in the Bay Area tech rat race / psychosis, make time to travel to other places.
Go to a small town in Europe or visit Asia - you'll see that life can be about much more than whether you're IC7 or IC8 or what company you work for.
Don't be the person to put on your tombstone: "He got divorced and neglected his kids but at least he made D2 at FAANG"
@trq212 Love the take @trq212 With AI generating PRs at an incredible pace, I’ve started relying on HTML-based visualizations to better understand changes. For complex PRs, I’d love walkthroughs that explain them step by step using Feynman-style techniques.
@RippletideCo@unclebobmartin Yeah, the critics I have get invoked as hooks before PRs, but I like what @unclebobmartin shared with established tools in the loop for reviews. I'm working on getting them into my hooks.
@unclebobmartin Thanks for the response! Agreed.
What prompting strategies or architectural guardrails are most effective for ensuring an AI agent adheres to Clean Code principles? Something I’ve been following recently is a code review critic with custom instructions that simplifies my code.