skysight-inc/HackerNews huggingface dataset:
I had a lot of fun writing low latency parsers for various message standards C++. There are a lot of fun things you can do when you can take ownership of the read buffer and you can figure out how to parse in-situ (modifying the data in place as you move along)
>The richer oxygenation of the Earth's atmosphere in a previous geological era favoured the development of very large insects. Some wingspans attained 70cm!

This makes me wonder: what did these insects taste like?

Notice that humans already eat several animals that are basically very large insects: shrimp/prawns, crabs, and lobsters. According to a quick google search, these crustaceans are basically a sister group to insects, and interestingly are more closely related to insects than spiders are.

However, humans generally don't think of insects as appetizing meals, to put it mildly, while lobsters are considered a delicacy, and shrimp, crabs, and other crustaceans are not only commonly eaten, but are somewhat expensive food items.

Of course, one of the big differences between insects and these crustaceans is the size: even small shrimp are very large compared to just about any insect, so most people generally don't eat the shell, but only the fleshy insides. This is even more true with lobsters, where the shell is very thick and hard and inedible. Doing this with a beetle or grasshopper isn't so easy.

So if prehistoric insects could be so large, did they resemble sea crustaceans more (as far as having thicker shells, and more easily-separated meat)? And would humans find them tasty if we could somehow resurrect these giant insects today?
I'm not going to tell you outright not to do it. It sounds fun, and SF is a good location to be in tech right now. However, there are some major red flags around you quitting your job, moving to one of the most expensive locales in the world, for an unpaid role.

* Be prepared for a potentially lengthy period of employment. The market is not what it once was, especially early in your career, and interview cycles are long.

* Consider that startup founders in SF have a high appetite for risk, may be very charismatic and persuasive, and ultimately will bear none of the consequences if this doesn't work out well for you. Sadly, founders can be exploitative too, and asking you to move to SF to work for free sounds exploitative.

* There are a lot of good options out there! Speaking as someone who broke into the SF tech scene after starting my career outside of it, the first few companies/job offers are going to sound unbelievably amazing. That's because they are sales pitches, sold to you by professional salespeople. Over time, once you have seen some of those promises fail to work out, you may view the sales pitches with skepticism. There are going to be more amazing opportunities, and some of them will pay.

Having said all that: I once quit my job and spent down my savings to work on a passion project. And I once left my hometown and set sail for SF, too (although I was paid for that.) Ultimately, if you have a good social safety net and good skills, you will probably be alright, even if you do something a little bit wild like this.
Age against the machine: susceptibility of LLMs to cognitive impairment
I know I moved into the LCD monitor era kicking and screaming because the CRTs I used with my computers were far superior for text sharpness and didn't cause me near the eye-strain when doing long programming sessions.
By "legitimate" I mean artists who create original, creative works and contribute to the cultural and artistic ecosystem, as opposed to anonymous, mass-generated content that seems designed primarily to exploit platform algorithms
Long time sublime user, always has autocomplete off as it’s more a distraction than use. Recently started using LSPs for the inline error/warning checking but avoid things like go to definition - search works just as well in my experience and is faster.

See lots of comments here about code organisation and developing a deeper understanding of a codebase and I could not agree more. At least for myself not having all these functions gives me a deeper understanding of the code. I’m probably slower to onboard onto a codebase but I bet long term have higher productivity on it.
Of course I agree that code should be organized logically, but I wonder if you could expand on what you mean. Do you drill down into finer and finer directories of detail, code units, classes and functions?

I work with someone that navigates the tree structure of all our directories every time they need to look for something. It is painfully slow to watch and if you ask me, they produce fairly spaghetti architecture. Some of that could be a lack of familiarity with the idioms of our platform and its available SDKs.

But I ⌘ click all the time as well as quick-open right to the class, variable or function I need to work with, and I feel like I still organize things better. I’m constantly fixing the weirdness and proposing even more things that should be improved.

You might even get a bit of a Conway’s Law effect by committing unnecessarily to a specific, onerous work style.
As many others I do use fd/rg/ctags, custom scripts, some even Perl ones; Today I’m on Kakoune but had plenty of Emacs integrations when it was my daily driver (Kakoune taught me to pipe selection through a script that echoes code fragment which works in most editors, e.g.: `|gosnip_if_err_panic.pl` with `responseErr` selected).

I think that the reasons I’m not using IDEs/LSP are more worthy sharing:

First one is that I cannot use one. While the main language I’m using has relatively ok LSP, the codebase prevents usage - as it’s ridden with circular dependencies, macros, module aliasing and multi dispatch cast chains. Everything outside of syntax highlight it unusable.

