HN user

licyeus

89 karma

https://sllvn.me

Github @sllvn, Twitter @licyeus

Posts0
Comments58
View on HN
No posts found.

There is a large, growing Russian diaspora and many writers/artists create works in exile. The language helps if you want to understand the millions who left their homes out of principle, but they are not the "enemy".

Thanks for the transparency + analysis.

I've been a happy Fastmail customer for 11+ years and will continue to be so. Everyone wrote that their experience with FM support has been good, but I've been even luckier: until today I never needed support. One bug per decade is a great record.

I am the OP.

I admit my second message was terse, but the correct social media response for a critical outage is "we're looking into it". Not "if you want support, go here".

Like I said, I do not have time to hunt for whatever support channels exist and file a ticket. I pay $50 a year so they can deliver a working product, including triaging their own issues.

I had EVO ICL done ~10 months ago. My contact prescription was -7.25 left / -6.75 right with thin corneas so I wasn't a great candidate for LASIK. Weighed costs of ICL vs PRK and opted for the former (mostly recovery time concerns + as you mention ICL can be removed). Dollar cost was ~9.2k USD, so it was significantly higher than other options.

Recovery was very quick. I was 20/40 a few hours after surgery and 20/15 the following day (could have worked at computer, but took the day off). Pretty intense dry eyes initially, but eye drops helped and this improved over next couple months.

