my most descriptive commit message😂😂😂

Programmers: Always use descriptive variable names.

Mathematicians: Single letter variable names always, ideally from obscure/dead alphabets.

Src: Twitter

Thanks Adobe for the such clear icons, I really appreciate your use of descriptive symbols (one is for "view full page", the other is for "activate single page view").

Wow. So descriptive

This is what I found in the logs:
3280546 I had a cup of tea and now it's fixed
9daaf6c copy and paste is not a design pattern
958ca5b It compiles! Ship it!
a9edf8d LAST time, Masahiro, /dev/urandom IS NOT a variable name generator...
438072f 640K ought to be enough for anybody
1fb839b Too lazy to write descriptive message
4d70890 ...
d6ce0c8 Ugh. Bad rebase.
a00b544 Programming the flux capacitor
49715cb Fix my stupidness
4babf07 Do things better, faster, stronger
49b3a7b SEXY RUSSIAN CODES WAITING FOR YOU TO CALL
12c7b55 formatted all
2658c87 and so the crazy refactoring process sees the sunlight after some months in the dark!
2376c89 - Temporary commit.
a83220a I honestly wish I could remember what was going on here...
3347007 work in progress
3382b4c well crap.
109748a Glue. Match sticks. Paper. Build script!
c3f025e Useful text
70394e7 Who knows WTF?!
0d78f14 breathe, =, breathe
5344e39 removed tests since i can't make them green
8a3a6bf better grepping
2777cc4 first blush
cf620ff Continued development...
9591c19 Too lazy to write descriptive message
767e0cd Some shit.
763602a Yes, I was being sarcastic.
8d7a602 /sigh
c6296e5 rats

Worst experience with cs profs? Oh boy....

Databases lab: "You'll need to work of this snippet, if your IDE tells you it's deprecated you don't need to care about it"
If you want to imagine the quality of the code base we were expected to work upon just think about that attached xkcd comic, basically an undecipherable black box.

The instructions where at the same time micro managing everything (he gave us frickin variable names to use, and no good ones, no the database connection had to be called datbc, yeah very descriptive) and yet so obfuscated that I'm not completely sure he didn't resurrect Kant himself to ghostwrite for him.

He also didn't like us to use any Java feature that was to 'modern', for example for each loops since "they offer no benefit over normal for loops".

Further, everything we wrote had to be documented with a relationship diagram and a uml. So far no problem if he hadn't invented his own flavor of both (which can be read about in his book).
Oh, and he almost failed me because I used a lambda expression in his 'code on paper' exam and this "arrows are a C command" I "must have been confused"... which is glorious coming from the guy who can't get operators and commands straight.

Guy I work with: Hey can I borrow you for a minute

Me: sure. What do you need?

Him: so this is a project me an the other dev worked on

Me thinking: Well I know he did it all and sent you the project so don't tell me you worked on it

Him: so we use it to do this and this and send an email to this new account I made because (2 minute explanation)

Me thinking: I don't care. Just tell me what your issue is! I already know what it is and does from what you told me the last time when you showed me. Which took an hour of my time.

Him: so he sent me this code which is called <Descriptive name> and in the method we have variables call <descriptive name> and it returns a <variable name>

Me thinking: You mother fucker! I don't give a shit what your method is named, what it the variable names are, and you don't need to read through every line of code to me! Just from the descriptive name you just said I know what it does! What the fuck is your issue!?

Him: we also have these other methods. This one is called <Descriptive name> which does...

Me: are you fucking seriously going to read me your code line by line and tell me what you named your variables AGAIN!?

Him: and we named this one <descriptive name>

Me: you mother fucker...

Him: and it calls this stored procedure. (Literally opens the stored procedure and shows me) and it is called...which has parameters called... And it is a select query that inserts

45 minutes later after he finishes explaining all 3 pages of his code and his 5 stored procedures that the other dev wrote...

Him: So anyway, back to this method. I need to know where to put this method. The other dev said to put it in this file, but where do you think I should put it in here? Should I place it after this last one or before it?

Me thinking: You fucking wasted my fucking time just to ask where to place your mother fucking method that the other dev sent to you in a project with only 3 files, all less than 500 lines of code with comments and regions that actually tell you what you should put there and 5 small stored procedures that were not even relevant to your issue! Why the fuck did you need to treat me as a rubber ducky which would fly away if you did have one because you didn't have an issue, you just didn't know where to put your fucking code! FUCK YOUR METHOD!

Me: Where ever you want

Him: Well I think it won't work if I placed it before this method.

I walked away after that. What a waste of time and an insult to my skills and really unchallenging. He's been coding for years and still can't understand anything code related. I'm tired if helping him. Every time he needs something he always has to read through and explain his shit just to ask me things like this. One time he asked me what to name his variable and another his project. More recently he asked why he couldn't get his project he found online to work. The error clearly stated he needed to use c# 7. His initial solution was to change his sql connection string. 😑

