sieep

Blazor at work to keep the lights on, Phoenix at home to keep my sanity :D

Hello, I'm someone who does not have a background in CS, so my apologies for not being able to read the paper in-full. Is there any clear-cut strategy you would recommend to model developers so they can improve in not just correctness, but in quality & efficiency? I'm sure it's in the paper & I wish I could understand it in-depth.

If you don't mind me asking a more personal question, I would love to go back to uni for a master's in computer science & hopefully assist with papers like this one day. Do you have any advice for someone with industry CS experience (SWE) vs. academic to make the leap to the academic side? I genuinely love this kind of stuff and already make a decent living so it's not for money.

firefox + DDG + linux + vpn is my preferred combo, or the 'privacy stack' as I like to call it.

Seems legit, I'll have to try later. Just curious, why didn't you make this a commercial SaaS?

Agreed, I don't want to have to dig through documentation to get the gist of your framework/library.

True. I'll go nag the senior to start updating that for the 100th time.

I can't wait to ditch my Samsung phone for a google pixel with Graphene.

Looks interesting & I'm excited to try this out myself. I like the more verbose null/error handling personally in professional code, but maybe that's because im still working in framework! I'll certainly be using these in my personal projects that'll be on .NET 10

Some big leaps being made in your argument, but I think the sentiment is where the heart of the issue with this tech lies. Privacy focused individuals will never buy a product like this, but it clearly is meant for the masses & not the typical HN user.

A privacy-first version of smart glasses running OSS would make me lean forward in my seat, at minimum.

This is an interesting take. I think they are heading down this path, especially with the 'Easy Apply' button which is essentially what you're talking about.

If I have to guess, the current business model is likely profitable & any deviations too far from that could hurt their bottom line. Incrementing slowly overtime to LinkedIn replacing the CV seems to be the play, mainly to keep the current cashflow going.

Escalating to a human in a time-appropriate manner seems like what people are asking for.