This actually happened to me, but fortunately I never actually used the domain. I registered tweed.dev intending to use robert.tweed.dev as a personal blog. It wasn't classed as a "premium" domain and the first year was £5 or something IIRC, which was half price compared to the normal renewal fee.
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.
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.
Ah, I only skimmed the article and missed that. The BBC RSS feed was the main example I referred back to while I was learning XSLT around 2010-ish.
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.
How is it in terms of heat & condensation build-up? Is there a certain amount of time after which it starts getting uncomfortable?
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?
I'm definitely taking my UV torch to the supermarket next time. However, most good olive oils come in dark glass bottles, so I don't think it will be possible to check those. Might be interesting to look for variation among the cheaper EV ones.
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.
I don't have a green laser, but I just tried shining a 365nm UV torch on the various bottles of oil in my kitchen.
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.
Why not just a scanner app for your phone? They work pretty well. I have a flatbed scanner that I keep stored away most of the time, until I need to scan a bunch of stuff quickly. If I need to scan the odd receipt, I use Tiny Scanner.
I always (and only) use named colours for debugging. For example border: 1px solid red; around some element that isn't rendering as expected.
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.
Yes, same here. It's not just "I'm hungry". It's more "I cannot think about anything other than food".
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.
More anecdata, but I find it depends on the type of exercise. An hour of cardio equals several hours of appetite suppression. An hour of heavy weight training equals several hours of unstoppable hunger. What I eat in that state (high carb, low carb, whey protein, etc) doesn't seem to affect satiety much.
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.
The Toshiba HX-10 MSX came with 2 plugs and a screwdriver. This was considered important enough to include a picture on the box, never mind the manual.
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.