He revealed the secrets !
He revealed the secrets !
He revealed the secrets !
Framing libraries as cheat sheets is hilarious
It's kinda fun to think of programming as magic.
And "libraries" as grimoires/tomes .
It's surprising how far you can go with the analogy.
My best comment ever in Reddit was describing Lord of the Rings as programming.
Some time ago:
Some other day:
Told ya.
I've never found a problem that can't be exacerbated with Microsoft Access.
Hmm, is this a new take on the "Stop Doing Math" meme?
"She". The gag of SwiftOnSecurity is it's Taylor Swift, posting infosec. Tho these days she mostly trolls like this.
Is it actually Taylor Swift?
Of course, do you think people just go on the internet and tell lies?
Yes. If you think that's cool, just wait until you meet @MargotRobbie@lemm.ee
Yes. On the matter security.
Me: Spends 4 hours making a pause menu... "I wish this was true... This man has not met the hell of a 50 state, 100 elif statement..."
Amateur Coders code: " We don't do this because its easy, we do this because we thought it would be easy"
We do what we can, because we must!
It's like if farmers were just letting plants do all the work, instead of manually assembling the potatoes themselves
It's like the joke about the invoice charging 0.10$ for a screw and 100$ for knowing which screw to replace.
Coding is easy. Software engineering not so much.
I love SwiftOnSecurity.
LLMs will replace the programmers right before they replace the satarists.
The job of a programmer is to reintroduce a bug that was fixed in the last patch.
Merge needs some stomp, yeah, mine stomp yours.
edit: note, this is a good thing, cause then we both have unlimited supply of tickets.
The biggest scam about programmers is they barely program
He's got a point, though, the further you go, the less time you spend inputting code. Although some people prefer to continue going head first and then remaking everything.
That is a lot of fun to do, most times. Also I need to provide for my family and the guys who pay my salary want their stupid features implemented like yesterday.
I half agree about fun, think it depends on how often clients want some weird shit done yesterday, it becomes a nightmare if it happens too often :(
Over the past month I feel like all I've been doing is writing tech design documents for systems I don't actually know anything about because I haven't had the opportunity to go in and do anything with them.
Fortunately I've finally managed to reach the point where everyone agrees that we should just start implementing the basics and see how that goes rather than try to plan it all out ahead of time since we're surely going to have to throw out the later plans once we see what we're actually dealing with.
like with many jobs you're learning to only do the work that matters, and oftentimes when you can avoid doing work that actually improves the product.
There's a reason why construction workers aren't making their own planks and nails, that would be horribly time consuming, inefficient, and they'd probably make shitty planks.
Not trying to become an expert in everything was the most important decision I made so far, I think
Absolutely. I barely touch code anymore, but I talk about how to touch code a lot.
Why don't they program using spreadsheets? Are they stupid?
@ElCanut geee, I wonder how did they make Microsoft Access.
There's an intern inside the server that checks every transaction by hand
Spoken like a true normie 👍
Can ya please go back to the Drop-Down thingy for your license? It's already annoying on its own, but it gets even more so when Voyager adds the Link-Preview
genuine c/programmerhumor
Sometimes it feels like most of my job nowadays is deleting code now.
To me, there is no greater high than seeing big negative numbers on a commit. Deleting stuff is the most satisfying experience in programming. A commit with +10, -142 is mint.
Be careful with that one. I'm not sure about your experience level, but a mistake newer (and some more experienced) programmers often make is taking DRY too far.
It's easy to "dry" something up to the point where it's spaghetti that's overly clever about how it reduces lines of code resulting in some crazy inheritance hierarchy even you (the author) are afraid to change a few years down the road.
There are of course other times when someone just copy and pasted e.g. sort logic all over the code base ... but that sort of thing is relatively rare