1,416 Matching Annotations
  1. Oct 2020
    1. “Yes. My objection is, that your proposal obliges us to wait.”

      It would be rather anti climactic for the mystery to be dependant on waiting for the reclaim of the diamond from the bank. It makes me believe that something else is likely to happen in between that timeframe, perchaps a new fact that reveals a different location of the diamond. At any rate it seems as if this part of the plot (the diamond resting in a bank) may not be what's really going on... Interested to see what is missing here, maybe Franklin will somehow remember something from before that event that renders this fact irrelevant, assuming that Rachel is truthful and did indeed see Franklin steal the diamon.

  2. Sep 2020
    1. But when you’re using Svelte within a larger Rails app, you probably already have a CSS system in place and there’s no reason to change that. You can just use the same CSS classes as you do elsewhere in your app, and everything will be fine.
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
    2. Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
    1. This has already forced me to forgo Svelte Material because I would like to add some actions to their components but I cannot and it does not make sense for them to cater to my specific use-case by baking random stuff into the library used by everyone.
    2. The point of the feature is to not rely on the third-party author of the child component to add a prop for every action under the sun. Rather, they could just mark a recipient for actions on the component (assuming there is a viable target element), and then consumers of the library could extend the component using whatever actions they desire.
    1. You'll have to create a new component that brings in the functionality of both. TooltipButton, TooltipLink, Link, and TooltipRoutedLink. We're starting to get a lot of components to handle a bit of added functionality.
    2. For the tooltip example, if you had a whole bunch of tooltips on different elements, it would be annoying to have different event listeners and "should it be shown" variables for each one.
    1. Perhaps at that point we're better off settling on a way to pass components through as parameters? <!-- App.html --> <Outer contents={Inner}/> <!-- Outer.html --> <div> <div>Something</div> <[contents] foo='bar'/> </div>
    2. I would hope for it to come with React-like behavior where I could pass in a string (like div or a) and have it show up as a normal div/a element when the child component used it.
    1. The lack of spread continues to be a big pain for me, adding lots of difficult-to-maintain cruft in my components. Having to maintain a list of all possible attributes that I might ever need to pass through a component is causing me a lot of friction in my most composable components.
    1. Three tests to prove a small piece of behavior. Although it might seem overkill for such a small feature, these tests are quick to write—that is, once you know how to write them
    1. Sometimes answering a single question can be very time consuming (such as setting up a benchmark), but discussions tend to stall out if concerns don't get thoroughly addressed.
    1. For example, you might want to use the browser’s knowledge of the user’s current time zone to group a collection of elements by date.
  3. Aug 2020
    1. Ray, E. L., Wattanachit, N., Niemi, J., Kanji, A. H., House, K., Cramer, E. Y., Bracher, J., Zheng, A., Yamana, T. K., Xiong, X., Woody, S., Wang, Y., Wang, L., Walraven, R. L., Tomar, V., Sherratt, K., Sheldon, D., Reiner, R. C., Prakash, B. A., … Consortium, C.-19 F. H. (2020). Ensemble Forecasts of Coronavirus Disease 2019 (COVID-19) in the U.S. MedRxiv, 2020.08.19.20177493. https://doi.org/10.1101/2020.08.19.20177493

    1. I have a theory that time scarcity is also linked to something I'll call time scatteredness. This happens when you really have no idea how long it takes us to complete tasks, and this skews how much time you think you have or need.

      I relate to this so much I can still feel the sting on my cheek from where it slapped me

    1. it’s a wise idea to begin tracking your time in order to get a more realistic handle on how long specific projects and tasks take you. That’ll override your optimism bias and keep your expectations for your own productivity in check.
    2. Pushing a deadline back once is one thing. Needing to do it over and over again will make it appear as if you don’t know how to manage your own workload.
  4. Jul 2020
    1. There is a usability problem here, it's basically impossible to read the output of Time#inspect in such a case, even though the input was readable.
    2. So, which is better? t.inspect # => "2007-11-01 15:25:00 8483885939586761/68719476736000000 UTC" t.inspect # => "2007-11-01 15:25:00.123456789000000004307366907596588134765625 UTC"
  5. Jun 2020
    1. Disqus:

      As for publishing this as an actual gem on rubygems.org...I have enough open source I'm involved in all ready (or too much, as my wife would probably say) and I'm not really interested in maintaining another gem. Are you interested in taking over this code and releasing it as a gem and being maintainer?

    1. I could get a lot more done in an 8-9 hour day with a PC and a desk phone than I get done now in a 9-10 hour day with a laptop /tablet / smartphone, which should allow me to be more a lot more productive but just interrupt me. I don't want the mobile flexibility to work anywhere. It sucked in management roles doing a full day then having dinner with friends and family then getting back to unfinished calls and mails. I much prefer to work later then switch off totally at home.
    1. Internally, we are continuing to encourage any employee who needs time and space to process current events or participate in protests should they choose to take sick time so that it doesn’t impact their personal paid-time off.
    1. Kempfert, K., Martinez, K., Siraj, A., Conrad, J., Fairchild, G., Ziemann, A., Parikh, N., Osthus, D., Generous, N., Del Valle, S., & Manore, C. (2020). Time Series Methods and Ensemble Models to Nowcast Dengue at the State Level in Brazil. ArXiv:2006.02483 [q-Bio, Stat]. http://arxiv.org/abs/2006.02483

  6. May 2020
    1. When someone asks if you have time for a meeting next Tuesday, you may have nothing on your calendar, so you say “sure.” If you hadn’t agreed to the meeting, you would have done something with that time - but what? By getting clear on what the “what” was that I could be doing made me better at saying no. When you say yes that one hour phone call next week, you are saying no to revamping your sales page or going to the gym or getting home an hour earlier. There is not always a right or wrong answer, but if you realize what you are saying no to every time you say yes, then you can make a judgement call: “Is this phone call more important to me than going to the gym today?”

      By blocking in your calendar in advance you make future tradeoffs explicit. You are no longer saying yes to a meeting on Thursday. You are saying yes to swapping out your gym session for that meeting (or not).

    1. Having to rebase and cleanup the commits while actively working on something is time and attention consuming.

      I'm not sure how I feel about that. Usually I'd say it's worth it to do it periodically, even while you're working on it. Just not obsessive compulsively to the point that it is distracting from actual work.

    2. Good commit hygiene in general is a tough thing to enforce. It requires manual labor and descipline, from both the author and the reviewer.
    3. If we can encourage people to create clean commits as they go, the example as you showed above should be far less common, because cleaning up such history as an after-math is most of the time almost impossible.