251–258 of 258 posts
I expect most side-projects are being built with AI-assistance now. Side projects are typically time constrained - if AI saves you time, why wouldn't you use it? They're also the ideal place to try out new AI tools that your professional work might not let you experiment with. (The headline of this piece doesn't really do it justice - it misuses "vibe coded" and fails to communicate that the substance of the post is…
The problem is people want to use 2026 tools to write their code but they want to be judged by 2016 standards. In 2016, if I saw 10,000 lines of code, that carried a certain proof-of-work with it. They probably couldn't help but give the code some testing as they were working up to that point. We know there has to have been a certain amount of thought in it. They've been living with it for some months, guaranteed. In…
Nice list of design patterns, but imo a big unmentioned one is a grid of rounded rects https://correctarity.com/roundedrects (maybe what this post calls "Icon-topped feature card grid." ...that might be the official design pattern term)
I’m not sure we can tell what AI design looks like, Stitch and a number of other tools I’ve tried produce inconsistent, wild results. The common theme is that they’ll all look like Tailwind-style components if not given any other steering.
Earlier quoted context omitted.
Just chiming in to say I don't care at all about accessibility and I find it bewildering that every thread sharing some project has a comment like this.
> Just chiming in to say I don't care at all about accessibility See Rawls 'Original Position' on why you should care: https://en.wikipedia.org/wiki/Original_position
Earlier quoted context omitted.
If you have some good sources let me know, I'll turn it into a guide that Claude can read
I use the W3 preliminary guidelines - you could try adapting them into a bespoke skill as a good start. https://www.w3.org/WAI/test-evaluate/preliminary Another possibility (although I’ve never actually tried this myself) is an MCP server that someone built specifically to connect to Lighthouse, which includes accessibility testing as part of its benchmarks. https://github.com/priyankark/lighthouse-mcp
I use these tools myself and they just build upon the awesome work from the open source community
Earlier quoted context omitted.
I think accessibility is a really admirable thing and helpful to society (like ramps or parking). But stop shoving your wants on others when you can fix it on your own. Just write a chrome plugin using ai that adjusts css to set contrast ratio of your choice. Can even use a local llm to figure out replacement colors. Accessibility that can be had on client side should not be a concern on server side.
stop shoving your wants on others when you can fix it on your own. Just write a chrome plugin using ai that adjusts css to set contrast ratio of your choice. Can even use a local llm to figure out replacement colors. Stop shoving your wants on others when you can fix it yourself. Just get some concrete and some lumber, and build that wheelchair ramp. You can even hire a contractor to follow you around town all day bu…
By your logic, when med-science will provide ways to fix legs, instead of fixing people's legs, we should be building wheelchair ramp all over the world...
I clearly said accessibility is good but what can be fixed on/around the source, should not be burdened on the site. Wheelchair is a perfect example of that.
You don't provide a wheelchair per site per person.
Imagine Chrome having accessibility toggle that sets this text contrast to whatever you prefer with one click/pre-settings. Now suddenly every site is compliant to your need.
More of the design accessibility should be option in the browser instead of the sites. That helps everyone better.