Hey Hey, I’m Hilman Ahmad. from the TornadoByte. I haven’t written on Medium in a long time. So yeah, I will write some financial articles related to our new project releases, called DSRCalculator.

Introduction

A debt service ratio (DSR) evaluates a person’s capacity to handle their debt commitments. A lower DSR signifies a healthier financial state because it suggests that less of the income is going towards debt-related obligations, leaving more money for other uses. On the other hand, a high DSR may indicate a higher likelihood of financial distress and difficulties making debt payments. DSR is a crucial tool for budgeting and decision-making because lenders frequently use it to assess a borrower’s creditworthiness and eligibility for a loan. DSR is not only a measure of financial health but also a critical tool for making sound financial decisions. It underscores the importance of managing debt effectively as a fundamental aspect of personal finance, leading to greater financial security and opportunities for achieving one’s financial goals.

Our Motivation

I’ve been wanting to apply for a loan to buy a property for the past two years. I’ve designated one of the agents, and I’ll be meeting them there. According to the agent, a minimum DSR of 60% is needed to pass a loan application in order to submit one. In order to calculate the DSR for loan eligibility, they sent me a WhatsApp after our meeting asking me to respond to a few of my commitments, including how much my salary is and liabilities like housing loans, car loans, education loans, and so on. I noticed that this is extremely manual, so I wondered: What if the user provided access to tools that would allow them to enter data and calculate the outcomes of their calculations?

Ideas of DSRCalculator

TornadoByte has decided to develop DSRCalculator, one of its financial tools for calculating the DSR. This application allows users to enter some of the necessary information, such as their income and commitments, in order to determine their DSR percentage within the acceptable range. With the interactive user interface, users can also experiment with the range and their remaining debt after submitting the loans.

This application was completed in one month by using the Next.js framework and Material UI as a library. As this DSRCalculator was being developed, we appointed a number of bankers and agents friends to gather real-time feedback and opinions. As a disclaimer, DSR eligibility for loan application success varies depending on the position, occupation, wage, age, and many other factors for individual applicants. As a result, this DSRCalculator is only intended to provide general information; for more precise financial eligibility, see your banker or agent.

See you.

DSRCalculator: Understanding Debt Service Ratio (DSR) in Personal Finance 💰 was originally published in TornadoByte on Medium, where people are continuing the conversation by highlighting and responding to this story.

Hey again, I’m Aan H. from the TornadoByte gang. I feel like writing today, so yeah. Are you team red? Or are you blue?

🔴Red vs. 🔵Blue

Think of the ‘Red Ocean Strategy’ as the original way companies do business. Imagine a gang of sharks hunting for dolphins. The tougher, slicker, the more skillful the shark, the better the outcomes will be. In this red hot zone, it’s a no-holds-barred showdown, with every company clawing for the same customers, often resorting to price wars and copycat tactics. Result? Skinny profit slices and major beef among rivals.

And then there’s the ‘Blue Ocean Strategy’, and this one’s like creating a whole new original business idea. Imagine being the only shark in the sea and you have all the dolphins there are to feast on. No competition in sight! You create a new business, you create a new pool of customers, and you reap all the money.

It’s Hard to Be Original

It’ll be very difficult to come up with a truly original idea, as many ideas are built upon previous ideas and concepts. When so many people trying so hard to be unique, meh… why do we even bother?

I enjoy eating beef. I’m a meat eater 🥩 pfft. Originality and uniqueness? Those concepts are so goody-two-shoes mainstream. Developing an original idea takes time, and it doesn’t guarantee success either. And what’s so wrong about playing the copycat game? After all, imitation is a strategy* that’s known to have made its way to success. Not every original idea is good; some of them are terrible. And their terribleness presents an opportunity for other hungry sharks. My spirit animal is the tiger shark. So, I can say that I am all Team Red🔴.

Another Poorly Designed Product is Another Opportunity.

As an opportunistic designer, when you encounter a good idea that is consistently and poorly implemented, what should you do? Hehe. When you know you are capable of improving it, why not? And if you have a group of friends and sufficient capital needed to create a better version of that idea, consider Steal it Like an Artist.

