This is intended as a bare-bones intro to saving for retirement, targeted at software engineers. Ballpark, you make about $100k a year in your 20s. If you want to have that same income in retirement, you need about four million dollars saved up.
MySQL is designed for lightweight connection creation. Therefore, you may not use connection pooling. However, if you are a connection pooling fan (Java and Ruby devs, please raise your hands), don't forget to configure the MySQL for that:
We Agile practitioners are probably less thrilled by these New Year’s traditions. We have been desensitized by countless iterations kicking off with commitments and coming to a close with retrospectives. Our cynicism toward a Waterfall approach most likely makes most of us jaded about these end-of-the-year festivities. Or maybe not?
I was recently asked for advice on how to go from two week sprints to one. The conversation was one I've had several times. Client: "We are a scrum shop that has two week sprints. We'd like to release faster. Any suggestions?"
I’m currently having a lot of fun experimenting with node.js using IntelliJ IDEA. I installed the node.js plugin, and although this added options to create a new ‘Boilerplate’ or ‘Express’ project, the rest of the node.js integration wasn’t quite so obvious…
Managing energy is more important than managing time. Energy is what gets things done, and time is only a crude surrogate for energy. Instead of only looking at what you could earn per hour versus what you could hire someone else for per hour, consider the energy it would take you to do something versus the energy it would free to delegate it.
Software is more about people than technology. When I graduated from college, I thought I only had to master technical skills to be a great developer, thinking that people skills are the appanage of managers solely.
Writing automated tests for your code is one of those things that, once you have gotten into it, you never want to see code without tests ever again. Why write pages and pages of documentation about how something should work when you can write tests to show exactly how something does work?
So, we found out that the major cost of random writes in our tests was actually writing to disk. Writing 500K sequential items resulted in about 300 MB being written. Writing 500K random items resulted in over 2.3 GB being written. So the obvious thing to do would be to use compression
We say it's only a matter of time before quality of life, and life itself, critically depend on software systems. Yet our methods for producing them sometimes resemble wizardry and superstition: in some fields of the software industry, everyone is a Vannoni.
Traditional capacity planning, where new servers were purchased to fulfill the demand of a single application with a load of 20% max, is terminated by cloud computing. The comparison below shows some of the basic differences between the traditional DC and the cloud: