HN user

jaf656s

199 karma
Posts0
Comments82
View on HN
No posts found.
Tailwind UI 6 years ago

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

Tailwind UI 6 years ago

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.

Visa Buys Plaid 7 years ago

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.

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)

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.

One result set is equivalent to another, and as long as you aren't using unnecessary nested loop joins or such, there are a dozen ways to solve a query.

If they consume similar resources I'd almost always opt for the simplest one to understand.

In cases where the simpler one is less efficient, I might still use it if the task didn't require absolute optimization.

There's a really good point in here that I had to learn the hard way: one of a founder's most valuable assets is a deep understanding of the customer's problem(s) and how to solve them.

The tech is far less important.

She first tried a naive tech-focused approach and realized that she didn't understand the problem well enough and making adjustments to the tech was slowing her learning down too much.

She made a great decision to optimize for learning speed and temporarily build a more traditional custom-fit bra business. She has learned a lot about the problem space and what makes a good solution.

Now she's using technology as a tool to enhance and optimize the process that already arrives at a good solution.

We do the same thing when we write code:

  1. understand the problem
  2. write a correct solution
  3. optimize the solution
When it comes to coding we know Knuth's Law of optimization by heart, but still make the same mistake in other contexts.

This is a great resource, but there are a few things wrong:

1. Fuel prices were low in 2015 and have been rising since then, so 39% of marginal costs is likely a peak.

2. The chart you referenced is only for marginal costs, and doesn't include fixed costs associated with a trucking company. The actual percentage of driver pay to the overall operating cost of a trucking company will be lower once fixed costs are factored in.

3. Automated truck companies will also want to capture a fraction of that 30-40% that is paid to drivers.

So in the end, shipping costs will likely drop in the 10-20% range, which is substantial, but it isn't enough to be revolutionary.

My point wasn't to the value created by having automated trucks, but to counter the point that shipping costs would drop significantly.

Also, since shipping costs are a small percentage of the price of most consumer goods, everyday purchases will not be affected much either.

In addition, there will still be much need for humans to take care of the maintenance of the trucks and manipulation of the cargo over the next couple decades. So there will likely be a significant number of truckers still employed, perhaps with increased productivity.

There’s already an industry that performs these tasks so there’d be a small percentage of absorption of current truck drivers.

You also assume there’d be more trucks, but there’d likely be fewer, at least at first. Since a fully automated truck could operate substantially more hours than with a driver. Drivers have hours of service that restrict how much they drive per day and per week.

Also, on a macro scale automated trucks wouldn’t be adopted if they didn’t displace workers.

In the actual interview, he says the only way to really learn marketing is to market something.

So write the medium article and try different ways to get people to read it.

Most people don't know how to do the latter and give up before even starting.

Your problem with figuring out how to talk to customers is that you don't know who you are trying to talk to.

First you need to figure out who you want your customers to be.

If your answer is local coffee shop owners, then it's easy to make a list of customers and you can call them, email them, or visit them in person.

There are many places on the internet that give free advice on how to do cold calls, emails, visits, etc. Steli Efti writes about it a lot on the close.io blog. There are numerous questions asked and answered on quora.

Start at those two places and once you know more of the basics, you can start learning more specific skills.

But if you don't know who to talk to, then you are trying to solve two problems at the same time: who to talk to and how to talk to them.

Solve one problem first, then the other.

Once you know who to talk to, then you can start talking to them to see if they have the problem that you are trying to solve.

If the service or product you are selling doesn't solve their problem you are not going to be able to sell it to them.

It's much, much easier if you are trying to sell to a customer base (market) that you understand well or already know some problems they face.

Then you can talk to them and verify that you are correct and they have the problem that you think they have.