skysight-inc/HackerNews huggingface dataset:
Looks cool! One piece of feedback I have is that I personally wouldn't want to autocomplete prompts as shown in the image you have there. I'd want something that "fixes" my prompts so that they're understood by the model. Like say if I put "Afro-Asian samurai carrying two swords in a cyberpunk environment", for it to say how I could re-word it to generate something closer to what I actually want.
Senior developers usually don't know any DevOps. CRDs, Operators etc are too advanced. And DevOps people keep inventing new words.
Just put everything in queues, even immediate things.

The AI feeds the action queues, and another isolated component performs the actions, including delays and follow ups.
$350k paid in Ethereum transaction fee. Transaction failed. Fee gone
The software (firmware) is great but the community especially over on Discord leaves a lot to be desired. They have this sanctimonious holier-than-thou attitude towards beginners and anyone dared to question their approach. Check out Thomas Sanladerer's saga with them, it's quite eye-opening.
While you probably do need to expect to delete usernames (usernames are expected to be identifying), but the user sneaking personal data into fields where it isn't expect is probably out of scope as not part of a filing system anyway. Certainly I wouldn't expect a serious problem to punt it to "we'll deal with it manually on a 3-month turnaround if it becomes relevant" as long as you're not actively designing your systems to not be able to delete data.
In industry we just call those junior and senior employees.
Maybe, but to me the whole reading list thing just added to a feeling that I didn't want to work at a company that approached hiring that way, whether or not it was actually necessary to read them.

I'm senior enough that I don't need to deal with that bullshit to get a well paying job, so in not trying to sell me on why I should want to work for them but instead giving me junior level "homework" they made me mentally raise the bar for how much money it'd take to make it worthwhile quite substantially.

Maybe they don't want people like me, and that's fine if that's an intentional choice on their behalf and not an effect of failing to realise that it's pushing away the most experienced candidates who have other options first.

Add to the fact that I was hesitant to even consider Facebook to start with and it was easy to pass on it.
agree with this. If done well, then this has all sorts of secondary benefits.
better engineered systems, more agility through implicit fire breaks, stronger devops processes, faster backups etc.

I don't think GDPR should have been enforced on existing systems as in many cases it became a tick box exercise.
Best practice and certification for new development would have made more sense.
I agree, we must eliminate them
Education + Roaming [0]
=
Edu + roam
=
Eduroam

[0]
https://en.m.wikipedia.org/wiki/Roaming
Don't pretend this is a victimless crime. He was tricked into wasting his time due to false advertising, and honest dealers who advertise the full price lose customers to fraudsters.
It is really important to be compatible with MySQL, which can greatly reduce resistance to adoption.

I miss the old days when everything gets into MySQL (even small images! Because backing up and restoring MySQL is easier than dealing with lots of small files)

When I am asked to set up a "BI", most of the time it is just a fancy word for "SQL Visualization". Being able to use the same language (SQL) throughout the whole pipeline is great. The boundary between OLAP & OLTP is kind of unclear. I like how TiDB's way of seeing it.
Java got type inference? I need to see this!

Is it still really verbose with lots of too small classes?

Edit

https://www.javatpoint.com/java-8-type-inference

Wow that's pretty cool.

More? Less? Interesting is just how far I checked out of that language years ago.
The hacker is somehow siphoning the gas to a miner that they also own.
Terraform only for me, have not experienced anything better.
Reminds me of a company I used to work at which took a similar approach. We used one file per person policy, each developer had their own file that contained functionality developed by them, named like firstName_lastName.ext - everyone owned their file so we didn't have to worry about merge conflicts.
Vulkans ease of use is an explicity non-goal I think - it's benefit comes from exposing the maximally flexible set of APIs to control the underlying GPU hardware, which is in direct opposition of a simple "hello world".

The idea is that you use high-level APIs built on top of Vulkan (usually engines like Unity, Unreal or Godot) that then leverage the underlying hardware.
> I've had multiple legal teams tell me that once they pay for something you need to keep everything. It's required to be able to mount a legal defence incase they want to do chargebacks.

Chargebacks are only actionable within a few months at most, so you could need to keep data during that period, but that would be short enough.

The GDPR requires for instance that you delete information from users that are inactive for a set of years (3 years ?). You wouldn't refuse to apply that on chargeback reasons for instance.
These are technical controls - are you sure they're the right ones for your organisation - - or even needed? Organisations that comply with the GDPR typically employ a data protection officer - the person responsible for creating or overseeing the creation and ongoing maintenance of a privacy impact assessment. That feeds into requirements long before any code is written, let alone implementing other procedural or technical controls.
That's categorically untrue. Diesel-electric trains are not uncommon, but there are many, many trains driven directly mechanically or hydraulically by the diesel engines.

