jkeisling/hacker-news-corpus-2007-2022 huggingface dataset:
>From company's point of view I can't think of any advantages of forcing programmers come to office every day. Why is this style of working so unpopular between employers?

I have seen companies on both sides, where remote work is successful and where it fails, and where it is successful, it is built into the business model, starting from the hiring process, to select individuals who are technically competent, and who also have demonstrated the ability to work independently. This severely limits the number of people that qualify, and limits the company's ability to grow aggressively. Some companies do not have the option of slow-and-steady growth, due to investor involvement. Most others are going to prefer reasonably aggressive growth (more money), and that means foregoing remote work in favor of hiring workers who are more easily replaceable. If a company can hire from the pool of workers who are technically competent, but who need a little oversight to stay productive, and that process works to produce the output needed, then that is much easier to achieve than having a long and expensive hiring process where the company delays growth while waiting for the perfect new hire.

>There are less distractions when you work from home.

For a lot of people, this is not true. Where it is true, it's still difficult to justify a remote work policy. Distractions can come from a significant other, kids, pets, roommates, a TV, or internet access. If you are single with no kids or pets and live alone, it's true you at least have control over most of your distractions. In situations where the quantity of distractions is fewer, there are still distractions that the employer has no way of detecting and managing. Suppose your coworker chooses to watch TV while he works, which leads him to write code with more bugs. He still hits the number of commits (or whatever metric), but his reduced productivity is difficult to detect and correct. What if you are unusually disciplined, and your estimate of other people's discipline is wrong by a significant margin? In that case, everyone working from home could be a huge hit to productivity. The employer can't have a policy of, "All single employees without kids, pets, or roommates, and who are also very disciplined, may work from home." As someone who does work from home 2-3 days per week, and who also has a spouse, a kid, 2 dogs, TV, and internet, I find that there are a lot of days when I'm working from home that I would have gotten significantly more done at our office.

>Some bosses _need_ to see you in the office otherwise they feel uneasy and lose sense of control over a team. This is both funny and sad..

This is probably not the man keeping you down, or a twisted need for control, or whatever. This probably has much more to do with the chosen business model, and the fact that most employees are not going to be a good fit for remote work. While you may be the ideal case, that is definitely not the norm. The company has to set policies based on all employees, and unfortunately that means the weakest link wins.
I was wondering why they didn't borrow java SimpleDateFormat

But then I noticed they decided to tackle the dd-MM-yyyyTHH:mm:ss problem AKA crazy case. Which is kind of noble.
I have no experience with this, but is it really that difficult for a business to pay its employees in cash if requested?
I'm not sure there was a control in these experiment.
Yep I have passed on even bothering to go to an interview because one of the people on the board was "dodgy"
I wonder how this would perform on iPhone 6's (or others) high speed camera.
Because "Becoming Steve Jobs" was mentioned many time recently, when I saw 'Jobs' in the title, I thought "Is it another article about Steve Jobs and that book"?
No clue what that is meant to mean.

SFTP is as secure as any other SSH connection and people use those extremely regularly to remotely administer hosts which lack a VPN.

Aside from terrible Windows support SFTP is likely one of the best secure remote file transfer protocols around (in particular for freeform file transfers, rather than structured like AS2 or similar).

Certainly better than FTPS.
Microsoft's hardware has always been excellent. I wonder why they insist on making software :-P
I have telemetry upload turned off which appears to then not gather the data (which is perfectly reasonable) rather than just not upload it.
It's a sad day when advice to be pragmatic is downvoted. Sure, I shouldn't have to be extra careful when talking to police officers because they should have a duty to protect innocent citizens. But I only get one life, so I'm going to to, just as I'm going to watch for people running red lights when crossing the street and staying in safe, lit areas when walking home alone at night.
If it's impossible to checkmate then it's a stalemate. So if one side has one king and the other side one king (or even one king and a pawn, bishop, knight or rook) then it's a stalemate and the game ends.

edit: forgot you can checkmate with just a king and a queen
We tend to be the most affordable employer of record with quite some margin.

