Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Of course it was just an example!

But even a chat message or an introduction does wonders.

My point was that, from the tale, I don't think the author did enough to actually accomplish the task and that the complaints on the internet public square is hardly justified.

Said so, I find it a well written piece that may be useful to younger engineers approaching these kinds of dynamics.

I would find extremely interesting a similar article comparing when stuff goes well and when they move at high speed highlighting the differences of approaches and results.



> comparing when stuff goes well

I suppose that then the dashboard team would have replied that same afternoon: "Done, here: __", end of story. Without needing any coffee.

And if they (the dashboard team) didn't see how the dashboard was important, they'd kept asking for clarifications until they knew, and then clearly said if they'd do it or not




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

Search: