As another old-timer, I honestly think this is not very good advice.
I mean "communicate" is always good advice, but reading between the lines, the situation as described is a setup for failure. I doubt it's intentional, but no one there knows how to develop software, apparently, other than to blame the junior for a timeline slip. There's only so much "managing upward" this kid can do.
My practical advice is:
Do tell the immediate boss what was said in the meeting.
Keep a good, positive, helpful attitude.
Understand there is no future for you at this place, because it is poorly managed. This is a place that will blame a junior for a timeline slip.
Do not blame yourself for the failures of the people whose job it is to support you. They are asleep at the wheel. This will be hard, because at this stage you don't even know in what way they are failing you, and likely will never learn that while there.
Do your best, anyway. But don't kill yourself over this.
I mean "communicate" is always good advice, but reading between the lines, the situation as described is a setup for failure. I doubt it's intentional, but no one there knows how to develop software, apparently, other than to blame the junior for a timeline slip. There's only so much "managing upward" this kid can do.
My practical advice is:
Do tell the immediate boss what was said in the meeting.
Keep a good, positive, helpful attitude.
Understand there is no future for you at this place, because it is poorly managed. This is a place that will blame a junior for a timeline slip.
Do not blame yourself for the failures of the people whose job it is to support you. They are asleep at the wheel. This will be hard, because at this stage you don't even know in what way they are failing you, and likely will never learn that while there.
Do your best, anyway. But don't kill yourself over this.