although the ocean and rainforest seem to be two different extremes of dissimilar environments, surf and turf have several similarities. One similarity that is present in both environments, yet seems counterintuitive is the fact both a reef and a rainforest are essentially nutrient desserts. Both ocean water and forest soil contain low levels of biologically relevant nutrients, and as a result, organisms have developed creative and sometimes symbiotic/mutualistic strategies to thrive in these nutrient-poor environments.

No option is perfect here, but a warning seems like a decent compromise unless there's a whole bunch of other plugins that break

What tabs would be particularly useful for is new music discovery, like an album you’ve been wanting to get around to hearing but haven’t yet had the time. I bump into this problem quite a bit. Adding a new album to my “Liked” songs on Spotify shuffles it in with all of my favorite stuff, and decluttering that playlist later is a hassle. Making a new album a playlist almost assures that it’ll be forgotten about. My decrepit, goldfish memory doesn’t have the space to remember to return to a playlist of an album two weeks later. As my colleague Victoria notes, she’s always “forgetting what I’m supposed to listen to next.” You know what would help with that? Tabs.

Cryospheric and hydrological changes in combination with socioeconomic changes are threatening downstream water security (Drenkhan et al., 2019; IPCC, 2019). Glacial melting impacts river discharge and the availability of water in areas downstream and change in runoff pattern of rivers draining from the glaciated catchments (Table 4). Hydroelectric power generation depends completely on water availability, and any variability in flow pattern of rivers can have far-reaching consequences for energy security of the country. Available hydrological simulations indicate reduced rainfall and shrinkage of glacier, thereby leading to shortage of water supply for power generation and irrigation particularly in highly glaciated basins (Gautam et al., 2013). The increasing drought frequency combined with other environmental degradation has already affected the livelihoods particularly of smallholder farmers.

The question is similar but its in a Rails context. The solutions would answer my question, but I'm almost certain that he could probably leverage Arel to solve his problem. The question I posted was designed purely as a Ruby question so that it was easier to search for. You might want to suggest an edit of the title of his question because it didn't show up when I searched for a solution to my problem.

That's it! Just replace let! with let_it_be. That's equal to the before_all approach but requires less refactoring.

That technique works pretty good but requires us to use instance variables and define everything at once. Thus it's not easy to refactor existing tests which use let/let! instead.

I've seen (and fixed) Ruby code that needed to be refactored for the client objects to use the accessor rather than the underlying mechanism, even though instance variables aren't directly visible. The underlying mechanism isn't always an instance variable - it can be delegations to or manipulations of a class you're hiding behind a facade, or a session store with a particular format, or all kinds. And it can change. 'Self-encapsulation' can help if you need to swap a technology, a library, an object specification, etc.

Also, Sandi Metz mentions this in POODR. As I recall, she also advocates wrapping bare instance variables in methods, even when they're only used internally. It helps avoid mad refactoring later.

But sure, go ahead and enforce self-encapsulation if you like; it makes it easier to do memoization or whatever later on.

The number one problem that I see developers have when practicing test-first development that impedes them from refactoring their code is that they over-specify behavior in their tests. This leads developers to write more tests than are needed, which can become a burden when refactoring code.

Unfortunately, given how widely used concat_javascript_sources is, this required changing a lot of tests. It would be nice if we could remove some of the duplication in these tests (so that similar changes would not require updating this many tests), but that can come in another PR.

Jbuilder gives you a simple DSL for declaring JSON structures that beats manipulating giant hash structures. This is particularly helpful when the generation process is fraught with conditionals and loops.

hyperscript is much simpler to refactor and DRY up your code than with JSX, because, being vanilla javascript, its easier to work with variable assignment, loops and conditionals.

Templates are prone to unnoticed runtime errors, are hard to test, and are not easy to restructure or decompose.

The feature is highly likely to be implemented, the API and implementation are the only real topics of discussion right now.

When a component reaches such a size that this becomes a problem, the obvious course of action is to refactor it into multiple components. But the refactoring is complex for the same reason: extracting the styles that relate to a particular piece of markup is an error-prone manual process, where the relevant styles may be interleaved with irrelevant ones.

(At the point at which it does make sense to turn this into a separate Tooltip.svelte component, the extraction is a completely mechanical process that could even be automated by tooling.)

there’s 3 steps to building software: Make it work Make it right Make it fast

Risk assessment◕Risk management strategy○Supply chain risk management◑

Risk assessment

none of them analyzed the threat of, and vulnerabilities to, a cyberattack spanning all three interconnections.

Problem definition and risk assessment

Problem definition and risk assessment.Addresses the particular national problems, assesses the risks to critical assets and operations—including the threats to, and vulnerabilities of, critical operations—and discusses the quality of data available regarding the risk assessment.

Further, federal agencies have performed three assessments of the potential impacts of cyberattacks on the industrial control systems supporting the grid.

The electric grid is becoming more vulnerable to cyberattacks via (1) industrial control systems, (2) consumer Internet of Things (IoT)45devices connected to the grid’s distribution network, and (3) the global positioning system (GPS).