In that case I stand corrected on the whole orbit bit. Thanks for taking the time.
In that case I stand corrected on the whole orbit bit. Thanks for taking the time.
I didn’t say “a little” money. It may be important or critical for the business but from a technical perspective, demonstrating how it can safely bring loads up and down decides whether the whole concept is actually feasible. That’s when people will start to get excited.
As far as I understood it, SpaceX uses the word “orbit” liberally. If it reaches the hight where an orbit would be possible, that’s “being in orbit” for them. In an actual orbit, the rocket would not fall back down again in an hour or so without active breaking. If my understanding is incorrect, I’m happy to be corrected. And even of that was achieved soon, it’s still all without demonstrating that the starship could actually carry a load and return it safely. Not even an inexpensive dummy load. All SpaceX is showing in their live feeds are empty cargo holds that fill up with hot gases and fumes during reentry.
I think the average person gets it right. It’s a nice feat to catch the booster and it will save money. But that’s a side quest. The main quest of getting an actual load to orbit and beyond is still pretty far away. At least compared with the official time line where they wanted to achieve much more than that three years ago.
Postgres handles NoSQL better than many dedicated NoSQL database management systems. I kept telling another team to at least evaluate it for that purpose - but they knew better and now they are stuck with managing the MongoDB stack because they are the only ones that use it. Postgres is able to do everything they use out of the box. It just doesn’t sound as fancy and hip.
Also, Kanban was invented in the 40s as a process for automotive production lines. That’s why it aligns so well with maintenance and operations projects in IT. It’s ridiculous how more and more people claim it comes from software development and would not fit hardware projects, when that’s the core use case of the methodology.
I specifically picked the statistic that claimed to have included the full cost of installing something new. Most other statistics only include prolonging the life of existing plants, thus ignoring the installation costs completely. You can just quote the paragraphs that prove your point the same way I have and then we can discuss further. Maybe I made a mistake, who knows.
Extremely cheap per kilowatt? Every statistic out there that I’ve seen and that includes government funding, as well as construction and deconstruction costs, paints a different picture. Nuclear is only competitive with coal or the relatively underdeveloped solar thermal.
In 2017 the US EIA published figures for the average levelized costs per unit of output (LCOE) for generating technologies to be brought online in 2022, as modelled for its Annual Energy Outlook. These show: advanced nuclear, 9.9 ¢/kWh; natural gas, 5.7-10.9 ¢/kWh (depending on technology); and coal with 90% carbon sequestration, 12.3 ¢/kWh (rising to 14 ¢/kWh at 30%). Among the non-dispatchable technologies, LCOE estimates vary widely: wind onshore, 5.2 ¢/kWh; solar PV, 6.7 ¢/kWh; offshore wind, 14.6 ¢/kWh; and solar thermal, 18.4 ¢/kWh.
Emphasis mine, source: https://world-nuclear.org/information-library/economic-aspects/economics-of-nuclear-power
Modern browsers happily show you the actual characters, while sending their encoded entities to the server. So, from a user perspective there is no ASCII limitation. Case in point: söhne.at (just some random website, I have no idea what they are or if they are legitimate)
Sure, there were electric cars. But if I remember correctly, Tesla was the first to deliver the whole next-gen package with an every day, everywhere car, plus charging stations plus the whole automation. If you wanted that, there was no way around Tesla for quite a while.
Teslas were the “best”, as in the only option for what they did. They were never the “best”, as in better than existing products for what they did.
Being first to market for such a long time was an incredible feat and it speaks volumes that their position isn’t much, much stronger at the end of it.
The original author of git flow begs to differ. But hindsight is always 20/20 https://nvie.com/posts/a-successful-git-branching-model/
If you use feature flags, don’t forget to remove them after some grace period. Almost everything bad about feature flags that you can read online is related to long-lived feature flags and all the dead code and complexity involved. Adding a feature flags without a commitment and plan to remove them (the flag, not the feature), is asking for trouble down the line.
Coffee seems to be a self enforcing meme at this point. It’s not unhealthy enough to have suffered the same fate as cigarettes. Which had pretty much the same jokes not too long ago.
Paperless -> Paperless-ng -> Paperless-ngx
There are different versions of Outlook depending on your subscription. Companies that do things properly, never see the problematic, “free version” of Outlook. They have very fine control over the features and data collections they enable.
Exactly this. This procedure is so common that you need to take care in situations where you don’t want the headers, as some tools set them per default.
My laptop was somewhat high end around 11 years ago and is still working solidly. I love the Thinkpad series btw. The only thing I had to do was upgrade to SSD and larger memory many years ago. I was an early adopter of windows 11 and after forcing the installation, it ran even better than windows 10 on the same hardware. The lock out felt extremely artificial and arbitrary.
FAQs are just a format of writing. They are usually what developers/managers want to communicate and not necessarily what happens in support.
No, I said they hadn’t demonstrated it. But 95% is close enough, I stand corrected.