<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Asael Shinder</title>
    <description>The latest articles on DEV Community by Asael Shinder (@asael_shinder_9f53bdca840).</description>
    <link>https://dev.to/asael_shinder_9f53bdca840</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4076536%2F805e5848-17cb-4252-ab0f-7ee7e52a32b5.png</url>
      <title>DEV Community: Asael Shinder</title>
      <link>https://dev.to/asael_shinder_9f53bdca840</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/asael_shinder_9f53bdca840"/>
    <language>en</language>
    <item>
      <title>More of What You Say in Meetings Will Be Written Down by Software</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:17:49 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/more-of-what-you-say-in-meetings-will-be-written-down-by-software-1mp5</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/more-of-what-you-say-in-meetings-will-be-written-down-by-software-1mp5</guid>
      <description>&lt;p&gt;Join a call at many companies now and you will see a small notice that the meeting is being transcribed. When it ends, a summary appears in the chat, with a list of decisions and actions, sometimes before you have closed the window. The main video meeting tools all offer some version of this, and more organisations are switching it on by default.&lt;/p&gt;

&lt;p&gt;That changes something quietly important about meetings. For years, a lot of what was said in them was gone the moment people left the room. Now more of it becomes searchable text that people who were not there can read, sometimes months later.&lt;/p&gt;

&lt;p&gt;There are real benefits. People who missed the meeting can catch up. Colleagues working in their second language can check what was said. Actions are less likely to be forgotten. Used well, these tools can make meetings fairer.&lt;/p&gt;

&lt;p&gt;But they also bring new habits worth learning early.&lt;/p&gt;

&lt;p&gt;Read the summary, especially when you are named in it. Automated summaries can be wrong. They can attribute a point to the wrong person, turn a maybe into a decision, or miss the caveat that mattered most. If the summary says you agreed to deliver something by Friday and you did not, correct it in writing that day. Once a summary has been shared, people tend to treat it as the record.&lt;/p&gt;

&lt;p&gt;Speak as if a stranger may read it later, because one might. That does not mean being dull or guarded. It means saying what you mean clearly, being careful with jokes about named people, and not discussing anyone's health or personal life in a meeting that is being transcribed.&lt;/p&gt;

&lt;p&gt;Know where the off switch is, and when to ask for it. Some conversations, like personal matters, sensitive staffing discussions, or early ideas that need room to be wrong, are better held without a transcript. It is reasonable to ask at the start whether this one needs recording.&lt;/p&gt;

&lt;p&gt;And if you chair meetings, take responsibility for the summary yourself. Check it, fix it, and send it on. The tool can write things down. Deciding what was really agreed is still a job for people.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>future</category>
      <category>ai</category>
      <category>meetings</category>
    </item>
    <item>
      <title>Your Self Assessment Is Due on Friday and You Do Not Know What to Write</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:12:38 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/your-self-assessment-is-due-on-friday-and-you-do-not-know-what-to-write-3l4l</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/your-self-assessment-is-due-on-friday-and-you-do-not-know-what-to-write-3l4l</guid>
      <description>&lt;p&gt;The annual review form has arrived. Before your manager writes anything, you are asked to assess yourself. What did you achieve this year? Where did you grow? What would you do differently? There are three empty boxes and a deadline on Friday, and you cannot remember what you did in March.&lt;/p&gt;

&lt;p&gt;Many people treat this form as a chore, write a few modest lines, and hope their manager remembers the rest. It is worth more effort than that. Your manager may be writing reviews for eight or ten people at once, and your self assessment is often the most detailed record they have of your year. What you write can shape what they write.&lt;/p&gt;

&lt;p&gt;Start by gathering evidence, not by writing. Go through your calendar, your closed tickets, your merged pull requests and the documents you wrote, month by month. Note anything that mattered. A feature shipped, an incident handled, a new colleague you helped settle in, a process you improved. You will find far more than you remember.&lt;/p&gt;

&lt;p&gt;Then pick the four or five that had the most effect, and write each one as what you did and what changed because of it. Not worked on the payment retries. Instead, redesigned the payment retry logic, which cut failed renewals from about two hundred a week to about forty. If you do not have a number, describe who benefited and how.&lt;/p&gt;

&lt;p&gt;Be honest in the box about what you would do differently, and keep it constructive. Something like I took on too much in the autumn and the migration slipped as a result, so next year I will raise capacity problems earlier. A clear, calm admission reads as maturity. A list of excuses, or no weaknesses at all, usually reads as the opposite.&lt;/p&gt;

