weli

Completely on point

> We require clothes for on-site interviews. We require phone service for phone screens and electricity and internet service for video interviews.

Yes but none of them are solely for the purpose of the interview.

> We don’t pay gas/mileage for on-site interviews for local candidates.

Gas is one of those gray areas because technically it's not a required expense. You could live in front of the office and just walk there, you could live in another state and have to spend 100$ on gas to get there. Since it technically is on the candidate, you applied for this job, on site, knowing how far away it was from your home. Therefore the cost is on you.

But LLM's are different. Is a cost on the candidate, that we require them JUST for the interview. Maybe that person would have spent the money elsewhere, or have spent the tokens for another job. That's where I think the main difference lays.

I thought about this but it's also a liability and puts too much strain on me.

1. Whatever limit I put needs to be completely arbitrary. 5$? 10$? 2. I cannot guarantee they will use it correctly. They might use it for the challenge. They might use it to generate harmful content. 3. It requires me to manually create and revoke keys. Candidates might want more credits. They might get leaked.

There are solutions. I just can't think of good ones.

I think finance will hang me upside down if I even mention that we need to provision virtual cards for every candidate

I've been a broke student with loans where I had to decide between gas to go to an interview or eating that day. It's not about 20$, is about how morally ethic it is to ask people to use their own personal money to just have a chance to get hired and how to try and minimise that.

Not an easy way afaik :/ but if someone knows a good way please let me know

read the blogpost, they are discontinuing deno after 1 year

I wholeheartedly agree. While I admire OP in his charitable endeavors. I can't help but think that this puts the incentives on studying things that offer little to no market value. Market value of a degree tends to be a huge predictor of how needed that skill is in the market. I don't know if what Tanzania needs right now is language PhD's instead of Architects, Engineers, Doctors, etc...

I didn't say it was unique to Christianity

Would you not agree that certain dogmas, just by their approach on analyzing the sacred scriptures, result in a higher degree of clerical classes that tend to use a proto-scientific method to the research of knowledge?

I agree, abrahamic religions tend to produce intellectuals that try to rationalize the religion to some extent, which in turn eventually generates the split between religion and science. Especially christianity tends to cope with this pretty well, there are things that you must agree with "on faith" and contradictions tend to be not only allowed but to some degree reinforcing the own faith of the individual.

I have no doubt that a St Thomas Aquinas born in this age would have made for a great scientist.

One important thing to remember is that the separation between religion and science was non-existent until about 500 years ago. When you don't have any notion about how the world around you works and suddenly crazy things like earthquakes happen talking about tectonic plates moving 200 km under you is more surreal than saying god is furious because you din't do any offerings last harvest.

Religion, to the human early societies, was not only beneficial, but necessary from the group cohesion standpoint.

I see reasons to have smart features in a fridge. Reminding you what food is going to be bad soon. Letting you know a list of recipes you can do with what food you have. Hell even being able to see and set timers without having to take my phone out. What I cannot fathom is the fact that the module running those smart features is not separated and modular enough so that basic functions like refrigerating are not dependent on an entire Android stack running.

That's what I don't understand. They could mitigate their name so much if they just split free/paid/enterprise. It's already shown that enterprise is much more estable and is largely unaffected from service disruptions. Why don't they go one more layer? For sure it's worth the extra complexity.

They affect different things. You want more powerful models -> more memory. You want the models that run to be faster -> more gpu cores.

Segments of the UI that don't conform to any other existing established design or conventions

Anecdotal, opinion:

Gpt is really good in vision stuff, or at least their MoE seems to be really cohesive. From my experience Claude models can be really good at language but the moment they need to look at a picture and decide why the design is not good what parts need improvement it degrades a lot. My easiest benchmark is giving them a screenshot of a feature in my app and tell it "identify non-normative UI blocks and improve readability and consistency". Sol does a great job at re-structuring the page into composable units that build upon each other and the general looks and feels of the app. Claude tends to over-focus one one part while completely forgetting about the rest or the cohesion as a whole.

You can compile to Linux targets though

A game inspired by living in Berlin for 5 years

Compactions are supported and heavily recommended! https://github.com/welidev/scroll/issues/1

Doesn't webhooks put even more work on them? You need to create a webhook dashboard, sometimes with multiple environments and administration endpoints, a way to set HMAC secrets, retriability and deliverability mechanisms, a local tunnel CLI for development, etc. With scroll if you already own a event log system the only work you need to do is exposing it to the client securely, same API keys as the rest of your existing REST api's.

> That seems unlikely to me, but I might be surprised.

I'm pretty sure you've hit the nail on the head. Especially now with LLM's you'd be surprised of how many people are running full on production apps that are coded solely by an agent, deployed with a mix of random providers (supabase + fly.io + whatever) and have no clue about what Kafka is. They are never going to ask for it because... they don't know they can, and why they should. They ask an agent "connect to stripe" and the agent codes your typical webhook ingestion mechanism, never proposes advocating for an event polling loop. Whenever there is a bug they will tell the agent to fix it and the agent will just write a webhook deduplication mechanism and that's it. You'd be surprised how little supposedly technical people care about the current state of technologies.

PS: Thanks for the feedback on the writing.

Not only this but the spec explictly allows provider-terminated connections followed by a 429 with a respected "Retry-After" if you want to definitely kick "slow" feeds. This combined with HTTP2/3 multiplexing makes holding feeds open pretty cheap.

I reached out through email :)

Just one correction. My spec doesn't force /scroll/ URL's, just proposes it as a convention.

Stripe events API is one of the examples of how to do things properly. And SCROLL is just trying to create a common spec so that everyone offers a stripe-like event polling api.

That is completely fine. In the spec cursors just need to be lexicographically comparable. They could easily be timestamps if the provider chooses to. In many of my example they are just alphanumeric dictionaries.

Maybe the LLM has written maximum 50 words of the article by just being directed to switch things around and improve grammar and or internal consistency

For the morale of the person who created the PR, closing every PR you make is pretty similar to just being banned

I'm not upset because LLM disclosure is mandatory. I'm upset about the consequences this has and how easy this makes for people to gatekeep new IC's under false and difficult to prove pretenses.

"This looks like AI, closed". And you as a new IC with no connections, no community visibility have no recourse to fight back against it. Anti-ai people love boasting about humans > systems and forget about those humans that will surely be negatively affected by this, even if low number.

If you are a new programmer who is just learning and spend time creating a PR for a project you have a lot of respect for and the first interaction is someone falsely accuses you of using LLM's then closes your PR you've now removed someone who could have genuinely grown into your community from ever joining.

Not only that but since now you are by default a suspect of having used an LLM (and you need to prove you didn't use one) why even bother not using one? You are going to get accused of it either way.

Please! Would love HN meetup in Berlin.