401–410 of 414 posts
I wonder what’s the most polished or “sanded” UI out there? You would think FAANG would have a half decent UI and UX with the amount of money they have. But anybody that has used Amazon.com or AWS, GCP, or even Azure would beg to differ. Personally, off the top of my head. The most polished UI/UX has to be “mcmaster.com”. I can find anything I need in what seems like a couple minutes. Compare this to big box stores l…
This post demonstrates why I hate UI programming. The number of unpredictable, niggling little things that can go wrong exceeds my patience for dealing with them. I kind of enjoy thinking through the ways something might fail and writing tests to catch them, but aimlessly clicking around to see if anything breaks feels haphazard and annoying. Is UI construction inherently that complex, or have we just not found the r…
I'm always torn whether this is a good use of time or not. If you're an early stage startup, it feels like shipping features (that work) quickly is your biggest differentiator, not how nice your UI is. I guess this is true if you're doing something in a not so saturated field, but understand that if you're in a saturated space, you probably do need the design to be natural os as to set yourself apart.
Oh my god, just look at Facebook's comment system. It's a fucking mess and it's based on their fancy React steposhi soft.
Mind boggling that even their own engineers can't create a usable UI. Well, they are too big to care.
Alan Kay was right classifying most software engineering as pop culture. It's 2024 and we are still fiddling with spaces around radio buttons, a problem that should have been solved decades ago.
Spaces, yes.
This is so lost in Agile. Engineers should get the time to “sand” their products, but we just don’t. If QA doesn’t make a ticket for the space between, it’ll never get fixed. The customer probably notices this kind of a thing but it’s a miracle if the customer bothers to report it, and another miracle if it eventually turns into a ticket, and another miracle if someone prioritises it enough to spend time fixing it. […
The idea behind "agile" is to recognize when something isn't working and improve it. You obviously have a process that does not serve your customers' needs: work with your team to fix it. If you have SCRUM ceremonies, a retrospective is where you can raise it, but really, any time works (retrospectives are to purposely look at the past few weeks, but things you notice along the way, look to solve along the way).
Agile is a failure because it imagines this pixie dreamland where every replaceable cog in the machine somehow has the ability to dramatically change how the machine operates. We don't. We don't get to design the machine we are a part of because that's not how capitalism works.
Earlier quoted context omitted.
By all "software engineering" books' definition, Waterfall is a software/development process. Good or bad...
Which book describes "waterfall" as an actual process, as opposed to something generally slow and bad?
Earlier quoted context omitted.
> If things never bubble up, does that not mean that this is really a non-issue? It's a small issue, not a non-issue. Or some might even be big issues but for a minority of users. They're worth addressing from time to time because they add up. And yes, the app is probably getting the job done, which is all the more reason to start polishing the app and stop bloating it into something it was never meant to be. Focus o…
You obviously have something against contemporary growth-obsession, but I don't see a relation to agile. Do I need to point out that there are cases where you would have enough profit only to cover running the business (if that) and can't afford to stress over smaller issues? > Why would you make the gap clickable? I already said why: if everyone expects that behaviour (OP obviously did). Just like "sanding your UI"…
How is padding different? It's kind of in the definition of padding. Background colors and click regions are expected to fill the padding but not margins. It's the standard CSS box model.
Earlier quoted context omitted.
> Others were made for study at art academies in the late nineteenth century and later, while the statue has also been replicated for various commercial reasons or as artistic statements in their own right. Smaller replicas are often considered kitsch.[2] There you go. Many of them were commercial, not art. It does also say "artistic or statements in their own right" -- I'd like to know what statement they're trying…
I'm happy to be downvoted/flagged for this, but please kindly fuck off from gatekeeping art.
Earlier quoted context omitted.
You obviously have something against contemporary growth-obsession, but I don't see a relation to agile. Do I need to point out that there are cases where you would have enough profit only to cover running the business (if that) and can't afford to stress over smaller issues? > Why would you make the gap clickable? I already said why: if everyone expects that behaviour (OP obviously did). Just like "sanding your UI"…
I do have an issue with growth obsession, but I concede it's unrelated. If you only have enough resources to do some subset of tasks, you should of course prioritize what's best for your business. I happen to work for a company that's not running on fumes, so I think they can afford to do some more sanding. How is padding different? It's kind of in the definition of padding. Background colors and click regions are ex…
I was responding to you raising technical questions about how could gap work in some edge cases by saying: "same as padding".
If "gap" is always used like padding, why wouldn't it behave the same?
FTR, I am not sure it's used like that commonly (I've stopped doing CSS UIs before the flexbox came to be): I am not putting that out as a conditional by accident.
Earlier quoted context omitted.
may I refer you to Karl Marx? Communism is perfect, it's just been implemented wrong.
If somebody says “be agile; do A, B, and C for better software engineering” , and you do not A, not B, and not C then complain about how terrible agile is, the problem is not with agile. You did something different to agile and got different results, so why are you blaming agile for your own failure? It is, in fact, possible to implement agile wrong – by doing the exact opposite of agile. This is not a rhetorical tri…