4 ms·

Idk, those two terms are as different to me as URL vs URI. Searching it will yield a long explanation about the differences, but IRL people will use them interc

Idk, those two terms are as different to me as URL vs URI. Searching it will yield a long explanation about the differences, but IRL people will use them interchangeably.

411111111111111 4y ago
It might seem that way to you, as a url is a subset of uri. I've never actually been in a company that has UX engineers though. It's usually UX or UX designers which work with figma or similar tools and delegate the coding to non-specific software/frontend engineers
- pcthrowaway 4y ago
  I think it's not a strict subset, there are URIs that aren't URLs (like ISBN numbers), but there are also URLs that aren't exactly URIs, like http://example-blog.com/latest http://example-blog.com/latest But in practice, sure, the 2 are pretty much used interchangeably edit: Perhaps I'm wrong, all resources I can find classify all URLs as a type of URI.
  - 411111111111111 4y ago
    Maybe my understanding of URIs is flawed then, but from your example it looks like an URI for blog articles sorted by publishing date. List<type> was a valid resource type as far as I remember.
sneak 4y ago
People do this a lot, but those of us who actually do the work instead of sit and talk in meetings about the work know that there is a huge difference between writing React components (UI) and designing flows in Figma (UX). It's just outsiders who say UI/UX as if they are the same thing.
- Retric 4y ago
  Yet I’ve seen people use the opposite definitions professionally. IMO it’s not the kind of thing that’s worth trying to get people to change.
- deleted 4y ago
  [deleted]
- hot_gril 4y ago
  I'm a backend SWE. How are those two roles not just UI designers and UI SWEs? Or frontend as our team would say. I get that "experience" suggests something grander than "interface," but that sounds like how I call myself a SWE just to sound better than programmer (which nobody calls themselves anymore, so there's no real difference). Maybe instead of backend we can say "cloud-end" cause "RESTful JSON API" lost its zing.
- deepsun 4y ago
  In our company: Writing React components -- frontend engineers (no "UI"). Designing flows -- UX (no separation on UXD/UXE, and they actually have to sit in meetings a lot, to figure out what users want and how others do it). And we use "UI" for folks in design industry: images, colors, fonts, look-and-feel, modern fashion, transition animations, etc. Maybe some nice interactivity that UX didn't care enough for.
hot_gril 4y ago
(Doesn't help that uri and url look very similar in printing)

Idk, those two terms are as different to me as URL vs URI. Searching it will yield a long explanation about the differences, but IRL people will use them interchangeably.

411111111111111 4y ago

It might seem that way to you, as a url is a subset of uri. I've never actually been in a company that has UX engineers though. It's usually UX or UX designers which work with figma or similar tools and delegate the coding to non-specific software/frontend engineers

pcthrowaway 4y ago
I think it's not a strict subset, there are URIs that aren't URLs (like ISBN numbers), but there are also URLs that aren't exactly URIs, like http://example-blog.com/latest http://example-blog.com/latest But in practice, sure, the 2 are pretty much used interchangeably edit: Perhaps I'm wrong, all resources I can find classify all URLs as a type of URI.
- 411111111111111 4y ago
  Maybe my understanding of URIs is flawed then, but from your example it looks like an URI for blog articles sorted by publishing date. List<type> was a valid resource type as far as I remember.

sneak 4y ago

People do this a lot, but those of us who actually do the work instead of sit and talk in meetings about the work know that there is a huge difference between writing React components (UI) and designing flows in Figma (UX). It's just outsiders who say UI/UX as if they are the same thing.

Retric 4y ago
Yet I’ve seen people use the opposite definitions professionally. IMO it’s not the kind of thing that’s worth trying to get people to change.
deleted 4y ago
[deleted]
hot_gril 4y ago
I'm a backend SWE. How are those two roles not just UI designers and UI SWEs? Or frontend as our team would say. I get that "experience" suggests something grander than "interface," but that sounds like how I call myself a SWE just to sound better than programmer (which nobody calls themselves anymore, so there's no real difference). Maybe instead of backend we can say "cloud-end" cause "RESTful JSON API" lost its zing.
deepsun 4y ago
In our company: Writing React components -- frontend engineers (no "UI"). Designing flows -- UX (no separation on UXD/UXE, and they actually have to sit in meetings a lot, to figure out what users want and how others do it). And we use "UI" for folks in design industry: images, colors, fonts, look-and-feel, modern fashion, transition animations, etc. Maybe some nice interactivity that UX didn't care enough for.

hot_gril 4y ago

(Doesn't help that uri and url look very similar in printing)