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

The lack of any proof reading drove me batty. I struggled get through it.

Something this long shouldn't be written in a single draft. If it's worth nearly 10,000 words, it's worth doing properly.

TL,DR: Guy realizes he was a jerk at the start of Silverlight. Continues to be a jerk, but doesn't notice. Oh, and Silverlight is dead.




I read it yesterday, and decided not to post it here for that very reason. I can live with a typo or two, but the error rate on this was so high as to make it difficult to recommend.


I agree. If you feel what you have to say is important enough for other people to read, put some time into shining it up, and making it readable.

Otherwise you leave yourself open to criticisms like: "If he can't execute on the small things in a blog post, then no wonder Silverlight is dead" etc.


It's terrible writing. How many sentences randomly end with a question mark?

> A guy I barely knew but was in charge of the video side of Silverlight?

> Fine, I thought maybe I can get a fresh perspective and start something new in this team?

> Iā€™m riding the Junior bench on all these ideas that he stole from not only Brad (my old boss) but also me?

Seriously?




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

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

Search: