News for hackers. Stuff that matters.
Re:When is a senior engineer not a senior engineer? by watwut on Saturday March 03, 2018 @02:44PM (#16511154)
Have you even read article? Customer was happy with smaller scope and it was agreed upon in advance! The original project got large also due to change requests and conflicting requerements, these got managed this time.

I did worked on complex projects and estimations, negotiation and communication about delays is more important there, not less. So is ability to work with people you don't like or consider lesser.

Given that the same team was able to produce smaller scope project, it is pretty sure they were able to do at least some parts of original project.

The rest frankly reads like fanfiction. As heroic as decision to spend nights in work and do it alone was, it was not rational decision.

Re:When is a senior engineer not a senior engineer? by bitL on Saturday March 03, 2018 @05:50PM (#16512169)
Obviously I was using a hyperbole, amplifying some angles, to get my point across as I thought that in your replies there was a lot of one sidedness. Frankly, I have seen many companies normalizing mediocrity and chasing away their best developers, or even blaming them for their own shortcomings, instead of fully utilizing what they could offer them, which IMO is a tragedy. So instead of just agreeing to what most replies alluded to, i.e. the Rick was a mediocre, uncommunicative and disorganized asshole with a heroic complex, I offered an alternate point of view that maybe the bigger problem was on the other side, for the sake of balanced view.