I still don't know how to cope with bosses who think you haven't done shit because they don't see an interactable UI yet.

I felt a bubble of anger rising inside of me while reading this

UI is key for the users so why should it differ for your boss? Why don’t you implement the UI first?

@lastNick I disagree, planning stuff out, setting up infrastructure, endpoints etc. can be just as important

@alexbrooklyn Users don’t care about such things. On the other hand: your architecture should be defined beforehand.

@lastNick I agree that users don't care, backend and devops is mostly magic that just works.

But that does not mean the person in charge of the developers does not understand the work that goes into the backend. My boss fully understands what goes into developing apps and he also respects the time given to backend development.

Also on 'architecture should be defined beforehand', defining it also costs time and so does setting it up properly, time not spent on UI.

Perhaps I'm not understanding your point

@alexbrooklyn My point is UI is key. Even if your boss is totally aware of the effort it takes to implement the backend he/she has to make money and even a photoshopped UI sells better than every “magic” backend.

I assumed that your done with requirements and software architecture because you already started implementing. At this development stage you can start with the UI so your boss has/can show something to users/the customer.