Eclipse, egit and online git repos
I've taken a little to learn how to re-use Eclipse. Pretty much I always switch back to Emacs. This time I setup Eclipse to Emacs bindings, setup for node.js and egit. Hopefully this will help me to stick to using Eclipse. I've also run my first git remote and I've testing adding everything and commit and push. I'm also reading lots of books on unit testing (I do something similar but not exactly and I'm not happy with the results. Something a little more structured and formal might help me deal with the complexity. Also I like the idea of automation. I'm also reading about continuous delivery. Sounds neat but I have a bit more (a lot) to learn before I can get to that level of automation. Luckily the node irrnode project is probably a good choice for experimenting on these technologies.
posted by Neil Cherry @ 11:45 PM
2 comments
2 Comments:
Somehow I missed out on the whole Emacs movement, so I have always used more mainstream IDEs such as Visual Studio and Eclipse. But given they way I code it would be impossible for me to use a simple non language text editor.
Everything I write I try to do with Test Driven Development (TDD). A large part of this methodology relies on the ability to easily refactor code. When a project gets large and has many authors it becomes extremely important to have an IDE that can go beyond syntax highlight and give you context based rename and reference checking. This is even more difficult for an IDE to pull off if you are using dynamic typed languages ( js , python, perl, etc)
In theory TDD should also give people excellent information regarding the codes use. While its helps me dramatically when consuming other peoples APIs, I find it isnt enough when folks dont know TDD and try to program with my code. For example Pytomation's pdf documentation https://github.com/zonyl/pytomation/blob/master/docs/DOCUMENTATION.pdf vs TDD https://github.com/zonyl/pytomation/blob/master/tests/devices/state.py
The TDD code is a lot more helpful to me but not easily to others.
Id be happy to answer any questions you have on CI, CD, UT, or TDD
Thanks, I will ask! :-)
I accidentally fell into emacs. I didn't know I was using it back in 1978 (I've been told it was tmacs then or something like that). Then I went from machine to machine and found uemacs or gmacs. Over the years I had a consistent editor. After 35 years of using those key strokes and macro editor you kind of get to know it. ;-) I think the Emacs+ plugin for Eclipse gives me most of what I need.
I've been kind-of doing some TDD most of my life (I always write tests for my complex functions) but never in an easily re-testable way. I recently read a blog where the blogger did a little ut, built more complex code and had lots of corner cases that made the code impossible to maintain. That's when I determined that I'm doing it all wrong and that I really need to sit down and really relearn everything with a modern IDE that I might find myself using at work (hence Eclipse).
So while I can write code, I want to start take advantage of the modern methodologies and tools to help built more stable and maintainable code (even when it's complex). I'll learn the refactoring stuff last. I tried that on a project I inherited and I must say that it didn't go very well.
BTW, emacs can be considered an IDE, you can code, compile, debug, lather, wash, rinse repeat. It's just that the modern IDE makes managing the project a bit easier. The one thing I really dislike about IDEs is the amount of screen space they consume and the lack of keyboard access to everything (I have to lift my eyes off the code to use the mouse).
Post a Comment
<< Home