I think, for me, I am often on two sides of the situation.
1. I'm moving fast and writing code to get things done for the customer and the product.
2. I have enough time to slow down and write or refactor "testable" code.
Often 1 results in untestable code. Often 2 results in a refactor or most likely a rewrite to create testable code.
This is an important difference. Optimizing to write code just because you think is clean (in the sense of shorter, reusable code) is often confusing to most. This also leads to pull requests that grow large and are hard or time consuming for others to review.
I don't wear a watch most of the times, I feel like wearing one to bed would be uncomfortable. Maybe I should hack together a sleeping monitor that tracks movements during sleep using a Kinect camera...
Hey amingoia, thanks for responding. I think the worry here is bigger than this single situation and is really about package maintenance and ownership for the community at large. This is a very popular package. Selling it to anyone just to move on is a burden on open source. I will say it is completely your choice here, but as a consumer of the package and the other 130K+ a week I would urge you and others to be a bit more careful when transferring ownership.
I got a Lenovo Y510p. Amazing machine. Running Ubuntu 13.04. The most common problem with any linux machine is FLASH VIDEO! They don't support DRM content (HBOGO, Amazon, xfinitytv, etc...). It's been a pain trying to find a work around. Also, video drivers can be a pain.
Don't. The Y510p has a really cheap screen. I know its price sounds enticing. I compared its screen with my Macbook Pro and it looks very "washed out".
I think, for me, I am often on two sides of the situation.
1. I'm moving fast and writing code to get things done for the customer and the product.
2. I have enough time to slow down and write or refactor "testable" code.
Often 1 results in untestable code. Often 2 results in a refactor or most likely a rewrite to create testable code.
This is an important difference. Optimizing to write code just because you think is clean (in the sense of shorter, reusable code) is often confusing to most. This also leads to pull requests that grow large and are hard or time consuming for others to review.