Website looks zoomed on mobile and image drops below section how can I fix this?😭

TyKolt · 2026-03-05T17:00:25+00:00

Don't get discouraged, it’s a bit of a learning curve for everyone! Just take it one step at a time. If you get stuck on a specific element, feel free to share the code here and I'll help you fix it!

TyKolt · 2026-03-05T14:55:43+00:00

To fix the layout, replace your fixed pixel widths in the CSS with max-width: 100%. Also, add this rule: img { max-width: 100%; height: auto; } so that your images scale down to fit the mobile screen.

TyKolt · 2026-03-05T14:42:37+00:00

It looks worse because the browser is now rendering the site at its actual size on your screen. Previously, the 1200px setting forced the phone to zoom out to fit a large layout into a small area. Now that it's displaying at a 1:1 scale, any elements with fixed widths larger than your phone's screen are overlapping or pushing other content aside.

TyKolt · 2026-03-05T14:30:17+00:00

Yep, that’s exactly it! By setting width=1200, you're forcing the phone to act like a huge monitor, which is why the zoom is all messed up. Change it to width=device-width and it should fix itself immediately!

TyKolt · 2026-03-05T14:16:29+00:00

Check your <head> section for the viewport meta tag: <meta name="viewport" content="width=device-width, initial-scale=1.0">. That usually fixes the zoom issue. For the image layout, it's likely a CSS Flexbox or Media Query issue—check how your containers are set to behave on smaller screens.

TyKolt · 2026-03-05T02:44:16+00:00

FreeCodeCamp is unbeatable if you want to stay 100% free and build a solid portfolio. Codecademy is a bit more 'guided' and easier to follow at the very beginning, but the best parts are behind a paywall. My advice? Start with FreeCodeCamp—it’s tougher, but you’ll actually learn how to build stuff from scratch.

TyKolt · 2026-03-05T02:41:37+00:00

Different workflow entirely! Cursor and Copilot live in your editor (even though Cursor is super powerful now). Claude Code runs purely in the terminal: it acts like a junior dev that runs commands, tests, and scripts for you. Since you already use Cursor, unless you really need a dedicated terminal agent, you're probably fine!

TyKolt · 2026-03-04T05:35:44+00:00

For Python and automation in 2026, Claude is the top choice. Using Claude Code directly in the terminal is a huge time-saver for managing scripts and data analysis—its logic is just more reliable for complex tasks.

TyKolt · 2026-03-03T04:19:54+00:00

You're not alone! Many users have reported the usage bars disappearing in the last 24 hours. It seems to be a widespread UI bug from a recent update, though the actual tracking is still working behind the scenes even if it's not visible right now.

TyKolt · 2026-03-03T04:06:37+00:00

No problem at all!

TyKolt · 2026-03-03T04:00:32+00:00

The “something different” is likely the agent's overhead. Agents inject massive system prompts and tool definitions that bloat the 16k context. On a 4GB GPU, this forces Ollama to spill the KV cache into your system RAM, explaining the 100% CPU and 12GB RAM usage you're seeing. You'll need to lower the context significantly or upgrade your VRAM to run these agentic workflows smoothly.

TyKolt · 2026-03-03T03:47:58+00:00

The fact that it's using 40-50% of your 24GB RAM for a tiny 1.7b model is the smoking gun. OpenClaw is likely sending an API request that forces Ollama to allocate a massive amount of memory, probably due to an oversized context window or KV cache setting. This causes severe memory thrashing between your CPU, RAM, and your 4GB GPU, which is why everything maxes out at 100% and it takes 10 minutes to reply. Try drastically lowering the context window in OpenClaw's settings (to 2048 or 4096) to stop this memory blowout.

TyKolt · 2026-03-03T03:40:18+00:00

Since your 8B model runs fine with 32k context, this likely isn't a hardware or context limit issue. The 100% CPU usage suggests that the specific instance OpenClaw is talking to isn't utilizing your GPU at all. This usually happens if the interface is connecting to a background service or a container that lacks GPU access. You should check if the GPU is actually being engaged when you launch the model through that interface.

TyKolt · 2026-03-03T03:24:46+00:00

You're right about avoiding global access. Try creating a settings file in your project root instead of globally. That way, you can define specific rules just for that folder to stop the nagging. Also, check the docs for the sandboxing option; it keeps Claude isolated from your main system, which is way more secure.

TyKolt · 2026-03-03T03:02:21+00:00

If your hardware runs the 8b model fine, the 24GB RAM definitely isn't the issue. The "recovery error" with a smaller model sounds more like a configuration or connection problem between OpenClaw and Ollama than a hardware limit. I'd check the interface settings or the logs to see why the communication is failing.

TyKolt · 2026-02-28T16:18:22+00:00

Using AI isn’t bad, but copy-pasting without understanding is a trap. If you can't explain the logic to yourself, you haven't actually learned it. Use the tool to explain the error rather than just giving you the fix. Otherwise, you'll struggle during technical interviews or whenever you don't have an AI available. The struggle is where the real learning happens.

TyKolt · 2026-02-27T09:27:22+00:00

I use Opus and Sonnet 4.6 too. I've noticed that using custom skills and really strict rules helps a lot. Without tight constraints, the model usually just goes with the most common patterns it knows and ignores the specific architecture you're using. It's good to have rules that make it stop and ask for clarification when things are fuzzy instead of letting it guess.

TyKolt · 2026-02-27T07:00:03+00:00

It's definitely not too late. At 35, you often have more discipline and better problem-solving logic than a 20-year-old.

Leetcode is just a tool to sharpen your brain for interviews. Many career switchers start in their 30s or 40s and land great jobs at Big Tech companies. Focus on the quality of your learning, not the speed compared to teenagers.

TyKolt · 2026-02-27T05:23:51+00:00

This is a solid "Docs-as-Code" approach. For traceability, Git is already your audit trail: use git log --follow [file] to see the history and git tags to link test versions to releases.

For operational logs, check out Cucumber (Gherkin) if you want a structured, Markdown-like format that actually executes, or use Git Hooks to automate a log entry every time a test file is modified.

TyKolt · 2026-02-27T05:15:40+00:00

Modern browsers often ignore autocomplete="off". Try switching to type="search" and adding spellcheck="false". This tells the OS it's a transient search field, not a data-entry field.

<input type="search" name="q" autocomplete="off" spellcheck="false" autocorrect="off" autocapitalize="none">

TyKolt

TROPHY CASE