You can read my comment[1] on that post, we actually both independently discovered this and I made a CLI around it during the flight a few months ago. I just realized I never posted it on HN so i'm posting it now
This is what HN mod-nerdery calls a 'followup dupe' - something that ends up on the front page as a direct consequence of something else that's already on the front page. Since there's only so much front page, you're better off waiting for a less dupey time.
That's a matter of taste of course but the important thing is that they get moderated away. So if you want others to see/respond to something related, add it as a comment to the ongoing thread or wait until the air of dupeyness clears.
It's the important thing because that's what happens so it's useful for posters to know. I just happen to know about it reading the moderation log and also wasting too much time here, like many other users. It is definitely a good thing if you think about it but that's not what I was talking about.
Nice! Is there a way someone can hit the same endpoints while not on a plane? From an environment perspective it’s a great use of time if the API is only available while in the air.
You cant access these in flight APIs in exactly the same way as you can while on the plane, but the same information can be found for almost all flight in the air that use ADS-B, and there are many services that offer this as an API[1]
And if you want to have some fun, you can buy a SDR (software defined radio) for $20 or $30, and receive this signal from the airplanes flying over your house.
I'm not in the recruiting space, but as a grumpy 40something man, I've grown incredibly sceptical of stated timelines, since they're clearly a form of bragging (and hence probably utter bollocks). Even if they were true, it's easy to build some wizz-bang in a few hours after you spent months learning the necessary tools.
Generally, does it add much to question a message in the footer with smaller text than usual, that seems to have been a offhand comment from the author?
It probably took you longer to formulate and write your comment than what it took for the author to add that in the bottom of the README.
It’s in the description of the repository as well. I’m not understanding where the hostility is coming from.
I genuinely want to understand if recruiters or hiring managers take time spent on a project into account when looking at candidates. For example if two candidates implemented some sort of basic API, do they look at the candidate who took two hours to implement it more favorably than the one that took 5 or 6 hours? Should people, in general, include time taken somewhere on a project page? Is there a threshold where it’s more hurtful than helpful?
[0]: https://github.com/NalinPlad/OuterFlightTracker/blob/main/tr...