skysight-inc/HackerNews huggingface dataset:
I'll give you any one of 3 or 4 ideas right now, if you want them. They're ideas I'd develop if I had the time, energy and brainpower. I've got personal connections for you too, if you want them, people who need the product. I won't even ask 50%, heck, 5% sounds fine by me.

My experience has been that, while that is useful, it's by no means sufficient to lead to a complete and useful tool. But I'd absolutely take that deal any day of the week, from the "idea" side of the fence. Imagine if you did it 20 times - quite a nice portfolio.
Just put it in your git repo.
By the time a doctor paid me enough attention to realise something was wrong I had suffered a spinal cord injury whose damage can never be reversed. I’m not falling all over myself to trust chatgpt, but I got practically zero for doctors either. Nobody moved until I threatened to start sueing.
Good news then, because curl supports IMAP!
Hugo here, founder at Namespace. We built Foundation based on what we learned from building Boq at Google — the app platform that drives the dev/prod workflow of many of Google’s main apps.

We leaned heavily on composition that spans build, test and production. You can define assets that yield code-level infrastructure definitions and also are automatically configured based on environment (dev vs test vs prod).

It was great building it, and we use it to build Namespace (namespace.so); our development-focused platform.
Can the climate survive the insatiable energy demands of the AI arms race?
Hey Dana! Paird.ai sounds like a fantastic tool for boosting productivity in coding. The combination of real-time code editing, screen sharing, and live video calls makes collaboration super smooth, whether with a friend or AI. The AI-powered code generation and smart contextual code evaluations are standout features, supporting multiple languages and enhancing the workflow. Thanks for sharing it here first—I'm excited to try it out and see how it improves my coding projects. Best of luck!
Yep!

(assuming our grand-grand-grand-grand-etc-children still have something like a tzdb)
no, to me it doesnt.

to me he's right about how devs should deliver it as engineeringly sound as possible, and executives should deliver it as timely as possible.

its a balance between having a usable product and a product they need at the right time.

it's not adversarial. its a conflict yes, but a healthy one.
Wow, it seems I was not able to satisfy your sky high metaphysical expectations either. Swearing does not make you right, good day!
Ah I see. Have a look at the pricing page then: https://elevenlabs.io/pricing

Everything else they bill in characters, so that's the "currency" customers have. It works out I think as costing roughly the same per minute as generating audio.
This doesn't seem to have anything to do with a robotaxi though? I mean, it could be used in one, but it's basically "sensors detect how the car can clean itself" (which may include driving itself to a cleaning station) in many pages of lawyer speak.
> frame rate changes dramatically change the lighting needed

Can you explain this?

Each frame is a effectively a still taken at some shutter speed. Suppose you shoot at 1/1000 shutter speed and you're comparing 60 vs 120 FPS. In theory you get twice as many frames at 120 FPS, but every other frame should be identical to what you'd capture at 60 FPS (in a hypothetical world where you can position two cameras simultaneously in the same physical space).

I just don't get how changing FPS influences lighting unless you're making an assumption that FPS and shutter speed are entangled somehow. But I don't see how that fundamentally needs to be true except at the very slow end of shutter speeds.
One thing I toyed with, but didn't get very far, was to encode the HTTP/1.1 protocol as a Sans-IO state machine with .await points for the IO, but rather than the IO registering Wakers with an async runtime, it relinquished control back to the user to perform the IO manually. One can think of it as .await releasing "up" instead of "down".

In the context of HTTP/1.1 the async code became a kind of "blueprint" for how the user wants the call to behave. At the time I was dead set on making it work for no_std (non allocator) environment, and I gave up because I couldn't find a way around how to need dynamic dispatch via Box<dyn X> (needing an allocator).
it works with textbooks too though
Isn't this more a lesson of keeping your cards close to your chest?

There's a very good reason why people are on guard with pitch decks. Cause those very people you pitched could just take the idea and throw money at it.
These boxes are also great for running a k8s cluster if you want to experiment.
Scaling Synthetic Data Creation with 1B Personas
I don’t see how your 32bit float argument applies to codec specs, since you can only get a 24bit signed int from/to a codec. You’ll need a limiter to convert floats to ints either way, 24bit or not.
Show HN: ClyTimer – An Easy to Use Fullscreen Countdown Timer for Mac
Think you're funny? ChatGPT might be funnier
The ideas are important, but remember the idea guy also was to run the company. That's a ton of work, too.

In any event, while I appreciate the offer, I'm now too old and domesticated to work on it. I guess my comment should have said I'd have loved to met someone like that in my early 20s, when I had more free time and my brain worked better :).
This is the wrong framing of it, shipping is an internal mental battle, not an external one.

We are not perfectly rational automatons that always work towards our rational best interests. Shipping is hard so we create mental battles inside ourselves to avoid it and use post-hoc justifications to feel morally ok with that decision.

