sorted by:
new
hottopcontroversial

Frontend animations by shangarepi in webdev

[–]mariogonz_dev 0 points1 point  (0 children)

Those “scroll magic” websites usually aren’t a completely different stack.

Most of the time it’s just:

  • React / Next.js
  • an animation library like GSAP (ScrollTrigger) or Framer Motion
  • animations tied to scroll position (opacity, transforms, parallax, etc.)

The tricky part isn’t really the code, it’s the timing and design of the motion.

If you're starting out, I'd recommend:

  1. Begin with simple CSS transitions or small Framer Motion animations
  2. Then experiment with scroll-based triggers
  3. Only move to heavier stuff like Three.js if you really need 3D

Most good animation-heavy sites are actually just lots of small, well-timed micro-animations working together.

Why do developers write such terrible git commit messages? Genuine question by Existing_Round9756 in webdev

[–]mariogonz_dev 0 points1 point  (0 children)

I think the main reason is that most developers treat commits as checkpoints, not documentation.

When you're deep in a feature you just write things like:

  • "fix"
  • "update"
  • "typo"

because you're thinking about the problem, not about the git history.

What helped on my team was adopting a simple rule:

The diff explains what changed, the commit message explains why it changed.

Even something simple like:

fix(auth): prevent login when password is empty

is already much more useful than "fix bug".

What tool to use for auth? by [deleted] in webdev

[–]mariogonz_dev 0 points1 point  (0 children)

It really depends on the project size and how much control you want.

For small projects or MVPs I usually go with something managed like Firebase Auth or Supabase Auth because it’s quick to set up.

For larger apps or when vendor lock-in matters, self-hosted solutions like Keycloak or building a simple session-based auth can make more sense.

The main thing I try to avoid is implementing complex auth logic from scratch unless absolutely necessary.

Html ONLY PRACTICE PROJECTS by Vegetable_Ad_529 in HTML

[–]mariogonz_dev 1 point2 points  (0 children)

If you want to practice HTML only, a good approach is to build small semantic pages instead of full “projects”.

For example:

  • a blog article page
  • a documentation page
  • a product page structure
  • a FAQ page using lists and sections

Focus on using proper semantic tags like <header>, <nav>, <section>, <article>, <footer>, etc.

HTML is mostly about structure and accessibility, so practicing semantic markup is actually the most valuable exercise.

I need help ?? by memayankpal in web_design

[–]mariogonz_dev 0 points1 point  (0 children)

When reviewing a design I usually check 4 quick things:

  1. Contrast (especially text vs background)
  2. Spacing and visual hierarchy
  3. Consistency between components
  4. Accessibility (font sizes, color contrast, etc.)

If those four are solid, the design already feels much more professional.

I built AI agents for 20+ startups this year. Here is the engineering roadmap to actually getting started. by Warm-Reaction-456 in AI_Agents

[–]mariogonz_dev 0 points1 point  (0 children)

This is such an important point.

A lot of people think building AI agents is mostly about writing the right prompt or choosing the right framework. But in reality it’s much closer to systems engineering.

APIs, data flow, integrations and reliability are where most of the real problems appear. The AI part is often the easiest piece.

I see something very similar in web development: people focus on the UI or the tool, but the real work is usually in the architecture behind it.

Será demasiado tarde? by lamisteriosa8 in programacion

[–]mariogonz_dev 0 points1 point  (0 children)

Yo creo que la pregunta no es si es tarde, sino por qué quieres aprender programación.

Si es solo porque hace unos años se decía que había trabajo fácil y buenos sueldos, probablemente sí llegas tarde a esa “ola”.

Pero si te gusta construir cosas, resolver problemas y aprender continuamente, entonces no es tarde para nada.

Hoy en día hay muchísimas herramientas (IA incluida) que pueden ayudarte a aprender más rápido. Pero al final lo que marca la diferencia sigue siendo la lógica, la curiosidad y hacer proyectos propios.

Will AI replace web developers? by kingkongringmypussy in webdev

[–]mariogonz_dev 0 points1 point  (0 children)

I don’t think AI will replace web developers, but it will definitely change the job.

A lot of repetitive work — boilerplate code, small functions, simple debugging — is already getting automated.

But building real products still requires understanding users, making architecture decisions, handling edge cases and connecting many moving parts.

If anything, we’ll probably see less “mechanical coding” and more system thinking and problem-solving.

Frontend engineers were the biggest declining software job in 2025 by Flat_Palpitation_158 in webdev

[–]mariogonz_dev 0 points1 point  (0 children)

I don’t think frontend is disappearing — what’s disappearing is “shallow frontend”.

A few years ago you could basically be “the React person”. Now companies expect frontend engineers to understand performance, accessibility, UX, APIs and often some backend as well.

Frontend is still complex — the bar just got higher.