Microsoft knows who he is because he alleges they deleted his Microsoft account and flagged his GitHub. And he says he was "publicly humiliated" in a CVE so I assume his name was on it.
> it more difficult to identify who to invite to join the priesthood.
How about this. Somebody forks the project and submits their patches to the fork . If the fork is successful (there are users actively using it), upstream can selectively go fish for the patches themselves. The maintainer of the fork eventually gets recognized.
Not ideal, I know, but building a reputation is meant to take time.
I think whats more likely to happen is patches & forks stop being shared. If AI continues to improve, I see a world where people are mostly no longer making software for others, but purely for themselves.
I've done it, personally. I've made all kinds of little utilities for myself kind of like a woodworker making their own jigs. While not purely "vibe coded," AI has let me actually finish a ton of personal projects that have been in my "eh, maybe I'll get to that someday" list. Now that there is very low marginal cost to make these tools, they can be highly specific, and they aren't all that useful to others unless someone else has the exact same problem as me, and well if so they can try to vibe code their own tool.
We'll get to a point where most of the open source projects are reserved for large scale infrastructure, as a cathedral not a bazaar, and then the vast majority of end-user level software will be highly personalized, custom utilities that generally aren't shared.
This is also an option with AI patches, if your AI contribution is good enough, let it get proven in use, and then it can be considered naturally as the developers of the original project look at what's going on with similar projects.
Same, I'm currently working more in React project, and I miss Angular so much that I actually use it in my personal project, it can be a genuine pleasure to use if you avoid over-engineering the rest.
React shines when it comes to the composability of components, eg. for data-table with customizable rows. It's still possible in Angular, but it's heavier.
For the rest (syntax, the ecosystem, routing, data-handling, DI), Angular is so much more straightforward. Services with dependency-injection is 99% of the time way simpler to reason about than React hooks, especially when you start to need cascading changes between hooks after user interaction.
A more than valid question! It's the only way I could figure out how to economically convey "I am a Russian who decided to leave Russia to not be complicit and because my history of protests and support for opposition makes it scary to stay, while I completely understand the level of privilege I'm enjoying and can't call myself a refugee even remotely". Even though I always wanted to live abroad, I didn't decide when and how exactly I would emigrate, hence "forced".
You sound like a candidate for asylum? Despite the administration policy, asylum law is still on the books. Might be good to get an application in and cross your fingers for a subsequently more friendly admin.
I am, yes.
As I said, I am aware of my privilege and even though I might technically theoretically be a valid asylum case It would feel like abusing a system designed to help people in actual dire need.
So even though I am more than willing to relocate, I would definitely NOT do that through the asylum process.
Ilia, first of all, from what you've written today, you come across to me like a decent principled person and that's rare nowadays. I admire that.
That said, if I may offer you my $0.02: systems exist for us to fallback on. You might know yourself and your situation best but sometimes the best way to not drown is to take a lifeline even if you know how to swim. I completely understand not wanting to take-up the space of someone in greater need but let the bureaucrats make that call.
I'm not very smooth with words but what I'm saying is, I encourage you to apply for social support systems nonetheless. That's not just specifically the asylum process but I'm sure there are other programs in the EU (for instance) where you might qualify. It wouldn't hurt your situation, let the bureaucrats make the call, I don't think anyone will take it against you.
Huh! Points to you for clarity of understanding. Wish I was an employer able to take note of this :) for now I would NOT take the 'apply for asylum' suggestion, not until we clean house. Could be the dumbest thing you could do right now.
Based on the name, he's either Ukrainian running away from the war, or Russian, running away from being complicit in the war. Shitty situation to be in either way.
I have to admit LLMs are actually quite useful at generating code for me, but I am experienced enough to know what I want. I use it as a next-generation autocomplete.
This is the "whole thing" in a nutshell for me too. It's useful, speeds some things up, but I've been doing this a long time.
The state-of-the-art or medium-term future of the tooling doesn't feel apocalyptic in itself, but the macro forces, implications of scaling, and general reactions to it on all sides are a different story.
It's apocalyptic to the people who previously clocked in, did mediocre work, and clocked out. For those of us willing to put in a little effort, it's just another tool. Though I think there's still a disconnect at the managerial level where they think firing half the team and giving the rest AI is going to 10x revenue.
I'm curious to see how many issues an LLM can find for OpenBSD. Not knocking OpenBSD at all, genuinely curious to see if all the careful development can stand up to LLMs.