I use it everywhere because it signals intent. You never know when someone might pull up fast or walk into your blind spot. This is the only indicator they have that you’re about to pull into traffic, or change lanes.
I use it everywhere because it signals intent. You never know when someone might pull up fast or walk into your blind spot. This is the only indicator they have that you’re about to pull into traffic, or change lanes.
Thank you for your opinion.
Anyway.
For those looking for the backstory, recommend searching for Godfrey the Hunchback, not his father Godfrey the Bearded, both being Dukes of Lower Lorraine.
And for true aficionados of privy horror, don’t forget the Erfurt latrine disaster.
I tried this with velcro ties. Looked good for a while. Then I had to replace one and add another cable. It was a royal pain unwrapping everything and rewrapping it.
Haven’t used them, but look interesting:
It cuts down on bathroom stops during long rides.
Have you looked at the free courses from AWS?
More links on the site: https://aws.amazon.com/certification/certified-cloud-practitioner/
Best practice, if going further, is to set up a console account and practice experimenting within free tier.
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.
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
I’ve always appreciated the feature of AI coding tools, where they confidently tell you they’ve done something completely wrong. Then if you call them on it, they super-confidently say: “Of course, here’s what needs to be done…”
Then proceed to do something even worse.
One-click Linux cluster. Local compute, NAS, or self-hosting. Be a shame if it all ended in landfill.
My first tech job out of college, I was told to go talk to “Dave,” the guru old-timey programmer and learn the lay of the land. He turned out to be this crotchety old guy, with low tolerance for idiots, but a soft spot for someone who actually paid attention.
A few months in, I was told to go fix a feature in the company’s main product which was sold to power utilities. This was a MASSIVE code base, with a mix of C, C++, assembler, and a bit of Fortran thrown in. I spent a week poring through all the code trying to figure things out. Then I hit a mystery workflow that didn’t make sense.
I walk over to Dave’s office and ask a specific question. Now, mind you, he had worked on this years ago, and had long moved on to new products. He leans back in his chair, stares at the ceiling, then without looking at the screen once tells me to go look at such and such file for such and such variable, and a list of functions that were related. I go back to my desk and damn if it wasn’t EXACTLY as he described.
Now, I’m probably as old as he was then. I don’t remember what I wrote an hour ago. No matter what I build, I’ll always be in awe of Dave and what he could keep in his head.
Getting less programmer_humor and more “I didn’t get the promo” angry vibe from this.
The Weekender is also anyone working professionally. You can’t stick any of your real work on public github.