Location: Croatia
Remote: Yes
Willing to relocate: No
Technologies: Android, Flutter, Kotlin, Dart
Résumé/CV: https://dmilicic.com
Email: [email protected]
Location: Croatia (EU)
Remote: Yes
Willing to relocate: No, except for the right opportunity
Technologies: Android, Flutter, Kotlin, Java, Dart
Résumé/CV: https://www.dropbox.com/scl/fi/ajks1rbmfa095f9cm9m0v/dmilicic.pdf?rlkey=tm1fxreew9c7ws2c16qvxrgt5&dl=0
Email: [email protected]
Location: Croatia (EU)
Remote: Yes
Willing to relocate: No, except for the right opportunity
Technologies: Android, Flutter, Kotlin, Java, Dart
Résumé/CV: https://www.dropbox.com/scl/fi/ajks1rbmfa095f9cm9m0v/dmilicic.pdf?rlkey=tm1fxreew9c7ws2c16qvxrgt5&dl=0
Email: [email protected]
I've been back and forth on this, but after working on a few AI-coded apps, I have, for now, confirmed my belief that it still matters whether the codebase is robust.
Firstly, I believed that it does not matter what's under the hood if it works. But I found that I can't make it work without the code being robust, testable, and maintainable to a certain degree.
Therefore, I am linking my article that explores this a bit more and shares what I think are the three most important points that you should still care about writing good code, which are:
1. AI will train on it - the most long-term reason, most people won't care, but it does affect everyone
2. You still need to do the final touches - it's probably not a good idea to prompt for one-line changes, it's like calling an electrician to change the lightbulb
3. Software is never done, and it should be easy to change - AI will struggle with more tokens, and you with more time, if your code is not of good quality
Anyway, I am just sharing my shower thoughts and hopefully will start an interesting discussion.
100% human written with AI used for spelling!