• 0 Posts
  • 78 Comments
Joined 1 year ago
Cake day: August 16th, 2023
  • Fades@lemmy.worldtoProgramming@programming.dev•Julia Evans' Git cheat sheet
    68·
    6 days ago

    GUI users = low skill ✅

    Majority GUI a weak subset and of little use ✅

    Elitism ✅

    Of course, this is all couched in “use what you like”, and top it off with a general sentiment of how this post is all but useless.

    If someone has to ask you for your git fu help the problem isn’t GUI use it’s the incompetence and/or inability to solve it yourself. Implying a strong correlation of the two is where I take issue.

    My personal experience? A built in GUI saves you so much time like the one in JetBrains IntelliJ, if I need something more use case oriented that is more than the core fn (intelliJ’s does not simply include fetch/push/pull, but much more including everything in the graphic) then I click terminal tab and do what I need. Similarly the git tree provides an immediate view and context of the branches, changes, tags etc.

    It’s almost like filtering people into GUI and CLI boxes doesn’t really work.

  • Fades@lemmy.worldtoProgramming@programming.dev•80% of programmers are NOT happy… why? - YouTube
    39·
    2 months ago

    Yeah absolutely.

    I would go a step further and point to how a lot of companies these days supplement their workforce with low skill contractors from places like India who are like 13 hours ahead, do not have any actual investment/commitment to the project/company.

    Why pay high prices for competent developers that can work alongside each other when you can have a just few competent ones and outsource the rest for those competent workers to corral, right? 🙄

    Generally this results in more work for the full time devs. When you ask for senior developers and get a team of ”seniors” that write code like juniors…. That’s just more work for the full time devs. Ask me how I know.

    Maybe I just need to stop working for Fortune 500s

  • Fades@lemmy.worldtoProgrammer Humor@programming.dev•Always try sudo
    3·
    3 months ago

    Yes absolutely, the parameter even if not in a strongly typed language should be a specific number and the unit should be implied. Overload the method to support different units if necessary or provide a unit as an additional parameter instead of forcing the method to parse the string for any unit type hints that may or may not be there

  • Fades@lemmy.worldtoProgrammer Humor@programming.dev•They did not reply.
    1·
    3 months ago

    I can accept your second point, but in your PR I would absolutely request you to rename the method to isYoung, and then in making said comment I would then ask… what value isYoung providing, and where is the line between young and !young ultimately for trying to get the dev to reevaluate the design. It’s hyper specific in an obtuse manner and I think it hints at design flaws especially with the perspective of product evolution