7znwjshsus

You can only do so much if your ingredients and oven is bad. I don't think you can judge the cook in those cases, only the restaurant as a whole.

I think it works quite well when they focus on architechture, mentoring, product planning, estimation, cross team communication, code review, devops and small feature/config requests. On slow days they can fix those nasty bugs that have been in the backlog for a while, or on tight deadlines they can help in the parts lagging behind in the important project. But yes I can see how this could be considered "bad" IC, but all that gruntwork is work that doesn't need to distract and slow down your team now.

It's amazing to work with a good team lead like that since you can focus 90% of your working time on getting top priority things done.

What I've seen from the opposite approach is that ICs have a lot of pressure to estimate, plan, document, communicate etc because the managers are too detached from the day to day work. Almost no actual work is getting done because of all the interruptions and endless technical bikeshedding because nobody has either the authority or understanding to call the shots. The ICs compensate for this by working overtime for free.

Those who don't know how to do that probably don't care anyway.

My main issue with this workflow is that if I alt tab to terminal, then it brings all of the terminals to front, rather than the one I wanted. Now one inactive terminal may be blocking the previous app that I want to use as reference for my active terminal. The only workaround is to resize and drag all the terminals around which I usually don't want to do. So I have to make the previous app fullscreen to move it to a separate window and then suffer from the slow window animation. It's just the worst UI ever designed. Never had any such issues with default ubuntu or windows. Things actually feel like a real desk(top) on those.

I think you misundestand the purpose of your contract. Your contract is for you to produce value, not just to have your butt on a seat for 8 hours. The problem is that you cannot measure impact in a concrete enough way for a contract. So time is used as a proxy. If you cant deliver your impact in that time, you will get fired regardless. Just fullfilling the contract is NOT enough for the employer, so why take it literally yourself?

That's not the risk. The risk is that Github has lackluster permissions and audit trailing and an employee could leak and sell keys. Or that they log keys and someone hacks their logs.

Rotating the secret is 100% the correct thing to do in this case.

I love how simple your cargo toml is. A big turnoff of leptos for me was the incredibly messy cargo toml of the examples. I could barely touch it without bricking the project.