The next year they decided it was premium after all, and wanted to charge £492,000 for renewal. I still have a screenshot of that, although needless to say I don't own the domain anymore.

https://www.youtube.com/watch?v=zsGaVrMr9N8&t=480s

The reason I remember this is that it inspired me to spend ages implementing Gouraud shading in my own graphics library (written in assembly language), only to discover that flat polygons look better most of the time.

[1] https://en.wikipedia.org/wiki/Gouraud_shading

AFAIK it's the only major implementation of this technique. Most other big sites that provided an RSS feed didn't bother, and most of those RSS feeds are dead now. The BBC one has hardly changed since those days and it still works really well as a dual-delivery system.

http://feeds.bbci.co.uk/news/rss.xml

Also, is passthrough good enough for things like typing, so you don't get an uncanny valley sense of the keys being just slightly off visually compared to your proprioception & touch?

The article mentions differences between brands, but IDK if there's a specific correlation with quality other than that fake olive oils certainly won't turn red/pink.

My good EV olive oil in a glass bottle goes a sort of pinkish colour. With the natural colour of the oil & the way the glass reflects/refracts light, it makes it look like copper.

I don't get the same effect with cheapo refined olive oil in a plastic bottle. I get a bit of fluorescence - the normal violet colour and much less than say a white piece of paper - but all or most of that is just from the container.

This makes it hard to accidentally forget about a rules that just just put in temporarily. Real colours will always match some design, which will have a carefully-chosen hexcode.

In the game there is a computer, which if you interact with it, allows you to play the entire original Maniac Mansion.

It might get a bit annoying when you want to go to sleep though.

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

I'm not sure it has anything to do with burning fat stores though, because I don't get the same feeling after say, a 3-day water fast. At that point I'm definitely hungry, but don't have the same insatiable food craving.

In fact, when I was experimenting with extended fasting, the only reason I stopped at 3 days is because I was lifting lighter weights every day and hit a point where my strength was physically depleted. I could only do about 3 reps instead of finding 15+ easy. Hunger wasn't really a problem after the first day of getting used to it.

I believe this could be the main reason why its almost impossible to eat at a caloric defecit (with surplus protein) and train anabolically at the same time. Some people are able to do that, it's just very rare.

Code that never needs to be touched is fine. Although the odds are that such code is either completely trivial or subtly wrong (or both).

Code that is touched every day is likely to be fine as well. It's should get smoothed out naturally, like a pebble in a stream. If not, you probably already have lots of alarm bells telling you it's a problem without the need for any further analysis. It's not the code quality that matters here so much as the test coverage.

The changes you really need to worry about are to code nobody has touched for 3 years and whoever wrote it no longer works for the company. Especially if that code was written with the mindset of "nobody will ever care about this code".

A better metric for deciding where you should focus the most effort on code quality is not frequency of modification, it is frequency of appearance in the runtime call-graph. Each call probably also need a multiplier for how deep in the call-stack it was, since that's where unintended consequences of a small change are likely to have the biggest blast radius.

https://www.msx.org/wiki/Toshiba_HX-10