• 0 Posts
  • 57 Comments
Joined 1 year ago
cake
Cake day: July 1st, 2023

help-circle

  • I was almost convinced they were keeping this broken on purpose, it’s been broken so long. Like, years long.

    It was broken so long I honestly wouldn’t have been surprised if news surfaced that Discord was taking back-handers from Microsoft under the table to keep it broken. With steam working so well on Linux now, broken discord streaming without actual working audio share was one of the last things that posed a hurdle for gamers ditching Windows.

    (In the meantime, thank you Vesktop for your service <3)




  • Another reason is brand identity.

    Using ‘.tech’ or ‘.flights’ or .sports’ for your site feels too “on the nose” and gives vibes of like browsing some directory where things are categorised and sorted. Even worse it implies there are other sites under the same category, and those other sites may be competitors, and this dilutes strength of brand.

    lt also suggests strongly what the business does, and while that might seem desirable at first it actually isn’t from a corporate perspective because it means the company becomes tied to their business area and can’t expand and grow out of it into other things.

    I think this is a major part of why descriptive TLDs continue to be less preferred over ‘meaningless’ two letter TLDs, because companies want the focus to be on the main part of the domain, not the TLD.





  • I had so many good times on forums back in the day.

    The personal nature of them was great for being social and making friends, but it was also good for the quality of the content for and user behaviour too.

    When everyone recognises you and remembers your past behaviour, people put effort into creating a good reputation for themselves and making quality posts. It’s like living in a small village versus living in a city.

    The thought of being banned back then genuinely filled people with dread, because even if you could evade it (which many people couldn’t as VPNs were barely a thing) you’d lose your whole post history and personal connection with people, and users did cherish those things.










  • Any company that hides their documentation has an awful product that they are actually embarrassed about, from a tech perspective. They are hiding it because they are afraid to show it.

    I’ve seen this so many times, and it’s a big red flag.

    These companies work on the basis of selling their product the old-fashioned way, directly to management with sales-people and business presentations and firm handshakes, and then once you’re sold then developers (which management doesn’t care about by the way) have to do the odious task of getting everything working against their terrible and illogical API. And when you need help implementing, then your single point of contact is one grumpy-ass old dev working in a basement somewhere (because they don’t care about their own devs either) and he’s terribly overstretched due to the number of other customers he’s also trying to help, because their implementation is so shitty.

    Conversely, public documentation is a great sign that companies took a developer-led approach to designing their solution, that it will be easy to implement, that they respect the devs within their own company, and they will also respect yours.

    When I am asked to evaluate potential solutions for a problem, Public docs is like the number one thing I care about! It’s just that significant.

    Side story - I once worked with one of these shitty vendors, and learned from a tech guy I’d made friends with that the whole company was basically out of office on a company-paid beach holiday - EXCEPT for the dev team. Management, sales, marketing, finance, they all got a company trip, but the tech peeps had to stay at home. Tells you everything you need to know about their management attitude towards tech.