skysight-inc/HackerNews huggingface dataset:
Obviously I'm not privy to your contract of employment, but so far in over 20 years in the market, all of mine established work hours.

If I worked less than that, I'd get paid less.

Some contracts had provisions for overtime, in which case I could be paid more for more hours of work.

That's selling my time. I'd still get paid the same for the same number of hours, regardless of my output.

With good or great output, there was a small chance I'd get a promotion, or a pay rise in the next round of performance reviews (which in my experience are nothing of the sort). With bad output, there was a small chance I'd get fired. In either case, my pay was never tied to my output. I'd still get paid for the hours I worked, regardless of how well I performed.

> you’re paid to fulfill a role

See above. You're usually getting paid to fulfill a role for a certain amount of time. If "number of hours you've fulfilled your role" is how you measure your output, then I 100% agree this is a silly debate.

That is not what I consider output though. A factory is paid per output. If they produce 100 cars, they get paid 100 * price of 1 car. If they produce 90 cars, they get paid 10% less, and so on.
Curious how they handle GQL injections. Most devs using graphql have no clue what they are as the majority just cargo cults new frameworks to keep themselves busy.
I'd agree strongly.

Moreover, if you're using third-party tools, you now have two problems: managing and organising content AND managing those tools and keeping track of their sunsets and shutdowns.

