greenbee

I have a 5-year old Hackintosh still going strong on El Capitan. I would say a few days each year of maintenance is a minimum to keep it running smoothly and updated.

I started off with free parts from friends and bought a semi-supported motherboard. Since then I've upgraded a GTX, added ram, switched PSU, added TB drives and bluetooth. My advice is to get supported parts as far as possible.

I get a huge productivity boost when I can use it because I can plug in several huge displays and my best keyboards/ mice. It's exactly like having a Mac Pro except slightly more fragile.

I can foresee still using my Hackintosh for the next few years because it's performance hasn't degraded. I will just keep swapping parts and upgrading as needed.

Plan for it to fail during crunchtime, and make sure you keep your Macbook handy. My Macbook Pro and Hackintosh work synergistically to repair and update each other :)

I think yours is a different scenario?

The article suggests that developers trying to match business concerns with technical implementation disproportionately takes up time, as each feature was not spec-ed out and described properly in a technical manner.

Accumulating technical debt would be a delay purely on the engineering side. The engineering team is not always to blame, though.

Having read the Peopleware book, I figured one of the reasons people work at night is to "escape" distractions in the office due to a bad working environment.

I'd like to know if anyone can offer a counterexample to this phenomenon, i.e. work in the day, sleep regularly, and still be just as creative.

On the other hand, Lollipop gave new life to my 2012 Nexus 4. Battery lasts longer on tether, the animations ease load times.

There won't be any more major Android releases for the Nexus 4, but now I think it would last nicely until the next Nexus/ iPhone S appears, which is likely to be a year from now.

One of my domains had it's Namecheap DNS down a few days ago for me. Just this morning, Enom's DNS was failing for another site.

Needless to say, migrated to Route 53 until I find a cheaper solution.

thanks!

I've been using Postman for a while. Overall, very impressed as it was intuitive straight from the first use. However, when putting files in a post request, it doesn't remember the files for you. Also, there is no way to stop an ongoing request besides resetting and clearing all the parameters. I really hope they would accommodate these options in the future.

Without access to spinal fluid or nicely chunked pieces of garbage like molecules

I would be really worried if I started clearing nicely chunked pieces of garbage like things in my sleep.