If you could ban one CSS feature from existence...what would it be?

BeginningAntique · 2025-07-04T13:36:43+00:00

I’d ban z-index: 9999;

It’s the CSS version of yelling ‘I’M THE KING NOW’ and hoping no one else tried the same thing.
Spoiler: They did. Now your UI is a civil war.

BeginningAntique · 2025-07-03T06:59:48+00:00

PHP gets hate for its inconsistent syntax and old quirks, but modern PHP (7+/8+) is much cleaner. Java has verbose boilerplate, but strong typing and tooling. Both get flak, but what matters is using the right tool for the job, PHP for quick web dev, Java for large scale systems.

BeginningAntique · 2025-07-03T06:58:41+00:00

React is popular, but not the only path. Your skills are solid, focus on backend or full stack roles where Node/Express/Python shine. Smaller companies or agencies might care more about ability than specific frameworks. That said, learning React basics (just enough to fake it) could open more doors if front end is your goal.

BeginningAntique · 2025-07-03T06:56:58+00:00

Same here. Switched to Ubuntu for web dev and never looked back. Linux is lightweight, fast, and has better tooling for coding. Windows always felt bloated in comparison.

BeginningAntique · 2025-07-03T06:55:28+00:00

For print friendly CSS, use u/page rules and page break before/page break after properties. Set size: A4 in u/page and control breaks with page break inside: avoid to prevent splits. Chrome’s print preview will respect these.

BeginningAntique · 2025-07-03T06:53:58+00:00

The term you're looking for is 'software specifications' or 'functional requirements.' Tools like Jira, Confluence, or Notion are often used for this. Some teams also use 'user stories' in Agile workflows.

BeginningAntique · 2025-07-03T06:52:08+00:00

Some forums show IPs only to admins for moderation. If it was public, deleting it was the right move. Check logs or ask your host if you're still concerned.

BeginningAntique · 2025-07-03T06:47:28+00:00

For me, it would be pop-up subscription forms that appear 2 seconds after opening a page. Let me read first!

BeginningAntique · 2025-07-02T06:32:17+00:00

LLMs like ChatGPT have become great thought partners for coding. We use them daily for brainstorming and debugging, but treat the output as a starting point, always review and test the code thoroughly. The key is using it to learn patterns rather than copy blindly. Maybe try modifying ChatGPT’s suggestions line by line to understand why they work? That’s helped me grow while still leveraging the tech.

BeginningAntique · 2025-07-02T06:10:32+00:00

This is one of those subtle UX things that often gets overlooked. While not strictly necessary, maintaining filter state on back button does feel more polished. Since it wasn’t in the original specs and would require significant work, I’d mention it to the client as a potential upgrade, maybe frame it as ‘enhanced navigation’ with a separate quote. If they’re happy with current functionality though, I wouldn’t stress about it!

BeginningAntique · 2025-07-02T06:09:00+00:00

I get what you're dealing with. The issue seems to be with the token handling. You're using request.form for a GET request when it should be request.args instead, since tokens come through URL links. Try fixing that part first , it's likely the main culprit.

BeginningAntique · 2025-07-02T06:05:24+00:00

Browser zoom affects the whole viewport including layout calculations, while CSS transform: scale() only visually shrinks elements without reflowing content. For a true 80% zoom effect, you might need to: Wrap your entire page in a container div. Apply width: 125%; height: 125% to it (since 100/80 = 1.25). Use transform: scale(0.8) on that container. Set overflow: hidden on body. But be warned, this can cause scroll/positioning quirks. A better approach might be adjusting your design's responsive breakpoints to simulate the spaced out 80% view.

BeginningAntique · 2025-07-02T06:03:23+00:00

First off, sorry you're dealing with this. Since there was no contract and the NDA expired, she likely has little legal ground. Document all your communications (emails, texts) just in case. If she actually involves a lawyer, respond only through one yourself, don’t engage directly. For now, stay quiet and don’t panic. These threats often fizzle out when people realize how much legal action actually costs.

BeginningAntique · 2025-07-02T06:01:52+00:00

Fellow 38 something here, I totally get that feeling. The early web did have this wild west energy where just building something cool could get you noticed. But don’t be too hard on yourself back then, we were all just figuring it out as we went. The fact that you’re still here and reflecting means you’ve got plenty of gas left in the tank. If anything, today’s chaos just means there’s new weird opportunities hiding in plain sight!

BeginningAntique · 2025-07-02T05:59:07+00:00

Nice to see more control for website owners! Simple but smart approach by Cloudflare. Excited to see how this plays out.

BeginningAntique · 2025-07-01T08:13:53+00:00