&lt;p&gt;Do not compare yourself with colleagues, and do not undersell your work out of politeness. Your manager cannot give you credit for things you leave out.&lt;/p&gt;

&lt;p&gt;Finally, keep a copy, and start a simple note today for next year. One line a week about what you did. Next November, the boxes will take an hour instead of a week of worry.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>feedback</category>
      <category>reviews</category>
      <category>career</category>
    </item>
    <item>
      <title>You Still Have Twelve Days of Holiday Left and You Feel Guilty Taking Them</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:07:27 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/you-still-have-twelve-days-of-holiday-left-and-you-feel-guilty-taking-them-3c8m</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/you-still-have-twelve-days-of-holiday-left-and-you-feel-guilty-taking-them-3c8m</guid>
      <description>&lt;p&gt;It is November, and the HR system has sent a reminder. You still have twelve days of holiday to take before the end of the year. You have been meaning to book them since the summer. Every time you looked, there was a release coming, a colleague already away, or a project that felt like it needed you.&lt;/p&gt;

&lt;p&gt;If you are honest, the problem is not the calendar. It is a quiet worry that taking time off will make you look less committed, or that things will go wrong without you and everyone will notice. It is worth looking at that worry directly, because it is usually wrong.&lt;/p&gt;

&lt;p&gt;Start with the simple fact. Holiday is part of your pay. Your employer agreed to it when they hired you, and they plan for people to take it. In many countries a minimum amount is a legal right. Most companies would much rather you took your leave than built up a large balance, and many only let you carry a few days into the next year, or none at all. Check your own policy this week, because days you do not take may simply disappear.&lt;/p&gt;

&lt;p&gt;Then look at what you are protecting. If the team genuinely cannot cope for a week without you, that is not a sign that you are indispensable. It is a risk your manager needs to know about, and your absence is the safest way to find the gaps while you are still around to fill them afterwards.&lt;/p&gt;

&lt;p&gt;So make it easy for everyone. Pick your dates now and tell your manager in writing, rather than waiting for a perfect quiet week that never comes. Two separate weeks are often easier for a team than one long block in December. Before you go, write a short handover. What is in progress, who to ask about what, and what can safely wait until you are back.&lt;/p&gt;

&lt;p&gt;Then actually be away. Turn off notifications on your phone. Set an out of office message that names someone else to contact. Do not check in once a day just in case.&lt;/p&gt;

&lt;p&gt;When you return, notice what happened. Most of the time, the team managed, somebody learned something new, and you came back with more energy than you left with. That is what the time is for.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>confidence</category>
      <category>wellbeing</category>
      <category>career</category>
    </item>
    <item>
      <title>Your Manager's Manager Has Booked a Skip Level Meeting With You</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 07:02:17 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/your-managers-manager-has-booked-a-skip-level-meeting-with-you-3h8f</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/your-managers-manager-has-booked-a-skip-level-meeting-with-you-3h8f</guid>
      <description>&lt;p&gt;A thirty minute invitation appears in your calendar. It is from your manager's manager, the head of engineering, and the title just says catch up. You have spoken to her twice, both times in a lift. Your first thought is that something is wrong.&lt;/p&gt;

&lt;p&gt;Almost certainly nothing is. Many managers run skip level meetings, where they talk directly to people two levels below them. They do it to hear how things really feel on the ground, without everything being filtered through their managers first. It is usually a routine part of their job, and they may be meeting everyone on your team.&lt;/p&gt;

&lt;p&gt;So prepare, but lightly. Think of two or three things you would genuinely like her to know. Something that is working well and deserves credit. Something that slows the team down and that she might be able to change. Perhaps one question about where the department is heading. Write them down so you do not go blank.&lt;/p&gt;

&lt;p&gt;Expect open questions. What is getting in your way? What would you change if you could? How is the team doing? Answer them honestly and specifically. Our releases take two days because the test environment is shared with three other teams is far more useful to her than things are a bit slow sometimes.&lt;/p&gt;

&lt;p&gt;Be careful with one thing. If you have a problem with your own manager, a skip level meeting can feel like the moment to raise it. It can be, but think it through first. If you have not said it to your manager directly, it will usually be fairer, and work better, to do that first. Complaints that arrive from above without warning tend to damage trust on every side. If the problem is serious, or you have already tried, say so plainly and calmly, and stick to what happened rather than how you feel about the person.&lt;/p&gt;

