skysight-inc/HackerNews huggingface dataset:
Try to fork in a POSIX compliant way an application using signals and threads, across several UNIX implementations.

Or asynchronous network programming with certificates, while using only POSIX APIs.

Dealing with filesystem capabilities, file locations, daemon configurations, port management utilities,...

Ah, and anything GUI related is not even part of POSIX.
In short, employers have some degree of power over you, and if you perceive people who wield power over you as wielding that power arbitrarily, that is nearly universally experienced as frustrating.

In GP's case, the arbitrariness originates from their potential employer not taking the effort to really evaluate GP's relevant skills in software engineering, but instead resorting to lazily ticking boxes on a checklist. And what's on the checklist isn't even particularly relevant.

What I imagine this does to GP's view of the world (based on what it would do to mine) is: "I believe I am competent because I've built up a set of subtle skills in software engineering over many years, and this is what I take pride in. But from an employment point of view, this is wasted time: I should instead have focused on optimizing the checklist (and I only found this out after years in the industry)."
This is a big misunderstanding of Nassim Taleb's "Antifragile" heuristic.

"Blue chip" corporations like Apple fall more into the "Turkey Problem" i.e people expecting the big, to continue being big.
> You can ask your candidate to explain the code... Is that not obvious?

Asking about projects is the obvious thing, but only substantial and interesting projects really provide any interview value. Yet another Todo app doesn’t fit that criteria. Neither is another scaffolded crud app.

A PR to fix a bug in a semi-popular library is worth. But saying “I have a lot of repos” is def not.
> Have you got a citation that Hamas is on a religious mission to "kill all non-muslims".

Read their own literature, read Wikipedia, read any source on Hamas. This isn't a hidden agenda, this is their stated goal.

> it's primary focus is to resist the Zionists which repeatedly encroach on Palestinian land.

I addressed the issue of "Palestinian" in the previous comments. There are extreme Zionists and there are people like me who support the idea of a safe place for Jews even if we don't support the previous Israeli government- the current one is too new to have an opinion on. And we're Zionists too. I want to see peace and equality for all the people.

> Imo, making a comparison to ISIS is a tad bit lazy given the historical buildup to the problems in Israel. Just because a bunch of guys have big beards and shout in Arabic doesn't really make them equivalent in their aims.

It would be lazy if I were doing that, but I wasn't.

I was explaining their ideology, explaining why it's different than the PLO. As for have big beards- Jews have big beards too, and some of the Jews with big beards in my family speak Arabic as their native language, so what's your point?
There are Catholic priests and nuns, and some 1100 Christians in total living in Gaza which as far as I know is controlled by Hamas.
>And yet, with Git, the response just seems to be "if you don't like it you must just not _get it_." Which, I guess is fair, but I don't particularly understand why everyone has to "get it"? Why can't we expect a tool that's used by so many be intuitive?

There are lots of UIs for git - many people on this forum will advocate for using one. My personal experience is that a UI manages to over-simplify the git workflow. It never quite allows you to perform all of the useful tasks you want, unless your use of git is very basic.

In a more general sense, git can also be considered quite conceptually simple; "getting it" is not the real problem most users have. The confusion about what commands do comes from the fact that users learn the tool backwards. No job bothers to teach a junior developer about the DAG and what commits, branches, and refs really are. Instead, they are forced to start with git's large and crufty CLI - so it's no surprise that it's hard to pick up any intuition about what's going on.

And that's a problem with lots of technical teaching, not just git. Since the focus is on getting immediate observable results, and not on conceptual understanding, users tend to learn how to use tools instead of how they work. That creates a culture of "I don't know what this is doing, and I'm too scared to mess with it" - basically the anti-hacker mentality.
I really like this. Something about the minimalism, and peaks my curiosity as to what was said about each link. Funny that this thread and https://www.askhnwisdom.com/ is in the list :-)
You usually want to authenticate the sender, both to make it harder for attackers to learn anything by sending you chosen ciphertexts and because users actually want to know who they're talking to. And if you're doing that, then that authentication will be non-repudiable unless you go out of your way to make it repudiable.
I bought from this company:
https://www.ksrlighting.com/
(UK based)

Very impressed with the colo{u,}r purity

You can disconnect the transformer and power with 36v DC. Dimming works well with a PWM Meanwell dimmer (0-10v input)

If you're like me and want to avoid proprietary/locked-in stuff, highly recommend doing the 0-10v thing. Your control system is then separate from what drives the lights
There's plenty of work around the farm to be done over winter (basically, all kinds of work that isn't strictly necessary around harvest season will be pushed out to whatever other time there is in the year). You still have farm animals to handle. There are repairs to be made. Trenches to dig. And as the winter comes full force, given how low-density an energy source firewood is, you at least needed to regularly get out to haul and process fuel for heating.

