skysight-inc/HackerNews huggingface dataset:
Rec | Full-stack engineers, First Product Designer | SF (Remote OK) | Full-time

We're Rec (rec.us), we're re-thinking how people participate in sports & recreation in their city. We partner with cities first, and then power all of the amazing facilities, instructors, and players in the neighborhood with a set of tools that gets everyone doing more. We've spent the past year building out our MVP and proving our model, which is now live and growing in 6 cities. and 2024 is all about going scaling fast with what is undoubtedly the best software platform in recreation.

We're hiring all levels of full-stack engineers, our first product designer, and folks on the sales team. Apply here: https://wellfound.com/l/2zwdUS
The fact is that the opposite is usually true
Here's an example: https://github.com/jampekka/vddfit

Codewise it's not pretty, especially the data mangling, but other people have managed to use it for their own purposes.

The model had to be implemented in C++ and wrapped for python bindings. It's a pain but sadly less painful than doing it with Julia's startup time.
Not on the rough checklist -

- pray to god whatever helm chart dependencies you have didn't break horribly, and if they did, that there's a patch available
Spotify Connect is a real game changer. I tap a song on the web player and it streams it on our living room amp, which supports it natively. No apps involved whatsoever.
I understand this but at the same time I don't have project managers at home (other than GF), Jiras to track, people to pry answers out of, meetings, code reviews, difficult jackasses, performance reviews, etc. I rediscover the reason I went into tech before corporate drudgery drained all of the fun. I can just build things and shape my tech to my household's needs while getting the feeling that I've built something and practiced my craft.
The dots are a legacy thing now. I agree 100%.

Yes, they protect you from shoulder surfing, all twice in your life, where that may have been a factor. Otherwise, they are just an implement to the user, at this point.
im not sure completely. There is probably inherent traits related to leadership/followership , and a cognitive bias to assume integrity of leaders seems plausible. Before society, might literally meant right.
In the past decade, I wonder how many stalker victims have discovered HaveIBeenPwned as the easy directing tool that their abuser used to discover and invade their accounts and privacy..

Yes, yes, I know, the site maintains that it's the victim's responsibility, prior to any bad actor taking advantage of the service, to sign up and then disable their information from showing up in the search.

Because the shock and awe of other users seeing 'Your info is out there!' immediately after entering their address, instead of after some kind of email verification, is more important than user safety.
Certainly not a way to get clicks. People are eager to see patterns—it’s in our wetware. For example: two podcasts about JFK: one is about a lone gunman, the other a secret conspiracy and coverup. Which will be more interesting? Get more of an audience?
Lobste.rs has an open moderation log: you can see what was done by who. It's one of the few places where I think it's possible to actually trust the moderators are treating things fairly.
You should learn a bit about Rails. It wont be strange that people still use it.
Calling hotels on the phone. When I suggest it to my 30-something peers they look at me like I have two heads though.
You really should just book direct. You'll often be treated better and will have better recourse on-site when things go wrong.
Yes, Critique (and Gerritt) is a good tool. Yes, Googlers tend to behave well in code reviews and conduct them decently, but..

The reality is that this kind of survey is a) self-selecting for the people who adapted well to Google's process, and b) not really measuring for productivity, just satisfaction with tools and some aspects of the (assumed given) process.

What I personally found is that Google is the kind of place where you can only truly be productive if you have the kind of brain that can fork off N work tasks at once and then fork/join on all of them.

If you're the kind of person that does better when going down the whole mineshaft on one problem at a time, you'll be screwed. Because you'll be constantly spending the bulk of your time sitting waiting for review approvals, or getting your account added into some ACL somewhere, or getting sign-off on a PRD or design doc, launch / security approval, or some other form of coworker approval. The only way to make progress is to do a bunch of those kinds of things at once and juggle between them.

After 10 years of battling it, I realized it's not for me, no matter the $$.

