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

help-circle


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










  • Google absolutely made a calculated decision when they decided to allow device manufacturers to fork AOSP and introduce closed-source modifications. If it wasn’t for that, I can’t imagine OEMs would have wanted to get on board, and so we wouldn’t have seen the huge adoption that happened, and Android might have become just another failed operating system.

    I do truly wish for a fully open-source “Linux on the phone” type experience, but what always kills that is apps, because companies just don’t make them unless the market share is there. Even Microsoft had to pull out after pumping so much money into Windows phone, and I think most of the reason was because they couldn’t incentivise developers to make apps enough.

    So I’m glad at least I can run Calyx, and have just a tiny bit more freedom while still keeping the apps I need, even if it’s nowhere near perfect.



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




  • The fade should be slow and subtle. At first the client thinks they are just imagining it, but then they start getting customer support calls about the site being faded, and their bosses are pointing it out too in meetings, and as it happens more and more the panic really begins to set in.

    Finally they reach out to you in a desperation when there’s barely anything left of the site and ask you to urgently fix the problem, and you just shrug your shoulders sympathetically and explain it’s happening because they haven’t paid - but not like in a way that suggests you are doing it on purpose, but a way where it’s simply an unavoidable natural consequence, like if you didn’t pay your electricity bill your power would get cut and the site is slowly “dying” and fading away because of that.

    They’d pay so fast.


  • I’m sure there’s nothing wrong with the program at all =)

    Modern webapp deployment approach is typically to have an automated continuous build and deployment pipeline triggered from source control, which deploys into a staging environment for testing, and then promotes the same precise tested artifacts to production. Probably all in the cloud too.

    Compared to that, manually FTPing the files up to the server seems ridiculously antiquated, to the extent that newbies in the biz can’t even believe we ever did it that way. But it’s genuinely what we were all doing not so long ago.