And "$HOM" and other things like that end up resolving to blank, so "cd $HOM" just gets resolved to "cd", which, as I said, puts you in ~/
2,933 karma · joined March 29, 2008
And "$HOM" and other things like that end up resolving to blank, so "cd $HOM" just gets resolved to "cd", which, as I said, puts you in ~/
One of the reasons that "don't do X" type of instructions work reliably is because you are telling the model "don't think of a pink elephant". There's also Anthropic's related research that shows that when you tell a model "don't do X", and it does X later for whatever reason, it starts acting more misaligned. This is because it thinks "well, I guess I am the sort of model that disobeys instructions, whatever" - this was specifically about cheating on tests, but you can imagine this happens in other contexts as well like following instructions on what kinds of text to output.
So, what you want to do is to avoid telling Claude "don't do X", and tell Claude "in your thoughts, in memories and various notes that you write, use your Claude-ese. In your output to humans, translate everything into long full sentences."
If anyone's interested, I can share my Claude Code output style that reflects this.
(Hi Adnan! Long time! (Adnan is an ex-coworker))
1. does that objection make sense? 2. How does jank approach that hurdle.
And it's essential that you check in regularly, rather than just give them a dashboard and say "ok, you go look here and tell me if anything is amiss", because they will never look.
Then tell your manager to read "The Phoenix Project". Or just extract the relevant lessons directly from there and send them to him.
"Sign here that you are resigning"
"No thanks, you'll have to fire me if that's what you are trying to do"
If you can't develop a counter-argument to that, there's no reason to believe another AI winter is coming.
I’ve been in your situation, and IMHO there’s no amount of time that will fix it. He’s reached his ceiling.
Do the hard thing. Or transfer him to a yet another team.
We are Academia.edu. Our mission is to accelerate and democratize the world's research because scientific discovery is based on it, and scientific discovery benefits everyone.
With over 180M free registered users and nearly half of the world’s academics using our platform every month, we are in a unique position to disrupt the $25B academic publishing industry. Our users range from researchers, academics, industry professionals and college students, with over 300,000 paying premium subscribers, contributing to a doubling in revenue over the last four years.
Our Stack:
- Ruby on Rails, Sidekiq
- PostgreSQL, Redis, Elasticsearch
- React + Typescript
- RSpec, Chromatic, Jest, Storybook
- CircleCI, Jenkins, Ansible, Terraform
- AWS ecosystem (EC2, S3, RDS, Redshift, many others)
- You don’t need to know any or all of these, but must be willing to learn!
What you’ll work on
You'll be designing and building systems to make our user base more productive on our platform. Here are some things that we are currently working on:
- A fast and scalable peer review system that identifies and distributes high-quality academic works
- Services that help academic authors understand the impact of their scholarship via text parsing and computation of bibliometrics
- Algorithmic approaches to identification of academic content and disambiguation of authorships in order to make every paper ever written available for free
- A paper recommendation engine that helps users discover the most relevant research
- Search Engine Optimizations to improve the discoverability of our corpus of 50M+ PDFs
Compensation: Base Salary + Equity. Base range: $160,000 - $240,000
Apply at https://jobs.lever.co/academia/ee3c7f6d-ec42-46ca-ad65-53846... and also email me at yuri@academia.edu (I'm the VPE) to tell me you applied so I can fast track you.