skysight-inc/HackerNews huggingface dataset:
Finding a Co Founder
Home stretch

My team is 3 people right now and we are very close to getting an MVP out, but we really need 1 more co founder with a technical background. It's in the event space, but we're not dealing with tickets or payment (but potentially in the future)

It's more of event discovery, think of it eventbrite/ticketmaster but more social.

Here's our landing page hashrsvp.com

The team
Me - product/marketing
Co-founder - product/design
Co-founder - engineering

Who do we want to meet?

You must be technical, have a passion for creating things you would love to see people use, and have insane work ethic. This is going to be hard, but the payoff is that you can build experience and potentially be financially free when we get acquired. Not sure if it's gonna be a unicorn but who knows, with proper execution it just could be. I'm happy to share more of the project if we get in touch.

If interested please send an email to infohypstock@gmail.com and include (1) something awesome you've built (2) why you would be right for this and (3) a phone number and how late I can call you.

Even if you aren't the right person, please upvote this and help us meet. Thanks for reading!
Using separate hash column for querying is nice idea.

It seems to me that some type of data might allow constant IV and still be secure.

From what I understand, it is important (in CBC mode) that the combination of key + IV + first block of plaintext is unique.

So, if key and IV are constant, but data is unique it is still secure. For example, social security number is unique and nine digits, which means it fits into 128-bit block. Using constant IV to encrypt SSN should be secure, right?

Email can also be used as unique identifier. But length of an email can exceed 16 bytes, so we don't have a guarantee that first block of plaintext will be unique (as two different emails can have equal first 16 bytes). So, it's not secure to encrypt email address with constant IV.

But if we would use a 16 bytes long hash of an unique email as an IV, there would be very low chance of (IV + first block data) collision. Probably secure enough?
I'm also trying to find some free time to contribute to some open source projects. It's not hassling but I just want to give back to the community—who gave me the career and many awesome tools already.

Getting into contributing is not easy, I have to admit. It's like you're having a second job and no one has the dedicated resources to help you understand the internal architecture. All you can do is submitting the bugs, questions, pull requests and hope for the best.
I guess the issue is that programmers work with a really big context window, and need to reason at multiple levels of abstraction depending on the problem.

A great idea to solve a problem at one level of abstraction / context might be a terrible "strategic" idea at a higher level of abstraction. This is what separates the "junior" engineers from "senior" engineers, speaking very loosely.

IDK, I'm not convinced by all that I've seen, that GPT is capable of that higher-order thinking. I fear it requires a degree of epistemology that GPT fundamentally doesn't possess as a stochastic token-guesser. It never pushes back against a request, or asks if you really intend another question by your first question. It never tries to read through your requirements to grasp the underlying problem that's prompting them.

Maybe some combination of static tools, senior caretakers and prompt hackery can get us to a solution that maintains code effectively. But I don't think you can throw out the senior caretakers, their verification involvement is really necessary. And I don't know how conducive this environment would be to developing the next generation of "senior caretakers".
That's cool, I wasn't aware of his books. I am more talking about his video content, I would love to see him do some funny videos that don't follow the mould of ZP.
Did Mayer really just spend two years professionally coding before becoming a product manager?

If true, that smells like a root cause for how bad Mayer is at running tech.
Nah, I think is a good way to keep the eras separated.
Twitter was ok, X is a shitshow.
TBH I think that, for the most part, I will only benefit from a few of these - mostly in terms of sugar. I routinely have positive experiences with Async rust and basically never have negative experiences/ issues that crop up because of it. In 3 years of writing Rust full time I had one async problem one time - I accidentally was causing an infinite select! loop in a tonic server, so the server would hang. Not really a big deal for 3 years of async work. I could have done the same thing in sync code just as easily tbh.

I also don’t think that async-drop as quite as necessary or desirable as it may seem. I really wanted it at one point and then I realized that it’s just too tricky. It reminds me of how File calls sync_all on drop but ignores the error - ultimately, “drop” is just a really tricky place for anything complex. I’d rather see a linear type, like:

