computer programmer. self-taught.
Greece
Joined May 2011
- Tweets11.9K
- Following135
- Followers146
- Likes29
anthony boudouvas retweeted
in the history of banking, not a single "more efficient" cost cutting was good for their customers. just saying.
anthony boudouvas retweeted
AI was supposed to make us work less
I've never been this tired in my life
most days I have up to 10 agents running at the same time. one fixing a bug, one writing pages, one refactoring something I already forgot I asked for, 3 other I have no idea what they are doing but i suppose i ask it?
and I jump from conversation to conversation all day
compared to 5 years ago, I probably context switch 100x more
by the end of the day my brain is fried. completely toasted. nothing left, not even for the people I love
I call it the fried brain effect
thought it was just me but almost every founder I talk to lately says the exact same thing
we got superpowers, and somehow the pressure only went up. if you can ship 10x more, you feel like you have to ship 10x more. every single day
I don't have a solution
honestly I have no idea where this goes from here
anyone else feeling this?
anthony boudouvas retweeted
interviewer: your C++ class has a copy constructor but no move constructor. what happens here?
me: std::move gives a compiler error?
interviewer: no, it copies
me: fine. i'll check is_move_constructible first
interviewer: that returns true
me: because it can copy?
interviewer: yes
me: so the class claims it can move, demonstrates that it can't, and i'm the one failing the interview
anthony boudouvas retweeted
Google: “[Swift] has matured into a viable systems and cloud language, pairing Rust-like data-race safety with predictable, reference-counted performance.” Announcing their Swift-based cloud SDK for backend services: cloud.google.com/blog/topics…
anthony boudouvas retweeted
JavaScript was never designed for the server. If that doesn't change soon, JavaScript on the server will be replaced by Rust.
The fix needs to happen in the engine. Sound types. Ahead-of-time compilation. Threads with shared objects.
"I love Rust! Rust is amazing ...if you never, ever, EVER have to look at it yourself." — @dhh
anthony boudouvas retweeted
Swift is swift, then I rewrite class to Objective-C and
change is: 21.3 ms→95 µs at 1M units, 384 µs→6.4 µs at 67K
there is no comparison. rewrite 1:1.
anthony boudouvas retweeted
I belive you because claude said: "while retaining code quality"
Just one engineer and a team of agents ported the GitHub Copilot agent runtime to Rust, shipping 800,000 lines of production code while retaining code quality. 🚀
How it worked 👇
github.blog/ai-and-ml/genera…
anthony boudouvas retweeted
I am done with this shit. It is over. The state of engineering right now is horrible. It has been half a month since I started a new role at a big company. Nobody knows anything here. The specs, code, tests, PRDs, tickets, resolution of those tickets, reports, etc., everything is made by Claude Code. Nobody on my team likes this. They are being forced to ship as much as they can. I have heard multiple times from higher management that pushing code is not a bottleneck, so why are we slow? People are working 12 to 13 hours a day just to press enter. Nobody is reading anything. Humans in corporate are doing nothing on their own. Everyone, literally everyone, from an L1 to an L7 engineer here is doing the same thing. Talk to Claude. There is no sense of victory. Nobody is resolving bugs. In reality, nobody is thinking anymore. Everything is done by LLMs. It is so soul-sucking. I would not mind it, to be honest, if we were at least given the time to check out the code and see what is going where. But no, the goal is to just ship. No matter what happens.
anthony boudouvas retweeted
My friendly reminder, after Microsoft software caused billions in damage due to benign features being chained together (ILOVEYOU) and then a bunch of Windows Server ecomm apps went down over holidays (and more), Microsoft just said:
"So now, when we face a choice between adding features and resolving security issues, we need to choose security. Our products should emphasize security right out of the box, and we must constantly refine and improve that security as threats evolve. A good example of this is the changes we made in Outlook to avoid e-mail-borne viruses. If we discover a risk that a feature could compromise someone’s privacy, that problem gets solved first. If there is any way we can better protect important data and minimize downtime, we should focus on this. These principles should apply at every stage of the development cycle of every kind of software we create, from operating systems and desktop applications to global Web services."
Full text: "Trustworthy Computing" January 2002. archive.is/6T7hl
We did this on our own. We did not ask for regulators to tell us. We had the data. We knew the issue was in the software. It was super difficult in the competitive and customer-demanding world we worked but we did it.
It is so confusing to me that the AI companies are acting so helpless and in need of oversight to prioritize making the right product. What do they think regulators would know about building their products that they do not know?
How much more evidence do we need?
anthony boudouvas retweeted
people were typing "RIP Steve Jobs" using software built on Ritchie’s work. he died that same month, and so many of those people never even heard about it.
jobs deserved the tributes. i just wish more people had known who else we’d lost.
somewhere that week, someone might have been writing their first "hello, world" in C, excited about everything they were going to build, without knowing the man who gave them that starting point had just died.
be dennis ritchie
> create C
> co-create Unix with Ken Thompson
> give generations of programmers the foundations to build on
> win the Turing Award
> your work reaches billions of people who never learn your name
> die in October 2011, while the world is mourning Steve Jobs
> your death makes far fewer headlines
> somewhere today, someone writes their first “hello, world” in your language
imagine building something so lasting that people begin their life’s work inside yours.
anthony boudouvas retweeted
the lessons (vague) from the "Shopify goes native apps" is this
- keep senior human in the loop
- don't trust the machine for doing things
- read the code (review the code)
