redshirtrob
Joined 14 years ago
Joined 14 years ago
I only learned about the typo when I asked him to sign my copy at a Christmas Tree lecture years ago. Instead of signing it, he corrected the typo. He had a mnemonic he used to remember the digits in a Potrzebie. He had the mnemonic stored on a file on his home machine. I watched him ssh to the machine, then fire up Emacs to look up the mnemonic.
Buckles and breaks were most common just after a train had left a section of track. The normal approach was to issue slow orders when the temperature got too high (buckle) or too low (break). So there was a lot of interest in finding more accurate ways to determine when slow orders were necessary and to optimize when to add/remove rail.
AFAIK this problem is still outstanding. The product I worked on years ago never quite succeeded. Railroads are a harsh environment.
I actually tried to enumerate the scenarios. When I hit five variables I realized the advice would be mostly worthless. That's 32 separate outcomes, some of which are pretty subjective, e.g. do I think this is a viable company?
Nevertheless, I've been down this road a few times. I have some wins and losses. I think this article misses an important point: Exercising is not an all or nothing proposition.
For example: If I join a startup and leave after a year, the difference between my strike price and the 409a price might be non-zero. I can still exercise a percentage of my options to avoid AMT. Maybe I can't exercise all of them without triggering AMT, but chances are I can exercise a fair amount.
If I'm offered an early exercise, I don't have to do 100%. I can do a number that fits my budget. I just have to make sure I file my 83b election form.
But I get what you're saying.
It's...not very good, but it's a pretty good example of Patterson's work. I read the first 3-4 books in the Alex Cross series, but gave up after finding no growth or improvement on the character or the author.
I think you'll find his popularity similar to what makes lots of other things popular. His books are rather bland, but not quite boring. He doesn't pack a lot of exposition between the action so the plot moves forward. Unfortunately this often makes the characters seem quite stupid as they rush to action rather than ponder the situation. I find this unrealistic and annoying, especially given Alex Cross's profession.
Obviously, I'm not a fan.
I was just on a developer group call the other day where another developer from another organization was having weird scaling issues RDPing into the vendor's sandbox. The solution was to adjust some buried registry setting on the remote machine, not fiddle with the local machine. Unfortunately I paid little attention to the details as I rarely RDP and when I do I can tolerate display issues.
I realize this is super vague, but it was so fresh in my brain I had to respond. Maybe someone who actually knows something can provide actual details.
My Mom was convinced I was sitting in the computer room playing games. When I told her: "No, I was programming", she asked what I was programming. Of course I told her I was writing a game, as all kids learning to program were. She responded: "See! Games!" as though she'd somehow proven her point.
But, like you, I've made my career from programming and it's treated me quite well for the most part.
Indeed it is. Our rule of thumb is that you have to finish what you start, and generally give it two chances. This worked well for me as a child. I wanted to quit everything after the first go, but there were many activities that I loved after the second go, and a few I was happy to be done with (looking at you trombone).
1. Finishing what you start means honoring the promise you made--be it to the teacher/coach, the team, or someone else. Oftentimes other people are depending on you.
2. Giving the activity a second try accounts for the possibility that the problem wasn't with the activity so much as the environment.
To be clear, I only apply these rules for the kids wanting to quit, not the parents. If, as a parent, I observe unacceptable behavior by the coach/teacher, dangerous conditions, etc I will pull the plug. Thankfully that hasn't happened yet.
At one point I asked the customer rep if there was any way to rid myself of this nuisance other than completely closing my account. She responded with the normal "that's your decision, blah, blah, blah...", but I was legitimately asking, not threatening.
I think I said something like: "No, let me be clear: I don't want to close the account. I just don't want to deal with this every six months either. I'm seriously asking if this is the only other recourse because it seems we've tried everything else."
It did get resolved eventually. It was also for a trivial amount so nothing like what you're looking at. It was still very annoying though.
There were a lot of systems in place to monitor rolling stock:
- Wheel Impact Detectors
- Hotbox detectors
- Acoustic bearing detectors
- Truck performance detectors
To name just a few. There were also efforts to monitor the railway infrastructure. The things I remember:
- Rail stress management (rails need to be under the right amount of stress, which of course varies with temperature)
- Top of rail friction management
- Rail profile management (the name eludes me, but the idea is you want the interface between the rail and wheel to meet certain parameters)
I worked on the rolling stock side measuring wheel impacts, overloads, imbalances, and a handful of more esoteric metrics. One of the outputs of these measurements was a train consist. For each of our locations we were able to build up the consist of the entire train (which was a fun CS problem in itself).
I stared at a lot of consists over the years. In North America I never saw anything longer than about 100 cars and 2-4 locos. However, in Northwest Australia they routinely ran 300 car trains meeting the description in this article. But, the reason they could get away with that is they were running a straight shot from the heart of the Pilbara to one of the port towns on the north west shoulder (Karratha and Port Hedland).
I need to check in with my old colleagues and see if things have changed. It wouldn't surprise me if train lengths have gotten longer, but I would be surprised if this correlated with a large increase in derailments, as that would have a tremendous impact on average network speed and thus profit.
As someone mentioned elsewhere on this thread, there are a lot of single track corridors. It's bad enough when one train has to sidetrack. It's really bad when a train takes out the whole corridor. These aren't packet switched networks. It's not easy to reroute. And it's really expensive and difficult to lay new rail.
All that said, our local CU does in fact keep their own mortgage portfolio. This may be rare, I don't know. They're a large CU associated with a government contractor.
When I bought my house they had the best deal (rate + closing costs) hands down. When I refinanced they were no longer offering 30yr loans on their portfolio (and I wasn't interested in 10/15), but still were originating them to sell. Unfortunately the 30yr rates were not as quite good as I could get elsewhere and closing costs were close to a wash so I went another direction.
I was able to do way, way better by going with a local bank, as did my friends.
The only thing I can figure is they are better for folks with "good" (not "excellent") credit and can maybe close the loan faster.
Maybe I'm just misreading your comment, but it has me confused enough to reset my password, login, and make this child comment.