Nearly rode on one these just yesterday:
https://en.m.wikipedia.org/wiki/British_Rail_Class_150
the problem is that most people/orgs don't think this way, they still think their solution is scalable and easy to start (like RoR) and no one optimizes for deletion so eventually you are stuck with all those initial choices until you spend a lot of money to overcome them (literally in every company i have worked at, authentication, MVC - with more than 3k loc controllers - and monoliths were "impossible" - as in not economically sustainable - to refactor.

I think there's a misunderstanding of the word "easy", django, springboot, laravel, RoR etc are easy to start with, as most architectural choices come out of the box, but then you can never leave that box.
Note that batteries aren't an all or nothing thing. Just like a Prius, you can start with small batteries that just save you burning fossil fuels (even with the added weight), and help you reclaim energy when braking or going downhill and then add bigger and bigger batteries, as batteries get better, lighter, cheaper, electricity gets cheaper, greener or diesel gets more expensive.

It's already started, real battery trains are in operation in niche roles (and nearly always have been since before lithium ion) but the process will accelerate and expand over time. They complement electrification of lines, they don't compete with them as you can use one or the other based on which works best for a particular stretch of track, or task.
Decent experienced massage therapist has made a dramatic difference for me.

Also gravity boots from time to time and basic stretching.
I use Things3 loosely, mainly for (reoccurring) reminders, also keep my shopping list and things like that in there. I also use it for work tasks, but not a lot, I don't like endless backlogs I will delete things that sit too long. I generally remember the important things.

I also use "remind me" in Slack a lot as most stuff arrives there. For me it's often just a case of "postpone till after I complete what I'm doing".

I use Google Calendar for appointments, birthdays etc, work wise I'm stuck with Outlook calendar, it's fine, works well to schedule meetings etc.
But only in the sense of financial risk.

That doesn't seem unreasonable to me that people who are entering some sort of financial contract with you have the ability to easy see your credit history.

But again, just don't use credit (or use it minimally) and you're good.
Practically speaking, if you're using personal data in ways that GDPR demads consent for, you ... probably shouldn't be doing that. You can store data that you need for a laundry list of legitimate purposes without consent.

The consent provision is an escape hatch for incumbents with consent-tracking infrastructure to carry on doing (and raise barriers of entry to) mostly-illegitimate processing (and okay, the odd thing that might be reasonable but that the law hasn't considered).
If you're a civilian on the receiving end of some bombs, it doesn't make a big difference indeed. For everyone else it does, unless we are taking that high ground argument in which everything is doomed and everyone is a jerk.
Look at what happened to the US when people were given free money.

Money is ultimately numbers on a piece of paper. It's inherent worth is equal to that of monopoly money. It takes a lot of effort to keep that from happening.
At GreenGo, we are trying to re-enchant local tourism for Europeans so that they are less inclined to take the plane => changing behaviours, not improving technology. We want to do that by making local destinations more desirable and making figuring out which destinations are accessible with low carbon transportation much easier.

So far we have built an airbnb-like platform (https://www.greengo.voyage) with a host selection component, but we have big plans to differentiate thanks to a recent 1.6M funding round. People who want to embark on this mission don't hesitate to contact me at felix@greengo.voyage :-)
>I really hate to be naive

Being naive/curious is the best way to start learning.

https://en.wikipedia.org/wiki/Real-time_computing#Criteria_f...

>>In the context of multitasking systems the scheduling policy is normally priority driven (pre-emptive schedulers). In some situations, these can guarantee hard real-time performance (for instance if the set of tasks and their priorities is known in advance). There are other hard real-time schedulers such as rate-monotonic which is not common in general-purpose systems, as it requires additional information in order to schedule a task: namely a bound or worst-case estimate for how long the task must execute. Specific algorithms for scheduling such hard real-time tasks exist, such as earliest deadline first, which, ignoring the overhead of context switching, is sufficient for system loads of less than 100%.[7] New overlay scheduling systems, such as an adaptive partition scheduler assist in managing large systems with a mixture of hard real-time and non real-time applications.
It depends where. Both the article and the responses throw everything in the same basket, as if it all universities are the same and all education systems are the same. The bologna accords sure tried to make all higher-ed work in the same fashion and it has been a disaster.

There is no doubt that in the US in a lot of universities graduate students are a cheap workforce that reinforces corporate interests through research that is funded by them to sway public opinion in certain directions.

To some extent this is due to the sheer amounts of money that flow into academy and the amount of money that you need to stay competitive. So you can't piss off your patrons.

For a long time at least the fact that graduate students in europe received a steady subsidy that is enough to comfortably live and universities received fixed amounts that are not dependent on industry push allowed universities to stay independent for the longest time. Although that too is changing.

There is a fair share of critique on the latter system, but in general it allows for more independent research institutions.
That 40% is removal of Russian investment capital following financial restrictions due to Ukraine war.
> Their product is simply inferior in every way, except for their library of master lessons

That's just not true. I've been using both for a long time and chess.com has more intuitive UI. I frequently find myself exporting my games from lichess into chess.com simply because the latter offers superior game analysis experience.
How can you even say that with a straight face when it's already getting scaled back?
I get your point, but it’s funny that you used a land locked country as an example.
Such a clever name :)
TAANG would be cool, Spotify is not really comparable with these companies IMO.
This a thousand times.

> And while they are the primary workhorses of research, there are large swathes of their graduate student careers where they are not particularly (or often negatively) productive.

Um, hello. This happens in industry as well. It's called training, learning, whatever. It's an investment on the part of the company in the future of its workforce. Why should academia expect to only pay employees who are "fully educated" and require no non-productive time to learn things?

As someone who has been there, academica is so f*cked up and those in it seem completely out of touch with the reality outside of it.
I mean the Allied waged total war on Germany including bombing cities into rubble and it turns out pretty well? Same with Japan?
Ultimately there’s some things that are best done with dictionaries, so it would be nice to have a simple tool to do this. Something like ‘x.?y.?z[“something”.?]’ would be nice, where the ? might pass any None through to the end without causing attribute and key errors.
I personally really like Alfred Tarski's book "Introduction to Logic and to the Methodology of Deductive Sciences". The first Polish edition was written in 1936 and the English version is still available from Dover: https://store.doverpublications.com/048628462x.html
Show HN: An Amazon Donating All Profits to Charities
Hi I'm Vin, the founder of BOAS. Currently selling sustainable baby/kids products but when successful we'll slowly roll out other categories. Sustainable buying currently sucks because it's fragmented and expensive. Consolidating sustainable products on one marketplace and enabling price competition on the marketplace will make it less sucky, just like Amazon did. We're doing this because we discovered that there's a big chunk of sustainable buyers and brands who don't want to buy from or work with them because they don't trust them with ethics and sustainability. That's where we come in.

We're donating all of our profits (over the lifetime, after scaling so we don't hinder our growth, our investors are philanthropists) because it's the right thing to do, and fortunately it actually seems like that's a USP that brands and consumers care for and helps us establish trust, which is critical to succeed in sustainability.