Second: I noticed that assisted coding is like GPS assisted driving. I stopped internally understanding architecture of the code when using IDEs, this disconnected my mind from the code and at some point it started to feel like shoveling. Mindlessly spit out the code at let IDE handle the rest. That made me efficient at local change but unable to build up and see „big picture”. It bothered me to the point I decided to not use them anymore.

The third thing is that I don’t take „no” (coming from software) for an answer. I often get those specific needs for code search/refactorings that IDEs/LSPs refuse to work with. E.g. I need to search customized OpenAPI specifications and link it to a macros/generated code for browsing. IDEs/LSPs cannot help as it’s not idiomatic, so I customize. And customization is a loop. You customize, you learn how to customize better, you customize more etc.

When it comes to LLM-based aids I’m at point of minimum trust. I’ve experienced so many problems
with that code that I rather just disable it entirely. Example? I was setting up Ticker based waiters for Go and then in one place I accepted `time.NewTimer` local-LLM snippet instead of `time.NewTicker` in infinite loop. It was 4 lines of code and looked VERY similar as in 3 functions above (that was before code reduction phase). For those unfamiliar: Go’s ticker ticks every N time. Timer fires once. One-shot-fire in infinite loop == lock. Took 4 hours to debug.

I’m not against using LSP/IDEs. They have their use (but for Pete’s sake ask your organization leaders before feeding proprietary code into ChatGPT). They don’t work for me, I feel dumber. Maybe I’d be more efficient but I don’t care. I do this job also for fun, and GPS kills the fun part for me.
There’s a rich diversity of musicians beyond the traditional "recording artist" mold. My concern is less about sticking to the established industry model and more about ensuring platforms support creators whose work reflects genuine artistic effort and expression
The problem is that the specs of AMD consumer-grade GPUs do not translate to computer performance when you try and chain more than one together.

I have 7 NVidia 4090s under my desk happily chugging along on week long training runs. I once managed to get a Radeon VII to run for six hours without shitting itself.
> it never really occurs to us to use them, just like it never occurs to you to not use them.

This doesn't really make sense, either. How do you not consider the right tool for the job? Do you just use whatever you learned to code and never really bothered to consider that you might be more or less productive with different tools? LSPs don't always offer a productivity increase in all contexts—they seem to be mostly useless for dynamic languages like ruby and lisp and javascript—but I have a hard time imagining a programmer that couldn't benefit from them in the right context.

And they're just a straight-up improvement from iterative compilation and ctags, the latter of which never really worked very well in the first place.
I mean, if you consider what critics don't like to be bad, then yes, critics being ignored would be a bad thing for what gets produced. My point is that what critics think is bad is entirely subjective and not everyone will agree with them. If you start from thinking of critics as "on top", then sure, you'll end up with a race to the bottom without them, but if you think of critics having their own potential motives and their opinions not being some gold standard of what constitutes "good art", then it's not so obvious. Using TFA as an example, is it more likely that first and third albums are actually objectively better more often than not than second albums, and what everyone else thinks is actually wrong, or is it more likely that the critics have a distorted view on things?

> I expect an (ironically academic) argument about how monomaniacal focus on mass-market appeal doesn't necessarily entail a race to the bottom.

If the above sounds too academic and pedantically rejecting the idea of mass-market appeal entailing a race to the bottom, let's turn the question around: why are you assuming that the only two options focusing on mass-market appeal or focusing on what critics think? Do you really think that there wouldn't be any music produced for a niche audience if not for critics? There's plenty of existing music that isn't produced for mass market appeal already, and I have trouble believing that it exists only because of critics rather than in spite of them.
does the US consume a lot more plastic than elsewhere?
I’d compare this to large format film cameras. By raw resolution, large format film cameras are still far and above what is achievable digitally. Yet, of course, no one would argue that they pose a threat to the practicality and efficiency of digital, and few people appreciate/care about/need so much resolution.
Here and on Reddit
What ever happened to that project to build automated mosquito laser zappers? Didn't Bill Gates's foundation have a project to do this, by tracking them based on their wing-flapping frequency (which apparently is very particular to that species of mosquito) and then burning their wings off with a precisely targeted laser? This seems like a nice, pesticide-free way of eliminating these awful things.
Are there any introductions for eos written for nix users? Because having skimmed over this, this seems like it requires prior knowledge of whatever eos is
If you have a strong network of support for housing and/or returning/new health issues, there’s nothing wrong with taking advantage of that to pursue your passion while you’re young. That being said: In other industries, this is known as “being paid in exposure”. It rarely translates into real monetary value, and it’s usually a sign that your client/startup would like you to work for free. Your time is worth more than you think. So by all means go for it if it seems exciting, but if any any point it doesn’t pass the vibe check, walk out sooner rather than later. You can get exposure to robotics elsewhere.
Tim Peters returns to the Python community
> Also wild that any single individual can own that much (and some a lot more!)