10 months later, vision is still great (though I expect my eyes to continue their normal progression). Halo-ing effects at night are stronger than I expected (believe they're related to pupil size + hole in center of lens), but I've mostly learned to ignore it (I also now prefer not to drive at night). Minor dry eyes but might try NAC supplement as suggested elsewhere in discussion.

I'd do it again in a heartbeat (hated dealing with contacts on camping trips) but wish I'd been more informed of halo-ing risks.

Canceling The Economist was the worst experience of any periodical, by far. You were right not to continue.

Recently canceled and (from transcript) it took 18+ minutes chatting with an online rep. They made sure I knew all the various benefits (newsletters, podcasts, etc), offered me multiple price discounts, and insisted that I try a slimmed down experience ("Espresso") for a month before truly canceling. I'll never consider re-subscribing.

I use stylish to apply my own (quick and easy) dark mode to hckr news:

  @media (prefers-color-scheme: dark) {
    body { background-color: #444; color: #ccc; }
    .entries a:hover { background-color: #666; }
    .c00 { color: #ccc; }
    a:link, .c00 a:link { color: #ddd; }
    textarea { background-color: #555; color: #ddd; }
    .pagetop { color: #ddd; }
    .pagetop a { color: #eee !important; }
    #hnmain > tbody:first-child > tr:first-child td { background-color: #630; }
  }

California CC tuition is not representative of the rest of the country.

In-state tuition for a full-time (15 credits) student at Salt Lake Community College is currently ~2100 per semester. At Denver Community College, ~3000 per semester.

That seems "nearly free" from our perspective in the tech industry, but when I was a young adult making $13/hr it was a challenge.

I built a text annotation tool recently, first in React before rewriting it in Svelte. I found React's virtual DOM annoying, esp. when dealing with text selections + wrapping those selections with elements, etc. Svelte was just simpler in this regard (and overall, IMO).

But if you're not a frontend dev and want to use lots of off-the-shelf components, Svelte's ecosystem is much smaller than React's, so you won't have access to full-featured component libraries like MUI, Chakra, etc. Additionally, Typescript support is stronger in React (it's mostly there in Svelte, but lacking in some areas [1]).

For both React and Svelte I found XState helpful to manage annotator state. It might not be necessary if your app isn't terribly complex (in particular, Svelte's built-in stores can handle complex state well), but I've found it a good way to think about state+events and more confidently make changes as a result.

1 - https://github.com/sveltejs/svelte/issues/4701

I initially preferred JSX ("it's just Javascript"), esp. with Svelte oddities like `$$props`, but after working with Svelte templating for a while I now prefer it due to things like property shorthand and event forwarding.

Re: `:else` syntax, I also made mistakes (`#` and `/` were familiar having worked with Handlebars/Mustache) until I internalized that `:` meant block continuation (also used with await/then/catch).

This seems pretty clearly not about nostalgia or technology.

Nothing signals "don't talk to me" like plainly visible earbuds. I used to wear a pair, with nothing playing, when walking around the city. Worked like a charm + more portable than over-the-ear headphones.

How is Gallup calculating risk? As far as I can tell from their appendix, they're using total hospitalizations / total US population. Ie, 2.6mm hospitalizations / 330mm population = ~0.8% risk of hospitalization.

This is obviously misleading: the pandemic is still ongoing. We're now at 3.1mm hospitalizations, does this mean risk has grown from 0.8->1% between Aug 9 and today? Or that in May 2020 the risk was essentially nil?

Once infected, risk of hospitalization (across all ages) is currently 7-8% (using 7-day rolling averages from CDC). Lower than people assume, but still concerning.

https://covid.cdc.gov/covid-data-tracker/#new-hospital-admis... https://covid.cdc.gov/covid-data-tracker/#trends_dailycases|...

Calico Energy | https://calicoenergy.com/ | Remote (offices in Seattle and Chicago), must be US-based (citizen or green card)

We're creating a utility data platform to help building managers / utility admins understand their energy footprint (think data ingest + dataviz-filled dashboards + admin workflows). We're looking for a senior full-stack engineer, though the work is pretty backend-heavy. Tech stack is .NET Core / SQL Server / Azure on the backend, Typescript / React / Redux on the frontend. We're a small team, so looking for someone who can take our vision and run with it, working with our PM and other stakeholders to ensure you're solving real customer problems.

I'm happy to answer questions here or via email at andrew.sullivan@calicoenergy.com (I'm an engineer on the team). The job posting is at https://calicoenergy.bamboohr.com/jobs/view.php?id=38

AFAIK, the Seattle / King County survey did not ask which neighborhood or zip code they lived in. The questions are listed on the survey PDF I linked earlier.

Do you have a source? Closest I can find is from 2016, and it's 25% of in-county zip codes equalling Pioneer Square, not 80% of all:

"The records show that more than 8,000 clients [of any homeless/housing services tracked by All Home] listed their last ZIP code as 98104, which covers Pioneer Square and downtown. That’s about 25 percent of all clients who gave King County ZIP codes. Putnam says clients sometimes list ZIP codes for the shelters where they last stayed or the neighborhood where they’d been seeking services."

https://www.seattletimes.com/seattle-news/politics/king-coun...

The LA homeless survey does track where people lived when they became homeless. In 2019, the number who became homeless outside of CA is 20% [1]. AFAIK, they don't release raw data so we can segment by newly homeless, but in 2018, this same figure was 14% [2].

Seattle / King County's survey asks a similar question and it's just 5% [3]. Conservative media up here likes to claim that homeless immigration is a significant problem (it isn't), but it seems like LA is facing a different challenge.

1 - https://www.lahsa.org/documents?id=3437-2019-greater-los-ang...

2 - https://www.lahsa.org/documents?id=2059-2018-greater-los-ang...

3 - http://allhomekc.org/wp-content/uploads/2019/07/Updated-7.11...

Github's GraphQL API calculates a "rate limit score" based on query complexity and allocates a max points-per-hour [1].

Similarly, Postgraphile (which I'm more familiar with than Hasura) allows setting either a max query cost or a max query depth [2]. I haven't had to use either, as I don't provide a public GraphQL API (and can just whitelist the queries I intend my clients to run), but there are ways to limit query complexity.

1 - https://developer.github.com/v4/guides/resource-limitations/

2 - https://www.graphile.org/postgraphile/production/#limiting-g...