#ActuallyAutistic web dev. Does front of the front-end. Loves perf and minimalism. Prefers HTML, CSS, Web Standards over JS, UX over DX. Hates div disease.
I'll opt to not name any specific sofware and just say: pretty much all front-ends made by back-end developers.
Why? Well, nobody wants to use such software. It may work fast, it may have all the features and the best architecture ever, but if it is hard to understand, lacks proper usability, or worse yet, is advertized with programming tools first mindset even when the actual software product is what should matter, you end up only wasting time and resources of everyone.
Hire a designer and/or a front-end dev who can teach how to do front-end. Or have at least someone bite the bullet and really get into front-end. No, not full-stack. Pure user usability focused front-end. Really get that brain power to focus into it. At least I haven't found anyone who can be truly great in both front-end and back-end at the same time. Maybe some such unicorns exist, but they are so rare you can't really rely on finding one.
The worst thing about these pieces of software is that they've had lots of great thought put into them, but then treat everything else with bare minimum as far as thoughtfulness goes. They may focus on making the software "look pretty" but still miss the point of having an actually good usability. So much wasted potential.
And on the flip side, databases put together by front end Devs are normally a complete dogs-breakfast. Even if they manage to stick to a naming convention and get the 3rd normal form correct, there will be no indexes, referential integrity or correct data typing (String is not a data type!). And don't get me started on Collation...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I'll opt to not name any specific sofware and just say: pretty much all front-ends made by back-end developers.
Why? Well, nobody wants to use such software. It may work fast, it may have all the features and the best architecture ever, but if it is hard to understand, lacks proper usability, or worse yet, is advertized with programming tools first mindset even when the actual software product is what should matter, you end up only wasting time and resources of everyone.
Hire a designer and/or a front-end dev who can teach how to do front-end. Or have at least someone bite the bullet and really get into front-end. No, not full-stack. Pure user usability focused front-end. Really get that brain power to focus into it. At least I haven't found anyone who can be truly great in both front-end and back-end at the same time. Maybe some such unicorns exist, but they are so rare you can't really rely on finding one.
The worst thing about these pieces of software is that they've had lots of great thought put into them, but then treat everything else with bare minimum as far as thoughtfulness goes. They may focus on making the software "look pretty" but still miss the point of having an actually good usability. So much wasted potential.
And on the flip side, databases put together by front end Devs are normally a complete dogs-breakfast. Even if they manage to stick to a naming convention and get the 3rd normal form correct, there will be no indexes, referential integrity or correct data typing (String is not a data type!). And don't get me started on Collation...