It just hit me that 'devRant' is in camel case.

I approve.

I said camel toe instead camel case in a meeting today...

I really appreciate that it's devRant, not dev_rant

Coworker 1: Ugh, what name should I give this variable? Any idea?

Coworker 2: Doesn't matter that much. Just give it a name.

Coworker 1: ** Types in "albert" **

When you're 6 hours in coding C and notice that you've been using the python code style guide.

Fuck Monday.

This is something that happened 2 years ago.

1st year at uni, comp sci.

Already got project to make some app for the univ that runs in android, along with the server

I thought, omg, this is awesome! First year and already got something to offer for the university 😅
(it's a new university, at the time I was the 2nd batch)

Team of 12, we know our stuffs, from the programming POV, at least, but we know nothing about dealing with client.

We got a decent pay, we got our computers upgraded for free, and we even got phones of different screen sizes to test out our apps on.

No user requirement, just 2-3 meetings. We were very naive back then.

2 weeks into development, Project manager issues requirement changes

we have a meeting again, discussing the important detail regarding the business model. Apparently even the univ side hadn't figure it out.

1 month in the development, the project manager left to middle east to pursue doctoral degree

we were left with "just do what you want, as long as it works"

Our projects are due to be done in 3 months. We had issues with the payment, we don't get paid until after everything's done. Yet the worse thing is, we complied.

Month 3, turns out we need to present our app to some other guy in the management who apparently owns all the money. He's pleased, but yet, issued some more changes. We didn't even know that we needed to make dashboard at that time.

The project was extended by one month. We did all the things required, but only got the payment for 3 months.

Couldn't really ask for the payment of the fourth month since apparently now the univ is having some 'financial issues'.

And above all: Our program weren't even tested, let alone being used, since they haven't even 'upgraded' the university such that people would need to use our program as previously planned.

Well, there's nothing to be done right now, but at least I've learned some REALLY valuable lesson:

1. User Requirement is a MUST! Have them sign it afterwards, and never do any work until then. This way, change of requirements could be rejected, or at least postponed

2. Code convention is a MUST! We have our code, in the end, written in English and Indonesian, which causes confusion. Furthermore, some settle to underscore when naming things, while other chooses camel case.

3. Don't give everyone write access to repository. Have them pull their own, and make PR later on. At least this way, they are forced to fix their changes when it doesn't meet the code convention.

4. Yell at EVERYONE who use cryptic git commit message. Some of my team uses JUST EMOTICONS for the commit message. At this point, even "fixes stuffs" sound better.

Well, that's for my rant. Thanks for reading through it. I wish some of you could actually benefit from it, especially if you're about to take on your first project.

I don't drink coffee.

*Keyboard breaks*
*Calls Desktop Support*
Me: Hey, my keyboard is broken. I want to replace it.

*Support guy sends new keyboard*
*Calls support again*
Me: Hey, the shift key on the left side of the new keyboard is broken.

I don't know who came up with this keyboard design, but that person really wanted to see developers who write in camel case suffer while their muscle memory adapts.

Just realised I can guess your main programming language by whether your nickname is in lower/camel case 🤔

Since apparently lots of you are into Linux, I would like some advice.

I'm wanting to install a distro to use as my main OS, but there is just too much choice.

I'm coming from Windows 10 so I read that KDE is a good choice for a desktop environment and the Plasma version looks pretty good.

Yesterday I've tried Deepin OS but I'm not a huge fan, looks good but not enough content / customization.

So right now I'm hesitating between Manjaro (with KDE) and Elementary OS.

Would you recommend any of these, and why ?

Btw, this is my first rant 😎

It really irks me when I see 'web developers' and 'front-end developers' write CSS like a bunch of first-timers. Not considering hierarchy, specificity or even following a proper naming convention (who the fuck mixes camel case AND lowercase for class names?!) It's worse when you already have Sass or SCSS and they still write their style rules WITHOUT PROPER NESTING or keep using !important like it was a goddamn semicolon.

This is fucking basic shit for a web or front-end developer, and God help you if I ever conduct your technical interview and decide to ask you on a whim to write an Angular app WITHOUT USING BULLSHIT SYSTEMS LIKE CLARITY, ANGULAR MATERIAL OR BOOTSTRAP for your UI. But if you can explain to me the pros and cons between using CSS grid and flex, I'll be fucking impressed.

I wish these 'UI experts' I keep encountering would learn to build an optimal static site without a fucking framework or build manager before doing advanced shit, for the love of Jeebus.

You are into too much of Java when only camel notations seems correct to your eyes. Even in case of normal words 😝.

Oh my god my brain is hard wired to write c++ in snake case. Spent 4 years doing it. This code base uses camel case.

I had a mid semester test and there was one question on how we should create class names. I was very tired, so the test started like around 9-ish. Instead of saying Camel Case method I said Camel Toe method.

Makes me wonder how did they come up with the name "camel casing" anyways?

So we had this legacy Objective-C codebase for a mobile app that was actually pretty good: I'd inherited the codebase and spent the past several years gradually improving it and I was actually quite proud of the work I put into it. So of course management decides to scrap it (with NO consultation from the engineers) and outsource a complete rewrite of the app in C# for Windows Universal.

Let me tell you. That code was without a doubt and without exaggeration the *worst* code I've seen in my close to 30 years of experience as a developer. I mean they broke every rule in the book, I'm talking rookie mistakes. Copypasta everywhere, no consistent separation of concerns, and yet way too many layers. Unnecessary layers. Layers for the sake of layers. There was en entire abstraction layer complete with a replicated version of every single data class *just* to map properties in pascal case to the same property in camel case. Adding a new field to a payload in the API amounted to hours of work and about eight different files that needed to be modified. It was a complete nightmare. This was supposed to be a thin client, yet it had a complete client-side Sqlite database with its own custom schema (oh and of course a layer for that!) completely unrelated to the serverside schema, just for kicks. The project was broken up into about eight or nine different subprojects, each having their own specific dependencies on various of the other subprojects in such a tightly-knit way that it made gradual refactoring almost impossible. This architecture was so impressively bad, it was actually self-preserving!

Suffice it to say it was a complete nightmare, and was one of the main reasons I ended up leaving that company. So just sayin', legacy code isn't always bad. :)

