How can an AI be Jong Zhe?

Sometimes the simplest technology is the most useful one. For me, it's a simple pomodoro application that I've created to show how much work I have been doing and to remind me to take a break from time to time. While it seems to be counter productive to take a 5 minutes of break once in a while, and a longer one after a certain hour, I have found it that I could work until the very last minute more refreshed than if I take long dives into work for hours on end. An important detail that I noticed when I take long dives into work without breaks is that although I tend to get a lot done at those dives, when I come back to work on the very next day, I tend to be less motivated and have more resistant towards doing or continuing on the work. Compare to the days when I follow the pomodoro time where I can ease into work much more easier on the very next day.

A job title is for me is just a rough description of what I could and obligated to do at this very moment. On one hand, I couldn't say that I have mastered all the skills needed to do for that describes for the job title. On the other, for the very least, the required jobs can be done and were done satisfactorily, even if there are always new skills to be acquired along the way. Moreover, having had a number of years of experiences in different type of IT jobs, both in technical and managerial jobs, I have to say that the job title is simply that I could fulfill the required work that the job title describes and it does not reflect all my job skills that I have accumulated over the years, be it technical or managerial. Thus, a job title only defines me at the current work that I am obligated to do and this can be a full stack software developer at the moment but it could be entirely different on the next one. Working as a Full Stack Software Developer My day to day work is supporting a custom Enterprise Software Resource system (ERP) that runs on ASP classic for its legacy system and also ASP .NET. Mostly my job deals with bugs but occasionally deals with improvements with new features that the users might want to use. The system we use is Azure Devops in the form of tickets or cards. From the tickets submitted from users and the software manager, we then start to piece together what is needed, the types of functions need to be created or modified. Since we use a GIT repository system, we fork the application from the main branch and we create a local branch that we can do and test. Once it's done, we push it to our own branch for the manager, who also acts as the tester, to test the work and validate if it's a passing test or a failing test. Once it is approved that we merge the work to the main branch where the software manager then deploys it to production.

For me, I've been fascinated by technologies since I was very young. And as I grew older, I can see how important technologies are in our modern society. I studied Information Systems in the university but it's all concepts and not as tangible as I'd like it to be. Software sits in the center of technology. Except for the simplest technologies, anything electronic will definitely use software. Moreover, software development is all about solving problems and with new technologies that are becoming more and more available, learning new ways of doing things are also fun. And it doesn't hurt to get paid for doing something you already like. so, why not?

Thanks! It's working now. I can now add my hashnode site to my linkedin websites on my profile, and I can also post my blog link on LinkedIn post. Nice!

You're right, Emil Moe. You can never be too careful.

Hi everyone! Glad to be in this community where we're bound together in the similarity that our lives, whether it's our jobs or passion, evolves around technology! Le me introduce myself. My name is Eric O. Jonathan. I am from Indonesia and went to the university in Hawaii, USA at Hawaii Pacific University. My relevant degree to the IT field is my master in Information Systems. Meanwhile, I'm already been back to Indonesia for about 14 years now and been working in various industries and in various IT roles from being a computer support specialist, assistant manager, IT Coordinator, Project Consultant, Lead Software Developer, DevOps leader, and now a Full Stack Developer. I have been interested in how technologies, specifically software, work since I was a kid and an outsider looking inwards to this type of profession in amazement as how software brought to life the technologies that we use everyday! To fast forward to today where I am in the inside looking at the mess that I'm in dealing with developing software, from patching someone else's work (my current day job) to creating a mess of my own (side projects). One thing I learnt in the software development practice, is that there's no perfect code! A perfect code now is obsolete in a few years time at most (unless your code is COBOL, then yours will last for ETERNITY). Meanwhile, for mere mortal like me, I just am contented with the ones I'm dealing with. However, that doesn't mean we should write spaghetti code. My motto is to follow the best practices of the day, and get the job done first. For the rest, I guess I just need to debug them as they come. I'm looking forward to write more blogs and maybe share a story or two. So please check them out when you have a chance! Thanks.

Your name rhymes with your country. Nice! :)

I just had a discussion with a colleague about a JavaScript file that we're both working on. There's this 'that' variable/object that was suddenly being used in the functions without having it being initially declared. Not being well versed in JavaScript I was assuming that must be a built-in Java object that is equivalent to 'this'. But then it takes different function arguments. It didn't seem right. If it was an anonymous function, shouldn't it also be declared as such somewhere in the script? Anyway, we traced the 'that' assignment on a different JavaScript file that was declared earlier before the JavaScript file that we were working on. And even worse, that assignment was declared in one of the functions there, not at the top as global variable! "This is sloppy coding!" I said. Just because the variable that you declared using 'var' can be used beyond the function that you declared at, that doesn't mean you have to use it as global variable! Using 'let' is still much better. It prevents unwanted behavior when treating variables as though they are available everywhere! So, that's my gripe with JavaScript so far. Sloppy coding can happen in any programming language but JavaScript made it too easy to do it.

Thank you! :)