A bigger issue I'm seeing is ordinary corrosion at metal-plastic interfaces where the magic coatings which keep the rust at bay get worn through due to vibration and dissimilar thermal coefficients. Another such problem sometimes occur when windows are not mounted with enough of a gap between the glass and the surrounding metal, again leading to the coating being worn through due to vibration and such. Look for the former problem at wheel wells, the latter at the bottom edge of rear windows.
Balancing your portfolio to include the top 25 or so best performing companies of the index
Therefore ETFs that track that - eg $XLG is the s&p top 50. Unsurprisingly, consistently beats the s&p500. Same for $QQQ - in this case the skew is for more tech stocks (which were the best asset class in a decade)
Anybody saying “destroy the planet” is being silly, but the average temperature over the last half a billion years is entirely irrelevant to the survival of modern civilization, or even modern biodiversity.
How do you know most people are willing to make the trade? People don’t have a choice. This stuff is driven by systems vastly larger than the individual. Nobody can decide to opt out of progress so they can also opt out of climate change. Even if I could opt for a zero-emissions lifestyle, climate change would continue with no detectable difference.
Layering (properly) is used to manage dependencies. You isolate interface logic from business logic with data in between. It lets you evolve the architecture. This is a useful abstraction, not just something academic.
i disagree with this premise, where there is increased dryness in some places it means there's more moisture in others
pretending like this is a global catastrophe doesn't account for the fact that the planet's deserts move, as do the jungles and the forests as they always have
this is just the next doomsday report, i don't have any respect for this kind of ankle-deep depressed teenager mindset being disguised as a study of atmospheric events
Whats interesting to me is climate change has been shown to actually increase total annual rainfall on land[1], but I guess this means that its those areas where farming was once feasible and where people now live are becoming more arid?
I hope I don't come off sounding like a twit, but does fast charging really matter all that much to people? I've had a few fast charge cables before, and although it's fine to have my cellphone fully charged in say, 20 minutes, it doesn't really mean anything to me, given that it will be left plugged in over night regardless.
Perhaps it's more useful to people who are constantly traveling, but for someone who isn't, I guess I just don't see a point in it. Would I turn it down? No. Would I pay more for it? If it's greater than 2$ more, no. Slow charge is "good enough" in my eyes.
I think Cognitive Load on a developer includes distractions/interruptions. Constant slack notifications, taps on the shoulder, meetings, etc. increase cognitive load. It's context switching. And to context switch one only has soo much memory and focus, to switch tasks one has additional overhead, thinking and memory/storage demands.
What jj does is not require you to pause. It’s fine with leaving stuff in a conflicted state, letting you do whatever you want as a next step. That may be resolving the rebase, but maybe you didn’t realize you were gonna have a conflict and want to get something else done real quickly.
In-memory, always succeeding rebases are just really nice.
Sure, but on a global scale the rich are a small percentage of the world population.
Some countries are very restrictive on prescribing antibiotics (almost too strict) and it feels like it falls flat as you can get it over the counter in a lot of places.
How? I remember where all the code is. And I watch juniors flail without a picture of the codebase in their head, because their IDE incorrectly taught them it's not their job to know.
Given the popularity of Github, and the fact that a readme file is the first thing you see when pulling up a project on Github, most projects these days do in fact have readme files.
Having the extended family over and the boys would all be playing outside until the street lights came on, and then inside to play whatever game came out. Clay fighter, mortal kombat, donkey kong country etc.
My family would pull straws to see which man would dress up as Santa clause and go door to door on my street to greet kids and give the adults some baileys or whiskey.
Every SOLID, Clean Code, DRY and so on are all terrible advice sold by a bunch of people who haven’t worked in software development since before Python was invented. Every one of those principles are continently vague so that people like Uncle Bob can claim that you got it wrong when it doesn’t work for you. Uncle Bob is completely correct though, but maybe the reason you many others got it wrong is because the principles are continently vague. Continently because people like Uncle Bob are consultants who are happy to sell your organisation guidance. I think the biggest nail in the coffin of everything from TDD to Clean Architecture should be that they clearly haven’t worked. It’s been more than 20 years and software is more of a mess than if ever was. If all these “best practices” worked, they would have worked by now.
YAGNI is the only principle I’ve seen consistently work. There are no other mantras that work. Abstractions are almost always terrible but even a rule like “if you rewrite it twice” or whatever people come up with aren’t universal. Sometimes you want an abstraction from the beginning, sometimes you never want to abstract. The key is always to keep the cognitive load as low as possible as the author talks about. The same is true for small functions, and I’ve been guilty of this. It’s much worse to have to go through 90 “go to definition” than just read through one long function.
Yet we still teach these bad best practices to young developers under the pretence that it works and that everything else is technical debt. Hah, technical debt doesn’t really exist. If you have to go back and replace part of your Python code with C because it’s become a bottle neck that means you’ve made it. 95% of all software (and this number is angry man yelling at clouds) will never need to scale because it’ll never get more than a few thousand users at best. Even if your software blows up chances are you won’t know where the future bottle necks will be so stop trying to solve them before you run into them.
I use the default endpoint in Sweden, and I can’t access Reddit and YouTube without being logged in (which I refuse to do). Not an issue in the end because it’s mostly a waste of time.
That seems to be university PR doing its "magic." The actual study is much more interesting: the humans weren't allowed to speak to each other, and pheromones wouldn't help the ants solve the problem, so both groups were communicating through haptic feedback. Ants do this naturally and demonstrated swarm intelligence behavior by "going with the flow", but the humans kept working at cross purposes by trying to implement a complete solution without coordinating the details.
I agree with the overall conclusion, even if it's phrased misleadingly: human collective intelligence is primarily about individual intelligences accessing group knowledge rather than groups working together to tackle complex problems beyond human comprehension. Ants are not individually capable of understanding the piano-mover problem at a basic level; research administrators are generally capable of understanding the work of individual researchers, they just don't have the time to digest all the details.
The larger issue for most quantum key exchange setups is the transition from classical to quantum: you want not to accidentally generate two unentangled photons in the same secret polarization.
I have to disagree. Boilerplate can simply be a one-time cost that is paid at setup time, when somebody is already required to have an understanding of what’s happening. That boilerplate can be the platform for others to come along and easily read/modify something verbose without having to go context-switch or learn something.
Arguing against boilerplate to an extreme is like arguing for DRY and total prevention of duplicated lines of code. It actually increases the cognitive load. Simple code to read and simple code to write is low-cost, and paying a one-time cost at setup is low compared to repeated cost during maintenance.