&lt;p&gt;Use some of the time to learn, too. Ask what she is worried about this year, or what she wishes engineers understood about how decisions are made. You will rarely get a more direct view of the bigger picture.&lt;/p&gt;

&lt;p&gt;Afterwards, tell your manager the meeting happened and roughly what you talked about. No secrets, no surprises. That keeps everyone comfortable with the next one.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>communication</category>
      <category>management</category>
      <category>meetings</category>
    </item>
    <item>
      <title>Your Page Is Slow and You Have Never Opened the Network Tab</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 06:57:07 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/your-page-is-slow-and-you-have-never-opened-the-network-tab-3g2i</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/your-page-is-slow-and-you-have-never-opened-the-network-tab-3g2i</guid>
      <description>&lt;p&gt;A customer says the orders page takes ages to load. You open it on your machine and it feels fine. You add some logging to the backend, the queries look quick, and you are stuck. Somebody asks whether you checked the network tab. You nod, and then quietly look up what they mean.&lt;/p&gt;

&lt;p&gt;Every major browser has developer tools built in, and the network panel is one of the most useful parts of them. In Chrome, Edge and Firefox you can open the tools with F12, or with Ctrl Shift I, or Cmd Option I on a Mac, and choose Network. Then reload the page. Every request the page makes appears as a row, with its status, its size, and how long it took.&lt;/p&gt;

&lt;p&gt;Start with the waterfall, the column of bars on the right. Each bar is one request, placed on a timeline. You are looking for shape, not detail. A long single bar means one slow request. A staircase of bars, each starting when the previous one finishes, means requests waiting on each other when they could run together. Dozens of short bars means the page is making far more calls than you thought.&lt;/p&gt;

&lt;p&gt;Click on a slow request and open its Timing tab. It breaks the time into stages. If most of it is spent waiting for the server to respond, the problem is on the backend, and you now know exactly which endpoint to investigate. If most of it is spent downloading, look at the size column. A response of several megabytes for a list of twenty orders tells you something is sending far more data than the page uses.&lt;/p&gt;

&lt;p&gt;Then make your machine behave more like your customer's. Tick Disable cache, so you see what a first visit costs. Use the throttling menu to simulate a slower connection. Pages that feel instant on office broadband can take many seconds on a weak mobile signal, which is often exactly what the customer meant.&lt;/p&gt;

&lt;p&gt;Finally, sort the list by size and by time, and write down the three worst requests. That short list is a much better starting point than guessing. Spend ten minutes on this panel before your next performance bug, and you will rarely be stuck in the same way again.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>learning</category>
      <category>webdev</category>
      <category>performance</category>
    </item>
    <item>
      <title>You Have Been Nominated for Your Company's Leadership Programme</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 06:51:55 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/you-have-been-nominated-for-your-companys-leadership-programme-2o2c</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/you-have-been-nominated-for-your-companys-leadership-programme-2o2c</guid>
      <description>&lt;p&gt;An email arrives from HR. You have been nominated for this year's leadership programme. Twelve people from across the company, six workshops, a mentor from the senior team, and a group project to present to the directors in the spring. Your manager put your name forward and is clearly pleased.&lt;/p&gt;

&lt;p&gt;You are pleased too, and slightly worried. You like writing code. Does this mean the company has decided you should stop?&lt;/p&gt;

&lt;p&gt;Not necessarily, and the first thing to do is find out. Ask your manager why they nominated you and what they hope you will get out of it. Some programmes are designed to grow future managers. Others are about influence and decision making, and are open to senior engineers who intend to stay technical. The answer changes how you should approach the whole thing.&lt;/p&gt;

&lt;p&gt;Then ask what it will cost you in time, honestly. Six workshops sounds light until you add the reading, the group project and the travel. Agree with your manager now what will move off your plate to make room. If nothing moves, you will spend months doing the programme in your evenings and your regular work will suffer, which helps nobody.&lt;/p&gt;

&lt;p&gt;Once you are in, take the parts that are rare. The workshops are useful, but you can find similar material in books. What you cannot easily find elsewhere is an hour a month with a senior leader who has agreed to answer your questions, and eleven colleagues from finance, operations and sales who will be running parts of the company in a few years. Get to know them properly. They will be the people you call when you need something done across the organisation.&lt;/p&gt;

&lt;p&gt;Treat the group project as real work, because people will watch how you do it. Choose a problem that genuinely matters to the company, keep the scope small enough to finish, and make sure everyone in the group gets credit when you present.&lt;/p&gt;