He should just go back to setting up computers and fixing printers. At least then he would never be in the office to bug me or the other dev with things like this.

SQL Server gives such descriptive errors after failing at 99% -_-

I wrote a piece of code. A logic. My senior changed it. And.. I am glad she did.

My descriptive variables and her conditional breakup of logic made up for a very beautiful piece of code. Simple and elegant. So much so that it makes total sense without any need of a comment.

Never thought I would be loving a 5-lines code piece this much.

This is one of those days when collaboration happens for the betterment.

Simply. Beautiful.

Comment the "why", not the "what". If your code needs comments to explain what it does, rewrite the code (use good, descriptive identifiers).

Always a very descriptive message.

Who prefers long descriptive variable names compared to variables that are acronyms?

For the love of God use descriptive variable names. I dont care if it is 15 characters long instead of 5. Besides any halfway modern IDE does auto completion.

"tTime" is not helpful. Target time? Test time? Total time? Tea time? Turtle Timmy? No clue...

I don't go to the doctor and tell him what tools to use. I was just told to delete the .scss files because they were taking up too much room and to put all partials and images at root instead of in descriptive folders.

Gee, thanks for the descriptive error. That's really helpful. I now know exactly what to do.

Good to know.

my team mate thinks that function name should be descriptive so you can understand what It will do.
Here are the examples of functions he created:

createArrayOfConsentChangedEventObjectForAConsentForAllDataProcessorsWithoutNameInEvent()

createArrayOfConsentChangedEventObjectForAConsentForAllDataProcessorsWithNameInEvent()

createAndPushConsentChangedEventWithAndWithoutNameForAParticularConsent()

I was supposed to review his code but this names are so annoying that I gave up on reviewing and just passed his code since functionalities were working as expected. -_-

Am I the only one who gets annoyed by long function names?

I just love refactoring :) that feeling when an agonic 50loc method with ifs, loops, streams, other shit shrinks down to 3 lines with descriptive and SRP-compliant method calls.. When you can actually read code as a nicely written story. When there are no rubbish comments, cryptic variables and no overly complex if-else skyscrapers jamming all the logic in one conditional chain. When all the abstractions are designed so nicely and design patterns applied so perfectly that extending either of the components is as easy as a walk in a park.

When everything is nice and neat. Only then can I sleep well and enjoy the autumn :)

just some random thoughts after today's coding session :)

Best error message I've seen all week!

just started an AI project (yes I know, very descriptive). should i have 20 nested for loops???

Thanks for the descriptive error message.

I've been lurking on devrant a while now, I figure it's time to add my first rant.

Little background and setting a frame of reference for the rant: I'm currently a software engineer in the bioinformatics field. I have a computer science background whereas a vast majority of those around me, especially other devs, are people with little to no formal computer background - mostly biology in some form or another. Now, this said, a lot of the other devs are excellent developers, but some are as bad as you could imagine.

I started at a new company in April. About a month after joining a dev who worked there left, and I inherited the pipeline he maintained. Primarily 3 perl scripts (yes, perl, welcome to bioinformatics, especially when it comes to legacy code like is seen in this pipeline) that mostly copied and generated some files and reports in different places. No biggie, until I really dove in.

This dev, which I barely feel he deserves to be called, is a biology major turned computer developer. He was hired at this company and learned to program on the job. That being said, I give him a bit of a pass as I'm sure he did not have had an adequate support structure to teach him any better, but still, some of this is BS.

One final note: not all of the code, especially a lot of the stupid logic, in this pipeline was developed by this other dev. A lot of it he adopted himself. However, he did nothing about it either, so I put fault on him.

Now, let's start.
1. perl - yay bioinformatics
2. Redundant code. Like, you literally copied 200+ lines of code into a function to change 3 lines in that code for a different condition, and added if(condition) {function();} else {existing code;}?? Seriously??
3. Whitesmiths indentation style.. why? Just, why? Fuck off with that. Where did you learn that and why do you insist on using it??
4. Mixing of whitesmiths and more common K&R indentation.
5. Fucked indentation. Code either not indented and even some code indented THE WRONG WAY
6. 10+ indentation levels. This, not "terrible" normally, but imagine this with the last 3 points. Cannot follow the code at freaking all.
7. Stupid logic. Like, for example, check if a string has a comma in it. If it does, split the string on the comma and push everything to an array. If not, just push the string to the array.... You, you know you can just split the string on the comma and push it, right?? If there is no comma it will be an array containing the original string.. Why the fuck did you think you needed to add a condition for that??
8. Functions that are called to set values in global variables, arrays, and hashes.. function has like 5 lines in it and is called in 2 locations. Just keep that code in place!
9. 50+ global variables/hashes/arrays in one of the scripts with no clear way to tell how/when values are set nor what they are used for.
10. Non-descriptive names for everything
11. Next to no comments in the code. What comments there are are barely useful.
12. No documentation

There's more, but this is all I can think to identify right now. All together these issues have made this pipeline the pinnacle of all the garbage that I've had to work on.