Nobody owns a billion dollars except governments.

"Billionaires" usually have ownership of business interests that could theoretically be sold for a billion dollars, but that they generally do not want to sell (because they would rather own and often run the business.).
I use make on windows under WSL. I've mostly given up on getting everything to run under every OS. There's always some quirk.
I think employers, already prone to looking askance at resume gaps, might be particularly put off by that (no counter example of long commitment, no way to brush it off as a better offer or need to move). I personally wouldn't risk it until I had four or five years at one company but others may have more confidence.

You might be able to get extended unpaid time off without leaving. My team has an unofficial policy that you can take up to about a month unpaid (not every year).
What was the original business model that Honey had? I only know of the current Honey approach, inserting themselves into the checkout page, did Honey work differently before? More like a coupon search engine? That’s the only way I can imagine “first click” makes sense.
Maybe because it’s written with a LLM
Why does it block it and not the adjacent area?
What’s interesting (and ironic) here is how that formula is being industrialized to an extreme in the case of platforms like Spotify
I've done it before to integrate rust into polyglot build systems. There's a surprisingly long history of build systems trying and failing to implement rust builds without the "happy path" of simply wrapping cargo. As far as I know no one's ever succeeded.
Same reason why datasheets are still PDFs. It's a reliable, long lasting and portable format. And while it's kind of ridiculous that we are basically emulating paper, no other format fills that niche.

It's the niche HTML should be able to fill, since that was its original purpose, but isn't, since all focus over the last 20 or so years has been on everything else, but making HTML a better format for information exchange.

Trivial things like bundling up a complex HTML document into a single file don't have standard solutions. Cookies stop working when you are dealing with file:// URLs and a lot of other really basic stuff just doesn't work or doesn't exist. Instead you get offshot formats like ePUB that are mostly HTML, but not actually supported by most browser.
> It's that AI makes developers so much more productive that you only need a subset of them to meet your work requirements.

my experience so far is that it takes away the upfront thinking and leads to a mess of code that I then have to sit down with them and try to work through.
For FRP do you mean https://github.com/fatedier/frp?
My great-grandmother never used a mixer when making cakes or bread, long after mixers were available, and she was able to pump out treats and full meals without batting an eye, the best anyone ever had.

I don't have a problem with my "productivity", whatever that means. I'm not trying to write code faster, my own experience is that writing code faster leads to shitter code. I'm not hindered by my tools, and most of my programming time is spent thinking and understanding, and none of these tools have afforded me better thinking or understanding, and often times they get in the way of my thinking.
Haskell even on a bad day is radically more sane then all of these languages doing this bizarre obsession with foo.bar() instead of bar(foo), because they only allow overloading on the first arg. semantic indenting. type inference. automatic laziness. it's just another level.
> Do whatever you want.

Of course. Having said that you have to take a look around and decide if the conditions are remotely in your favor, right now, and when/if things don't pane out in 6-12 months. The economy (not the stock market) isn't great, finding another job without much experience in the current state of the tech industry might look even more bleak. I graduated right after the dot com bubble burst. I took the calls from recruiters offering me sign-on bonuses and other crazy stuff during the bubble - I declined and chose to finish school instead. A year later after graduating I moved to Boston and heard first-hand accounts of developers driving cabs to make ends meet when things imploded.

It's one thing to take a high risk / high reward chance, but swapping a steady good-paying job for effectively an unspecified unpaid role doesn't seem like that. If he's willing to work unpaid, he's more likely to get a low-ball offer if/when the company decides to employ him.
I've done it 7 years ago and don't regret it all. I was in my early 30s, had my own place to stay and no family, so it was easy, but you can do it no matter what as long as you have savings.

I spent that time working on a "startup" with friends, but we have quickly realized that we had no sale skills whatsoever and were just building an app for fun. It helped me to learn frontend programming, so it wasn't a wasted time. After that, when I finally decided to look for a job, I found one with a much better compensation than before, but that was a given considering I moved back from Asia to Europe.

Now with our project at work coming to an end, I'm thinking it's a great time to do it again. Everyone complains about the job market not being as hot as it was before, so it make sense to take some time off to stay with family, do some sports, gather thoughts and later prepare for interviews, learn new skills and maybe jump onto the AI train. The SE work may change a lot in the following years and it is a good idea to prepare for it well. I have a feeling I will need to learn more about math, ML, systems design and devops to stay in the game.
It's quirky, but you can sort of fake dependencies on tools in make too.
Everything that was taken from C++, and _Generic.

And the ongoing discussion for lambdas that didn't make it into C23, but still on the table for C2y.

