If you’re looking for prefab, just get a bottle of Kewpie Deep Roasted Sesame dressing and marinade: https://www.kewpieshop.com/products/deep-roasted-sesame
Doesn’t matter how you cook the chicken. Bake, BBQ, sous-vide. Just slather some of this afterward on top. It’s like goddamn crack.
Have found it in many places, from local supermarket, to Trader Joe’s, Costco, 99 Ranch, even Dollar General. Costco’s is cheaper in bulk, but they don’t always carry it. Also good on pasta or rice with veggies and ANY protein, including tofu. Baked salmon. Check.
Only caveats: don’t cook with it in oven (smokes). Add it afterward. Also, don’t overuse it.
Years ago. Client on-site meeting had run long past lunch. Was in a hurry to drive back home and beat the traffic. It was 1-hour normally, but 2-3x during rush hour.
Saw a sign for a ‘natural’ market. Pulled in. They had an open-face cooler with prepackaged foods and drinks. Sandwiches looked a bit stale. Grabbed a ‘Fresh Vietnamese Shrimp Spring Roll’ and a drink. Hopped on the freeway. Ate in the car.
Never Again.
PS: Still got stuck in traffic.
Github actions and docker containers. A match made in heck.
Software guy. Most productive/distraction free time of the day is mid-afternoon. Drinking at lunch would just take that zone away and push everything to the next day.
Happy to wait till 5pm, or whenever feels like a good time to do a git push.
RFC 2549: https://www.rfc-editor.org/rfc/rfc2549
This problem was solved years ago: https://spectrum.ieee.org/pigeonbased-feathernet-still-wingsdown-fastest-way-of-transferring-lots-of-data
At one point in my life I was working on a massive Android AOSP fork that itself had lots of variants for different downstream devices. Custom drivers, specialty services, etc. Thousands of people were actively working on all parts of it, and it had been around for at least a decade.
There was incredible tooling around onboarding, local dev, testing, PR management, CI/CD, and post-release telemetry. Almost everything was automated. All code was reviewed at least once, and sometimes more for critical components. It was an immediate rejection if there wasn’t sufficient test coverage. Big subsystems took months to architect, build, and deploy.
Nobody got to cowboy things and just push to release. It was much slower than a solo or a few people at a startup. The whole point was consistency and predictability, and you could see why.