Hello readers of 2coffee.dev. Another week has passed, so quickly that when looking back at the homepage, I couldn't believe that I had stopped writing for such a long time. To be honest, last week was quite busy as I was focused on releasing an important update for the product at work. Perhaps that's why the concept of time has temporarily been buried. Hmm... Need to think of something to talk about...
π 1 year ago
When was the last time you wrote documentation for a system or a function? Did you use any images or diagrams to describe how it works? I'm talking about those activity diagrams, sequence diagrams... to model the workflow of the program. Standardizing the workflow with diagrams has played a significant role in conveying meaning. Because if everyone knows and understands, then...
π 1 year ago
Writing about certain topics can be quite challenging. Not because they are difficult, but because it's hard to present them in a structured and easy-to-understand way. Since I learned about the saying "You only truly understand a topic if you can explain it to others," I've been following this principle as a commandment in my mission to convey content through writing. In my list of drafts, I've missed out on many topics just because I couldn't achieve this goal. But it's okay, I'm sure that gradually, I'll "truly understand the topic" eventually.
π 1 year ago
As a programmer, I believe that everyone has thought about leveraging lines of code to automate tasks. For example, a JavaScript code snippet written by a programmer to calculate the total amount of money spent on an e-commerce platform, instead of manually adding up each order in a never-ending list. Automation brings many benefits, the most obvious of which are time savings and reduced errors in repetitive processes. Moreover, if the code snippet I wrote can be shared with others, it's truly a win-win situation. I also create such code snippets, but instead of calculating order values, they focus on solving common work-related issues. For instance...
π 2 years ago
During my studies, I learned about the Waterfall software development model in the subject "Analysis and Design of Information Systems". The name of this model made me think of a powerful waterfall, with water cascading down from top to bottom in one direction only, implying a sequential process that is not easily reversible. But in reality, during my professional career, I haven't...
π 2 years ago
What I believe many programmers aspire to is writing code that is easy to read and understand. There is plenty of evidence, such as the numerous Design Patterns that have been introduced to guide people in solving problems the way many still do. However, that's not all there is to it. Writing comprehensive code depends on each individual programmer. We have various tools to aid in source code editing in many ways, such as formatting, colors, display interfaces, debugging support, allowing us to choose according to our preferences or collaborate with teams. In addition, there are still rules in place for team members to adhere to.
π 2 years ago
Hello readers of 2coffee.dev, today let's take some time to have a conversation. The topic of today's article is "Should You Fix Other People's Bugs?" Well, this question might seem simple. Of course, when you work for the same company, on the same team, and the same product, everyone collaborates and fixes bugs together, right? Why even ask this question? That might be the thought of many when it comes to fixing other people's bugs. But I believe that, aside from that, there are still people, including myself...
π 2 years ago
The last time I went for a job interview was about 4-5 months ago. Like many others, I went to various places, each with its own interesting experience, and I realized that no two interviews were the same. I prepared myself to be comfortable and set criteria for a new work environment, not focusing too much on theory but rather answering based on my practical work experience. One day, a CTO asked me a question: "What level do you think you are at?" Without hesitation, I answered...
π 2 years ago
Modern programming is somewhat different from the past; we have more choices in terms of technology and programming tools. Part of this is due to the growing community, which creates powerful tools to solve problems, ultimately reducing development time and optimizing repetitive work. Nowadays, when facing a problem, the first thing I often do is search on Google to see if there's a tool that can solve it for me. Sometimes, even when I know how to solve it, I still search to see if there's a better way. In recent years, JavaScript has been rapidly evolving...
π 2 years ago
In your opinion, what factors make a piece of code good? Concise code, easy to understand, thorough comments, standard syntax, adherence to code style, readability, easy maintenance... There are countless criteria for defining "good" code, and ironically, achieving all of them at once is a challenging, if not impossible, task. For instance, you can shorten the code to make it look neater, but it might complicate future maintenance because concise syntax often sacrifices code transparency. You can provide detailed comments, but it may confuse readers, as excessive comments can clutter information...
π 3 years ago