Paying contractors is free through us.
Going from your original numbers (which I didn’t check), a play current pays out just under half a cent (1/230), and you’d like Spotify to pay around 5 times that (avg 2c). Spotify distributes about 70% of revenue to rights holders so you’re asking Spotify to pay out ... 350% of revenue to rights holders?

Spotify could almost certainly be charging more, but it’s already incentivised to maximise revenue, and it has competitors, so it seems like it’s probably found the market value of a play?
I would agree there are people that are buying in now that think there's no risk that Bitcoin will go down, and think it's only going to keep going up, and will probably sell as soon as it drops and lose a lot of money.

There's definitely a risk it could go down. Bitcoin has been super volatile in the past, and has cratered to 20% of its price before and probably will again. Might even be relatively soon (within a year, I'm guessing).

But people who have held on to the asset through those dips are now doing incredibly well, assuming they sell before the next major dip (and probably even if it they don't, 20% of $48,000 is $9600, and if they bought while it was $3500 a year ago, that's still triple what they bought it at).

People who have bought and held since it was $220 back in 2015 are likely doing extremely well.

There's very few assets out there that can offer 200x returns in just five years.
Okay, I'm just not used their taste.

Nothing is better than fresh potatoes, made by my wife with feta cheese on top of them and beer. I like them to have some meat in them.
If we know where the yellow dots go, just print a yellow rectangle over them.
Some more of the Zappos vision might actually bleed over into Amazon (the article mentioned the Amazon distribution center that followed the "$2000 to quit" Zappos approach).
I'm downloading some kind of font manager from Extensis right now. I was thinking I'd just use the copy of ATM Deluxe I have (and paid for) somewhere...except that it doesn't support Windows XP. And Adobe discontinued it five years ago.

Brilliant.
This was interesting:

When employees log in to their computers, we ask them to look at a picture of a random employee and then ask them how well they know that person -- the options include "say hi in the halls," "hang out outside of work," and "we're going to be longtime friends." We're starting to keep track of the number and strength of cross-departmental relationships -- and we're planning a class on the topic.
Agree. 1 year.
Right. I had the same question about directly comparing the GDP figure versus the debt figure. It'll certainly help if someone knowledgeable lays bare the important factors and how they bear on the "rising debt" issue.
Not a surprise they got hacked...

These two issues (the hack and how they treat bug reporters) challenges the way I see slack as a company...
Your entire portfolio is very well executed, I might not agree about the usefulness of them all, but you've done it nicely and professional. An inspiration! Thanks for sharing!
I've been thinking about a clean way to handle multiple inheritance (for mix-in style classes) in JavaScript for a while. I think this approach is the best I've come up with so far.

There's more documentation (and source) on this github repo:

https://github.com/mckoss/namespace/wiki/funcs.js
> Most of all , I would not feel comfortable handing out my card to small shops or vendors that I hardly ever visit.

Why? Fraud protection is the same, and smaller vendors are more worried about their reputation in the community than, say, Target or Best Buy.
Good call, sir! I'm expecting a torrent of replies now with obvious examples I'd forgotten about(!) :-)
Read my post as high sarcasm...
Maybe try using an RSS reader and over time build up the exact things you want to read. Eventually, you'll have a perfect feed of things that interest you (well, maybe not perfect, but close). Another option is Reddit, which has the ability to subscribe to specific groups that show up in your feed. It's community generated if you would prefer not to hassle with building an RSS feed library yourself. I find myself coming to HN for startup stuff and Reddit for more directed conversations about Python or Ubuntu since they are already filtered and show up when I'm logged in.
> This is pointless semantics.

Not really. If I mail something to you, I pay the postage. That's how mail works.

When I connect to the internet, if I request something from you, we both pay our respective ISPs to make it happen. That's how the internet works. And the limit to connection speed has historically always been the last mile on one side or the other.

