The one I hate? Your unit tests pass when run locally, and in your sandbox environment, and in dev, and in UAT, but prod? Fuck that, failing with reckless abandon.
That’s probably cause you or your packages use CoreJS. It’s basically a one man project that’s holding up the whole modern Internet infrastructure. You can look up the story online, but it was a pretty small donation request for a really relatable individual.
I guess this highly depends on package maintainers, Node already provides funding in package.json for much less invasive funding requests (and that can also be disabled) and you might also block executing the scripts during package instalation which are sometimes used for advertisement. I think this was a lot worse in days NPM didn’t support funding, especially for projects depending on a huge number of dependencies. But I’m not that old Node/JS dev to tell how things were back then in reality.
@alphacyberranger
This is why I have my VSCodium set to highlight all indentation levels in my settings.json
To see the editor indent guides, set "editor.guides.indentation": true and "editor.guides.highlightActiveIndentation": true.
editorIndentGuide.background: Color of the editor indentation guides.
editorIndentGuide.activeBackground: Color of the active editor indentation guide.
So back in the ‘70s I dabbled in programming (now called “coding”, I hear). I only did higher-level languages like Fortran, Cobol, IBM Basic, but a friend had a job (at age 13!) programming in assembler. Is assembler now called assembly, or are they different?
I thought that the assembler is a specific program that translates mnemonics into the corresponding machine code. Perhaps in early computing this was done by hand so a person was the assembler (and worked in assembler), but now that is handled by software (and supports various macros). So programming in assembly would generate a stream of text that must be assembled by an assembler. (Although I have heard people refer to programming in assembler as well, just not often.)
I hear people say “program in assembler” but IMO that’s wrong. I’d say you write the code in “assembly language” (or better yet, the actual architecture you’re using like “x86 assembly”) but you “assemble” it with an “assembler”. Kind of like how you could write a program in the “C language” and “compile” it with a “compiler”
A compiler and an assembler do wildly different things though. An assembler simply replaces mnemonics while a compiler transfers instructions to a whole other language.
Depends on the language, really… C maps pretty closely to assembly language, it’s not as simple as one mnemonic to one machine code byte, more like tokens get mapped to sequences of machine code, a function call translates to some code that sets up a stack frame, a return tears it down…
It’s still called programming, coding is the same thing. Assembler more commonly refers to the utility program that converts the assembly code to machine code while assembly refers to the code itself, but the term assembler code is also valid. It’s uncommon to simply call the code assembler because it would be easily confused with the utility program.
I was too young/poor to afford an assembler for my 6502 so I wore out the assembly long hand on a legal pad and then manually converted each operation to machine code.
Needless to say my programs done this way were exceptionally simple, but it’s interesting to understand the underlying code.
I’m a bit confused. I thought “build system” referred to systems like autotools, scons or cmake. How are they related to green checkmarks? Couldn’t one also get green checkmarks when using a build shell script or makefile?
So they were developing the game by sharing zips of their versions? OMG. There should be a tutorial of minimum Dev knowledge for wanna be new developers. They have very cool ideas, but the way they program…
For example Shadows of Doubt. Was running super bad last time I checked out. I think that too much accessibility to game Dev tools is lowering the quality of a lot of games (in resource hungry sense).
It is still in early access and optimising the game is their current goal according to the road map, though as the whole concept of the game is about simulating every NPC properly at all times it’s always going to be really heavy game to run.
And you are right about accessibility making resource hungry games more common - they allow indies to make projects and use concepts that would have been scrapped as technically non-viable by a publisher before. Shadows of Doubt started development back in 2015, which would have meant reducing the scope of the game until it ran on a PS4. Being indie, they could just do whatever instead, and now it’s going to be enough if they can make it run acceptably on a PS5.
When I interviewed junior devs for my team, I had zero theoretical questions, and only two coding questions which were basically code that had to be debugged, and once it was running, for them to implement some minor things that I asked them to implement. I said I don’t mind if they googled, I only wanted them to share their screens while they worked, so that I can see how they worked and how they googled/adapted the answers to their code. I interviewed over a dozen people ranging from freshers to 4 yoe, and you should see how terrible they were at googling. Out of all them, only one fresher came close to being good in the interview. Even ‘4 yoe’ devs who ‘spearheaded’ various projects sucked at basic python and googling.
As an IT person, hearing that someone has already restarted to try to fix it, gives me mixed feelings.
First, they might be lying. I’ve had it happen that people tell me they’ve done something when they have not. Restarting is usually an easy one to verify, just check the uptime of the system.
Second, maybe they did everything right, and actually restarted, that’s cool that they tried something before calling in. I appreciate that.
Third, if the second thing is true then, I’m now frustrated, because now I have to get dirty with whatever is happening since a reboot that should have fixed the problem, didn’t fix it. I know it’s not going to be an easy fix. Most of the time, I’m right, unfortunately.
I’m all for users trying stuff before calling in. But recognise that you don’t, and shouldn’t have access to some things. Sometimes that’s administrator rights, sometimes that’s a piece of software, sometimes it’s the ability to turn off the AV/firewall.
It can be a lot of things. If you’re not sure if what you’re trying won’t screw things up more than they already are, then don’t do it. If it’s something simple that you know how to do, go for it. If you happen to get it fixed, so much the better.
“Customer self resolved” is usually the fastest way to get a problem resolved. That’s good for you, for me, and good for everyone.
programmer_humor
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.