skysight-inc/HackerNews huggingface dataset:
> LSD chemists must be extremely careful in working with ergot because of its toxicity. Remember the people poisoned by rye bread in the Middle Ages? Once the chemist obtains the fungus, he has to carefully and precisely culture it to extract the ergot alkaloids (an alkaloid is a compound containing basic nitrogen atoms). The darkroom setup becomes necessary here, because the fungus will decompose under bright lights. In fact, LSD itself may break down quickly when exposed to light.

> If working with toxic ergot weren't hazardous enough, the solvents and reagents (compounds used to bring about chemical reactions) are also incredibly dangerous. The solvent anhydrous hydrazine, for example, may explode when heated. It's extremely poisonous and carcinogenic (meaning it can cause cancer). Another chemical often used in the process, chloroform, can also trigger cancer, in addition to damaging the kidneys and liver. Both substances are easily absorbed through the skin or inhaled.

I don't know what your living situation is, but I would ask you to have a little bit of consideration for your own well-being and that of your neighbors. I have witnessed significant permanent damage to living spaces, not to mention the humans within them, from petty criminals who thought it'd be a good idea to run a meth lab in an apartment.

The toxic byproducts get into everything. You will make mistakes, and you will probably quickly kill yourself, if you aren't arrested first. If your neighbors are fortunate, the nature of your clandestine chemistry experiment will be found out, and remediated before too many people suffer permanent harm.

I suggest sticking to beer.
They aren't really twisting anything.

A 20 minute in person chat over a whiteboard can save weeks of back and forth on written communication. It's not that crazy. My work place has "do what you want policy, but we want to encourage remote work and shrink our leased offices". My team at least has 4 people that come to the office regularly, and 2 that work remotely 100%.

The #1 complaint of full time remote workers is they feel we all agree on designs and decisions and they just get to see a doc that 4/6 have already signed off on verbally and they feel not involved. I have no idea how to "make them feel involved" nor do I care tbh. I'll always do what's more efficient and what reduces red tape. If that's me just standing up and saying "hey A, B, and C, you guys got a sec? Here is a problem I found, mind going to the whiteboard real quick" will always trump "shit, let me look at everyone's calendar and schedule a 30 minute meeting" then get an email asking about agenda, and 2 people who have personal conflicts and someone asking to reschedule last minute.

> Verbal communication is usually a huge time waster and can be outright disrespectful if someone prefers to rob everyone's time and digress and to push the "distilling" part onto everyone else - if the distilling even happens before everyone has tuned out and just agrees to finish yet another meeting.

You do far more pointless meeting and verbal communication when everyone is working remotely anyway. A conversation that just needs 3 people will now involve 12 because everyone needs to forward a meeting invite to everyone they think might even be remotely interested.

The "outright disrespectful" is just a people problem. outright disrespectful people will be outright disrespectful in both verbal and non-verbal communication.
Even better, every app is doing their own styling so they can all look like Discord
As soon as it’s mixed in anyway, it’s the worst of both worlds. The company has the overhead of maintaining an office building, people cannot move to low cost of living locations, companies are restricted to hiring candidates that live within a 30 mile radius, meetings will automatically cater more to those present in the office instead of diving completely into remote first, there will be an unspoken pressure to come in more often etc. It truly is the worst.
hybrid work is never going to work unless VR gets really good. If you aren't remote first as a company in terms of communication policy the remote people are going to get left out of the loop a lot compared to office workers. I don't think there is a good middle ground here, you have to go all in on remote or office

The question is if any of the supposed benefits of office work exist, there's really no data I've seen . Remote has plenty of easily measurable benefits like no office costs, no commute, no office distractions, easier to recruit, salary arbitrage geographically, etc.
As a manager I love WFH for myself and based on feedback I love it more than many of the ICs at the company. No walking between meeting rooms, no taking notes on a tiny laptop screen, no forgetting someone's name (or role), no sitting in uncomfortable meeting room chairs, no ad-hoc conversations taking up my limited non-meeting time, no juggling being even more late to a meeting versus using the bathroom, etc.

The real difference in my experience is that extroverts prefer WFH and those tend to more often become managers however plenty are ICs as well.
What exactly is an office superior at other than providing:

- Leaking roofs

- Stinky coworkers

- Shitty food

- Flickering lights

- Constant interruptions from people just saying "hi"