So what Comcast did is pushed the congestion from the last mile to a peering point by purposefully not upgrading the peering point. And predictably, what happened is that the last mile wasn't the limiting factor anymore. According to 20-30 years of internet history, that's breaking the internet. Maybe not Comcast's contract with their customers (since they can unilaterally change that at any time) but definitely in terms of expectations.

That would be like gas stations suddenly advertising the pre-tax price on their signs only once you're done pumping $30 worth of gas they charge your card for $40 because of the taxes. Might not be explicitly illegal since so many other products are advertised on the pre-tax price. But it would be breaking with decades of convention. People might get really pissed as a result.

Sadly few of us have options to get internet aside from Comcast, where as in the gas station scenario we could easily stop patronizing BP or Texaco or Shell or whoever. That also gets people riled up. And rightly so!
wycats: IE 10 and up, Safari 6 and up, Chrome, FF, Opera, last 2 versions.
You can exercise the option to buy the Seaboard right away.
Because twitter will constantly try to show you content you don’t want in order to engage/enrage you.
It doesn’t work that way. That’s how it should work, but that’s not how it does work. It only proxies your request, hiding your IP, not hiding the fact that the email was opened at all.

https://blog.filippo.io/how-the-new-gmail-image-proxy-works-...
My current car is a BMW X1, which isn't really a big car at all. But I do need more space a few times a year, usually on extended trips.

A bigger car of a non-premium brand with a small engine would probably cost about the same in taxes, insurance, consumption.

F-150 is total overkill of course.
Likewise. Long live WebOS!
In this particular example (S3), I don't think this is really a concern.

Anyway, I'm curious... what components do you run into that don't support this yet? At least in your examples I can't think of any major players that don't do HTTP/2 out of the box, except, well, old versions.

Is this more of a hypothetical? In my experience HTTP/2 is pretty much ubiquitous for anything current.
I don't "remember" what happened last time "we" culled cats, so what happened?