struct LinearFile {
fn close(self) -> Result<File, std::io::Error> { self.sync_all(); File { inner: self.inner } }
}

Where Linear can’t be implicitly drop’d, you have to .close() it, get a File, and File can be dropped. Hand wavy and not necessarily a good implementation but hopefully this is getting the point across. This would be preferable to shoving more into a drop impl when drop is such a constrained interface.

Or maybe add a try_drop(&mut self) that will run implicity but also ? implicity. I don’t know.

I guess the point is that I’m not sure an async drop can ever be worth it.

TBH I feel like ~30% of people's complaints about async are solved by:

a) Encouraging a sync + async API in libraries

b) Adding `block_on` to the stdlib, which will help with (a)

People mostly seem to care (and imo this is stupid but whatever) about using async in sync contexts when they don't want to, and they don't seem to know that you can just block.
Not sure about developing countries like Libya decades ago, but in places like France, Germany etc. there are well-developed procedures for dealing with this sort of thing, and you should definitely contact the police if you find something like this.
Speak for yourself, I want 5G. Also, I think you're conflating 5G as a whole with the variations like low-band, mid-band, and mmWave. 5G allows carriers to have more customers in a more compact area and give speed benefits. Have you never had just random drops out in a big city or a big concert with 4G? It's enraging. 5G helps fix that problem. 5G can also help people in rural areas that have no access to high-speed internet services, something T-Mobile has been pretty good at pushing.
Can confirm. A crypto bro / lawyer invited me to learn to shoot. I hate guns but figured it was a way to spend time with him. The result is I now have noxacusis, a repetitive stress injury of the ear.

At times I've been unable to tolerate everyday noises like talking or faucets. An unstudied condition that's hugely disabling. The other person in my city with this condition lives in a closet 24/7 with earmuffs.

What's his excuse? "I'm a libertarian and I don't like when gun ranges bother me. I just want to get out there and shoot". Dumbfounding.
Excuse me? Because they installed NordPVN they are "low life wannabe warriors"? What are you even talking about?
> These apps will routinely behave like they've never seen rush hour (or any hour) of Boston traffic.

Interesting - when I pick a route it typically says something among the lines of "increased traffic at this hour".

It does indeed seem to assume that the traffic situation won't change for the duration of the trip, but I got around that by checking different departure times.
> Making it easy to search or scan for a specific change.

I'm trying to imagine the near infinite terms I would have to search for to find the commit where I "changed from a hash to a set".

Regardless, every other thing you said could also just be done in the central PR body (and thus the merge commit) and be much easier to access.

Instead of "priming the reader" it's infinitely more helpful to tell the reader why you did something, because you can't extract that from a diff.
I could argue this either way, personally.

It seems to me that we give cops extraordinary powers and it's not unreasonable to subject them to levels of scrutiny that would ordinarily be unacceptable, to guard against the abuse of those powers. Particularly since we clearly have a problem with too many cops abusing their power.