Disclaimer: it’s important to approach situations ethically and within the bounds of intellectual property and legal considerations when considering implementing an idea inspired by someone else’s work. But, know the boundaries, guys.

Time to S̶t̶e̶a̶l̶ Shine

Here are some takeaways I like from ‘Steal Like an Artist’ that really vibe with me. However, I focused on the idea of stealing ideas rather than copying someone’s design style. Haha!

1. Nothing is Original: Kleon argues that all creative work builds on what came before it. There’s no such thing as pure originality, and artists should embrace the idea of borrowing, remixing, and adapting existing ideas.
2. Side Projects and Hobbies: Sometimes, your most creative and innovative work comes from side projects and hobbies. These activities can free you from the pressure of your main work and lead to unexpected breakthroughs.
3. Share Your Work: Don’t keep your creative projects hidden away. Share them with others, whether through social media, a blog, or other platforms. Sharing your work can lead to valuable feedback and connections with like-minded individuals.
4. Be Patient and Persistent: Creative success often takes time. Be patient, and keep working on your craft consistently. Don’t be discouraged by failures or setbacks.
5. Stay Curious: Cultivate a sense of curiosity and keep exploring new ideas, concepts, and interests. Being open to new experiences can lead to fresh inspiration.

Not related to the above writing, but recently I moved to Ampang, a town nearer to the city center — Kuala Lumpur. So I might share with you guys my new work setup.

I think that’s all. Bye for now.

Slaying the Red Ocean Strategy: Power of Design was originally published in TornadoByte on Medium, where people are continuing the conversation by highlighting and responding to this story.

So what is Black Box Testing? In black box testing, imagine the software as a mysterious black box. Testers focus solely on its inputs and outputs without any knowledge of the internal workings. It simulates the perspective of an end user. Here some key points you need to know:

• The purpose of black box testing is for to evaluate the software’s functionality and ensure it meets specified requirements.
• For the test design, tester create test cases based on functional specifications, user stories, or other external documents that outline the expected behavior

So what are the advantages for black box testing? Wait… Here it is:

• Simulates real-world user scenarios.
• Testers do not require in-depth knowledge of the software’s internal architecture.
• Encourages thorough testing of all possible user interactions.
• Identifies discrepancies between expected and actual behavior.

Still with me? 😎Lets go to the white box testing!

So what is white box testing anyway? In contrast to black box testing, white box testing allows testers to look inside the “white box” and examine the internal structure, design, and implementation of the software. Here’s what you need to know:

• The purpose of white box testing is to assess the software’s internal logic, uncover potential coding errors, and ensure the software functions correctly
• For the test design, testers create test cases based on the software’s internal structure, such as code paths, branches, and specific conditions. This requires knowledge of programming languages and code analysis.

White box testing also got the advantages of it. Lets break into key points:

• Provides deep insight into the software’s internal behavior.
• Enables targeted testing of specific code segments and critical areas.
• Helps identify bugs, bottlenecks, and performance issues.
• Supports early detection of coding flaws and security vulnerabilities

Yeayy! We have come to the comparison part. So you guys want to know what it is? Lets go…..

• Knowledge Requirement: Black box testing requires minimal knowledge, while white box testing necessitates programming skills and understanding of code structures.
• Testing Focus: Black box testing prioritizes user perspectives and expected outcomes, while white box testing concentrates on internal workings and uncovering coding issues.
• Coverage: Black box testing covers functional aspects and overall system behavior, while white box testing focuses on specific code segments and internal structures.

So thats it! Congratulations you have finish reading this interactive blog 🤣I hope you now have a better understanding of these testing techniques, their purposes, and how they complement each other in software development. Remember, both approaches are valuable and should be utilized based on the specific needs and requirements of your projects. Happy testing!

See you guys with the next post ya! 🏎️

Demystifying Black Box Testing vs White Box Testing: A Journey into Software Testing ✈️ was originally published in TornadoByte on Medium, where people are continuing the conversation by highlighting and responding to this story.

