skysight-inc/HackerNews huggingface dataset:
Perfect analogy! I will be sure to bring this up when me meet for our next sprint.
Last I had checked most platforms don't have much in the way of modifying messages or accessing PM/DMs.

What I wanted it for was a timezone converter, so everyone saw the time in their own timezone. Our group is from across NA, so somebody saying "I'll be on at 6!" can be hard to figure out when dealing with a dozen people from 4 timezones
I honestly do not understand why anyone would just stare at a blank chat window for a minute (or more) instead of switching back to what they were doing (or, in most(?) cases, just looking at a different screen).

It's similar one of your sibling comments which compares a chat message to a person walking up and saying "hello"... They are absolutely not equivalent; it's perfectly alright to not immediately respond to every message you get (or even only giving it a bit of your attention), even if they are not emails.

I wonder if this is a generational thing...
There exists plugin for VSCode which checks for attributes inside template literal
https://marketplace.visualstudio.com/items?itemName=runem.li...
We are all just machines and we work and work until one day we break or are no longer efficient at what we do. And then we are replaced.
I've gone all in, I'm in for life. Emacs has already deprecated at least a dozen apps, web apps, and websites I used to frequent. I'm starting to despise any other software...

...so when does someone teach me the secret handshake?
About 3 years ago I've had issues multiple times in Tokyo with taxi drivers not speaking english at all, thus not being able to communicate the destination. I assume Uber would smooth over that aspect as there is literally no need for communication.
How to Get on Your Bosses Good Side
I believe there is a story along the lines of "Would you rather train people to see them leave, or not train them and have them stay?"
As you ironically tell someone else what to do.
The idea of people needing to congregate into large, dense urban centers while global climate change apparently wreaks havoc on our food supply chain is down-right psychotic.
> a handful of large advertisers decided they didn't like a lot of the content on YouTube and refused to pay for it. The beef is with the advertisers, not YouTube.

No, the beef is with YouTube. They could offer advertisers the option to pay more and only advertise on “high-quality” content, or pay less and advertise everywhere.

Make it a slider with example videos and let them select what they’re comfortable with.

Instead, they went with no choice and arbitrary demonetization cutoffs.

If P&G doesn’t like my shaky repair videos on niche products that nobody else has made, fine. But P&G shouldn’t dictate what’s worthy of advertising or not for every other advertiser AND publisher.
IMHO, a better approach is for u1 to say "nvm, john's got it" before u2 replied.
> It amazes me how most of the other streaming services try to turn everything into an algorithm, via "special radio" stations,

I think they do that because it's the only way to keep people from switching to rival platforms. Spotify's selection isn't that different from Google Play Music/Apple Music/Amazon Prime Music etc. There's also little in the way of community interaction on those platforms beyond "sharing playlists".

SoundCloud at least has a system where you can comment on specific parts of a song. It creates a really interesting visualization of which parts of a single song people enjoyed the most.
Bloodsucking worms from pythons are killing native Florida snakes, study says
This is the "common knowledge" thing to do, but I don't think it's always applicable. If you have an advantage in the market (e.g. are sought after), you can simply present a high figure and either they accept or you move on to the next. By playing the let-them-go-first game, you're implicitly signalling that you don't know where the ceiling is. On the other hand, if you say a high figure with confidence, they may accept it even if they weren't really prepared for that to begin with. Information asymmetry can also go the other way.
aka "Don't ask to ask, just ask" the mantra of IRC for at least 25 years.
And just like Canada abandoned the Montreal (IIRC) goals just before they were due to take effect and destroy the economy, this law has no force or power until it actually goes into effect, starting 6 years from now.

Tldr : it's meaningless virtue signaling.

