Exploring Hong Kong and stumbled across street view taken from the air. Is this done elsewhere? Seems quite novel but this area is actually completely walkable.
Clojure brought back my joy of programming after years in the Java framework driven world and the JS churn driven world.
It feels like gardening where slowly your art takes shape, and every single line of code does has a visible impact (no magic) that you can immediately see via the repl
That said, clojure done with AI feels like any other language done by AI. They are interchangeable and thus the language has become irrelevant.
Attaching ticket numbers has always been enforced by automated checks wherever I have worked, so it is not necessary to “try” to enforce it.
Similarly with AI it is fairly simple to have eg a pre-merge check that validates the commit msg is somewhat useful. This could be implemented for example with GitHub org level checks that must run in a PR.
Old school but all the machines for paying in cash in Japan are so optimized for speed. Train stations, onboard buses, convenience stores. Just throw in a handful of coins and it quickly picks what it needs and returns what it doesn’t.
In other countries (eg australia), the ticket machines could only take a single coin at a time and would reject if you did it too fast.
I believe this is one (of several) reasons why cash has continued to be dominant in Japan.
After boiling them, drain the water, shake the pot so the shells crack a bit, soak in cold water for 10 min. The shells will come off easily. Same as what is done in food business.
I like the ideas proposed in “Turn the ship around” - create a bottom up culture and a culture of over communication so as a manager you can just sign off instead of delegate.
A few people mentioning pressure cookers as an alternative. A heavy claypot is the ideal manual alternative for those with a gas stove.
Probably the most popular is “kamadosan”. It makes beautiful rice and you have control over it so eg it is easy to create a crust on the bottom if you like.
Unfortunately I have an induction stove now so a bit hard to use, but I occasionally cook rice on a small charcoal stove when enjoying the slow life.
Re your kustomizen complaint, just create a complete env-specific ingress for each env instead of patching.
- it is not really any more lines
- doesn’t break if dev upgrades to a different version of the resource (has happened before)
- allows you to experiment with dev with other setups (eg additional ingresses, different paths etc) instead of changing a base config which will impact other envs
TLDR patch things that are more or less the same in each env; create complete resources for things that change more.
There is a bit of duplication but it is a lot more simple (see ‘simple made easy’ - rich hockey) than tracing through patches/templates.