Hey, I just finished recordings for A11Y course on Udemy*/YouTube, comes with 61 CodeSandboxes, where you can just quickly click to jump into the problem.
https://github.com/Ditectrev/Awesome-A11Y-Book-Course-Web-Accessibility-A11Y

*If you like the content, DM me, I'll send a free link to the video version.

[ Removed by Reddit on account of violating the content policy. ]

Just curious how you guys do it because I've definitely been in a place where the client took advantage of certain things which were not mentioned.

Are you guys using any software or something?

Hey everyone, I am a developer and I have faced this problem many time which is even when i give ai proper context, the small changes can get annoying. move this text a little, make that image smaller, fix the spacing... sometimes it doesn't understand what i mean or does something different from what i wanted. then it's more explaining, more prompts, more tokens burned.
so i started building this. what if ai creates the website, and we just adjust the little things ourselves?
you click something on your website, move it, resize it, edit the text or change an image, and it saves that change directly into your code. no digging through files and tweaking margin and padding values just to see whether it looks right.
you can also preview desktop, tablet, and mobile together and see how things look across them. for supported changes, you choose whether to change only that screen size or apply it everywhere. so adjusting something on mobile doesn't have to mess up your desktop layout, it depends on what you choose.
right now it has:
- drag, resize, and text editing
- image and background changes, including uploads from your device
- movable device previews with canvas zoom
- controls for selecting a whole container or individual things inside it
- edit history and undo/redo
- HTML support, with experimental React and Next.js support
the video shows where it's at. it's still in the initial stage, and there's a lot to fix and refine, including expanding which edits can be made separately for each screen size.
honestly, idk if other people need this, but making the change i'm picturing instead of explaining it again feels useful to me.
would you use something like this? and should i open-source it so we can build it together, or would you rather just use it once it's more polished?
Also any ideas to add then feel free to say.

I'm tired of building complex filter UIs just for users to ignore them, type "shirt" into the search bar, get 400 results, and instantly bounce. our backend retrieval is actually really fast, but the human query formulation is awful.

Instead of writing 500 lines of custom debounced react filters to try and force them into categories, I'm looking at intercepting the keystrokes with an intent layer on the frontend. basically an ai-autocomplete that formats their vague text into a structured JSON payload before it ever hits the API.

Has anyone used frontend intent layers to fix vague search? looking at commandbar vs just dropping in a lighter ai-autocomplete hook.

Hey. Currently working on a DateRangePicker and need your opinions. Do you think the second-date-invalidity I show currently by making the second selection-cell red with an icon is good or do you think i should just mark all invalid fields as disabled after the first date is selected?

https://imgur.com/a/qCd7KQk

I have been reached out for the Frontend SWE l4 role at Google, can someone share with me what kind of questions to expect in the frontend interview also where to prepare it from, i have worked on frontend but I dont think i know it in depth specially now when most of the work is AI led, so any resources to prepare would be helpful. Also there is supposed to be 2 dsa rounds later afaik, does anyone know what level of questions to expect in that. Also how long do you think they provide to prepare for these, i dont want to take too long but i also dont want to be underprepared. I have searched alot regarding Frontend l4 interviews at Google but i didnt really find much data, so if anyone can help that would be great.

Feels like well over half my week now is reading through components and styles a model generated and deciding what to keep. Reviewing's a real skill, fine, but the tooling is rough, I'm scanning a wall of JSX and CSS trying to spot what changed, with no clean way to accept this chunk and throw out that one. Is anyone on a review loop that feels like a real diff for generated UI, or are you all just eyeballing the whole component every time?

Building Cashvelope was a massive personal challenge. I wanted a true envelope budgeting app that put data control back in the user's hands.

Working on this late at night after my main work hours meant dealing with severe burnout, redesigning local data structures three times, and fighting through backend edge cases solo. Building a app end-to-end alone is a completely different beast than writing code for a client.

To fellow devs who built and released your own side projects:

How do you balance feature scope creep with actually getting the app across the finish line?

hi! I didn't think I'll need that in my life, but I very need to know how to use CSS properly. I mean what are the differences between one thing and another, what's more popular to use etc. So, I'm trying to relearn CSS.

For the context: I learned CSS in 2022 only to pass the exams and that's all, and then I was like "yahoo! I won't return to the web design ever again!". So, I can use the atributes with classes, id etc, but I can't understand what are the important things to properly use them. I didn't think I'll need to program projects related to web programming. I find JS and PHP quite easily to understand, bcz every thing has one meaning there. It was a bit hard to understand HTML for the first time, bcz I thought every tag has its own function, but when I understood that plenty of tags are semantical and I can just use <div> and <span> if I want, I started to use the semantical tags properly. CSS is the hardest part in Front-End for me, bcz Idk if plenty of things are similar to the HTML ones(an atribute is optional and it depends on you if you want/need to use that) or the programming languages(1 thing = 1 meaning).

Here are my questions about CSS to understand it better:

1. which position is the best? Bcz usually I used "position: absolute";
2. why to use the coordinates(except for the z-index) if you have the margins?;
3. why a lot of web developers prefer to use the paths from a vector image instead of uploading the .svg file itself?;
4. what to use: the standard shadow or something like "filter: drop-shadow(10pt 10pt 6pt);"?;
5. I liked the grid, but I saw a lot of developers use flexbox. Is it important to choose one thing over another or is it something optional?;
6. are the CSS similar, but different atributes important only for the browsers?;
7. what's the point in making something like "p.name1 {}", when I could just create a new class?;

I hope I didn't forget anything, but if I did, I'll make a new post about them

Edit: I can't change the title, but I meant questionS*

we went from a small team to 20+ and release QA scaled worst. more devs shipping more Al-generated code meant more flows to re-verify before each release. it ate real hours. my weekends too. adding people didn't help. the verify work grew faster than the team.

we put the verify step inside the agent loop using testsprite CLI. the agent runs a real session against the live app. when something breaks it gets a failure bundle it can act on and rerun. cloud account was a mild pain to sort out. passing checks pile up into a suite that sticks around so coverage builds as we ship.

people still own the judgment calls and the fuzzy edge cases. moving the routine verify work into the loop stopped release QA from tracking headcount. how are other founders keeping QA cost flat while the team grows?

i’m working on a scraper for several sites and the current proxy pool gets flagged pretty quickly, looking for a residential setup with reliable ip rotation, what are you guys using for larger scraping projects?