They uploaded to GitHub but won't give me access — are they right?

I have an objection here. If you don't write this down from the start, it leads to arguments later.

Processes without records never improve, because you don't know what to fix.

My perspective changed after experiencing that. Just because everyone does it doesn't mean it's right.

Hasty decisions become decisions you have to fix six months later.

Let me share my experience. The answer varies greatly by industry; there is no one-size-fits-all rule.

Of course, it varies if your situation is different.

I'm in the same situation, that's why I'm asking. Code without setup documentation isn't yours, even if you have it.

That's all, sorry if I went on too long.

Yes, that's exactly how it is with source code repository access. If you don't write this down from the start, it leads to arguments later.

Taking notes for two weeks yields better results than a six-month estimate. If you post the result here, it will help others too.

Could you elaborate on that? If you get three different answers on a topic the question was asked wrong.

The cheap-looking path usually ends up costing more later. Don't hesitate to ask; those who don't ask always pay more.

This is my opinion, I'm not claiming it's absolute truth.

Exactly like that. Every "we'll look at it later" in a meeting means unbilled work.

In legacy systems, the most expensive thing is unknown dependencies. If you have questions, write them; I'll answer as best I can.

we need to make a distinction here. if scope grows, either time or budget must grow. tbh there is no tihrd option.

if you have questions, write them; I'll answer as best I can.

I'm curious too.

Great work.

I'm in the same situation, that's why I'm asking. In legacy systems, the most expensive thing is unknown dependencies.

Just because everyone does it doesn't mean it's right. Correct me if I'm wrong.

I have no experience with source code repository access, so I'm asking. Don't hesitate to ask; those who don't ask always pay more.

Good luck with that.

I have no experience with source code repository access, so I'm asking. In legacy systems, the most expensive thing is unknown dependencies.

Hope this helps.

Generally correct, but one part is missing. When making a decision, first look at what data you have on hand.

If you post the result here, it will help others too.

to get into the details: If you get three different answers on a topic the question was asked wrong.

Exactly, and not many people know this. When making decisions, write down the worst-case scenario too, not just the best.

Good luck with that.

This approach has a cost which isnt discussed... honestly most time waste accumulates in tasks waiting for approval.

In legacy systems the most expensive thing is unknown dependencies. honestly proven by experience.