Switching from a camel cased standard(js) to a snake cased standard (rust) tutorial

pub fn do_shit() {°°°}
...
pub fn doMoreShit()°°

*Notice wrong case*

To self:

Aaarghbkflahvflw. Why can't you fucking get the damn case right! And you call yourself a fucking senior programmer, you piece of useless shit.

#existentialCrisis
#questioning_life

pub fn do_other_shit()
...

Inconsistent camel case. Not that complicated dude

I'd like to use snake case like everywhere. Got that from rust.

Now in typescript, but seeing libraries and baseline core libraries in camel case, I end up going back to camel case.

I guess consistency is more important to me

Razer Blade Stealth, 1350€ instead of 1800€ 🤔 should I ?

PyCharm's Warning: "Function name should be lowercase for PEP8 naming conventions."

Do Python developers not like camel case function names?

What does projektaquarius do when he doesn't have a working IDE? Reformat code (that I am already refactoring) to an industry standard format and prepare for the arguments that are going to come from the other group who has their own coding standard that isn't industry standard.
Already preparing for the Pascal case versus Camel case argument. Emotionally that is. Mentally the argument basically just amount to "your group didn't want to refactor the code so we did it. Live with it or you do it."

Oh boyyy, I just had to work with Asterisk again. And holy shit it is still the clusterfuck it was many years ago.
We got:
- Inconsequent documentation that is mixed through all versions.
- The config sprinkled over what feels like 20 gazillion files.
- AEL being a half assed attempt at a "pRoGRamMinG LanGuAgE"
- The fuck you mean with extensions, endpoints and AOR's?
- Inconsistent config parameter naming. Some are snake case, some camel case some are just everything smushed into a single word.
- queue_log determines wheter to write a log to a file. queue_log_to_file Says to do so independent of you having a realtime backend. Whatever the fuck that is.
- Log compression is done by executing a gzip command after a rotation??!!?!!

Intern: *writes text-color: 'white'* Hey, I'm trying to apply this color, but it doesn't work.
Me: Remove the "text-" from it.
Intern: *confused*
*Removes "-" and makes it camel case.*
Me: No, it should just be "color".
Intern: Okay, that works. Thanks.
(-_-)

Ohai,
It's been 172 days (since my last post)

We work with multiple platforms, a legacy language and c#. This dev uses underscore between variables in c# and camel case in the legacy platform. The thing is the legacy system has used underscores since 1981 and I've never seen a readable example of c# using them between words.

I also told him I was working on learning to use patterns and how the process of software development should work by training. His response... Why would you want to do that?

