Meme Monday!
Today's cover image comes from last week's thread.
DEV is an inclusive space! Humor in poor taste will be downvoted by mods.
Meme Monday!
Today's cover image comes from last week's thread.
DEV is an inclusive space! Humor in poor taste will be downvoted by mods.
For further actions, you may consider blocking this person and/or reporting abuse
This is me π―
Haha, feel you on that one π
Sooo me π
"how to kill a daemon"
βDelete table from snowflakeβ
This is the best meme I've seen on DEV π
current status
Let's start with an awful AI-generated meme
Even the syntax is incorrect. That's an anonymous function (arrow function) symbol, not a greater-than or equal to >= symbol. π
Everyone who upvoted this will have their Official Developer Card revoked!
You are on double-secret probation!!
...faster than zig? Damn, that's a lot of confidence, considering the language isn't even as polished as it intends to be π€
Faster than nocode?
Assembly?
True tales of horror from my own youthful past:
Same as above, except with "DELETE"
... in client's production.
I'm better for it, but could have done without it.
Eh, itβs a rite of passageβ¦youβre not really a dev until you break something important at the worst possible timeβ¦
Or so Iβm toldβ¦ π
Rollback
"we didn't just delete the entire user accounts table on mainnet did we?"
"rollback"
"it's blockchain, there's no rollback - it's live on mainnet for everyone to see, forever."
Why is this one so accurate? π
Unit tests are the only tests I somewhat enjoy writing, at least when I have the option of using a sane language
Funny thing, I've also heard that "very clearly written/self-explanatory" quote from senior devs. Normally the ones you don't want to work with, you know, those who leave the company right after delivering their beautifully uncommented code for others to maintain.
Funny thing, some of the best code I have reviewed had no comments or other documentation.
It was just good code that was self-explanatory.
Some of the worst code I have reviewed had a ton of comments and documentation - it needed it, since it made no sense.
So as I am concerned good code > documentation.
I agree "Good Code > Documentation".
Unfortunately, the idea of "self-explanatory" varies from person to person, and especially, from experience level to experience level. What may be clear to one developer may not be so self-explanatory to another. You can have the most amazing, beautifully crafted, perfectly architected, self-explanatory code, but if the next person doesn't understand it... then it's not so amazing or self-explanatory anymore.
So why not extend that a bit: "Documented Good Code > Good Code > Documentation."
Self-explanatory is certainly different from person to person, that is true.
The code I was referring to was written the same way I'd have written it, minimal solutions, no extra fluff, no magic numbers, no magic behind the scenes stuff going on, no extraneous abstraction.
"Good code needs no documentation" sounds like cowboy style old school macho thinking - however, in my 20 years of experience, there is truth to it.
In SE classes, and code tutorials, documentation is often talked about as absolutely necessary and the gold standard of good practice - I have not seen this play out in reality or real life. Hardly anybody writes documentation, and when people do, it gets outdated in the next version since nobody thinks to update the docs either.Or auto-generated docs that have no substance.
I would say if you go write documentation then write examples on how to use the APIs or libraries - that's useful. I don't see it enough.
Don't spend time explaining what methods are doing - name them so they spell out what they're doing. Same with objects, variables. Save comments for the rare occasion something really obscure is happening - and know that the fact that something obscure is happening probably means your code is not good. When I find the need to write a comment on my code, so I can understand it a month from now, I always feel like it's a red flag - that code I wrote is probably not the best and simplest way to do it.
If you think about good code as being the documentation, then writing documentation on top of is is basically the same as duplicate code. It can get out of sync.
I bet the message is from the project manager.
Real coders use print statements
Teacher: Okay, class. This is a test. This should be easy for all of you. "11" + 1
Other Languages: 12!
Teacher: No!
Javascript: 111
Teacher Correct!