Hasen Judy

@hasen_judy

Programming. Mastodon: @hasen_judy@mastodon.social

Tokyo, Japan
Vrijeme pridruživanja: ožujak 2018.

Tweetovi

Blokirali ste korisnika/cu @hasen_judy

Jeste li sigurni da želite vidjeti te tweetove? Time nećete deblokirati korisnika/cu @hasen_judy

  1. proslijedio/la je Tweet
    2. velj

    A new article, "Immediate Mode GUI Programming" motivates Gio's choice of the unusual immediate mode model and compares it with the traditional retained model.

    Poništi
  2. proslijedio/la je Tweet
    29. stu 2019.
    Odgovor korisniku/ci

    microservices are just dynamic linking over http.

    Poništi
  3. proslijedio/la je Tweet
    30. svi 2019.
    Poništi
  4. 17. sij

    So I watch just one DBZ video, and all of a sudden YouTube is recommending me TONs of DBZ videos. This machine learning based recommendation system really ticks me off.

    Poništi
  5. 7. sij

    A possible way to prevent this is to put some arbitrary limit on the compile time code execution, in terms of memory size or execution time or both. Chrome could also have prevent web bloat by for example rejecting any javascript code past some arbitrary limit, like say, 2MB.

    Prikaži ovu nit
    Poništi
  6. 7. sij

    A prediction that I can make based on this: When the Jai compiler is released, many people will abuse compile time code execution with crazy meta programming tricks that result in slow compile times and very difficult to understand code, like what they do with C++

    Prikaži ovu nit
    Poništi
  7. 7. sij

    A similar process explains why as hardware becomes better, software becomes worse. As browsers become faster, websites become slower and more bloated.

    Prikaži ovu nit
    Poništi
  8. proslijedio/la je Tweet
    5. sij

    The Future Self we become is the collection of habits whose benefits we emotionally experienced. Analytical goal-setting without having emotionally experienced the benefits of actions is unlikely to result in any action taken.

    Prikaži ovu nit
    Poništi
  9. 21. pro 2019.

    The app on Android doesn't work well half the time. That is, you open a video and then it just waiting forever and nothing happens!

    Poništi
  10. proslijedio/la je Tweet
    18. pro 2019.

    The fact that everyone thinks software needs so much maintenance (especially open source software) is a sign of how broken things are. If you are writing something solid, that does real work, why should it have to change like seasonal fashion? People still use LINPACK.

    Poništi
  11. 6. pro 2019.

    Swift's type inference is terrible. Some things _fail_ to compile because the compiler can't figure out the types of things. It doesn't just say "I can't infer types"; it says "types are wrong". If you create intermediary functions with explicit return types, it works.

    Poništi
  12. 18. stu 2019.

    Fixing typos and mistakes reported by the compiler may seem annoying at first, but it doesn't interrupt your flow so much. It's similar to "ask for forgiveness rather than permission". Write the code first, fix the typos later.

    Prikaži ovu nit
    Poništi
  13. 18. stu 2019.

    - Instead of relying on the text editor's autocomplete, rely on the compiler to tell you about errors after you've written the code. It's easier to get things done when you're just writing code fluidly than waiting on the IDE all the time.

    Prikaži ovu nit
    Poništi
  14. 18. stu 2019.

    This may sound like a trivial point, but I've started to notice that once I tried to teach myself to follow these habits, my ability to do things has been improving. - Come up with a predictable naming scheme so you don't forget what you name things

    Prikaži ovu nit
    Poništi
  15. 18. stu 2019.

    It's similar to relying on third party code. So many programmers are so used to relying on third party code that they can't imagine writing any significant non-trivial or non-glue code by themselves. They even consider it "bad practice" to even _attempt_ to do such a thing.

    Prikaži ovu nit
    Poništi
  16. 18. stu 2019.

    - They cannot remember what anything is actually called or which file it is defined in because they're used to autocomplete. - They cannot perform a refactoring that is not included in the IDE under the "Refactor" menu. (ok, they sort of can, but they consider a major feat).

    Prikaži ovu nit
    Poništi
  17. 18. stu 2019.

    Having this ability to do things without the assistance of the editor/IDE means you can do a lot of things that other people would normally be scared of. Many programmers are so reliant on the IDE that they _dread_ to do anything that the IDE does not help them with

    Prikaži ovu nit
    Poništi
  18. 18. stu 2019.

    He is not afraid of making large refactorings by hand. He would change what kind of parameters a function takes or what kind of fields a struct has, and then would go through all code that uses these functions / structs and modify them to match the new definition.

    Prikaži ovu nit
    Poništi
  19. 18. stu 2019.

    He doesn't write flawless code the first time around. He sometimes makes obvious mistakes (obvious for someone watching) but that is not an issue: these mistakes are found easily by just trying to compile or run the program and so they can be fixed quickly.

    Prikaži ovu nit
    Poništi
  20. 18. stu 2019.

    He can type code fluidly without constantly referring to manuals or deferring to the autocomplete of some editor/IDE. He does look things up, but not all the time; he can type large chunks of code as if he has a large chunk of structs/function names and parameters memorized.

    Prikaži ovu nit
    Poništi

Čini se da učitavanje traje već neko vrijeme.

Twitter je možda preopterećen ili ima kratkotrajnih poteškoća u radu. Pokušajte ponovno ili potražite dodatne informacije u odjeljku Status Twittera.

    Možda bi vam se svidjelo i ovo:

    ·