Not sure when you were testing, but we do call out some instability on the Fidelity Institution Status page in the Developer Dashboard.
> To maintain system stability, Fidelity currently limits access during high-volume windows. As a result, please expect unavailability between 9-10:30am and 3-4:30pm ET. We recommend end users link Fidelity accounts between 5pm - 9am ET.
This is a very biased interpretation. Your salary may not be adjusted if you work in a similar CoL area. Only if you move from HCoL to LCoL (and vice-versa!)
Too many people assume remote work always means working somewhere far away from a major urban city.
It's cool that you're working on this! But piece of advice: It would be really nice to see the platform (a screenshot or video) before having to sign up.
Saw this awesome project on Lobsters. I went ahead and ported these components to generalized, composable Styled Components. There's also an npm package at `every-layout`.
You mean "React Components" right? Nice effort, but please mention that these components are supposed to work with React. If we now use the word "Component" as a synonym for React, you make it look like there are no other frameworks than React.
I'm incredibly interested in how the brain experiences time during events of stress or high action. (The skier tripping/falling is used as a visual example in this article.)
On a much smaller scale, I wonder how time experience is changed among individuals who consume media at different speeds? For example, I watch all video media (Youtube, Netflix, various movies) at 2x speed. It could be intriguing to compare my experience of a movie versus someone who watched it regularly. Does the constant 2x-ing affect my evaluation of time in regular life?
I'd be happy to read any and all articles/papers you may have on the topic.
> I'm incredibly interested in how the brain experiences time during events of stress or high action.
Read the book Black Box Thinking by Matthew Syed.
There's a couple of sad examples. One is some doctors who lose track of time while trying to intubate a patient. Another is an airline pilot losing track of the fuel level while trying to figure out whether the landing gear has come down. Both preventable issues where people's focus narrows so much they lose sight of the critical variables.
That's definitely something I've experienced as well! I've learned to take the time to absorb what people are saying/meaning with a greater degree of detail. (That's at least how I believe I'm behaving, though it's tough to self-analyze.)
Moving from this state, to a state where typical human interactions seem rapid, is like a context shift. Difficult to do without a change in location/scenery.
The super fascinating thing is the difference between how the brain experiences time and how the brain remembers itself experiencing time. It seems possible that intense experiences cement more details in your memory, which your brain interprets as having taken longer, without actually affecting the "in the moment" realtime experience.
Might work. Context here is I prototyped a json dsl to do similar graph-like resolving right on top of a python app as a wsgi middleware. Worked pretty well right on the metal.
With this sort of graphql extension, having generic query power for restful clients is awesome. TBH I think that's pretty great compared to baking graphql clients.
> To maintain system stability, Fidelity currently limits access during high-volume windows. As a result, please expect unavailability between 9-10:30am and 3-4:30pm ET. We recommend end users link Fidelity accounts between 5pm - 9am ET.