Hide Table of Contents
I own a domain. There's many like them, but this is mine.
My domain is my best friend. It's my life. I must master it as I must master my life.
Without me, my domain is useless. Without my domain, ...
Ok, you got it! :-)
To test every and any crazy idea that may possibly work.
Work in progress
Messing directly on the VPS, code warrior style, it's definitvely more fun. But while burning the midnigth oil, between a coffee and another after a hard day's work... It can be dangerous. :-)
After thrashing my VPS twice, I decided that fun is not enough and started to eat my own dogfood. :-D
Firing up a Gentoo box from scratch is not for the faint of heart... ;-)
(yes, I'm using Gentoo)
GIT is more famous and more used, but Mercurial gives me some (few but relevant) advantages when tracking moving files around the file system.
And the GIT's advantages (that aren't few neither irrelevants) don't matter on this context.
I ended up using both: GIT for repositories where colaboration is expected (everybody use it!), and Mercurial for my private ones.
I'm paranoid. A LOT. :-)
R/W access to critical sections on this server are done exclusively by SSH, restricted by Security Group to a few seleted IPs.
And Content is considered critical section by me. :-)
Ergo, just checkout from foreign services right into the server's directories are unthinkble.
Continuous integration is nice, but there's no automated tests to check design neither recension :-) so the old and faithful Eyeballs Mark I is still needed during inspections on the development machine.
So, being already on my machine (due development and testing), and being my machine already authorized to access my intranet by SSH, why bothering adding an extra point of failure on my security?
rsync goes, rsync came (and commit from here) and I have a simple deploy mechanism, with transparen mirroring and backup. The server was owned? No stress : fire up another instance from a snapshot and by rsyinc the /etc, /home and /var I'm back to business in no time. :-)
(change management on /etc should be something already integrated on the O.S. I say)
Yep, I'm still using Eclipse. :-D
Every time I give something else a shot, I end up coming back to it. In a hurry. (dude, Android Studio sucks...)
I develop for Android, C/C++ (for Desktop and embedded systems), Enterprise Java, Python (for the Web, but also for embedded scripting). I cut my teeth also on ASM for some microprocessors and microcontrollers, and recently Lua was welcomed to my Portfolio.
It's not feasible to use a IDE for each solution - it's insane (and, again, Android Studio SUCKS).
Since Mars, the Eclipse Foundation acknowledged its failures, and things started to improve. A lot.
So try to evangelize me is fruitless - the day Eclipse dies will be the day I'm coming back to EMACS. :-D
(that I end up using now and then...)
The follwing tools are commonly seen on my desktop: