skysight-inc/HackerNews huggingface dataset:
SEEKING WORK | AI and LLM development

If you are looking to build a product utilising ChatGPT, generative AI, LLMs etc and you're looking for technical help// advise, I can be of service! I can either give you advise, build the architecture, or code it myself, depending on what you're looking for. Some examples of what I can build

• Chatbot that answers questions from your data.

• Agent// bot that automates some workflow according to user query.

• Parse PDF or images using vision models and extract useful data.

• A lot more. Contact me if you have some idea but not sure if it can be built.

As a software developer I've worked with a lot of startups in my career, both as an employee and as a consultant. Tech stack I have experience with

• Backend development using Python, NodeJS, Golang.

• Data engineering with Apache Airflow, Debezium, etc.

• Frontend development with React, TypeScript, NextJS.

• Cloud engineering with AWS, Docker, GCP, Kubernetes.

• Blockchain development on Solana, Ethereum, etc.

• System administration on Linux, and so on.

Working with startups has also lead me to learn how to go from zero to one as fast as possible.

More recently I have been working with LLMs, OpenAI, generative AI, etc. I've been building a lot of products utilising these technologies, most recently I've founded Turbine https://useturbine.com. I've also been doing a lot of consulting work helping clients build cutting edge solutions using OpenAI APIs and similar technologies.

• LinkedIn: https://www.linkedin.com/in/summitkg/

• Website: https://sumit-ghosh.com

• Github: https://github.com/skulltech

• Email: sumit@sumit-ghosh.com

Thank you!
No - trust informs your strategy for conducting code reviews. All code should be reviewed.
The claim is not from the mpeg-la patent pool that is supposed to cover h265/hevc. It's an outside claim.

Has anyone paid Broadcom for this patent claim yet? Who? Where has this claim been made before?

This is part of what's so vicious & ugly about patents. Try as you might to avoid patents, there is a multi-decade window where some giant legion of lawyers can jump out of the bushes & make huge claims against you. Business as usual can be severely disrupted at the drip of a hat to some claim no one saw coming, with no precedent.
TFA mentions a gyroscope, but I don't see one in the assembly diagram.
Ask HN: Please Help My Brother
Hi HN,

My brother is 21 and for the last two years has been experiencing extreme back pain for which there is no diagnosis. We're located about an hour outside of NYC.

This has impacted his life very severely, to the point that I am starting to become concerned that he may be having suicidal thoughts. He's seen a couple dozen different doctors and a (big) handful of physical therapists, and he doesn't think anything they are prescribing to him is working, and he's completely disillusioned with medical care at this point, as he's continuously recommended the same treatments without a diagnosis, treatments that he feels have not been working for him, and he feels that doctors are not listening just prescribing "cookie cutter" treatments.

Of course, he's had tons of xrays, MRIs, etc..

What's the guidance? What can I possibly do and how can I get him help?
And believe, me this is a hypothetical, but what if you were offered some kind of stock option equity program. Would that do anything for you?
The application of patents and copyrights to software are identical to how they are applied in chemistry and other physical engineering disciplines -- I've worked with both. A patent covers the physical algorithm, a copyright covers the design of an implementation of the algorithm. In chemical engineering, these are licensed separately, but the patent is more important and the copyright is worth little in practice.

The algorithm is the expensive step, design of a novel implementation (a copyright) is purely mechanical and any engineer can produce this part. If there was no patent, everyone would just pay an engineer to produce a new implementation of the chemistry algorithm. This would put the inventor of the chemistry at a huge disadvantage, since the costs of producing a new copyright is the same for everyone but only the inventor would have to amortize the cost of the invention. It would be more economical to never license the copyright from the inventor in many cases.

Regardless of the mechanism, the question ultimately comes down to who is going to pay for the cost of R&D. Copyright does not answer this question either in theory or in practice.

The alternative to patents is trade secrets, which have their own issues. In areas of software that use trade secrets almost exclusively, the state-of-the-art in software is often decades ahead of academic literature and open source. The cloud has been a huge boon for software trade secrets in that it makes reverse engineering difficult. Trade secrets makes it difficult for outside people to advance the state-of-the-art because the know-how is not public and creates negative externalities in terms of employment contracts.

To address another notion, virtually no R&D is done in open source. This is an empirical observation made by many. The incentives for doing R&D in open source are very poor. There are already large gaps in technology between what is available in open source and what exists in closed source software. Again, it all comes down to who is going to pay the significant costs of R&D.
> The RTO is being entirely driven from the top by institutional investors
> The return to office has nothing to do with productivity

I agree for many big tech firms, but I'll present the other (or my personal) side.

