8 ms·
A lot of negativity here, mostly based on the 90s site. Reading the excerpts, what the author is doing is quite clever. He creates an identity, the reliable, e
by shubb 13y ago
A lot of negativity here, mostly based on the 90s site.
Reading the excerpts, what the author is doing is quite clever. He creates an identity, the reliable, effective Senior Engineer.
The reader wants to be more like that identity, so he takes you through different situations and says, 'This is how a Senior Engineer would act and think in this situation'. For example, [A senior engineer would not ship his code until it was really production quality, even when rushed].
The situations and issues he talks about are often a result of social pressure (to ship, to deliver features that don't matter in order to show progress on the burn chart). It's easy to get caught up in those moments. If the book allows you to step outside that, and think 'What would a true Senior Engineer do here', and the answer is 'The long term right thing', I think it's valuable.
But not $25 of valuable. Sorry, that is too much for a speculative purchase (which this is, given the author isn't a known quantity like Jonathan Locke at bottom of the thread.