Commit

d461360

In my experience it is fine for simple prototypes etc. to explain what they want, as long as they don't expect it to be the final outcome or feel they know better than engineers because they managed to create something that seems to be working at surface level :)
Sure, why not. If its their own side hustle they are the captains, meaning they also bear any risks and responsibilities. Of course this can also be an opportunity to learn in the process, but you need to have the motivation for that. A lot of folks don't even look at what is…
Which is where I am torn sometimes. I learn from looking at some code, but other concepts go over my head when applied in detail. I understand the high level and some pitfalls, but most of the time software is a means to an end for me, not really the goal. The problem lies in my opinion with the lack of judgement I can apply to the code produced. I can look at the screen, the files and separation and say: LGTM, but apart from that, I can’t really tell you why x or y implementation is right. Most of the time I’ll just think about the use case and entities I need from it and let it do its thing, test and repeat. I am not really wanting to become a developer really, which maybe maybe a slopper myself, but on the other hand I really enjoy being able to create/direct the software into existence that solve my problems, that I otherwise would have never being able to solve.

commit d461360

I completely understand - AI has enabled us to do a lot of fun things and much faster at that, so I am not blaming anybody for making use of that potential. I think the line I personally draw is when you make things public to be used by other people. You then assume a certain…