It's because I'm away or simply because I don't want to answer. (You decide)."

That was my status message on my IM clients and I never used the "away" status. For some reason it worked, because it left to the sender with the responsibility of deciding what was the actual reason for not receiving an answer. And because that simple reason no-one ever felt offended because no-one wanted to think that I do not want to answer.

I think we have a really deep cultural problem, fueled by the IM applications were there is an "expectation" of being available all the time... With the message status confirmations is even worse. Sometimes you simply cannot answer (I.E.: you check your phone in the middle of a meeting and is nothing of importance so you can answer after the meeting is finished).

We need to learn again to not to expect an immediate answer.

Me too here!

We work on embedded development. We focus mostly on design production-prototypes (Systems that are close enough to what you'll get if you manufacture 10,000 units in China).

Really often we have to do the "full-stack" that includes as you said starting from the HDL, doing the circuit & PCB desing, generate a BOM, going through chip-datasheets to provide the minimun stack to run anything, providing network connectivity and send data to the cloud to be consumed by a client-app.

We don't call ourself full-stack developers (even we do the real full-stack) because we don't think that anyone can do everything and do it well.

Our prototypes most of the time are proofs of concepts that are latter supported by a development team that segregate the different development goals and have different people focused on the specific parts of the system.

In "business-jargon" "full-stack developer" usually means "We are a bunch of cheap assholes that don't want to pay for a full-development team".