Has it been reported what service is driving such a dramatic increase to Neon? I presume v0?
Readit Newskylehg commented on A recap on May/June stability at Neon neon.com/blog/an-apology-... · Posted by u/nikita
kylehg commented on Ask HN: Is patio11's salary negotiation guide relevant in today's market? · Posted by u/sideway
I think the overall thrust of the article — "always try to negotiate, try to get better at it, it's low-downside and high upside" — is still very relevant and I frequently share it with friends interviewing even today.
Some specific things haven't aged well from this article in my recent experience:
1. Many companies have comp bands advertised and enforced by local law, and even outside of this many have implemented more regimented/structured comp in an attempt to reduce bias. 2. Relatedly I've seen more companies take a "no negotiation" policy, especially for more junior roles. 3. The market overall is much more an employer's market and is not growing as quickly, so the median SWE has less leverage.
I think the biggest impact of these changes is that the cost of not negotiating has become lower, and consequently the upside to negotiation is less, especially if you don't have competing offers or are more junior.
That said: competing offers is still the single most effective negotiation tool, as others have said. I've seen companies be relatively inflexible on cash comp but highly flexible on equity comp, which tends to not be required as part of job listing bands, and becomes the lion's share of comp as you get more senior. And often there are carve-outs of matching offers.
TL;DR: Still worth a read, but many of the specifics need discounting.
kylehg commented on Zelma lets you find, graph, and understand U.S. school testing data using AI zelma.ai/... · Posted by u/kylehg
Project from Emily Oster — Brown economist and author of "Expecting Better" — to standardize access to US standardized testing data
kylehardgrave commented on Ask HN: Anyone else burnt out due to extended lockdown and work-from-home? · Posted by u/throwwfh
Fwiw I was feeling very much this way until recently, and blamed it on WFH. I love working in an office and missed my commute, having clear boundaries to the day, having good touchpoints with colleagues. I just felt completely unproductive, highly distractible, and procrastinated everything.
Then I took two weeks off over Christmas/New Years and drove across the country to a new location where I'm working for a couple months, and it's been markedly better since then. I don't know how much was the change of scenery and how much was the vacation, but it made me realize at least part of the problem was general burn-out rather than WFH specifically.
If you're like me and many people I know, you probably haven't taken much vacation because there's not many places to go. I'd encourage you to use some of those days and go into nature, drive somewhere far, whatever you can that feels Covid-safe and mixes things up!
kylehardgrave commented on React Concurrent Mode reactjs.org/docs/concurre... · Posted by u/gmaster1440
It’s a bit tricky because as the docs explain, the only Suspense integration we currently use in production is Relay. I definitely agree we need a complete Relay example that people can run (maybe Relay docs have one already?). But a lot of people don’t know Relay so it would be hard to teach both new UI patterns like useTransition and Relay at the same time. This is why we didn’t do it in the main docs.
How a form would work really depends on how your data solution manages a cache. Relay has one answer for that, some other solution may have completely different answers. So I wanted to keep the first examples simpler and less opinionated.
As more libraries start to integrate Suspense I think you’ll see more such complete examples. But this release wasn’t for the end users as much — it was more for people who would create those libraries.
Hope that makes sense.
Maybe I just missed this, but I couldn't find any kind of guidance for library maintainers on implementing Suspense. Reading the demo code + React-Cache it seems that it's basically about providing an interface that throws unresolved promises, but is there any more detailed documentation?
MobilizeAmerica | Full-stack engineers | NYC | Full-Time | Onsite preferred, but remote possible
MobilizeAmerica is a new type of event platform that makes it easy for progressive campaigns and grassroots groups to connect to citizens and drive them to the highest-impact volunteer opportunities that win elections. Through our web and mobile apps we help organizers scale in-person and digital volunteer programs by optimizing every point of contact with potential volunteers, from cold leads through confirmations and follow-up contact.
We’ve proven out unique hybrid of tech + organizing in the Virginia 2017 elections, and are poised to work with hundreds of campaigns in 2018. We’re funded by Reid Hoffman and Higher Ground Labs.
https://www.mobilizeamerica.io/jobs
Please reach out to me, the CTO, with any questions! kyle@mobilizeamerica.io
kylehardgrave commented on What I would have written dcurt.is/what-i-would-hav... · Posted by u/bradgessler
"And yet I see no solution to this problem. I will forever be a slave to 140-characters..."
I'm having a hard time sympathizing with this.
It's not Twitter that "instantly takes complex ideas out of my brain, over-simplifies them, and ships them off to random people." It's ME. Twitter is just a medium — the solution is to care about those complex thoughts enough to see them through.
Not to say that the instant gratification of tweeting does not exist, or is easy to fight — it's a struggle, and something to be mindful of. But the battle is already lost when, as this article does, you shift all the blame to the service instead of looking inward.