It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?
It states the OpenStreetMap data is from May. Is it fully offline and needs to wait for the next app update?
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.
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.
1Password can’t fail that hard easily. They’ve done great write-ups to compare their architecture to that of LastPass. Long story short: it’s the secret key that protects you: https://blog.1password.com/what-the-secret-key-does/
Trouble with those tests is, that they become unreliable or even meaningless, when you have done then once before, let alone daily.
When I installed Kinoite to start using Linux as my primary daily driver, the first thing I did was setting up Ansible, creating a new playbook and all Linux configurations I made from that point on, are only ever done through that playbook, which is backed up in my Forgejo instance. One command and everything is being set up exactly the way I want. It feels extremely liberating.
Windows hss supported slashes in both directions for a very long time. I almost exclusively use forward slashes to reduce mental load when switching between OSes.
Whether they are fertilized depends on the facility that produces eggs and the population of chickens at the time. Cage system housing might produce almost no fertilized eggs because the animals are isolated. That system is however outlawed in some regions of the world because of animal cruelty and the requirements of high amounts of antibiotics to counter the spread of diseases. All other systems produce at least some amount of fertilized eggs, for example because of misgendered roosters becoming part of the general population until they get spotted.
Some people have successfully hatched some supermarket eggs and that is entirely plausible. They are not being hatched by the hens until the nest is full, so they may be laying around for many days before the hen starts sitting on them - they don’t need to be kept warm immediately.
When the low rolling character convinces the high rolling one, that they are seeing things, the real fun begins.
Very well written. I’d only change something about this paragraph:
- Operated without production interruption even with frequent team member exit during critical phases of operation
Sounds like people were quitting on you because of terrible work conditions you fostered. An alternative could be:
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.
You can implement public or semi public ledgers without Blockchain. That’s what banks are doing already by sending huge CSV files internally and externally. Blockchain is not a technology of zero trust. It’s close to the opposite. You trust a few peers and blindly trust everyone they trust. That way you trust a network that you know nothing about and if the network decides on a common truth that you are convinced is incorrect, there is nothing you can do about it. The consensus always wins and there is no single entity to complain to and get it fixed. This is great for making sure that many actors need to be bad actors in order to have the whole system fail. It’s bad if you don’t trust anyone and want to make sure that your standards are always observed. From a technology standpoint I love the concept of Blockchain. But use cases that are not forced are few and far apart. Too few for the amount of hype it receives.
It depends. Some hardware degrades gracefully while my current desktop system won’t even boot and throws error codes on an empty battery. It took me hours to figure out what was wrong the first time it happened.
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.
It’s the same argument. Getting a reasonable amount of charging is possible in 15 minutes. But not everyone has immediate access to fast charging stations. If everyone could always make a deliberate decision whether to go easy on the battery and save money or having to be places, EVs may look much more appealing to a lot of people.
Cool, thanks