Glad to see them recovering! In my experience, phalaenopsis are very hardy and resilient. If anything, the seem to prefer some level of benign neglect - especially when potted in the junk big box stores sell them in. After repotting ours in well draining potting material about 7 years ago it’s been very smooth sailing.
People walking on the snow will compact it down, eventually forming an ice layer. Rain is much better at melting snow than ice, so these paths can remain as the snow melts during/after rain.
People walking on the snow will compact it down. Even if it’s below freezing, snow will still melt some and then refreeze when this happens. Eventually you’ll get a layer of ice.
Rain is mu
Absolutely. If the leaves don’t perk up I would snip the flower/baby spike.
Hard to tell, I’ve had Phalaenopsi put out more flowers on old spikes, as well as babies. We’ve had one for over 10 years that’s been through quite a bit before I finally pulled it out of the moss we bought it in, cut most of its roots out, and potted it in bark.
In my experience, they’re pretty hardy. I would personally let the spike go until you know what it is and make the call. Watch the leaves, as long as they don’t get more raisney I would probably just leave it alone.
This can also be one of the frustrating parts of open source.
Find something you don’t like? Fix it. Will the repo owner approve your pull request? Who knows. Maybe they’re a bit absentee. Maybe they view the original behavior as working as designed. Maybe your design doesn’t fit their architectural model, so they’ll (eventually) heavily refactor your changes and merge them in.
You can always stand up a fork, but keeping those two at feature parity and going in the same general direction can become harder and harder with time.
That’s not to say not to try! But it also means reaching out to the repo owners/maintainers before making your first change.
Great lakes life. Ganted, there are way fewer cargo ships than saltwater ports, but it’s hard to beat a big ship for cheaply moving goods/raw materials around.
Tell that to my very sideways baby Jade :(
This did it, thanks!
We have a test environment but it’s a hot mess. All the data is made up and extremely low quality. All the things you would normally interface with are also in test, but getting other teams to coordinate testing in the test space is… a chore. We do the best we can with mock services, but without having real services or representative data some of the data pattern assumptions don’t play out. Leaders value writing code and our lack of architects that span teams mean that when team architects either don’t meet ahead of time, make assumptions, or don’t ever agree on a design then…
We always host UAT. We also track logins. Guess how many users even show up for UAT, let alone actually click on anything.
This is why the vast majority of our testing happens in prod when our users are doing real work.
Sorry for the baby rant :)