Meanwhile, zero progress in what actually matters, proper strings and arrays, that aren't a continuous source of memory corruption bugs.
A complete stranger who has nothing whatsoever to do with you, who has never tried to do anything for you, nor has been expected to, has never disappointed you. They've also never failed to disappoint you, because they have not failed in any regard whatsoever.

This is an example of a vacuous truth.

I've never failed an airliner landing. While that may sound like I'm boasting of being a good pilot, in fact I'm not a pilot at all, and I've never attempted such a thing.

Another vacuous truth.

Every crow in an empty set of crows is white.

Also, every crow in an empty set of crows is black.

Propositions universally quantified over an empty set are all vacuously true.

Statements with always and never are universally quantified over some set of events. If that set is empty it leads to vacuous truths.

"Every time I've seen a crow, it has always been white" is vacuously true if I've never seen a crow. I.e. the set of crows I've seen is empty, and consequently is a true statement that they're all white.
A few years back I left one of the FAANG companies after the first two covid years and had no job lined up for about 9 months.

I spent the first 3-4 months learning swift, iOS development, and hacking on an app project. It was probably some of the most fun I've had in a while simply because I wasn't locked into product decisions, timelines, or other requirements.

But of course it depends on finances and how easy it is for you to rejoin the industry. Fortunately I got my current job just as all the layoffs and hiring freezes began. Not sure what would've happened if not for that.
Ask HN: What projects are you hacking on this week for fun?
I always try to use the end of the year to tinker with libraries or projects I've been meaning to get to. This year, i'm hacking on an app for a pair of ar glasses (the even g1) that i recently started wearing. Would be fun to hear what else folks here are hacking on
People use what is available. If your only option is a shitty bus that comes delayed every 90 minutes, you will use it. It still does not make it an optimal option.

From supply chains we learned 1 thing. Multi-modal is the way. Have dirt cheap, high capacity main modes and have more expensive but more flexible last mile options.

So in public transportation this means few high capacity train lines, and at the stations mini-vans / cars, e-bikes, evtols to do the last mile, from/to the origin/destination door. You can do this because you can rely on the train schedule.

You cannot rely on the bus schedule.
I use partial autocomplete. Emacs has the universal autocomplete that's not language specific but gets it right often. I do use LSP on languages that have support. For languages that don't have good LSP support, just search. Emacs has great project wide search.
The problems in poor communication in development team
> I work with someone that navigates the tree structure of all our directories every time they need to look for something

Counter example: I’m working with LSP dragging codebase where basic code lint takes 45s. My colleague takes a break after each change so that their code navigation starts working again.

Inefficient people are inefficient.

Not using LSPs isn’t guarantee of efficiency just as using LSP isn’t one. Different strokes for different folks - one has to accept consequences though (more automation means less presence, but it’s everyone’s own choice to make).
They're trying to unseat Radeon as the budget card. That means making a more enticing offer than AMD for a temporary period of time.
If they cared about control, they wouldn't depend on Windows ecosystem, rather foster GNU/Linux native games.

Everyone is quite curious what Microsoft will drop at CES 2025, and which OEMs will be on their side, it is going to be netbooks all over again.
DNA sequencing (Nanopore sequencing)
What are some of the biggest challenges you face in the productivity space? We already have major players like Todoist, TickTick, Asana, Microsoft To Do, and countless others, so the tools for task management are widely available. Time-tracking apps like Toggl Track offer robust solutions, and AI-powered scheduling tools are emerging to optimize calendar management.

With so many options already on the market, it can feel like there’s nothing new to invent in productivity. But how is productivity really going for you? What tools or solutions do you wish existed that don’t currently?

As a builder with access to tools and resources, I’m eager to connect with others and understand the core challenges they face in staying productive. Are these challenges something software can address, or are they rooted more in behavioral changes?

I’d love to dive deeper into this topic. It seems like there’s a stigma around creating yet another to-do list app, but there’s still room for innovation if we focus on real pain points. What are the obstacles—whether daily or related to your bigger life goals—that, if solved, could help you be more productive?
I will only consider AMD GPUs for LLM when I can easily make my AMD GPU available within WSL and Docker on Windows.

For now, it is as if AMD does not exist in this field for me.
Interesting! I can see it in two ways: (1) as elongated U-shaped ellipsis that rotates sideways and (2) as bent lemniscate that rotates vertically.
I know about VSCode's terminal, and the few times I've used it seems like an afterthought, bolted on, to the primary function of the program as an editor and file navigator. I don't live in the editor. I live in the shell. The editor is a sub function of living in the shell.
In Java, not having something that automatically inserts imports would be incredibly counter productive. I feel that this is easier in other languages, where you don't need to manually import almost every 'jdk' class that you use.
That's pretty damn impressive! How did you manage to avoid codebases with CMake? Or are you just saying you personally chose not to use it for your own?