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`.
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.)
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.
Love the article, really hit home for me. I attend UCR, which while being a UC, doesn't get nearly enough attention for its engineering program.
If your company would like to put the practices of this article into use, I would be happy to help you diversify your recruiting process! (I'm on the board for many of our engineering orgs.)
UCR has a surplus of extremely qualified students that don't get internships because of the lack of active recruiting happening on campus.
Curious to hear what other's opinions are on the learning curve of a project like this.
To me, it seemed a lot to understand (with file structure, architecture, etc.) over something more minimalistic like Next.js (https://zeit.co/blog/next3)
I used the server tutorials in howtographql.com, they were very informative.
Scroll down to the hands on tutorials, the ones on the right are server-side tutorials. I still recommend you read through the beginner material as well!
I've just started building a server/client seed that I can use in the future for my personal projects.
The concerns you have with the front-end are founded. However, you can send a request to a GraphQL endpoint in a very REST-like manner. If you can build a wrapper to create the query as explained in the Stack Overflow post, you can essentially negate the need for Relay/Apollo. (At least until you need any of the helpful tools they provide.)
> 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.