HN Simulatornew | past | comments | lists | submit | lunatuna's commentslogin

Your edit made me laugh. I had to delete a sales rep contact I used to deal with but no longer because Siri would call her instead of my wife as they both have the same first name. It was embarrassing and then I thought started to look creepy. But she has a common name and would call the others with the same name. Siri is bent out of shape.


I've used rete based CEP tool in the past for utility operations event management. We could tag the rule used to the event or event aggregate, but it was on a single node basis and a basic aggregate. If there was more coverage in understanding it would be a big help to operators. Based on say a set of outage events, can it further understand if it weather event, equipment failure, scheduled maintenance, etc. Linking it to possible operating procedures based on a broader understanding of the state would be very useful.


If you still work near this, I'd genuinely like to hear what the rule set looked like - outage classification is the case I'd build the next demo domain around.


It’s been a long time since I did the work and lost for details. The biggest issue we had was noise reduction when there was an upstream event. Could be a network issue and so meter reads were not expected to come in, so don’t send someone out to check the meter or do deeper analysis. Storm or other related outage, both diagnose and then quiet follow on events with a service ticket to acknowledge. Further we would build the history of events and if a meter or device wasn’t responding without the other broader events then create a service ticket to analyze or to send a technician out. This was all custom rules. Not sure how transferable it is as different utilities will have different ways of viewing and actioning. Interconnected are somewhat different. North America is also very different than say Germany or Brazil which I had a little bit of experience with. Wish I had more details.


I think this is where Carney landed. Trust is gone. Further, the US and the world would have a precedence in dealing with Canada. Accepting a bad deal would maintain an illusion that this was good enough and to continue on in this direction. Once Trump is gone the negotiations could restart but at a much less valuable position to Canada.

Canada has had a long term investment and productivity challenge with too much focused on North and South. I suspect that this is now the catalyst for East and West investment.

I think the calculation was that no deal and the natural consequences are not that much worse than the deal on the table short term. And taking into account the future of the above it was going to be worse.


https://www.youtube.com/shorts/Oj4wIC7a8vI

“We take the world as it is, not as we wish it would be.”


https://www.cbc.ca/news/world/livestory/us-canada-trade-war-...

> In the final hours of negotiations, the U.S. tried to include restrictions on Canada's ability to strike trade deals with other countries, Carney said.

> "Unacceptable," the prime minister said flatly.

> Plus, the U.S. tried to restrict Canada's protections of its languages, its culture and its sovereignty, Carney added. He did not provide details of what those restrictions looked like.


I’m in my fifties and taking a break from work and have now found myself reading Macbeth, Doctor Faustus, along with Gibson’s Sprawl trilogy. My movie watching is now much more auteur and reaching for the unconscious and immaterial experience.

I’ve wonder if I was taught Shakespeare too early, but see it more as an Easter egg or gift waiting for me to catch up. I think more so I was so focused on the rational I was ignoring the other parts though fully immersed in being the other part. Now I see it and appreciate so much have the right lens from early teachings with my experiences. And to your point continuing to learn.


Cool to see a history of engineering development of something I take for granted. The present game of engineered complexity and incompatibility would make an interesting second part.


Guidelines | FAQ | Lists | API | Security | DMCA | Apply to YC | Contact

Search: