javascript

Attention over time

7-day rolling share of analyzed posts/comments mentioning this entity · 90 daily points ending 2026-10-15

Final complete day: 2026-10-15. Attention was 1.1% — this entity appeared in 30 of 2,852 analyzed posts/comments in the seven days ending that day (45 mentions).

Each point is a seven-day rolling window of complete UTC days; a point is comparable only when at least 100 analyzed posts or comments fall inside it. A day with no analyzed records counts as zero; missing coverage is marked and never shown as zero. The series ends at the latest complete analyzed day — it never extends into the current incomplete day. How attention is measured.

Recent mentions

1. 2026-10-15 14:50 UTCComment

   It doesn´t take 6 months to a year, but you do need to grind some fundamental syntax skills. Best option would be to use something like CodeWars. Go to the website, sort the easiest javascript practice questions by popularity and start solving them one by one. After you finish the first hundred, answering the questions like the one you had trouble with will be automatic. You just need repeatable practice and if you don´t get that in your daily job, you need to look it up by yourself.

2. 2026-10-15 08:48 UTCComment

   I think two separate problems are getting mixed together: understanding the logic and remembering JavaScript syntax. For the loop, put the steps in plain English: "Start at 1, show the number, add 1, and stop after 5." If that makes sense, you understand the logic. You can look up the syntax in the docs. I'd spend 15 minutes working without AI on small variations, such as counting backward or counting by twos, then rewrite the solution in a blank file. That should make the actual sticking point clearer instead of reinforcing the memorization loop.

3. 2026-10-14 23:22 UTCComment

   Hey I'm a front end lead. I am assuming you're talking about web-apps. Skills in the order I would learn them, if I was you: Usability. If you have designers you don't have to deep dive, but a 101 course or the youtube equivalent will help a lot. It is mostly a lot of tips like "try to have no more than 7 menu items without grouping them, because human short term memory holds 5-9 things." It should give you a structure to think about what UIs do and why. Graphic design: read about layout grids. You have to understand spacing to be able to replicate a design properly. Things need to line up, be evenly spaced etc and we use grids to do that. On the web we have to think about fluidity and form factors too. Optionally you can get into visual hierarchy, colours, and fonts - but a designer would do that work for you. Accessibility. You can put accessibility testing including screen reader testing in your CI pipeline. Read a few articles so you avoid the main beartaps. Browser technology. Learn about modern HTML and CSS, it has a lot of features - you might not need JavaScript for more than you imagine. Brush up on stuff like HTTP cacheing, redirects, error codes. There's a ton of power in HTTP and REST and HTML. The book Every Layout changed how I think about CSS. Design systems. There are a few standards for how to structure a design system, which can be applied to CSS. It's just a format for organising and naming colours, fonts, spacings etc Typescript. It's quite like C#. The type system is a bit fiddly but very powerful. Your agents will be a lot more reliable if you start out with good types. For extra credit find a way to share over-the-wire types between front and backend. We tend to use functional patterns like map and reduce a lot. A framework and metaframework. Take your pick! Make sure you're doing server side rendering, it's 2026. React/NextJS is the most employable but I hate it. Whatever you're using, learn how it works. Try to avoid loading spinners whenever you can.

4. 2026-10-14 12:23 UTCComment

   You need to find your own sensible sequence for solving problems and learn to use it consistently. Every problem can be broken down into smaller units and placed in an order of operation. This is true in programming and in just about anything else in life. You need to understand what each unit represents and how the units work together. When you look at code, you’re looking at sentences. They’re written in a language you haven’t learned to write yet. Learn the characters and words the language uses, understand what they represent and then learn how to put them together to communicate instructions. For instance, suppose you’re trying to write a loop in JavaScript that counts from 1 to 5. You have to give the computer several pieces of information to accomplish that. The computer doesn’t know what you want it to do until you tell it. for (let shit = 1; shit <= 5; shit++) { console.log(shit); } Think of the code as a shell that you’re filling with instructions. Each part has a specific job, and the parts work together to produce the result. **for** tells JavaScript that you’re defining a loop. A loop is an action that repeats. The word for doesn’t tell it what to count or when to stop. It establishes the type of instruction you’re about to give it. **( )** mark the beginning and end of the loop’s control instructions. Everything between them tells JavaScript where the loop begins, what condition it must follow and how the value changes each time. **let** tells JavaScript you’re creating a variable. A variable is a named place to store a value. You use one when you need to store information that may change while a program runs. **shit** is the name of that variable. The name itself has no special meaning to JavaScript. I could call it i, counter, number, banana or almost anything else that follows JavaScript’s naming rules. It wouldn’t change how the loop works, provided I use the same name consistently wherever I refer to that variable. Think of it like labeling a container. The label helps you identify what’s inside, but changing the label doesn’t change the contents. **=** is the assignment operator. It puts the value on the right into the variable on the left. **1** is the starting value. You’re telling JavaScript that the variable named shit begins with the number 1. **The first ;** separates the starting instruction from the condition that comes next. **shit <= 5** is the condition. The symbol <= means “less than or equal to.” JavaScript checks whether the current value of shit is 5 or less before each iteration. If the condition is true, the loop runs. When the value becomes 6, the condition is false and the loop stops. **;** separates the condition from the instruction that updates the variable. **shit++** means increase the current value stored in shit by 1. The two plus signs together are the increment operator. After each iteration, JavaScript increases the value and checks the condition again. If I wanted to count by 5 instead, I could write shit += 5. If I wanted to count by 2, I could write shit += 2. The starting value, stopping condition and increment are separate instructions. **{ }** mark the beginning and end of the block of code that repeats. Everything inside those braces runs during each iteration. **console** refers to a developer tool that can display information while code runs. **.** accesses something belonging to an object. Here, it connects console to its log method. **log** is the method that displays the value you give it. **(shit)** tells the method which value to display. Because shit changes during the loop, the displayed value changes too. ; marks the end of that statement. So what have you told the computer to do? Start a variable at 1, check whether its value is 5 or less, display the value, add 1 and repeat until the condition is no longer true. You don’t need to memorize every possible solution. You need to understand what the pieces mean, what each one does and how they work together. Once you understand the pieces, you can change the variable name, starting value, stopping condition or increment to solve a different problem. That’s the difference between memorizing code and understanding how to write it.

5. 2026-10-14 10:40 UTCComment

   If you want to go beyond webdev, embedded development with Node.js on Raspberry Pi is a solid jump because you still use JavaScript but deal with GPIO and hardware timing. Debugging async sensor input is way rougher than browser JS.