Attaching some screenshots of just a tiny fraction of the code to show some of the crap I'm talking about.

Today I finally had to write a function for which the most descriptive name is objectively kill_all_children

i am fucking tired of companies that come to me expecting to magically fix their STEAMING PILE OF BULLSHIT AND TRASH CODE. how about when i ask "can i get a project brief", instead of saying "just fix it" or "it just needs to do this", GIVE ME A FUCKING COHERENT AND DESCRIPTIVE WRITEUP OF EXACTLY WHAT YOU NEED. i can't read your minds, let alone read the code the previous cock sucking developer wrote, so guess what? i'm left with no other option but to completely rewrite it. to top it off, instead of giving me god damn excuses as to why you can't get me the api key for your order processing, MAKE A NEW ACCOUNT AND GET IT TO ME. how the fuck do you expect me to test an application when i don't even have access to the fucking api the whole shit pile is based around? i swear to god if these people expect me to have this done by the end of the week but want to be little cunt nuggets they can go eat shit. fuck you, fuck your "contract", fuck your company, FUCK EVERYTHING. greedy, shit faced bastards

A couple of months back we were discussing sh with a third party vendor for a very large ass fuck system that another department uses. I had been called into the meeting because the entire I.T department counts on me to at least act as an assessor to the many issues that other departments might have.

the department for which i was working with manages the databases that our institution uses, and in this particular question the DBA (my best friend mind you) was part of the meeting.

Mind you, issues that the third party vendor were having were all fixed by our DBA, and he had documented and mentioned these items to me as I provided assistance to him through the 3 weeks prior to this meetings. Once such case was that we needed a transitioning as well as intermediary system for some processes to happen from one DB to the other and a lot of other technical babble. Well, the DBA used to be an excellent (fuck you) VB developer who recently re-learned the language into .net. He had shown me many of his old programs and even by the limitations of the language they were elegant and fascinating. They really are and ya'll devrant fam know that I ain't one to hate on tech at all.

When the DBA explained how he went around some of the issues by generating programs that could assist him, he mentioned the tech stack, I had coached him into knowing that being descriptive about the tools he used would be beneficial to everyone else. While he mentioned VB.NET the vendor snickered and my boy got quiet.

Then I broke the silence, fuck you. "what was that?" and the dude said "nothing, sorry"
So I said "no no, I want to know, I am not going past this point until you, the dude getting paid over $100 an hour for something YOU couldn't fix explain to me the little hehe moment you had"

The mfker went silent. then explained how he was aware that people were moving past vb.net and shit like that, me "imagine that, someone used a tech stack that your ignorance thought obsolete to fix something you could not solve, even though we are paying you for it, were it me or in my hands, and mind you i have direct access to the VP so this foolishness might change, I would have cut you and your little sect loose months ago, I have no patience, or appreciation from leeches like you or the rest of the "professionals" that work for your company or other similar entities, much less, as you can see, my patience runs even less when you people snicker at the solutions that our staff has to take when you all slack"

The entire meeting was uncomfortable as high heaven.

Fuck you, if someone I know manages to run shit on fucking liberty basic then so fucking be it. I will slap you 10 fucking times over, and then fuck your girl, if you try to put someone else down for the tech stacks you use.

I hate neck beards, BUT I hate fake ass neckbeards ever more

*Colin Farrell in true detective mode: FUCK....YOU

gotta love the descriptive latex errors

How I met python
[long read but worth]

There's nothing wrong with falling in love with a programming language for her looks. I mean, let's face it - Python does have a rockin' body of modules, and a damn good set of utilities and interpreters on various platforms. Her whitespace-sensitive syntax is easy on the eyes, and it's a beautiful sight to wake up to in the morning after a long night of debugging. The way she sways those releases on a consistent cycle - she knows how to treat you right, you know?

But let's face it - a lot of other languages see the attention she's getting, and they get jealous. Really jealous. They try and make her feel bad by pointing out the GIL, and they try and convince her that she's not "good enough" for parallel programming or enterprise-level applications. They say that her lack of static typing gives her programmers headaches, and that as an interpreted language, she's not fast enough for performance-critical applications.

She hears what those other, older languages like Java and C++ say, and she thinks she's not stable or mature enough. She hears what those shallow, beauty-obsessed languages like Ruby say, and she thinks she's not pretty enough. But she's trying really hard, you know? She hits the gym every day, trying to come up with new and better ways of JIT'ing and optimizing. She's experimenting with new platforms and compilation techniques all the time. She wants you to love her more, because she cares.

But then you hear about how bad she feels, and how hard she's trying, and you just look into her eyes, sighing. You take Python out for a walk - holding her hand - and tell her that she's the most beautiful language in the world, but that's not the only reason you love her.

You tell her she was raised right - Guido gave her core functionality and a deep philosophy she's never forgotten. You tell her you appreciate her consistent releases and her detailed and descriptive documentation. You tell her that she has a great set of friends who are supportive and understanding - friends like Google, Quora, and Facebook. And finally, with tears in your eyes, you tell her that with her broad community support, ease of development, and well-supported frameworks, you know she's a language you want to be with for a long, long time.

