91–99 of 99 posts
I’ve been doing this for 20 years. I see it as you having two primary options. You should stay there, learn the new tech, and see what happens. If it works better than you expected, then your mind will be changed and you’ll be well positioned for the new economy. If it turns out how you expect, now you have experience working with this tooling to inform your positions at your next company. Either way, a few months in…
Nah. There's always pointless fads and food fights. Just tough it out. (Until a better gig comes along.) I wish I could advise my young self "this too shall pass". The savvy play is to be a "team player". All those dumb hills I choose to die on... For dumb crap which eventually self-mooted all by themselves. There was a comment (or a story?) some time back about how to survive as a software developer when projects ar…
It's wild to me that somehow we're wrong for not wanting to have to do this every day to get by...
> I'm a 'senior engineer' with ~5 years of industry experience
What is the definition of junior, mid (?) and senior engneer? I've been writing code profesionally for over 20 years, but I'm not sure if I'd call myself an engineer at all, let alone a senior one.
Personally, I had try to have a candid discussion with your CTO/CEO about your concerns and see if there’s room for a more balanced approach. If it’s clear they’re not interested and you start feeling your skills are stagnating, it’s reasonable to look for a company whose engineering values align better with yours.
Ultimately, AI tools are “just tools.”
Nah. There's always pointless fads and food fights. Just tough it out. (Until a better gig comes along.) I wish I could advise my young self "this too shall pass". The savvy play is to be a "team player". All those dumb hills I choose to die on... For dumb crap which eventually self-mooted all by themselves. There was a comment (or a story?) some time back about how to survive as a software developer when projects ar…
> Everyone lies, needs to suspend disbelief... It's wild to me that somehow we're wrong for not wanting to have to do this every day to get by...
Does the person lying to me know they're lying? Surely they know that I know, right?
I'm also terrified that I'm lying to myself. Am I just in denial? Is some level of wishful thinking necessary? What are my blind spots?
I'm no smarter about any of this stuff (The Human Condition) than anyone else.
ICYMI, I enjoyed the book Everybody Lies by Seth Stephens-Davidowitz:
https://www.goodreads.com/book/show/28512671-everybody-lies
Please share any books, links, observations you have. TIA.
We now have access, but that CIO is also gone and we don’t hear about it much anymore. We still have the tools, and a general AI (for use outside of code) is coming, but the blind hype seems to be gone.
Maybe your leadership will shift, or come back to reality in time.
Personally, I think it’s a red flag when leaders jump on hype trains that hard. They’re so desperately trying to avoid missing the boat that they ignore common sense and risk. Not good.
It's the same elsewhere. Some places are actually using it as a way to get rid of people 'resistant to change'. It also remains to be seen what technical skills we need 5 years from now. I did memory management and pointers 15 years ago and I can still do them now. What I'd suggest is adapt to it, find ways to push back. Obviously things like "delete entire unit test file & have claude generate a new one" is a bad id…
> I've seen claude "monkey patching" a system so that it returns true to the tests. I’ve watched Github Copilot do the same thing. I’ve also seen it doubling down on ridiculous things and just spewing crash-laden messes. There seems to be a low upper ceiling on how “competent” it is, which makes sense.