(There are some other things that Google does exceptionally smartly, though. The monorepo and the way they handle third party deps [check them in and only allow 1 version for whole company]) I think is one. Both of these things seem crazy at first, but they are amazing at minimizing whole classes of complexity around versioning and dependencies that add mostly needless overhead to the job of engineers)
23andMe confirms hackers stole ancestry data on 6.9M users
I got laid off in Jan 2023 and they only gave me the 2 weeks, but was able to at least negotiate that my end date fell on on Feb 1 so I could at least have healthcare until the end of the month.

"I don't recall saying good luck"
Might make more sense to think of it less as a donation and more as buying fuzzy influence.
Although I haven't used Nim, something I miss while using rust is `static if`. You can sort of approximate / do a subset of this with #[cfg(xxx)] directives in Rust.
But further work from the same leadership has been discontinued...
HFT? :D

Which country are you in?
I really like his informative posts. I remember reading about how he used k-anonymity to check passwords against the pwned file without having to transmit the passwords and it led to me studying that and later using it for some professional projects.

I sometimes think what I would have done had I never read his posts about checking without transmitting real PII.
There is only so much metaphorical food in the world.
That's selling modern and historical recruitment short: there's always been personal economic calculus for volunteer armies.

"Will service improve my personal situation? Enough to be worth it?"

Hence why recruitment correlates with unemployment.

Nations with effective recruitment policies understood this, and typically funded it with things they had in abundance (e.g. land grants, pensions, etc).
I prefer hotels, and dislike how booking mixes in airbnb type places. I've been using google maps to find hotels and then just book directly with them.
Agree, I like to have a top level "verify" script that does all checks and have CI run exclusively and minimally that one script. Ideally the verify script is just a wrapper around a build and test command
i must be an outlier to this default. there has been enough evidence over the years that the ivy league schools are just as shady as any other school. they just have more money to make hiding things easier. with as many laps around the sun as i have now, i'm just super suspect of pretty much anything at this point.
Passkeys do not fit my use cases very well and in some cases introduce an unacceptable amount of friction. I don't plan on using them for that reason.
It's deeply dirty, in a sort of teflon get-away-with-anything way. Of course Harvard needs money to run, and has in the past accepted all manner of dubious donors, but implicitly receiving a payment quid pro quo to kill research is pretty low.
Link to source letter: https://www.sec.gov/Archives/edgar/data/1447669/000119312523...

Don't miss in there:

"We’ve decided to end-of-life (EOL) Twilio Programmable Video as a standalone product. Given it’s such a niche area and a relatively small part of our portfolio, we believe partnering with video industry leaders is the best way to ensure long-term product innovation for our customers. Removing Programmable Video from our portfolio will also allow Communications to more effectively focus on our pillar products - Messaging, Voice, and Email."
The other side of this coin is without QA, there is no app.

Sure, technically, it can be thrown out the door, and often is, in just this form, but it's a shit-tastic mess without QA time and the users are getting real tired of half-assed garbage that cost twice what the prior package cost.
You didn't answer my question. Why should it be done at universities? I get that stuff like it is already done there, but why?

Short selling has a long history. Obv people don't like them but don't know any successful lawsuits. Prob a lot easier and cheaper to capture a uni than sue some short seller.
PipeWire 1.0: Linux audio comes of age
Yep exactly - large corporations are like, 25-75% compliance keeping machines before they do anything else. They have entire departments for this kind of thing. All these companies would love to lock the best training data behind a multi-million dollar licensing fee.

Let information be free. Don't try to create artificial scarcity on digital goods though. Including art. If you want to sell your art, you are more than welcome too! But expecting a company to send you a payment because they read your publicly posted fanfiction seems likely to fail.
I briefly used Ecto when trying out Phoenix framework but have not worked enough with it to form an opinion.
You can render decorations server-side, it's just not guaranteed that the client will respect it. If you really want a Qubes-style SSD desktop, it's attainable in Wayland although it will look incredibly ugly and be highly redundant. Good luck pitching that to GNOME and KDE devs as a default.

