This is indeed so true; yet money doesn't buy time. Unless you are in your dream location there's always inherent costs to visiting relatives / friends, match their schedule, or simply go wherever you feel good. So you end-up with a double need for money ;)
In some degree, it does. If you have more money than you need, you can opt to work less hours (not everyone can, but in Germany for example most people have that option).
OP here, the post is only a simple trick that may be of some use to some people.
Eventually we merged that logic in an in-house app we built back in the days when the containers orchestration tools were still "rare", if i recall https://github.com/toscanini/maestro had just launched but wasn't really usable yet...
The idea it that if I have a few containers that need to know each others. Say an application server `app` and a PostgreSQL database `db`. While conceptually I need to spawn only `app` and `db`, I have a script to actually spawn `ns` (i.e. dnsmasq), `app`, and `db`. That script will register the IPs of `app` and `db` into dnsmasq (as you describe in the post).
This means that I can run that script more than once on my laptop and have multiple triple (`app`, `db`,` ns`) side by side without fear of crosstalking between logical groups.
I'm perfectly fine with the DNS/DHCP approach, just wondering what are the alternatives out there. That dnsmasq approach worked like a charm for several of our projects for 1+ year.
Always wondering of the extra round-trip on DNS request when we could have a hardcoded value in the host. We're talking local network so the latency ain't much of an issue but still. Then there is the possibility of a dnsmasq restart when a request occur, caching ala nscd could work, but then we're in for a lot more trouble when it comes to expire that cache !
I'd love to hear about other people's workflow when it comes to address that issue - are you simply re-provisoning the all shebang if a critical component is to be updated or change? or relying on etcd/zookeeper as mentioned? or ...
We use consul. Each instance has it's own bind setup with DNS forwarding and it forwards normal traffic on through the regular DNS servers and anything in .consul on to the consul client running locally.
13.04 is vulnerable, just out of the support period of ubuntu (decreased from 18 months down to 6 months in 2013) - basically out of luck, either use a ppa, or upgrade to 13.10
Really? I'm so surprised to see so many "Awesome! Go for it" answers to this.
While I admire the dedication and focus it takes to stay up to such routine, I am certainly concerned by the quality of life and the narrow mindedness of enforcing upon oneself to code on a daily basis. What about days off? Going out friends / family for a weekend or holidays? One would suggest to bring your laptop so you can stick to it? This is madness to me...
I love to code, contribute to OS projects, do code for a leaving and for myself - but for nothing in the world I'd even attempt such thing.
Setting yourself with goals is great and required to some extend but on a proper schedule. Going to the gym 3 times a week can be achieved without being complexed by the fact you didn't go there every single day - and yet you can substantially improve yourself. I don't envy those buffy dudes that stick to it.
I'll stick to enjoying evenings with my wife, do code maybe 1 or 2 times during the week days, spend an extra day on more complex issues on the week end, and rest for the last day. Just saying.
Mhh, read the article a bit more carefully. Specifically:
Minimum viable code. I was forced to write code for no less than 30 minutes a day.
30 minutes a day? That's not exactly a huge quality of life problem or a work addiction. That's keeping a useful skill up to par, the same way I'd expect a good musician to practice every day.
Besides, when you're a serial procrastinator, tactics like these can help you break out of that rut.
