• 0 Posts
  • 190 Comments
Joined 3 years ago
cake
Cake day: June 20th, 2023

help-circle

  • Deestan@lemmy.worldtoAsk Lemmy@lemmy.worldI want to go to study in Norway
    link
    fedilink
    arrow-up
    3
    arrow-down
    1
    ·
    edit-2
    3 hours ago

    Generally speaking, as long as you don’t push any National Pride, you will be included and treated as a normal human being by everyone (barring some absolute nutcases).

    E.g. at the University in Bergen, there are multiple long-time professors from countries that are or were heavily contentious and loudly hated as countries by large portions of the Norwegian populace at multiple times in the past 30 years: Russia, Turkiye (murdering kurds), China (don’t get me started), USA (horrific war crimes and torture camps), Israel (the usual), majority muslim countries (blamed for all terrorism in early 2000s). And of course immigrant or exchange students that are getting along fine.

    Some places may have problems of course, but in general you can feel confident that it will not be a problem.












  • Deestan@lemmy.worldtoTechnology@lemmy.worldSoftware as Fast Fashion
    link
    fedilink
    English
    arrow-up
    2
    arrow-down
    6
    ·
    6 days ago

    I don’t care whether it goes away. Neither have tapeworms, and while some people claim it helps with weight loss, most people are not up for it.

    The first usecase: One-off scripts. That is “do my homework for me” help. You can spend a minute reading the manual instead. Next time you do it, you can do it faster than through the LLM.

    The second usecase touches on something you might be bad at: abstractions and maintainability. We already had autocomplete. Autocompleting a block of code is a sign that you are not writing anything new and a signal to think about whether there is semantic duplication in the code that should be explored. Avoiding the annoyance of writing the block is you solving the wrong problem.


  • Deestan@lemmy.worldtoTechnology@lemmy.worldSoftware as Fast Fashion
    link
    fedilink
    English
    arrow-up
    15
    arrow-down
    4
    ·
    6 days ago

    I have yet to see a developer endorse LLM output in an area they are able to do useful work in.

    Either it is someone who thought the LLM helped them write unit tests, and it’s never tests that capture the intent of the code, because they don’t know that is important. They see tests as “this stuff I have to add for process reasons”.

    Or it is an LLM helping them write a fade-in tooltip with 200+ lines of React Javascript, because they don’t know this is a one-line CSS rule.

    Or have the LLM add code documentation that does nothing but repeat the function signature, because they don’t understand they need to empathize with the person using of maintaining the functions. Write something that helps jump a non-obvious gap, or write nothing.

    Or have the LLM do code review because they think it’s about obsessing over syntax, not about discussing how the change applies to the intent.

    Or have the LLM write their pull requests because they think it’s a boring process thing that summarizes the change, and not a discussion of the purpose, intent, cost, value and approach of the change.

    Moral: If you think LLM is good at X, it’s because you really really suck at X, and you need to get better at it instead of pumping out shit work faster while learning less.


  • Frameworks can be fine. Using them before understanding what you make is not. At that point you often see it is faster and better to just make the parts you needed yourself.

    Model as in you have a clear opinion on what your system does, why, how, and what it doesn’t do. A model evolves during development, which is where it becomes hard: You always need to make room for things you didn’t predict, so you need to adapt and refine the system model so that the change makes sense.

    Adding features until a full system explanation consists largely of “but”, “and also” or “except”, things like “and you should ask Bea about how that part works” or the worst of all “this part can be anything”, is the opposite of working from a model.


  • We’ve had a growing invisible divide in software for two decades now:

    A: People who jam in frameworks, copy examples online, and adopt “processes” and principles that bigger companies claim work for them, that only result in pulverizing responsibility, speed and understanding. They don’t expect to understand their tools. They fudge them until they stop giving off visible problems and wrap that up in “grown up words” by making ineffectual unit tests, make a PR, tagging it “bugfix: ticket #877”, sending it to review, debating some syntax, and spend the next two years debugging the system because of all the small things that go wrong because the thing they make don’t behave according to a clear mental model.

    B: People who don’t think knowing a single programming language counts as competence, and prefer making things according to a model (instead of copying someone else’s framework and contorting their own work to fit inside it)

    Group A are the reason shit sucks today, and they believe LLMs can code, because they themselves can barely code and just copy impressive looking convoluted shit from others anyway.