I wouldn't look forward to having to do that every time I changed prices!
I wonder how many small independent stations are there these days? Almost every one I see is either in a supermarket, a big chain like Esso, or a smaller chain like Harvest.
It doesn't mention any filters beyond batch number and effective start date. They're definitely storing the lat-lon information though, so it would be nice to do area-based queries, especially if you're building an app with a map view.
I'm not sure there's much real scientific research on preparation (at least when this was published in the 90s), especially as it can be quite subjective. There's a bit about factors affecting caffeine content on p.425:
> The quantity of caffeine that infuses into a tea brew is determined by infusion time and by leaf style. Longer infusion times lead to greater quantities of caffeine in a tea beverage. Smaller sized tea leaves give a more rapid and stronger infusion, whereas larger leaves and uncut leaves lead to weaker infusions. This results in more or less caffeine extraction, respectively. The caffeine content of a typical tea beverage will range from 20 to 70 mg per 170 ml of infusion, with a typical infusion being prepared from about 2 to 2.5 g of tea leaves. Coffee brews typically contain from 40 to 155 mg caffeine per 170 ml beverage. There has been little research done on the pharmacology of tea-beverage caffeine. One study suggests a dose of caffeine from tea has a different physiological effect than a pure dose of caffeine (Das et al., 1965). This has been attributed to the amino acid theanine, which is unique to tea. However, there are no well-designed clinical studies to support this position. The consensus among scientists today is that caffeine from all beverage sources has a similar physiological effect. The actual content of caffeine depends on many factors, particularly the method of brewing. A brew prepared by the Chinese "gong-fu" style is likely to have a different caffeine impact compared with the Western style of loose tea or to that from a tea bag (Hicks et al., 1996). Some reports have suggested that green tea contains significantly less caffeine than black tea. This may be influenced by the clone of leaf used to produce the tea or by the impact of different brewing techniques. No significant differences have been found when brewing green and black teas under similar conditions (Hicks et al., 1996), discrediting the theory that withering and fermentation have a significant impact on caffeine content (Sanderson, 1972).
Heathrow is by far the largest airport in the UK, with several times more flights per day than any other, and flights to a broader range of destinations. So it affects a lot more prospective fliers. I looked up European airports and found some mention that Rome and Milan also have this new equipment, but they're both still significantly smaller than Heathrow.
Yes but Heathrow has around twice as many departures per day (edit after your edit:) than Gatwick.
This is on BBC news. Heathrow is twice as busy as any other airport in the UK. It's the easiest major airport to reach from London (other than LCY which is not that "major"). I literally know people who are leaving from Heathrow this week and are affected by this. C'mon, it's newsworthy.
Oh okay, you're asking why is it on HN front page rather than more generally why is it newsworthy. That's a fair point. I suppose it's a big feat of logistics and engineering to manage a switchover at such a large airport with so many terminals
It also fits in a handful of bytes or kilobytes what would take half a gigabyte to communicate in a video - sometimes making the difference if you have limited bandwidth or a cap on monthly traffic.
It's also ridiculously easy to cache (download a book in 9 seconds, board a transoceanic flight - no problem)
It also doesn't require the right sound and lighting conditions to see and understand a video (either those conditions, or good noise cancelling headphones - and now you're unaware of your surroundings)
It's also the only viable option on insanely low power devices which get months of battery life per charge.
It's also something you can read at an incredibly speedy pace if you are good at it and practice - though occasionally a decent audio/video player will be of use with this.
It's also something you can fall asleep while consuming, and tomorrow you won't have much trouble finding exactly where you left off.
It's also the only medium where semantic reasoning and indexing at scale makes financial sense. I can run RAG over millions of text rows in Postgres for pennies, but the compute costs to process and embed video content are still prohibitive if you care about margins.
Amen. It's one real "downside" in this day and age is that it requires fairly undivided attention to be used... that aside, it's without question my favorite way to interact with information.
On that note, a big thank you to whoever added "read this page" to Safari on iOS! Being able to turn long form articles into ad-hoc podcasts has been a game changer for me.
> Text is searchable, skippable, scrollable, compact, transmissible, and accessible in a way that audio and video have never managed to be.
That's just a very long way of saying it's difficult to monetise; it's why audio and video are preferred by producers of content.
Few people are interested in disseminating an idea, a concept, anything... they are interested in levelling up their fame and followers. Text is typically no good for that.
Video keeps blowing up because people want to connect with humans, and life is making that harder than it needs to be, so people are settling for these weird parasocial echo chambers. With the rise of AI, all text is suspect, and authenticity is king.
True, but it's a lot harder to sneak those things than text. I've seen convincing Yanis Varifakis and Neil DeGrasse Tyson fakes, but even those don't survive any scrutiny. I'm sure that will change, and people will find new ways to signal authenticity in videos (leaving in fuckups is already in style).
Video to a lot of people is way more engaging than text. Also video is much more information dense. You can’t teach people to do things over purely text but show them a video and a 1000 different indescribables become instantly apparent.
That being said I love a good book over its movie version anyway. Because text is cheap there is so much more detail you can include. There is no way text can compete with the information density of a video.
Same thing if you swap "text" and "video". That's the point of different media - they differ along those dimensions. For example, "a picture is worth a thousand words" means that for some information it will be less compact to describe all the details of a video with words
Obviously there are some pieces of information that can be conveyed better with a picture or diagram - network connections, block graphs, etc. But as a general rule text is far more efficient for knowledge transfer.
If I have a text file and an audio file of the Great Gatsby, and I want do any of the following, then I'm going to use the text file:
* Find a particular quote
* Determine the number of times the word "Gatsby" is used
* Go back a few pages to remember exactly how something/someone was described
* Intermittently stop and compare with a supplementary file and/or write notes
* Find exactly where I was just before I fell asleep
* Get through it in 3 hours without rushing or missing bits
* Store it on a portable device along with thousands of other books
There is no such general rule, and humanity has always used various media, and for every biased test you come up with (frequency of a word in a text) you can just as well come up with a test that benefits the other medium (frequency of some sound in the audio book)
* Go back a few pages to remember exactly how something/someone was described
Or you don't forget how someone looks because a visual illustration is easier to remember
* Find exactly where I was just before I fell asleep
You can't, the book closed when you fell asleep and you forgot the bookmark . But when the phone fell it disconnected your headphones which stopped the playback.
While this is our course a good point, one extremely good part about text is that unless there given text is quite literally just plain text data, it's a lot easier to embed things like videos, pictures, audio, etc. into a textual medium especially when compared the other way around -- that is the fact that text in videos and pictures and so on tends to be quite limited when compared with the kind of "rich text" with the more audiovisual content added between blocks of text.
So one can use the thousand words of pictures while most content is textual, whereas the other way is significantly worse, since it of course lacks all the searchability et al.
You're discussing a mixed content document format, the original point was about some mythical benefits of text, explicitly vs video, which removes all the embeds from your document
ACII is a standard, but it's also standard. To a really high degree. 99% of webpages are UTF-8.
You could make a similar argument about, say, H.264, but the dominance is not as compelling and drops massively if you account for different container formats.
What if the project involves trying one approach for a week, then assessing whether that approach still looks viable vs moving onto a different approach? This happens a lot with challenging projects, you basically just keep trying different things until one works.
Then you know that it's going to take at least, say two weeks, one week for the first implementation and a week to finish it if it works.
On the high end, could it take more than 2 years? 1 year? 6 months? Stop when you are 80% confident that it won't take longer than some period.
So your estimate might be between two weeks and six months. Is that an acceptable estimate for the "buyer"? If not, is it worth expending effort to narrow the estimate?
Yes, this is basically what happens. Except sometimes there's no realistic way to narrow the estimate. In research-focused teams you don't "scrap" a project that you can't break down. Instead you need to have a way to manage wide estimate windows.
Because, for whatever psychological reason, estimating in time leads to a false sense of accuracy, people pointlessly argue over whether something will take 5 days vs. 6, and people tend not to be overly optimistic and forget to account for things like sickness, meetings, etc.
Estimating in points that are basically a Fibonacci sequence keep estimation precision limited and avoids implying false guarantees. Yes, in the end the chosen stories are based on summing to a number of points that is roughly equivalent to what the team has achieved per-sprint in the recent past, so in that sense it is ultimately estimating days in the end. But again, for whatever psychological reason, people seem to be more realistic about the variance in actual delivered points per sprint, as opposed to when you try to measure things in hours or days. The points imply more of an estimated goal than a deadline guarantee, which helps keep both team expectations and management expectations more reasonable.
Can't you do that by just limiting the precision? You can only vote 1, 2, 3, 5 or 8 days. Not sure what "points" are adding. As far as I can tell, it's an attempt to account for estimation difficulties by introducing a "velocity" concept. But I think it makes things more complex without actually solving the issue.
> and people tend not to be overly optimistic and forget to account for things like sickness, meetings, etc.
> But again, for whatever psychological reason, people seem to be more realistic about the variance in actual delivered points per sprint, as opposed to when you try to measure things in hours or days. The points imply more of an estimated goal than a deadline guarantee, which helps keep both team expectations and management expectations more reasonable.
> and people tend not to be overly optimistic and forget to account for things like sickness, meetings, etc.
> people seem to be more realistic about the variance in actual delivered points per sprint, as opposed to when you try to measure things in hours or days
Okay I think I'm with you. In my team, the PM pre-calculates the number of available days in the sprint per developer before taking any estimates, factoring in planned holidays and estimates of sickness and meeting time, and adjusting for seniority. I guess points are kind of a crude way of doing the same thing.
> I guess points are kind of a crude way of doing the same thing.
Right. But you sound awfully judgmental in saying "crude". I'd call it robust, and not trying to produce some kind of false over-precision. In other words, appropriate to the task at hand.
So how does your team adjust capacity planning in case of disruptions like annual leave, company all-hands days, public holidays etc... ? How do you figure out how many points to reduce by?
I have a two year old and often worry that I'll teach him some intuitive arithmetic technique, then school will later force a different method and mark him down despite getting the right answer. What if it ends up making him hate school, maths, or both?
I experienced this. Only made me hate school, but maybe because I had game programming at home to appreciate math with
Just expose them to everyday math so they aren't one of those people who think math has no practical uses. My father isn't great with math, but would raise questions like how wide a river was (solvable from one side with trig, using 30 degree angles for easy math). Napkin math makes things much more fun than strict classroom math with one right answer
Commonly school is teaching a method. "Getting the right answer" is just a byproduct of applying the method. If you tell your kid that they should just learn the methods you teach and be dismissive or angry about school trying to teach them other techniques, that's probably going to cause some issues downstream.
Techniques of an "intuitive" character often lack or have formal underpinnings that are hard to understand, which means they do not to the same extent implicitly teach analytical methods that might later be a requirement for formal deduction.
I hope that I wouldn't be dismissive or angry. My worry is that my son will feel dejected because he (correctly) thinks he understands something but is told he's wrong. I also worry about him getting external validation from following a method, and will value that over genuine understanding and flexible thinking. But I see your point that it's my responsibility to help him work through that and engage with the syllabus.
I wouldn't look forward to having to do that every time I changed prices!
I wonder how many small independent stations are there these days? Almost every one I see is either in a supermarket, a big chain like Esso, or a smaller chain like Harvest.
reply