You want to clean up the planet? Start with the ten most polluted rivers, all in India or China, and the lead smelting industry which was forced to close in the US and then, predictably, moved to China...
Make the decisions for Bear Grylls on his new interacive Netflix show
Apologies, I should have been more clear. I have two companies, however one is the main focus (the enterprise one) whereas the other c-corp is a mobile gaming platform I do in my free-time. You are right though, there will surely come a time where hard decisions must be made.
Well, because the second you look back to the other window and remember what you were doing, it's just going to ding again with whatever their actual question was.
What do you mean by "broken toys"?
Speech is bidirectional, synchronous streams, so you can process it while it's being emitted. Text chat on the other hand commonly is asynchronous and packet-based, i.e. you only get completely formed sentences.

That means with text there's an idle period between the "hello" packet and the followup. Just seeing the greeting and having to decide whether to wait, respond or ignore it is an annoyance that does not exist in spoken conversation.

It's not about the time itself, it's about the uncertain, possibly unbounded latency and the context-switching.

In fact text is not just higher-latency, it also has a lower bandwidth. It's really important to use it efficiently.

For a bit reduced latency and higher throughput they could implement liveposting as some imageboards do[0].

[0] https://imgur.com/HQKEwXE
If you like this you might want to investiage email as a method of communication.
The only way to win is not to play.

I had to stop letting Slack interrupt me. Too many of my colleagues had started using it as an email replacement. So I keep it on a secondary monitor or desktop and only glance at it when I'm done with a task. I don't let its icon bounce/beep/bloop/be badged.

I still try to be respectful on my end and go as far as composing everything I want to say in an editor before pasting it into Slack, gathering links to screen shots and logs in advance, etc. We can still model good behavior, right?
It's worth noting for clarification I'm talking about inserting to construct a set and reading out the keyspace. Not specifically reads, which is I think what folks below are objecting to.

The read side barely matters for the use case we're discussing.
If solar panels were dirt cheap that would be a solution. But the panels are a lot more expensive than the ground it covers. A farmer would probably be better off to just keep the panels year around and grow nothing.
DING DING DING.

I've seen quite a few people only focus on the $300k aspect in HackerNews (and made negative remarks) without thinking about the trajectory.
If the array works at all, we've been reliably able to get /something/ for at least a year and sometimes much more, which I guess isn't too inconsistent with that.

Still, a lot of our problems haven't been brain-related; instead, there's an infection or mechanical damage to the connector pedestal/wire bundle. I'm not sure that the sewing machine by itself will be able to sidestep those sorts of problems.

I would be very happy to see better alternatives. I'm just not ready to switch based on this.
>>The hard part is knowing what can be solved with ML

I’d say THIS is the hardest part by far. It requires a very rare mix of business domain expertise and technical knowledge with regards to ML/DL.
Another similar one, even in person, is someone shouting an (often negative) exclamation and making everyone wait a minute before explaining themselves.

"Oh crap!" <long pause as everyone around is panicking, waiting on what actually went wrong>

Sometimes something really wrong happened and the person is trying to process it. That's cool. But more often than not, it's like "Oh shit!" <2 minute pause as people ask what happened> "I forgot about my cat's birthday!". Thanks for the dose of anxiety.
Also, sorting is O(n), which is exactly what your perfect hash table would be, recursive.
Cool! This is a great list and I will be sure to review. I appreciate it and will definitely try and reach out at some points. Cheers.
Internal politics (Inbox was a clear threat to Gmail UI) and product adoption cannibalism
I actually wasn't aware Reed was even on the board, but this makes sense considering the potential conflict of interest, as Facebook wants to push towards more video-based content (such as long-format videos delivered via IGTV).
Actually, they do! This is a frequent misunderstanding, but buyer's remorse is a common thing and a lot of folks return the items that they've bought because they're unsatisfied with it. Even if it is 5% of all customers, the numbers will add up really fast for Amazon.

It's quite clever if you look at it from an aggregate perspective. They're casting a wider, second net to catch the fish who slip through.
Buffet streaming killed it because it's cost-competitive to the consumer, period. That's a triumph of capitalism.
cool! you got a link?
Yes! This is something that is not just about developers and seems to be a huge gap in hiring.

