4 ms·
I agree. I'm the AI luddite on my team of red team security engineers, but I'm still using it in very limited use cases. As much as I disagree with how the guar
by wedemmoez 6mo ago
I agree. I'm the AI luddite on my team of red team security engineers, but I'm still using it in very limited use cases. As much as I disagree with how the guardrails around AI are being handled, I still need to use it to stay relevant in my field and not get canned.
- hootz 6mo agoI'm already adding "Agentic Workflows" as a skill in my LinkedIn profile. Cringed hard at that, but oh well...
- pydry 6mo agoWhat if the hiring managers at the jobs you'd actually prefer to work at also cringe when they see it on your profile?
- hootz 6mo agoThat's actually a really good point.
- hn_throwaway_99 6mo agoIt's becoming so ubiquitous, I highly doubt it. At worst I think a manager would just see it as fluff, but not a negative.
- bluefirebrand 6mo agoI hope the hiring managers I would actually want to work for would see it as a red flag on resumes
- MarcelOlsz 6mo agoWhy? It's just the name of the game, everyone gets it. Especially if you're a generalist/frontend type.
- bluefirebrand 6mo agoIt's simply not a game I'm interested in playing. I'll find something else to do instead, leave the AI jockeying to others.
- pesus 6mo agoAt this point, I'd assume those hiring managers are also being forced to use AI in their jobs (or pretend, at least) and probably wouldn't read too much into it if it's not a substantial portion of their resume. I do feel the same way, though.
- pydry 6mo agoI asked coz know several managers who would look upon it as a red flag and I suspect OP would probably prefer to work for them rather than AI sheep.
- miltonlost 6mo agoI'm using claude but then refuse to do much cleaning up of what it spews. Im leaving that for the PR reviewers who love AI and going through slop. If they want slop, I'll give them the slop they want.
- whstl 6mo agoNot advocating that people should follow this but: As someone that loves cleaning up code, I'm actually asking the vibe coders in the team (designer, PM and SEO guy) to just give me small PRs and then I clean up instead of reviewing. I know they will just put the text back in code anyway, so it's less work for me to refactor it. With a caveat: if they give me >1000 lines or too many features in the same PR, I ask them to reduce the scope, sometimes to start from scratch. And I also started doing this with another engineer: no review cycle, we just clean up each other's code and merge. I'm honestly surprised at how much I prefer this to the traditional structure of code reviews. Additionally, I don't have to follow Jira tickets with lengthy SEO specs or "please change this according to Figma". They just the changes themselves and we go on with our lives.
- grvdrm 6mo agoFavorited. I was talking to someone (non-dev) yesterday who prototypes with Claude and then goes back/forth with the lead engineer to clean it up and make it production worthy (or at least more robust). I like that model.
- kelzier 6mo agoI thought the de facto policy was that the individual remains responsible in a team context.