skysight-inc/HackerNews huggingface dataset:
"Things that try to look like things often do look more like things than things. Well-known fact," - https://www.goodreads.com/quotes/964367-things-that-try-to-l...
Why is this the top story? This is a major foot gun. Don’t write business logic in the database. You may think you are simplifying things but in fact you are making them more complex.

Instead adopt a solution for structuring your business logic in a sane way, such as using a workflow engine. Your code will become simpler and well organized that way without creating a tangled web of distributed rules, as well as exist all in one place.
2 factors - something you know and something you have. The device is what you have, the pin is something you know, otherwise anyone can pick up your security key and use it
I've been researching GPT's functionality -- probably 90% of what I've sent it has been hypotheticals. I shudder to think what it thinks of me :-)
Of course I forgot the word "detection" after phishing, thanks for pointing that out.

Apart from that, I repeat that I'm conscious about what you are saying. This is the fundamental problem of phishing and social engineering techniques detection in general. I just can't think of a better way to solve the problem without a human analyst nowadays. Maybe in the future, with the improvement of the AI engines out there, there will be a new way of handling the problem.

I appreciate constructive criticism and I know the problems my tool, which was born out of curiosity to automate a SOC + threat intelligence workflow, is subjected to. I may really appreciate also any suggestion or advice on how the workflow could become more usable in the real world.
Just had this conversation with one of my juniors. He brought up scalability concerns with a PG queue and wanted to know if EG REDIS was a better choice. My whole tack was to lay out the actual context for the system—we’re going to soft launch, it’s for a hardware product, and we’ll have some one post-launch to make changes. Then I brought up my values since I’m basically in charge: maintainability, speed to first release, and ease of understanding. He made the decision that a PG queue was better for now because it’s easy to change our minds later, we already know PG, and we’re not anticipating fast scaling in this application.

I think a lot of the problem in industry is simply lack of rigor. We talk a big game about being software engineers but nobody takes the time to talk about values, requirements, trade-offs or business context for decisions. It’s a shame because these topics are the actual engineering of the system.
I feel like that would be the case no matter the school and no matter the subject.. In any class there are some students who just don't care, or are out of their depth.
The little bunny!
Please, if you back with Ally bank, email them and tell them you want Webauthn, not SMS. Ask to have the email forwarded to the head of development.

Please and thank you.
And when that process fails, what recourse does the average Joe have? Especially when you can't afford to have much downtime between phones.
We are helping our users with qa tasks involving code generation, where the answers may be either JSON, executable code, or markdown discussions involving the same. We are tuning for a bunch of tools following that pattern so our users don't have to.

It's easy to make a labeled training set for grading our homework (catching regressions, ...) in the case of classifiers, and that's basically what the blog post showed.

What about for the above qa tasks? We can ask GPT4 whether a generated A was a good answer for a Q, but that's asking it to grade itself. Likewise, in the code case, we can write unit tests for the answers. (Trick: we use the former to more quickly do the latter.) But I feel like there has to be better ways

Another: OpenAI always updates models based on use, so we have to be sure our tests are real holdout sets that never get back to them...
It's JavaScript Object Notation. An array of objects looks like that, if you want to have another data structure you can do it and have the accompanying code to consume it.

The only thing holding you back from doing that is 1kb of JS as the second argument to JSON.parse
I got it when I started needing nvm a while back. Tide is the second thing I've added - I tend to keep things fairly minimal.
In which country is this interpretation of copyright law valid ?

Soon: Freedows 12. "Your Honor, I just looked at the compiled code, so it must be considered clean from copyright claims!".
>> As a climate scientist myself, I can tell you this is untrue and a harmful legend

Other climatologists say otherwise:

https://reason.com/2017/01/04/georgia-tech-climatologist-jud...