- Unproductive commutes
Does this also work if you're using the generic OpenVPN client to connect to the VPN? I've used a bunch of different VPN providers over the years, but they usually just offer an OpenVPN configuration that you can use with the normal client. I'm not aware of this also allowing them to send traffic the other way, but maybe it does?
Let's say someone makes a site that compares prices in different stores. It needs a lot of scraping, but is useful for consumers. Obviously, the only ones who are against it will be the store owners.
Sounds like a setup issue, which can be tricky on Jellyfin to get transcoding properly working.
Crinacle's IEM Ranking List
I believe anybody who's shopped for a desktop CPU in the past decade knows this. The difference is that a Ryzen 5600X costs 10-15% more than a regular 5600, not twice as much and then some.
> increases paperwork and pointless documentation

You added this yourself. Documenting stuff is not pointless or "paperwork" (e.g. filling forms to get certain things done).

Working remotely async requires people to document their meetings, have documentation in place for newcommers to your project, etc. It's far from pointless.

The alternative is to have these mythical "watercooler chats" that people keep saying exist where 2-3 people gather together and exchange ideas and decide on things without letting other participate or know about until it's too late. I've never seen much of that while I worked in an office but if it exists, the company has way bigger issues.
Hey Guys,

We have a ProductHunt launch next week.

What do you think of our launch page? Do you have any suggestions?

MonitUp AI Time Tracker tracks your daily activities, measures your productivity and gives you AI suggestions to improve your productivity.
And it doesn't require internet access to watch things on your local network.

That was the last straw for me with plex.