After saying all this, you look around and notice that the two of you are alone. Letting go of Python's hand, you start to get down on one knee. Her eyes get wide as you try and say the words - but she just puts her finger on your lips and whispers, "Yes".

The moon is bright. You know things are going to be okay now.

Testers be like: "Error when using system (see screenshot)"

Nice one, super descriptive with where and what you did to encounter the error, oh and cheers for the finger nail sized screenshot!

In my wallowing experience as a freelancer I've noticed that almost all C/C++ clients are perfectionist. You just can't please them by getting the job done quickly.

I got a libcurl job from one the other day to scrape data from a target website and within an hour it was ready. I notified the client and he was both amazed and confused assuming it would take the whole week.
C++Client: The code works but you need to take your time.
Me: Sorry?
C++Client: Yes, it works but you used "string" instead of "wstring"
Me: 😊 Oh okay... *converts strings to wstring*
C++Client: And also variable names should be more descriptive.
Me: 😏 *int foobar => int very_long_descriptive_foobar_01*
C++Client: And also use "shorts" for page nums it'll save some bytes
Me: 😕 *int => short...*
C++Client: And also use forloops instead of whileloops
Me: ☹️ *whileloops => forloops*
C++Client: And also use -- instead of ++ in loops
Me: 😤 *for(... i++) => for(... i--)*
C++Client: And also...
C++Client: And also...
C++Client: And also...
C++Client: And also...
C++Client: And also...
C++Client: And also...
C++Client: And also...
===> Seven "and also" days later <===
Me: *completed 10 Java projects behind the scene*
C++Client: And also use pthread instead of thread
Me: 😧 It's day 7 already!
C++Client: Oh I see, great job. You can compile and send me the archived source.
Me: 🤩
C++Client: And also...
Me: 🏃💨

What an error Message...so descriptive everyone knows what it means

Descriptive variable names and method names > comments

My head is melting. Does anyone have a colleague who constantly complains about missing specs, documentation, project organization, bad processes and procedures? Everything needs to be planned. Not a single small code change can be done without reviewed details. 10min job becomes a week-long session of whining and dabbling.

You give the guy a small task and at the end of the day nothing is done. Just page after page of written documents and lists in Word and online notebooks. Version numbers, meaningless measurement results, latencies etc. And all you asked was "could you just fucking fix this one thing and quickly compile and check it". But no. There must be a review and at least 10 people need to be called into conference. Someone needs to approve everything just so that he can later move to blame to others. "Yeah I know it's not working but I showed you the code and you reviewed it!". Yes, you did, but other people have work of their own so sometimes you need to tie your own shoelaces.

And sometimes finally there's some work done. All indentations are shit. There’re code changes everywhere just because the guy didn't like the previous smaller, compact and logical code. The code doesn't even compile properly anymore. And if you complain, the reason is "there's no proper reviewed and stamped process description, so I cannot know if a variable is supposed to be 10 characters long. Besides 200 character long variable names are much more descriptive". For fucks sake.

Some coders should've gone to work in some tax office basement.

Error messages these days are so descriptive.

Me: Write a small descriptive paragraph on the changes made to files and what needs to be worked on.

Team: “Add function 🙂” *10+ files changed*

*Reports bug on Firefox (bugzilla) 3 months ago*
*spend a lot of time being clear and descriptive as possible*
*gets literally no attention*
*someone else reports the exact same bug 5 days ago but with a picture and less words*
*everyone responds*
*mfw I didn’t know you could add pictures 😑*
*my bug gets closed for being a duplicate even though it’s the original*

Fuck you cunts

Developers who think using cryptic variable names (like acronyms) is better than long descriptive variable names.....but then feel the need to document/comment the variable name rather than just naming the variable properly in be first place.

// Current CGRect to draw into
let ccgrd = self.currentCGRect()

Instead of just

let currentRectForDrawing = self.currentCGRect()

If you know you're writing code that other people will have to work off of and you refuse to comment, can you at least have descriptive variable names so I don't have to spend an hour trying to figure out wtf something is. One letter does not make a variable name.

Another day, another shitty set of JIRA tickets.

In this week's edition, we run into an issue you'd think is a meme, something you couldn't even make up: three tickets with IDENTICAL titles, but miraculously, they actually refer to three DIFFERENT tasks! (Also comical, they're not bugs, they're tasks, but mouth breathers don't really know the difference, and at this point I just don't have the energy to attempt to explain what could be explained to elementary school children.)

I present a rare look into our national archives!

This document features two exhibits:

Exhibit A: product owner's original ticket titles

Exhibit B: translated-into-competency-because-i'm-not-mentally-deficient ticket titles

Just more proof that 'product owners' don't own shit, the devs are the real ones who actually know what is going on.

