• GreenKnight23@lemmy.world
    link
    fedilink
    arrow-up
    17
    ·
    16 hours ago

    I worked with some pretty dumb people who mocked me for years as the guy who couldn’t design a UI to save my life because the product I inherited was designed by someone in the 1990s. it wasn’t pretty but it was functional.

    any time a UI request came in for the new product and I would try to take it, the PM would pull it and give it to someone else. “oh, their skillset is better suited for UI/UX.” I was told.

    I got fed up with it and designed my online portfolio. used it to showcase my work and skills even documented my process from mockups to design iteration and final products.

    I then posted on linkedin my new portfolio and listed myself as open to connect. within a day the PM made a point to pull up my portfolio on standup and asked me where I got the template. told them, “no template. as you can see in the documentation I designed it from scratch using HTML5 CSS3 and JavaScript. I also included the js packages I used.”

    they were stunned and immediately started to shuffle some UI tickets my way. I just said, “sorry, my skillset is better served for backend requests.”

    I quit two months later after a few interviews that seemed to go well. I hated that shithole.

    moral of the story? don’t discourage people from taking on tasks they aren’t obviously suited for. they might just surprise you.

    • squaresinger@lemmy.world
      link
      fedilink
      arrow-up
      4
      ·
      5 hours ago

      I agree with your final take, but why would you want to take frontend tickets if you can also do backend work?

      • GreenKnight23@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        3 hours ago

        change of pace, mostly. I also like the challenge. when I’m not challenged at work I lose interest easily and can spiral into not doing my job. so it’s nice to break up a long running project with some new bugs or tasks that are unrelated.

      • TeddE@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        5 hours ago

        Raw spite. If you’re upset enough to build a whole LinkedIn profile, you’ve already mentally moved on to the next company.

    • I Cast Fist@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      4 hours ago

      Ugh, i’ve had to write some Selenium tests where I had to come up with weird ass Xpaths because not a single fucking element had an ID and over half would spawn something in a different div

  • magic_lobster_party@fedia.io
    link
    fedilink
    arrow-up
    23
    arrow-down
    6
    ·
    1 day ago

    JavaScript frameworks are invented because pure HTML and CSS suck for dynamically loaded pages, and vanilla JavaScript suck in general.

    • TrickDacy@lemmy.world
      link
      fedilink
      arrow-up
      12
      arrow-down
      1
      ·
      1 day ago

      JavaScript frameworks actually exist for two reasons, one, vanilla JavaScript lacks ease of use (does not suck and I don’t care who disagrees) and two, people love over engineering the fuck out of technology. See: technology since the iPhone came out. We have advanced systems around the world spinning up processes to make up for the fact that touch screens are hard to type accurately on.

      • magic_lobster_party@fedia.io
        link
        fedilink
        arrow-up
        9
        ·
        1 day ago

        jQuery got popular because Internet Explorer, Firefox, Chrome and other browsers weren’t exactly cross compatible. Writing vanilla JS was risky business in that sense.

        It also supported AJAX across all major browsers, which meant the website could make API requests without reloading the entire page. It was super revolutionary to press a button and it only changed a part of the page.

        Then Angular and React took it a step forward and that’s where we are now.

        • TrickDacy@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          1 day ago

          I am very aware of the progression. But you’re vastly glossing over how much complexity (and feature set) was added after jQuery. If JavaScript sucks, how would you change it? Shitty browsers implementing it poorly in the past (and safari doing so today) doesn’t make it suck.

        • TrickDacy@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          20 hours ago

          Unless those are mostly overly complicated, it doesn’t speak to what I’m saying. But I guess it means people like doing their own engineering better than relying on others

      • Nat (she/they)@lemmy.blahaj.zone
        link
        fedilink
        arrow-up
        1
        ·
        1 day ago

        Immediate mode rendering and components seem to be why people use them. And you know what? The web should natively support those but doesn’t (well it kinda bad components, but ehhh). Otherwise I agree, the frameworks are overcomplicated.

    • Biyoo@lemmy.blahaj.zone
      link
      fedilink
      arrow-up
      2
      ·
      11 hours ago

      On mobile the header has overlapping content- not the worst but shows very little attention to detail for a CSS toolkit :(

  • yetAnotherUser@lemmy.ca
    link
    fedilink
    arrow-up
    12
    ·
    1 day ago

    OP, I don’t think you’ve correctly linked to the post (when I visit the linked webpage, the browser tries to download an ActivityPub activity instead of showing the post in the Mastodon web UI). Please replace the link with this one.