Do we really need humans writing code anymore though? Another year of development and AI is just going to be superior to a human writing code. It's already about 90% there.
Humans still write the code, we just do it using AI tools.
If we abdicate and let all software development and operations occur through the use of fully autonomous agents, someone is still ultimately responsible for the agents work/screw-ups. Thus, there is still a human writing code, from an ownership perspective. We all know it won't be the capital/manager class holding the stick there.
I don't even care about that. Sure, use LLMs to write code. But the way Andy talks to his employees and treats them is so disrespectful, I find it actually despicable.
Unfortunately, it's not super easy for me to migrate away from Proton, but it's the next personal tech project I'll undertake.
Prototype self-driving cars where able to handle 90% of driving around 1990. Sometimes it is very hard to go from something that works very often to something that works always.
Depends on what do you mean by "writing code". Once, writing code meant punching holes in pieces of paper and feeding that into a machine. Then the technology changed. Writing code became entering cryptic numbers into the machine. Then the technology changed. Writing code became typing words and punctuation that have some passing connection to English but otherwise meaningless to a non-professional. Then the technology changed. Writing code became much more like writing text but still not resembling any actual text. Then the technology changed... It will change again. It still won't magically produce something sensible out of nothing.
You are right. Let's just hand the keys to everything to the AI companies. They've proven to be trustworthy and ethical. I trust them so much, I'm just going to stop thinking and say yes.
FFS. ProtonVPN is borderline irreplaceable as one of the three or so VPNs that you don't have to trust because they've been tested in court not to have VPN logs. Losing one of them hurts.
Based on my own usage, one of the things that AI continues to be really, really shit at is data governance. And this is a place where a “move fast at all costs” attitude simply will not do. It is just so very easy to accidentally start leaking data in a way that undermines privacy safeguards.
https://www.tuta.com/
Is the only other major player I am aware of— although they have a significantly smaller product lineup than Proton, and aren’t as viable an alternative to Google for those who want a fully integrated suite.
Tuta does Mail and Calendar fairly well, cant speak to their drive product.
The CEO sounds like .. a loser. :) I'm kidding! He sounds very smart!
If the company isn't going to hit revenue targets they might actually need to fire people and this can be a good way to provide cover that devs aren't meeting requirements so they can be fired with cause.
A past company CEO sounded very similar to this internally before they fired 30% of the staff because they didn't have enough money.
My current vibe reading on CEOs who think every job can be done with AI today is the athlete who starts celebrating before crossing the finish line, to be passed bysomeone who takes the win. My guys, it's not that good yet!
Being cruel to your employees qualifies, regardless whether they care about the product, IMO. And it seems like those employees did care. Words matter and shape the environment people work in.
Failure to take advantage of available tools does not suggest whether you are a good guy or a bad guy, just whether you are a competent guy or an incompetent guy.
> “That’s bullshit and loser thinking. Of course it’s possible to be fast and secure,” Yen wrote in the channel at the end of August.
What a jerk. I agree that security doesn't have to be given time—like all software, implementation takes the time it takes.
But he doesn't have to be such an asshole about it. In my book, there's nothing more representative of "loser thinking" than casting petulant aspersions like "loser thinking."
After everything in the past six months do we really think that humans are better than coding agents at writing secure code?! This announcement honestly makes me more confident not less in their products.
The issue is that, per the article, "Andy Yen, the CEO of Proton, had a message for an employee in the company’s security Slack channel who urged the company to at least take a few days to pentest newly written code before pushing it live. “That’s bullshit and loser thinking. Of course it’s possible to be fast and secure,”
I think anyone who has been working around in IT long enough, knows that it is in fact very, very hard to be fast and secure. Even with AI.
There’s going all in on AI adoption, then there’s what proton has done.
This is disgusting, full stop. Destroying any sense of trust in your company by allowing people to rat on others is going to bite them in the ass.
And all for AI, which ultimately is a tool that the largest portion of people already have adopted and those that haven’t often understand it’s the way forward anyway. Like instead of letting your people do this organically, maintaining trust in their org, you poison it instead. And for what? A few extra dollars in the bank? The greed is gross.
Article seems somewhat one sided to me. The style of the CEO doesn't sound good, but there's no discussion of specific tooling, harnesses, and other automation they have in place. Reading the letter posted, it sounds like they've got more in place than the article implies but people have been resisting adopting.
Yeah this sounds a lot to me like blowback from current or former employees. There's no specific evidence yet of bad security practices, but the mere suggestion of it is a problem for a company whose image is centered on privacy. It's a knife well-aimed by someone who knew where to aim it.
Fully expecting this will get me a torrent of downvotes here, but...
I'm not sure he's wrong. I'm speculating here but I can imagine the kind of developers Proton attracts--likely people who care a lot about the code and who care about the craft. That's fine, but when you're running a company in this environment, and that's what things look like internally, you do have to be a little brutal to shake people out of old ways. A manifesto titled "Your old job is gone" may actually be warranted.
It sounds a lot like there are people internally who are still fighting the shift, and they've taken to leaking things that hurt the company's security image. Part of the CEO's job, if he's going to push hard in the direction he's decided on, is to fire those people who will undermine it before they do. That this has all now backfired is entirely on him. Maybe he thought he was "motivating" people by calling them losers, or shaking them out of an outmoded way of thinking about what we do, but none of that matters when you have employees attacking your main selling point and the core image of the company in public.
He's not wrong that he needs to move fast, or that processes need to change, or that the job has changed, but his execution isn't so great.
45 comments
[ 4.9 ms ] story [ 29.2 ms ] threadIf we abdicate and let all software development and operations occur through the use of fully autonomous agents, someone is still ultimately responsible for the agents work/screw-ups. Thus, there is still a human writing code, from an ownership perspective. We all know it won't be the capital/manager class holding the stick there.
Unfortunately, it's not super easy for me to migrate away from Proton, but it's the next personal tech project I'll undertake.
/s
Any good alternatives?
The other option is self hosting.
Don't worry, they can vibe code the rest in no time. /s
If the company isn't going to hit revenue targets they might actually need to fire people and this can be a good way to provide cover that devs aren't meeting requirements so they can be fired with cause.
A past company CEO sounded very similar to this internally before they fired 30% of the staff because they didn't have enough money.
My current vibe reading on CEOs who think every job can be done with AI today is the athlete who starts celebrating before crossing the finish line, to be passed bysomeone who takes the win. My guys, it's not that good yet!
What a jerk. I agree that security doesn't have to be given time—like all software, implementation takes the time it takes.
But he doesn't have to be such an asshole about it. In my book, there's nothing more representative of "loser thinking" than casting petulant aspersions like "loser thinking."
I think anyone who has been working around in IT long enough, knows that it is in fact very, very hard to be fast and secure. Even with AI.
This is disgusting, full stop. Destroying any sense of trust in your company by allowing people to rat on others is going to bite them in the ass.
And all for AI, which ultimately is a tool that the largest portion of people already have adopted and those that haven’t often understand it’s the way forward anyway. Like instead of letting your people do this organically, maintaining trust in their org, you poison it instead. And for what? A few extra dollars in the bank? The greed is gross.
I'm not sure he's wrong. I'm speculating here but I can imagine the kind of developers Proton attracts--likely people who care a lot about the code and who care about the craft. That's fine, but when you're running a company in this environment, and that's what things look like internally, you do have to be a little brutal to shake people out of old ways. A manifesto titled "Your old job is gone" may actually be warranted.
It sounds a lot like there are people internally who are still fighting the shift, and they've taken to leaking things that hurt the company's security image. Part of the CEO's job, if he's going to push hard in the direction he's decided on, is to fire those people who will undermine it before they do. That this has all now backfired is entirely on him. Maybe he thought he was "motivating" people by calling them losers, or shaking them out of an outmoded way of thinking about what we do, but none of that matters when you have employees attacking your main selling point and the core image of the company in public.
He's not wrong that he needs to move fast, or that processes need to change, or that the job has changed, but his execution isn't so great.
He'll probably survive just fine though.