(If you're alluding to the idea that the "black death" plagues were worsened by cat culls, that's an oft-repeated story but somewhat dubious with regard to verifiable facts. Cats themselves can carry the plague bacteria & transmit it to humans – eg https://www.nytimes.com/1994/04/08/us/house-cats-spread-huma... – and even regions where cats are superstitiously cherished suffered repeated plague outbreaks.)
This is also clogging the roads with traffic, wasting our time in traffic, and polluting the air. If you can't afford to move closer to a new job, you'll have to commute.
It's more like "why are they downtown?" they have no good reason to be there, and many bad things they're doing which are already illegal. It's not really nimby if i live in the midwest and am just scratching my head like.. "that dude is doing drugs in front of a cop in that video, why isn't the copy arresting him?" Is that compassion? Lol
An app for team collaboration that only works on one mobile OS? Should we start asking what phone people have at job interviews?
If you want to collaborate I am working on a lot of cool qfin related projects. Hit me at my email in the profile. Cheers
Emily Short https://emshort.blog/my-work/
It's explained at the end of the Eagles song Hotel California:

We are programmed to receive.
You can check-out any time you like,
But you can never leave!
I've been a customer of both for years -- in Linode's case, since 2009. Your comments are coming across like sour grapes, so I think this is a good opportunity to hear about some of Linode's mistakes from a longtime Linode customer.

First, you guys had the customer support interface compromise in 2013, and the worst part about that was the way that it was handled by your organization. Linode wouldn't own up to the compromise initially, dragged their feet on announcing anything about it, and then tried to downplay it.

Then there was another similar incident in 2016, and, amazingly, the response from Linode was nearly identical to 2013. No lessons learned. After that, I started seeing influential people on HN say things like, "don't use Linode". I stayed on Linode, but I also started using DigitalOcean after the 2013 compromise and split my hosted services evenly between the two of you after 2016.

DigitalOcean aggressively iterated multiple aspects of their products in that time period. They announced block storage in 2016. Your customers immediately started asking when Linode would come out with a competing service, and that didn't happen until 2018. Here, it was Linode rushing to build a DigitalOcean feature.

Linode initially focused on expanding RAM and disk space for your customers' instances at the same price points. Every year, you'd announce, "hey, we're doubling your RAM!" or some such thing. It was awesome, but I also thought at the time that you were shooting yourselves in the foot. How many customers looked at that and went, "yep, cool, now I can downsize my Linode and give them less money each month"? I know I did, at least a couple of times.

Then, you chose to try to compete with DigitalOcean on price. As a long time Linode customer, I never wanted that. If I want a $5 VPS, I'll just go to DigitalOcean. Hell, you shouldn't even want me as a customer for $5. Let them deal with me instead. I wanted Linode to be the larger, slightly more expensive provider with the even better support.

I've had to deal with Linode support a few times over the years. They've mostly been awesome and first class. I've never been unhappy enough with Linode to want to leave altogether. Both of you should be focused on eating AWS, not each other; showing up to a competitor's HN thread to complain about them being copycats is really poor form.
As a mathematician, rationality is very important to me. (It is sufficiently important that I believe in determining my own criteria for rationality, rather than using someone else's list.)

In this spirit, I have an infuriating (to others) habit of reflexively arguing against someone else's position. (It was originally born out of the "search for counterexamples" mindset of a mathematician, but now it's an unconscious behaviour.) This habit is so comically ingrained that, if the person to whom I make this argument switches his or her position, then I will in turn switch to arguing for the original position.

I don't know whether this counts as highly rational, highly contrarian, or just annoying.
Yes—that's a fair point. It comes up a lot in the slightly (but not entirely) different context of press releases: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&sor..., which are a lede-burying genre par excellence.

The current article is arguably a borderline case, but it takes a long time to get to the ethics issue and I'm not sure that's what the bulk of it is about. Maybe it should be, but that's more of an editorial point.
But the Federal Pension is miles better than the equivalent and eventualy the IRS is going to wake up and start taxing perks like "free" food
Because it was wrong.

It's not a penalty, it's just a downvote. Penalty would be flagging.

Honestly sometimes I wish people had to justify upvotes...
It is a more descriptive term, too, because the mechanics are almost always still the same as "adventure games" (where you find objects and apply them in puzzly ways to move to the next area, etc.)
Coal, steel, water - and now this?
I don't use these hints for verification; in fact, these hints don't verify anything.

It is trivial to create an integer type in Rust that only accepts certain values, and doing so doesn't require these hints, e.g.,

#[bounded_int(start, end)]
struct MyBoundedInt(i32);

creates a type called MyBoundedInt that never will take a value outside the range [start, end); this can be proved formally, i.e., there is no safe Rust program that can violate that. No need to run any kind of verification on top.

The place where Rust differs from Ada, and the reason I use these attributes, is to enable the layout optimizations that Rust performs (e.g. Option<NonZero> having the same size in bytes as NonZero, and many others).
The same goes for me as well - however I wonder what the motivation behind watching coding livestreams is in this case? There are some people on twitch that have multiple hundreds of viewers during the multi-hour (!) live coding sessions...
> This is why no language is "just faster" than another.

No, that is not what this is. Rust IS faster than most languages on earth.

This is FACT.

Some tools ARE better than others. You only heard the "opposite" when a outlier happened or a user misunderstood how use the tool.

Also this apply to interpreted languages too!:

http://lambda-the-ultimate.org/node/5075

IF you hit their sweet spots.

PD: Just check the Rust reddit. Tons of case of naive newcomers with massive improvements on speed/performance just porting to Rust.

---

This kind of history is similar to "A virus happened on OS X/Linux!" Then say "No OS is more secure than others!" is a massive flaw. Some are more secure. Only this time is news precisely because is RARE!
I'm always amazed at people who think that programming languages and typing and editing are the hard part of what software engineers do. I spend much more time trying to understand the problem that I'm trying to solve, and to make decisions about how to do that in a way that I won't regret.
I develop a FOSS adblocking DNS stub resolver and client. And I believe, DNS-based content-blocking will become drastically ineffective as it gets more popular.

Besides CNAMEs breaking all sorts of assumptions a client software makes (and hence also causing security headaches in the process as outlined in the paper), there are a couple other DNS cloaking techniques that the paper doesn't discuss:

1. ALIAS records (not standardized? popularized by Route53) hide CNAME-like pointers. Another variant of this is, some DNS nameservers (like Cloudflare) flatten CNAME records (aka transparently ALIAS endpoints): CNAMEs aren't sent with the answer, that is, you're straight up served the A/AAAA record with IPs (which could easily be third-party). DNSSEC doesn't help here, afaik.

2. The shiny new SVCB/HTTPS records open up another avenue for DNS cloaking. For example, consider this (unverified if correct) record with a chain of pointers:

example.com SCVB IN 0 example.net
example.net CNAME IN example.org
example.org SVCB IN 0 example.us
example.us SVCB IN 1 example.uk (ipv4hint=2.2.2.2, ipv6hint=2:2::2)
example.uk SVCB IN 0 example.de
example.de CNAME IN example.fr
example.fr SVCB IN 1 . (ipv4hint=..., ipv6hint=...)
example.fr SVCB IN 2 example.es (ipv4hint=..., ...)
example.fr SVCB IN 3 example.it (...)
example.fr CNAME IN example.ru
example.es CNAME IN example.it
example.it SVCB IN 1 . (...)
example.it SVCB IN 2 example.ch (...)
example.it A IN 4.4.4.4
example.it AAAA IN 4:4::4
example.ch SVCB IN 0 example.ru
example.ru SCVB IN 1 . (...)
example.ru A IN 3.3.3.3
example.ru AAAA IN 3:3::3

(the above is missing the example where targets follow "port prefix naming" viz. _443._https.example.com)

Though it remains trivial to uncloak domains hiding behind SVCB/HTTPS records, implementations have to be careful about what they let through. Flattened CNAMEs and ALIAS records; however, to my knowledge, remain undetectable.

But: All indications are that it is foolish to rely on DNS to discern between first-party and third-party. I mean, I can already run www.example.com on Netlify, app.example.com on Vercel, api.example.com on AWS, and cdn.example.com on Cloudflare... and those endpoints could very well be running anything the cloud providers want (third party).

IP based firewall doesn't suffer these shortcomings, but then, enforcing IP blocks are complicated by Virtual Hosting (multiple web services behind a single IP) and IPv6 (too many addresses to curate and block).
Yeah but none of those are inherent advantages of Lisp...

I really don't get this sort of "Lisp is cool" article touting advantages the Author was impressed by during their childhood that have long since been overtaken by technical advancements in other languages.
Pint-sized cans of beer are rare, many beers come in 500ml cans. 330ml cans are common, especially for craft beer.
Try the Graviton servers on AWS. Compare r5.large to r6g.large. Way cheaper (.10 vs .166) and faster for the things I have tested (also, no hyperthreaded cores). No doubt in my mind that folks are going to be using them in cloud for sure. This isn't comparable to the stuff you listed. Not even counting the M1, which is crazy.
Thanks! Seems like something that could be added to KiCad, well, if I could decipher the API.
My belief is that your first goal should be cognitive optimization. I.e. make it simple and clear. That includes using hash maps when that is the proper data structure since that’s is what is called for at a base design level.

The next step is to optimize away from the cognitively optimal, but only when necessary. So yeah it’s really crazy this was ever a problem at all.
Thank you for your kind reply. I totally agree better doc is needed to tie the actual code to its intended functions and architecture. One problem I've had repeatedly with writing this kind of doc is that it immediately goes out of date as soon as you refactor -- which we do often! That kind of low-level doc isn't something you need every day, but when you are chasing an ugly bug, it can be awfully helpful to have some plain English explanation how two functions relate to each other, or how their arguments are used -- since this is the source of most bugs.

Right now, it's very difficult to get doc that fully aligns your architecture diagrams with the actual code, function names, parms, etc. To us, this is the Holy Grail and part of what we are trying to built at Mimix. Using our MSL language, we plan to bring some of these kind of reuse and code diagramming features to the wiki editing environment.