The choice of when to ship isn't nearly as important as the answer to why you aren't shipping on the choice you said you would ship. Yes, shipping at different points of maturity represent different sets of tradeoffs in a complex multi-dimensional matrix and it's an intellectually fascinating challenge but often, the choice is far less important than the debate that sucks it in and engineers end up bikeshedding the decision. Whenever you find yourself bikeshedding, it's important to realize you don't solve it by looking at the decision but by looking at why people feel the need to bikeshed in the first place.

You talk about how "Your job is to create great software. What's great software? The kind you'd be willing to put on your resume without feeling bad.", what is the "job to be done" by that belief for you? Is this a true, genuine held belief by you or is that here as a cover to some deeper belief that is uncomfortable to surface?

The answer is something ultimately only you can answer and no internet comment can force that deep degree of introspection, only those close to you who have a requisite degree of insight and therapeutic practice can reliably help with that. But the larger point I want to make is that the shape of the conversation around shipping is all around exploring where we feel different mental resistance around shipping at any point in time and uncovering where that resistance truly comes from vs the reasons we make up to dress it up.
It kind of depends on demand. So far I've been doing fairly small production runs to test the waters (and I'm still new to selling physical products; I'm a software engineer by day). If sales pick up, I'd love to start selling it in Europe.
> look at more granular metrics to do with just coding. The average time from the moment a developer picks up a work item to the time it gets merged (assuming code reviews happen in a timely fashion)

We do collect this data.

I personally don't put a lot of stock in these kinds of metrics because they depend far too much on the way specific teams operate.

For example perhaps Copilot helps developers understand the codebase better so they don't need to break up the tasks into such small units. Time to PR merge goes up but total coding time could easily go down.

Or perhaps Copilot works well with very small problem sizes (IMO it does) so developers start breaking the work into tiny chunks Copilot works well with. Time to PR merge goes way down but total code time for a feature stays the same.

For what it is worth I do not believe there have been any significant changes with these code level metrics either at the org level.
"It doesn’t need to be shipped to the public"

Ok, I took it by the usual meaning of ship it to the market. Not having people test it.
Manticore Search 6.3.0 is out
I agree, this is great.

Maybe some of the particular features aren't the greatest, but why can't we make things more dynamic and, god forbid, fun? I always loved compiz wobbly windows and cube.
That might be a nice improvement, but I believe people want a single command without any arguments for this use case.
People are complicated. You can have a high view of some aspects of yourself and a low view of other aspects.
Passions, feeling special, finding the special one. Do I dare suggest that identifying (or equating(!!!)) these are not just urgent issues for young mathematicians, but young people in general? Or maybe even every one?
How to Brew Delicious Coffee in a Moka Pot?
That quote doesn't seem like a very strong commitment to... Well, anything at all.

Then again, Hollywood has been screaming "No CGI" for years and that's an outright lie in many, many specific cases (looking at you, Top Gun). So color me skeptical (even if I generally do have more faith in Nintendo)
Most deadlines are made up anyway. If it doesn't happen usually nothing happens.
Negative. desktop.ini doesn't get edited when you switch (for example) from Details to List.

Also, I think only the desktop allows moving icons around freely.
No, almost certainly the other people didn't start the project because they saw his video and were so inspired by the idea they rushed off to build it. Almost certainly, it was a case of parallel evolution where they faced a similar problem and there are only so many parameters in the design space so they figured out a similar solution.

People who focus on ideas think their ideas are so inspirational and unique that they must be protected. In reality, anyone who has tried to go out actively and convince anyone else to build their "brilliant" idea quickly realizes the level of indifference and lack of engagement anyone else has to your baby.
What makes it better than simply watching it on a TV?
The author keeps ranting against CICO, even though even such results alre perfectly compatible with it. He's just burning the calories in a different way.
Another thing that is forgotten about the first iPhone: I think Apple negotiated with AT&T (?) to change the voice mail system so you could select from your iPhone (voicemail app?) which message you wanted to listen. Prior, you always needed to call the mobile provider voice mail system, then listen the messages in order (or skip them). That was a huge early selling point for the iPhone. I know -- no one cares about voice mail in 2024, but it used to be very important.
I think it's very different when you're one-man-show vs a cogwheel in organisation. In former case, just like the author mentioned, your struggle is more with yourself. You need to make yourself move forward. And "Just ship it" approach gives you that - you get external push to carry on. External user(s), external comments and demands give you that bit of energy to carry on.

In corporation setup, you always have a manager and peers that push you. You have periodic meetings with team/manager whatever to show what you have done, and then, depending on company setup, it's quality vs speed discussion. But that's very different from being all alone with your code and computer trying to build something from the grou up.
Hmm. Wasn't it completely unreliable for moving around large numbers of files at the same time? Like if file #243 of 400 failed for some reason, you could actually lose data?

