erpellan

Calling a constructor is DI. ‘new’ is the only DI framework required.

Benefits:

Unbelievably fast startup time

No magic

No annotations, XML or YAML required

No classpath scanning related security vulnerabilities

Conpletely deterministic

In no other language is ‘calling a constructor’ considered so complicated a framework is required.

Try it!

Is it me, or do the protanopia (top right) and deuteranopia (bottom left) images look identical? If I’m colour-blind this would be a weird way to find out.

It’s hard to get good data - everybody seems to have something to sell.

That said, I’m enjoying this person’s YouTube channel: https://youtu.be/XCvUf9WU4qI

He at least refers to physiology and his videos avoid taking about toxins, acidity and other woo too much.

I accidentally did a nearly 60 hour fast for the first time ever last week as a result of watching that channel and doing some reading. Ate dinner on Monday, I was aiming for 36, felt fine on Wednesday morning so extended to 48 then decided to push on and skip dinner. Woke up at 3am on Thursday feeling such a genuine hunger that made me realise I’ve never been more than ‘peckish’ for most of my life. I caved and ate a small spoonful of ghee (pure fat) which lit my brain up like fireworks. Hunger immediately abated, the physical relief was incredible.

The main advice I followed was to drink more water, probably about double my usual consumption and take electrolyte salts.

https://reddit.com/r/fasting is also a pretty good resource

Context also matters in the date parsing scenario. 11/12/22 could be several different dates depending on the context.

For some people memory is event-driven not interrupt-driven. They can remember all the steps in a complex task, or when with friends, all their shared history but forget to take out the trash, or birthdays, or to call their friends.

“We collected data all summer long, from all over California. Nobody pressed the defrost button! Guess we can get rid of that”

Touchscreens for any functions related to operating the vehicle should be regulated out of existence IMO. It’s a car not a phone.

The optimisation function should be how much you can do without needing to look away from the road.

That final, 1 word sentence is one of the major problems of PRs. An engineer might spend several hours really thinking through a problem, talking with colleagues, whiteboarding options and coming up with a workable solution that addresses all the obvious issues and a bunch of non-obvious ones.

Only for a drive-by take-down by someone with none of the context. It's a totally asymmetric investment of time. Even helpful review comments might only take a minute to write but a day to incorporate.

Interesting! How does this compare to Serf / SWIM?

https://www.serf.io/docs/internals/gossip.html

https://www.cs.cornell.edu/projects/Quicksilver/public_pdfs/...

Even if Google dusted off their 2005 codebase and ran it on today's web it wouldn't come close to the results quality of Google in 2005. The SEO industry has been in an arms race with the search engines for 16 years. 2005 Google would be like a goldfish in a piranha tank.

So that’s about $1B per production vehicle delivered? Not bad!

There's also Accoya acetylated wood, which is already commercialized: https://www.accoya.com

It frequently loses track of libraries, claiming large chunks of the codebase won’t compile until caches are cleared and it is restarted.

It gets stuck indexing forever, losing all code completion and navigation abilities until it’s restarted.

Git integration sometimes stops working. It will list the files to be committed but does nothing when you click commit, until it’s restarted.

Exiting presentation mode leaves the font set to a huge size (until it’s restarted).

I feel the non-JVM targets are a real distraction from what is a lovely language. I’d rather they focussed more on fixing the issues with kotlin in IntelliJ - you’d think controlling both the language and the IDE would result in a less buggy experience than the current situation.

Fuel cell and battery electric car R&D are about the same age. Both technologies were actively explored from the 1990s. For personal vehicles BEV is hands down better. The next generation of BEVs charge at double the voltage of the current crop, with charge rates of over 350kW. This brings the 20%-80% charge time down to less than 15 minutes, or about the time it takes to use the facilities and drink a coffee on a long journey. And you can refill the car every night at home on super cheap electricity rates (a major advantage of BEV), so only on actual driving-all-day-long road trips do you ever need to charge during the day.

