jaf656s

it would surprise me if the IRS would resolve this favorably for you if your defense was "we didn't keep detailed timesheets"

I don't think he posted a link to his personal site, just said the link was there.

I don’t think it’s in good faith to accuse someone of using multiple accounts to flag your comments without any basis and I believe this type of behavior is directly in violation of the guidelines of HN.

In that case I suggest you didn’t communicate very clearly. You came off trollish.

So you purposely provoked her instead of asking for reasonable clarification?

oh yeah, I forgot about media queries. Which is impossible inline, but also adds to the verbosity

I have been using tailwind on a new project and I only see 3 real benefits over using inline css styles:

1) Sizes are standardized in a predetermined set of discrete size classes. So you start to think about sizes, padding, margins, etc in terms of steps instead of values. You can change the steps in one place and they apply globally. It's a little easier to standardize a rough style guide compared to starting from scratch.

2) Colors are standardized in a similar way. You just need to configure your app's core colors and then you can just think in terms of steps instead of color values.

3) You have a smaller set of "best practice" means to achieve most outcomes compared to all that's available with css. You don't need to know the best way to do what you want, you can just browse the documentation to find what you want.

Outside of that, you still have to use @apply to collapse utility classes into more semantic classes if you want style changes to cascade (tailwind recommends using components or view partials to achieve this instead of via css classes, though this would work equally well with inline styles)

The styles are very verbose, just like with inline styles. They are only slightly shorter than inline styles since they are basically abbreviated forms of inline styles.

You can still do everything tailwind does for you by using your own style guide and building out css classes, but tailwind gives you a head start.

It feels like it makes you more productive in the beginning because you get a toolset with a lot of decisions already made for you, but I suspect it will make things a bit slower as the app gets more complicated.

Plaid provides an api to access transaction history and verify bank account ownership.

They don't do ACH transfers.

It's harder/impossible to deliver hyper-personalized political ads in those other mediums.

It's worth taking some time to figure out the ramifications of all this.

whoops, I thought they said dark energy/matter

The reality is closer to:

We have a lot of observational evidence that the equations are very accurate.

But when we put all the mass we know about into the equations, the result of the equation doesn't match our observations.

Since we have a lot of evidence that the equations are very accurate, then it's more likely that there's more mass we haven't accounted for.

(at least for dark matter)

There are also a lot of resources for therapy for young children if they are diagnosed early.

In California, you can start receiving state funded therapy at 18 months.

In this case it sounds like a bad interview and that they missed a good opportunity for discussion!

You're exactly right wrt interviewing. I was talking in general and not in the context of an interview.

If you are interviewing someone and they solve the problem you ask, and then you don't give them some sort of guidance or constraints to meet your "correct" guidelines, then you aren't doing a good and fair interview.