I mean just LOOK at Exhibit A's titles. As a big smart manager, do you write those tickets, smile, and say to yourself "Ah, yep, that's very clear, I'll definitely remember what each of these mean literally 5 seconds from now!"

Is asking for literally 30 seconds more of thought too much to ask for? Apparently.

Just kill me

Happy friday ☠️

People don't seem to know how to properly do print-debugging, so here's a simple guide:

1. A log of "aaaaaa" or "got here" isn't as helpful as you think when ALL OF THEM ARE THE FUCKING SAME. You put a descriptive label or copy verbatim the conditional statement. This saves time matching statements, allows one to watch multiple branches at once, and allows others to understand and help faster when dragged in to help.
2. When trying to see where code fucks up, before each line, paste said line into a proper print statement for your language. If there's, say, a function call or some shit, have it output something like "functionCall(varA=<varA contents>,varB=<varB contents);" Most normal lines should be like this too, but it's especially helpful for calls and comparisons.
If need be, add return values after if they're not shown in another print statement later.
This allows for a trail of execution AND the line that fucks up will be the last in the log, making finding it easier when dealing with hangs and such.
3. Putting something unique like "DEBUG: " or something in front of all statements ensures you can just search for them to ensure you're not rolling one out to production. It also separates debug output from normal output at a glance, making digging through logs faster.

I've learnt that you should always make descriptive comments in your code to explain it.

If you are a web developer, consider using proper page titles.

Page titles are one of the most basic elements of a web page and yet websites often fail to make proper use of them.

Without a proper page title, your user does not have an accurate idea of what page is in the tab without having to open the tab, which gets tedious if many tabs are open. With a proper page title, an instant glance on the tab does suffice.

Some sites only put in their site name or something like "Search - Site Name" without including the search query in the page title, or "User profile - Site Name".

An example of this is, disappointingly, archive.org. As thankful as I am for the Archive, they could make better use of page titles to make browsing their library more convenient. While they use proper page titles on item pages (including both title and author!), they use non-descriptive titles on their 2023 search feature (downgraded from lightweight static HTML+AJAX to a JavaScript app) and user profile pages.

The user name of a profile or a search query and ideally a page number should be in the page title so a browser tab with a search can be found faster and can also be seen on social media sites that auto-generate preview cards with page titles.

Descriptive page titles also improve your search engine ranking! You surely don't want to miss out on that, do you?

Variable name
Descriptive VS Short

New job: Asked my manager if i can add documentation for the code/project.
Manager: it's completely useless to use hours on documentation. If you don't understand any thing just ask around. It saves time. Just use descriptive variables and method names.
Me: :|

Found a function called WriteActualFile 😖

Ah yes, who doesn't like descriptive error messages?

in-App-purchases are so self explanatory in the App Store. Seriously, why can’t you at least just write something like premium, but only write the apps name?...

honestly some online courses are bullshit. i joined one for some sample code, and no comments, no explanations, the variable names WEREN'T even descriptive.

this is from a website with a published book… how about you take some fucking responsibility for your code?

the language was c++ and they are still using printf! shake my fucking head. you have global variables that are one fucking letter! please, stop, get help.

…AND IT WASN'T EVEN ON GITHUB

How am I supposed to know which fr*cken whitespaces they are…

The tooltips don't even display!

Plus, emojis get descriptive names in their tooltips. These characters' tooltips are JUST THE CHARACTER ITSELF.

Wow, Issues on GitHub are really a good way to maintain a descriptive TODOs for your personal project

When people use one character variable names in their code I'm just like:
How do you guys live like this... 😰

I have this idea for a story, but I lack graphic talent. It's always frustrated me that I can't bring the ideas in my head out in to visual form, but the programmer in me knows how to be descriptive enough.

Thanks to AI I genuinely think I might be able to make my story as a visual novel. Here's one of the first successful renders of a scene.

This might just work. I'm excited...

SO MAD. Hands are shaking after dealing with this awful API for too long. I just sent this to a contact at JP Morgan Chase.

-------------------
Hello [X],
1. I'm having absolutely no luck logging in to this account to check the Order Abstraction service settings. I was able to log in once earlier this morning, but ever since I've received this frustratingly vague "We are currently unable to complete your request" error message (attached). I even switched IP's via a VPN, and was able to get as far as entering the below Identification Code until I got the same message. Has this account been blocked? Password incorrect? What's the issue?

2. I've been researching the Order Abstraction API for hours as well, attempting to defuddle this gem of an API call response:

error=1&message=Authentication+failure....processing+stopped

NOWHERE in the documentation (last updated 14 months ago) is there any reference to this^^ error or any sort of standardized error-handling description whatsoever - unless you count the detailed error codes outlined for the Hosted Payment responses, which this Order Abstraction service completely ignores. Finally, the HTTP response status code from the Abstraction API is "200 OK", signaling that everything is fine and dandy, which is incorrect. The error message indicates there should be a 400-level status code response, such as 401 Unauthorized, 403 Forbidden or at least 400 Bad Request.

