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

help-circle


  • 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.









  • This is great, honestly.

    If you go back to antiquity, education was about philosophy. It was about learning how to observe, and think critically, and see the world for what it is.

    And then in modern times, education became about memorisation - learning facts and figures and how to do this and that. And that way of teaching and learning just doesn’t fit any longer with what our digital age has become.

    In my opinion, we are heavily overdue for a revamp of what education should be, and what skills are most important to society in this post-truth world. Critical thinking is an important foundation to real knowledge that we don’t teach enough.



  • It’s such a painful thing, and the scary truth is that it can happen to anyone.

    I’m sure we’ve all experienced instances of this, in some smaller and insignificant way.

    You take a packed lunch to work. Every day for five years you’ve taken a lunch to work, without fail. Its part of your routine, you don’t even have to think about it. Get your wallet, get your keys, lunch out the fridge and into your bag, out the door.

    Then one day you open your bag at lunch-time, and it’s not there. Why isn’t it there, you think? You remember putting it there like always, but then the memories of different days are all the same as each other, and it just blurs into one.

    And then you remember. Just as you picked up your wallet and keys, your phone rang. And it’s your Dad, who says he just had someone call to say he needs to transfer money to keep it safe, and you’re telling him no no no Dad it’s just a scam, don’t transfer anything! And you have to go or you’ll miss the bus, and did I get my lunch, yes yes I put it in my bag like always.

    But you didn’t put it in your bag. Its still sitting in the fridge at home.

    And obviously a lunch is not a baby. But the principle is the same. That frightening realisation that your own brain didn’t merely forget, but actually lied to you about what really happened that morning is the same.

    And it could have been a baby instead.

    Scary.





  • 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.