> 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.
883 karma · joined July 2, 2014
> 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.
Too many people assume remote work always means working somewhere far away from a major urban city.
The article seems to say that the 60-min cardio group had been closer to that sweet spot, but it's not very concrete about that assumption.
https://mega.nz/#!XZ5gXQaY!v9o4KM48y2e0k7ama2O82ZLefvezK2F8Z...
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.
This could be a technology, language, stack, anything that's cool to you!
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)
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'd love to the idea to seek through the content. (Maybe through the parens keys?)
For me, it would ideally show a sentence (or x chars) both before and after. Or maybe a view similar to less?
It goes over several ways to secure your endpoints, along with pros and cons for each.
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.)
https://stackoverflow.com/questions/42520663/how-send-graphq...
I've been using it while following along the backend JS tutorial at howtographql.com and was wondering if it's now outdated and what the migration would look like.
My suggestion: If your audience will experience a major speed/efficiency/accuracy improvement using your tool, you should definitely have rigorous before/after comparisons. Also show how it's easier to use your tool than any existing tool (if true).
Less experienced: I would go with a step-by-step walkthrough of a basic example, with some "Going Forward" inspiration at the end.
More experienced: I suggest doing a deep-dive into an aspect of the technology that may be taken for granted. A lower level understanding is usually appreciated. Maybe address some newer features that can improve a developer's workflow with the technology.
I wonder if this is a consequence of the behavior Hammer is describing?
Anyone had a similar experience or have a better tool to suggest?
I end up watching a much greater percentage of those than movies I try to find and enjoy on my own.
However, with my Netflix usage increasing, I've found that I usually peruse their recommendations and watching something from there.
https://rradczewski.github.io/ymmv/assets/office_noise_noisy...
I don't think this chart demonstrates your point. Don't you want people to eventually stop needing to use Noisy at all? As of now the chart just shows that more people are familiar with the Slack command.
I would also be interested in knowing how large the team is that this is being tested on.