So... I don't see how the isolation design is strange. Wayland makes sure that windows are individually isolated, and Flatpak/Bubblewrap isolates the backend and provides interaction portals. It's not a perfect solution, but it does stop your timer application from being a secret keylogger. If your biggest concern is a Trojan horse attack, it sounds to me like Wayland did what it set out to do.
That’s me too. I disliked having podcasts in otherwise perfectly OK music app, and also Spotify’s efforts to rebrand ‘podcasts’ as something else than “mp3s on RSS”. But I was a paying customer for 10+ years so they had a good run.
I think Passkeys are a great idea utterly ruined by vendors licking their chops over locking users in and creeping remote attestation.
Lots of studies about marijuana use after legalization. Many point to a reduction or no change in the use by teens.

https://www.cnn.com/2019/07/08/health/recreational-marijuana...

One could also argue that removing blackmarket sources would make it more difficult to find drugs as an adolescent, as adults are less likely to buy for teenagers.

This study seems to support that idea
https://www.newscientist.com/article/2209053-us-teens-may-be...
Location: Wisconsin, USA

Remote: Only

Willing to Relocate: No

Technologies: Backend Software Development

Resume: https://www.linkedin.com/in/victor-weinert/ (send me a message and I'll provide a pdf)

email: contact through linkedin and I'll share

I have 1.5 years of experience programming spring boot/grails, I have a lot of knowledge configuring the underlying spring framework to meet business goals.
This will greatly speed up development! Congrats
It's not an exact science and there's a grey area of course, but what I have in mind is mostly code that's just needlessly confusing in ways I think very few would disagree with. I can't really think of a specific non-trivial example at the moment, but just like natural language I do think some code can objectively "hard to follow", even if that's somewhat vague and not strictly defined.

Other factors are if I'm the primary or one of the primary maintainers, the standing of the other person (also a maintainer or one-time contributor from another team), and things like that.
Generally, it goes something like this imaginary Slack convo:

Me: I think we are getting events from SQS out of order and that’s why we are seeing some weird synchronization issues. What do you think about sending events to the regular queue and a FIFO queue at the same time and comparing them?

Team: How would that work?

Me: Since we are using a single threaded consumer here, I think we can simply override the transport class and instead of pulling from one queue per transport instance, we set up a feature flag allowing us to pull from two, compare the events and if they are different, alerting us in the logs.

Team: Sounds good!

You don’t need a full design spec, just agreement from the team on the approach. There won’t be any surprises in the review.
It’s important to remember that OP want alone. Virtually all pundits gave trump less than 25% chance of winning—most of them far less.

There are lots lessons to take from this. I’m not sure which is most important.
They also check for your being legally allowed into the UK. If you don’t have a visa, they don’t let you through.
Non-performant code is going to eventually slip into any codebase. The trick is to monitor for when performance falls to an unacceptable level. Not toss all ORMs because some minority of generated queries are problematic.

If maximum performance, 100% of the time was the end-goal, I would not be writing Python.
> What does Spotify really have?

As far as I can tell, its biggest beneficiaries are the 3 record labels who can use Spotify being one of its customers to be able to negotiate better terms with Apple/Alphabet/Amazon.
Sorry, but no. EIRP is actual power plus antenna gain; ERP is the same thing minus 3 dB.

By definition, an omni antenna has low gain. Narrow directional antennas will have high gain, resulting in higher EIRP, but would not be suitable for covering a whole city.
Very unfair generalisation.
I used to be able to "find what I need on Search" by typing it into Google and clicking on the results. This worked very well for me, but apparently not for Google.
I agree with everything you said, but I don't see how it leads the OP's formulation being silly or wrong or not useful. Here's another example (of my own) where you can pick an upper bound for `n` and base your complexity analysis around it. In this case, we're trying to provide an API guarantee that a search takes O(m+n) time despite wanting to use an O(mn) algorithm in some subset of cases. We can still meet the O(m+n) bound by reasoning that the O(mn) algorithm is only used in a finite set of cases, and thus collapses to O(1) time. Therefore, the O(m+n) time bound is preserved. And this isn't a trick either. That really is the scaling behavior of the implementation. See: https://github.com/BurntSushi/memchr/blob/ce7b8e606410f6c81a...

