- English
- EspañolSorry, this article is only available in Spanish
-
29Apr
Tags: Code, exception handling
-
25Apr
This happened to me some time ago but it can help someone else. At the time I had some troubles sending emails with SMTP and JavaMail. My code was based on the examples provided by chuidiang (The explanation in Spanish here, the Java code here). The code perfectly works with gmail (
smtp.gmail.com), but not with our servers. In fact we couldn’t access the mail Server and got exceptions as:javax.mail.MessagingException: Could not connect to SMTP (smtp_host):(port)I asked to gaussmath and he gave me “a recipe” for testing whether we were seeing the mail server or not. I believe the next tips can be helpful to others.
The basic idea to connect via telnet from our local box or the server where our application will be running to the SMTP host and execute the next tests:
- Step-1->
Telnet (smtp_host) (port) - Step-2->
Helo (domain.com) - Step-3->
mail from: (fromMail@domain.com) - Step-4->
RCPT To:(toMail@domain2.com) - Step-5->
DATA - Step-6->
Test mails - Step-7->
. - Step-8->
quit
Some other issues you should be aware are:
- Are you able to ping the SMTP host?
- Can you connect with Telnet to the SMTP host using port 25?
- Check firewall. Is it enabled/disabled? Is port 25 open?
If you are working with Windows Vista and cannot execute Telnet, the reason is that Telnet is disabled by default. But you can enabled it. You can check the steps here for this.
Tags: enable telnet in Windows Vista, JavaMail, sending emails with Java, SMTP, telnet
- Step-1->
-
25Apr
-
16Apr
Team trust is something we need but something we just don´t build.
Key points to consider to build professional trust (from Esther Derby)
Address Issues Directly
Building trust depends on team members having the courage to speak directly to the person “bugging them”, rather than going through a manager to communicate these concernes. This can be done also through a feedback (or “feelbad” as a friend says
)Share Relevant Information
Speak your mind. If you don´t agree, say it! Don´t wait until the disuccion has over and then came back saying you disagree. Also consider doing it in a constructive way.
Follow Through on Commitments or Give Early Notice When You Can’t.
Just do your best to be honest with your progress and be proactive when things are not going as planned for you. This is related to point #4.
Say No When You Mean No.
I guess in my case, I almost say always yes to everything related to work and then I have to say No because I just can´t with all the tasks assigned to me.
So, you don´t have to say “yes” to every request in order to look like a “team player”. Saying Yes to everything can lead others to doubt your word. If you can´t say No, your Yes won´t mean anything.
Admit you don´t have all the answers.
Show What You Know and What You Don´t Know
Share the information you have, the things you know, but also be aware and open about the things that you don´t know.
Tags: agile
-
13Apr
What I did and what I didn’t like about certifications. First of all, what are these things? Well it is a way to show “the world” (specially “recruiters” part of the world) that you are proved in certain area. My story about certifications it is not long but also not that short, currently I held 3 of them and more are in process.
In order to get the certifications; I studied by my own for some of them and I attended to lessons for some others. What was the difference? Well! I took some lessons because I didn’t feel with enough knowledge to get the certification and even more I expected to learn something else from my classmates (and I did!).
For example, SCJP, obtaining this one it was not an easy deal. I studied by myself during a month trying to understand the nuts and bolts of the Java language, it best reward was to practically became some sort of Java pre-compiler. That for sure helps a lot when coding
Obtaining the CAPM was a totally different story! By that time I have some experience with “software project” terms but I was not an expert at all. So I decided to enroll for some lessons (well! It is also a requirement but I have done this even if it were not a requirement); the course last for 3 months and all I can say “It was awesome!”. I learned a lot from my classmates who have much more experience than me managing projects for all kind of companies bank, insurance, software and government.
So what I like about the certifications? The process! You have to pass some days figuring out things, reading, learning and even meeting people (that in the future can become a job contact and/or a very good friend).
What I didn’t like? Specially this happened with CAPM, I was disappointed when answering the exam I realize that almost everyone who had previously memorized the material (PMBOK) would be able to pass the exam. I not saying that certification doesn’t worth it, I am just saying that I expected that exam show more challenges than just memorize.
If you want some good reading material for Java certifications, you can check Javaranch also you can look for head first series books. For PMI certifications almost all you need it is in ther site (There is a Head First Book, but I haven’t read it).
I will talk about my experience about certifications and job market, later…
See you,
Buho
– Hi guys this is an example in two languages
Recent Comments