Go look at any big company job listings. There are many positions that have no "entry level" roles. The lowest level of experience will say "5 years of {x}".

If you're a company that does not take people without experience, where do you think they're getting the experience? You're relying on other companies to train your employees, and naturally you're not getting a chance to create the exact employee you need.

Hire people that are intelligent, humble, and willing to learn. Ignore credentials, and promote from within. In most situations, you'll get the right result.

Aside: The weirdest part is there are some positions that seem to not have entry-level jobs anywhere in the industry, you have to sneak into them. For example my girlfriend is a "Brand Strategist" at a web design agency. This is what she always wanted to be, but when she was applying it seemed that every Brand Strategist job required 2-3 years of Brand Strategy experience. So she applied to her company in a role she didn't really want and then basically talked her way into the new role. Obviously she's doing well and she will never face this barrier again. But that was a stroke of good fortune.
I'm a remote worker too and have been for over a decade.

Please, just put it all in with the message: "Hi. I have a quick question if you're available. Let me describe it as best I can here to start: ..."

This way even if I was not available to respond immediately, at least I have some actionable information when I do reply.
This fails to account for the fact that in the Japanese home market fuel efficiency was already a key requirement
It's hard to understand until you've worked at a place where you and all your co-workers are context-switching between 5 projects all due yesterday and everybody is pissed off. I didn't mind the "hello" at my older jobs where I actually wasn't stressed out.
maybe that's a business model. go find high ranked content on HN from a couple years ago, make a site about it, put some ads, and pretend it's something new.
I think my reply would have had more context in response to a sibling reply made by another poster:

Consider the scaling factor for salaries; My salary is on the high end in my area, but would be on the low end of a living wage in the Bay Area.
My salary is in the neighborhood of 120k; I'm a senior-level engineer with almost a decade of experience...

So think about the trade offs. If you’re young and single, the tradeoff between a one bedroom in a major city anywhere not on the west coast and the west coast and the difference in the salary you can make is well worth it.

In most major cities a junior developer will make $60K and can probably find an apartment for $900/month in a decent part of town. If they work on the west coast and get $250K and find an apartment for $2400K/month, that’s a tradeoff worth making.

10-15 years into your career, you may already be married with kids. That $120K he’s making can easily buy a 3000 square foot house in the burbs, brand new build, great school system and close to work for $350K. This is from personal experience (not the salary, the price of the house). Now that tradeoff between $150K and $300K-$400K doesn’t look so appealing when you can’t live nearly the same lifestyle on the West Coast that you could live on much less money

If he’s like me, he’s probably built a local network where any door he wants to open locally is probably already open to him.

In my case, I’m 45, but because of $bad_life_decisions, I only started taking my software development career seriously a decade ago. But I do have a great local network, skills that match what the market demands and the house in the burbs with the wife, the white picket fence and 2.1 kids.

I don’t really need new doors opened to me. As soon as the youngest graduates and I’m willing to travel, I am already in the position of being a high earning “consultant”. Not bragging, I have been working over 20 years, I should be able to consult somebody
The reason people still care about Unix pipes is because you can take a bunch of arbitrary commands and string them together in a way that produces some useful results. Moreover, you can configure each pipe to do different things depending on what you need at the moment.

What stops you from stringing together a bunch of arbitrary objects to achieve the same effect? Well, a bunch of things:

1. Verbose syntax of the language.

2. The need to compile new code.

3. Early binding that stops you from calling things you don't know about before compiling code.

4. The fact that objects can't just take arbitrary method arguments.

#1 is self-imposed.

#2 is solved by JIT compilation and some other technique.

#3 is not a problem in dynamically typed languages.

Most importantly, #4 is explicitly what polymorphism in OOP was supposed to solve. Poly = many. Morphos = shapes. The idea that the object adapts to the messages you send it.

With this in mind, ls -a | grep “gear” can be interpreted as code that does the following:

1. Send the object representing 'ls' a message with -a argument. This will supposedly construct a list.

