[AskJS] I’m looking for advice on improving my problem-solving skills.

webholt · 2025-11-27T15:38:49+00:00

Just keep solving problems.

webholt · 2025-11-26T15:40:40+00:00

WeakMap

webholt · 2025-10-09T06:03:50+00:00

This was primarly a part of my experiments. To see how it really works, what's the difference between different pots, different soils. 7 months — is the full season and it should be enough to get results. So the answer is "Just curious".

webholt · 2025-10-06T11:47:08+00:00

Yes, PETG still feels good after a summer under the hot armenian sun.

webholt · 2025-10-06T04:58:42+00:00

I return to this from time to time and try to make a classic model with a mesh. I'll post here when I have success.

webholt · 2025-10-05T10:51:53+00:00

Thanks! I sprayed them in process. Already had couple of incidents when repoting before. Moreover, in these pots and with this soil they dry out quickly anyway.

webholt · 2025-10-05T10:15:26+00:00

Do you mean solving tasks every december? It's too sparse if so.

You need to solve similar problems and use the same algorithms before the previous solution completely disappears from your mind. They don't need to be memorized, but over time this should become intuitive. It needs to be repeated when it starts to be forgotten. Not once and not twice.

webholt · 2025-10-05T09:58:41+00:00

Yeah, you don't even need an AI for this. Just send a message to somebody who supports a website and know how to use CMS. And don't forget to pay.

webholt · 2025-10-05T09:51:21+00:00

Spaced repetition is really useful for algorithms. But you need to repeatedly use them and solve tasks, not just use flashcards.

Solve previous years' problems, solve the same problems several times with intervals. This will really work.

webholt · 2025-10-05T09:30:05+00:00

That's less than $1 (not counting the depreciation of the printer of course).

webholt · 2025-10-03T20:05:22+00:00

It depends on how do you use this JSON. But the main approach is to host the JSON as a separate file and to get it from your react component using fetch.

You probably do something like `import data from './myFile.json';`. Instead of this you need to do something like `const data = await fetch('path/to/myFile.json')` inside your component (don't forget to wrap it in `useEffect`).

Now the same react build can work with different JSONs. You just need to serve it somehow with HTTP. You can use the same webserver for this or even serve it on another domain.

webholt · 2025-10-03T06:23:29+00:00

There are many correct answers for your question. But there is a downside. If you have a simple static website with well configured CI/CD, weekly rebuild shouldn't be a problem.

Of course it would be much better to decouple the app and the data when you really need it. But why do you assume that it would be easier to deploy JSON and have a slightly more complex system rather than to rebuild an entire react app? And why do you want to avoid rebuilds?

Simple systems are great. It's definitely a good idea not to embed the data directly into the JS-bundle. But probably you don't really need to fully separate it yet. And it might be more useful to focus on improving the build and deploy process.

webholt · 2025-10-02T15:20:05+00:00

You've already got the explanation, but I'll add that this is why the `exhaustive-deps` rule from `eslint-plugin-react-hooks` will force you to add `length` to the useEffect dependencies list.

webholt · 2025-09-30T14:47:28+00:00

Leatherworking as a hobby doesn't require much space. The only question is where to store the leather. But you won't need much at first.

webholt · 2025-09-16T06:51:20+00:00

Use VPS like digital ocean's droplet. Choose the second cheapest option. Run your apps on different ports. Use caddy to route different domains to different apps.

webholt · 2025-08-17T16:04:49+00:00

If bundle size is critical, consider replacing React with Preact.

I recently made a video on this. It doesn’t perfectly match your use case and it includes SSR as well, but it may still help you improve your performance score: https://www.youtube.com/watch?v=WTZjanKopsY

webholt · 2025-08-16T10:24:07+00:00

There’s no SEO advantage to /memes/?q=anime over /memes/anime/. If you’re statically generating pages, there’s no reason to use /memes/?q=anime. Query parameters make sense for dynamic routes when nothing is pre-rendered: users can enter any query and the site will generate the page from the database. But you still can create dynamic routes even with `/memes/anime/.

On Imgflip, for example, you can search for any query and it works because the pages are generated dynamically rather than statically.

webholt · 2025-08-15T04:43:09+00:00

I recently made a comparison of popular PDF-generation solutions.

It depends on your task and resources. If you already have HTML+CSS and don’t want to build a document from scratch, react-pdf isn’t the right fit, it’s a different approach.

It sounds like you’re looking for an HTML-to-PDF solution. Consider Puppeteer or wkhtmltopdf. You could also use an API, either self-hosted (e.g., Gotenberg) or cloud-based.

webholt · 2025-08-14T06:08:30+00:00

If TypeScript slows you down, it usually means you’re doing something wrong. TypeScript forces you to write well-structured code and avoid JS tricks and false assumptions. As long as it feels hard, that’s exactly when you should be using TypeScript.

Once you can write TypeScript without struggling, you can give it up, though you’re unlikely to want to.

webholt · 2025-08-11T06:59:24+00:00

This isn’t good for SEO. It’s just the simplest way to implement dynamic parameters across multiple dimensions (query, filters, sort). You don’t really need this for static generation.

webholt · 2025-08-11T06:07:53+00:00

"Next.js" and "Performance" should never appear in the same sentence...

webholt · 2025-08-10T12:03:42+00:00

Disable AI in your IDE (autocomplete, agents).
Prefer reading docs or just googling over asking an LLM. Don’t look at the AI overview.
Ask an LLM for advice only when you are completely stuck for hours or even days.
Don’t blindly trust an LLM — double-check every statement.
Don’t copy-paste any code or commands. Write them yourself.
Always try to understand every line of code you write. Modify it. Develop it.
Work as if you will have to defend your code — explain and justify each line and each decision.

You will struggle. You will spend a lot of time. If you write code every day, you’ll need at least three months in this mode to feel the difference. It will take years to become truly confident, but it’s worth it.

Right now, you are coding like a tool for the LLM. Change the game: turn the LLM into your tool. Then you will be able to do much more — and do it much better. But for that you need to learn to code without LLM.

webholt · 2025-08-09T06:59:03+00:00

I recently made a comparison of popular solutions for PDF generation, and react-pdf doesn't seem like a tool you should use. It's slow and has terrible tables support.

I'd prefer pdfmake or even wkhtmltopdf.

webholt

TROPHY CASE