this post was submitted on 12 Sep 2023
17 points (100.0% liked)

Web Development

0 readers
1 users here now

Icon base by Delapouite under CC BY 3.0 with modifications to add a gradient

founded 1 year ago
MODERATORS
 

Hey guys! Sorry if this isn't the best place for this but I couldn't really find anywhere else.

I've been working for 6/7 years as a web developer full-time now, and I'm still plagued by one mega frustrating habit. When I'm working on something complex on one page, and it gets completed, I'll fairly often get notified either by the client or my boss a day or two later while they're testing the whole site that there's something broken on another page.

Almost always, it'll be down to the fix I've recently made.

Is there a way to avoid this kind of tunnel vision? I try to keep my code localised as much as possible, avoiding interacting with global scope and, if it's really for one specific thing, tying it down to that page in particular, but short of testing the entire site every time I make any change... is there anything else I can do?

Thanks!

you are viewing a single comment's thread
view the rest of the comments
[–] rayquetzalcoatl@feddit.uk 3 points 1 year ago

Those look great! I have thought about front-end testing before but was a little unsure of how to really implement it. I'll give this another look. Thanks!