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.
It's frustrating for the participants, but typically for these "internship programs for disadvantaged students", future employers will not treat it as equivalent to a regular internship.
That includes the company that runs the internship. In my large tech company experience, usually the entire "internship for disadvantaged students" program led to zero job offers.
Honestly, it might be a good idea to avoid those programs entirely. You often don't get to work on "real problems" while you're there. The program exists for PR much more than to give you useful experience.
That said, I don't have experience with this specific program, so this might not fit the archetype.
That's what it says on paper but that's not reality. If you are asian you are suddenly not disadvantaged even if you are an immigrant. It is just legal racism.
The fact that employers even get to play games like this tells you a lot about our current situation ironically.
"Disadvantaged" is not something that is defined purely by race (atleast in the UK) The key factors that are considered in your university application are all pretty much pure contextual factors IE; income, poor academic performance family history of higher education etc..
If you are of Asian descent in the UK the biggest factors to determine if your going to get into a program like this is not your skin color. Its an evaluation of you and your family's history and providing ascent to people less fortunate.
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.
Boston was the last major city I saw to actually add this in the US (every other major city metro I've seen has it). Boston got it last Spring or Summer if I recall. The MBTA is a nightmare, but at least I don't have to reload my Charlie Card anymore...
The best part is it's very useful for getting rid of lots of smaller denomination coins, just dump them all in and the machine will give you the fewest number of coins back that equal the balance.
I've seen people on YouTube using the U-Scan at Walmart like a CoinStar. Apparently if you lift where the coin slot is you can dump in coins and it will process it all. If the total is more than your bill, it gives you the money back.
While I'm not sure about the refund of an overpayment, there are also the toll booths that have buckets to throw change into. Though most tolls seem to be electronic these days.
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.
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.