189 karma · joined August 10, 2017
No one should be judging you if it's not your thing. Those of us that enjoy it readily admit its faults and own the fact it's not a game for everyone.
“In order to be effective working at any layer of abstraction you must have in-depth knowledge of the layer below where you’re at”.
To be the most effective at AI assisted engineering (if treated as an abstraction layer) you need to understand how code works, behaves, architectures etc. and what well performing, well built things look like. Doesn’t necessarily mean you have to know everything like you would pre-AI, but enough to be effective.
https://ziglang.org/news/migrating-from-github-to-codeberg/
See the "Exhibits A,B,C" links.
I think my biggest point further down is that you have to _already know_ that it's a bad idea - if you don't you can't instruct the agent to avoid it. What I see is so many more developers who just never get to that point now.
> For many people in this industry this became the default when Google and StackOverflow appeared. Is AI really so much different there if you look at the root cause? I feel AI is just another tool for quick answers without investing time in understanding the problem. That mentality is not new and has not changed in decades with previous knowledge bases. Sadly.
Excellent point :)
Remote: Yes
Willing to relocate: Yes (except to Seattle, CA, New York, Florida or Texas)
Technologies: Rust, Node.js, Go, Vue, Azure, Big Data Tools
Resume: https://drive.google.com/file/d/1R3YWdfAd_aYqQ8BzCNNx1RXr_77...
Email: johnw.darrington@gmail.com
I'm currently working as an architect for the Idaho National Laboratory. Looking to broaden my horizons - literally. Hoping to find something that can get me and my family out of Idaho.
I've worked on big data systems and management for a while, helping write a custom data lake for INL in the process. I've managed teams and projects at various sizes. I'm hoping that I can make a difference somewhere and build a great product and team.