2. Send 'grep' object a message with "gear" argument. This will construct a configured grep instance.

3. Send response from #1 as a message (or stream of messages) to #2. This will generate a filtered list.

4. Send the object resulting from #3 a message that would request a console-friendly representation (e.g. a string with codes for color in console).

5. Display #5.

This is (with some caveats) very close to how OOP was envisioned in the 70s and early 80s. Except pipelines are a very crude way of stringing things together. You can get way more sophisticated with objects. E.g. :

https://www.youtube.com/watch?v=I9LZ6TnSP40

https://www.youtube.com/watch?v=if72CFsF_SY
Or maybe it's just that an asynchronous medium has different etiquette than face to face?
That 'feature' does nothing. I've tried everything, but getting youtube to stop suggesting to me videos from Jimmy Fallon or Conan Obrian or any of those other 'lame obsolete-format "late night" shows for tepid boomers who miss Johnny Carson' seems to be totally impossible.
Yeah agreed - it's more irritating than anything else. It anecdotally also seems like the people that do this also tend to be more annoying and slower at typing in general, but maybe I've just conflated the two.
Yep just incrementally better.
I'm glad this is the top-rated comment--it teaches me that there are people who are totally different from me! I'm a remote worker who is sharply annoyed by "Hi" [send] "QQ" [send] [wait 30 seconds] "[question]". I find it impolite, and I am honestly (honestly, honestly!) surprised anyone feels otherwise. It's nice to be able to express this here; there's no way I could say it at work!
There's a cross-platform (win mac lin) app called Lectrote[1], by Andrew Plotkin, built on Electron. For Android I use Fabularium, TextFiction (both can do speech) and IFMapper tool. Can't say anything about iPhone.

Speech output is supported in clients Frotz[2], Git[3].

Talking back should be possible with OS methods or Sphinx or whatever. I think speech input for IF case is more about 3rd party tool for controlling terminal with voice.

I also thought about one-handed chord keyboards, so you can kick back or walk and listen while typing with one hand. Unfortunately, there're no practical solutions and prices for keyboards like "twiddler" are insane.

[1] https://github.com/erkyrath/lectrote/releases
[2] https://www.davidkinder.co.uk/frotz.html
[3] https://ifarchive.org/indexes/if-archiveXprogrammingXglulxXi...
> why are you falsely assuming

JudgeWapner: 8 days and -2 karma. Nice track record so far.

Edit: I got down voted for calling out a troll? Oy.
While we're telling people how to talk: please don't tell people how to talk.
To be absolutely clear, we don't know shit what Socrates thought of Democracy. Socrates wrote absolutely nothing down. We do know what Plato thought of it though, since he is the author of all the dialogues.

Moreover, Plato came from a wealthier, more prominent family than Socrates and he had family members on the side of the Tyranny of Thirty or whatever they called themselves, anti-democratic revolutionaries that claimed governance of Athens for a few years and weren't terribly liked.
We were acquired in the early 2000's for something less than the preferences owed to the VC, so they did sort of ok (by everyman standards, doubled their money in four years) and everyone else just chalked it all up to a life experience :).
Haha I remember at Google, we had an escalating series of go/ links for people's chat preferences: nohello, yeshello, notonlyhello, etc etc.

This always just seemed like common sense to me, and I say that as someone whose in-person manner of speech is substantially more polite and flowery than most people. There doesn't seem to me to be a big difference in politeness or friendliness between "hello <new IM> [content]" and "hello, [content]".
This is exactly what I do, and it generally has good results. I don't have to worry about being rude, because the greeting - usually a simple "Hey!" - is there for those who care about it, and my question is also right there. Makes Slack turnarounds MUCH faster.
We just got the CCPA (effective Jan 1, 2020), which basically GDPR, in some ways stronger.

