Hacker News new | past | comments | ask | show | jobs | submit login

On your final point, I hope the engineer realized how obviously dumb the move was.



Nah, not sure it really stuck. Both times I saw it they were more interested in being 'technically right' rather than see the trust between companies that they were destroying.

It's interesting because in that environment building trust was sometimes more useful then being the best GPU/perf engineer. I had developed a reputation of not reaching out to the support teams unless it was a problem that I characterized pretty well. I'd uncovered enough driver bugs with one vendor that I was given personal contact info of senior engineers on the vendor's side and told to reach out to them directly in case of any further issues.

That meant I could skip 3-4 levels of support and cut out ~1.5 weeks of back and forth verification of issues. As such I was able to close on actual critical perf/functionality problems much faster than just about anyone else.

Much like you should treat your IT/support staff with a ton of respect(because they never get a shoutout when things go right and always get thrown under the bus when things go wrong), showing you that respect people's time and only raise issues with in depth repros goes a long way. I'd much rather have a collaborative environment like that then resulting to escalating through your account rep/director/vp. Both gets the job done but one will have the other team dragging their feet every step of the way.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: