Forem: Rust

Telegram Got This Simple UI Pattern Wrong

Rust — Tue, 31 Mar 2026 11:33:00 +0000

Do you know the difference between radio buttons and checkboxes?

I recently ran into a few misunderstandings while using polls in Telegram with multiple selections enabled. The poll shows radio buttons even though users can select multiple options.

By default:

Radio buttons signal single choice
Checkboxes signal multiple choices

So when users see radio buttons, they think they can pick only one option. And that’s exactly leading to unexpected results if you create a multiple selection pool.

Users trust visual patterns more than instructions. When UI elements don’t match their expected behavior, misunderstandings are inevitable.

Clarity and consistency in UI are not optional — they directly affect how people think and act.

UI #Frontend #Telegram

Jira Board for Everyday Life

Rust — Mon, 23 Mar 2026 11:15:00 +0000

Do you use a task manager in your everyday life?

I’ve been using a task manager since school. It started with a simple to-do list in my notebook. Later, when smartphones became common, I created my first digital to-do list on my phone.

Today, there are many tools to manage your tasks:

Notion
Obsidian
ClickUp

…and many others.

I used Notion for a long time. It’s a really good tool, but I found it difficult to manage routine weekly tasks. At the beginning of every week, I had to manually recreate my routine tasks. Later, I created a template, but I still had to manually manage tasks that were not part of my weekly routine.

One day, I talked with my project manager at work, and she shared an interesting idea: why not implement Jira in real life? I thought about it for a couple of weeks and discussed it with my friends. It was amazing to realize that I’m not alone. Many IT professionals think about using Jira in everyday life because it’s clear, standardized, and a familiar tool.

A couple of months ago, I started implementing my life in Jira. I created Epics. In my system, Epics represent yearly goals, for example: read 12 books per year, launch one of my projects, save X amount of money, and so on. Epics combine monthly, weekly, and daily tasks under them.

I also created labels to separate different areas of my life: family and friends, career, health and self-care, learning, sport and challenge.

But what excited me the most was the automation part. Finally, I was able to set up my daily, weekly, monthly, and even yearly habits as routine tasks. I was really happy about that because now I don’t have to think about recreating them anymore. However, it’s worth noting that the free plan has a limit of 100 automation runs per month.

I also customized my board statuses: Current Week, Daily Results (usually tasks where I can see the result at the end of the day), Today, In Progress, and Done.

Another great feature is that I can share tasks with others (for example, my family members) and try to be more productive together.

Jira has five priority levels, which felt like too many for me at first, so I started with three. Later, I expanded them to four levels.

Overall, Jira is a great tool if you love systems and metrics. However, it can feel a bit heavy for everyday life planning. I believe it works best for engineers or people with a structured, analytical mindset.

But I’m really curious about your experience:

Do you prefer simple to-do lists or more structured systems with metrics?
Have you ever tried using tools like Jira for personal planning?

I’d love to hear your thoughts and approaches. Maybe there are even better systems out there that I haven’t tried yet.

The Moment I Realized Dev Tools Matter

Rust — Mon, 09 Feb 2026 14:00:00 +0000

When you are starting your web developer career, you have to focus on the following (or similar) things:

HTML
CSS
JS/TS
Git
React
Vue
Sass/Less
Bootstrap / Material UI / Ant Design

And the list is rising and rising every year. Job seekers try to study more and more. Then you start searching for your first company. You absolutely know it’s not easy. And then there is your first job offer and the first day in your company. You are happy, and there is onboarding. You are trying to learn more: Jira, Agile, team code styles, team rules, BAs, PMs, QAs, and etc. Finally, you start writing your code and fixing bugs.

In all these things, I have absolutely forgotten about one important skill — how to fix bugs better and more efficiently using Dev Tools. Honestly, I am not sure that I really knew much about Dev Tools, because modern frontend courses often don’t include a Dev Tools section or include only a very limited part. As a result, juniors don’t understand how helpful Dev Tools can be.

Today I would like to talk about how often Dev Tools are pushed to the second or even third place when a junior starts working. But this is not a guide like “How to use Dev Tools” or something like that.

During the first couple of months at my job, I used Dev Tools only to look at styles in the Elements tab and the Network tab to check request errors. That’s all. I was lost among the tabs and didn’t know what all those values meant… And it didn’t feel required for a junior. My attention was focused on other parts of the job, and I completely lost focus on my efficiency. I ignored Dev Tools for a long time: I tried to debug using console.log instead of breakpoints, and I tried to write more code instead of analyzing already written code in Dev Tools. Just tell me that I was not alone…

Then I started to understand how powerful Dev Tools really are:

Use Breakpoints and inspect variables live
Measure rendering and scripting performance in real time
Detect UI freezes and long tasks
Analyze unnecessary re-renders
Inspect framework component trees, props, and state
Simulate slow networks, weak devices, or even offline mode
Audit accessibility issues
Use Lighthouse to analyze performance and SEO
Use the Memory tab to inspect localStorage, sessionStorage, cookies, and IndexedDB
Debug production bugs that don’t reproduce in development mode

Dev Tools are like your car dashboard. If you know exactly where to look, you can find the reason for almost any problem. But modern Dev Tools are much more crowded compared to a car dashboard. It feels like a car is bigger and more massive than modern websites, yet Dev Tools contain far more information than a car’s dashboard.

So Dev Tools are often the real difference between a junior developer and a middle or senior one. You can keep working with console.log or asking AI to debug the code using those logs — and sometimes that will work. But if you truly want to grow, to understand what’s happening instead of guessing, you need something more powerful. You need to see, measure, pause, and analyze.

That’s where Dev Tools stop being optional and start becoming your habit.

And if you want to become a master, this is one of those skills you simply can’t ignore.