I'm a developer. And I am looking for a job in an office, actually about to take one very soon and get out of my remote-only gig.

A lot of engineering cultures don't function well without face-to-face, high bandwidth conversation and whiteboard time.

1. Our design process has suffered greatly, specifically the process of collaborating on high-level design and consecutively lowering the conversation into a low-level design. Instead it becomes: one person writes something up, and we all read a doc with bunch of text and diagrams, add comments, owner iterates. Collaboration is serialized. When we try to get into a room and brainstorm, the limits of voice/video chat take over and we can't effectively communicate 3-4 people at a time like you can in the same room. And unfortunately my company hasn't given everyone iPads to whiteboard together, so I think you cut out an appreciable chunk of the engineering population who are primarily visual thinkers (a la 'Visual Thinking' by Temple Grandin).

2. Junior folks flounder, unable to ramp up quickly drinking through such a thin pipe of information (a lot of which is tribal and needs to be received from the mouth of others). The talented folks were going to succeed anyway and have adapted, but the average kid is isolated and out of sight of management. The senior folks love that isolation and never want to return to office. The junior folks may think it's cool, but in 5 years many more will still be junior engineers.

3. Work is more than productivity. I don't need to drink the kool-aid and take the slide down to the ball-pit, but I need daily face-to-face contact else I start to feel alienated. I wish my social life was nested in a loving community of best friends but it's not. I live in NYC, my friends are a 40 min train ride or too busy to meet up on a nightly basis (as am I). I might feel different about this if I had a partner and kids, but then I'd say anti-RTO is driven from competing priorities for a worker's time. Which is fair, but not the argument here.
I micromanager will work around that by splitting the requirements up in tiny jira tasks that cannot be ignore easily, and then follow up daily on every single task.

This completely kills initiative, tough, and may reduce the value added by each team member by 50% or more.

The only time to use such tactics is with someone who is acting in very bad faith and at risk of being fired. It can be done for a while to establish an example, while rewarding better behavior with more autonomy gradually.

If they still ignore the instructions, then that's proper grounds for firing them (even in Europe), and if they chose to leave because of it, well, that's ok too.
It replicates for millennia, it uses air to build plants, it self repairs, it contains the code for its operating system.
WWW was a simple layer over HTTP, inspired by many other existing hyper text systems.

Every great invention is just a simple addition to all the accumulated knowledge in human history up to that point.
The internal state is no bigger when hashing small things though right?

I assume most microcontrollers are unlikely to be hashing things much bigger than RAM.
> they are easily a $100B+ company once they nail down how to monetize

That would be amazing if Google, Microsoft, Amazon, or Meta sat on their hands while OpenAI got that big.
Would have been much healthier for their business to cut people before they burn their customers.
>LINEAR DIFFERENTIAL EQUATIONS WITH CONSTANT COEFFICIENTS ARE THE BOTTOM LINE

Yes! Jesus. People so often forget you can literally take variables and just fill in easy constants to get a sense of how they work. I can't believe this isn't, like, the first thing they teach in DE.
Maybe, like any system it almost certainly looks better on paper than in practice and I haven't thought about it too hard. Mostly I thought it was an interesting idea.

> They declare a high price they're happy to walk with and then continue trolling people with their patent

They can if they want but by declaring a high price they are also then obligated to pay a lot of taxes. So the system disincentivizes both under and over estimating the value of patents. It also incentivizes property going to the highest value use. So if I can do something more valuable with your patent than you are able to do (for whatever reason) I can afford to pay for it more than you can afford to pay the tax.
Is the incentive financial? Isn't this assuming you earn more?
Yes indeed. I remember a full team of old mainframers going together in a room with printed code and review it together. 500% inspections. Many pieces of code would hold for decades without major refactoring. A lot of the code being produced today is quite garbage IMO, and you can see that in the infrastructure requirements it brings with it, growing faster than our bandwidth.
Because it’s wildly obvious that bureaucracies are the organizational form of control whether you choose a capitalist, fascist or socialist or communist system, it’s been proven over and over in everything from the NHS to shareholder capitalism to communist industrialism. They all relied on metric measured bureaucracies. I mean it’s a part of basic history here that you seem to be entirely missing.

If you want a hyper explicit example it would be the cybersin project in socialist Chile.
A Nuclear Renaissance Is the Best Path Forward
They also never had sole custody and control over the weapons themselves or the tools to enable them. The weapons were in, say, Ukraine, but they were never Ukraine's.
You mean something like a CDC algorithm? I know that some Backup tools like Restic use this.

