No kidding, I read your comment first and then wondered how bad could it be. Turns out the whole comment is nearly that one sentence. Sentences are like functions, sometimes you need a really long one, but oftentimes they work better in reasonable chunks.
My ISP in a small rural town supported IPv6. I have a few personal projects that only have a public v6 address because I don't want to pay AWS for an v4 address.
It worked fine for a year and a half after I moved in, then they did some work and suddenly no IPv6. At least I could enable 6to4 on my router, but that has intermittent issues.
As someone who wishes IPv4 would just die, I wish I had options to push back on such nuisances.
It doesn't make sense that you would lose more weight by sleeping only considering metabolism.
I can see an argument around sleeping always being a net loss, since you're never consuming food while sleeping. Sleeping more thus means you may eat less.
I worked for about 8 months on an internal product for doing transmission studies at a large utility company. Basically, it would feed a PSS/E [1] file specifying most of the transmission grid into a power flow simulation software called TARA [2]. We would add a few extra elements to the grid to simulate a wind or solar plant. TARA would spit out all the components that would be overloaded, with or without contingencies. We would read the results and estimate the transmission costs.
Essentially, we were replicating the process that the ISOs used internally. The users of this product were all former ISO employees. The goal was to speed up the process of determining whether transmission costs were going to ruin a project before any money was spent. ISOs take months to do their analysis. The users told me that they were usually looking for $0 transmission upgrades on $50m+ projects.
The grid and contingency files from the ISOs were under confidentiality agreements. This rubbed me the wrong way from a competition point of view. We also had data about projects slated to be built which could take away capacity from our projects.
I could see a SaaS in doing this sort of analysis. It's probably bureaucratic between reselling TARA, NDAs, and maybe legal issues if the analysis was wrong. I have doubts about the market, most of the money is in big projects at big companies that are already doing this sort of thing.
imo, that's basically the dirty secret of grid data, post 9/11 it seemed as if everything went behind the CEII wall, but in reality it has always been that if you're a legacy player or have the money you can make sure you have access to everything.
It's a thorny issue and something I ponder in my day-to-day[0]. We're members in ISOs where it makes sense, and can provide CEII data once we've confirmed customers already have access, but I would love to be able to show some of it publicly. It's also odd how things vary from market to market. Transmission outages: public everywhere, except ERCOT, where they're considered Secure. Generator bids: anonymized and delayed by up to 90 days everywhere, except ERCOT, where it's 60-days and not anonymized at all (yes, ERCOT is different wrt to FERC jurisdiction).
Years ago I worked at a market monitor[1], and we got everything, just cloning the changes to ISO databases overnight every day, second-by-second PI (plant information) data, it was awesome. The potential advantages from data asymmetry are big enough that there are multiple companies with physical sensors out in the world measuring power lines in different ways to try and reconstruct grid activity in real time, and then others doing it entirely from access to CEII and a deep understanding of how the grid function. But all of this is heavily oriented towards traders, not developers, although I would use trading tools when developing projects because they were the most advanced.
The first job I had as a software engineer was at a trucking company that had a desktop Swing application. If an exception happened, the user would get a pop-up with buttons to email support the stack trace or cancel. The email went to all the IT staff and someone would usually reply within an hour, often with a fix.
The engineering work was atrocious looking back. I probably fixed 50 random NullPointerExceptions in my 3 years there this way. But, it was one of the most productive places I've worked at because everything was done simple and there were no barriers between users and developers.
The first job I had as a software engineer was at a trucking company that had a desktop Swing application. If an exception happened, the user would get a pop-up with buttons to email support the stack trace or cancel. The email went to all the IT staff and someone would usually reply within an hour, often with a fix.
The engineering work was atrocious looking back. I probably fixed 50 random NullPointerExceptions in my 3 years there this way. But, it was one of the most productive places I've worked at because everything was done simple and there were no barriers between users and developers.
Nice site, slick. Not sure what use the data has to me, but I don't make posts, so that's my fault.
It would be nice if the chart would move down or something when you select a post that's lower in the rankings. I had to scroll back to the top after clicking one of the bottom posts.
I think of the word as a mixture of complaining and sympathizing.
I would consider it commiseration if one were to complain to their coworkers about an HR policy in the hopes of receiving sympathy or agreement about the problems with the policy.