(I've been bitten by that last twice, and still have un-migrated Readability articles. Made all the worse by the fact that Readability at some point employed its own URL-redirecting link-shortener ... which of course also went offline.)
That's what I mean by "no good reason". This is the scale where you start to notice the stupid stuff you let through - N+1's, excessive unnecessary string allocations in inner loops, debug logging etc.

What I mean is, there's nothing fundamental about their tech choices that could explain such low scaling limits. It'll be either poor design/architecture, poor coding standards or both.
My intuition is that if you did a lifecycle analysis of things like more modular and repairable phones (or I guess jeans), it would be pretty likely that it would be environmentally worse because you're using more materials for added interfaces, connectors, which adds more weight for shipping and therefore fuel, etc. Compared with the amount of people who will actually benefit from DIY repairability and modularity.
Lemmy.ml, the original developer's instance, is well known to be a small server.

Lemmy.world is well into 31,500+ users on a single server and still growing strong. But growing pains have begun to creep in in any case. The server's software clearly needs a few optimization passes.
Interesting that every time I bring up the social economical reality in Canada on hn and I got down votes or whataboutism but never a productive refutal. I wonder why ;D
How did they do it? Atlassian doesn't know how: https://community.atlassian.com/t5/Jira-questions/How-to-i-d...

"Jira can not work without the REST API, so there's no way to turn it off."
actually, i believe this was very profitable for reddit.

the others examples mentioned above are more pertinent.
This is not true, I've played it on Linux with Proton myself just fine today. Maybe the poster has a different issue.
FWIW I worked in software for 14 years, and never used Slack or Discord, so I wouldn't be so quick to generalize

"Everybody else is doing it" is a weak argument

"Everyone else" isn't building a browser from scratch -- it's more important what those people are doing and using
There are a few technical hurdles that must be overcome for "everyone wears a headset to work" to work at all.

* The headphones must block outside sound sufficiently, so you only hear the people in the same room through the call and not directly.

* Your headset must not pick up when other people in the same room are speaking.

But even then, it has serious drawbacks compared to an in-person meeting:

* Latency. With anything over a 50 ms roundtrip (including hardware), people inadvertently start speaking over each other, and typical latencies are much much higher than that. It becomes more difficult to break into a discussion, trying to make a small interjection often disrupts the flow of conversation.

* Lack of non-verbal communication. Webcams remedy this to some extent (though many are negative to using webcams in their home for other reasons).

It can be argued that this is a small price to pay for the ability to WFH, but it's disingenuous to say that pushback against "everyone on headset" is just due to people feeling "daft" doing it.
I'm very pro-WFH, but I don't understand/agree with a lot of the dialogue in support of WFH, including much of this article.

For example, some software developers in these discussions will say things like "What do you care, if I only work 1 hour a day, so long as I get my work done?!?!?! :emoji: :emoji:"

My answer is not "There should be butts-in-seats for 40 hours a week, because that's what we pay you for!!! :emoji: :emoji:"

My answer is that (for the kind of things I'd like to be working on) the kind of work we do requires creativity, thinking holistically, diligence, effort, perseverance, team focus, etc.

It's not hitting metrics of number of sprint tasks you can plausibly claim you completed satisfactorily. The hiring and compensation should be guided by the idea that people are neither fungible commodities nor simple automatons. We're looking for a large chunk of some of this particular person's best work, while they're also having a non-work life.

If they're outsourcing their work, phoning it in, thrashing their mental swap space with their side gig, taking on a second job that leaves them fatigued, etc.... the team isn't getting much of their best work.

We will be flexible and supportive when life takes more time&energy than usual, as it sometimes will, for anyone. And there's daily ebb&flow for how available a person's best work can be.

But something like a second "full-time" job is harder to accept.

Also hard to accept is someone who treats software engineering like a factory job, thinking all that matters is the metric for how many fungible widgets they assemble over the course of a week. In software, that usually means: piles of half-butted unthinking new tech debt liability grunted out.

Also hard to accept is this article attempting to deconstruct and critique societal structures, with the author's particular perspective and theories... when it's unclear how that informs an organization where people just want to do great work as a team, benefit financially from that, and have lives besides.

Want to end WFH? Don a revolutionary beret, and gift-wrap a bunch strawperson-argument blog posts that help discredit WFH in the minds of some of those you most need to persuade.

Please, for the sake of WFH, don't make ostensibly pro-WFH arguments that go full anti-corporate in ten different ways.
Serious question (since I'm not familiar with AI/ML), what's the point of releasing these "smaller" (5B, 10B, 13B) models, given there are plenty of bigger models now (Falcon 40B, LLaMa 65B)?
can hallucinatory AI in current form be so worth enough...
I don't think the Lemmy developers were expecting #RedditBlackout to dump 150,000 users onto their federation in a week.

They were probably trucking along with various feature requests when suddenly performance became an issue this past week.
> if people just saw it is a simple alternative to REST, with a well defined set of query (GET) and mutation (PUT/POST/DELETE) endpoints, they wouldn't get caught up in all this "infinite object graph" stuff that I never hit in my day-to-day.

Can you explain this more? How can you avoid infinite graphs? If I have User {things: Thing[]} and Thing {owner: User}, you have to deal with this issue.
I think the footnote you elided sums up my opinions here. I wasn't the one who brought up "talent" or "experience" - that was a direct response to the top-level comment.

The footnote makes it clear neither are necessary. And that saying "even 'talented' and 'experienced'" folks couldn't from Haskell isn't a slight against the language choice but rather the aforementioned folks.
Or maybe building an entire business solely on someone else's API (especially Reddit, Twitter, etc) is extremely risky and almost always ends with the third-party apps paying the price. So as I said before:

"Either the API gets blocked for third-party clients, or you purchase a high price for it." [0]

[0] https://news.ycombinator.com/item?id=36087219
> The developer only exists to serve the product and customer. I do not know why the developer should be the center of any company, none the less why they should be on a billboard. Buyers don't care, they want a great product.

I think the point is that developers are (or were) the customers. Twilio got adopted because they targeted and excited developers. Now they don't care about targeting the developers, they're targeting executives and marketing professionals.

I did not down vote you, and I don't think you deserve the down votes.
We're going to Mars, we're going to conquer the solar system and beyond. We're going to have human populations at record levels.

It might be hip / cool to degrowth but as others have pointed it's unnecessary and after reading the link, seems more marketing than substance.
> plough ahead with a mic/speaker in the middle of the room and the remote guys become second class citizens, not being able to hear half the room.

there’s really no excuse not to have a decent conference phone in meeting rooms. i’ve seen them in use since 2000 at least, and personally purchased one that wasn’t even $1k.

we had meetings and calls with remote people long before covid.
That tells me nothing, is it bad?
But in what other country can you be elected as dogcatcher?

* https://www.vermontpublic.org/vpr-news/2018-03-16/meet-the-c...

* https://www.npr.org/2018/04/07/600482792/you-couldn-t-get-el...
No, I disagree. On the Recommended tab for my TV show folder, the rows are:

- "Recently released" and "Recently added", which I agree are useful — but don't belong in a separate tab, as I always sort by recentness.

- "Start watching": Shows it thinks I should start watching; why? I know what I have and what I intend to watch.

- "Rediscover": Shows I have started watching but not finished, pointless. I could just browse.

- "More in [random genre]": Pointless, I know my library, it's my library.

- "Top rated TV": Ditto.

- "Recently played": Never use this, doesn't belong under "Recommended".

It's all just pointless stuff, and not appropriate as a default view when I'm navigating into my own library.
I'm shocked that in this entire thread there's nary a mention of the elephant in the WFH room: the commute.

Not only is commuting a (potentially huge) waste of time, but it forces me to risk my life on the road.

In the US this commuting time is uncompensated, and I've never heard of anyone being compensated for risking their life by driving/flying to work, and that risk is not even acknowledged.

It's also far less stressful to roll out of bed and "be at work", as it were, than brave the commute, rush hour traffic, the belligerence of other stressed-out commuters, potential road rage, traffic tickets, stressing out even more when you're late or you're stuck in traffic, etc...

All for what? I'd rather spend more time with my friends and family than my coworkers.

No, now that I've tasted WFH life, I'm going to do everything in my power to avoid commuting. Maybe if they doubled or tripled my salary I might consider it, but nothing short of that is remotely worth it (pardon the pun).
My first play through while narrating
I hand-change every file name.

Please tell me I'm an idiot and show me a better way. Lol it won't save me the hundreds of movies I've put in "Title (year).type" format, but it will save some future work.
Twilio are still doing better than their competition. To name an example, MessageBird laid off 30% of their workforce in late 2022 vs Twilio's 17% in early 2023, and they are known to be an absolute clusterfuck, which is not something you hear about Twilio (yet).
I could see this going to court if he ran with the outcome being the equal protection clause winning out over that. I might be misremembering, but I think that clause was to keep England from sneaking someone in to take the presidency of the nascent United States.
> This is exactly the sort of thing that’s been happening in Miami.

The example quoted is exactly the sort of thing that's not going on.

And where's the threshold for calling people bilingual? If you say "get down from the car," you're (likely) using that phrase only to people outside your environment. It's lack of fluency.

> “Thanks God,” a type of loan translation from “gracias a Dios,” is common in Miami. In this case, speakers analogize the “s” sound at the end of “gracias” and apply it to the English form.

That's just an assumption of the "mmm, let me think 2 seconds" kind.

The writer also calls it Spanish, but e.g. beef is "ternera" in Spanish. It might be Cuban Spanish, which has a fairly large vocabulary that differs from other Spanish variants.
I've seen things you people wouldn't believe...

Open floor full of people - all doing Teams calls...

With colleagues who could not come, because there was not enough desks at the office, for everyone to book...
A certain degree of overhead just has to be there, a distributed system needs to exchange information between nodes after all. And both the protocol and many implementations leave room for optimization at least. I think tackling that is one of the long-term challenges for the ecosystem, but I wouldn't say it is categorically "not scalable".

EDIT: As an example, right now in Mastodon federation traffic is handled by sidekiq queues running Ruby. Someone makes a post -> tasks to send that information to all their followers instances get queued, which then send individual HTTP requests to all those instances. This to me feels like something that could be moved into some smaller and more-efficiently-written component that batches requests, makes sure to reuse connections, ... at least for paths that see a lot of traffic.
A common reason is to reduce cost and latency. Larger models typically require GPUs with more memory (and hence higher costs), plus the time to serve requests is also higher (more matrix multiplications to be done).
its not even a good way to maximize output
Everyone is deeply afraid of being called Hobophobic.

It's the actual root of the problem, see recent HN threads. We can't even talk about the problem and be taken seriously
You don’t trust them and need to exit asap.
Can I ask you something?

I grew up in the 2000s. I've constantly seen people on the internet complaining about its modern state, saying the internet of the 90s was so much better, less spam, filled with smart people, etc. Basically saying that the mass influx of people is what turned the internet into the cesspool it is today.

I of course never got to experience this, so all my life I've only been able to dream about what this is like. But this Lemmy / Fediverse stuff seems promising. A discussion platform that requires technical expertise to engage in (for now) while also being completely decentralized... seems analogous to the early internet for sure.

Am I correct in this assumption? Are these platforms home to high quality discussion and little spam? If so, then I think I'd bite the bullet and try to figure out how to actually set this stuff up on my PC.
RAM requirements
There’s a handful of efforts like this which I find really exciting and hopeful. It’s clear we can do damage to the environment but I think it’s important to try to learn and take positive restorative steps given our position of stewardship of the planet. I’ve heard this kind of effort be called “ecomodernist” as it’s a step after the idea that all human intervention is only destructive and the best option is to do nothing.

Pleistocene park in siberia
https://pleistocenepark.ru/

American Prarie plains rewilding in Montana
https://americanprairie.org/

Ecomodernist manifesto http://www.ecomodernism.org/
> Why? Because there are many CEOs (and VPs, and so on) that have got there with the joyous idea that the reason you become a CEO is to get paid for other people’s labor, which also means you don’t have to work. That’s also because the modern corporate interpretation of capitalism is inherently patriarchal - borne from the prospect that we all look up to someone, and we must learn from them and grow from them, until we eventually go and make our own children (companies). But until then, we’re under their “care” but also the rule of their law.

> This is a misinterpretation of what capitalism is (for better or for worse, the most efficient extraction of money from labor - which also means getting the most from workers), and what attracts people to management roles (misinterpreting control as an efficient way of extracting value). The reason that there are so many bad managers - middle and otherwise - is that lots of people see management as delegation of work that you take credit for, mostly because that’s how many corporations function on a grand scheme. It’s framed palatably as contributing a small piece to a larger whole, but middle management’s truly noxious existence proves that people absolutely love it. The attraction to these positions isn’t what a true manager is - fostering talent, making the company better, getting more done, winning together - it’s about control and abuse.

Pretty clearly laying out the corporate capitalist office environment as nothing other than a big MLM scam.

Rest of it was really good as well, but I felt like highlighting that bit for the people who only read the title.
If you feel unfulfilled in yourself how can helping others help you overcome that? Say you feel bitter about the way you've been treated all your life (shunned, bullied, isolated), will that rancour disappear one day because you helped a few people?
The post argues that it’s management’s responsibility to make sure employees are adding value. This idea that managers shouldn’t care how many hours someone works as long as they get their shit done, goes counter to the idea that managers should be hands off a let engineers innovate. I think the most innovative companies let engineers prioritize much of the work. But in that case there is much less clarity about whether “shit got done”, so you’re paying for smart people allocating their creative energy into your business many hours each week. For the same reason, remote work ultimately brings a more transactional work environment and I believe less of a growth environment for individual professionals. People are so obsessed with the additional comfort that comes from working at home, that they fail to see that in fact there are real downsides.
Where are you finding that number, 150,000? The instance in question has one one hundredth that figure and the Lemmy devs claim 27,000 accounts grand total.
Dar – backup and archiving large live filesystems
As I've noted, the Einkbro web browser (optimised for e-ink, though usable on emissive-display devices as well, Android only) has a "save to ePub" feature.

This does, of course, strip all site styling. Images / artwork may be preserved, depending on how they are presented in the original HTML. (If using <img> tags, yes, if served through JS ... not so much.)

What's genius, though, is that multiple articles can be saved to a single document, which can be appended over time.

I use this to group items by similar topic, project, or interest, or to create a "BOTI" archive, where "BOTI" stands for "best of the interval". The idea here is to select the best items over a given period of time (week, month, year, etc., though I seem to be settling on six to twelve months), and organise those in a single place. You've Still Got to Read It[tm], but at least you've organised the material.

Reading this on an e-book reader, using the bookreader software, is also virtually always preferable to reading the same content online in a Web browser.
Where did they pull the 1.9 years of flight? The SpaceX plans to go to Mars talk about 80 to 150 days, with 115 days average [1].

[1] https://en.wikipedia.org/wiki/SpaceX_Mars_program#Colonizati...
They forgot black mold and dead snakes/rodents.
Depends. Some hifi headphones and speakrs are actually matched. Rare now, but used to be very common when driver designs and production tolerances were looser. I have some 1930's brandes headphines that were matched, but are basically a magneto driver and sound awful (but clear) by any modern standard.
Crab and lobster shells could be used to make renewable batteries
It may remind you of [any other protest] in that it will end, but the question is whether the 2% of Reddit users responsible for its value and culture go with it.
Tesla's U.S. electric vehicle market share could drop to 18% by 2026
HN has decent technical discussions and some really good historical/personal anecdotes. Otherwise, it falls short and lacks in ideological diversity. And there is also bullshit here.
I kind of hope you hold onto this throwaway account so you can tell us what you ultimately decide to do - from what you've said it sounds like the right course of action for you is to exercise your options to lock in your equity (assuming you have enough spare cash to do so) and move on, starting things off with a long vacation because you've been working crazy hours. Or you could start by just taking a long vacation and deciding what you want to do. Or a short vacation to work up to the long vacation - at the very least, a disconnect from the grind would probably really help.

I say this as an individual contributor though, and I imagine it must be tougher to consider walking away when you're a manager and you have a team of people who will be directly affected if you leave.
Zotero (and possibly Calibre) seem to be the tools best suited to serious archival, based on what I've seen.

Sadly, no full-featured Android apps.
I think the additional issues come when you want to define access by a relationship instead of just the entity, which means you need to check access based on the edges, and not the nodes. You'd have to do this anyway with REST, but I think it's easier in some ways to make mistakes and allow more access than intended.