Etc. My life experience is only slightly farm-adjacent. I'm sure someone who grew up on a farm can contribute more examples of winter work.
If you happen to have a few links, i'm interested!
At least in the UK they do reserve the right to file missed/late payments with credit reference agencies FWIW.
Maybe, but I have trouble thinking of a Python language decision that was made (or not made) because there should be a single way to do things. Can you think of one?
I've been gaming on linux for almost a year now and I've had no issues at all. I've mainly been playing popular titles but Proton makes every game feel like it's a linux native game.
> maybe some people really would be happier dropping out at 14 and just getting a job.

Note that in Europe, mandatory schooling ends in 15-16 in most states.
I saw once a guy sitting next to the door in a small crammed office. He would get hit by it from behind each time someone opened it. Must've been a marvellous experience, he quit rather quickly.
Replace highways with high speed rail and you run into the same problems.

The Japanese when they built their shinkansen demolished countless old temples and ran straight through beautiful nature.
People might work faster if you whip them?

I can be, but it isn't generally true. I am very comfy and still motivated.

If I am not comfortable, I might try to change that. Intrinsic and extrinsic motivation I guess.
It works on iphone 7 but the page does a refresh 2 seconds in to a fallback page then again to s “problem occured” page
Brother is pretty much the only printer brand I hear good stuff about anymore. I have no experience with them yet, but when I get sick of my Samsung, I'll probably check out Brother.
If the applicant has graduated from a university, technical school, whatever, then look at the records from their exams there. Also taking into account the average level of the university, technical school in question.
I once cost my employer a bunch of valuable data due to a bug in my code that the second I discovered the data was gone I knew why it was gone because I understand inodes and their relationship to filenames.

That's to say it's information that is useful to have in your head if you're an SRE, just part of understanding Linux fundamentals.

That's not to say it was a good question. Despite my encounter with that bug in my code I still wouldn't have answered the question correctly. Filenames point to inodes, inodes point to data. The word filename might not even pop into my brain when thinking of inodes in isolation.

Also it doesn't show the full picture, I'm not at all sure I have what it takes to be an SRE let alone one at Google, that I sort of know what an inode is says nothing about if I can properly use that information to make architectural decisions.
Tim Spector: the data explorer who uncovered vital clues to Covid
I'm not a gamer, but annecdotally, the pandemic has given me enough screentime that I've finally been able to switch to Linux as my primary OS. I wonder how many others are in the same boat.
Nowadays OS matters pretty little.

Personally, on some level, I don't even notice difference working macOS, Linux and Windows. Other than platform specific development work, it doesn't really matter in the big picture.

Other than that, only Linux allows me true visibility to its innards. Fast to fix almost any issues, should they happen. And I say this as someone who has for example no problem debugging Windows kernel remotely. Or reverse engineering using Ghidra etc.
> What is the output of the expression below?

> int i = 10;

> **++&&*+p;

> Followed by a myriad of options. Including things like Syntax error.

I consider myself fluent in C and to a lesser extent C++ -- that's a Syntax Error in C, at least.