Frankly, I am extremely frustrated and tired of working with poorly documented, poorly designed and poorly maintained developer services which fail to follow basic methodology standardized decades ago. Error messages should be clear and descriptive, including HTTP status codes and a parseable response - preferably JSON or XML.
-----

This whole piece of garbage is junk. If you're big enough to own a bank, you're big enough to provide useful error messages to the developers kind enough to attempt to work with you.

Just JIRA things:

We've got a very descriptive ticket with the title: "API Interface"

Can't wait for the rest of this Friday to play out, I'm already joyful and in the holiday spirit.

Best git commit messages ever(sarcasm):
- Fixes.
- Changes.
😥

For my graduate level people(aka Masters degree students or holders)

How normal would you say that: giving dense ass lectures in NN with absolutely NO practical examples and just a fuckload of theory + 1 simulation project in Pytorch in which a robot is to detect collisions is?

is it normal? i mean I knew about Pytorch from a very shallow overview, but these assholes gave that project and expected it completed in a week with a fuckload of dense ass lectures and no practical exmaples.

I know school is supposed to be hard, that is not my gripe, but in yalls experience are teachers more descriptive and fun in other institutions? do I just have shit luck with teachers? I don't feel like wasting my money. If your experience was better then let me know, cuz I want education yes, but i want it better.

Any other language: Hey fuckface, you can't name this variable by a single letter, tf is wrong with you? use some descriptive shit.

Golang: lmao fuck u

I really find it interesting how we use short variable names for items in golang. Kinda makes sense when you think of it. Most of these items come up in short methods for which the mental model lets you know and remember what you are doing, they even make sense when going through the std lib in which that shit is all over the place. YET years of going by other languages has made me squint my eyes a bit in frustration every time I see it.
Say for example that a function is implementing io.Writer. What would you call the method parameter? you could argue that writer would be sensible since it has it in the signature, but what about when the io.Writer in itself is a file or a socket or whatever? writer would be funny or strange? nah fuck it just w, it makes sense, but x wouldn't. I find these points to make sense even if i don't like them.

Would, now, this practice be acceptable in C? you are supposed to write the same modular code with C in which you compose large functionality in separated units of code, yet I am sure this practice of single name variables is something that C engineers dislike greatly.

Are go devs just doing this out of blind love for their preference in languages? and how would this work if mfkers add generics to go(I hope not, Go is simple enough to understand in order to extend functionality through the empty interface, but that is a preference of mine as well)

The more I use Go the more I like it to be honest, I think the code looks ugly syntactically, but that is subjective as all hell and based on my constant preference for a language to look like Ruby, which even though it might not be everyone's cup of tea it remains to my eyes as the most beautiful language in existence, again, an obvious personal preference.

Looks familiar?
I really need to start giving more descriptive names when I test code..

Var that=
Vat thatt=
Var thattt=
....
Func workFFS=

Have to write ugly ass wrapper classes around a third party dependency since my team can't be bothered learning its vocabulary. A vocabulary which is very well thought and self-consistent. Apparently, defining our own which is only occasionally more descriptive is preferred. It's already collapsing under the weight of its own maintainability cost. And, if someone joins the team that knows the dependency they are fucked anyway as they'll have to use our wrappers.

Time and time again I've tried to oppose this move on several different merits: maintainability chief amongst them, but no one listens to the lowly new hire.

I should just pipe my thoughts to /dev/null and save my breath...

I've finally got into the habit of writing descriptive comments in my code. I've always just got so into the coding and comment later when I don't know what the code does anymore xD

The best motivational comment

I posted a rant in which I mentioned that "few" developers who don't want other to progress and are present to show off at every platform....
Got a comment, which I want to share...
Thanks to @MrCush

Ya, most of them tend to stalk the stack overflow and Arch Linux communities. On stack overflow they tend to refresh their browser nonstop to see who their next victim is on a new question and then spend an abnormal amount of time searching the site for a similar question and then downvote you and report as a duplicate. “Umm ya, the question you linked is similar to mine. I found that one as well but unfortunately it wasn’t in the same environment with the same conditions that I raised and didn’t help me. Oh btw, he posted that back in 2002 and HEY LOOK, he got reported for a duplicate as well. Seems like you reported him as well.” 
The issues of arrogance and being unhelpful on that site are so vast that nobody else that registers can get enough points to be able to be allowed to answer someone else’s question so you never get any new blood.

Arch Linux “elites” like to answer your question with a link that you’ve already been to as they always link the same site. “Dude! There’s a wiki for a fucking reason. Did you read this page?”
Yes I did read that page and it was helpful to a degree but since I’m absolutely new to Arch, a lot of the information on the wiki is a bit too descriptive and over my head. Not to mention every paragraph links you to another wiki page which then links you to another and so on that I have no idea where I left off....
“Dude! If you don’t understand everything on the wiki then you shouldn’t be using Arch Linux man! Gtfo scrub.”
Took me a long time to get comfortable with Arch because of these assholes. You got to start somewhere and doing is the best way to learn.
Reading the wiki on how to install Arch now seems so simple to me because I know what to ignore and what is required but back when I first started it was absolutely confusing.