It's "California only", but companies have little choice but to implement it for the entire US (much like car manufacturers building all US cars to meet Cali emission standards).
That's fine, but then you must follow through on that courtesy by having the actual question ready to paste and send when the person says "yes". By taking more of their time, you're being rude, not courteous.
Um, well yeah, those doing music professionally have always been a minority and still are, which has no bearing on this post, or this thread, or what I was talking about.

The thread is about professionals; those making money from music. Mr. Bach and Mr. Handel weren't farming all day, I can assure you.
For the same reason that brands aren't concerned that the bus carrying their ad may be waiting for the light to change... In front of a strip club.
you have to register first
I tried that, but it never worked as well for me as it did in Sublime Text, or more recently VS Code.

I get what you mean about Emacs's nearly universal code conventions, but that's an example of something I personally found to be more useful in theory than in practice. While I love the concept, 95% of the time I'm hacking around in Python. The rest of the time is a hodge-podge of shell scripts and the rare C snippet. Maybe a little SQL now and then, or perhaps some JavaScript. When I'm working in something that isn't my usual, I find myself spending much more time reading code than writing it, and in that context I don't get as much benefit from those conventions.

Of course this is all incredibly subjective. If you get a lot of benefit from that, awesome! I can definitely see the appeal. I just don't feel like it makes a whole lot of difference for me.
My pet peeve is when you get the message "Hey, have you got a minute?"

You type back "Yeh, sure". And then wait... and wait....

Whenever they do actually ask the question almost an hour later, I'm always tempted to reply "Sorry, the minute is long gone".
It doesn't squeeze any humanity out of people to ask them to actually ask what they want, instead of just saying "hi".

The annoying part is that they will wait until you reply to the "hi" before asking the question, which is a waste of time.

It's not impolite to say "Hi. If you have a moment, can you tell me why I am getting this error in my JS on line 20?". Saves hassle.

I work for myself and am not at all overworked. Still annoyed by it.

You wouldn't send an email saying "hi" (usually).
I guess it varies by the scheme but the ones I've seen are loans that don't pay interest for a start. Wikipedia has info https://en.wikipedia.org/wiki/EB-5_visa
If you let an algorithm script a movie, it would be a 2-hr superhero movie with extremely simplistic moral conundrums, that will cost $300m to make, but will gross $1 billion +.

If the algo scripted a TV sitcom, it would be 5-6 mostly white people who occasionally hook up, break up, get married, struggle to conceive, and then everything eventually works out.

Same goes for music. People have a habit of liking what's in front of them. Few are going to want to make the effort to find something that's more than "good enough".
I guess it just doesn't bother you as much as it does others. I absolutely hate needless interruption, and every time I get a "hello" without anything else substantive, it means an extra interruption that wastes my time.

I often won't switch back to what I was doing after replying to the "hello", because my brain is doing a little wager, hoping that the question is short and quick to type out, because doing two mini context switches back and forth is tiring. And if my brain loses that wager, I end up sitting there idle for longer than I'd like.

It's funny how there's so much attention being paid to social niceties in this thread when a simple social nicety is learning how to best communicate with people on an individual basis. And I think that's even more important when the purpose of sending a message to someone is to ask for their help with something. If you're asking someone to take time out of their day to help you, doesn't it make sense to do your best to respect their time, on their terms?
It's nice to see #2 for package managers, something I've been thinking about recently. I haven't look much into this yet, but I wonder if IPNS could provide a step forward in supply chain protection since package signing isn't available yet in certain managers/repos or not commonly utilized.
Argument by turtles is only invalid if it doesn't converge in the end. If a professional designer needs to have less than half of a professional coder's expertise, and a professional coder needs to have less than half of a professional hardware engineer's expertise, etc., then the whole thing converges to a finite value.

An alternative way to view this: the output of your work in your field will almost always be priced and used outside of that field. The more you know about how your work will be used, the more context you have to evaluate whether or not you're doing things right. Given how human cognition works, having extreme tunnel vision is actually suboptimal, compared to being somewhat proficient in things around your particular specialty.
Seems like the license brouhaha spurred some changes and new relationships. Probably not a bad thing.