> If an algorithm is defined as being unscalable (fixed input), what sense does it make to describe that it scales constantly with input size?

I'll answer your question with another: in what cases does it make sense to describe the scaling behavior of an algorithm as O(1)?
When I was at UW in the dorms I felt bad for the students who came from southeast US, they’d start school like end of September, and then leave beginning of June and go back home and essentially only get the worst of western Washington weather, and miss out on what is absolutely amazing weather and sunshine in the summer months.

If we only experienced western Washington for those months hardly anyone would stay, but those summer months are so incredible it makes it worth enduring the dreary gray for a good amount of people.
Giving me memories of tag based Coldfusion days.
I'm on the other end of this in a way. I think it may come from having to read and write all day every day. Sometimes just having somebody yak at me for a few minutes is useful.

I really enjoy watching instructional videos, especially for recipes. The demo of the cooking techniques is almost always hard to write or talk about, and easy to show.

In the kitchen it works this way for me:

1. Watch the video once or twice all the way through to "learn it" and decide if it's what I want to do.

2. Put together my mise en place and basic prep for the recipe. Learning to do this was a game changer.

3. Finally, put it on my phone or tablet in my kitchen and let it play while I work, it's mostly audio at this point as I've "seen" the content a few times but I'm just listening as if the video is a coach. I'll hit pause at the major steps, and scrub back if I need a refresher on a technique or step.

I've gotten through some very complex dishes this way, and never hit the equivalent rhythm using cookbooks or recipe websites. The audio part of step 3 is really critical to me as it helps me focus on the food rather than remembering all the steps and it's just fills up the background space in my kitchen or act as a coach. The only way it would be better for me is if it automatically paused after each step and I could then ask it "what next?" or "go back two steps, I missed a step" or some other audio prompt.
One reason (as indicated by these events) is to gain influence with the administration of one of the most influential universities in the world.
The epitome of hegemony and privilege can't credibly act as an arbiter of truth, particularly in the current milieu, where it's simultaneously a bastion of The Oppressors™ and The Colonists™ as well as one of those liberal colleges indoctrinating The Children with Communism™ and/or Socialism™.

In short, few people actually care what Harvard has to say because it's popularly perceived as a mouthpiece for The Establishment.
As someone who left in 2021:

- OWNERS is absolutely a necessary and important thing, and yes it sucked when it made finding an approver hard, but the point of OWNERS was to optimize for _local_ ownership. (For non-Google folks: think CODEOWNERS files, but hierarchical/recursive, so approvers in /OWNERS, a/OWNERS, a/b/OWNERS, and a/b/c/OWNERS can approve changes anywhere in a/b/c/...)

- I joined in 2017 and it never took 18 months to get readability. If it took you 18 months, it was because you spent 2 weeks writing code in one of those languages and then didn't keep it up. I worked through the stats on this too- by the time I left in 2021, there was virtually no delay to enter the readability process for Java and it was maybe a few weeks for Python.

> There was no way to update every call site of your library in an efficient way.

Does FB have something better here?

G had sufficiently many tools for this, IMO: csearch+grep+sed for the easy changes, Refaster/clang-tidy for more complex stuff (admittedly C++ AST matchers are black magic that few people on even the C++ teams understood). Although I do wish I had known about Comby before I'd left.

