7znwjshsus

4 ms·

1.
by 7znwjshsus 3y ago
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.
2.
by 7znwjshsus 3y ago
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 hav
3.
by 7znwjshsus 3y ago
Those who don't know how to do that probably don't care anyway.
4.
by 7znwjshsus 3y ago
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
5.
by 7znwjshsus 3y ago
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 ti
6.
by 7znwjshsus 3y ago
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 d
7.
by 7znwjshsus 3y ago
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.