I don't know any more because I use Total Commander on Windows...
I worked on bk

> The data received was SCCS, which was an understood format with existing tools.

You'd be surprised. SCCS is not broadly understood. And BK is not exactly SCCS.

I read the SourcePuller code when it was published (sp-01). It's pretty easy reading. I give Tridge credit for that. I wrote a little test, got it to checkout the wrong data with no errors reported. Issue was still there in sp-02 .
That's because folders have no size. It requires calculating children size recursively.
As others pointed out, you can do that, you can also set them in .curlrc, or you can write a script if you want to allow for multiple URLs to be downloaded in parallel (not possible with an alias), or now you can just use wcurl :)

Note: wcurl sets a bit more flags than that, it also encodes the whitespaces in the URL and does parallel downloading of multiple URLs.
That "those guys" may have seen the video he posted was just an unsubstantiated suspicion of his though. The sad part about having brilliant ideas for apps (as I have also found out, fortunately before putting a lot of effort into the idea) is that there are millions of other developers in the world, and one of them is almost guaranteed to have had the same idea a bit earlier than you. Unless it's a super niche thing, but then the market for it is also super tiny...
"Superintelligence" 10 years later
Thank you I got the names confused!
Path Dependence in Relational Design
I am not defending Shipt and there is no doubt gig workers are in a very vulnerable position. However, the data analysis results as presented in the article do not support the article's main point. "40% are getting paid at least 10% less" is not unnatural to expect whenever pay is redistributed, especially since some 30+% are getting at least 10% more. Imagine a _hypothetical_ situation where Shipt is 100% on point and driving a fairer version of the algorithm patch removing a way for workers to "optimize" for short, well paid trips, resulting in pay cuts to those who had learnt how to do it, while not changing/increasing pay for everyone else. We would see the same kind of result: some portion of workers would get paid 10% less, some 10% more. This does show that workers are paid differently for the same work they have been doing, but does not prove the change is unfair.
an added benefit of shipping early is you get a feeling for whether people are interested, before you spend a year developing a toaster that eats its own toast.
I think this might be more closely related to self-efficacy: https://en.wikipedia.org/wiki/Self-efficacy
Well, in an honest sense, that's kind of what YC's matching program does. I'm working for a company I found on there right now. It's a much different experience from job searching but it's full of people with ideas. Half or more of them are complete nonsense but any decent engineer should be able to sift the gold from the dross.
AI overtakes software, finance, and distraction industries (content generation of any kind - text, image, video, multi-modal). Distraction industries (social and regular media) are a time waster and brain frier for most humans who often consume to escape their world or decorate /fill their time.

In software the UX is the big burden AI will overcome. Not having to deal with all the typing and clicking frees up more tasks and energy for deciding what needs to be done. Brain energy.

Distraction industries, like sugar, become obviously tart when oversaturated and AI is quickly pushing that boundary. Once people realize they’ve been served a pacifier to the brain in every free minute, they will start thinking more and consuming less.

So now AI frees more human brain energy towards what is actually needed - what problems need solved for humans, not for overloaded interfaces or zombified content consumers.

Examples: Trustworthy, efficient and safe transport for kids to and from enrichment activities. Education of others on tasks that could earn them a living. A better healthcare experience, because 60% of the admin paperwork is AI automated and health workers can talk to patients instead of typing. Organizing people to do more things together to clear the social-media-generated loneliness epidemic. Making new, interactive experiences people would pay to do, especially with friends. People ask for more things to look forward to. Not more things to type. AI is a new hands-free take on UX and UI.
So, he's a fan (and paying subscriber) of his "competitor" app now, but still not enough of a fan to actually mention what app it is. Which is kind of frustrating, I read until the end of the post to see if it's mentioned, but it isn't. And it also leaves me with a nagging suspicion that the whole story may just be completely made up (or at least grossly exaggerated)...
>No. Your job is to do what the company pays you for.

Yes and no. Ultimately, your solution will live on after you. Even if theres no way for it to backfire publicly, your coworkers and future employees have to deal with it. It can absolutely ruin your reputation and cost you future employment. Admittedly its much easier for a contractor to draw a red line, but I had done this as far back as my first full time IT job, setting boundaries with the owner of that business as to what is and is not practical and achievable.
Ask HN: Dedicated hardware can 10x inference. Can we do the same with training?
Recently, we saw Etched that basically implemented transformers in verilog. Before that was Groq, which had some specialized hardware for working with tensors. Both of which can deliver 10-100x faster inference speeds than your 8xH100s.

I'm vaguely aware of the fact that training is a lot more complex than inferencing, so the fruits of further optimizing hardware are not as low hanging nor rewarding.

