Help me ask why you didn't just
11–20 of 363 posts
Re: Help me ask why you didn't just
#12Re: Help me ask why you didn't just
#13"Can you walk me through what you've tried so far?"
Re: Help me ask why you didn't just
#14> That's an interesting solution! I don't know whether I would have thought of that. My first thought was to use sshd. Can I show you something?
Re: Help me ask why you didn't just
#15That's my go-to phrase. It implies that I am looking to be educated, and not that I think they messed up.
Re: Help me ask why you didn't just
#16And honestly I think phrasing isn't that important - if you know someone for months or years and aren't usually a dick - people won't automatically assume the worst.
Also this may be cultural. I've worked with English people and with Germans and the level of acceptable criticism and required disclaimers was very different. My own nation (Polish) seems to be somewhere in the middle but closer to Germans.
Re: Help me ask why you didn't just
#17Re: Help me ask why you didn't just
#18I tend to use “How come you you didn’t use x?” Or even “how come X didn’t/wouldn’t work?”, and let my body language and facial expression indicate genuine curiosity,and maybe even perplexion at the scope of problem. I don’t feel Author considered the non verbal ways of communicating intent. “How come” feels slightly lest antagonistic then simple “why” but that may well be regional differences
Re: Help me ask why you didn't just
#19Why don't we just use a jsonb column and put all the attributes in there instead of inventing a complicated table structure?
My take on this is always: if you so lack understanding of the problem space that you can't understand why everyone is discussing something complicated, stop proposing solutions until you do. When you do understand that, come back with your reasoning:
Although a relational structure is a better way to do this in general, I think in this situation it isn't necessary because the format of the data is intentionally client specific and opaque to our code. We might be able to simplify things a lot by storing it as a jsonb field