is soo cool when people is up to joke around with my bad jokes.

-- Talking with a coworker about a new button in a results table --

dude: hey jhon, I'll name the button 'SHOW RESULTS' and the endpoint will be named that too. cuz there is a 'SHOW STATS' already

me: dunno, use something more meaningful, this is about unparsed results, right? so what about...

me: unparsed results ? unparsed stats ?

me: another one bites the dust? show must go on?

me: innuendo?

me: pick one 8D . But I think innuendo is pretty descriptive

dude: ok

me: seriously, 'show unparsed stats'

dude: got it

-- then the dude sends me the screenshot --

me: LOL, 8D

me: you got my respect man (_ _)

There is a period in developer's life when writing comments in your code is a good idea. Then, after some time, when you write comments, it means your code is not that descriptive, is not so good that you consider writing comments.

Dev Mantra

I do not write code with my keyboard. He who writes code with his keyboard has forgotten the days of the punch cards. I write code with mind.

I do not write non descriptive variables. He who writes non descriptive variables has forgotten the days of the punch cards. I write self descriptive code.

I do not debug by brute force. He who debugs by brute force has forgotten has forgotten the days of the punch cards. I debug with breakpoints and stack traces.

Wow. 3 super descriptive changelogs in a row.

Idk but i think i have the inability to ask a question on stackoverflow. Whenever i come across a specific problem my first instinct isn't to ask stack. It's to research, research and research. Then i go ahead to ask to those iknowsomuch pricks.
Do i enjoy it? No, i do it because i fucking need to.
So, stop shoving the fucking rules or policies or whatever the fuck it is on my face and answer the damn question if you know it. If not, fuck off. I hate it when they mark it as duplicate. Like are you actually serious. I've gone through the whole fucking internet including stack, searched the damn problem in different keywords, tried all the solutions for the related questions and problems and that's what you come up with. Label it as a duplicate or not descriptive enough. Oh just seriously fuck off with your "oh i have some admin capabilities let me use it on random shit". These are the people where they have no authority on anyone or led anyone or any team in their shitty lives yet act like a dickhead when someone in need of help comes to them. Oh you piece of shit, just fuck off. You miserable cunt.

What does my current job hate descriptive names? Like to the point of active antagonism? We're a subscription based service. Why is SubscriptionExpiration the date you log in? Why does SubscriptionStatus only contain the name and id of product you're subscribed to and nothing to do with an actual status? All I need is the date a user subscribed. Why is this so hard!?!?

Git Commit Part 3:
28d48b0 This is why the cat shouldn't sit on my keyboard.
95df68f I must enjoy torturing myself
c5acfc2 Fix my stupidness
3a57702 I hate this fucking language.
6cb212a Too tired to write descriptive message
292b1e2 That last commit message about silly mistakes pales in comparision to this one
f4a091f Does not work.
5af1ca1 small is a real HTML tag, who knew.
e7d2d84 Best commit ever
f54d32b de-misunderestimating
f587ca1 Added translation.
352e29c Future self, please forgive me and don't hit me with the baseball bat again!
54403a6 Now added delete for real
9f42f38 Who knows...
5df8457 more ignored words
56bd0ef Added missing file in previous commit

I am just student looking for job, and got this pre interview test:
Develop an Android or iOS app with login and password input field, download button, place for image we prvided.

... reading further:
What we are looking for in the code ?
internal quality:
-consistent formatting of the source code
-clean, robust code without smells
-consistent abstractions and logical overall structure
-no cyclic dependencies
-code organized in meaningful layers
-low coupling and high cohesion
-descriptive and intention-revealing names of packages, classes, methods etc.
-single small functions that do one thing
-truly object-oriented design with proper encapsulation, sticking to DRY and SOLID principles, without procedural anti-patterns
-lots of bonus points for advanced techniques like design patterns, dependency injection, design by contract and especially unit (or even functional or integration) tests

external quality:
-the app should be fully functional, with every state, user input, boundary condition etc. taken care of (although this app is indeed very small, treat it as a part of big production-ready project)
-the app should correctly handle screen orientation changes, device resources and permissions, incoming calls, network connection issues, being pushed to the background, signing deal with the devil :D and other platform intricacies and should recover from these events gracefully
-lowest API level is not defined - use what you think is reasonable in these days
-bonus points if the app interacts with the user in an informative and helpful way
-bonus points for nice looks - use a clean, simple yet effective layout and design

... I mean really ? and they give me like 2 days ?

Half of my time coding is spent coming up with descriptive, unique var names that won't clash with damn namespace.

such a descriptive name Google .The person who wrote this interface deserve a cookie