But nevertheless, I'm curious to hear a bit more about the details from folks that work in those fields. Is it worth it? Is it possible? What's the complexity here?
probably S4 or something
Not sure if this question is a troll but in the off chance it isn't here is a sample budget for the Australian government https://www.aph.gov.au/About_Parliament/Parliamentary_Depart.... It looks like the average revenue for a given year hovers a little under half a trillion dollars. So yeah they can afford it. The idea that "their coffers are empty and their balance sheet is negative" also indicates serious ignorance about how governments finance operations. I'd suggest you start with the country you currently live in and understand how your own government finances its operations. That will likely help you understand how Australia does it.
In my case, I was talking about technical things like data structures and IMGUI/RMGUI, which I don't think anyone feels motivated to trick others about. :)
(Who came up with R squared anyway? Seems like someone wanted to remove the possible minus sign from R but didn't know about the ABS function, so he used the square which has this side effect of making the numbers too small.)
Plenty of that software is fairly well optimized, but most software is not that optimized. Microsoft Teams, Discord, Slack, basically anything else that also uses Electron... it's not UI design, it's legitimately wasted work, and tons of it.
I’ve recently moved to Europe and found myself surrounded by hundreds of famous galleries, which are essentially the main entertainment here.

I started visiting them and looking at classical paintings, little by little googling what it was and why. It turned out to be so exciting!

Now, a year later, I can say for sure which of the women with a severed male head in their hands in the painting is Judith and which is Salome. And I understand much better how people lived in these parts before, and why they live the way they do now.

Therefore, I completely agree with the author of the article - sometimes you need to plunge into the unknown, and this unknown will reward you.

I’m afraid to imagine how many discoveries await me in museums of contemporary art.
How about instead of a market we just tax by fossil fuel usage?
Author here! I need to update this article. Years later, I actually got motivated by the comments on HN (whenever this gets posted). P

People are always like "why don't you just ship your app?" ... so I did!

I'm happy I went through with and it's way WAY better than any competitor in this category

Check it out at https://benji.so (landing page is still w.i.p)
https://archive.is/AlQJ9
Actually it is not that bad. New ideas often require a significant push so people not only get comfortable with it but also start to demand it. Having someone else bigger to do this hard work opens an actual market for it that you can now enter.

You don't need to be first or second, esp. if you're a small player. You can still win some market share over time (and it doesn't need to be small compared to what you would achieve if you would be first as the market is now bigger). Make it helpful to people who find the established solutions lacking on features or workflows that could be better.

In other words, when is it the right time to ship? With a good product, at any time. Does it matter that there are already multiple established players? Not really, you can always come up with a better version.
It's not made up, I'm not using the competitor app for years, and I didn't want to give them more attention because this space is super competitive.
Engineering is tradeoffs; the whole concept of quality only makes sense in the context of a certain budget. If an engineer takes two weeks hand-crafting some one-off charts in d3 and react that could’ve been done uglier in some BI dashboard in a day, it might look good on a résumé—but it’s shitty engineering.
I am trying to wrap my head around it, still unclear what it does l.
What tech stack are you guys using?

If you don’t mind me asking
Tick tick tick …
I was once involved in an indie game project. We had a middling idea for a crappy game but we were all hankering for software development experience in that field.

Of the 3 of us who set about coding it, 2 of us just sat down and started blocking the thing out. The third, pushed faulty code to the SVN, created a design document crediting the entire idea to himself, and then called a meeting telling us he is the game designer and he would sue us if we made the game elsewhere. The 2 of us actually contributing just looked at each other and dropped the whole thing. He basically played his cards face up and we got to see he was a pissant.

Later I did see someone with the same general idea on steam. Good for them honestly. If they came up with the idea separately, great. If they stole it from the loser, also great. If they managed to persevere under him they deserve some coin.
The alternative to considering "asians" or "germans" is probably not understanding each person's cultural background individually but rather putting everyone in a single "world" box. Which is the biggest and most useless one of all. Once you have a good understanding of a typical german you can of course zoom in and get more detail, but if you refuse to learn about germans in general then that's going to make you less understanding of both an old person from east germany and a young person from west germany, not more.
> Your job is to do what the company pays you for.

The problem with this mindset is the most companies are short-sighted and when the problems inevitably start coming in it is the developers who are placed under pressure.

It is the developer being paged at 2am on a Sunday. It is the developer working overtime to get the feature out because the codebase is a giant mess. Etc.

Having a minimum quality bar is a must. The OP was suggesting a professional level of quality - not gold plating everything.
Can I hit you up for one those in September if my current thing doesn't work out? Completely serious.
> work at FAANG, make $400K/yr

Or: work at an unnamed high frequency trading hedge fund, make $800K/yr. (The number of people on HN claiming to be this person surely exceeds the number in the Real World by ... multiples.)
If we waste resources overengineering everything, it takes resources away from other parts of society that require them.