Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)N

nic2555

@ nic2555 @lemmy.world

Posts
0
Comments
6
Joined
3 yr. ago

  • AI Coding Is Massively Overhyped, Report Finds

    Jump

  • Maybe I should try it to understand, but to me, this kind of feel like it would produce code that would not follow the company standards, code that will be harder to debug since the dev have little to no idea on how it work and code that is overall of less quality than the code produce by a dev that doesn't use AI.

    And I would not trust those unit tests, since how can you be sure if they test the correct thing, if you never made them fail in the first place. A unit test that passes right away is not a test you should rely on.

    Don't take it the wrong way, but if Claude write all of your code, doesn't that make you more of a product owner than a dev ?

  • Windows 11 Escalation Vulnerability Let Attackers Gain Admin Access Within 300 Milliseconds

    Jump

  • If only there was some kind of database where we could reference the most common vulnerability and exposure incidents, such as this one, and then ranked them based on their criticality, for everyone to be well informed.

  • Was the first too coincidentally

    Jump

  • You're right, that's a 2009-2013 Dodge avenger.

  • Study Finds Consumers Are Actively Turned Off by Products That Use AI

    Jump

  • Yes. But not all Machine Learning (ML) is LLM. Machine learning refer to the general uses of neural networks while Large Language Models (LLM) refer more to the ability for an application, or a bot, to understand natural language and deduct context from it, and act accordingly.

    ML in general as a much more usages than only power LLM.

  • Tests are code too

    Jump

  • TDD doesn't imply that you write all the tests first. It just mean you have to write a test before you write a line of production code.

    The idea is to ask yourself "what is the first step I need, where am I going to begin?". You then write a test that validate this first step and fail. Then you write the code to make it pass. Once your done with that, you ask yourself: "what's the next step? ". You, then, repeat the process for that step.

    This is a process you are going to do anyway. Might as well take the time to write some test along with it.