On the other hand, going to the restroom is not likely to be a place where cops abuse their power (assuming they don't have someone in custody when they do, anyway. Cops do love their loopholes.)
I'm not sure why

1. Companies say they won't raise rates, or that rates will go down
2. People believe them

Every year, employees expect raises -- at least a cost of living adjustment, and every year senior management gets huge bonuses and such.

Prices for parts and labor for repairs and upgrades will increase, if only because these costs are additive -- things will break, new tech will need supporting, etc...

The real question, IMO, is at what frequency do costs rise and by how much? Sure, I'd like to limit the amount of big money transfers to execs, but that's not really possible.
Almost an Agent: What GPTs can do
Roaming charges have nothing inherent to do with the presence or absence of 5G. You can have multiple networks with their own 5G hardware that charge roaming fees, and you can have a mixture of 4G and 5G but agreements that no roaming will be charged.

If you've got a plan that specifically limits you to 5G if you want to avoid roaming charges, then that's between you and your (likely oligopolistic) carrier.
Building specialized agents is a great way to achieve what humans do through teams and organizations. For individual developers the benefits are dubious, but for ChatGPT, it’s obvious that the end game is letting developers/people build and humans curate (through downloads, ratings, usage) the most interesting agents and then setting ChatGPT up to be grand central to use that knowledge to hire the best agent/teams for a job (or putting them against each other and presenting pros/cons).

To that end, the ease of building is key: lots of folks would be happy serving their little niche with no monetary gain (see open source software) which, for non-developers has never really been possible outside of social media posts/influencers.

Maybe it pays off, maybe it doesn’t but generally the strategy feels sound.
I've run almost exclusively Linux for the past 7ish years. First with Dell and then System76. It's been an overall very smooth experience.

I decided I wanted to get a machine with a powerful video card recently, so now I'm running an Alienware with Windows for the first time since 2005 on my primary monitor and my Linux machine on a side monitor. The only real win for Windows is that it remembers my audio/video settings with a lot of peripherals plugged in. Linux seemed to forget every few hours and Zoom meetings were a nightmare. If WSL was more consistent it would get a stronger vote, but there are weird experiences in there.
Show HN: Robocoder – GPT-4 Turbo in VS Code
You may have missed who I was replying to in the thread. The toplevel comment quotes Teflon's website talking about "cookware" in a generic sense, like heating up a pan with nothing in it is universally bad. That's bullshit. Obviously Teflon doesn't want to directly admit that it is specifically Teflon that, when heated, releases gases that will kill your birds dead. This happens at temperatures that would be no problem at all for stainless or carbon steel. That was my point. It's not the "overheating cookware" that's the problem, corporate weasel wording aside, it's specifically the Teflon that is the problem. I don't own or use any non-stick cookware.
This is a really interesting post, and it's predictable if disappointing the degree to which the comments are rehashing all of the same tired arguments about async rust.

I for one am pretty satisfied with async rust, and I'm excited for the stabilization of async-trait. I'd love to see some of the improvements discussed in this post come to fruition. Generators in particular are something I've found myself wanting on multiple occasions, because writing custom Iterators is relatively complex.

The point about return-type notation is really interesting. Once async-trait is stabilized, we'll probably go through and rip out as much usage of the `async-trait` macro as possible, so I'll be curious to see how often we run into the issue described there. I also really like the idea highlighted in the blog post of adding async sugar to function closure types as part of expanding the support for async closures, e.g.:

where F: async FnOnce() -> T
// rather than
where F: FnOnce() -> impl Future<Output=T>

Personally, the lack of good support for async in closures remains one of my only issues with async, just because we often write code in a more "functional" style, and whenever we're dealing with complex async stuff we often wind up having to drop out of that.
Sometimes, because I don't understand chip design, I wonder why we can't simply make 5nm MOS 6502 or similar chips. Technically I suppose we could design a modern CPU with the 6502 or Z80 instruction sets, but would they be of any use? They should be absolutely tiny and use virtually no power, but would they be compatible with anything?
Gives me Seoul vibes.
It's the VC wheel. You buy a successful outfit. Saddle it with the acquisition debt. It's no longer profitable because of debt service. You need more revenue in a thin margin business. You start alienating users and dumping unrealistic expectations on employees. Company goes boom or dies like a wet fart.

I mean it was purchased by a company that unironically calls itself Gamurs Group.
I have to admit that async syntax has a certain charm, as it has deep connections to iterators. (I have to program with Unity for my master thesis). But Structured Concurrency leverages well-known blocking syntax that doesn't require further explanation. It's not even specific to virtual threads.
I would love it if some of the other old-timers could make it back. I assume the people I really liked, Steven, Jason, Kirk, Maddy and of course Fahey, since he no longer is with us, are very unlikely to come back. I also miss their Japan pop-culture reporting from Richard Eisenbeis and Bashcraft. The latter was a big part of what made me visit kotaku instead of Destructoid or Polygon.
A big difference between Rust and other languages like Dart is that our async/await is based on the same sort of coroutine transform as generators would be, rather than continuations, so its a lot less additional complexity to add generators compared to another language that has both async/await based on continuations and generators based on coroutines.
Biden's Elusive AI Whisperer Finally Goes on the Record
Thank you for the recommend. Given where I now am, I don't believe that I need this. But it is a resource I will likely forward to others.
For what it's worth: thanks to Dart's async/await and async* and sync* , I find it incredibly easy to write performant, clean concurrent code in Dart. I've implemented an application (very IO heavy, highly concurrent) that is half Dart, half Java (for reasons) and the async code in Java is atrocious, while the Dart code is just beautiful.
Radar Labs | Software Engineers (infra, platform, data, full-stack, mobile) | ONSITE in New York City | Full Time
https://radar.com Radar Labs is a location infrastructure SaaS platform.

Over the past year Radar has been used from 100M+ devices doing 10,000 qps.

WE are are a small but mighty engineering team (10 engineers!). We're based across the US, with an HQ in NYC in Union Square.

There's a ton of opportunity to make an impact and work on a variety of things, as we're a pretty fluid team:

- Infrastructure (e.g. Grow our footprint from multi-AZ to multi-region in AWS using Terraform CDK, MongoDB Atlas and others)

- Platform (e.g. Build out abstractions for our product engineers to ingest and compute geo queries at high-scale)

- Data (e.g. Process, deduplicate, and evaluate 10s of millions of POIs from a variety of vendors and open data)

- Mobile (e.g. building a control system that automatically configures optimizing battery-life and location accuracy for different use-cases over time)

- Product (e.g. build tools to visualize and debug location data at scale)

Check out our jobs page here: https://radar.com/jobs

If you have any questions, feel free to reply here or you can e-mail me at tim@radar.com
> Not sure why this is news outside of the Twitter-techno-pseudo-academic-influencer bubble.

The paper is making the rounds despite being a weak result because it confirms what people want, for non-technical reasons, to be true. You see this kind of thing all the time in other fields: for decades, the media has elevated p-hacked psychology studies on three undergrads into the canon of pop psychology because these studies provide a fig leaf of objective backing for pre-determined conclusions
where the hell are you eating for 66 bucks?

hell, i'm in Canada in a big city with high COL and my quick in-and-out breakfast on Saturday was 15 bucks for a brekke and 3 for coffee. even with a tip i'm just over $20 for pancakes, bacon, and a couple of refils of diner coffee.

are you paying for the table of 4?
> Jurors cannot be tried for their findings.

True, but not the issue here.

> A juror is free to infer that you are guilty when you plead the fifth,

No, they aren't, which is why:

(1) If the trial judge decides before the case goes to the jury that a reasonable jury could not convict the defendant without making such a prohibited inference, the judge can dismiss the case, either in response to a defense motion or on their own, without even sending it to the jury,

(2) If the trial judge makes the same determination after the jury returns a conviction, the judge can toss the verdict and and acquit the defendant (which they could not do with a jury acquittal), and

(3) If an appeals court reaches the same decision after the trial judge has accepted the jury verdict and entered a conviction, the appeals court can reverse the conviction (which they could not do for an acquittal.)

Criminal acquittals are a constitutional special case of jury freedom in the US, as a special protection against imposition of criminal punishment by the government. The freedom juries have to ignore the law and facts and acquit because they feel like it in criminal cases is neither symmetrically reflected in a similar freedom to criminally convict, nor manifest, in either direction, in civil cases.
This is a terrible idea, because criminals would immediately start intentionally breaking officers' body cams.
Western machine tools eade sanctions to fuel China's nuclear program
Having written an async library (as in, the non-blocking stuff and state, that to the caller looks like async)... Understanding it isn't the easiest.
To sell them to management I just call them time wasting prevention measures.
I thought he was pretty solid in "Extra Punctuation". It was a nice change of pace to hear him gush about Undertale or muse about narrative in games instead of his usual routine.
Why do you run benchmarks on such small datasets? It is very hard to judge performance..
>This is where the final rebase comes in—you should be combining all the small commits into one.

Sorry, but I'm a software engineer, not a git engineer, and the less I have to do with git, the better. KISS applies to git, too. A simple thing like not creating a commit for every stupid thing keeps the history clean, doesn't bog down the developer by requiring to think about writing a commit message every 2 minutes, and keeps git simple.

>Most of my commits when I'm working like this are named "draft". The names don't matter when you're going to redo the history later.

But then what value have you added by naming everything "draft" and creating a commit? There is no value in doing this.

>You've never started down one path for solving a subproblem only to realize 30 minutes in that it's not going to work?

Sure I have, but I don't need to enter it into the git logs. I'll either start over in a clone of the repo if I want to save the bad work for whatever reason (which is very unlikely), or I'll just stash the work, or whatever. The thing I don't need to do is commit the bad work.
You legit don't understand the need to placate Wall Street and institutional investors??
That doesn't help distinguish him from every other joker in crypto.
The ability for hacker news commenters to grossly over-simplify and misrepresent things like this is unparalleled. Just like it takes all folks to make a village, it also takes those folks to do some missions that police forces have. The problem is when the culture of a police force is all of one type. There, however, is value in having people appear strong to those who would take advantage if weakness is detected. Today's punisher skull is yesteryear's ceremonial armor and masks.
Tumblr could have been a great purchase and kept Yahoo relevant today but they ruined it, and I mean with multiple compounding changes not just the explicit content ban.
you can also use YCombinator founder matching
Bankruptcy is nothing to be ashamed about although it's preferable to avoid it.

The world changes a lot and it's trivial to get caught in situations where it is unavoidable.

Bankruptcy provides a legal way to force some restructuring to hopefully save the company.
Seeing like a bank
Like this? https://en.wikipedia.org/wiki/Trap_street
You can remap everything in emacs (see evil-mode, vim for emacs) so you’re not tied to the ctrl-meta nightmare. There are vim plugins too, but not as integrated.

You can also uses a normal editor and copy-paste to the REPL.
I get hit by this constantly: https://github.com/systemd/systemd/issues/2460
Because why not experiment if others get shit when it goes bad? I'd do it too...
AT&T was blocked from buying T-Mobile, not Sprint.

https://en.wikipedia.org/wiki/Attempted_purchase_of_T-Mobile...
> it’s worth pointing out it’s not yet possible to leave a user review for Modern Warfare 3 (2023) on either Metacritic or Steam, since the game has yet to launch fully.

PR Dept: "the reaction is so negative we gotta get 'look how silly those people who don't like us are' counter spin out right now."
Even that word sounds like something a manager who's compensating for not actually doing anything besides attending meetings would say.
Yeah it's a very common generalisation. Modern researchers all think the same thing, people in the past used to think something different.

"The days of old have turned to dust" as it says in the Epic of Gilgamesh (ie one of the earliest surviving works of literature includes a moan than things are not as good as they used to be).
I ignore them. If a technique is useful enough, it will become mainstream and won't need to be advertised by a small community of apostles on X or Mastodon.

I work as a junior programmer/sysadmin. Most of the work I do has centered around being aware of the abstract logical nature of the problems I solve. Thus, I have had little issues solving a routing policy in IOS, JunOS, OpenBSD or plain old Linux, for example. Or writing some WSGI application to interface with an old water meter. Or fixing a broken Ubuntu 12 webserver that no-one has accessed in years.

Considering the comments on another topic on HN today, It still looks like GPTs have great issues with abstraction, which I personally experienced when I asked it to fix some issue I've been having regarding data structures I've been using in a project. So I don't think I'll be running out of things to do so soon.