&lt;p&gt;And if you do the programme and decide you do not want to manage people, say so clearly afterwards. That is a perfectly good outcome. You will understand how decisions are made above you, and that makes you a better engineer whatever title you hold.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>career</category>
      <category>leadership</category>
      <category>growth</category>
    </item>
    <item>
      <title>Your Mentee Wants to Quit a Job They Started Four Months Ago</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Mon, 16 Nov 2026 06:46:45 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/your-mentee-wants-to-quit-a-job-they-started-four-months-ago-1ec5</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/your-mentee-wants-to-quit-a-job-they-started-four-months-ago-1ec5</guid>
      <description>&lt;p&gt;Your mentee started a new job in the summer. They were thrilled when they got the offer, and you helped them prepare for the interviews. Now they message you on a Sunday evening. I think I made a mistake. I want to start applying again. Is it too soon?&lt;/p&gt;

&lt;p&gt;Before you answer the question about timing, find out what has actually gone wrong. Four months is long enough for the honeymoon to end and short enough that a lot of things are still settling. Ask them to describe a normal week. What do they dread, and what, if anything, do they look forward to?&lt;/p&gt;

&lt;p&gt;The answers usually fall into one of two groups. The first is the kind of problem that tends to ease with time. The codebase is bigger than they expected, nobody gives them much direction, they do not have friends at work yet, and they feel slow. Almost every new joiner feels like this for a while, and most people underestimate how long it takes to feel useful in a new place. Six months to a year is common.&lt;/p&gt;

&lt;p&gt;The second group is different. The job is not the one they were offered. Their manager is unkind or absent in a way that is not changing. They are being asked to do something they think is wrong. Or their health is suffering. Those are not reasons to wait it out just to make a CV look tidier.&lt;/p&gt;

&lt;p&gt;If it is the first group, help them try one or two specific fixes before deciding. Ask their manager for a clear goal for the next six weeks. Find one person on the team to pair with regularly. Set a date, perhaps two months away, to look at it again honestly.&lt;/p&gt;

&lt;p&gt;If it is the second group, or if the fixes do not help, back them. A short role on a CV is far less damaging than people fear, as long as they can explain it in one calm sentence without criticising the employer. Help them write that sentence. Remind them to look at what went wrong in their last search, too. What did they not ask in the interviews that would have warned them?&lt;/p&gt;

&lt;p&gt;And tell them that leaving early is not proof they are bad at choosing. Sometimes you only find out what a job is like by doing it.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>mentorship</category>
      <category>career</category>
      <category>jobs</category>
    </item>
    <item>
      <title>Software May Help Decide Your Next Promotion</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Thu, 12 Nov 2026 09:05:24 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/software-may-help-decide-your-next-promotion-2me5</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/software-may-help-decide-your-next-promotion-2me5</guid>
      <description>&lt;p&gt;More companies are buying tools that use AI to help manage people. Some summarise your work into draft performance reviews. Some suggest who is ready for promotion based on project data. Some score activity in the tools you use every day. They are sold as a way to make decisions fairer and faster, and some of them may well help.&lt;/p&gt;

&lt;p&gt;The law is starting to take this seriously. The European Union's AI Act treats AI systems used to make decisions about promotion and termination, to allocate work based on people's behaviour or traits, or to monitor and evaluate workers' performance, as high risk. That brings obligations for the companies that build and use them, including human oversight. Employers using such a system are also expected to tell workers and their representatives before it is put into use. The Act already bans AI that tries to recognise emotions at work, except for medical or safety reasons. In the EU and the UK, data protection law also gives you rights around decisions made solely by automated means.&lt;/p&gt;

&lt;p&gt;You do not need to be a lawyer to act on this. You need to notice what a tool is measuring, and how your work looks to it.&lt;/p&gt;

&lt;p&gt;Think about where your best work actually shows up. Commits and closed tickets are easy for software to count. Unblocking a colleague, reviewing someone's design carefully, or talking a team out of a bad idea usually leave much fainter traces. If a tool is part of how you are judged, make that invisible work visible in writing. Short notes in your own words of what you did and what changed because of it.&lt;/p&gt;

&lt;p&gt;Ask questions early, politely and in writing. Is any software involved in reviews or promotion decisions? What data does it use? Who checks its output, and can I see what it said about me? A good employer will have answers, and asking shows you care about fairness, not that you are making trouble.&lt;/p&gt;