Hey there, fellow TBytians! I am Aan H, the Design VP for TornadoByte, and~ (//drumrolls playing in the bg) this is my first blog post ever.

I won’t deny the fact that I use AI services a lot to simplify my daily task. They’re time optimizing and help me accomplish my task efficiently. AI language models like ChatGPT and Bard are totally slaying the game 🔥 nowadays, changing the way we interact with computers. So, let’s dive into this epic face-off between ChatGPT and Bard to see who’s got the skills and the feels! 😎💬📝

ChatGPT

ChatGPT, powered by OpenAI’s GPT-3.5, is the ultimate chatbot 🤖 that knows it all! Seriously (maybe I’m biased toward this one, hehe), it can answer questions, help me generate UX copywriting, give you suggestions, and even have super realistic convos with you. It’s like having a BFF who understands your gibberish prompt but still works! 🤯

Bard

Now, Bard is a genius (because it is from Google, duh)! 🎵📝 Bard is still under development, but it has learned to perform many kinds of tasks. With Bard, I can save time with my UX research and help me collect the latest, more correct user data available. Personally, I think Bard needed more training in terms of prompt processing. IYKWIM heheh

Use Cases

ChatGPT is the go-to for customer support, virtual assistants, and getting info on anything and everything. It’s like having a personal assistant who’s always got your back! 🙌💼💬 On the other hand, Bard is perfect for unleashing your inner poet, getting that writer’s block busted, and creating captivating content. It’s pure artistic magic! 🖌️✨📚

Limitations

Okay, so let’s keep it real. ChatGPT can sometimes give wacky answers, outdated data, or struggle with tricky topics. It’s like that friend who occasionally misses the memo but is still pretty awesome! 😅💬❌ Bard, while great at analytical data and numbers, might produce some mind-boggling lines that don’t quite make sense. It’s the quirks that make it unique, you know? 🤪🎶❓

Conclusion

In this epic battle of ChatGPT vs Bard, both AI language models bring their A-game. ChatGPT rules the chat scene, while Bard unleashes the creative vibes. So whether you need a conversational buddy or a poetic muse, these models are the bomb! 🔥💬🎵 They’re pushing boundaries and opening up a whole new world of AI-generated awesomeness. Let’s embrace the future and ride this wave together! 🌊🤖💥

Okay, till next time. XOXO

ChatGPT vs Bard: Battle of the AI-Language Models! 💥🤖 was originally published in TornadoByte on Medium, where people are continuing the conversation by highlighting and responding to this story.

After completing my bachelor’s degree in physics, I felt lost and uncertain about my future. In an attempt to find my calling, I made another series of misguided decisions and ended up pursuing a Master’s degree in electrical engineering. Feeling confused and unsure about my next move, I unexpectedly reunited with old friends from our school days. Little did I know that this chance meeting would set in motion a series of events that would change my life. It became a remarkable journey of self-discovery and transformation that I never could have anticipated.

Hidden ‘blessing’ decision

When I reconnected with my friends, one of whom happened to be an experienced software engineer, they generously shared valuable advice on potential career paths I could explore. Surprisingly, my decision to pursue a Master’s degree in Electrical Engineering, which I initially considered a mistake, turned out to be a hidden blessing. It led me to discover the world of coding. Motivated by this newfound interest, I embarked on a self-taught journey, starting with HTML, CSS, and JavaScript. As I dived deeper into web development, I learned about the Angular framework to recreate the web application of the Golden Screen Cinema (GSC) ticketing system.

Rejection

After wrapping up the experimental phase of my Master’s degree, I returned to my hometown, fully dedicated to writing my Master’s thesis. At the same time, I eagerly sought out software engineering job prospects, only to encounter disheartening setbacks in the form of repeated rejections due to my lack of a computer science background. Undeterred, I embarked on a new path within the oil and gas industry by day while devoting my nights to relentless learning and coding. To bolster my chances, I tirelessly worked on various mock projects to build a robust portfolio.

COVID-19

In early 2020, the COVID-19 pandemic brought about major disruptions in my life. Due to the circumstances, my factory had no choice but to implement unpaid leave for 80% of its staff, including myself. With newfound free time during the day and night, I embraced the opportunity to fully immerse myself in coding practise. I devoted up to 16 hours each day to learning and honing my skills while building an impressive portfolio through various mock projects. The transition to online interviews made the job application process more accessible, and after persevering through numerous interviews, I was ecstatic to receive a job offer from a telecommunications company. This moment marked a significant milestone in my personal and professional journey, filling me with genuine happiness and a profound sense of excitement for the future.

Message

The IT industry is currently experiencing high demand, and many individuals are eager to transition into this field but often lack a clear path forward. To address this, I recommend visiting the website https://roadmap.sh/, where you can explore different career plans. Personally, I suggest starting with front-end development as it offers a tangible visual output, unlike back-end development, where you primarily work on code, APIs, and data handling without immediate website visualisation. Once you’ve chosen a skill, such as front-end development, you can further specialise by selecting a framework like Angular, React, or Vue. From there, it’s crucial to focus on one stack and put in the hard work to master it.

When it comes to learning, there are numerous free resources available. Platforms like Udemy, Coursera, and YouTube offer a wide range of educational materials. However, it’s essential to maintain focus and concentrate on learning one thing at a time. Rather than trying to absorb multiple subjects simultaneously, prioritise one specific area of interest and dedicate your efforts to mastering it. This focused approach will allow for deeper understanding and better retention of the subject matter.

Good luck in your career! 🚀

Career Change: How I become a Software Engineer without a CS Degree 📈 was originally published in TornadoByte on Medium, where people are continuing the conversation by highlighting and responding to this story.

Hello there 🙋🏻‍♂️, I am Hilman Ahmad, the Software Engineer at TornadoByte, and today I will talk about GraphQL, which is seriously 😡 I will explain a super simple explanation even kids can understand.

GraphQL is a query language or API (application programming interface) that was created by Facebook in 2012 and was later publicly released in 2015. It’s all about making life easier for web and app developers.

You see, when these developers want to get some specific information from a server, they usually have to send a request and then get back a big chunk of data, even if they only need a tiny piece of it. It’s like getting a whole pizza when all you want is a single slice! That is traditional REST API (representational state transfer).

But GraphQL changes the game. It lets the developers be super specific about what they want. They can ask for exactly the data they need, like toppings for their pizza. No extra stuff, just what they crave. This means they get a lightning-fast response with only the data they actually want, saving time and making their apps run smoother.

But that’s not all! GraphQL is like a ninja that can gather data from different sources and put it all together. It’s like having a magician who can bring together information from different APIs into one awesome response. It’s like mixing up the best ingredients to create the perfect dish!

So, in a nutshell, GraphQL is a superpower for developers. It’s a language that helps them get exactly what they need, ditching the excess baggage and making their apps shine. It’s like having a personal chef who serves up only the tastiest data, leaving the developers and their users happy and satisfied.

Okay, now we’ll talk about something more technical 🛠️. In the REST API, clients make HTTP requests (GET, POST, PUT, and DELETE) to specific endpoints (URLs) on the server, and the server responds with the requested data. REST APIs typically expose a fixed set of endpoints, each representing a specific resource or collection of resources. The server determines the structure and content of the response data. In this case, the clients cannot control the response data, which may lead to under-fetching and over-fetching of data.

On the other hand, with GraphQL, clients have more control over the response structure as they can specify the exact fields they need, reducing unnecessary data transfer. Let’s say they have a requirement to show a table of users viewed by name, age, email, username, etc. On the top of the page, there is also a requirement for a dropdown that shows a user list view by name only. By using GraphQL, developers do not need to create multiple APIs; they are able to request data from clients based on variables that they want to have in response. Cools right? 🤓

Conclusion

The REST API is a more traditional approach with predefined endpoints and fixed response structures, while GraphQL provides more flexibility and efficiency by allowing clients to request specific data structures with a single query. The choice between GraphQL and REST depends on the specific requirements of the project and the trade-offs desired in terms of flexibility, network efficiency, and developer experience.

See you again next time 👋🏻.

GraphQL: A Simple Explanation Even Kids Can Understand 🤯 was originally published in TornadoByte on Medium, where people are continuing the conversation by highlighting and responding to this story.