Igor's Computer Blog

I tend to quote software trivia  - starting a list for my future reference: Igor's Laws Of Programming 1. No duplicate code 2. Trust Tests not experts 3. Create Issue then whine Design Patterns Gang of Four  - The original patterns that kicked it off. Cloud Design Patterns - MS guide to making great cloud services Enterprise Design Patterns - How to make enterprise apps. Stats Bugs solved by using a static type system  15% . Bugs per  KLOC is a language independent constant @  15-50/1000  . Reading to be a great programmer Pragmatic Programmer  - How to be a great programmer Reading to make great software:  Clean Architecture  -  How to design a large scale system. Agile Principles And Practices  - How to design components. Code Complete 2  - How to write code C# in a nutshell -  The c# book worth owning Fluent Python - Writing great python code Programming in Scala - Learn about language design in an awesome language (honestly I didn't get

Copied from  Seth Godin  as I've always tried to articulate this, but was never able to so I'll copy swaths of his post: I can run a comfortable 6 miles per hour, but I can also run 10 miles an hour at full speed.  But, turns out I can only run 10 miles an hour for 5 minutes, while I can run 6 miles per hour for hours. Ten miles an hour is maximum speed, but it isn't optimum. Systems have an optimum level of performance. It's the output that permits the elements (including the humans) to do their best work, to persist at it, to avoid disasters, bad decisions and burnout. One definition of maximization is: A short-term output level of high stress, where parts degrade but short-term performance is high. Capitalism sometimes seeks competitive maximization instead. Who cares if you burn out, I'll just replace the part... That's not a good way to treat people we care about, or systems that we rely on. As a valuable contributor seeking to build a career,

You might say I have a monitor obsession. I'd not disagree, but I would argue I spend 8 hours a day on my monitor, so having the best monitor I can is worth it. I'd also argue, monitors last forever, so you might as well get them as soon as they meet your needs. Speaking of, I now have a 43" 3840x2160 monitor.  It lows my 34" ultra wide out of the water, and I'm now getting rid of my 27" and 30" monitors.  There's a few things you'll need to know when getting this monitor. 1) T he left and rightmost 1/2" are in shadow when you're close.  This is a weird effect, described here . According to the author of the review it happens on all the current 43" monitors. When you move your head to see the left most edge, you can't see the right edge because it's in shadow, and vice versa.  Most windows have a margin so you won't notice. The place I have noticed it is in terminals (conemu and iterm). 2) Not everything can dr