--Originally published at cerros27
Deadline, Chapter 16
--Originally published at cerros27
The Deadline – Ending
--Originally published at Coder Bebop
It is always hard to say goodbye to a story, especially one that teaches you something elementary. Even with a unidimensional character such as Webster Tompkins, who strives for greatness through the help of his friends (not very different from other characters). I suppose this was made be so average readers can identify with someone ordinary in an extraordinary situation.
I liked the ending, I would have expected it to be a lot flatter, so it was rather surprising to see this little twist. Though, there is very little development on her relationship with Webster, so you can’t really say we earned this. But meh, it was a happy ending for an ever uplifting story about true management, simple details.
On a side note, it would have been funny if Laksa had contracted herpes from her Belok mischief, too.
Guest Speaker Reflection Iliana Valdelamar Flextronics
--Originally published at cerros27
Deadline, Chapter 15
--Originally published at cerros27
The Deadline Chapter 22
--Originally published at Coder Bebop
Not too much happening here, it was funny seeing Tompkins get back at Belok and having his top-of-the-world moments with tthe magazine journalist as well as giving Bill the idea to buy th US.
Deadline, Chapters 13 and 14
--Originally published at cerros27
Deadline, Chapter 12
--Originally published at cerros27
Guest Speakers Reflection Lucio and Candelario Gutiérrez
--Originally published at cerros27
The Deadline Chapter 20-21
--Originally published at Coder Bebop
I was craving for these two chapters to end so I could complain about the anticlamatic way the Belok affair was taken care off, but the author saved himself from getting burned in the last two pages of chapter 21.
Miracles may happen (but don’t count on them).
Webster Tompkins
Guess that is one way to teach a pseudolesson (?).
Just a few paragraphs before we were having an explanation on how if we do a terrific design from the beginning, there is not even need to do inspection in the end, which was nice, but did they need two whole pages to say that? I think the author spent more time looking into technical details such as function points et cetera, rather than give us a better resolution to the hierarchical problems. I literally skipped all that and perfectly understood how the progress was going.