Advocating a Positive Society Through Technology and Good Will
I studied BS Nursing at Cebu's University of San Carlos. Passionate about helping others, I proceeded to work in the largest industry in the area. Today, I lead a fairly sizable team of fraud analysts. My main interests revolve around leadership, growth in others, a helpful society, and as a hobby, web development. I hope one day to create a bigger impact through technology.
Nothing here yet.
No blogs yet.
Truth behind these words! Exactly why the HR hiring process matters A LOT, if they're going to be in your team, you should be able to check how they are professionally. It makes working with them so much easier. Professionalism is a must. Will trumps skill in my books. Then again, these "professionals" are uncommon, and one might be forced to hire the next best candidate.
How To Deal with Someone Who Thinks They Know It All But Really Doesn't in 3 Easy Steps I lead a team of 12 analysts at work, they get a lot of things wrong a lot of times. I've come up with a formula when dealing with mistakes and it's fairly simple: all you have to do is to ask the right questions, you don't have to tell them anything . That's right, you can make them realize their own mistakes and have them come up with their solution (otherwise, it would be you doing their job instead). I'll tailor fit the answer to someone who "thinks they are right." What you need to prepare: Company/Department vision or goal Model design(s) His design Respect The Conversation in 3 Easy Steps: 1. Create a good atmosphere Ask him how he is. If you work with him, you would know a bit about what they are up to. Ask him about his quest to become a better designer, this will help you transition to a discussion on his project 2. Ask him how he feels about his project 2.a Pull up his design. Start the discussion with the Good Parts " Speaking of design.. I wanted to get your opinion on your project " Let him start with the good parts, and agree with him on the good parts that you actually think are good as lying won't help. If he says "everything is good" let him elaborate what makes it good. Having him write these down will be very helpful. Remember: If at some point you don't agree with what he says, do not say he is wrong, it'll only make him defensive. Say 'okay' and just tell him to write those down. Later you can compare what he thinks is good and what good really means for your project (2.b.i). 2.b. Ask him about what he thinks needs improvement Ask him what about things he thinks he can improve on. Having him write these down too will be very helpful. Remember: Have him say these, avoid the urge to enumerate what needs to be done properly. If you're lucky, he'll hit some of your items you wanted him to know about. If you're really lucky, he'll hit all and add some more to your list. If you're even luckier than that, he'll hit all of the stuff on your list and IMMEDIATELY state how he can improve on it and you're conversation ends here. Pat him on the back and your back as well because you've hired an excellent employee. If you're unlucky, like the most of us proceed to section 2.b.i 2.b.i He REALLY Thinks he's Right Here's where your Company's vision/goal becomes useful. If somewhere there states for example: "Making UI's Simple and Elegant" but his work is the complete opposite, then you can go back to 2.b. and ask him " How can we make this design more simple and Elegant? " A model design also helps, show him a design that fits the company/department/project's vision. Ask him what makes the model design look/feel great , have him list these down. Make him do a comparison, his notes should tell him everything. He might have listed down "I have 15 useful buttons on my navbar" as part of things he did good, but finds that it is contrary to a "Simple" UI design. Then you can go back to 2.b. and ask him " How can we make this design look/feel great? " 2.c. Now he's acknowledged his work isn't perfect and might have provided his own suggestion (some might even be really good this time), but now is time to provide your inputs too Avoid telling him what to do, suggest instead with phrases like: " I've an idea. What do you think if we did this, that, etc? " " You know, we had a project like this one once, and what worked well was when we placed this and that over here and there. What do you think? " 3. Let him know you're on his side and you're there to help him Because you are. If he does a crappy job, your doing a crappy job too. In fact, I encourage you to see this in another perspective, one that is trying to help him. Because if you're genuinely trying to help him, it'll show and chances are he'll be more receptive. The day will end with you doing the world what we all need, a bit of kindness.
Unlike all of the answers here, I am neither a professional programmer nor an efficient one as well (I work for a bank and I just started learning web dev/programming a few weeks ago - I hope I'm still welcome! :] ). I'd like to believe, however, that I have some developer skills and am keen on improving those. My humble developer skills include HTML, CSS, and some JavaScript. I learned most of these through books and an online course on Coursera to give me some sort of "dialogue level" explanation of things. I train myself by: Doing most, if not all, of the exercises in the books I read and the videos I watch before proceeding to the next chapter. Planning, designing, coding, and sometimes improving a website once a week and applying things I learned throughout the week and those in the past in these weekly websites. And more recently, reading web development stuff here on Hashnode. I love the feeling when I write something and discover the next week that there are easier ways of doing things. Just last week I built a portfolio that had each of my skills and my proficiency level of those (most were 1 out of 5 stars) on cards spread out over my page all in HTML -it wasn't that long but- it was looooong. Then I discovered the Angular's repeat, controller, app systems and found that I could do this in a much cleaner more readable way. The feeling is almost like the first time you played pokemon and discovering new things and places for the first time. Also, I still can't get my head over Github. I understand how it works I.. I I just don't know, I can't explain it. I try to place my projects on there but I just mess everything up. Someday.
I was never very good at math but I've read in several places that you really only use basic math in coding anyway. Math is the reason I didn't minor in Computer Science like I wanted to over 10 years ago when I was in college. The feels. :( I wished I studied CS too but the idea of maths put me off.