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

help-circle


  • This is giving me stress daymares about Spanish in high school.

    Still, it’s an interesting point you make.

    But then again, with definitive articles you have a bunch of things that are not supposed to convey gender conveying gender. Like a toaster… It would suck to have to remember the gender of a toaster, or, well toasters in general.




  • Great meme, and I’m sure op knows this, but for anyone else who is curious…

    007 in theory means:

    • 00: you have already committed your code to your local code base
    • 7: When you try to merge your code with everyone else’s there are 7 files that others have worked on since you last refreshed your local code base.

    To resolve this, you need to go file by file and compare your changes with the changes on the remote code. You need to keep the changes others have made and incorporate your own.

    You can use git diff file_name to see the differences.

    If you have made small changes, it’s easier to pull and force an overwrite of your local code and make changes again.

    However multiple people working on the same files is usually a sign of organizational issues with management. Ie, typically you don’t want multiple people working on the same files at the same time, to avoid stuff like this.

    If you’re not sure, ask someone that knows what they’re doing before you follow any advice on Lemmy.







  • erogenouswarzone@lemmy.mltoProgrammer Humor@lemmy.mlClassic John
    link
    fedilink
    English
    arrow-up
    6
    ·
    edit-2
    1 year ago

    Any mention of a server room reminds me of the fable of the guy, we’ll call him Mike, who unplugged the Internet.

    I can’t remember where I read it, I think it was greentext on Reddit years ago.

    So Mike is an intern, and due to some weird circumstances he becomes the only network admin in the building. Well, one day he doesn’t esnt feel like working, so on his way in, he stops by the server room and unplugs the internet.

    He then goes to his desk like a normal day. Then he starts getting phone calls. Everybody is freaking out because there is no Internet. So he begrudgingly descends into the server room and starts playing video games on his phone.

    Close to the end of the day, he plugs the Internet back in and ascends a hero to the employees because they think he’s been working hard all day to give them internet.



  • erogenouswarzone@lemmy.mltoProgrammer Humor@lemmy.mldo as i say...
    link
    fedilink
    English
    arrow-up
    0
    ·
    edit-2
    1 year ago

    Does anyone have any good advice on variable naming? Here’s some of my rules I try to live by:

    • camelCase
    • use prefixes
    • prefixes should be one word followed by an underscore.
    • 10 character limit or 3 word limit, not counting the prefix
    • functions should be prefixed with the file in which they’re defined, ie utils_FooBar
    • file names should be one word
    • Start Bools with is
    • Don’t use not in bool names.
      • This has farther-reaching implications that will keep you from making confusing code most of the time (I’m sure this will be controversial, but it works no matter what they say)
    • start output with _
    • Globals should be g_VARIABLENAME
    • use the least amount of words possible
    • but being too verbose can draw attention - use this to aide in readability
      • calc_ImportantValueThatWillDecideTheUsersView is better than calc_SumYears if the variable is more important than the others.
    • Even the greatest variable names are not replacements for documentation
    • Even the most readable code is not replacement for documentation.
      • Force yourself to love documentation.

    Edit: I realize I was speaking about function-naming with the prefix stuff.

    For variables, I still use prefixes, but for variable type. Even if you define the variables as types, it’s still incredibly useful. For instance,

    a string is s_MyName,

    enumerable is e_MyType,

    A number is int or double or whatever i_MyAge or d_MyWeight

    This might be obvious for custom objects, but I’d still do it like this p_Person or per_Person.

    Seriously it does make a huge difference




  • erogenouswarzone@lemmy.mltoProgrammer Humor@lemmy.mlWar Crimes
    link
    fedilink
    arrow-up
    35
    arrow-down
    1
    ·
    edit-2
    2 years ago

    It would be great to use some emojis in coding.

    Imagine how much more readable it would be if you could break a loop with 💀 or return true with 👍. Or use ❓for ifs, or ↔️ for switch (the emoji didn’t work for that one). Or use an emoji to represent a custom object?

    Maybe the ECMA should get on that!

    Edit: I guess you can use emojis for custom objects in js.

    Edit 2: ➡ for console.log


  • For real.

    I think the “real” programmers are scared because you can now do basically anything in js/ts, and they’re going to have to learn something they’ve always looked down on.

    With web assembly coming fast a lot of these people are going to start realizing it would be nice to have a cheaper, js-only developer on hand. Then mgmt is going to realize they can have more developers that aren’t total pains in the ass. And so long “real” programmers.

    Then, some day, I think js will be the only language - or something like js.


  • Yes, but only because it gives you a link to where that was run. Click the link to the right with filename:lineNumber, and it will open the sources tab to that line. Set a breakpoint and rerun to pause there, then step through the code’s execution.

    Of course, if you’re using minified or processed code, this will be more difficult, in that case figure out how to do it in VS Code.


  • Watch a Video or read something because it really is an invaluable tool. But here’s a crash course:

    Debuggers, or IDEs, let you step through your code in slo-mo so you can see what is happening.

    1. Set a breakpoint - Click to the left of a line of code so a red dot appears. Run your program, and the IDE will execute to that line, then pause.
    2. Look at variables’ values - While the execution is paused you can hover over variables before that line to see their value.
    3. Step through the code - See what happens next in slo-mo.
      • Use “Step Into” to enter into a function and see what that code does.
      • Use “Step Over” to not go into a function and continue in the current spot after the function has done its business.
      • Use “Step Out” to exit a function and pick up the execution after it has run. Use this when you’re in too deep and the code stops making sense.
    4. See whats in the heap - The heap will list all the functions that you’re currently inside of. You can jump to any of those points by clicking them.
    5. Set a watch - Keep a variable in the watch so you can see what its value is at all times.
    6. Set a condition on the breakpoint - If the breakpoint is inside a big loop, you can right-click on the red dot to create a conditional breakpoint, so you write something like x===3 and it will only pause when x is 3.

    There are many other things an IDE can do to help you, so def look into it more if you want to save yourself a lot of insanity. But this is a good starting point.

    If you’re developing for the web use F12 to open web tools, and when an error happens, click the file/line number to see that point in the Sources tab, and you can debug there.