Hacker News new | past | comments | ask | show | jobs | submit | andrewingram's comments login

I prefer to minimise vowels in early guesses, because I find i'm good at filling in the blanks between consonants, but not the other way around.

Yeah, it may be right to dismiss the environmental criticism as the weakest one, but I don't think the article sufficiently makes the case for that dismissal.

In a system centred around the premise that money is the only thing that motivates, for thing A to beat thing B, there has to be more money to be made from doing thing A. I don't think the case has been made here (though perhaps it has elsewhere) that PoS can beat PoW on these grounds -- are there sufficient incentives to make that shift?


I think "spacer components" is a bit confusing and not really the message someone should take away from this. I think it's better to say something like "Make parent components responsible for managing spacing around their children", not as catchy I admit.

My own understanding is that it’s supposed to be a prediction input organic growth and nothing more. All it’s really telling you is whether a customer is likely to provide you with another customer, which is why only really high values answers matter, because “hell yeahs” are all that really matter.

I’m skeptical as to its usefulness even for this, but most companies I’ve worked for use it as a general KPI which is even more aggravating.


If you go into the trouble of collecting it, it's reasonable to use as a KPI, as it carries useful information.

I imagine you are annoyed that they optimize for it. And yes, it's not reasonable to optimize for it. Why do people optimize every KPI?


>Why do people optimize every KPI?

Because if it's not worth optimizing around, how key can it be?


You can do a lot of things with a number that are not optimizing.

For example, you can satisfy it, you can alert on behavior, or you can use it as a control (but ok, maybe this one makes a two number KPI instead of two KPIs).


In most startups I’ve worked at, the engineers have for the most part been the ones yearning to work on more sustainable strategic solutions to problems, but it’s the pressure from the rest of the business to ship ASAP that forces everyone into a tactical execution mode.

There’s always been an emphasis on the numbers that need to go up, in order to make the fundraising deck look good so that the company can keep existing; whilst focusing on the long term can often temporarily have a negative impact on numbers (or at least stall them), such that those accountable for those numbers will never sign off on it.

Yet these companies ended up as unicorns, so they’re at least doing _something_ right.


It's better to have a business with profits and things to fix up than having no business. It's a tradeoff that has been proved to be valid.

As an engineer, it's hard leave some things half baked, but it is what it is.


This kind of tree is being used by Rome in their Rust rewrite (https://rome.tools/blog/2021/09/21/rome-will-be-rewritten-in...).


This is (mostly) untrue. It's easy to deploy Next anywhere you can run a node server. What's more fiddly is deploying it somewhere that has its own special environment, like AWS Lambda, Cloudflare Workers, Netlify etc; basically "serverless". But adaptors do exist for most of these to make it fairly painless, they're just not part of Next itself.

The advantage of Remix in this area is less that they've written their own adaptors for these platforms (do we really care who writes them, as long as they exist?), but more that the level of abstraction they've chosen appears to make it _easier_ to write these adaptors.

Edit: Something I missed, is that Remix does appear to work on Deno, whilst Next doesn't.


I believe you're right, Remix has no such features. Ultimately Remix can be thought of as a compiler that eliminates a lot of the boilerplate for which we could already do perfectly well back in 2015 (ish) with React Router 2 and 3.

There's a bit more to it than that (mainly some magic related forms and data reloading), but if you were hand-rolling your own React SSR code back then, you'll find that the overall capabilities of Remix are somewhat similar -- just much less verbose.


For some yes, for many, no.

At one point I was working out 4 days a week, was absolutely ripped, and salsa dancing multiple nights a week; but I was still depressed.

It really depends on what kind of depression you have, often it’s a consequence of something else (in my case, probably an anxiety disorder and a genuine difficulty forming lasting social bonds).


I have similar experiences from salsa lesson. I did years and years of classes, but did one private lesson (and a few years later another) with an exceptionally good teacher and got more enough actionable insights to fuel my improvement for at least a year.

Even experienced dancers who teach will often say what they think they're doing rather than what they're actually doing, which I always find frustrating. The approaches that work best for me are:

1. Describe how it feels to do what I need to do

2. Describe at the biomechanical the principles of what I need to do, which muscles to engage, how my weight should be distributed etc.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: