skysight-inc/HackerNews huggingface dataset:
Nice to see this.

Few months ago I've created a platform to analyze jobs based on Google for jobs data in real-time.

You can search by job title and location, and it will give an indication about the job market.

I did it as I wanted to understand which publishers are appearing more on Google For Jobs, and how many jobs are remote in certain locations.

https://rta.jobdescription.ai
The article is from a couple of years ago, but their bad practices continue.

I subscribed to their PRO offering, but due to some kind of glitch on their side, I am unable to actually download any scores listed under PRO. When I try to download, the site just says "PRO subscription required"; when I go to my account, it says "PRO subscription active".

The thing is, downloading scores is not something I do every day. So, I would run into the problem, submit a support request and forget about it for a while. Next time I want to download a score, I run into the same issue again, and realize that their support never even bothered to reply to my previous request. Rinse, repeat.

What a terrible company to do business with.
"the users..."weird""

I would have chosen another word for them...
Is the culture section being 100% blank a very wry joke about there being no culture or a mistake?

https://abseil.io/resources/swe-book/html/part2.html
It's so closely related and so often mistaken, feature flags and tenant features are two completely different things
Great comment. Google and others blazed a trail, but by 2010 you could find similar, often specialized tooling and practices emerging at most Fortune 500 tech companies.
Related: The Carrot Problem https://news.ycombinator.com/item?id=37100226
Thanks a lot for the approach. Now I recall we had a Lua/nginx setup a couple of years ago similar to this and it was actually really low maintenance (wasn't on AWS though). I need to check the monetary aspect of the Cloudflare approach, but for best effort "Free" plans this could be a cheap option on AWS.
No, you're saying that like those extreme highs are distant specters. They already happen and are part of our immediate future. At which point, the human body cannot survive by evaporating water. Drinking cold water is an active measure which frankly is not available to all people, especially many of those most vulnerable to these fatal temperatures. When the WBT passes a certain level it will kill you straight up. Cold, not so much. People live in Antarctica. And although we will get storms and more extreme weather, the planet is getting hotter.
I'm not really talking about artisanal 3-man software shops, I'm talking about mid-sized companies with thousands of engineers, who don't realize they are already larger than and facing the same problems as Google was when they started adopting these practices. And to be clear, rejecting something as proven as pre-commit code review is not only to reject the example of Google and many other very successful enterprises, but also to ignore decades of developer productivity knowledge before Google existed. It's almost like the fact that Google adopted a long-standing best practice makes modern engineers reflexively revolt against those best practices. This can only be seen as a structural advantage for Google.
That is not the surveillance panopticon that HNers imagine.

That is "Little Brother" -- prurient neighbour-watching.

Yeah, Little Brother is everywhere. (It's the bigger threat to our culture, IMO).

But this isn't a UK-specific problem. The USA, for example, has Homeowner Associations, which tie neighbourhood-watch curtain-twitching and petty compliance to personal freedoms, property values, paint colour and lawnmowing. The average suburban person in the UK arguably has more freedom from curtain-twitching busybodies than in the USA (where 26% of the population live in an HOA or condo association)

The British police do not have warrantless power to just lazily aggregate Ring doorbell footage or any other such thing (they may have faster access to cloud content with a warrant, but I suspect it is probably still faster to just look at the doorbells in the immediate vicinity and ask permission).
For string related stuff — there’s not much in the stdlib that can replace the stuff in abseil. (Haven’t looked at Dawn in particular, though.)

E.g. absl::StrFormat — no equivalent until std::format was standardized in C++20.

absl::StrCat: You could use streams, but, ew. Also, StrCat is optimized to reserve sufficient size in advance, so it is more efficient than appending to a string or using a std::stringstream.

absl::Cord. No equivalent in the stdlib.
The reality distortion field is strong.

An mp3 player was in every kid's jeans pocket before the ipod was even announced.[0] Its innovation was costing twice as much and having white earphones, which made it suitable as a wealth-signaling fashion accessory.

[0] https://en.wikipedia.org/wiki/Portable_media_player#The_MP3_...
some people are born with social privilage, but a lot of folks work at it.

meetup.com groups, linux user groups, powershell scripters forums, python guilds, SCADA code conferences, etc.

doesn't even have to be tech stuff per se, my ISP account executives (sales guys) used to pull leads from Cars and Coffee meetups, painball, beer tasting events, etc.

you may not be born with blue-blood connections, but you can certainly build lots and lots of connections, and tech, esp. startup tech, is a place that lends itself well to that. go get em, killer.

> Also, isn't it a bit scummy to keep someone in your life just in case you need a job?

if you only see this as transactional, esp. in a one-way transactional sense, you're never going to network successfully; it's quid pro quo, and you need to be willing (and able) to give as well as receive. and not always just job stuff.
It seems possibly counterproductive to equate "exercise" with "stress". I find I am invariably much less stressed, emotionally, during and after exercise. I am not convinced that any amount of "stress" is good for you.
When you have the golden goose, you don't actually know how it makes the gold. You think you know, and you aren't completely clueless, but you don't really know, because it's complicated.

The obvious thing to do then is to not change too many things around it. Or at least document the changes.

So then you get a bunch of processes that are designed to not rock the boat too much, in case the magic dies.
This is basically the whole premise around the "creator economy". Learn what you're interested in, write it down, preferably in public, repackage/repurpose into something of value for the person one step behind you in knowledge/skill.
I can't `ping ::ffff:192.168.0.1` and have it ping my router. There is a range reserved for representing IPv4 addresses, but the stack doesn't translate.
The Clean Energy Future Is Roiling Both Friends and Foes
> The Process becomes more important than the Product.

I don't know if the process is more important, but at a certain size codified process becomes a requirement.
Jlama (Java) outperforms llama.cpp in F32 Llama 7B Model
Those aren't publicly routable though... that's the problem.
It's actually not that flawed, you've more or less invented 6to4. Every v4 address has an associated v6 network (basically 32.2.a.b.c.d.*), and you can send packets to that network by crafting packets that use protocol 41 ("6in4"). It only gives 2^80 addresses per v4 address but that should be enough for anybody.

But uh... it doesn't seem to have helped as much as you're thinking.

Also, you didn't address how v4-only devices or software would talk these bigger addresses (how can you fit >32 bits into a sockaddr_in struct?). That's one of the big difficulties of v6 deployment and it won't go away no matter how you design v6.
It's a really useful perspective in real-life scenarios when you're not developping critical software. Of course a baseline of risk-avoidance is always important, but businesses/custommers/users most of the time are ready to handle some risks, like downtime, bugs, delays, etc. SWE and developpers are the more risk-averse of the two parties, which leads to us over-valuing the importance of robustness and stability.

For example, it's way easier/faster to implement observability and some sort of rollback of bad versions than to try and prevent every possible way an app could crash and trigger a bunch of problems. What's going to happen if the app crash is pretty simple : customers will be mad (CS/Marketing/PR can handle them), you'll notice the downtime quickly and rollback (or maybe even rollback automatically!). Then you'll be in a perfect position to handle what went wrong : systems will be back on a known stable position and all the stress of trying to fix something in a live production system will be gone.
This is really, really upsetting to be happening in my country. I know it is a very big country, and Kansas isn't exactly proximate, but we are either a country that protects the press, or we are a country where the press protects those who have power. If this is allowed to pass without the people ordering the raid fired, I am not optimistic about what the future holds.
GH: https://github.com/tjake/Jlama
https://archive.is/rQgNx
Oh boy, this is a favorite topic of mine because I get psychosis over 7000 feet.

And it is all about my genetics. I am a lowlander by heritage, a Sami from Finland, and I carry genetic changes in NOS1AP that lower my ability to make nitric oxide at altitude. But the other factor is polymorphisms in GCH1, a gene linked to altitude adaptation:

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5460084/

See GCH1 is the enzyme critically needed to make something called tetrahjydrobiopterin (BH4), and BH4 last at the center of the creation of all the catecholamines, like dopamine and serotonin, but also Nitric Oxide.

https://www.researchgate.net/figure/Fig-1-Tetrahydrobiopteri...

They make a drug called Kuvan which is a BH4 analogue but they only sell it in the EU because they want those of use with mental illness in the U.S. to suffer.

But zinc will increase the activity of GCH1 and alleviate many of these issues for me.

https://www.sciencedirect.com/science/article/abs/pii/S00062...

It has nothing to do with low oxygen, but rather low catecholamines.
Yes, Java has this one strong inconsistency on its type system. The interesting thing is that the addition operator has a not completely predictable behavior exactly because the language designers insisted that custom operators reduce the language predictability.

But anyway, it's much less bad in Java because you can force it to err by declaring what type of thing you want it to return.
Remember that your goal is to have something to say, not to make the code better. No matter how good the code is, you need your fingerprints on it somehow.
I just wish more places would adopt `third_party`; I would also love reproducible builds but I'll settle on third_party.
It's also Google licking the cookie. They maintain a moat around ads by doing just enough to threaten to destroy anyone that gets close to their ecosystem.

Facebook survived because G+ product vision was so out of touch with reality and FB were not part of the anti-compete hiring nonsense so that they managed to poach a lot of good people.
2^nflags actually. Which is a much bigger number.
The approach obviously doesn't work at all for unidirectional protocols. This approach also doesn't work when there are multiple equal cost paths, but with different MTUs. Which used to be more common and now tends to only happen when changing link technologies. The original sender needs not just the discovered MTU, but the original header information that may have been used for flow hashing.
Why? I don't want into any "official chat network". I despise whatsapp and its success in Europe is a testament to the lacking class, culture and taste of its clueless inhabitants.
>most tools are exactly the same sort of thing that you'd create in any other place, we just have more of them

Why? Why reinvent the wheel 10 times?
Based on what is it pretty clear that everything went downhill when engineers stopped calling the shots?
Alright, let's use the custom approach. And then you need another field. and then you need some slight type checking or (de)serialization, which can change over time. You'll end up writing your own custom, kludgy ORM over time.

I have seen people write their own custom crazy version of GraphQL ("I've created a JSONified way of fetching only some fields from an API call) over ego or just ignorance. It's never a good path.

Why bother moving away from SQLAlchemy, which will do all of that for you in a simplified, type-checked and portable way? SQLAlchemy is literally one of the best ORMs out there, it's ease of use and maintainability is insane.

People that complain about ORMs might have never really used SQLAlchemy. It is that good. I'm a fan and zzzeek is huge force behind why it is so good.

And as always, if you need an escape hatch, you can use raw sql for that ONE sql statement that the ORM is giving you grief for.
Society with privacy is different from and preferable to society without privacy. For one example, a lack of privacy enables the identity based political fragmentation that afflicts us. For another example, in developing relationships of any kind, people choose aspects of themselves to reveal to other parties. When negotiating a price, information about the counter party is an advantage.
> You're correct.

No, s/he's not. The original claim was:

> It is in general undecidable whether an object is UNREACHABLE. [Emphasis added]

Being unreachable is not the same thing as being "no longer used by the code". The latter is indeed undecidable, but the former is not.
Bug Tracking vs. User Support
As a non-engineer user, I know I have regularly felt unwelcome in various ways.
Probably all of the above is true.

From an outsiders, it looks like all of FAANG has scaled to the point where delivery, perf and managing the business has become quite cumbersome. This, I suspect is why they're all used the economic climate to cut back, as they largely are unable to see the benefit of the additional hiring.

I have no doubt most of the talent is top tier, but being a strong engineer doesn't deliver profits nor cost savings on it's own.
I guess I'm just used to it now, but I kind of like the UI. It's easy to skim the page to find the part I'm looking for.
It's janky, and when you do choose to use a best-effort tool with no dedicated support, you absolutely have to plan for it being a pain point and the likelihood of eventual migration.

That's true at Google, just as it's true anywhere. But what makes Google a much better experience than most places is a willingness (and ability) to pay for internal dev tooling of every sort with dedicated headcount. And that results in a consistently better experience than pretty much anywhere (I understand Meta has a comparable culture and ability to fund it, and I wouldn't be surprised if some or many of their internal tools surpass Google's). It's also unfortunately not replicable as a strategy, because you need a giant money spigot to make it work.
To put it simply it's very difficult to determine what objects (in the C term) are garbage. Hence why we have things like reference counting. We need extra data to hint to the collector what is, in fact, garbage.
I cannot more strongly endorse this.

It would be tremendously beneficial if their software dropped the abseil dependency, especially where it is almost entirely unused. Hell it'd be better if they simply vendored the bits they need.

Having to use Bazel, and having to manage an additional dependency like abseil can be hellish for small projects with uncomplicated build systems.

The worst part is that abseil leaks through interfaces and you end up being coupled to it as a consumer of a library. It's bananas. I don't need yet another stdlib.
It certainly creates a lot more work for authorities than simply gaining the attendee list.
Representative democracy is basically worhtless except for one or two issues that are important to a significant number of people. Not to mention that US copyright and especially enforcement against the internet archive also affects people who are not US citizens and can thus not even pretent that their vote matters here.
>if its google id be happy to try to persuade you via chat.

I would be curious as to how you view projects that are staffed entirely 20%.
On top of the judge signing off on the warrant when this likely contradicted federal law, we have this:

> When the newspaper asked for a copy of the probable cause affidavit required by law to issue a search warrant, the district court issued a signed statement saying no such affidavit was on file, the Record reported.

Not a lawyer and I know it takes quite a lot for a judge to be disciplined but that would seem to be something a judicial conduct board would want to look at.

https://apnews.com/article/marion-kansas-newspaper-raid-aca0...
I would also assume so but then I suppose that it's basically impossible at this point to avoid a leetcode interview where you have to prove that you can solve Fizzbuzz, even if you've literally written a book on the language. But my goal wasn't to get a job writing Rust in the first place.
Perhaps, I think there are a couple of things contributing to the declines represented since mid 2022. I believe them to be economic conditions. My outlook is quite the opposite as I think data roles will continue to grow in demand over time for the next 3 years.

The overall economy is not doing well right now, at least in the USA. There is significant amount of extra talent (supply) on the market due to big tech hiring freezes and layoffs, which also contributes to lower demand of new roles. There is the return to office debacles occurring all the while housing is becoming even more unaffordable due to high interest rates (compared to the recent 2 to 3% during covid) and low supply a consequence of the rates where owners aren't going to want to trade a 2 to 4% for 7+ nearly 8% right now. I don't cite rto debacles to have a debate on the specifics of if rto is good/bad, but I would speculate that it's pushing more talent onto the job market to escape working environments forcing any style (rto or forced remote) that an employee disagrees with.

So, in my mind the only thing my speculation doesn't really cover is how that would contribute to lower HN responses to which I don't have an answer, maybe it truly is shrinking. However, my gut says it's the economic factors. I think (and hope) that the shift in conditions occurs in the next 6 months and hiring ramps back up as companies recover and adapt.
> may in fact be doing harm without actually sufficiently preventing any risk.

The biggest practical impediment to increasing velocity of delivery that I encounter is trying to convey this. People can visualize and estimate the risk and impact of a deployment gone wrong, but have a hard time estimating the impact of processes that slow down delivery. Therefore they overindex in heavy and "safe" processes (which often don't increase safety) at the cost of speed of iteration.

I'm not sure how to define this asymmetry, maybe some variation of loss aversion.
I agree apt or dpkg ending up in a bad state would probably mean bricking for lots of people. It's something I remember also having to do in some cases after dist-upgrades.

I remember having occasionally dealt with having to manually run dpkg reconfigure to install packages that had somehow ended up in a semi-installed state during an upgrade, or some other similar bad state. To someone who's not familiar with the distro's internals, and probably to some who are, that would just appear as a mysteriously broken system that no longer operates.

I guess for me bricking would be if I can't get the system working again using some kinds of relatively well-documented or known repair steps (that is, known to me or sort of generally). I'm more bothered by something not quite working right and not understanding it than I'm by a complete but repairable bricking that I understand or know how to fix.

That's almost certainly not how most people would perceive it, though.

And even though I'm probably not that averse to fixing things, I also originally moved from Debian unstable to the newly founded Ubuntu because I didn't want to deal with routinely playing sysadmin on my personal box any more.

With that said, I don't know if it's because of stricter checks being made by dnf before package operations or what, but I've never got dnf/rpm into a non-working state on modern Fedora. Despite my old affection for Debian-based distros, I admit that apt/dpkg has seemed more flakey to me after this.

After nine years, I wouldn't even know how to try doing something similar to manually running dpkg reconfigure on Fedora. If that even exists.

(edit: sentence)
Guilt isn't being ascribed to the victims or casualities. It's being ascribed to the Europeans who hold prejudices against Islam and are alive today. If you aren't one of those people, there isn't much left to critique until you read the book.
Music2Image Exports Videos with Music
What do you mean by "higher stack" here? SREs being highest paid is true for my anecdotal knowledge and what I've seen in salary surveys. I'd be interested in updating my understanding though.
If Putin said the US withdrawal from Afghanistan was incompetent and resulted in unnecessary loss of life and billions of equipment for the Taliban
Would that statement be Russian propaganda or the truth?
If I understand GP correctly, it's 'performing raw SQL queries', or specifically here, 'mapping query fields to model fields': https://docs.djangoproject.com/en/4.2/topics/db/sql/#mapping...

Basically you call `.raw("...")` from some model's queryset, but there's no requirement you actually query that model's table at all.

class SomeModel:
name = models.CharField()

class OtherModel:
foobar = models.CharField()

SomeModel.objects.raw("select foobar as name from thisapp_othermodel")

will yield `SomeModel`s with `name`s that are actual `OtherModel` `foobar` values.
Hidden behind what sound like individually interesting ideas is a whole lot of exhortation to do early optimization. That is seldom if ever more productive

If you click through to the interview with Elon, he cites the elimination of a fiberglass mat in the Tesla battery pack. He makes it sound clever, but the fact a mat without a clear purpose was there to begin with was a failure to manage specs. Nobody knew who specified it. Obv someone did. But when you lose knowledge like that, you're not clever for fixing it later.

Elon's anecdote also points to chaos and turnover as causes for losing that knowledge. If you work for a mercurial manager who fires people on a whim, how likely are you to observe proper change management in the spec process instead of hoarding knowledge for your own job security?

Elon is reinventing processes that have better existing instatiations.
Entitled "special" people are a problem everywhere.

Dev's who are labeled as high performers get greenfield projects that can be pumped out quickly / look good ... someone else does the maintenance, they get all the flack for an obvious bug that wasn't fixed even if they didn't make it.

The random executive who is thought to be highly successful who jumps from department to department spreading his fingerprint long enough to make an impact and leaves quickly enough to avoid any responsibility for the results.

I fear it is a human thing and people are really good at sensing when they can get away with things.
“Making it easier for people to break the law” is a weird way of saying “Making it harder for authoritarian governments to abuse its citizens”
My hot take (as a DS of 12 years): data scientist was always a over-hyped title and led many to unrealistic expectations. I think we will see a rise of data-inflected product managers (this is what I am already seeing), as IMO data scientists are most effective at scoping problems and pioneering solutions, not scaling them.