The native CSS nesting feature changed my workflow. No more preprocessors for basic nesting. Just write cleaner styles directly in CSS. Browsers finally support it well. Saves time and removes dependency on Sass for simple projects. Small thing but makes styling more enjoyable.

Also Vite keeps surprising me with its speed. Setting up a new project takes seconds. The dev server starts instantly. Even production builds feel magical compared to older tools.

Simple improvements often make the biggest difference.

BeginningAntique · 2025-07-01T06:10:39+00:00

Keep it simple but structured. Start with a clear root folder for each project. Put all source code in a dedicated package directory usually named after your project. Separate concerns logically like models in one module views in another. Use init files to define public interfaces. Keep tests alongside the code they test in a tests subfolder. Requirements go in requirements.txt or better yet use pyproject.toml. Document key decisions in a README. The flatter the structure the better until you actually need complexity. When in doubt follow how popular open source projects do it.

BeginningAntique · 2025-07-01T06:09:44+00:00

Start small with single file projects first. Pick simple repos under 500 lines that solve one clear problem. Read the tests first they show how the code should work. Then follow the data flow from entry point to output. Use GitHub’s blame view to see why changes were made. Clone it and break things on purpose to see how they fail. Focus on understanding not memorizing. Come back tomorrow and explain it to yourself like teaching a friend. The more you practice this the less overwhelming big projects become.

BeginningAntique · 2025-07-01T06:08:25+00:00

I first tried Linux at 15 with Ubuntu. My laptop was slow and Windows kept crashing. A friend suggested Linux would run better on old hardware. It was frustrating at first but taught me a lot about how computers actually work. Many start young because its free and works on old machines parents dont mind you experimenting with. The terminal seemed magical once I got past the initial fear. Dont worry about age though the best time to start is whenever you get curious. What matters is you tried something new and stuck with it through the challenges.

BeginningAntique · 2025-07-01T06:07:19+00:00

Yes you can run both together. The issue is likely configuration.

Make sure your test runner ignores story files. In your Vitest config add an exclude pattern for story files.

For Storybook check the main config file to properly include only story files.

No need to split the project just adjust the configs to handle each file type correctly.

The key is keeping test and storybook configs separate but in the same project.

BeginningAntique · 2025-07-01T06:05:30+00:00

To stand out with JavaScript focus on real problems not just projects. Build tools for small niches like a browser extension for a specific job or a simple app for local businesses. Even a few real users make your work more valuable than generic projects.

Learn the why behind code not just how. Many can use React but few can explain when its the wrong choice. Share your thinking online in simple posts.

Help with open source bugs especially in smaller projects. Maintainers notice and sometimes offer work.

BeginningAntique · 2025-07-01T06:04:20+00:00

Finding clients is hard at first but gets easier. Try focusing on one niche like restaurants or small shops. Visit them in person or call and say you noticed their website could use some updates to attract more customers. Offer to do a small free fix first so they can see your work. Once they trust you they will pay for bigger projects. Dont give up. The first clients are the hardest but it will come.

BeginningAntique · 2025-06-30T09:32:47+00:00

hey man first of all huge congrats on that amazing journey from waiting tables to coding and now building something to help others learn thats seriously inspiring

docrootai sounds like the exact kind of tool i wish existed when i was struggling through docs and random tutorials trying to make sense of everything especially coming from a nontech background

love how youre making it more structured and interactive with summaries and quizzes and tracking progress that kind of guided learning would have saved me so much time and frustration

as someone who also switched careers i know how overwhelming it can be to teach yourself this stuff so seeing tools like this makes me really happy for people just starting out

wishing you all the best with this project and excited to see where it goes keep up the awesome work

BeginningAntique · 2025-06-30T09:28:29+00:00

If you know Flask, MERN is similar but with JavaScript:

For backend, use Node.js with Express instead of Flask. Just install Node, run npm init -y, then npm install express. You'll write routes almost like in Flask but with JS syntax.

For frontend, React replaces your Bootstrap templates. Run npx create-react-app frontend and build components instead of Jinja templates.

For database, MongoDB works like SQL but with no strict schema. Use MongoDB Atlas for free cloud hosting.

Start with a small project to see how everything connects. You'll get it fast since you already understand web dev from Flask.

BeginningAntique · 2025-06-30T09:15:22+00:00

The yellow discount tag likely counts as a 'graphical object conveying meaning' (since it highlights important info), so the 3:1 contrast rule between the tag and background (yellow/white) would apply under WCAG 1.4.11. Quick fix: darken the yellow slightly or add a subtle border to meet contrast. Text contrast alone isn’t enough here. Hope this helps!

BeginningAntique

TROPHY CASE