https://en.m.wikipedia.org/wiki/Rolling_hash
Having worked on both a project that used the main-only branch strategy without pull requests, and projects that use the feature branch strategy with pull requests, I prefer the feature branch with pull request strategy.

It's easier to provide feedback and make changes prior to merging. There is usually value in the feedback that improves the quality of the merged code, whether a reviewer is requesting a change to adhere to code standards (I know, enforcement should be automated), or suggesting a different way to implement the change.
Was it? Where was this idea that you owe library developers a % of your full revenue (vs. licensing costs) automatically come from? That sounds exceptionally greedy, especially since it wasn't negotiated with individual developers like most of similar contracts.
Ah looks very nice.
More stuffs to play with on weekend :D
At least they laid off the CEO that nearly managed to torpedo the entire product.
They grow very quickly. The median third and fourth primes are 42719 and 5737850066077 - see https://oeis.org/A284411 .

If p_k^* is the median kth prime then we have

log log p_k^* = k - C + O(1/sqrt(k))

where C is a constant around 0.59483; that is, p_k^* grows like exp(exp(k)). This is "Corollaire 1.2" of the paper that the post links to (https://tenenb.perso.math.cnrs.fr/PPP/p_k%28n%29.pdf). (It's in French.)
Yes, and there are theorems to that effect. There is no distinction between "software" and "hardware" in mathematics.
LLaVA-Plus: Large Language, Vision Assistants That Plug and Learn to Use Skills
> The discrimination theory you describe

This is not theory, the courts have spoken on this. that you're calling this theory tells me you both don't know and haven't checked.
That’s right. But those companies that are subject to extra world taxes are determined by why their home country is, not via international treaty.
> Most of all I get sad when I see ineffective teams with no ability or motivation to improve—whether remote or co-located.

This. I get that remote isn't always practical or effective, I do. But it's the staunch insistence on one way of working, and the denial that it needs improvement, that pisses me off so god damn much.

If I could actually get more work done in an office, of course I would go back. I have a huge backlog of shit to get through! But an hour commute isn't making that easier. And we all have been in the office where half the team is spread out just because they want to get away from noise, or to find a more comfy place, or they need heads-down time without interruptions. We've all been in meetings where 3 people are remote just because they needed to let a repair man in at noon, or their daughter's sick, or something's going on. And that is fine. So what's wrong with keeping that the same, and just not requiring people go in?

Then there's all the other dysfunctional shit that has nothing to do with an office, where the office is the excuse to never fix it. We can't figure out our online communications? No problem, just buy a big room and shove people in it and they can just walk up to each other all the time. We can't properly organize our documentation? Big room, shove people in it, walk up and ask where something is. No documentation? Big room, shove people, interrupt, ask how it works. Need to decide something but don't want to have a meeting? No problem, just interrupt 5 people at once and have an impromptu meeting. Who needs to improve their business process when they can just have people interrupt each other all day and never write a single thing down?

Remote doesn't magically work well either. You have to do specific things to make remote successful. I'm pretty sure the reason for mandatory return is just that they don't want to try. Even if half the workforce wanted to work in an office, they could buy a smaller office and let workers do what they need to do. But that would still require improvements to get the remote half to work well with the in-office half, so let's just avoid that extra work and force everyone into the office. That's easy for management, but sucks for the workforce, and the business.
Completely unreasonable that this doesn't have more votes.
Very funny; highly recommended.
The higher up somebody is, the more they prioritize speed over quality. Low level employees do not have the breadth of context that higher-ups do. The more that each level understands this about the other, the more aligned their expectations will be.
Yeah, It's not that I don't see the advantages. I wish that there was a way to get our cake and eat it too. Maybe we can dependently typed eat our way through to the other end, where while we do have monomorphization errors, having constraints on generic types feel natural and ergonomic, much more like in a system like Lean.

I think what it boils down to at the end is where you want your pain to be, pains from constantly hitting limitations and providing an escape hatch like macros, or pains from having a system that is too powerful and all the chaos that brings.

I'd rather reign in the chaos, after all we also choose to be Turing-complete, and not always terminating like Coq, but mmv.
I'd probably use a Blake too. But:

SHA256 was based on SHA1 (which is weak). BLAKE was based on ChaCha20, which was based on Salsa20 (which are both strong).

NIST/NSA have repeatedly signaled lack of confidence in SHA256: first by hastily organising the SHA3 contest in the aftermath of Wang's break of SHA1

No: SHA2 lacks the structure the SHA1 attack relies on it (SHA1 has a linear message schedule, which made it possible to work out a differential cryptanalysis attack on it).

Blake's own authors keep saying SHA2 is secure (modulo length extension), but people keep writing stuff like this. Blake3 is a good and interesting choice on the real merits! It doesn't need the elbow throw.
Yeah, MLS just assumes there is some mechanism for authorizing keys. Right now it just supports certificates and raw keys (https://www.rfc-editor.org/rfc/rfc9420.html#name-credentials) but this is extensible so you just need to add a new credential type, and there are others under consideration.
I mean, have you ever taught a class? Do you know how it feels when we make sure a topic is covered both in class and recitation with plenty of time for questions and the students still stuff it?
Well, yes. I cannot get into details, but I am pretty confident that the CEO was pressured in a similar fashion as well.
On the other hand - ask Epic. Yes, their fortnite income dwarfs everything else - but the engine is still highly profitable.
Sounds to me like you are trying to use the innards of a hash algorithm for something for which it was not designed...

Either modify the algorithm to your needs, and rename it.

Or just use something thats already suitable off-the-shelf. Plenty of merkle-trees out there.
> Yes, but the top brass are racking in tens of millions.

I agree that leadership should lead by example. However, tens of millions represent a small fraction of the > 100 million hemorrhaging that the company is reporting.
You can use a CDC algorith, but if you know that duplication mostly occurs at power-of-two boundaries, there is no need to use that. Deduplicating on a binary tree basis is sufficient.
I thing CDC is what you're looking for. Some backup tools like restic use it. See https://en.m.wikipedia.org/wiki/Rolling_hash
SEEKING WORK | India | REMOTE | React, Node

I am a front-end focused full-stack developer experienced in React, Typescript, and Node.js. I have been working as a freelancer/part-timer for the past 3 years.

My Skillset:

• Developing complete dynamic web applications using React, Node, and MongoDB.

• Designing and developing application-specific APIs using NodeJs.

• Building custom payment forms and checkout flows using Stripe Elements and the Stripe API.

Technologies I use:

Front End: HTML, CSS, JavaScript, TypeScript, Tailwind, MobX, Redux, React, React-Router

Back End: Node, Express, PostgreSQL, MongoDB, Mongoose, Bcrypt, JsonWebToken

My github: https://github.com/maverickamit

Portfolio: https://amit-ghosh.com

email: amitdgpghosh@gmail.com

Availability: Up to 40 hours per week.

Please feel free to reach me at my email for any inquiries.
Is it a recent feeling you're having? Or something old? Anyway, by the way you phrase it it seems like something you don't enjoy. I just want you to know that there are steps to get out of there. It takes some time ( Like, months for the first results and years for the really really good stuff) and big scary steps (yes, like working on yourself and adressing some situations that make you feel like shit) but it is really worth it.

If it's something old maybe you should start therapy and self-help book to reflect a bit about yourself, have a little pump and get the courage to get out there, do fun activities and proactively talk to people. If it is new you should consider recontacting old friends and maybe working a bit less. Also therapy and self-help's never bad. Well, good therapists and diversified self-help.

Good luck pal :) You'll see that even the smallest steps make you feel really better. Just do them often and you'll go far
I would appreciate the thoughtful gesture, but I would rather have 20 more minutes with my signifiant other than an umbrella. And that's the point of the article. Disrupting a work pipeline to answer an executive question might be fitting here. Sure they would have liked the answer to their question (umbrella) but they didn't want to lose 20 person hours to that question.

Good communication is key.
I've never heard these called "dingbats" even though I lived in such a building in Oakland many years ago. What I do know them as is "soft story" apartments, due to the likelihood of collapse of the living quarters over the car ports in an earthquake. (In my case, I lived in a unit that was not actually over a car port, but still would probably have suffered collateral damage.)

Seems odd the article did not mention it, here is one that does discuss dingbats and the earthquake risk they pose.

https://www.kcrw.com/news/articles/what-it-will-take-to-eart...

Edit: I see now TFA does mention soft story earthquake risk, I didn't see it beause of the web site delay in showing me the entire article.

"during earthquakes, there’s an unsettling amount of shaking, thanks to the soft-story carport construction. (That said, dingbats have seen a wave of recent retrofits with strengthened seismic codes). "
The issues you describe could all be nullified by making a simple change - The price the person can purchase your property for must be X% greater than the fair value you declare. If you set X at 10% then there is no chance for property investors in your example to flip if the price increases by 10% during the year. You could even make X dependent on market conditions - If all the housing market moves up in your area, X is increased for everyone by that amount.

I could see X being quite high. What we really want to avoid is just those situations where someone will not take any price to move, and therefore an entire railroad has to be diverted miles around because the path in one spot is blocked.