Having to log into a server on the internet to access local content isn't just bad, it's broken by design just like DRM.
It’s a massive cutting of waste: commute times, commute energy use, and middle management.
There is `git bisect skip` (https://git-scm.com/docs/git-bisect#_bisect_skip), which lets you cope with a testing process that sometimes doesn't yield a true/false result. But it's more useful for untestable commits than for inconclusive results like you'd get from a single boot here.
There is, it's called a USB 4G modem that plugs straight into whatever server you want.
Pocket, built in to Firefox, provides (and generally exceeds) Readability's capabilities:

- It renders a "clean" view of most Web articles, using the Readability JS library itself.

- It provides tags (and far more than Readability did, accounts topped out at 500).

- It has an Android app.

That said, Pocket still has a whole mess of failings, lacking features, and sheer bone-headedness. Of the list I'd written of in 2017, most remain:

<https://web.archive.org/web/20190512092903/https://old.reddi...>

Pocket now has in-page search (within the Pocket Android app). It does not have full-text search of your articles. The rest of the issues remain, and a few others have cropped up.

Pocket remains very much an Article Roach Motel: articles check in, they don't check out.
How to Stop Concurrent Operations with Ruby and Polyphony
It's not a figure of speech. It's a very deliberate attempt at deeply mischaracterizing the position in an attempt to make it appear absurd. "Oh yeah, that's right, who would ever wake up one day and decide to be homeless? What an idiot who would think that!"
That's not how it works. You think you're being funny. You can't keep it together enough here to even genuinely engage. In case anyone else is reading, no, one exposure to Andrew Tate's toxicity is not what causes one to become misogynistic. It's an entire society and repeated exposure to his ideas, and ideas like his that cause it. It is not one exposure to a Tide advertisement that makes somebody sit down and say, "hey I should go buy Tide because of this advertisement!"

Not like feeding them and giving them shelter. Remember, you don't want to give shelter. You, and your ilk, the vocal faction of SF politics, will accept nothing short of housing first.

I obviously believe it is awful to be homeless. You say I straw manned you - tell me, am I wrong? Do you support anything short of housing first?

If, say, the voting public doesn't want to give everyone 1000sqft in the heart of San Francisco, but is in favor of sheltering and forced drug rehabilitation and mental health facilities coupled with enforcing laws. You're telling me that you would not prefer the current state?

My thoughts are your (presumed) preference of status que over a compromise that doesn't cause maximum suffering for all is the worst of all worlds. You're the "Bernie or Bust"er of the unhoused. You're the person who would rather have Trump than Biden, if you can't have Bernie.

"Well, if I can't give everyone a free house in San Francisco, and change the distribution of wealth, I'd rather people suffer and die in the streets (via decriminalizing everything, and being anti-shelter), because then at least the taxpayers will also suffer the consequences of it, and then maybe things will change."
A great article by James Mickens entitled "The night watch" explains what it really means to be a kernel dev.

https://scholar.harvard.edu/files/mickens/files/thenightwatc...
"Menus at the top of the screen provide consistency between applications. You don't have to wonder if an application's menu items are behind a hamburger menu"

Menus' consistency has nothing to do with where they are positioned. You're talking about bad design. You can just as easily have dumb, non-standard affordances at the top of the screen... you see it on iOS all the time.

And the "slamming the cursor" argument is countered by having to move the cursor much farther, especially on large monitors with lots of real estate. Not to mention that vanishingly few users actually do this.
Is anyone frustrated with anything about Prometheus?
I don't know, man, the whole "screw your rights" thing really hurt. I get that it was hyperbole in the heat of the moment, but coming from Arnold it just stung.
not every language is indentation based ...
On my end, it definitely does not work with https. I'm using the main stable version on the tvOS app store that I downloaded about a week ago. The default connection url is http://, and changing it manually to https:// causes it to fail and throw no errors. FWIW, I can't connect with https via the web interace either, so in theory this could be just an issue with my server install.

If the indexing and metadata is done by the server, then the server just is worse than Plex at figuring out what things are.

I can't tell you why it crashes when I try to play back videos that work just fine via the web interface, but it does. They're normal 1080p h264 .mkv files.
Yep. At least the people I work with have generally been pretty good about it for a while but written documentation generally, meetings agenda, minutes to at least some level of detail, etc. all seem pretty useful especially in situations where at least some people are going to miss the meeting for whatever reason.
> The founders were wrong about a lot of things, they also failed to account for the fact that political parties were naturally going to emerge.

“Failed to account for” is a romanticization. The factions largely existed as the system was designed, and it was designed around and to accommodate them, with actual parties being set up around them immediately. Washington wasn’t making a warning, he was complaining about the existing status quo.

> Constitution as a frame for government worked well if you just want a land owning elite to run things, it works pretty poorly when you want to have a functioning democratic republic.

And it was a compromise between factions whose one point of agreement was that they wanted a landed elite to run things. This wasn't an accidental result.
You have the CEO of a public company come out to play and address a public post, which is pretty cool! Your attacking style of questioning just makes people like Jeff less likely to engage with the community. You could frame the same question in a more constructive style.
I have a theory about RTO that is not so much about psychology, but rather is about pricing power.

WFH creates another, national and in some cases international job market alongside every local job market. A lot of local job markets are captive labor pools, because of family ties, low cost of living, and inertia. It is an easier coordination problem for a small number of local employers to set wages for that market than it is to coordinate setting national wages.

WFH makes it harder to have pricing power on local wages. Even if remote employers adjust wages for local cost of living, those wages are still often higher than local employers' wages, or the benefits are better, or the work is more interesting. Many local employers cannot compete for talent in a WFH environment.

By breaking apart a national labor market into many local markets, the problem of managing wages becomes a more tractable problem.
My SaaS backend is a GraphQL Server that has single-handedly saved me tons of hours for integrations and coding. The first iteration of the app was using rest and that was a pain. Hitting multiple endpoints to get all the details of an order is not something I miss. On top of that, I get a beautiful playground that acts as a query builder and documentation.

Have you actually used GraphQL in production or for a wide-scale project? A lot of these criticisms for GraphQL comes from people who have played with it for an hour and determined it's not good. Give it a real chance and you'll see why big companies are using it and understand why the ecosystem is growing so fast.
You are confirming that you are heavily biased by what seem to be extremely poor and uncommon experiences (I mean, leaky roofs?). It's normal to be biased based on personal experiences but it still does not make wfh objectively superior (or vice versa).
I think it's perfectly ordinary for a new web application to hit scaling issues at that number. Accidental O(n^2) stuff, missing database indexes, poor use of memory, excessive I/O are easy mistakes to make during initial implementation and probably will get fixed.
The article rests on the idea that the management knows what needs to get built, but my experience so far was that they are usually even worse at that.
Kinda, by all accounts the original motivation was to solve the proliferation of endpoints. Everyone was already writing per-screen endpoints to solve the network requests problem (which, contrary to what many believe, wasn't magically solve by http2), but they were doing it in a way which played out in several ways:

1. Having to make a new endpoint every time your frontend changes

2. Not making a new endpoint, and just augmenting the existing one for a screen. Which would cause them to accumulate dead data over time (especially if multiple app versions had to be supported concurrently -- in the case of Facebook this was ~3000 versions).

3. Being lazy and finding a similar endpoint meant for another use case and piggy-backing it for your new usage.

All of these would create maintenance and organisational problems.

GraphQL is essentially a system that lets you write endpoint specs (in the form of GraphQL query documents) that the backend knows how to support. It's not a free lunch, you still have to do a lot of work on the backend to allow it to do this efficiently and securely (nowhere near as difficult as people make it out to be though), but it does a really good job at solving the endpoint maintenance problem.
Before Elon people were copycatting Steve Jobs. I think every decade has the Insufferable Successful Asshat that pervades the Id of business owners and managers.
Yeah, Jira definitely needs Benevolent Dictator in charge of the stuff that bleeds out to other teams.

You can have any funky workflows you want, but labels and I think components are instance-globals.
See also the "great northern vowel shift": https://en.wikipedia.org/wiki/Inland_Northern_American_Engli...

Fascinating phonetic rotation occuring in the north of the US.

Also, regarding the Miami dialect: obviously fake. I don't see a single "coin" or "crypt" phoneme in the whole article. ;-)
Reminds me of Bryan Cantrill's Fork Yeah talk about the acquisition of Sun by Oracle
Is ActivityPub not scalable? I keep seeing criticisms of it on this front.
Any tips for Atmos? I've tried turning on "spatial audio" for albums that support it on apple music, but it just sounds more distant and echo-ey. It sounds so bad that I can't imagine anyone liking it, so I must be doing something wrong
Wallabag is the one suggestion that keeps popping up persistently, though I've not used it myself. You can deploy your own instance.

<https://github.com/wallabag/wallabag>
LLMs can label data as well as human annotators, but 20 times faster
You can also measure the work output directly which is not hard in most industries.

I don't work in an IT shop, but we have no issue seeing who is slacking and who is actually working when working from home just from the deliveries, no monitoring required. But I guess that's included in your "other proof of work".

There are some people who need discipline though, there were some guys in my previous company that were notorious for showing up at the 10 am teams meeting with a bed head and a yawn or the 2pm meeting outside in their garden. You could also notice their output go down quite drastically.
I honestly don't understand the complaints here. In our deployment it's implemented as an HTTP handler right next to all the REST ones and gets all of the standard authz/authn/obervability wrappers. It's allowed us to focus more on core development because the schema was exported over a year ago and hasn't changed much. It functions almost identically to the REST components but is easier to develop against. No issues with scale or performance that aren't apparent in the REST components either.
Well, if this happens, we can file it under "strange things that the Simpsons somehow predicted perfectly."
Using a Google-hosted bug tracker? Ha!

If they ever start actually giving outside companies access, I give it 3 years before the shutter it.
Ask HN: How to approach early red flags with CoFounder
DELETED
Gluestack-Style: Universal and Performant Styling Library
The sometime political media convention that an action can't be described as a GOP responsibility if the 50 Republican senators are joined in it by 3 Democrats is purely obfuscatory if one is trying to actually understand what sides are involved in a political debate and what's entailed by empowering one party or another. Let's not adopt it here.

(Also, while maybe there's something to the Locast stuff-no idea-I'm not sure what a Democratic nominee is supposed to think about Fox News or Kavanaugh's temperament.)
What’s better a 130bn model or 10 13bn models working together.
Hey Jeff,

Good to see that y'all are still pushing in the right direction! I left between the layoffs to pursue some innovation in the semiconductor space, but I look back fondly on my time at Twilio (Sendgrid)!

Building APIs into businesses is no easy task, but I'm glad that there are those still fighting the good fight, even if the field changes. Best of luck to the Twilio of the future!
Uber Eats barely existed in Brazil. Not sure what was there to beat anyway.
I think there is a little more to it but housing is certainly one reason.
> I am meticulous at making sure the structure and filenames are correct before dumping anything new to the library to the point where I have a complex script to process movie and tv show filenames and folders.

I'm curious to know why you chose to write a custom (and complex) script yourself instead of using something like Sonarr/Radarr for this task? Does your script do something that the *arr apps are not capable off or is there another reason?
Yet another post that is pure bias. I won't bother listing the reasons you're wrong, because I feel they're fairly apparent, but instead just point out that every single one of your points is also possible when working from home.
Well, by that definition, the opposite of Capitalism is Democracy.
Yes, I referred specifically to the Skycar, which was the last major effort, but yeah, Moller was playing that game for a long time.
A related book (really a collection of essays / articles he previously wrote) I enjoy reading periodically is Infinite Baseball by Noë.

Noë is an analytic philosopher whose work deals largely with the nature of perception. He’s also a big baseball fan and has written quite a few articles for different sites on the intersection of the two. The first chapter describes how, in his view, baseball is really an infinite game.

Even if you are not a baseball fan, I think the book is an interesting read. A lot of his observations are not about the sport itself and therefore does not require detailed knowledge of the sport. Instead, they are musings on how we engage with the sport and what we get out of the sport, and those ideas can be generalized to many other activities.
I think GP's point on company culture is the right answer.

My only thoughts to add is monoliths can be aligned as well as microservices, if not a bit easier depending on the team.

You have to align microservices to talk to each other anyways, and there's no reason you can't make those boundaries work in one codebase instead of many.

That said ownership is more important in a monolith, whether that be a single team of architects or architects responsible for a specific well defined part of the code base.

Having a solid process for only allowing well thought out code in is a cornerstone to keeping alignment.
I agree, as you say, there are very few jobs people want to do, but they do them anyways. Thus, people will probably continue to work for employers that deny them water breaks. The question is whether we collectively want workers to be treated that way in our society.