Before I started working, I used to feel like I depended on documentation and the internet a little too much owing to ultra crappy long term memory. After spending some time at my internship going through code written by "professional developers" several years senior to me and trying to write unit tests for it (surprise: the code was in production without having underwent any sort of testing), I feel like the amount of time I spend online reading usage recommendations, alternates for optimisation, best practices for writing clean and descriptive code and all that is a lot more rewarding. Some bad things help you feel good about yourself.

Apologies if this has been asked here before, but I wanted an open feedback on a query: Is there such a thing as overdocumenting?

I take pride in being a very articulate developer, being as descriptive as possible in my emails, internal communications, PR review comments, JIRA etc.

A product guy from the company today mentioned: "Though I understand your good intent behind being as descriptive as possible, it is possible that some of the junior engineers might get overwhelmed/ intimidated looking at those comments/ emails and it might stop them reaching out to you with your doubts."

I was not able to wrap my head around this, because I don't understand how a descriptive explanation might overwhelm anyone. It's a skill I picked up going through my career and I personally have always respected peers who documented things properly.

Open to feedback. Thank you in advance.

The term "CPU" is stupid nowadays, what even is "central", when there are entire server farms primarily employing GPUs.

I propose "GPP" - General Purpose Processor - as a much more descriptive name instead.

I got frustrated with my code. I decided to open a new file and rewrite everything with better descriptive names to variables, and combined 3 functions that basically did the same thing into one to be called. It cent nice until my shift was up and I had to go home.

As much as I hate writing documentation, I agree that it's a necessary evil. I also try to be as descriptive as possible where it makes sense. But, do we really need a 6-page document explaining how to run a query that updates a user's role?

stateofjs survey reminds me of all that's wrong with JavaScript: too many frameworks each of which has to reinvent the wheel and depend on too many node_modules child dependencies, most don't support TypeScript properly (ever tried to convert a node-express-mongoose tutorial to TS?), there is still no proper type support in JS core language, and browser features get added in form of overly complex APIs instead of handy DOM methods.

Instead the community gets excited about micro-improvements like optional chaining which has been possible in other languages for decades.

At least there is something like TypeScript, but I don't like its syntax either, it's overly verbose and adds too much "Java feeling" to JavaScript in my opinion.

Also there is too much JS in web development, as CSS and HTML seem to have missed adding enough native functionality that works reliable cross browser to build websites in a descriptive way without misunderstanding web dev for application engineering.

After all, I'd rather have frontend PHP than more JavaScript everywhere.

Anyway, at least the survey has the option to choose how satisfied or unsatisfied people are about certain aspects of JS. But I already suspect that most respondents will seem to be very happy and eager to learn the latest hype train frameworks or stick to their beloved React in the future.

When a non-descriptive error occurs while uploading to a system and all you can do is incrementally remove your changes to deduce where the error started popping up

Productivity hack - For me, it’s mostly a single word - planning. I wasn’t always good at it, definitely not yet a “master” of it, but breaking that proverbial elephant up into smaller pieces, and organizing a plan of action for dealing with them is the #1 productivity “hack” for me. Sorry that it’s not an actual shortcut, or anything…I personally don’t believe in those anymore. Complementary habits to this are thoroughly commenting code, having descriptive commit messages, file names, and variable names, maintaining documentation. Use that Readme.md. This is true of any project, even if I’m the only developer - never underestimate your own ability to totally forget shit.

I hate it when colleagues name their commits with a non descriptive name like "minor changes", "minor fixes", "small changes" and so on. I know that good naming is a difficult task in software development, but do I expect to much when I want them to explain shortly what exactly they changed since the last commit?
Good commit messages are always helpful if you want to do good PR reviews and furthermore if you want to go back to an older commit because someone fucked something up.
Don't get me wrong, my colleagues are great people and great developers, but some of them ignore the fact that good commit messages might be useful in the future for others and themselves

Don't you just hate it when a git pull request assigned to you doesn't have a descriptive title and no description at all? I think I'm having a migraine! #%!%^*#

I mean... Nothing to descriptive, and it's technically not a CS degree. But it got me a job and helped me learn some fundamentals that I was lacking.

I was originally going to try learning on my own because I hated school. Now I'm glad I at least went through the Associate program I went through.

Mongodb CEO and the developer who build this shit for brains interface should be tarred and feathered. Almost 90minutes in and I cannot connect to anything other than error codes. What in the actual fuck is your job other than to make it difficult for a "free tier" user to connect?
"connect ECONNREFUSED 127.0.0.1:27017"

Oh ok another 20 minutes of work and you give me a bland beige error code like "```TLS/SSL is disabled. If possible, enable TLS/SSL to avoid security vulnerabilities.```"... um ok how do I enable it for your site, your database or on my computer... oh wait you don't say shit do you?

So now I'm fully 81 minutes into this shit show and all I get for error codes are these really descriptive gems 'getaddrinfo ENOTFOUND cluster0.hudbd.mongodb 'dot' net` comes up if I choose `mongo` with "connection string scheme" above it or `bad auth : Authentication failed'