HN user

throwingrocks

164 karma
Posts1
Comments63
View on HN

instead of writing 100 class names for every element, every page, every project, again and again…

I'm turned off from daisyUI with marketing like this. The alternative to daisyUI certainly isn't this.

I use Tailwind in a similar way that daisyUI does: by putting my utility classes in components and reusing the components.

daisyUI's value prop is that not everyone wants to do this for their custom design system. They should just stick to that instead of making false claims.

bulkshitter

With all due respect, this perspective baffles me. Some see it your way, others see so much opportunity.

There is a popular argument that a software developer’s job is not write software but to solve a user’s problem. Bullshit

Wait, what?

I was never particularly interested in the code itself

Instead, I was always more interested in the product

Confusing contradictions aside, I had trouble engaging with this article.

The author seems to think every developer thinks like they do. Some people actually enjoy helping their business/users.

The author also has trouble imagining other perspectives as a people manager. From the linked article,

I do not get any sort of high from managing people. I don’t think anyone gets that same high from this role

Hate to break it to the author again, but some people actually enjoy seeing those they mentor/manage succeed.

Being a people manager isn’t the right fit for everyone. Perhaps being a developer in the next 20, 5, or 1 year won’t be the right fit for the same people it is for today.

Progressive JSON 1 year ago

IMO if one has to work this hard to sell/explain a tech there's 2 possibilities 1/ there is no real need of tech 2/ it's a flawed abstraction

There’s of course a third option: the solution justifies the complexity. Some problems are hard to solve, and the solutions require new intuition.

It’s easy to say that, but it’s also easy to say it should be easier to understand.

I’m waiting to see how this plays out.

This comment section is predictably boring and shows that HN isn’t always a great place for discourse. Change is hard, I guess.

These days, vendor lock-in hardly feels like a worthwhile consideration when evaluating frameworks. A near complete rewrite feels inevitable when transitioning from, say, React to Svelte.

Storage on Vercel 3 years ago

now my defacto playbook for building lasting bottom up disruptive cloud companies

What companies have you built (or played a role in building) using this "playbook" that fit your description?

No. No.

Saying “no” multiple times as if a statement is so absurdly wrong is such a meme at this point and another interesting difference between face to face and online interactions. I can’t imagine having a discussion with friends and someone throwing a bunch of “no”s out.

They failed specifically because of business they were servicing.

This is so disingenuous. They failed because they made risky investments, interest rate hikes put their investments in jeopardy, and when they tried to raise extra capital (responsible thing to do), people were alerted of the problem and left the bank (responsible thing to do).