This isn't a particularly difficult one to spot, but I can understand how it would be if you weren't very familiar the language.
If you've collected any links or other resources on this topic I'd love to learn more. I'm interested in this and what we can do about it.
I'm using IPFS to host generative media for https://pollinations.ai and it has been quite stable and fun to use. I think it has been getting a lot better in recent months.
Googler here. At some stage of the interview process, we have to check whether you're able to code, there's no way around it if you're applying for a coding position. So yes, we'll have you code the solution to a problem. Of course in the real world we'd use a library or look up the algorithm on stack overflow like everyone else. Good for you if you came up with a workable algorithm for the problem quickly. But that's not the only point of the interview. An important goal there is to check if you can really code. We don't usually care if you don't know find the perfect algorithm (unless it's for a senior position), and in fact it's a desirable property if you don't, because that allows us to see your thinking process. Some of the best interviewees I've had, they didn't have the right solution, but impressed me with how they thought about the problem and dealt with the situation of having a problem in front of them that they didn't know how to solve. How they considered possible boundary conditions and restrictions and extensions. Someone saying "yeah, this is just depth-first-search" and then spits up a memorized solution gives me zero insights on whether the candidate is good (and will likely not allow me to write great feedback on the candidate, unless they're able to sell me that they understand what they are doing and why and how). It's usually expected that most of the interview will be taken up by you implementing some algorithm, and it's expected that you won't get every detail right.

We do NOT require you to produce token-by-token perfect code, and nowhere in the process will I ever have to give feedback on whether the code produced was actually valid. So maybe you misunderstood your interviewer's intention, or something else went wrong, or maybe they were just joking. But it's not the interviewers task to copy code into GCC and try it out, that'd be a huge waste of time. So let me be very clear and explicit: no-one gets classified as "no hire" because they've forgotten a semicolon somewhere. You messed up somewhere else.

With that said, if a candidate says they can write in a language, we expect them to know the language, its idioms and at least parts of the standard library. Not every nook and cranny (e.g. I'd often instruct candidates "just pretend you have some library that implements a heap, and invent an API for it, I don't care about that part"), but if you call "strlen" in the termination-condition of your for-loop instead of before, or do other stuff that shows you don't know the language well, that's a red flag. After all, we expect you to be able to write production-level code that servers billions of users.
If you start with "I'm sorry if you find this question offensie, but recently we had a wave of candidates who had problems with basic things so we need to start from the beginning" and the candidate still feels offended, well, they're being offended too easily which might cause problems in the future.
Tips and Tricks to Ace the Certified Kubernetes Application Developer
I really well versed with Python, Golang & Rust. I will not choose Rust for interviews. For me, Python is much more productive in an interview setting.

But I get what you are saying though.
Not updating a web browser is a fantastic way to make your computer very insecure.
I understand the desire to keep things the same but personally I would value security above that.
Software engineers can learn everything and can take on whatever tasks. Small teams may look for specific skillsets they need, big companies can afford to hire people then find something they can work on later. Also, they are more candidates so they are basically doing a filtering rather than looking for the right candidates.

Yes, there are 3 months trial period, but Google will have thousands of candidates every week, they need to quickly filter them rather than evaluating them equally. Many people interviewing don't even know the job they are interviewing for, that's the problem of big organization.
Isn't as easy to shatter in handling too, lacking stress concentrators.
I missed my chance on this. I hope I'll get another after my kids grow up a bit. I believe this is called "sabbatical" (except in this case it'll be self-funded).
If anything, the “hunting down” would be for the purpose of hiring them.
> JDs have successfully backed judges into reading ministers minds.

No need for mind reading, if there is no documentation for the process (meeting notes) or its results they probably didn't do it correctly if at all.

> 5. Nobody has an actual alternative.

Weird, the road in question was at points in (recent) history completely abandoned. Then gained a higher status despite reports pointing out how irrelevant it was, until it was finally upgraded because it was easier than fixing the A30[1]. Either the Wikipedia entry is lacking some important information that makes it necessary to build a road through Stonehenge or no one looked at the alternatives present in the past.

[1] https://en.wikipedia.org/wiki/A303_road
I worked at Google and did a fair share of interviews. Two observations:

When you have 3 interviews per week for a prolonged period, you, as an interviewer, are not going to do a stellar job every time. What's worse: you will develop a routine and it becomes very easy to give candidates that do not fit your routine a lower grade. It takes effort on the interviewers part to recognize talent that perhaps doesn't fit your routine or your expectations. If you are not going to end up being a bad interviewer you also have to try to relate what you see in interviews to what you know about work.

For instance I _never_ asked people to code live (mostly on whiteboards back then) because it just isn't a relevant exercise. And I was kind of horrified at experienced interviewers who asked people to code and then got obsessive about small details that the tooling would have taken care of. Absolutely pointless.

The only piece of advice I found useful from the interview training was this: this is the candidate's big day. For you it is a chore, for them it is their big chance. Keep that in mind and respect it. I kept telling myself this for every interview - and some days I felt really terrible because I wasn't properly prepared.

The other thing that horrified me was when we let inexperienced people who had been out of school for less than a year interview people. These interviewers barely knew how to write software themselves, and they'd get even more hung up on irrelevant stuff because they simply had no idea how to be software engineers.

I doubt that I would have done very well in those kinds of interviews because this isn't how I work and it certainly isn't how I teach people to do problem solving. Problem solving requires more time because any even mildly tricky problem worth solving tends to have a lot of facets far beyond picking an algorithm or knowing how to code it up. That's the easy part because for that part, you have books, papers, tools and other people to seek advice from.

Junior programmers right out of school with no engineering experience have no business interviewing developers. They make poor and overly judgemental interviewers and only rarely are able to spot talent if it doesn't fit their template. They also aren't going to fight for candidates that may not fit the imaginary template, but have some special gift because they are junior programmers. It takes a certain amount of balls to say "I know you think this candidate is rubbish, but I see something here and I don't care what you say, I am going to insist".

(btw, statistically, this used to be a good predictor for later success: candidates that were somehow "controversial" in that they didn't make the grade with some interviewers, but displayed something that made other interviewers fight for them)
I wish this was the case in London. I'm at a FAANG and have recently done a few interview loops with non-FAANG companies based in London (as well as a few that are based in SF but hire remote in London) and all were offering <40% of my current TC. When I told them my current TC they offered 50% of my current TC.

Starting to wonder if there is simply no chance of getting even close to the FAANG TC and whether I'm stuck for the 4 years at my current job.
I'm so thankful that Valve is embracing Linux. They obviously have commercial interests behind it and fear the Windows Store [1] and vendor lock-in by Microsoft, but they have made gaming on linux better, even for non-steam games and embraced the open source ideals of linux, at least for their work on steam os and proton. I'm happy I don't have to have any windows systems for gaming anymore and I pretty much have valve to thank for that (and all the other great people working on wine, lutris and co of course)

[1] https://www.bbc.com/news/technology-18996377
I think it matters a lot, specially on machines that are not that new, with modest resources
This is just a job ad. Is that... allowed here?
I’ve applied to and been rejected by Codecademy 3 times. After the 3rd time I decided to build my own just to prove to myself that I could and that the interview process is broken:

https://codeamigo.dev
I'll risk giving an impression of being set in my superior ways: just type Ctrl-D as it suggests? It works for every readline-like environment, like shell, ssh session, redis cli, and so on.
Windows has no epoll(), but of course that doesn't matter for games.
Is "moderate to high proficiency with WordPress" congruent with "PHP developer"?

Every time I needed to do anything significant with WP I ended up writing PHP.
nope: https://news.ycombinator.com/newsfaq.html
At work in 2011 but only because a colleague was really into it and could smash out a good XSLT in an hour, so I ended up using that and making modification (maintaining it). The XSLT was for taking really awful responses from an API and making them more palatable.
Most apps do get this wrong. I use Taskwarrior and its ability to tag tasks, combined with the ability to schedule them for a future date and not show them until that date, is essential. I used to use Orgmode for the same reason. I use the tags mostly like GTD contexts: if something can wait until a routine meeting with a particular person, I tag it “discuss” and with the person’s name, and more importantly I routinely check these lists when meeting with people.

This can be done with no app at all though, which is what 43 folders is all about. David Allen says often in his book that the exact app or notebook you use doesn’t matter as long as it works for you.
Well, my Samsung doesn't work reliably over wifi from Windows and Mac, so this issue is hardly limited to Brother and Arch.
More than a decade ago I had an amazon interviewer write some perl on a whiteboard, and ask me to find the error.

There were two - I pointed out both and they didn't seem super happy about it. To this day I'm still not sure if one of them was an unintentional error.
And sometimes better (like Classic Wow).

I only ran into issues with Rust(which is getting support) and pubg because of anti-cheat and the fivem mods for gta5 (something about lack of support for shared resources).

But it's working so well and so much less weird stuff going on compared to windows and osx.
Yep. This interview process is pretty much why I'm out of the market. Could I increase my comp? Probably. But the hours of my life are slipping by, and those never come back. I used to enjoy the hours I spent learning to code. Absolutely loved it. Doing this Leetcode crap just to jump through hoops is a miserable waste of life, though.
“servers billions of users”

And therein lies the problem.
Show HN: Finding the next markets just got easy
The inode question is tricky. It is certainly not something an employer should take for granted you have memorized. But the answer can be reached by reasoning, at least if you know something about filesystems and the concept of hard links. Which you probably do if you have read the "ln" man page.

It is still a pretty poor question, I remember getting a similar kind of question when I passed through the (at the time, in Sweden) mandatory conscription testing, where you are tested for which role you best fit as a military conscript.

One question on the intelligence test was: "What is heaviest, gasoline or water?". I did not know how to approach the question, I had not memorized the density of gasoline and I didn't think an intelligence test could have assumed that either. I was stumped. How could that be an intelligence test question? Only afterwards did I realize that the test creators probably assumed that knowing that gasoline floats on water as common knowledge, and if you were intelligent enough you should be able to derive the answer from that. I think the inode question is similar.
This is quite interesting, I've been considering making a todo app to help with ADHD. I've definitely experienced many of the same issues mentioned by the author, and even some apps labelled specifically for ADHD seem to fail on many of these issues.

If it's a chore to add a task, I won't add them. If it's a chore to go through tasks, I won't come back to the app.

It's also a really important point about some tasks being inherently different in scale to others, and the importance of separating them.

I feel like many todo apps focus too much on being a "todo app" rather than actually trying to get you to get things done. All this tagging and categorizing and such are features that take effort and time for me to manage, which in turn help make those apps into huge graveyards of stuff to do, which in turn make me want to not open them ever again.

IMO a todo apps that is blank most of the time is the best. Meaning, you haven't got anything you need to do. Help me keep track of small tasks, and repeating tasks, and let me either complete them or postpone them. If there's something I've postponed too many times, just delete it. It shoudn't become a notes app, it's about getting stuff done.