When the first ICE cars arrived they had to buy fuel from pharmacies and general stores and probably had the exact same anxiety. Electricity is ubiquitous. Pretty soon charging points will be everywhere, with the added bonus that you start every morning with a full 250+ miles of range.

If it's made from fossil fuel, whether coal, gas or oil, we cannot afford it. Any 'solution' that includes taking carbon out of the ground is not a solution. The fossil fuel industry would love to sell us on blue hydrogen. They would get to keep doing exactly what they're doing, but now with added subsidies to pay for turning it into hydrogen.

Blue hydrogen would be a disaster.

That is the equivalent of having a 5m column on one side and being open to air on the other side.

There is no free lunch - for the membrane to experience 100m of water pressure on one side only, something else has to be reducing the pressure by the same amount on the other side.

It reads like the spokesperson specifically and precisely refuted the claim put to them exactly as it was stated. We can infer nothing - it might be that he thinks nobody should work remotely, or everyone should.

Same with indicator stalks - not all road junctions are at 90 degrees - I'd love to see a video of activating a yoke-mounted turn signal with it turned. I don't want to do trig just to find the turn signal and then have right and left switched around because the yoke is upside down.

Intel don’t have production runs of CPUs with different clock speeds. They make a batch, test them then work out the clock speed that batch is good for. Then sell them at a variety of prices. You can overclock and 90% of the time it’ll be fine. Maybe it dies after 5 years instead of 10. Or maybe after a week. In the case of Tesla maybe that move took brought forward the EOL of the battery by 2 years or maybe 2 weeks. Even our bodies don’t work that way - our brains prevent us from using our full strength except in extremis because if we did our muscles and tendons would be seriously damaged. Soft limits are everywhere.

Early days but it's starting to happen: https://octopus.energy/tesla-energy-plan-faq/

Both the movie and the original book are, IMO, great. The science in the book is possibly more consistent and is a 'better' story. I rewatch the movie about once every couple of years on average.

One of my issues with schema languages is that they're not actually languages. Having used kotlin's typesafe builders a few times, other mechanisms feel hamstrung by comparison.

That could be fixed with 1 additional concept. Instead of

    Customer: 1 - 1: Set(Dates)

What if it was

    Customer 1 - *: Contract: 1 - 1: Set(Dates)

Overlap achieved.

I was slightly surprised to get all the way through the article without seeing a single mention of NNTP.

We already have the technology to build net zero carbon buildings. But the building trade is both notoriously conservative and extremely effective at lobbying to protect their profits (at least in the UK).

Superinsulated, almost airtight houses with ground and air source heat pumps and solar PV should be mandatory, as should banning of all in home boilers in new builds.

That’s all easily achievable even without some of the recent novel inventions such as engineered wood: https://www.nature.com/articles/nature25476

We have to stop treating the atmosphere as a free line of credit with no limit that we can just dump all our externalities into, or we’ll find out very soon that there is no such thing as an externality at planetary scale. We’re all in the same hermetically sealed box, breathing each other’s farts.

Sorry for the rant. It’s hard to stop once the despair creeps in.

The article is about forecasting not estimation. That's the point. Don't estimate. Measure.

It usually goes without saying that most forecasts do not include provisions for black swan events. It's generally assumed that going bankrupt or other project externalities will have an impact on the delivery.

It's called semantic satiation and it's awesome and weird.

https://en.wikipedia.org/wiki/Semantic_satiation

That page also links to one of my favourite phrases: Buffalo buffalo Buffalo buffalo buffalo buffalo Buffalo buffalo!

If they've hijacked a subdomain, they can submit it to LetsEncrypt and get a cert. LetsEncrypt checks that you control a domain by asking you to serve some data from it. The domain is already hijacked so from LetsEncrypt's perspective it's yours.

I've worked with several ex-GS people, all of whom were convinced they were the smartest person in the room, none of whom were even close. Some of the 'GS do it this way' ideas were so terrible we wondered if part of Goldman's strategy was to seed their competition with them as part of a sabotage effort.