[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"verticals":3,"game-reaction-time":44,"comments-game-reaction-time":85,"search-suggestions":87},[4,20,32],{"id":5,"slug":6,"name":7,"tagline":8,"description":9,"accentFrom":10,"accentTo":11,"icon":12,"defaultLocale":13,"locales":14,"features":16,"position":19},"019fe637-3d33-714b-b57f-23e163ffca0c","dev","Web Development","Read it. Run it. Prove it.","A post a day on modern web development — most with an editable playground and a quiz that explains every answer. Free, no account needed.","violet-500","cyan-400","◇","en",[13,15],"fa",{"courses":17,"paths":17,"articles":17,"exams":18,"flashcards":18,"packages":17,"community":17,"certificates":17,"teams":17,"commerce":17},true,false,0,{"id":21,"slug":22,"name":23,"tagline":24,"description":25,"accentFrom":26,"accentTo":10,"icon":27,"defaultLocale":13,"locales":28,"features":30,"position":31},"019fe637-3dc2-754c-8657-0f175bfee7c6","lang","Languages","Learn a language the way you learn a codebase.","Grammar explained the way good documentation explains an API — one idea at a time, each with a quiz.","amber-400","⌘",[13,15,29],"es",{"courses":18,"paths":18,"articles":17,"exams":18,"flashcards":17,"packages":18,"community":17,"certificates":17,"teams":18,"commerce":18},2,{"id":33,"slug":34,"name":35,"tagline":36,"description":37,"accentFrom":38,"accentTo":39,"icon":40,"defaultLocale":13,"locales":41,"features":42,"position":43},"7b3c16f2-931d-410e-802e-e1fa4edab7de","soft","Soft Skills","The half of the job nobody wrote documentation for.","Weekly, on the parts of working life that decide more than your code does — first weeks, meetings, interviews, promotions, and the people around you. Written from what actually happens, and recorded as a podcast you can listen to on the walk.","emerald-400","teal-300","◉",[13],{"courses":18,"paths":18,"articles":17,"exams":18,"flashcards":18,"packages":18,"community":17,"certificates":18,"teams":18,"commerce":18},3,{"id":45,"slug":46,"title":47,"tagline":48,"description":49,"genre":50,"surface":51,"coverUrl":52,"accentFrom":53,"accentTo":54,"motif":55,"status":56,"weekKey":57,"featured":18,"sessionSeconds":58,"freeLevels":57,"maxScoreRate":59,"maxScore":60,"config":61,"faq":65,"controls":75,"seo":57,"playCount":19,"playerCount":19,"createdAt":82,"updatedAt":83,"releaseAt":84,"publishedAt":57,"you":57},"01a09b23-a070-72da-824c-732950e5dfbe","reaction-time","Reaction Time","Green means click. Everything else is you being too eager.","Wait for the screen to turn green, then click as fast as you can. Five rounds, averaged, and the average is the number that counts — one lucky 140ms means nothing if the other four are 300. The world sits somewhere around 250 milliseconds for a visual cue, most people land between 200 and 300, and anything under 180 consistently is genuinely quick. The catch is that the wait is random, between one and five seconds, so you cannot anticipate it: click early and the round is void, which is the whole test. Reaction time is measurably worse when you are tired, and measurably better when you are warm and paying attention, so it is worth taking twice before believing the result. Takes about thirty seconds, needs no account, and works on a phone — though a mouse will beat a touchscreen by a few milliseconds every time, which is worth knowing before comparing with anybody.","REFLEX","DOM","\u002Fcovers\u002Fgames\u002Freaction-time.png","rose-400","red-500","pulse","PUBLISHED",null,45,400,7000,{"rounds":62,"maxWaitMs":63,"minWaitMs":64},5,5000,1000,[66,69,72],{"answer":67,"question":68},"The median for a visual cue is around 250ms. Under 200ms is fast, under 180ms consistently is very fast, and under 150ms usually means the click was anticipated rather than reacted to. Audio cues are about 40ms quicker than visual ones for everybody.","What is a good reaction time?",{"answer":70,"question":71},"Touchscreens add real latency — typically 20 to 50ms between your finger landing and the browser hearing about it — on top of the display's own refresh delay. Compare phone scores with phone scores.","Why is my reaction time worse on a phone?",{"answer":73,"question":74},"Sleep, mostly. Reaction time degrades sharply with fatigue and improves with warming up, caffeine and simply expecting the cue. Practice helps for about a week and then plateaus — the ceiling is largely physiological.","How can I improve my reaction time?",[76,79],{"keys":77,"action":78},"Click \u002F Tap","React",{"keys":80,"action":81},"Space","React with the keyboard","2026-09-13T14:19:58.448Z","2026-09-13T15:02:52.179Z","2026-09-22T09:00:00.000Z",{"locked":18,"total":19,"comments":86},[],[88,92,96,100,104,108,112,116,119,123,126,130],{"slug":89,"name":90,"articles":91},"webdev","Webdev",93,{"slug":93,"name":94,"articles":95},"javascript","Javascript",78,{"slug":97,"name":98,"articles":99},"frontend","Frontend",70,{"slug":101,"name":102,"articles":103},"css","Css",32,{"slug":105,"name":106,"articles":107},"tutorial","Tutorial",24,{"slug":109,"name":110,"articles":111},"typescript","Typescript",14,{"slug":113,"name":114,"articles":115},"performance","Performance",12,{"slug":117,"name":78,"articles":118},"react",11,{"slug":120,"name":121,"articles":122},"browser","Browser",8,{"slug":124,"name":125,"articles":122},"node","Node",{"slug":127,"name":128,"articles":129},"grammar","Grammar",6,{"slug":131,"name":132,"articles":129},"programming","Programming"]