Log in | Sign up

  • 1 Post
  • 32 Comments
Joined 2 years ago
cake
Cake day: January 22nd, 2024

help-circle







  • For me, it’s all about the maintenance now. If it encourages you to write messy code, you will come to loathe your codebase. If it gives you clean, easy to navigate code you will love it more and more.

    When I was a young programmer I couldn’t abide any boilerplate at all and loved clever magic that made it disappear. Now I don’t mind a bit of boilerplate and hate non-obvious machinery.

    When I was young I bought the promise that object oriented programming would solve the software complexity problem, but now I think that at best it’s neutral and sometimes it makes it worse.




  • All depends what your trade offs are. “Milliseconds of run time versus months of debugging.” I know one team that were died in the wool C programmers but their baby had one too many security issues and their CTO said they had to reimplement it all in rust. One of them resigned but the others spent ages on it. They hated the borrow checker with a passion, almost as much as they hated the CTO, but after a bit they admitted it had some benefits and in the end they have a love/hate relationship with it. They hate the process still, but they love the result. The Milliseconds vs months quote is from my friend on that team. He said one subsystem had a seriously massive speed boost because they turned off the logging they used to do to recover from some infrequent intermittent bug that simply doesn’t happen any more. They’re proud of what they did.



  • Are you sure about this? Do you have proof?

    When Google explains in their privacy policy that their Fonts API collects your browsing data, I believe them. Without proof.

    https://developers.google.com/fonts/faq/privacy

    When I embed Google Fonts in my website via the Google Fonts Web API, what data does Google receive from my website visitors?

    When end users visit a website that embeds Google Fonts, their browsers send HTTP requests to the Google Fonts Web API. The Google Fonts Web API serves the Google Fonts Cascading Style Sheets (CSS) and subsequently the font files specified in the CSS to the users. Such HTTP requests include
    (1) the IP address used by the respective user to access the Internet,
    (2) the requested URL on the Google server, and
    (3) HTTP headers including the user agent describing the website visitors’ Internet browser and operating system versions as well as the referer (i.e. the webpage on which the Google font is to be displayed).