&lt;p&gt;And if you become a manager, treat any score as the start of a conversation, never the end of one. The people who will be trusted with these tools are the ones who can explain every decision without pointing at the screen.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>future</category>
      <category>ai</category>
      <category>career</category>
    </item>
    <item>
      <title>You Watched Five People Try Your Feature and Most of Them Could Not Find It</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Thu, 12 Nov 2026 09:00:14 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/you-watched-five-people-try-your-feature-and-most-of-them-could-not-find-it-423k</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/you-watched-five-people-try-your-feature-and-most-of-them-could-not-find-it-423k</guid>
      <description>&lt;p&gt;Your team finally ran a usability session. Five people from outside the team were asked to complete a task using the new feature you built, while you watched quietly on a call. Three of them never found the button. One found it and then did not trust what it did. Only one finished without help.&lt;/p&gt;

&lt;p&gt;You spent six weeks on that feature. Watching it fail in silence is one of the hardest kinds of feedback to receive, because nobody is saying anything critical. They are just struggling, and you cannot help.&lt;/p&gt;

&lt;p&gt;That is exactly why it is so valuable. Every other kind of feedback on your work is somebody's opinion. This is behaviour. Nobody was being polite, nobody was guessing what users might do, and nobody had read the design document first.&lt;/p&gt;

&lt;p&gt;Resist the first reaction, which is to explain. They should have looked at the menu. They were not our target users. The tooltip covers it. Some of that may be true, but if three people out of five missed it, the next three hundred will as well. The usability researcher Jakob Nielsen has long argued that a handful of test users finds most of the obvious problems, which is why five people can tell you so much.&lt;/p&gt;

&lt;p&gt;Instead, go back through the recordings or your notes and write down the exact moments people hesitated. Where did their mouse go first? What did they say out loud while they looked? Which words on the screen did they read, and which did they skip? Those moments are your list of fixes, and they are far more precise than anything a reviewer could have written.&lt;/p&gt;

&lt;p&gt;Then separate the problems from the solutions. Users are excellent at showing you where something is wrong and much less reliable at telling you how to fix it. If one participant says just make the button red, note that they could not see it, and then decide with your designer how to make it findable.&lt;/p&gt;

&lt;p&gt;Finally, thank the team for running the session, and ask to watch the next one before you build anything. The cheapest time to learn this lesson is before six weeks of work.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>feedback</category>
      <category>ux</category>
      <category>usability</category>
    </item>
    <item>
      <title>You Have to Record a Demo Video and You Hate the Sound of Your Own Voice</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Thu, 12 Nov 2026 08:54:51 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/you-have-to-record-a-demo-video-and-you-hate-the-sound-of-your-own-voice-4lb7</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/you-have-to-record-a-demo-video-and-you-hate-the-sound-of-your-own-voice-4lb7</guid>
      <description>&lt;p&gt;Your feature is finished, and your manager has asked for a five minute video walking through it, to share with the teams who were not in the release meeting. You record a first attempt, play it back, and want to delete it immediately. Is that what I really sound like?&lt;/p&gt;

&lt;p&gt;Almost everyone reacts this way, and there is a simple reason. When you speak, you hear your own voice partly through the air and partly through the bones of your skull, which carry lower frequencies. A recording only captures the air. So the voice on the recording sounds thinner and higher than the one you are used to. Everyone else has been hearing that version all along, and it does not bother them.&lt;/p&gt;

&lt;p&gt;So the first step is to stop judging the recording by how strange it sounds to you. Judge it by whether someone who was not there would understand the feature after watching it.&lt;/p&gt;

&lt;p&gt;That changes what you work on. Write down the three things the viewer needs to take away, and build the video around them. Start with the problem the feature solves, in one sentence, before you show any screens. Show one realistic example from start to finish rather than every option in every menu. Close your other windows, turn off notifications, and make the text on screen large enough to read on a laptop.&lt;/p&gt;

&lt;p&gt;Do not script every word. Read sentences sound stiff, and you will hear it. A short list of points on a piece of paper next to the screen is enough. If you lose your way, pause, and carry on from the last point. Most tools let you trim the beginning and end, and nobody minds a natural pause in the middle.&lt;/p&gt;

&lt;p&gt;Limit yourself to three takes. The first one is practice, the second is usually good, and the third is often worse because you are tired and trying too hard. Send the best of them.&lt;/p&gt;