Please have a look through the website, try to buy something (if you want to pay even better ;)) and let us know what sucks or what you don't understand about what we do. We're currently on Shopify and have a technical integration with most ecom platforms. Ultimately we would want to own the whole infrastructure ourselves.
Because building wells is more effective at improving access to clean water.

Do you really think giving people more money would make developing countries develop faster? It would just create incentive for companies to keep things as they are, so they can extract that money in exchange for things like bottled water. Those companies would seek to corrupt local governments to do so. That leads to widespread aid redirection and skimming.
> PHP is documentation done right because of the comments, essentially "Stack Overflow" for PHP before stackoverflow.com was a thing.

It's funny really, for a programming language to rely on comments made by random people, instead of having those aspects covered in the documentation itself. Shows a bit of lack of care. It seems half-assed as many things in the ecosystem seem. What happens, if they ever lose that database of comments? The whole world scratches their heads wondering how to use standard library functions? Ridiculous. I hope they have good backups.

> I've found an example of documentation done wrong recently with Microsoft .NET 6.0. Apparently, Microsoft has decided that code samples are no longer important

And for as long as important documentation resides in comments in PHP docs, the same can happen to PHP docs. Lets say they push out PHP 9 and some things change. Someone thinks "Ah those comments are not actually true any longer. Lets get rid of them." Bam, massive resource lost, because the knowledge has not been integrated into the documentation.
Not sure you needed to experience Nazi propaganda back in Nazi Germany to understand the dangers of that propaganda or why it was wrong. Of course you'll miss some nuance but I'm not really sure how important that really is.
iFixit and Samsung are now selling repair parts for some Galaxy devices
Sequoia

https://www.slideshare.net/eldon/sequoia-capital-on-startups...
Vendor lock-in is always omni-present, even if you are using Kubernetes. The only difference is that the vendor lock-in you get when you run Kubernetes is mainly with the infrastructure layer hosting the code, instead of the code entrypoints.

Not to mention any managed services you want to use, which also will lock you in. So I don't do anything extreme to avoid vendor lock-in, other than making my code general enough to only have a small surface area for the lambda entry point. As a practical example, all of my APIs hosted on Lambdas are ordinary ASP.Net apps that would work identically if hosted in Docker containers.

