Every week, we feature a new developer/blogger from the DZone community here and in our newsletter, catching up to find out what they're working on now and what's coming next. This week we're talking to Zemian Deng, Senior Application Engineer working at Oracle for the Enterprise Knowledge Management product. Some of his most recent DZone posts include:
- How to Export and Import MySQL Databases
- Using crontab to Startup Service
- A Simple Cron Wrapper Script With Logging
1. What have you been working on lately?
I just joined Oracle few months back in Feb, and I am excited to work on their Oracle Knowledge Management System and getting ready for the cloud service.
2. You've written a lot about WebLogic Server. Are there any particularly interesting features or uses that you don't feel get enough attention?
Not really. I just happen to work on it quite a bit lately, so I shared a few notes in my blog. They are general stuff anyway, but for those who are new to WLS, it might be helpful.
3. Are there any particular developer tools or resources you couldn't live without?
4. Do you have a favorite open source project (or projects) that you've contributed to recently?
I am using Weld, Jersey and EclipseLink quite often in my current project. I think they are very good projects, and best of all they fit/come with your standard Java EE stack!
5. Do you follow any blogs or Twitter feeds that you would recommend to developers?
6. Did you have a coding first love -- a particular program, gadget, game, or language that set you on the path to life as a developer?
Okay fine, I admit I do use something else besides Java from time to time, for example Python. It reminds me the "simple is better" rule. I like a language that has a built-in "poetic" philosophy, don't you? :)
The Zen of Python, by Tim Peters
Beautiful is better than ugly.
Explicit is better than implicit.
Simple is better than complex.
Complex is better than complicated.
Flat is better than nested.
Sparse is better than dense.
Special cases aren't special enough to break the rules.
Although practicality beats purity.
Errors should never pass silently.
Unless explicitly silenced.
In the face of ambiguity, refuse the temptation to guess.
There should be one-- and preferably only one --obvious way to do it.
Although that way may not be obvious at first unless you're Dutch.
Now is better than never. Although never is often better than *right* now.
If the implementation is hard to explain, it's a bad idea.
If the implementation is easy to explain, it may be a good idea.
Namespaces are one honking great idea -- let's do more of those!
7. Is there anything else you'd like to mention?