• 0 Posts
  • 90 Comments
Joined 3 years ago
cake
Cake day: July 5th, 2023

help-circle



  • if you want fast web pages there’s nothing faster than pure CSS and HTML. those are both running native machine code in the Web browser directly.

    JavaScript (with or without frameworks) gets slower the more things you do with it as it only works in a single event loop. this means one function you wrote that takes a long time blocks everything else from finishing until it completes, even the browser rendering and interactions. that’s why really bloated pages feel like they’re lagging and you can’t click buttons or scroll.

    imo do as much in CSS and HTML and use native web components for reusable components that you can drop anywhere in your HTML. if you want it to feel like an application, since you have backend experience you could use web assembly but treat this as a single application, it’s not really meant to replace html/JavaScript


  • i have what i call the ihop theory. when you feel this way go-to ihop and order off their lunch menu. everything about the experience will be horrible and you’ll feel terrible for having paid for it. literally the next meal you have will be the best thing you had in ages and you will value every bit of it.


  • it’s great if your commits are smaller and more focused. main issue is it can be harder to solve some diff issues as it requires solving merges at each commit being rebased. so if you have a large feature branch that can be challenging when it starts to diverge a lot (ex: bug fixes on main). though the argument then is more for keeping branches smaller and focused which is a better process imo.

    just beware it can be confusing for newer git users and when using shared branches can cause no ff commits.







  • the 1000x before bit has quite a few sideffects to it as well.

    • lesser used languages suffer because there’s not enough training data. this gets annoying quickly when it overrides your static tools and suggests nonsense.
    • larger training sets contain more vulnerabilities as most code is pretty terrible and may just be snippets that someone used once and threw away. owasp has a top 10 for a reason. take input validation for example, if I’m working on parsing a string there’s usually context such as is this trusted data or untrusted? if i don’t have that mental model where I’m thinking about the data i might see generated code and think it looks correct but in reality its extremely nefarious.






  • 🙂 Daily Quordle 1278
    7️⃣5️⃣
    4️⃣8️⃣
    m-w.com/games/quordle/
    ⬜🟩⬜🟨⬜ ⬜⬜🟨🟨⬜
    ⬜⬜⬜⬜🟨 ⬜🟩⬜🟨🟩
    ⬜🟨⬜⬜⬜ ⬜⬜🟨⬜🟨
    ⬜⬜⬜⬜⬜ ⬜🟩⬜⬜🟨
    ⬜⬜🟨⬜🟨 🟩🟩🟩🟩🟩
    🟨🟩🟨⬜🟩 ⬛⬛⬛⬛⬛
    🟩🟩🟩🟩🟩 ⬛⬛⬛⬛⬛
    
    ⬜⬜⬜⬜⬜ 🟩⬜⬜⬜⬜
    ⬜🟩🟨🟨⬜ ⬜⬜🟨⬜⬜
    🟩⬜🟨⬜🟨 ⬜⬜⬜⬜⬜
    🟩🟩🟩🟩🟩 ⬜⬜🟩🟩⬜
    ⬛⬛⬛⬛⬛ ⬜⬜⬜⬜⬜
    ⬛⬛⬛⬛⬛ ⬜⬜⬜⬜⬜
    ⬛⬛⬛⬛⬛ ⬜⬜⬜⬜⬜
    ⬛⬛⬛⬛⬛ 🟩🟩🟩🟩🟩