Pricing so far is one of the biggest benefits of doing serverless approaches. I'm down to paying a couple of dollars per month for something that I'd pay tenfold for if doing Kubernetes. Both the monetary sum of only paying for what you're using, and also not having to worry about cluster maintenance, scaling and management is a godsend.
Ugh... Sorry but this is not physics.
I'm happy to assert that making anything other than false be false is a mistake.

The problem is sum types. Specifically, languages which "don't have" sum types often secretly do have sum types, absolutely everywhere, but no language facilities to deal with them because they "don't have" sum types. That's what the billion dollar mistake is, it's sum types (thing | NULL) with no language facilities. In Python that's (thing | None) but the same penalty accrues.

Now, PEP 505 introduces a bunch of actual language facilities. They might be a good idea for Python, other languages successfully did this, but I think as a lesson going forward what we should take away is that we do want Sum types and we should stop pretending we (sometimes?) don't, which means new languages need to be designed for them.
Mystery of Noah’s Ark Solved
Vroom and Carvana are shit with mechanical inspections/repairs, but CarMax should be fine; unlike Vroom/Carvana their in-house mechanics operate basically identically to the service center of other dealerships. Also they actually look and drive trade-ins before making an offer.

CarMax should be a little bit more expensive because you're paying for a 30-day return policy and 90-day warranty even if they're not itemized. But like, for the Tesla linked, nearby RWD 2022 Model 3s are priced between $55-60k from other sellers. So that's 5% over the cheapest comparable listing.
It's not as easy as saying "there is an exemption", because courts ruled in many such cases and usually denied that argument, at least here in Germany and other EU jurisdictions I am aware of.

E.g. you cannot just keep medical records (unless you are e.g. a hospital and are required to safely keep that data) or dick pics either. Decisions about other less sensitive PII often haven't been made yet, but chances are the courts will not side with you but with the person whose PII is concerned.

What you can keep is enough information to identify the paid user in court (e.g. name and address data) and enough information to e.g. show you fulfilled your contract. E.g. if you're an email provider you probably can keep logs that show a paid user accessed your service and sent and received emails regularly, i.e. meta data about usage. What you cannot keep is e.g. the actual emails a user wrote or received or what contacts were in their address book.

Then, there are statues of limitations, e.g. in Germany usually 3 years for any debt disputes. Keeping data beyond that wouldn't be covered by exemptions, as the data would no longer be necessary to mount a defense.
I believe that the linear relationship between GDP and energy consumption makes it impossible to achieve growth and fight climate change.

That said, I'm working in the climate insurance start-up Descartes Underwriting, trying to compute risks for many natural perils: cyclones, wildfires, hail, droughts...

We're not on the mitigation side, but on the adaptation side. The financial service we provide helps companies survive and recover after catastrophes : I feel like my work has a positive impact! And although frightening, it's really interesting to first-hand witness the perturbations of climate.

https://www.linkedin.com/mwlite/company/descartesunderwritin...
Not possible. Imagine the number of scenarios that require fixes. There are just too many of them. So you either end up with a gigantic amount of crystals (but still can't solve a problem in some exceptional cases) or you have a small number of crystals but a high number of situations where you can't resolve the problem with them.

So maybe those crystals are more like app-configurations that we already have: you can tune things in a predictable way, but as soon as it goes beyond that you need to change the code.
More sustainable than having a growing population depend on surface water and open air defecation.
Oh… thank you! I have never thought about this. So it makes sense!
PHP's strength is its architecture: stateless, interpreted, and its rich ecosystem.

The language isn't as good as Java, but is familiar, and has made lots of improvements, including around types.
Especially considering how easy it is for duplicate content to reach the top results on Google these days.
Basically the same as any other OS, but typically stripped down to the bare essentials. The key differentiator is the kernel scheduler, which is typically set up to provide regular and guaranteed time slices to processes.

Normal operating systems provide time slices in big chunks, and not very predictably.

The RTOS approach is less efficient overall and has lower total throughput, but some applications don’t need a lot of horsepower, just consistency.

Think: robotics, audio, servo motor controllers, etc…
Check out Livecycle (https://livecycle.io/). I'm part of the team there and it sounds like it could be the tool you're looking for, since our aim is to make the review process more organized, clear and collaborative for front-end teams.

The platform lets teams collaborate on top of PR preview environments where all relevant stakeholders can comment with text, screenshots, video captures, and by easily editing HTML/CSS elements, as you mentioned you wanted to do.

All review comments are organized in the Livecycle playground (with relevant notifications for playground collaborators) and also synced back to Git where developers can see them in full context.

So using Livecycle, your team will be able to clearly collect UI/UX feedback from everyone, and avoid unnecessary tickets and emails. The whole process becomes transparent and collaborative (for both technical and non-technical stakeholders).

It takes just a few minutes to set up, and at no cost. We're available and happy to help and answer any questions and also to tell you about our upcoming rollout of an SDK...