There's also a long list of people who were listed as IPCC reviewers, who claim they pointed out serious flaws in the research, were ignored, and whose names were then put on the final report anyway.
s/bother/bothers/ Bloddy hell.
Right. But that's a point in favor of Apple ensuring consistency on their platform, isn't it?
What do you believe 'buy' means if it doesn't mean access to download the game and a digital licence to use it?

Also is GameStop allowed to use the term 'buy' in their shops? Because they are often selling a licence too, it's just in a box.
berita tercepat dan terpercaya di Kabupaten Tangerang
Also:

> Yes, it is written systemd, not system D or System D, or even SystemD. And it isn't system d either. Why? Because it's a system daemon, and under Unix/Linux those are in lower case, and get suffixed with a lower case d. And since systemd manages the system, it's called systemd. It's that simple. But then again, if all that appears too simple to you, call it (but never spell it!) System Five Hundred since D is the roman numeral for 500 (this also clarifies the relation to System V, right?). The only situation where we find it OK to use an uppercase letter in the name (but don't like it either) is if you start a sentence with systemd. On high holidays you may also spell it sÿstëmd. But then again, Système D is not an acceptable spelling and something completely different

Definitely a reference to being a daemon.

https://www.freedesktop.org/wiki/Software/systemd/
Betbola138
> pro-western

What does being pro- or anti-West has to do with the topic? There are many Russian expats in Germany who openly manifest their support for Putin's war on the streets of Berlin. You can be anti-Western and at the same time pragmatically leave Russia to avoid draft and being killed for basically no reason.
Reverse engineering is legal. The files that they distribute don't contain the copyrighted assets needed to actually play the game.
>I found it very hard to know when to go fast and when to go slow, what to skip and what to include. The feedback coming through wasn't real-time. I kept surprise open-notes tests to gauge where the class was lacking.

Teaching is a skill. Over time you would be able to gauge these things easier.

Or you could do what some of my HS teaches and college professors used to do, and basically teach it how you see fit, and put the onus on the students to seek out help if they need it.
There’s a big gap between $5 and $21… for now. That I have no doubt they’ll spend all their time building features so they can increase prices to close that gap.
If you ever start a business selling anything at all, the very first thing you will need to realize is that you never base prices on how much something costs.

You base prices on what people are willing to pay.
Lol. The consent popup on this site is nearly identical to the "dark pattern" example in the Cloudflare Zaraz blog post. No reject all option. You have to click learn more to customize to deny cookies.
Right — standards, not ethics. You still haven't explained how ethics matters here. Like I said, plenty of engineers that follow standards rigorously do it in the service of unethical goals.
I ended up hiring a US emergency dispatcher team and repurposing them - they would literally phone you up as second line - no robots.
Automated and smart decompilation is the ONE thing I would love to apply AI to.

Especially given the fact that we can generate and infinite training set:

High level code -> compiler -> assembly code

All the AI's got to do is learn the inverse map.

All you have to do is grab all of github, feed it to random compilers, grab the assembly output.

Boom : instant training set for a decompiling AI (and one that can recreate original code from assembly, hopefully complete with comments and meaningful variable and function names)>
Still not got it.

https://www.gov.uk/alerts

People can report their feedback via this link.

https://surveys.publishing.service.gov.uk/s/A7XZXQ

Yes

18 or over

No

My Device did not receive the Alert or I dont Know!

https://www.reddit.com/r/CasualUK/comments/12w9mt4/its_fucki...
They're correct. This article goes deep into the emails, what they said, the non-investigation that followed and more:

https://www.rossmckitrick.com/uploads/4/8/0/8/4808045/climat...
You are wrong about your military assessment.

A quick win would mean Russia would hold on to a lot of military resources. By providing Ukraine just enough to deny Russia any wins, and Russia stupid enough to not pull out, they are basically draining Russia to death.

Right now Russia is sending T-54's to the battlefield. Their 'storm the front' tactics is killing their soldiers at a crazy rate.

Now this is the military standpoint, there is also a humanitarian side. Now on the humanitarian side, I agree a quick win would be better and save a lot of lives. I'm a proponent for NATO to control the skies, at least West from the Dnipro river.

But claiming it's a military failure on the Western side is just plain wrong. This right now is NATO's ideal military scenario.
One major disadvantage of triggers is the inability to do canary deployments and vastly increased complexity of rolling deployments. When SQL code lives within the application, we can trivially run multiple variants of such code simultaneously. Running alternate version of a trigger for e.g. 10% of traffic is way harder.

What I would recommend instead is making use of CTE (Common Table Expression), because DML (modifying queries) inside `WITH` are allowed and taking leverage of `RETURNING` keyword in both `UPDATE` and `INSERT` we can execute multiple inter-dependent updates within single query.

With such approach we can trivially run multiple versions of an application in parallel (during deployment, for canary deployment etc.) and we have similar performance advantage of a single roundtrip to database.
Additional advantage is the fact that there is only one statement which means that our query will see consistent database view (with very common read committed isolation level it is easy to introduce race conditions unless optimistic locking is used carefully).
Thank you for your response! What you said makes a lot of sense, and confirms what I suspected - that at the end of the day these might not be that useful to those who actually are meant to use them.
Nielson knows I'm sure. That's a very good question. I'm sure the answer is just as complex. A mix of replaced jobs (or lets say, restructured jobs) into social media platforms vs traditional media (broadcast, print/web) over additional jobs in the sector.
This article actually never answers the question, why does this steam network releases steam in the streets?
Re: cost & holidays/hours

On pricing - I don't think it matters for small orgs the way it does for big orgs.
Let's say today I am in a role where I am effectively the CTO of a 5ish person startup, with only 3 technical. So whether I spend $200/year or $1500/year, I don't really care. Both are more than $0, and require me to review a contract, do a POC, have a lawyer or someone review things, etc.

My internal time to do all those things is more like $10-30k, easily.

Now, do I decide it's worth my time knowing that my devs are going to basically turn off their phones / go to do-not-disturb-mode still because it's sense of working hours is non-existent (making it worse than PagerDuty & Slack notification tuning, both of which I already despise)?
>Reverse engineering is legal.

Depends on how you reverse engineer. If you just throw a compiled binary into a decompiler, rename the variables and release that, you're probably breaking the copyright law in whichever country you reside.
Sounds like your problem isn't the trigger per-se
> First, it’s great to read the full paper with no paywall. Kudos.

It’s MDPI. The no-paywall thing is part of their predatory scheme. Along with blazing fast reviews with not too many questions asked. Seriously, it’s completely unbelievable that any significant article would be thoroughly reviewed in 2 weeks, as this article seems to have been.

> Second, I agree with the conclusion that more research is needed.

Indeed.
Listened to this episode on a road trip yesterday and really enjoyed it. If you do a "part 2", I'm curious to hear more details about how they pulled off the growth of Reddit, broadening from an initial niche community into a wider collection of communities. Thanks jl and clevy!
At the CC system I went to, it was fairly common for underpaid associate professors at nearby community colleges to teach some of their usual university courses at the community colleges for extra income. It's still a lot of work for them, but I think when you teach a familiar course at an additional school, you can save a lot of prep work so it's a little bit more like teaching another section of the same course than taking on a whole new one.
We've got some overlap on the stack part. But I am more focused on the infra side of platform engineering (including bootstrapping clusters), seems for you it's more app dependencies. Check https://www.kubestack.com and ping me if you're interested in chatting.
My guess as someone who's been in a position to implement it a few times but haven't gotten to:

- "Upstream" Support, For various combinations of stacks I've worked on, there has always been one component that didn't support it cleanly, (Flutter x Ory was my last attempt for example). If it was as easy as "just" enabling it I'm sure it'd be more popular, but when your provider or tech stack doesn't support it out of the box it's usually not worth the effort to implement it from scratch.

- Customer support. This has many sub problems. At my current job, customers get confused between social login and email/password all the time. Adding a newer more complicated technology would be a recipe for disaster.

Similarly, because my job deals with money in a country where mobile theft is fairly rampant, the additional burden of trying to reassociate a users public key/account/device is problematic.

Finally, I think the concept of managing private keys for a user is fairly complicated, though with passkeys and google/apple syncing your private keys for you I hope to see this burden fall away, and with it the rise of webauthn
That wasn't my experience at all, feels like a theoretical discussion. Let's take something like SoCal, "luxury" housing built 30-50 years ago is not considered luxury. Even if those still advertise as "luxury", they definitely can't ask for the same prices despite companies having monopolies on certain regions.

Reality is that it's too expensive to stay a "luxury" housing, all the labor costs and major renovations just don't make sense from a financial perspective.

The fundamental issue that people miss is that the cost of building a "luxury" housing and "affordable" is not that different. Throwing quartz countertops and a tiny gym with outdated cheap equipment for a few extra k is nothing when the place costs 500k+. Sizes are also not relevant, since newer apartments are smaller than older ones. We can't just build an old affordable house, that's it. We need to start building as much as we can and impact the demand by evaluating the impact of new businesses coming to the area.
I don't understand what is confusing. It was founded with assets (Tesla and Google shares) of which it must sell 5% a year but could sell a lot more.
You would be surprised how widespread it is across certain ecosystems. Even the apple JSON parser supports it. A lot of the .json config files in the JS/VSCode ecosystem are actually JSON5 files.
Software developers make up maybe a third of that wave, if that. There's also artists, scientists, teachers, journalists, political activists and all kinds of other folks that simply don't see the future in the country. A lot of them are families with kids, so it's often not the lack of responsibilities but a higher willingness to take the risk.
I was gonna mention that as well. There's a relevant talk from the System distributed convention https://www.youtube.com/watch?v=QtQMWUik0oY
It's about caching views or queries and updating them when necessary as well as keeping your cache and DB in sync automatically.
Sentry requires a platform to work, it's much easier to monetise. I'm not even sure it's possible to self-host?
The problem, at least in my experience is that the quality of community colleges seems to vary wildly, and you can’t really shop around too much when it comes to education.
People who left the country are not just software developers. We have seen the exodus of musicians, scientists etc, which after some very painful decision process just packed their things and took next flight anywhere. Many took their families.
I guess it depends how you count them:

> Other key findings in the report were:

Of the 89.3 million head inventory, all cows and heifers that have calved totaled 38.3 million.
There are 28.9 million beef cows in the United States as of Jan. 1, 2023, down 4% from last year.
The number of milk cows in the United States increased to 9.40 million.
U.S. calf crop was estimated at 34.5 million head, down 2% from 2021.
All cattle on feed were at 14.2 million head, down 4% from 2022.

from https://www.nass.usda.gov/Newsroom/2023/01-31-2023.php

So the question is: did they estimate the young buffalo calves as well? That seems to be what brings the cow total number from 40 to 90 million.
As the Ars article makes it clear, the predicted range of temperature change was extremely wide, 0.35 to 0.7 degrees by now even if you allow for the re-scaling to a shorter time period, yet actual change was at the very lowest point of that uncertainty interval.

That by itself doesn't tell us that they understand the climate though. Remember that previously they were extrapolating a cooling trend into an ice age. Anyone can extrapolate a linear trend forward on a graph into a disaster zone territory, but that doesn't imply real understanding.
Interesting take on 2FA. The user not being able to screw up is of course important, but the second factor (something you have) works primarily because it is tied to something physical and therefore local to the user, which is not subject to remote attacks.
> I don't really have a good understanding of why, but it's just something I've noticed.

Have they ever worked at the bottom? Working at the bottom of your discipline ensures you learn basics in a non-theoretical manner.

I was once interviewed by someone who asked me a question about restriction enzyme digestion. He didn't like my answer so rephrased whatever the question was along the lines of "what's the unit defition of a restriction enzyme?". Which I answered along the lines of "One unit is the amount of enzyme that digests the substrate DNA in one hour. But you always use more enzyme.". The unit definition is theoretically true, but it's irrelevant for most bench work. You (almost) always use more enzyme because: 1) your DNA is usually not the test substrate DNA, 2) the enzyme is not fresh at the supplier where it was tested (enzymes degrade in functionality over time, even when stored properly), 3) due to stochastic effects or other mechanisms (such as denaturing) some minimal amount of DNA may remain undigested, and an extended digest or digest with additional enzyme can help maximize digestion, and 4) enzyme is cheap compared to your salary and having to redo things. I unfortunately didn't get the job. Maybe I would have if I had said the unquoted part (but still probably not, he was just one interviewer out of many).
It's not the amount of data, it's what it does with that data. Try typing "Tell me a story about a unicorn arguing with people on Hacker News" into a card catalog and tell me how good it is at storytelling. Typing that into GPT-4 might not win any literary awards, but it obviously understands what you meant and does a passable job.
All fun and games until Microsoft releases GPT4-empowered next-gen Tay AI on it.
This is not reverse engineering by any definition of the word. Even in my country, where looking at the copyrighted code is legal when it is done for "interoperability" purposes, you just CAN'T decompile the thing, ship it and call it a day. My implementation being remotely similar to the original one would get me into trouble. Here, they are distributing literally a clone of the original game, down to the same checksum. Not only it is a useless legal defense, it is absolutely idiotic to think that it would be.

And in many countries of the world (including the US), not even looking at the copyrighted code is necessarily allowed. See the entire clean room thing.
https://archive.is/MzLMa
> The biggest complaint I have with these pithy articles is that they try to sell you on a particular trade-off without explaining what the deal is.

This is basically the clickbait in the wider world affecting software development, even though it might not look like it. Boiled down to the essentials, we are telling each other the software version of "Here's How to Lose 10 Pounds in Time for Summer." way more often than "How To Balance Diet and Exercise to Remain Healthy Over A Decade".

But it's up to us to those of us who like more discussion to reverse these trends. In that vein -- do you have good sources that typically talk about tradeoffs with technology rather than promoting a specific one? Kleppmann's book on Data Intensive applications is one I have found in the past.
Wtf is a “paved dirt road”?
Vaping is more accessible to kids, single use vapes are a plague, people are mixing their vape liquid to customize it so we don't really know the impact of that.

I'm not comparing a cigarette to a vape pen in terms of health, but both concepts
Umm yeah but in this case they just wanted to take a few pics for curiosity's sake. It doesn't look like the site they published them on even makes them money, there's no ads.
You just unintentionally made your problem distributed which is can of worms and you'll find out later when your project is successful in production.
I agree. They should be sued. Of course it’s incredibly hard to prove and even harder to sue someone you like. And lawsuits where neither side has money are tricky.

Probably universities or departments as a whole should be sued.
What's old is new again. In 2007 we were using triggers and stored procedures heavily with mysql and a java app. Unfortunately we were also reliant on read replicas. Some of this replication behaviour did not translate well with the mix of these functions and auto incrementing IDs. Sometimes it would result in foreign key constraint violations and all of a sudden our replication would stop. This was even worse when we tried multi master setups. I spent years dealing with this. Ultimately we dropped the use of the most complex queries and shifted them into code which made the replication more stable but at the cost of Dev time.

Morale of the story, use it with caution. I know postgres is different but when you start turning you database into a ball of mud things get dangerously difficult to debug and fix.
Can you give some more detail plaese?
I've enjoyed all of the episodes so far, but this one was definitely the stand-out.
So now you only memorize one 15 character random password for your bitwarden, is this the way to go? I am new to password managers.