Rosie - the tool for executing large-scale changes, i.e. if you made a change to 1K+ files (often 10K+ or 100K+), you needed a way to break the change up into multiple PRs - was also an absolutely critical part of this. I never found the approval process Byzantine - undocumented, perhaps, but remarkably streamlined considering that LSCs meant making simultaneous changes to code in Ads, Android, Cloud, Geo, Search, Technical Infrastructure, YouTube, or however Google breaks down the engineering these days.
I've been running my own email server for myself and a dozen or so friends since 1998. It hasn't been a problem. I had to evolve it over time and set up DKIM and DMARC. Spamassassin, greylisting, etc have helped me cut down on my incoming spam. It hasn't been a ton of work, maybe a day or two a year to deal with a new version of whatever that needs to some config changes.

I've been running my own mastodon instance for me and a few friends as well. It's been fine, we federate fine, no bans that I know of, no reports about my users. I think more smaller instances is probably better for the health of the network than a few huge instances. Especially if those instances are free to users.

Large instances need more moderation than a couple of admins can handle, I am concerned that instances like msdn.social or whatever may not be sustainable from both a 'actual costs' standpoint (bandwidth, hardware, etc) but also from a moderation standpoint.

In terms of my instance, the costs are very low, the mastodon software itself is frankly kind of painful to maintain, it's designed to run in a way that is scalable but that makes it a bit too complicated for a smaller instance..

I hope we see some more interesting experiments in moderation, tools like spamassassin for mastodon to automatically score and flag local posts for moderation review.

It's early days. I think we may just end up with what we see in email like the blackhole list. Have an instance full of nazis you refuse to moderate, your instance ends up on the list and everyone who subscribes to it will just defederate automatically.
It's easier to re-use if you need the same generated field in multiple places.
> This is a call for service providers in these dumps to move to Passkeys faster

Does it really matter? I think all of my accounts use 20char autogenerated passwords from google that are unique for each account. So if one is breached, it’s just breached. Seems to have the same protection as a passkey.
I think the common perception that investors make housing unaffordable is wrong. Investors want rent-paying tenants and have an incentive to build, maintain, and upgrade housing. Here is the abstract of a recent working paper "The Impact of Institutional Investors on Homeownership and Neighborhood Access" https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4554831

'I estimate a demand system to study the effects of institutional investors’ conversion of large fractions of owner-occupied housing into rentals in the suburbs of US cities. I find the purchases and subsequent conversions of houses resulted in a tradeoff between homeowners and renters. Institutional investors decreased the housing available for owner-occupancy by 30% of the homes they converted, and their demand shock raised the price of housing in a census PUMA by 7.4pp per 1pp of housing they purchased. Higher prices made it harder for people to buy homes. However, the institutional investors increased the supply of homes available for renter occupancy by 69% of the houses they converted, and lowered rents by 2.3pp per 1pp of housing they purchased. The increase in the supply of rental housing allowed the financially constrained to move into neighborhoods that previously had few rental units. The people who moved into institutional investor-owned homes had lower incomes, a lower likelihood of having a bachelor’s degree, were more likely to be white, came from areas with worse historic economic mobility, and came from areas with lower school test scores than others who moved into the same census tracts. The findings suggest that institutional investors made it harder for people to purchase homes, but easier for renters to access neighborhoods that previously had few rentals.'
Topic article basically shows screenshots with UI quite similar to Gerrit. It would be really great to get even a small glimpse of details from ex-googlers instead of "Critique is so much better than Gerrit".

We have a kind of big repo for a single product with multiple teams working on it. For my company I've configured a few Gerrit QoL things:

* Submit rules with different sets of required reviewers per directory.

* Keep review labels on trivial rebases.

* CI could be triggered manually by comment in a review.

* Submit requires CI verified label.

Gerrit has a nice query language to search for reviews.

On top of that Gerrit provides patch-oriented workflow backing slick review process and keeps history clean.
I think metal conduits are most useful in more industrial-ish spaces where they're exposed -- they're quite resistant to getting banged up. Schedule 80 PVC works, too, but it's harder to work with than steel (at least for an electrician with the right tools).