"It’s hard to find programmers these days who aren’t using AI coding assistants in some capacity"
I don't think this is true at all. In fact there are major tech companies that ban the use of AI when coding and those folks do it for their job everyday without an llm.
I could have understood it in a month - onboard, try something out and decide if it helps. But a week and then a meeting on a Saturday to explain why or get fired?
Management is hard so I’m generally a little more patient with managerial missteps. But this is a different level of unreasonable. Heck a lot of developers in the finance world adopt slowly because they’ve worked with compliance departments and it becomes a habit.
One week is a big part of the idiocy here. Anyone half busy with anything is going to miss miscellaneous bullshit from management like this, especially when management is prone to these "flights of fancy" with random tooling or the new hot thing.
I personally ignore or delay things all the time because of actual work I'm doing. If running some random AI tool is more important than "keep the company working," that's a really sick and fragile culture.
A mature CEO would characterize the "not good reasons" engineers had for not onboarding.
I think most people would agree that engineers outright refusing to comply with what was asked of them would be a "not good" reason for not onboarding.
But Brian Armstrong is playing Strong CEO for the podcast circuit. So he can't admit that engineers were let go for potentially justifiable reasons. He has to leave room for speculation. Speculation that maybe some engineers were let go for trivial reasons, because Brian is tough, and tough Brian demands complaint employees.
The people who didn't comply because they were on vacation and then had to go to a Saturday meeting to explain themselves think Brian is something -- but I guarantee it's not that he's tough.
We've all seen this playbook before. This is the incredibly dumb, Idiocracy-emulating world in which we now live.
I tried AI for coding in my own time since the very early days of GPT 3.5 but I didn't try it in my day job until much later when Cursor came out. Now I use Claude Code frequently.
IMO this was the optimal approach, trying in my own time and not risking damaging the company codebase until it was safe... But I might have been fired, by the sounds of it.
Because consumer investments is where we should "appreciate mediocrity." And yes, that's a real quote from a pro-vibe coding blog post whose URL ends with /youre-all-nuts/ [1]. Absolutely wild, lol
Readit News
I don't think this is true at all. In fact there are major tech companies that ban the use of AI when coding and those folks do it for their job everyday without an llm.
Management is hard so I’m generally a little more patient with managerial missteps. But this is a different level of unreasonable. Heck a lot of developers in the finance world adopt slowly because they’ve worked with compliance departments and it becomes a habit.
I assume "onboard" means something like "set up an account and get it working locally".
I personally ignore or delay things all the time because of actual work I'm doing. If running some random AI tool is more important than "keep the company working," that's a really sick and fragile culture.
> Well, I thought I remembered you saying that you wanted to express yourself
A/V reference, for those inclined: https://www.youtube.com/watch?v=F7SNEdjftno
I think most people would agree that engineers outright refusing to comply with what was asked of them would be a "not good" reason for not onboarding.
But Brian Armstrong is playing Strong CEO for the podcast circuit. So he can't admit that engineers were let go for potentially justifiable reasons. He has to leave room for speculation. Speculation that maybe some engineers were let go for trivial reasons, because Brian is tough, and tough Brian demands complaint employees.
The people who didn't comply because they were on vacation and then had to go to a Saturday meeting to explain themselves think Brian is something -- but I guarantee it's not that he's tough.
We've all seen this playbook before. This is the incredibly dumb, Idiocracy-emulating world in which we now live.
If i was working on a finance or finance adjacent company i'd be very hesitant to use anything that might send data outside the company.
IMO this was the optimal approach, trying in my own time and not risking damaging the company codebase until it was safe... But I might have been fired, by the sounds of it.
[1]: https://fly.io/blog/youre-all-nuts/