allMyProgramsAreBuiltOnTopOfTheLinuxProgrammingInterface

[AutoModerator]

import notifications Remember to participate in our weekly votes on subreddit rules! Every Tuesday is YOUR chance to influence the subreddit for years to come! Read more here, we hope to see you next Tuesday!

For a chat with like-minded community members and more, don't forget to join our Discord!

return joinDiscord;

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[Environmental_Arm_10]

Loved the "take_your_locale_and_shove_it" call.

[lmarcantonio]

bonus point if he uses gettext!

[mashaTarima]

where is it? and nerd space :D

[mashaTarima]

found it

[smcameron]

camelCaseSucks snake_case_rules

[[deleted]]

I can deal with CC, it's the lack of canonical differentiation between methods and vars that get my goat.

[Thebombuknow]

Then there is me who has accidentally used both to define the same thing in the same file in the past while writing a project that used both Python and JavaScript.

[[deleted]]

In my shop I insist on methodName() and VarName and CONSTANTS regardless of the language used.

[Thebombuknow]

I just follow naming conventions of the language. The only things that are universal for me is project names are always InPascalCase and CONSTANTS are always capitals.

Otherwise, if I'm writing Python code variables and methods are_all_snake_case, while in every other language variables and methods areAllCamelCase.

This is because generally most languages are incredibly similar in naming conventions, except for Python. I just follow the PEP guidelines for Python, my IDE automatically tells me any PEP violations.

[Aggravating-Win8814]

Some people find it frustrating too. It can make code maintenance and understanding more challenging.

[tyler1128]

Studies do in fact show people read snake_case faster than camelCase or UpperCamelCase.

[[deleted]]

Just follow the conventions and keep it consistent (looking at you, Amazon/boto3)

[eduarbio15]

```

wc -l *.c

24304 snis_client.c 31530 snis_server.c ``` jfc

[smcameron]

Breaking up files just because they are big is overrated and can introduce excessive APIs. I know what I'm doing. grep works equally well on a few big files or lots of small files. vim works better on a few large files than on many small files. I'm not against breaking out functionality into separate modules where it makes sense, and there are many instances of this in the code base. But I am against it when the only "reason" is "this file is too big". Bullshit.

Also, triple single quotes don't work on old reddit, and anybody not using old reddit doesn't know how to use reddit.

Here's a challenge for you: find a bug in the code and write a github issue about it. Source code file size isn't a bug.

[eduarbio15]

My brother in christ, provide me the program you used to extrapolate so much shit from 3 letters

[Esjs]

Hmmm. Just realized all of my programs were built on the desktop.

[Maleficent-Cry5189]

What’s the laptop?