He also copies and pastes code everywhere and pays no attention to scope.

And worst of all I'm his coverage when he is gone. If I have to debug one more sloppy bug I am going to face desk.

Decided to go through my current project and change the naming conventions to actually obey the standard Microsoft C# naming convention standards.... Fuck me this is going to be fun -.-

(I use camel case and a lot of 'unnecessary' abbreviations :-P)

Question for the Android users!
I'm tired of Google and its intrusive apps and shit so I'm thinking installing a custom ROM, but I see that there are plenty of them (Lineage, Paranoid, Dirty Unicorns, etc etc), so I'm looking for advice ✌️😎

Life is to take decisions. Which u prefer
Google vs Shodan vs 🦆 🦆 go
Angular vs vue vs react vs other
Gnome vs unity vs KDE
Atom vs vscode vs sublime or other
iOS vs android vs other
Natives bs ionic vs react native vs xamarin vs flutter
Gmail iCloud or outlook or proton mail
Camel, pascal ,snake case
C# or Java or python
Sql or not sql
Debian , fedora ,linux mint or kali
Server side rendering or client side
Aws vs gcloud vs Azure vs ibm cloud
Firefox vs chrome vs safari
Free without privacy or ads or paid without ads or privacy
Nintendo vs pc vs ps4 or xbox
WhatsApp or telegram or other
Sleep at night or not

Coment your favorite

Snake case or camel case ?

Friday morning's meeting:
CTO: Ok guys, deadline is next Friday so today we close the last big issues and next week no more new features, only bug fixing.

Monday morning's meeting:
Business: So here is the new mock-up for the search feature (basically they changed the whole behavior).

😐

What Android emails app do you use ? 🤔

Seriously, what's with the naming ordeal?
We start with userInput, then spiral into userInputUpdatedFinalV2

Are we writing code or crafting spell incantations? camelCase, snake_case, kebab-case, PascalCase – it's a syntax battleground.

Can we have names that make sense, for sanity's sake?

Imagine that I have written 1000 lines of code and imported many libraries. Sometimes I get confused when trying to use a name I defined earlier. In my mind is this name a class or a method, is it a local or global variable, is this a constant. So I came up with a way and it totally works, although my ide complains, but who cares, I use it anyway.
I use PascalCase for class.
camelCase for methods.
snake_case or lowercase for global variables.
kebab-case I don't use this
UPPER_CASE for constants
snake_caseL or lowercaseL with a capital letter L at the ending for local variable.
I hope this is helpful 😊🤔

Cocaine. Wait that's not what you meant, didn't you?

Mostly copied from YouTube and stack overflow. Someday stuck with camel case because my friends got fed up with me ¯\_(ツ)_/¯

VSCode. I used to be a WebStorm guy, but at one point I found out that I could do like 85% of the stuff in VSCode, and switched over. Things I still kinda miss from the JetBrains ecosystem:
- the elaborate refactoring
- the built-in navigation across the file and the project
- the really clever expand select and go to open/closing bracket (VSCode is kinda getting there, but for expand select it honours camel case words and that can't be turned off, it's weird with HTML files with inlined JS or CSS; for bracket jumping it must rely on an extension)
- the way that everything within the UI is predictable and navigable with keyboard only (tried opening a dropdown in VSCode without having a specific keybinding for that specific dropdown? In WebStorm it was Alt+Up/Alt+Down for any dropdown that has focus IIRC)
- the visual way of changing a colour theme (in VSCode you have to guess what is what before modifying a value; by the way this is an idea for an extension that I might research)

What I like about VSCode:
- the speed (although it can get slow with large files; on the other hand JetBrains IDEs are not that slow except for the startup, given that you're not working on a potato, but here we are)
- its extensibility and very active extension development (and the fact that it's rather easy to write your own extensions, although I haven't benefited from that very much)
- the ease of syncing settings (the Settings Sync extension and now the built-in mechanism introduced I think earlier this month)
- it's free (so I don't have to pay for it myself or nag to my employer to issue me a license)

I've tried Sublime and it's hands down the fastest thing I've seen (it can open a 100 MB text file on the shittiest computer you can find and edit it efficiently), the problem is that it's not so rich in extensions. I've tried vim, nano and whatnot, but I'm far from that, just not my cup of tea. I'm okay for the occasional file edit while SSHd somewhere, but that's all.

In an ideal world we'd have something like Sublime's performance with VSCode's ecosystem and JetBrains', well, brains...