&lt;p&gt;Then ask one colleague to watch it and tell you what the feature does. If they can, the video worked, whatever your voice sounded like to you.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>confidence</category>
      <category>demos</category>
      <category>speaking</category>
    </item>
    <item>
      <title>A Colleague Sends You Hi and Then Nothing for Ten Minutes</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Thu, 12 Nov 2026 08:49:38 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/a-colleague-sends-you-hi-and-then-nothing-for-ten-minutes-4ff1</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/a-colleague-sends-you-hi-and-then-nothing-for-ten-minutes-4ff1</guid>
      <description>&lt;p&gt;A message arrives from a colleague. Hi. You reply. Hi, how are you? And then you wait. Five minutes later, sometimes ten, the real question appears. By then you have switched away from what you were doing, started wondering if something is wrong, and checked the window three times.&lt;/p&gt;

&lt;p&gt;It is a small thing, and it happens many times a week in most teams. It is also one of the easiest habits to change, as long as you remember why people do it.&lt;/p&gt;

&lt;p&gt;Usually it is politeness. In conversation you would never walk up to someone and fire a question at them without a greeting first. People bring that habit into chat, especially if they are new, junior, or come from a culture where starting with the request feels rude. They are being considerate in the way they know.&lt;/p&gt;

&lt;p&gt;So do not lecture them, and do not send them a link to a website about it in front of the team. Instead, show them a better pattern, and give them permission to use it. Something like this. Feel free to send the whole question in your first message, even if I am busy. Then I can answer as soon as I see it, instead of us waiting for each other. That makes the change about saving their time as well as yours.&lt;/p&gt;

&lt;p&gt;Model it yourself. When you need something, put the greeting and the request in the same message. Hi Priya, quick one. Do you know who owns the billing export? I am trying to find out why the totals changed on Monday. Your colleague can reply with the answer straight away, and if they are in a meeting they can answer when they come out without any back and forth.&lt;/p&gt;

&lt;p&gt;If it is a team pattern rather than one person, raise it once at a retro as a small team agreement. Many teams write down a few norms like this, alongside when to use a channel and when to message someone directly.&lt;/p&gt;

&lt;p&gt;And when someone does start with hi, just reply hi, what can I help with? It keeps the warmth and moves things along. The aim is not to make chat colder. It is to stop good manners costing everyone ten minutes.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>communication</category>
      <category>remote</category>
      <category>messaging</category>
    </item>
    <item>
      <title>Your Program Crashed and the Error Is Two Hundred Lines Long</title>
      <dc:creator>Asael Shinder</dc:creator>
      <pubDate>Thu, 12 Nov 2026 08:44:28 +0000</pubDate>
      <link>https://dev.to/asael_shinder_9f53bdca840/your-program-crashed-and-the-error-is-two-hundred-lines-long-a9g</link>
      <guid>https://dev.to/asael_shinder_9f53bdca840/your-program-crashed-and-the-error-is-two-hundred-lines-long-a9g</guid>
      <description>&lt;p&gt;The service fell over during testing and the log has a wall of text in it. Two hundred lines of class names, file names and line numbers. You scroll up and down, recognise none of it, copy the first line into a search engine, and hope.&lt;/p&gt;

&lt;p&gt;This is one of the most useful things you can learn to read properly, and it takes less time than you would think. That wall of text is a stack trace. It is the program telling you exactly which chain of calls it was in when it failed.&lt;/p&gt;

&lt;p&gt;Start by finding two things. The type of error and its message. Then the first line that mentions your own code. Everything else is context.&lt;/p&gt;

&lt;p&gt;Where those live depends on the language. In Java, the exception and its message come first, followed by lines starting with at, each one a method call. The top one is where the error was thrown. Much of what follows may be framework code you can skip until you find a package name you recognise. In Python it is the other way round. The heading says most recent call last, so the error type and message are on the final line, and the call nearest to it is just above.&lt;/p&gt;

&lt;p&gt;Then look for chained causes. In Java a trace often contains one or more sections beginning Caused by. Each one is an earlier error that was wrapped in a new one, and the last Caused by is usually the original failure. A message like failed to start the application at the top can hide a message like connection refused at the bottom, and that is the one you need. The lines ending in a number of more are not missing information, by the way. They are repeats of frames already printed above.&lt;/p&gt;

&lt;p&gt;Now read your own line of code with the message in mind. A null pointer on that line means something there was null. Which thing, and where did it come from? That question will take you further than any search.&lt;/p&gt;

&lt;p&gt;Practise on purpose. Next time someone on your team shares a trace, read it before you read their explanation, and see if you reach the same line. After a few weeks, the wall of text will become a map.&lt;/p&gt;

&lt;p&gt;– Asael Shinder&lt;/p&gt;

</description>
      <category>asaelshinder</category>
      <category>learning</category>
      <category>debugging</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
