this post was submitted on 06 Feb 2026
72 points (100.0% liked)
chat
8566 readers
105 users here now
Chat is a text only community for casual conversation, please keep shitposting to the absolute minimum. This is intended to be a separate space from c/chapotraphouse or the daily megathread. Chat does this by being a long-form community where topics will remain from day to day unlike the megathread, and it is distinct from c/chapotraphouse in that we ask you to engage in this community in a genuine way. Please keep shitposting, bits, and irony to a minimum.
As with all communities posts need to abide by the code of conduct, additionally moderators will remove any posts or comments deemed to be inappropriate.
Thank you and happy chatting!
founded 4 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Some more details.
To be clear, I was late on my deliverables (because I had lost sleep thinking about what to do about the other stuff but that's besides the point.) However, I was being yelled at while doing another thing that was asked for, explicitly due in 2 hours. (during the meeting he asked for this, he went on a long tirade about being the strong man for yelling and "embarrassing himself") I'm not saying I wasn't in the wrong, it was just the straw that broke the camels back for me.
My advisor has given me lots of feedback. It conflicts day from day and is completely impossible to follow. (A few weeks ago he told he "Finally understands" my place in on the team, as the one who "Understands things".) He also doesn't know how to program (in the computer science department) so he has no concept of the actual quality of my code.
This is the biggest of the red flags, but the other communication issues seem serious as well.
This shit is equally enraging and terrifying by proxy. I'm sure this could be charitably interpreted many ways, but in context of this guy's vibecoding, this reeks of someone who would rather press the "theorem is obvious/intheliterature/leftasanexerciseforthereader" button than really engage with the work they're supervising. It's not required (and it would be weird) for your advisor to understand every aspect of your work that they supervise at the depth and facility you do, but they should feel like they broadly understand it and nearly every supporting concept involved unless your work is absurdly multidisciplinary to the extent that your advisor has never really studied computer science directly.
Yeah, this and bringing all of this up in a group meeting with other researchers where presumably the task was not to berate a student for being late is more what I was referring to about direct communication.
In my experience, to communicate issues meeting expectations (outside of maybe "lab manager" type duties that might affect everybody's work when whoever is on duty is late or fucks up), professionals only bring this stuff up in direct 1-1 meetings.
Even then, the criticism in a group meeting should be general and feedback for specific individuals given in private. "Guys, the hazardous materials cabinet was unlocked when I came in this morning, can the last person out double check even if they haven't used it that day?" is public feedback. "dat_math, you didn't tidy your workspace properly before leaving last night" is private feedback.
Anyone who has written a computer programme knows that you cannot predict how long it will take before you start. Doubly so if you are coming up with something new (which I assume you are). If something takes longer than expected to write, it takes longer than expected to write, and that's it. Definitely not an excuse to shout or be unprofessional about.