So I told my wife one week ago: "Yeah, you should totally learn to code as well!"

Yesterday a package arrived, containing a really beautiful hardcover book bound in leather, with a gold foil image of a snake debossed into the cover, with the text "In the face of ambiguity -- Refuse the temptation to guess" on it.

Well, OK, that's weird.

My wife snatches it and says: "I had that custom made by a book binder". I flip through it. It contains the Python 3.9 language reference, and the PEP 8 styleguide.

While I usually dislike paper dev books because they become outdated over time, I'm perplexed by this one, because of how much effort and craftsmanship went in to it. I'm even a little jealous.

So, this morning I was putting dishes into the dishwasher, and she says: "Please let me do that". I ask: "Am I doing anything wrong?"

Wife responds: "Well, it's not necessarily wrong, I mean, it works, doesn't it? But your methods aren't very pythonic. Your conventions aren't elegant at all". I don't think I've heard anyone say the word "pythonic" to me in over a decade.

And just now my wife was looking over my shoulder as I was debugging some lower level Rust code filled with network buffers and hex literals, and she says: "Pffffff unbelievable, I thought you were a senior developer. That code is really bad, there are way too many abbreviated things. Readability counts! I bet if you used Python, your code would actually work!"

I think I might have released something really evil upon the world.

So... I just remembered a story that's perfect for devrant.

My brother got into engineering in university, and during the second semester they had their introductory class to programming. They had weekly homeworks that the lecturer would check and give grades accordingly.

The factors that could influence the grading were: execution (meaning that the code would excecute as intended), efficiency and readabilty. The weeks passed and everyone was doing well, getting fairly good grades. Everyone was happy.

Until one day a random guy we'll call bob got the worst grade possible. Bob wasn't a bad student. He had over-the-average grades in all the weekly homeworks and even impressed the professor in some. Naturally, he was baffled when he saw his grade on the google spreadsheet. He was pretty sure his code ran well. He always tested it on different machines and OSs. So, at the end of the class, he went straight to the helper of the class, in a pretty imperative manner, to demand to know how the fuck he got that grade. It's impossible he got excecution, efficiency and readabilty, wrong. All three wrong? Impossible. Even the stupidiest kid in the class had some points on readabilty.

"Oh, so you are Bob. Huh?" said the helper in a laid-back attitude. "Come with me. Prof. X is waiting for you in his office."

This got Bob even more confused. As they approached the office, the courage he had in a first moment banished and gave way for nervousness and fear.

The helper nocks the door. "Prof., Bobs here"

As soon as Bob sits in the chair in front of Prof. X's, he knew something bad was coming.
"In all these years of teaching..." said Prof. X hesitantly. "In all these years of teaching I have not come even close to see something similar to what you've done. You should be ashamed of yourself." Needless to say, Bob was panicked.

"In all these years I have not seen such blatant mockery!" added the professor. "HOW THE FUCK DID YOU EVEN DARE TO SEND A HOMEWORK WITH SUCH VARIABLE NAMING" That's when Bob realised the huge mistake he made. "NEVER IN ALL THESE YEARS I HAVE SEEN SOMEONE NAME HIS VARIABLES *opens the file on his desktop *: PENIS, SHIT, FUCKSHIT, GAYFUCKING<insert Prof. X's name>MAN, GOATSE, VAGINAVAR, CUMFUNCTION, [...]" The list of obcenities went on and on. In each word, the professor hit the table harder than the last time.

Turns out Bob felt so in comfort with the ease of the course he decided to spice things up by using "funny naming conventions" while coding, and then tidying everything up before uploading the homework. This week he forgot, and fucked it big time.

So remember folks, always check your code before committing/giving it in/production. And always adhere to naming conventions.

Just finished writing a script with all the classes and variables named after the characters from Sherlock Holmes. I regret nothing.

OH MY GOD

WHO NAMES A CONFERENCE ROOM AFTER AN -ADDRESS-??

At my new job, we had all day training on Friday. It was emphasized many times that we should not be late. I look at the meeting invite many times, and it says [123 Fake], with Fake being a Very Well Known Street, and I see on Google Maps that there's an office building there. Great, we must have an off-site training facility to help our clients become certified in our product. It doesn't say which floor, but I assume the small space we have in that large office building will become evident once I check in with lobby security.

Friday morning comes, I get to the office building 20 minutes early, and try to check in. They've never heard of my company. Maybe there's a computer lab we rent out? No, they don't know anything about that. I don't have work email or slack set up on my phone yet, so who do I call? I try reception, no one answers. Eventually I call our customer support line.

I shouldn't be at 123 Fake St. I should be at the office. Because that's the name of the conference room!

YOU HAD ONE JOB, ROOM NAMER!

Last night my boyfriend and I tried to think of worse names for conference rooms. The only ones I could think of were "meeting canceled" (but with that, at least I would be in the correct fucking building!) or just naming every conference room "conference room". Here's the thing: there's not just one 123 Fake St room! There's two of them right next to each other! So you can easily show up and think, I remember I was supposed to be in this room, but which one?

And I'm not even the first person to make this mistake. CLIENTS have gone to the wrong building before because they get included on meeting invitations that include conference room names! WTF!

It's pretty common to have Chicago conference rooms named after neighborhoods, or iconic buildings, etc. But nobody is going to think, "meeting in Bucktown? I'll just wander around the neighborhood until I find people with laptops". It's obviously a conference room. BUT A FUCKING ADDRESS OF A NEARBY OFFICE BUILDING? It's not even an iconic of a building!

Names matter. I care a lot about names in code. I never realized it could apply to the physical world as well. So now I am on a mission to change the names of these Goddamm conference rooms so I'm the last person to be directed to the wrong fucking building.

OH, and I'm out $9 for a taxi ride and a pair of gloves that got lost in the taxi so that's GREAT.

Variable naming conventions..

Don't you hate when you switch languages and start to mix up naming conventions?

PineScript is absolute garbage.

It's TradingView's scripting language. It works, but it's worse than any language I have ever seen for shoddy parsing. Its naming conventions are pretty terrible, too:

transparency? no, "transp"
sum? no, cum. seriously. cum(array) is its "cumulative sum."

There are other terrible names, but the parser is what really pisses me off.

1) If you break up a long line for readability (e.g. a chained ternary), each fragment needs to be indented by more than its parent... but never by a multiple of 4 spaces because then it isn't a fragment anymore, but its own statement.

2) line fragments also cannot end in comments because comments are considered to be separate lines.

3) Lambdas can only be global. They're just fancy function declarations. Someone really liked the "blah(x,y,z) =>" syntax

4) blocks to `if`s must be on separate lines, meaning `if (x) y:=z` is illegal. And no, there are no curly braces, only whitespace.

There are plenty more, but the one that really got me furious is:

98) You cannot call `plot()`, `plotshape()`, etc. if they're indented! So if you're using non-trivial logic to optionally plot things like indicators, fuck you.

Whoever wrote this language and/or parser needs to commit seppuku.

PHP's lack of consistence in naming conventions with built-in functions. For example, str_split() and strlen().

Hello, I just want to let you know I'm working on a 15 year old product and it is currently in production.

It uses Angular.js and one of the earliest versions of React.js. I cannot use ES6, we don't have Babel, no JSX syntax, no CSS preprocessor. No webpack.

I must support browser since IE6 with an ES3 syntax. (luckily I got some some polyfills for an ES5 syntax)

When I build a component I have to call React.createClass and React.createElement.

The render() function is basically a nested pile of React.createElement.

There is no documentation for this product, no tests, no anything.

I had to reverse engineer it in order to understand how it works.

The code base uses mixed programming styles and naming conventions, plus thousands of little js files.

Oh and obviously no hot reload, every time I make a change I have to restart everything.

Please, send help.
I'm in danger.

Sincerely,
An underpaid developer

....
I'm not crying, you are crying...

Remember when folders/files were named like this when you were young (or was it just me 😅):
- project.xyz
- project-better.xyz
- project-last.xyz
- project-last-last.xyz
- project-final.xyz
- ...

Me: So what you are doing in the IT field?
Him: I am hacking bank websites.
Me: OK, that's cool. It is good in free time. What is your actual job?
Him: I am seriously hacking the bank Web site!
Me: Trust me, if you seriously doing that you will never ever mentioned it...
Him: No, I am doing it legally... The bank hiring me to try to hack the website...
Me: OK, you mean that you are cyber security tester?
Him: That is almost the same...
Me: So you are tester?
Him: I am hacking bank's websites...
Me:....

Why Pdf is a new religion:
Pdf is complicated.
Pdf is ubiquitous.
Everyone follows their own conventions and calls it a standardised pdf.
Conversion from pdf to any other format is problematic.

Keep adding to the list...

The hardest part of programming is not the inner workings of the chosen frameworks and tech.

It's the damn naming.

I will spend hours trying to figure out what to name things for sense and clarity and then a fraction of that time coding it together.

*me, staring out the window*

"Hey dude can you--"

"Ssshhh. I'm naming things."

Just got picked up for a project. 20,000+ code base, no comments, no docs, variable names like x, xx, xxx, no function name conventions, and a mishmash of Czech, French and English class names.

I thought this job was too good to be true. #fml

Getting really sick of brand naming conventions these days, Youtube just suggested me a video called "Samsung Galaxy S20 Ultra vs iPhone 11 Pro Max!"

Like what are those, Transformer names? 🙄

I'm editing the sidebar on one of our websites, and shuffling some entries. It involves moving some entries in/out of a dropdown and contextual sidebars, in/out of submenus, etc. It sounds a little tedious but overall pretty trivial, right?

This is day three.
I learned React+Redux from scratch (and rebuilt the latter for fun) in twice that long.

In my defense, I've been working on other tasks (see: Alerts), but mostly because I'd rather gouge my freaking eyes out than continue on this one.

Everything that could be wrong about this is. Everything that could be over-engineered is. Everything that could be written worse... can't, actually; it's awful.

Major grievances:
1) The sidebars (yes, there are several) are spread across a ridiculous number of folders. I stopped counting at 20.
2) Instead of icon fonts, this uses multiple images for entry states.
3) The image filenames don't match the menu entry names. at all. ("sb_gifts.png" -> orders); active filenames are e.g. "sb_giftsactive.png"
4) The actions don't match the menu entry names.
5) Menu state is handled within the root application controller, and doesn't use bools, but strings. (and these state flags never seem to get reset anywhere...)
6) These strings are used to construct the image filenames within the sidebar views/partials.
7) Sometimes access restrictions (employee, manager, etc.) are around the individual menu entries, sometimes they're around a partial include, meaning it's extremely difficult to determine which menu entries/sections/subsections are permission-locked without digging through everything.
8) Within different conditionals there are duplicate blocks markup, with duplicate includes, that end up render different partials/markup due to different state.
9) There are parent tags outside of includes, such as `<ul>#{render 'horrific-eye-stabbing'}</ul>`
10) The markup differs per location: sometimes it's a huge blob of non-semantic filthiness, sometimes it's a simple div+span. Example filth: section->p->a->(img,span) ... per menu entry.
11) In some places, the markup is broken, e.g. `<li><u>...</li></u>`
12) In other places, markup is used for layout adjustments, such as an single &nbsp; nested within several divs adorned with lots of styles/classes.
13) Per-device layouts are handled, not within separate views, but by conditionally enabling/disabling swaths of markup, e.g. (if is_cordova_session?).
14) `is_cordova_session` in particular is stored within a cookie that does not expire, and within your user session. disabling it is annoying and very non-obvious. It can get set whether or not you're using cordova.
15) There are virtually no stylesheets; almost everything is inline (but of course not actually everything), which makes for fun layout debugging.
16) Some of the markup (with inline styling, no less) is generated within a goddamn controller.
17) The markup does use css classes, but it's predominately not for actual styling: they're used to pick out elements within unit tests. An example class name: "hide-for-medium-down"; and no, I can't figure out what it means, even when looking at the tests that use it. There are no styles attached to that particular class.
18) The tests have not been updated for three years, and that last update was an rspec version bump.
19) Mixed tabs and spaces, with mixed indentation level (given spaces, it's sometimes 2, 4, 4, 5, or 6, and sometimes one of those levels consistently, plus an extra space thereafter.)
20) Intentional assignment within conditionals (`if var=possibly_nil_return_value()`)
21) hardcoded (and occasionally incorrect) values/urls.

... and last but not least:
22) Adding a new "menu sections unit" (I still haven't determined what the crap that means) requires changing two constants and writing a goddamn database migration.

I'm not even including minor annoyances like non-enclosed ternaries, poor naming conventions, commented out code, highly inefficient code, a 512-character regex (at least it's even, right?), etc.

just.

what the _fuck_

Who knew a sidebar could be so utterly convoluted?

i was asked to start a new project, and another dev was brought onto the team shortly after. as soon as he joined, straight away he started an entirely new project and worked on it through the whole weekend, then came back on monday and just sort of pasted his files into/over the code i had already started and was working on, with no regard for folder structure or naming conventions or anything. his work was even split between 2 almost identically named namespaces (both of which were completely different to the existing project namespace) and his shit broke everything i did in the first place. the cherry on top is that none of his work was even functional, it was purely dummy/mockup web pages that weren't linked to any sort of backend.

when i asked him wtf he thought he was doing, he kept saying "i didnt touch your code" and refused to acknowledge that pasting a project over a different project can break stuff, then said it "wasn't his fault that i'm slow and not keeping up". and just kept saying vague bullshit about how i have to do it his way because he "has more experience"

he had no idea what my previous experience was, he had never asked and i had never told him, he just decided that he had more experience than me.

i dug through the shit and found out that he didn't just break my work, he had actually purposely deleted it when he realised it was getting in the way of his spaghetti. i showed him the commit and confronted him with it and all the cunt said was "well the good news is, you know the fix" and kept trying to dismiss me in the most disrespectful ways he could think of. i eventually snapped at him (long overdue at this point) and told him that any experienced developer would not commit code that didn't even fucking compile, especially when they're the one who broke it, and that he needs to grow up. of course he then complained that i was being unprofessional.

our manager decided we should go with fuckfaces """code""" without even looking at the work either of us had done, purely because fuckface is older than me and that's how the world works.

in the end i just told my manager that i refuse to work with the guy and he could either take him or me off the project (guess who he picked) or i quit.

after a few months of the guy failing to deliver any of even the basic functionality that was asked for, the entire project got scrapped, and the dude just quit once everyone realised he was literally just larping as an experienced dev but couldn't accomplish simple tasks.

i never received an apology from anybody involved.

Trash, trash, trash.
Who the fuck writes this shit?

Who the fuck lets these trash should-be-junior devs roll their own crypto? and then approves it?

The garbage heap of a feature (signing for all apis) doesn't follow Ruby standards, doesn't follow codebase conventions, has `// this is bridge` style comments (and no documentation), and it requires consumer devs to do unnecessary work to integrate it, and on top of all this: it leaks end-user data. on all apis. in plaintext.

Fucking hell.

I spent an hour arguing with the CTO, pushing for having all our new products' data in the database (wow) with an API I could hit to fetch said data (wow) prior to displaying it on our order page.

He never actually agreed with me, but he finally acquiesced and wrote the migrations, API, and entered my (rather contrived) placeholder data. (I've been waiting on the boss for details and copy for three days.)

Anyway, it's now live on QA. but. I don't know where QA is for this app, and it's been long enough that i'm kind of afraid to ask.

Does that sound strange?
well.

We have seven (nine?) live applications (three of which share a database), and none of their repos match their URLs, nor even their Heroku app names. (In some of these Heroku names, "db" is short for the app's namesake, while in the rest it's short for "database").

So, I honestly have no idea where "dbappdev" points to, and I don't have access to the DNS records to check. -.-

What's more: I opened "dbappdev" on Heroku and tested out his new API -- lo and behold! it returns nada. Not a single byte. (Given his history I expected a 500, so this is an improvement, I think. Still totally useless, however.)

And furthermore: he didn't push the code to github, so I cannot test (or fix) it locally.

just. UGH.

every day with this guy, i swear.

Proud dev moment : as I was following the variable naming conventions from my company, I got to name a variable "l_o_tr" 💪

teacher - gives a lecture about Java Naming Conventions...

Opens Notepad, ( he doesn't use an IDE, when I asked him he told he haven't worked on a IDE before )

and does this

public int user_account_number;

me - *wtf*

thanks God he didn't mess up with the braces and indentation otherwise I would have got eye cancer( already the white theme of notepad was causing nausea)

We have this weird db naming convention requirement by the client all table names should be of 4 letters. And guess what somebody thought of naming a table 'ANUS'

One time a former colleague reformatted all the code because he was very strict on code conventions.. so.

If (1==1)
{

Instead of

If (1==1) {

After some discussion on why he should never do this I denied him the rights to commit any longer..

Also..

One time a user requested a feature.. he wanted a drop down with some values without specifying where he wanted it. To our best knowledge we put it somewhere where we thought it would be usefull.. for instance when it is a car model drop down ypu expect it to be somewhere near a car screen right.. little did we know that he didnt have any rights to acces that screen at all hhahaha.. after that he came yelling in our room telling us to think for him.. in not so light words I told him that he should write his stories properly and that if he creates crappy stories he leaves me with a lot of freedom of interpretation of his stories so stop crying and get the fuck out of my room..

Its not that I get angry easily but I cant handle dumb people that do dumb stuff around me..

One of my colleagues shared this today. Spot on.

This one time I developed some useful plugins and a command line interface for the platform we built at work.

Then when it was done I thought it had some good value so I created a pull request to donate it to the platform. That same day I got 3 complaints that my pull request did not conform to conventions and that there was no ticket for it and they complained about the fact that it made their jobs harder.

It was in fact the last time I developed something for work in my spare time.

Opening somebody else's code(11000+ lines in 2 js files) only to find a 100+ "var a" declarations and naming conventions like var chart1, var chart2. Best part? Not a single comment. Even better? The one who wrote the code doesn't remember what does what.

Today I was talking to my manager about html and css.

As i was explaining certain things about the structure of the files and the naming conventions for the css classes I mentioned the body of the document.....but got...er...distracted...yes distracted...and said booty instead of body.

She started laughing and I made a tomato look pale because of how red I got. I zipped my hoodie all the way up and talked from the hood hole around my face.

Best solution ever.

Hey Kids, wanna buy some JAVA ?

Currently, I am going through a legacy application built in microsoft access back in 90s.

* No Comments
* No Relationships between tables
* Random code that does nothing
* Weird form layouts
* Weird naming conventions

I need to copy this functionality into modern version using SQL Server Management studio and asp.net core, I also need to kill myself because none of this fucking shit fucking fuck makes sense.

I do my best to write clean and concise code along with comments but after this ordeal I am going to up my game because nobody should need to suffer through spaghetti code and stupid logic that is uncommented.

😶

That's it, I'm done. My sincere condolences go to the poor soul that will have to maintain this complete and utter crap of code, as I have been doing the past 2 weeks.

3-4 big 4K+ lines files of completely unindented, practically undocumented, interspersed HTML, PHP, JavaScript and CSS! All in the same file.

All the function and variable names are complete nonsense. You might as well have smashed your head against the keyboard and let whatever came out be the names.

You took all the naming conventions that you could find and unleashed your seriously damaged imagination. lowerCamelCase, UpperCamelCase, snakecase, everything in the same fucking function name.

I really needed the money from this project. But I'm done. My mental sanity is more important that try to figure out how to make a decent and usable webpage of THIS COMPLETE DISASTER.

You, the one before me. If you wanted to make sure that no one else besides you could work with this crap, then congrats, YOU FUCKING DID IT WITH HONORS. FUCKING SUMMA CUM LAUDE. PhD and all.

dear api author at my company pt. 2:

If you're gonna create an api method that takes some arguments.

And one of those arguments is an array.

THEN MAKE THE FUCKING ARGUMENT'S NAME PLURAL YOU FUCKING PIECE OF SHIT.

REPEAT WITH ME, MOTHERFUCKER.
ARRAY, PLURAL, NON-ARRAY, SINGULAR.

I need to pass a shitload of filters for the data for this table, and for every suckin fuckin filter I need to singularize this shit. Thank god for es6.

I know this sounds like nitpick, but I swear to fucking alpha omega this guy is inconsistent as fuck.

Every time it feels like he makes up a new rule.

Sometimes I need to send arrays of ids, other times arrays of objects with an id property on each.

He uses synonyms too, sometimes it's remove, other times erase.

PICK ONE MOTHERFUCKER.

If you can't do the basic things well, then what is to expect of more advanced stuff?

Naming conventions you fucking idiot, follow them. It's programming 101.

You're already sending them as plural in the fucking response. Why change them for the request?

And that's just style, conventions.

This idiot asshole also RARELY DOES ANY FUCKING CHECK ON THE ARGUMENTS.

"Oh, you sent a required argument as null? 500"

We get exceptions on sentry UP THE ASS thanks to this useless bone container.

YOU'RE SEEING THE EXCEPTIONS TOO!!!!! 500'S ARE BUGS YOU NEED TO FIX, YOU CUMCHUGGER

And sometimes he does send 400, you know what the messages usually are?
"Validation failed".

WHYYYYYY YOU GODDAMN APATHETIC TASTELESS FUCK???
WHAT EXACTLY CAUSED THE FUCKING VALIDATION TO FAIL????

EXCEPTIONS HAPPEN AND THANKS TO YOU I HAVE NO IDEA WHY.

The worst of all... the worst of fucking all is that everytime I make a suggestion to change shit, every time, you act like you care.
You act like the api is the way it is because you designed it in a calculated manner.

MOTHERFUCKER. IF A USER HAS ONLY PRODUCT A, THEN HE SHOULDN'T BE ABLE TO ACCESS DATA FOR PRODUCT B. IT IS NOT ENOUGH TO JUST RESTRICT SHIT WITH ADMIN ROLES. IDIOT!!!!!

This is the work of someone who has no passion for programming.

Frontend dev: Hey, could you break HTTP conventions and change the API so I don't have to manage the context of the request?

maybe I'm really pedantic, but I fucking hate people who write code without a consistent form or style... putting spaces or breaks randomly or not at all is SO fucking annoying and I'm wasting time converting it to a more readable form... THEY FUCKING COULD HAVE DONE THAT IN THE FIRST PLACE FOR FUCK SAKE!!

Not usually a person to rant about spacing and conventions but this is great.

4 devs, all using IntelliJ. Now IntelliJ auto-changes tabs to spaces which is nice, and GitHub doesn’t really care as long as the spacing is consistent. Now here is the fun part: 2 devs have 4 spaces per tab, 1 has 3 spaces, 1 has 5 spaces.
GitHub merge conflicts everyWHERE.

And yes it isn’t the old 2 vs 4 spaces. It’s 3 vs 4 vs 5 somehow

personalproject C++ codebase:
- Clean code,
- 1 class per file,
- naming conventions
- comments .
- No more than 10 files per folder

Work C++ codebase:
- 22 classes per file.
- Classname not the same as file name
- weird variable names CmdStng
- All files in one source folder.
- Source control from 20 years ago

Me every time I cannot find anything I wondering why it is in a different file on line 3574 inside another class with an unrelated filename

I love static sites and fancy new frameworks. Had an interview some time ago at a medium sized company. They specifically wanted someone to build static sites and introduce the company to Vue and Gridsome.
I got really excited for my first project. It was a wordpress site and I had to build a custom WP theme for it. Not exactly what I expected. Also I had no prior PHP knowledge, nor any experience with Wordpress. So I got really upset, because it wasn’t the technologies I was used to.
The first week was hard, I wanted to quit. But once something clicked. And I realized I know this. This is not PHP, not Wordpress, not Vue, but just simply a programming language. At the core everything programming language is the same. PHP became comfortable, Wordpress conventions didn’t bother me. I realized I can use great technologies with WP too. I get to know twig, added some sass, compiled everything nicely with webpack. And after a month I have a beautiful, fast and efficent site. I love it.
I realised that I don’t love the languages and frameworks. I love coding itself. I love creating efficent and reliable, clean code. No matter the architecture.
And my advice for you is to stop hating particular languages and serious debates on what is better, and hating your job when you can’t code in your new shiny framework. Love coding itself, because it’s a wonderful activity. We are creators, we are artists. Not <insert specific programming language here> developers.

R is the worst language.

* Indices start at 1, so you have to fix all your calculations by either +1 oder -1. It sucks

* Vectors and Lists are both neither vectors nor lists

* Data frames dont have a proper api. Simple operations like add or remove are a pain.

* The naming „conventions“ suck. Why on earth would add dots in your identifiers? You never know if its an object, a value, a function.

* The namespace is cluttered. If you import two libraries that deal with the same problem domain, it is likely that they define functions with clashing names that will overwrite each other defined on import.

I'm a jr developer. I started off in automation testing and don't mind it but the testing codebase is cancer, doesn't follow basic Java conventions even basic naming conventions like camelcase, and the tests are super slow using hardcoded Thread.sleep(). Since the automation tests are not automated, I have to run manually. YES manually, every morning I wake up early at 7am to run the 2.5 hour long tests (7am because this before people get to work and when the application goes back online). I run this bitch and monitor them but most of them fail anyways. I also have to write a email report on the results which means I have to explain why shit is failing so I have to debug all this crap. This shit literally eats up an additional 2-3 hours of my work day everyday and the time is not even accounted for. ALSO, since it's running on my laptop, it makes my computer slow most of the day. If I have to debug, I can't have the browser be headless so fuckin chrome browsers be popping up every 2 minutes. I did this for legitimately 8 sprints until I decided enough was enough and bitched about it and the team told me I had no choice. I eventually got them to push towards automating it but it's still in progress so I'm still running this dumb shit. The contractors try to take advantage of me any way they can by giving me mindless bitch work they don't want and they know I don't usually say no since I'm a jr resource. I hate running the fucking automation tumor. Sometimes I go into the meeting rooms alone to scream.
I feel like I'm wasting my life away and not learning as much as I could somewhere else

Programming challenges:

Easy: Hello World!
Medium: Matrix multiplication
Hard: Artificial intelligence
Impossible: Coming up with meaningful names for variables and scripts...

Someone at work snuck something past the censors.

Our Hadoop servers all have "bigd" in their name 😂

We're no strangers to code
You know the conventions and so do I
A full commit is what I'm thinking of
You wouldn't get this from any other dev

I just want to tell you about my problem
Gotta make you solve it for me

Never gonna git you up, never pull you down
Never gonna rant around and rebase you
Never gonna merge your branch, never gonna say $#@*!!
Never gonna risk a cry and build you

So I'm a perfectionist, especially when with code, smells, solid, design patterns, naming conventions, etc and I be have this co-worker that blackmails me every time he doesn't want to do something saying "I don't know it so my code is gonna be ugly".

Naming is hard.

I have discovered a fresh hell

Some guy I’ve never met or heard of in the office lobbed a comment at one of my *approved and merged* pull requests. He doesn’t say anything specific, only that my REST urls are not in line with naming convention. That’s all he says, and I’ve already walked the URL consumers through the code and given them the URLS.

I’m really annoyed that this guy won’t just say what he has in mind, but fine whatever this is a professional environment and developers are not known for being a diplomatic people. Let it go and get your work done!

I do some googling and find an obvious change that needs to happen- I implement it, open a new pull request and inform my URL consumers of the change.

This rando still isn’t satisfied and still won’t say what needs to change. I am on round 3 of this wonderful cycle and this guy is acting all fuckin HAUGHTY about it. “Here is a list of conventions I found googling, you should read them even if it takes 4 hours because it will benefit your career”

Sure dog you’re probably right on that one but we are in a professional environment and at this point you are holding up production so you can wave your dick around! Just SAY WHAT YOU MEAN SO WE CAN MAKE THE CHANGES AND GET OUR WORK DONE

Both apps I'm working on have legacy code:

iOS app has 100's and 1000's of lines of code with no documentation, no proper naming conventions and cut and pasted code off the net.

Android app has skeleton code from a Spanish taxi app + remnants of a funeral webcasting app, there's also the same no documentation, bad naming conventions and cut and paste code off the net.

The server is also as bad, it had methods that we're never used, I for one don't fully understand the server but from what I can see it's a mess.

I had a hard time understanding both apps and gladly majority of the modifications I made we're not including existing stuff, so I guess I just basically pilled my code onto of the already existing software.

I would have gladly started from scratch given the chance.

What kind of variable conventions do you use?

timesincereseat
TimeSinceReseat
timeSinceReseat
TIMESINCERESEAT
TIME_SINCE_RESEAT
time_since_reseat
global{'tsr'} # so nobody can read it :)

Quirks of.... PHP 😂😂😂😂

It's just a quirky language, you either love it or you hate it, or you hate it because you caught the bandwagon in town.

Weirdest quirk though, would have to be function naming conventions and order of arguments.

Shit be crazy at times but you get used to it.

At my first job, our employee email addresses followed a somewhat unusual naming convention: last name plus first initial, e.g. smithj@company.com for John Smith.

They were ultimately forced to change it, though, when they received a complaint from a new employee. His name? Tommy Shi...

Katie, we get it, you know and like Scala. You mention this often.

It doesn't make you superior to everyone else. And it certainly doesn't mean you have to pretend every language is Scala, ignore any language-specific paradigms and conventions, and bastardise every bit of code you write until it's done in the most weirdly Scala-ish functional way possible even when it makes zero sense to do so.

Stick with the conventions of the existing language & codebase you muppet. Yeah, it's boring and won't turn you on, but it's a hell of a lot more readable than a random bastardised mixin in the middle of another existing inheritance hierarchy.

So here I am reinventing the wheel making an HTTP server in C.
Finished implementing HTTP/1.1 and WebSockets support and now I find out the current thingy is HTTP/2.
Well that's fine, I'll add support for that later. In fact I kinda dig it since it uses binary conventions instead of plain text ones.
I dig a little bit and find out there already is an HTTP/3 going around which uses UDP.
Why me.

Something that really annoys me is when people abuse the lax semicolon rules in JavaScript. Personally I believe semicolons should be a standard and always used in a language like JavaScript, and while the loose rule on semicolons may be considered convenient when one is forgotten every now and then, it is /not/ meant to be abused and semicolons completely unused. It's particularly annoying when I have to work on a group repo at work and the standard is to not use semicolons. JavaScript to me is much more similar to a C style language than something like Python, so even though the language is built to be loose and easy conventions such as bracket scoping and semicolons should be kept and practiced.

Python prorammers ignore this.

Oh so now we got a fucking new fight started on devRant on which line to put brackets on.
Fucking why!!??
Both conventions basically mean same thing and even no fucking ide is partial about the fact.
Stop it!

-not commenting
-leaving console logs behind in production
-not testing if it works in IE
-using root too much
-using if instead of switch
-never staying consistent with naming conventions
-starting projects and never finishing

I was reminded of people's posts about preferred text editors in another post, so I thought I'd do the same, but also add some super old technology that I used along the way.

The first text editor I consistently used was pico. I used it to write my first webpage at school.edu/~username. It was a natural choice, because the it was the default text editor in pine, which is what we would all use for our email after opening a serial connection to the college's Digital Unix server. Or if we were the lucky ones who had a computer in a wired dorm, telnet. My dorm was not wired until my sophomore year.

I got my first job in tech in 2001, working as a night shift tier-one support technician. By this time, most people were using web based email, or POP3, but I wanted to keep using pine (or elm, or mutt) because I was totally in love with the command line by this time, and had been playing with Linux for two or three years by now. I arranged a handshake deal with a guy in my home town who had a couple well-connected NetBSD servers, to let me have an account on one for email and web hosting (a relatively new idea at the time).

I recall telnetting into my shared hosting account from the HP-UX workstations we had in the control room. I would look at webpages on HTML conventions and standards, and I kept seeing references to this thing called vi. I looked into it more deeply, and found that it was a text editor, and was the reason I always had to CTRL-Z out of elm. I was already finding pico to be lacking, so I found a modern implementation of vi called vim that was already installed on the aforementioned NetBSD server, and read through vimtutor on it. I was hooked instantly. The modality massively appealed to me, and I found editing files to be an absolute delight, compared to pico, and its nascent open source offspring/successor, nano.

My position on that hasn't changed in the years that have passed since then.

What's your text editor origin story?

My failed interaction with a girl:
So I go to a convention at the university.
It's nice I'm having fun, I see a girl dressed as Hermione, she is cute so I go talk to her for a little we joke around I'm really starting to like her. Then I say bye and hang out with friends for the rest of the evening. I see her leaving so I run to her and after catching up to her I ask if I could have her phone number. She says yes and enters her number on my phone. I'm super happy. I excitedly wait for the next day's evening to message her. We message for a while the next day she messages good morning, so I think things are going well, she must like me too right ? I mean we glanced at each other at the convention, she gave me her phone number and messaged good morning so I'm pretty sure she does...

Turns out she doesn't, she says she thought I wanted to be friends...
WHAT ?! FRIENDS ?? Are you 12 ? What friend would run to you to get your phone number and after getting it there would be a stupid grin on his face ??? She looks at 9gag and doesn't know the most overly used meme of "friendzone" ? Unbelievable either she was screwing with me or she is just that socially dense. So after that I'm pretty mad but I don't say any mean things I just accept the fact like a gentleman and carry on with my life. But also feeling depressed after believing we actually had a connection. Ugh I guess back to the coal mines for me huh, stupid conventions 😒

Another gem from same co-worker who is a "Senior Developer". Unnecessary function that fills a dropdown box(?!) with numbers 1-100. I really really hate this guy.

Bonus: Best Practice Example of Naming Variables...

Why the fuck do these little shits use variable names like p,q,pq?
Wtf are you? Babbler Baboon !

So for almost all of my c++ assignments I've recieved various emails from the instructor about things like "incorrect header guard" and "library inclusions out of order".

The first being that I didn't include the namespace inside of the guard (I did "FILENAME_H" instead of "NAMESPACE_FILENAME_H")

The second is that I accidentally included header files from my project before any of the standard libraries. This one wasn't even intentional, it was caused by vscode when it formatted/prettified the file.
EX:
#include "test.h"
#include <iostream>

In my opinion these seem pretty nitpicky and, especially that first one, appear to be more like naming conventions or best practices than something to deduct marks for.

On the flip side though I did accidentally store a couple functions in the global namespace which I understand isn't particularly safe. I also made a couple one line conditional statements that simply never evaluate to true, but I didn't think this was a huge deal.

I don't normally code in any of the c languages outside of college so I'm not sure how important these are to actually follow. I've apparently been deducted an entire 10 percent off the assignment because of the head guard. I know that every professor has different criteria for deducting marks, but even this seemed rather unnecessary.

What does everyone think?

Some of these things are not like the others. One of these people is a tv scientist not an actual data engineer or data scientist, while another is an activist and while is extremely respected, has no room in a data+ai talk -.-

When I wrote my first algorithm that learns...

So in order to on board our customers onto our software we have to link the product on their data base to the products on ours. This seems easy enough but when you actually start looking at their data you find it's a fuck up of duplication's, bad naming conventions and only 10% or so have distinct identifiers like a suppler code,model no or barcode. After a week or 2 they find they can't do it and ask for our help and we take over. On average it took 2 of our staff 1-2 weeks to complete the task manually searching one record of theirs against our db at a time. This was a big problem since we only had enough resources to on board 2-4 customers a month meaning slow growth.

I realized when looking at different customers databases that although the data was badly captured - it was consistently badly captured similar to how crap file names will usually contain the letters 'asd' because its typed with the left hand.

I then wrote an algorithm that fuzzy matched against our data and the past matches of other customers data creating a ranking algorithm similar to google page search. After auto matching the majority of results the top 10 ranked search results for each product on their db is shown to a human 1 at a time and they either click the the correct result or select "no match" and repeat until it is done at which point the algo will include the captured data in ranking future results.

It now takes a single staff member 1-2 hours to fully on board a customer with 10-15k products and will continue to get faster and adapt to changes in language and naming conventions. Making it learn wasn't really my intention at the time and more a side effect of what I was trying to achieve. Completely blew my mind.

If you're going to fucking build a fucking templating system, you fucking better make sure it fucking follows proper structure -- Bootstrap, vanilla CSS, whatever -- so that when I follow conventions your fucking shit doesn't fucking shit all over the fucking place in fifty fucking different ways.

Few years ago as a junior android dev with couple years of self taught experience of working in startups I submitted a simple android app assignment for a junior android dev role. Assignment had only like 8 requirements so I followed them to the letter. That didn't end well.

App was simple just 3 screens. Login screen with username and password input fields, login button.

Had to call a login endpoint after login button was clicked, redirecting to home screen, calling items endpoint, displaying a list of items and when an item was clicked passing item data and redirect to item details screen.

Needless to say big swinging dick senior was not impressed. UI was not perfect, I forgot to display a loading animation when fetching data, didnt handle back button properly.

I agreed with some points but other comments were clearly just nitpicking: his preferred variable naming conventions, his opinions on architecture that was not up to his standard (official google arch at the time was not up to his standard).

He also was mad that app wasn't prepared for release to googleplay (another out of the ass requirement). Like I would prepare a 3 screen app for prod release that he will forget ever existed after 20min of his review.

Lots more of nitpicking, encapsulation this encapsulation that, omg now hes shocked that there are a few warnings after the project is built.

Regardless my self confidence was destroyed at that point and after few more negative experiences I dropped android dev alltogether for a couple years and switched to game dev.

After game dev ran its course I went back to android dev and found a supportive place where I could grow.

Looking back, they were actually hiring atleast a mid level for a junior position but I was grilled as a senior. The guy literally didnt wrote any single positive thing in that review about my code even tho my senior peers said my project was decent back then, its just that I didnt handle a few edge cases and that's all.

I looked up the guy in linkedin, turns out hes a uni dropout who posts all books that he red about software dev in his education section of his linkedin profile. Found a bunch of other narcissistic stuff on his profile. Guy was a fucking idiot. Even if I worked under him it would have probably sucked.

Learned some important lessons I guess. Always get a second, 3rd and 4th opinion and dont take criticism too seriously. Always check what kind of person is providing feedback.

Ok, here goes...

I was once asked to evaluate upgrade options for an online shop platform.

The thing was built on Zend 1, but that's not the problem.

The geniuses that worked on it before didn't have any clue about best practices, framework convention, modular thinking, testing, security issues...nothing!

There were some instances when querying was done using a rudimentary excuse for a model layer. Other times, they would just use raw queries and just ignore the previous method. Sometimes the database calls were made in strange function calls inside randomly loaded PHP files from different folders from all over the place. Sometimes they used JOINs to get the data from multiple tables, sometimes they would do a bunch of single table queries and just loop every data set to format it using multiple for loops.

And, best of all, there were some parts of the app that would just ignore any ideea of frameworks, conventions and all that and would be just a huge PHP file full of spagetti code just spalshed around, sometimes with no apparent logic to it. Queries, processing, HTML...everything crammed in one file...

The most amazing thing was that this code base somehow managed to function in production for more than 5 years and people actualy used it...

Imagine the reaction I got from the client the moment I said we should burn it to the ground and rebuild the whole thing from scratch...

Good thing my boss trusted me and backed me up (he is a great guy by the way) and we never had to go along with that Frankenstein monster...

I always try to explain the new coding conventions to my team but they think it's funny and should not be taken seriously [facepalm]

"Don't go too crazy with the design, this is just quick to get it out, this is a one time deal" - management

Half a year later...

"Well if you would properly design components up front, it wouldn't be so hard to extend the code" - management

Well if there were some sort of god forsaken process in place, with assigned tasks, priorities, iterations, and conventions, maybe everything wouldn't be a last second shit show and there would actually be forward progress on a project instead of throwing shit over the wall and hoping everything lands in the correct places.

So I just started going to university and have a subject called "programming", we are taught Java, Haskell and Prolog. Every week there is a sheet with homeworks, programming tasks. Often we get something like a boilerplate, so we implement some methods and stuff like that. Those tasks are prepared and created by scientific assistants. They upload the boilerplate and sheets. Take a look at the programming style they follow in Java. Actually I can't find a pattern they follow, except from the spacing between the lines. We are 1000 students in the informatics course, of which probably 10% know how to properly program 😅
So like 900 people see and adapt/learn this real bad coding convention. It really pisses me off, that they basically don't give a shit about convention or teaching them. I have to say that the logic some times is as worse as the conventions 😓
Besides I am not cocky with conventions, but I think at a high-class university they should teach proper convention.

My current job at the release & deploy mgmt team:

Basically this is the "theoretically sound flow":

* devs shit code and build stuff => if all tests in pipeline are green, it's eligible for promotion
* devs fill in desired version number build inside an excel sheet, we take this version number and deploy said version into a higher environment
* we deploy all the thingies and we just do ONE spec run for the entire environment
* we validate, and then go home

In the real world however:

* devs build shit and the tests are failed/unstable ===> disable test in the pipeline
* devs write down a version umber but since they disabled the tests they realize it's not working because they forgot thing XYZ, and want us to deploy another version of said application after code-freeze deadline
* deployments fail because said developers don't know jack shit about flyway database migrations, they always fail, we have to point them out where they'd go wrong, we even gave them the tooling to use to check such schema's, but they never use it
* a deploy fails, we send feedback, they request a NEW version, with the same bug still in it, because working with git is waaaaay too progressive
* We enable all the tests again (we basically regenerate all the pipeline jobs) And it turns out some devs have manually modified the pipelines, causing the build/deploy process to fail. We urged Mgmt to seal off the jenkins for devs since we're dealing with this fucking nonsense the whole time, but noooooo , devs are "smart persons that are supposed to have sense of responsibility"...yeah FUCK THAT
* Even after new versions received after deadline, the application still ain't green... What happens is basically doing it all over again the next day...

This is basically what happens when you:=
* have nos tandards and rules inr egards to conventions
* have very poor solution-ed work flow processes that have "grown organically"
* have management that is way too permissive in allowing breaking stuff and pleasing other "team leader" asscracks...
* have a very bad user/rights mgmt on LDAP side (which unfortunately we cannot do anything about it, because that is in the ownership of some dinosaur fossil that strangely enough is alive and walks around in here... If you ask/propose solutions that person goes into sulking mode. He (correctly) fears his only reason for existence (LDAP) will be gone if someone dares to touch it...

This is a government agency mind you!

More and more thinking daily that i really don't want to go to office and make a ton of money.
So the only motivation right now is..the money, which i find abhorrent.

And also more stuff, but now that i am writing this down makes me really really sad. I don't want to feel sad, so i stop being sad and feel awesome instead.

I found out that a major open source project pulled in some of my code for an enhancement I wrote in my own repo. The code was modified some to match the current conventions of the project, but it contains some of my original comments so I know it was based directly off my code. I'm not entirely sure how to feel. On one hand I'm super stoked to know that the maintainers of the project actually looked at my code and included it. On the other, I'm a little bummed they didn't credit me or at least give me a little shout out...

Filthy sysadmin wouldn't let me call the iOS build server "CiderMill" :(

all of them. countless wasted hours.

as fate decided to turn me from $random-dev-geek into "the guy that calls the shots in tech", one of my earliest decisions was to automate formatting.

everywhere, automated at CI.

gofmt was an inspiration for the industry.
js?/ts? use prettier
C++? use ClangFormat
etc.

always default settings.
enforced by pre-commit hooks and CI.

never a single argument about bracket style, I don't care if someone likes single or double quotes better.

"fucks given" counter is fixed at 0.
everybody prefers it (ok, sometimes after a while sometimes)

of course there is still some more conventions to do for us humans.
IMHO the most critical ones.

like naming or even casing (camel, snake, kebab, - which one works where), but taking out most of the "so what" decisions takes discussions to a much more resonable level.

We're having a mini-hackathon at our school last Saturday as a final exam of our Web Engineering course, showcasing what we learned throughout. The theme is all about helping university students gain their productivity and improve their interaction with technology.

Me and my team tried to create a note-sharing platform for students. We loved the idea and we're so excited to create it. But excitement turned into shit hole during development.

A fuckton of merge conflicts, divisive code conventions, and usage of god-awful Bootstrap for front-end came in. 😱😬😣

Despite these things, we are able to win the hackathon (i still can't believe we won). but he worst part of winning is that the prize is not cash nor the internship (the judges are from the company who somehow looks for interns), but fucking useless GIFT CARDS!!

But in the end, we're proud of it. I thought that it will be just a concept but in the end, it became real and it turned out to be great. ☺

Rant Mode: ON

Do you know what really grinds my gears? Those dreaded "404 Page Not Found" errors. It's like a digital black hole, sucking your users into a vortex of frustration.

And don't get me started on inconsistent coding standards. It's like trying to decipher hieroglyphics written by different ancient civilizations. Why can't we all just follow the same conventions?

Oh, and software updates that break everything! You spend hours perfecting your code, only for a new update to come along and wreak havoc. It's like the universe is conspiring against developers.

But hey, despite the rants, we developers are a resilient bunch. We thrive on solving problems, no matter how infuriating they can be. So, here's to the endless debugging, the endless coffee, and the endless love-hate relationship with coding. We wouldn't have it any other way.

Rant Mode: OFF

Phew, that felt good. Thanks for letting me vent!

Looking to update the way I write my code to follow:
- Coding Convention
- Standard Work
- Coding Standards
- Whatever other name they call it

And found this...

We were discussing if table names should be singular or plural.
As a good developer, I had to check stackoverflow.
#savetheS is a movement now

It's depressing how much time I spend asking, begging, demanding, and pleading for the older devs on my dev team to follow simple naming conventions. And every time I ask, they act like it's new information.

Talking with manager about C++ ...

ME: ... and those are the main differences when coming from C03 to C17.

MGR: OK. I think I got it... are these changes those kind of changes that when we know them we can work in any industry if they use C++?

ME: No they are not, sorry. They are like basic enablers to even start considering entering some industries. What you mean are standards. AUTOSAR standard for example is for automotive industry.
The standard requires some level of C++ standard competency.

MGR: Are these standards like plugins for C++...

ME: ? ... no. They specify rules and architecture, conventions and such.

MGR: ... aah. Architecture, I know that word. So in fact they are plugins....like...like...Eclipse IDE has architecture and it can have plugins....right ? ... and you just plugin that AUTOSAR standard to C++ language.

ME: I think you mixing stuff up on multiple levels here. I think we are not ready to talk C++ competency as a strategic decision yet... lets get some basics down first and discuss this stuff in one month.

MGR: ... ?..but, but I mean it can't be that hard. I think I almost got the gist. I just misunderstood at some point.

ME: Sure, sure. No worries...you almost had it *with deep sarcasm*.

Picked up an older project which is in prod for 2 years now. I got a DB error related to a null in an array.
Proceed to check the front end(angular 1.5). Ended up in a 3000 lines file😫
What's worse the array was processed by multiple functions including 'filter' and 'filter2'. Naming conventions ftw😂 I don't know whether to laugh or cry 😂

Working on another SaaS product, and now I've run into a "fun" conundrum that is hard to determine cleanly in an automated fashion.

I'm certain it's stupid bullshit opinionated conventions like this as to why so many devs are driven to burnout and bitterness...

I can't tell if I'm being a baby - but I asked for a specific sub-domain for a reason / and they gave me a domain that looks too similar to local and live - just like I was trying to avoid... : /

Seriously? 🤔

I asked him: "What are the projects conventions?"
He replied: "Everyone codes as he likes to"

And I was like... It will be a nightmare😂😂

!rant
the most popular ecommerce solution in php is a massive (cosmological scale) pile of corporate crap (magento) and the next most popular is an abomination (opencart)
after fucking around with both for a month (the client asked for the project to be using only one of the two) I'm still barely reaching any results, and most of my time is wasted with the stupid bloated spaghetti that is opencart FUCK THIS,
like seriously. who the fuck writes a single line three left joins sql querry with four or five aliases a couple concacts and a bunch sorting fuckeries just to query the categories list, then just query the details of the specific category from a different function,
also why the fuck map each language string manually. or the fucking hardcoded seo urls, or the use of myisam for all tables, and no fucking foreign keys, let that settle for a minute, no foreign keys, the delete method in the model has at least a twenty lines, and then he came with the genius idea of duplicating models, in the front and the backend, accessing the same data, as the same user, but different naming conventions

I'm going to convince him to use something sane like codeigniter/laravel/fuelphp or I'll deny the project

Working on small scale games to working on a full blown VR 4 person MO game, the scale from one to another is pretty big, I seem to manage somehow though :D takong it all one step at a time, making sure I don't use any repeated code in places that could need it, cleaning up classes so it's easier to access for debugging, building nice inspector things so people that create art/particles and such don't have a hard time understanding my weird naming conventions.

I could go on and on really xD i've learnt so much and i'm still learning, and I really have nothing to rant about thesw days so i've gone back to lurk mode lol

I envy all those developers with clean codebases and consistent coding standards and nice architecture.

I'm fixing bugs and optimize code in someone else written project. which looks like spaghetti. with naming conventions like "a", "bbb", "zA" comments written in unknown language and off course the deadline was yesterday.

hey do you know if there is a JavaScript libary for naming newly created files acording to user convention? Instead of "Unamed file".
Like [DATE]_[0000]_[NAME]_[SIZE].[Filetype] --> 20210708_0001_Pictureofme_1000x1000.jpg

There is a brand new service of the swiss post office that scans all your mail. But in the app it says only "unnamed document" for each new letter.
I'd like to suggest them, that you can set up a naming convention for each new pdf to my liking.
thank you 🙂

Restarting regular expression parser from scratch has been good. I am somehow both much farther to completion and farther away from completion than I was in the earlier implementation.

Further in the sense that this implementation is going to be way more flexible to changes in the language

Farther in that I haven’t even got all of the regex parts added to the first stage yet.

But I’m feeing good about it.

Even if I did refactor it so my constants are in all caps and now feel like my core is yelling at me.

(mostly !dev) Fuck humans! Really: what a scum bag race. All that shit talk about human dignity, the highest values are just sugar coating the low base motives we mostly live by. Like people have such fine antennas for your income, social status, the power or lack thereof you exert over other. They know it before you open your mouth, that they can pick on you, harass you, because you're the one on the receiving end, the one that bows away. The bullies feel that. On an overcrowded chicken yard you'll find more dignity than in human society.

Everybody drooling over that polished photoshop life on facetubeinsta: materialistic, consumeristic, masturbatic wastage. At least we now say it openly: that if we were the winners, we'd also take it all, live that empty luxury, life of fame. But 99,99% of us, we aren't in that position, just working off our arse to only keep afloat. And for the stars, those fake images, we're just rats to click on ads to better train Google.

No wonder that software, as a picture of human communication is such a shitfest of arbitrary, entropic conventions and endemic epidemic of quirks, bugs and evil trap doors. As a whole: an insults to reason, a challenge to sanity. (...Conway's law)

And I'm still a bit pissed at our profession, that, you know, as engineers, scientists, physicists, we still see us in the lineage of that "great" age of enlightenment and reason,.. while it's all just a cover up. Sure science and their ideas are nice as long as you serve a purpose or make some money. Sure democracy and free speech are great achievements, but in the end some elites and monopolies rule the world at their gusto - and will not stop destroying the world unless we're already one feet in the abyss (like 1962, be we ain't had enough of that shit, hadn't we?)

I've been writing Java the last few days. Really makes me remember why I enjoy writing objective c / swift so much. It's not necessarily the crazy syntax of objective c. It's the conventions behind the languages. It's very easy to make your code read like prose. Which when you become used to this it's very hard to jump back into spaghetti code with abbreviated variable names and such.

Small rant for today: why in God's name do some people feel the need to ignore the conventions of the frameworks THEY chose to use for theyr projects, and start just throwing stuff randomly around the whole codebase?

ARRRGGHHHH...

Phew...all better now :)

I told you fucking moron clients doing that "little" change would be complicated and in the worst case it would end fucking up your whole spaghetti crap. A really HUGE spaghetti monster of that you aren't aware because you guys don't know a shit about coding conventions.

*Clients call me complaining about their software is broken*

-Hey, we're in serious trouble. Our users aren't being able to see the proper calculated values. Why that little change had so much side effects?
- I already told you why.
- Can you fix it asap? Our clients are complaining.
- No. Deploy an old copy of the affected modules while you give me a prudent time to refactorize that crap.
- Refactorize?
- ...

I used to work in their place, 3 years later I quit that crappy job and decided to make them my clients. I escaped from the micromanaging thing but I didn't from their ugly practices.

Anyways, I have to fix this shit asap. Money talks, at least until I can find a better client.

Currently working on an inventory system. I have main, Side, local and premium items. And I also have inventory slot lists for each type. My Lists are called:
MainSlots
SideSlots
LocalSlots
PremiumSlots.

I grin everytime I type it out...

Being a front end developer and working in a team of motivated "full stack" developers sucks big time.
So, recently joined this new company with a very small project which just started, basically a cloud version of a really old desktop app. Few people from the team completely from the asp dotnet background decided the architecture few months before I joined in.
So, they did it something like this -

- mono repo dotnet project with VueJs app served within it (because that would be maintainable 😑)
- vue app served by pointing the built files through dotnet index file (simply because they didn't care about the gift to the front end world which is webpack or even had any knowledge about it 😑)
- added typescript because, u know it's cool 😑, without even knowing that they don't possess that team which know how to write the types (f***ers write classes for every payload object coz they don't know what interfaces are)
- no loader to load typescript, they are running tsc in watch mode and we have .js and .js.map for every .ts file in our project which some teammates are even pushing to repo

Recently, I added eslint with git hooks to the project so that everyone will at least stick to the coding standards. Now, to avoid the errors they are bypassing the git hooks by uninstalling the library and then installing it after the commit😂😂
Then we have a girl who uses document.getElementById to programmatically change styles in a Vue project😑😑😑😂
Then we have dotnet people using dotnet coding conventions all over the front end app.

People, how do I deal with these so called "full stack" people?

When you have a dev domain, yet your senior developer coworkers still add "Dev" to their app names..

I really really hope that no one post this,a friend texted it to me and I wanted to share it because made my day.

Idk where it comes, so feel free if know where this came from to post it:

//FUN PART HERE
# Do not refactor, it is a bad practice. YOLO

# Not understanding why or how something works is always good. YOLO

# Do not ever test your code yourself, just ask. YOLO

# No one is going to read your code, at any point don’t comment. YOLO

# Why do it the easy way when you can reinvent the wheel? Future-proofing is for pussies. YOLO

# Do not read the documentation. YOLO

# Do not waste time with gists. YOLO

# Do not write specs. YOLO also matches to YDD (YOLO DRIVEN DEVELOPMENT)

# Do not use naming conventions. YOLO

# Paying for online tutorials is always better than just searching and reading. YOLO

# You always use production as an environment. YOLO

# Don’t describe what you’re trying to do, just ask random questions on how to do it. YOLO

# Don’t indent. YOLO

# Version control systems are for wussies. YOLO

# Developing on a system similar to the deployment system is for wussies! YOLO

# I don’t always test my code, but when I do, I do it in production. YOLO

# Real men deploy with ftp. YOLO

So YOLO Driven Development isn’t your style? Okay, here are a few more hilarious IT methodologies to get on board with.

*The Pigeon Methodology*
Boss flies in, shits all over everything, then flies away.

*ADD (Asshole Driven Development)*
An old favourite, which outlines any team where the biggest jerk makes all the big decisions. Wisdom, process and logic are not the factory default.

*NDAD (No Developers Allowed in Decisions)*
Methodology Developers of all kinds are strictly forbidden when it comes to decisions regarding entire projects, from back end design to deadlines, because middle and top management know exactly what they want, how it should be done, and how long it will take.

*FDD (Fear Driven Development)*
The analysis paralysis that can slow an entire project down, with developments afraid to make mistakes, break the build, or cause bugs. The source of a developer’s anxiety could be attributed to a failure in sharing information, or by implicating that team members are replaceable.

*CYAE (Cover Your Ass Engineering)*
As Scott Berkun so eloquently put it, the driving force behind most individual efforts is making sure that when the shit hits the fan, you are not to blame.

Some Udemy courses are super cringe.

Can tell this guy isn't formally educated nor a professional programmer.

His code is so badly formatted and his naming conventions reeks of inexperience.

Spaghetti everywhere.

I hate discussions about how to name resources in a REST api. It’s not like there will ever exist a client that magically knows your conventions. At some point, you need to hardcode an URL in a client/browser. That’s fine, just keep it simple.

This has been a great source of bike-shedding in my job recently.

And don’t even get me started on HATEAOS...

Fuck forced coding conventions in uni, especially if they are as stupid as Google's Java Conventions. They are a disgrace to nice code but we will have to use them going forward

Stupid spaces everywhere. Else on the same line, wtaf. And don't even get me started on indentation with fucking spaces. Tabs are superior in every single way fite me irl

People who mix different naming conventions are the worst. My MATLAB teacher mixes PascalCase, camelCase, snake_case and weird hybrids like everythingIs_SoWrongWith_this 😠

School made me a stickler for the Linux kernel coding conventions in regards to the C language. And even though I shouldn't feel bothered by reading other coding styles.....i still get annoyed.

I try not to get irked cuz I find it a small thing to get annoyed at.... but i still do.....bad.

And even then i dislike how there is not padding inside of funcion parametes

void
fu(int here, int there) {}

Should be

void
fu( int here, int there ) {}

That space man...its needed.

Man this is such a small thing to be annoyed at..

I just love code-golf, I only started recently, but sometimes it's nice to fuck all coding conventions, missuse lazy evaluation and abuse scope leaking.
I'm normally really tidy with formating and whitespace placement, but code-golf is also a testing field for uncommen constructs and I think it can give deeper insights into a language.

I don't like languages specifically for code-golf though, these are just stupid and no fun (at least for me).

When you notice that the guy next to you is using Urban Dictionary to name public methods in modules.

Have to follow same coding conventions of colleagues just to avoid merge conflicts.

Why does it always follow the same format?
Me: we should do do and so because xyz. Alternatives are this and that because uvw.
Manager: no, I'll hire another manager.
[Q]uit, [T]ry again? T... fml
Manager 2: let's have a meeting.
Meeting almost ends up being about an entirely irrelevant topic. Barely get the requirements before the end of the day.
Me: write summary following conventions.
Manager 2: let's hire another manager. Manager 1: great idea, manager 2!
Manager 3: let's build a spaceship!
[D]evsplain, [R]agequit, [T]ry again?

class Manager:
"""This shouldn't be too hard..."""
...

I'm always helping out a girl in my class with her coding assignments but her code is absolutely atrocious. I don't have the heart to tell her that her whole method, file and variable naming, and process is wrong and is causing her so many headaches.

Today I tried teaching a 36 years old student about HTML and layout. My inner self is always restless for practice as an excuse for less talking, but in the end I end up doing even more talking and getting kinda embarrassed.

Good thing is that student understood everything well enough in this 1 hour. I also inserted some good stuff: tips and tricks, conventions mentioned, trends... He even craved for more information.

I'm going to prepare to make further studies more fruitful, because the next synopses won't be as theoretical as today's one.

Forgive me Linus for I have sinned. It has been since the dawn of time since my last confession.

I hardcoded naming conventions for file names into a script that is used to remove incorrect lines of text that are created during our process to create the files that we send out so that healthcare claims get paid correctly and copy and pasted the code for each new state’s health plan since the users(who are supposed to be technically inclined as they’re in IT as support analysts) can barely figure out how to set up the excel file to remove the lines. There are now 18 files of the same python script with different US States’ names.

I've been to 4 kubernetes related tech talks and they've all been the fucking same. No depth, no new cool things, no little tricks or demonstrations, just the plain old boring shit I've seen a thousand times.

I've worked with it and love it for big projects, but going to conventions to hear someone talk about it is completely meaningless. Perhaps it's because I only learn by doing.

And before anyone says 'then don\'t go', I usually go with either friends or a colleagues and want to show my face, and have some drinks and snacks.

This was my techtalk.

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

Do Python developers not like camel case function names?

I have co workers who laugh at me everytime I discuss to them how we should create clean code. (create functions for repeating code, naming conventions, generic code).

They would brag instead how they make another javascript ui library/plugin work(we are web developers by the way). Looks good in the front end but a mess in the backend.

I already created generic classes, generic database views that can be used by them if they want. But they create a new one with the same functionality.

I am a bit of a shy guy, and they are bit of loud, and I don't want to look like a know-it-all-guy, so I just let them do what they want.

I am just concerned how we can work easier by easily reading each others code.

When the dev that worked on the project before you clearly sucks in naming conventions 🤦‍♂️

Hell is working on a file 4000 lines long file containing html css php and sql with inconsistent coding conventions

How do y'all deal with reading other people's code?

Context: was given a frontend project (I'm a frontend dev) that was started and is managed by a backend dev who just started doing frontend.

I want to start from scratch as I don't understand a thing he codes, conventions are all off, and the structure is just weird.

I was always a bit confused by the naming schemes in official python libraries. So I decided to lookup the official naming conventions, according to PEP 8. Lo and behold, the very first sentence:

> The naming conventions of Python’s library are a bit of a mess [...]

I'm shitting there hammering out some code butchering some real problems when I suddenly realise I'm surrounded. I look around and yes it's the bloody committee.

The committee is what I call the rest of the department and it is dominated by the old guard which comprises of the programmers that have been around for longer.

None of the old guard can program particularly well but because they had been around the longest they'd all grown senior. The committee had free reign but anyone else doing anything differently has to get approval from the committee.

The only way to code otherwise was to copy and paste existing code then to primarily rename things. If anyone did anything that hadn't been seen before then it would have to be approved by the committee. Individual action was not permitted unless you were old guard.

I swept my headphones away expecting it to be something unimportant. It was.

First things first they announce. We're going to add extraneous commas to the last element of all possible lists separated by comma including parameters or so they say. Ask but why so I do.

Because the language now supports it. They added support for it so it must be the right way someone proclaimed. Does it? I didn't realise we were waiting for it. Why do we want it though?

Didn't you hear? It's all over the blogosphere. It massively improves merge requests. But how I ask?

Five minutes later I grow tired of the chin stroking, elbow harnessing, slanted gazes into the yonder and occasionally hearing maybe its because and ask if they mean when you for example add an element the last element registers as changed from adding a comma. Turns out that's all it is.

How often do we see that tiny distraction and isn't it pointless to make the code ugly just for a tiny transient reduction in diff noise I ask. Everyone's stumped. This went on and on and got worse and worse. But it makes moving things around easy half of them say in unison like the bunch of slobs that they are. I mean really. It doesn't make expanding and contracting statements from multiline to single line easy and it's such a stupid thing. Is that all they do all day? Move multi-line method parameters up and down all day? If their coding conventions weren't totally whack they wouldn't have so many multiline method prototypes with stupid amounts of parameters with stupidly long types and names. They all use the same smart IDE which can also surely handle fixing the last comma and why is that even a concern given all the other outrageously verbose and excessive conventions for readability?

But you know what, who cares, fine, whatever. Lets put commas all over the shop and then we can all go to the pub and woo the ladies with how cool and trendy we are up to date with all the latest trends and fashions then we go home with ten babes hanging off each arm and get so laid we have to take a sick day the following to go to the STD clinic. Make way for we are conformists.

But then someone had to do it. They had to bring up PSR. Yes, another braindead committee that produces stupid decisions. Should brackets be same line or next line, I know, lets do both they decided. Now we have to do PSR and aren't allowed to use sensible conventions.

But why, I ask after explaining it's actually quite useful as a set of documents we can plagiarise as a starting point but then modify but no, we have to do exactly what PSR says. We're all too stupid apparently you see. Apparently we're not on their level. We're mere mortals. The reason or so I'm told, is so that anyone can come in and is they know PSR coding styles be able to read and write the code. That's not how it works. If you can't adjust to a different style, a more consistent style, that's not massively bizarre or atypical but rather with only minor differences from standard styles, you're useless. That's not even an argument, it's a confession that you've got a lump of coal where your brain's supposed to be.

Through all of this I don't really care because I long ago just made my own code generators or transpilers that work two ways and switch things between my shit and their shit but share my wisdom anyway because I'm a greedy scumbag like that.

Where the shit really hit the fan is that I pointed out that PSR style guide doesn't answer all questions nor covers all cases so what do we do then. If it's not in PSR? Then we're fucked.

To all the masochists who spent hours debugging misspellings:

1. Learn your tools
2. Learn good practice

Every IDE should point out when you're not using a variable you've initiated or using an uninitiated variable as well as at least highlight, if not simply list, every occurrence of the variable under your cursor and let you find all references or even display the number of references next to a variable at all times, and finally, every IDE should autocomplete for you so when it doesn't you know you've messed up. Good IDE makes all the easy mistakes hard and all of the hard tasks easy. Including running tests. If you don't know how to configure your IDE to do all these things take time and learn it. If you still can't figure it out, replace your IDE maybe...?

Also use the debugger. Preferably one that nicely integrates with your IDE. If you don't, check point 1.

Also write tests and *run them*.

Also if your misspellings tend to consist of a missing `s` at the end of a plural noun just call it `entityCollection` instead of `entities`. And read up on more good programming practices and naming conventions.

Last week me and my friend have been changed from a legacy PHP project to new Ruby on Rails-based setup. What, in first instance, looked like a great improvement, now becomes a nightmare.

All this convention-over-configuration is awesome - but only if you already know the conventions, or if somebody told'em to you.

And everything is going even more out of control because the damn project is based upon Spree gem and several other extensions, that MUST be changed to meet out company needs.

I'm getting really mad with all this pressure. Ruby seems to be a great language, but I'd rather be working with Laravel. Its overall organization, the centralization of CLI commands in artisan, and the astoundingly clear, eloquent, direct and well-designed documentation made my adoption curve there a little more pleasant.

I mean, legacy PHP systems are awful, but Laravel framework sounds way more easy-to-learn and well-constructed when compared to rails.

But given all this nightmare, I really want to be proved the opposite.

Why are more games or media platforms not encouraging the use of similar account naming conventions to Blizzards launcher or Discord.

The way you can have a name# with a 4 digit code pretty much gives you the ability to have 10k users with the same account name but still be unique.

Just tried PokeMMO which has been around since about 2010 I believe? Not only is their system shit with a 3 char limit and the inability to delete characters, but the game is so fucking old that I literally spent between 30-60 mins looking for a variation of my name that was both likable and available.

I've never designed a naming system like discords before, but surely its a better alternative to this shit?

Started vacation today and arrived at our glorious holiday lodge. It is lovely. All very modern and funky. And it has a lovely cooker hob with touch controls... ooooo!!

And I swear I've never seen anything as complicated and confusing in all my life. It's a fucking cooker!! But it has no knobs you turn to set how hot a fucking cooking ring is. This thing has 2 pages of instructions to fucking turn it on - and they don't bloody help!! Want a ring on at heat 6? That's 9 fucking touches - but not like a smartphone touch, each a fucking 1sec+ touch!!

UX is about conventions and thinking of your users. The people who designed this obviously think they're visionaries and pioneers when everyone who actually uses their gear just curses them up and down for being stupid. Cookers are cookers and everybody knows how they work and how they use them?!?!

Holy shit designers, stop being too fucking clever for yours and everyone else's good!!

You can tell how nice and relaxed I am having started my vacation today... and read the rest of my rants to see how little I swear. But, by God, this thing is ridiculous. I blame the influence of @Letmecode for my reaction!! 😂

I switch back and forth between js(Vue) and Java and get them mixed up a alot which slows me down because I have to look up conventions. Any tips on managing multiple Lang's mentally

What are the best conventions I should try to get my boss to send the team to? He said we have a budget for a few events, but other than the fun ones (WWDC, Google.IO, etc) I have no idea which ones have actual, meaningful content.

Any suggestions?

Started testing my most recent side project today... Renaming 1.1TB of movie files according to proper naming conventions over a 100Mbs network. Been running for 11hours already and not even a quarter of the way through

I now understand why people say python is such a damn hard language to keep big projects. I'm so hell lost in all those code indentations and lack of conventions!!!!
GET ME BACK TO RUBY PLEASE I BEG AAAAAAA

Hey, you, my new colleague, you are annoying. I have reviewed your PR and left about 50 comments on your mess. I even explained to you why half of your code is shit in a very polite way. I have explained why you have to rewrite that and even how to do that in the best way possible. Result? Half of the code is gone, it works as before but without the overhead.

Now you're annoying cuz I have to go again on conventions and best practices. I totally understand that you've been doing it differently and throwing buzz words at me won't help. Just stop and do it as it's needed in this project, don't reinvent the wheel only because you can.

You know what? Fuck it! I'll approve all your PRs, anyway I am leaving soon. There is no benefit for me to teach you stuff. You're one of those guys that I voted against in interviewing process. But guess what? My manager decided to hire you anyway! Ha! I rarely vote NO and you were a one of those...

Your confidence doesn't impress me. That works on people that have no clue on what you are doing. Your just average at best, not a superstar.

Fuck it, you're on your own now!

Whoever uses "status" as boolean in responses to indicate whether error happened (true) or not (false)??????!!

I haven't chimed in on this spaces vs tabs war at all on this platform, mostly because I personally don't care and adapt to my work's/project's conventions, but I just have to put this out there now.

I am honestly so confused about the entire thing since seeing a lot of recent rants on the topic. I was originally conditioned to believe that the majority of devs in the world were FOR spaces over tabs. Thus, whenever I start a project, I default to spaces.

Contrary to that, it seems most devs here (or at least those who enjoy instigating some banter) actually prefer tabs. Now, I recently binged Silicon Valley and can't help but wonder if people around here are simply jumping on that band wagon for the sake of the joke.

Side note: I also thought Vim was more widely used over Emacs but Richard Hendricks asserts otherwise there too.

I know the main arguments for both sides - spaces yield code that looks the same in all editors while tabs produce smaller code. Anybody who argues that spaces are less efficient because you need to physically press the space bar 2/4/8/etc times is just retarded. If soft tabs weren't a thing, I don't think anybody would be on the side of spaces and for that reason I believe that episode in Silicon Valley was just trying to be overdramatized and push peoples' buttons.

All of that being said, I wonder if it's just a generational/field of development thing. Would it be wrong to propose that more older devs in the field of embedded and OS development (using C and the like) are in the spaces party while younger devs perhaps more into application and web dev (Javascript, C#, and shit) are all about tabs? I'm actually fresh out of university, but like I said my preference is spaces, though I don't really care.

I'm actually interested to find out what kind of environments breed these opposing mindsets so what do you guys think?

So as a student developer with years of background in web development (including both front and backend), c++, java and c#, I was more than surprised when I found out my Informatics assignment hadnt received the proper excellent mark. In fact both me and a friend of mine who has been working with C++ in particular for years got a --mark.

// The assignment was the most simple Windows Forms Application with 2 buttons and a textbox

When we asked about that the teacher said we hadn't labeled the buttons and textboxes, though we had actually taken our time to put labels next to each UI element that would need usage directions.

Though what she meant was renaming the actual variable names, those being textBox1, button1 and button2.

We of course got really mad, because w both follow the accepted naming conventions for each of the languages we write in. Arguing was to no avail. Even telling her that variable naming was not in the assignment instructions was pointless as she said it had been self explanatory​..

The others for whom computers are powered by magic, did their assignments as they had memorized everything that teacher had shown them. Why? Because she didn't teach them how to code in the first place. So they copied what would work.

Fucked up educational​ system, sadly nothing new..

Oh and btw, the naming she uses and teaches students to use is:

button1 - btname
label1- lbname
textBox1 - tbyear

I'm in a dilemma.

I started this job about 9 months ago and it's really not what I expected. I'm the sole developer in my department that handles applications built around our customer database.

Well it's pretty boring and there is a lot of technical debt with the source code since usually 1-2 people are taking care of it so they never had proper conventions. And we have super old applications running on legacy solutions like cold fusion 🤢

I also receive a lot of problem tickets that never contain enough information to actually do anything and the people don't realize I have no idea what they do or what their business processes are.

The upside is I'm paid very very well for this job > 100 in a place where cost of living is cheap. And when there's no work to do I can work on side projects.

It's really not fulfilling work and idk if I should stick it out. I also don't know where I would head next. There's not very many companies working on cool stuff. Maybe remote work?

Anyone else have a similar story?

In the 21st Century the problem is not to allow the use of Chemical & Biological Weapons & 'maybe' just 'maybe' achieve total nuclear disarmament (not in the next 120 years) It's not just the responsibility of the UK, USA, & France but that of every country that's a signatory of the conventions that banned the use of such weapons to intercept and retaliate against members that use such kind of weapons. From Kenya, Ghana, South Africa, Brazil, China, India , Afghanistan, Butan, Taiwan, Iceland should use heavy force to stop the use of such weapons.

The „UI-God“ in our team has never heard of dry or clean code.
Clashing classnames for modules in global namespace, gives a f* about patterns, naming conventions, structure and everytime I rebase it breaks my code.
I need the same amount of time fixing his work as he spends on it.

I'm going to confess: I am the type of developer that creates the ExcruciatinglyLongAndSpecificClassNameObject with the UtterlyDetailedExplanationMethod. It's just a thing I keep doing, despite voiced frustrations from people I've worked with. It just feels right in the mindset of self-documenting code

And while I acknowledge this isn't a flawless process, I see no other way around without losing information. I've tried alternatives, but everything feels like trading one issue for another:

- Abbreviations work as long as they are well known (XML, HTML, ...). As soon as you add your own (even if they make sense in the business context) you can bet your ass someone is going to have no idea what you're talking about. Even remembering your own shit is difficult after X months.

- Removing redundant naming seems fine until it isn't redundant anymore (like when a feature with similar traits gets added). and you can bet your ass no-one is going to refactor the existing part to specify how it differs from the newly added stuff.

- Moving details to namespaces is IMO just moving the problem and pretending it doesn't exist. Also have had folks that just auto-include namespaces in VS without looking if they need the class from namespaceA or namespaceB and then proceed to complain why it doesn't compile.

So, since I am out of ideas, I'd like to ask you folks: Is it possible to reduce class/method name lengths without losing information? Or is self-documenting code just an ideal I'm trying too hard to achieve? Or are long names not a problem at all? I'm looking forward to your answers.

Part of the PR feedback was the use of capitals and the conventions. I tried to look up some backup documentation of angular in the styleguide regarding this topic. Didnt find any.

His answer was that it’s a C# convention. DUDE IM NOT PROGRAMMING IN C# AM I ?! You are mixing up conventions between ts, js, ng and now C# how the fuck am i ever going to follow this?!

The project that I'm assigned to was developed in haste because of some competition with other vendors.

The Devs who worked on the original code didn't really follow each others spacing conventions. So now there are files which differ in spacing. A lot. And I'm used to the standard 8 spaces=1 tab convention.

Every frikkin time I have to even look at the code, I have to refactor it (but not save it) and then undo the refactoring because when I try to check in the refactored code, every line shows a conflict.

Every line.

So if I have to work with code which was written by more than one person, my life's a living hell.

Ctrl+Shift+F people! Use it or lose it!

So I decided to pick up go, I must say I am very impressed.

As a Java developer I have always felt a certain chaos in C development (no established infrastucture of project conventions) but I am starting to fall in love with Go.

Is there anyone out here who has professional (or advanced) experience with the language? I would love to learn more in-deth stuff like proper conventions and patterns.

Once upon a time I spent a week writing down a "Coding Conventions" document, setting up linters for JavaScript & CSS based on those rules and put the call to the linter in our gulp build task, only to figure out the next day it was commented out by some guy because "the build task was throwing errors" due to his shitty coding style...

Do you prefer:

$order->getShippingAddressCountry();

or

$order->getShippingCountry();

Fuck me, being a perfectionist slows me down.

Beign stuck on: Save that shit as address_shipping_country or shipping_country is purely stupid, i know.

How do you get your stickers?
Conventions?
Do you just buy them?
Also which sticker is your favorite (that you own)?
Is there a sticker you want, but can't seem to find?

Sometimes my hatred for code is so.. overwhelming that I think I need a sabbatical or should even stop altogether.

Let's face it. All code sucks. Just on different levels.
Want to go all bare metal? Love low level bit fiddling. Well, have fun searching for concurrency, memory corruption bugs. Still feel confident? Get ulcers from large C/C++ code base already in production, where something in the shared memory, function pointer magic is not totally right?
So you strive for more clean abstractions, fancy the high level stuff? Well, can you make sense of gcc's template error messages, are you ready for the monad, leaving behind the mundane everyday programmers, who still wonders about the scope of x and xs?

Wherever you go. Isn't it a stinking shit pile of entropy, arbitrary human made conventions? You're just getting more familiar with them, so you don't question them, they become your second skin, you become proficient - congrats you're a member of the 1337.

Android devs, what are your thoughts about the naming conventions google tries to enforce on us, especially with the xmls?

I opened a new project after months of leaving android dev, and thought of trying the basic activity template with name 'myActivity'

On clicking it, a ton of files got created : myActivity, myActivityFragment ,... And in xml the reverse naming notation : activity_my, fragment_my, content_my,...

This naming is uncomfortable .in a large project, activities usually acts as complete modules in which different tasks are handled : logins getting checked, data being cached, database being accessed and much more...
So if my activity 'abc' has a content fragment and a toolbar whose design is in another xml, shouldnt the 3 of them be named like:
abc_activity.xml
abc_activity_fragment.xml
abc_activity_toolbar.xml

And not
activity_abc.xml
fragment_abc.xml
toolbar_abc.xml

??
At the very least , it would look nice since the components that are displayed together will have their files together. And i don't know much about testing, but i believe it would be helpful there too

Why is it that when people are anal about linting they don't like the default/mainstream conventions?

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)

We've introduced an official coding style at my work, which is great. Visual Studio will even alert us when code isn't up to snuff.

What Microsoft didn't think to do was let me automatically apply naming conventions across entire solutions or even just projects. I got to spend a few hours today manually going through hundreds of files and and applying the style guide.

I can automatically apply brace style across an entire solution, why won't you let me do the same with naming conventions?! A few hours down, a few more to go.

Just began to learn Node.js. Wondering why the modules aren't named starting with an uppercase letter.

I am mostly self-taught. If I am (really) interested in doing something new, or if I feel there is a need of doing something, I just do it. Simple.
Learnt a great deal by looking at others' codes (like how things are done, conventions etc), tinkering with the IDE, working on personal projects etc.

The first freelancer i hired on @upwork actually copied code from their other projects into mine. I could tell because every PR had a new coding style, naming conventions and massive amounts of unused css.
Knocking out 2 birds with one stone.

I swear these underclassmen are in a contest to see how many unique one letter variable names they can come up.

So i just wasted almost 12 hours because of naming conventions. Yeah good job me 🙄

First rant;

First of all I am an applied computer science student in the second semester.

We've got a few assignments and the first set went fine but this last week boy ohh boy - first of all today I got noticed by one of my two teammates that the other one won't get stuff done in this assignment (he also did next to nothing in the first)
Also the the assignment is unclear and the given methods and parameters don't care about naming conventions (for one method I don't even know what it should do). Also we have to use new liberies (java.io etc.) and learn them on our own so far it would be okay, the time limit is two weeks, also doable
BUT the same chair also made one assignment for web development with the same deadline and also no explanation how to do stuff.

I don't say I am perfect but the expectations are too high, while also studying for other modules

Lets use naming conventions to connect our controllers to our views. No fuck you.

Doing someone else's Code Review in my project: "You must retain the holiness and piety of the code you write by following PascalCase naming for files and kebab-case naming for CSS variables. Avoid using duplicate strings by declaring enums in a constants.ts file and using that all throughout the app"

During my own Code Review in someone else's project: "WHAT THE FUCK DO YOU MEAN I CANNOT PASS FUNCTION REFERENCES AS PROPS TO A REACT COMPONENT AND ALWAYS NEED TO INVOKE IT INSIDE AN INLINE FUNCTION FOR THE PROP."
"WHAT KINDA FKIN DRUGS ARE YOU ON TO USE snake_case IN TYPESCRIPT DID YOUR MOM DROP YOU ON YOUR HEAD WHEN YOU WERE BORN YOU SACRILEGIOUS PIECE OF SHIT"
"WHAT DO YOU MEAN I SHOULD USE BOTH SINGLE AND DOUBLE QUOTES FOR IMPORTS AS PER LOCAL OR GLOBAL; I'LL SHOVE THE SINGLE QUOTE UP YOU WHERE THE SUN DOESN'T SHINE YOU FKIN DEGENERATE MORON"

As much as I do believe in self righteousness of my own coding conventions over others (I might be slightly better than others but I really can't claim good authority because I've had my lapses in conventions too; and being one of the newer members of the team certainly doesn't help, despite my boss supporting my initiative), I guess it is high time we bring in some already established code conventions in the team that is finally big enough to warrant them. Maybe AirBnB.

Why Dart was designed with idiocy:

1) naming conventions are idiotic

Most other languages are smart enough to not throw errors when the variable name matches its type. And lots of others, for any lexemme - only 1 naming kind is allowed.

Fine. Oh wait, there's that thing called existing databases and GraphQL & other APIs, should they all adapt to this? No, because 2) is the bonus

2) String keys in objects. Unless it's a class with boilerplate, you write them as strings and access them as strings.

So here's the solution when you want to integrate Dart with existing services: write a lot of JSONSerializable decorators to fit with dart's pissy naming requirements.

I hate when programming books have shit code examples.

Just came across these, in a single example app in a Go book:

- inconsistent casing of names

- ignoring go doc conventions about how comments should look like

- failing to provide comments beyond captain obvious level ones

- some essential functionality delegated to a "utils" file, and they should not be there (the whole file should not exist in such a small project. If you already dump your code into a "utils" here, what will you do in a large project?)

- arbitrary project structure. Why are some things dumped in package main, while others are separated out?

- why is db connection string hardcoded, yet the IP and port for the app to listen on is configurable from a json file?

- why does the data access code contain random functions that format dates for templates? If anything, these should really be in "utils".

- failing to use gofmt

These are just at a first glance. Seriously man, wft!

I wanted to check what topics could be useful from the book, but I guess this one is a stinker. It's just a shame that beginners will work through stuff like this and think this is the way it should be done.

If by coding style, you mean conventions and not design patterns, then I'm surprised no one has mentioned the official documentation nor the standard library of sorts. I'm relatively new in the industry but at least I'm quick to realize that every language/framework community tend to have their own preferred style; not a one-size-fits-all thing. And these preferences are usually set off by code samples from the official docs. This is true at least for the big communities where the official docs are well-written.

Updating and aligning naming conventions :/

Looking for some names I can use for servers/devices. Currently I am using planet names from Star Wars. The names of those planets in the outer rim I use for rootservers/devices which are not physically located in my home. Any other ideas/topics?

I am really being tested with my creativity in naming conventions with these two sites rn.

Site 1 is a blog for a place called "The Post", so literally everything is called .post

Site 2 is a development built out of shipping containers, where each container is a different features of the property... just like a container would wrap features in their app🤦‍♂️

So I was reviewing coworker's code the other day...
incomingMessageProcessor.processIncomingMessage()
....well thank you there captain obvious

The best naming

The first company I developed software for had no coding conventions and it was visible in the codebase of almost all of our products. This is why I follow the coding conventions for every language I use.

A year ago I built my first todo, not from a tutorial, but using basic libraries and nw.js, and doing basic dom manipulations.

It had drag n drop, icons, and basic saving and loading. And I was satisfied.

Since then I've been working odd jobs.

And today I've decided to stretch out a bit, and build a basic airtable clone, because I think I can.
And also because I hate anything without an offline option.

First thing I realized was I wasn't about to duplicate all the features of a spreadsheet from scratch. I'd need a base to work from.

I spent about an hour looking.
Core features needed would be trivial serialization or saving/loading.

Proper event support for when a cell, row, or column changed, or was selected. Necessary for triggering validation and serialization/saving.

Custom column types.

Embedding html in cells.

Reorderable columns

Optional but nice to have:

Changeable column width and row height.

Drag and drop on rows and columns.

Right click menu support out of the box.

After that hour I had a few I wanted to test.

And started looking at frameworks to support the SPA aspects.

Both mithril and riot have minimal router support. But theres also a ton of other leightweight frameworks and libraries worthy of prototyping in, solid, marko, svelte, etc.
I didn't want to futz with lots of overhead, babeling/gulping/grunting/webpacking or any complex configuration-over-convention.

Didn't care for dom vs shadow dom. Its a prototype not a startup.

And I didn't care to do it the "right way". Learning curve here was antithesis to experimenting. I was trying to get away from plugin, configuration-over-convention, astronaut architecture, monolithic frameworks, the works.

Could I import the library without five dozen dependancies and learning four different tools before getting to hello world?
"But if you know IJK then its quick to get started!", except I don't, so it won't. I didn't want that.

Could I get cheap component-oriented designs?

Was I managing complex state embedded in a monolith that took over the entire layout and conventions of my code, like the world balanced on the back of a turtle?

Did it obscure the dom and state, and the standard way of doing things or *compliment* those?

As for validation, theres a number of vanilla libraries, one of which treats validation similar to unit testing, which seems kinda novel.

For presentation and backend I could do NW.JS, which would remove some of the complications, by putting everything in one script. Or if I wanted to make it a web backend, and avoid writing it in something that ran like a potato strapped to a nuclear rocket (visual studio), I could skip TS and go with python and quart, an async variation of flask.
This has the advantage that using something thats *not* JS, namely python, for interacting with a proper database, and would allow self-hosting or putting it online so people can share data and access in real time with others.

And because I'm horrible, and do things the wrong way for convenience, I could use tailwind.
Because it pisses people off.

How easy (or hard) would it be to recreate a basic functional clone of the core of airtable?

I don't know, but I have feeling I'm going to find out!

I took a few days off to move and when I came back, my manager had posted a message in chat about how horrible one of the naming conventions was (an implementation I made). One of my co-workers then defended it and defended something else I wrote that he was complaining about.

We had a 1:1 the day I got back and holy shit ... I did loose my cool and I'm not proud of it, but the guy went totally bat shit. He said I was the problem with them team, screaming about going off and writing rouge things, how he was my boss and I needed to do what he fucking told me to.

In my 20+ years in tech, I have never had to deal with a psycho. He served work release for assault and witness tampering last year and he told us a story that made it seem like it was his all his "crazy ex-girlfriend" who made trumped up charges. After that conversation, I doubt that's the case.

He's still under house arrest for something else until the end of May too. The entire team told me not to do any 1:1 calls with him and our project manager, who is really amazing, will probably be on any calls we need to do in the future.

I've also all confidence in him as a manager. Even when our PM tried to do a retro for the team, he still passively aggressively bitched about things that obviously related to my projects and the entire team could see it.

Short Story, !rant:

I'm a java dev looking into php and laravel to be able to contribute to webtrees, an online genealogy software.

Feels odd, because last time I had contact with PHP was 4.x.
But nice to see similar concepts, eg handlers instead of controllers, conventions, decent IDEs like phpStorm.

So, anyone interested in helping out?

- "Two months" training upon hire, with all the other hires too.
- Entire thing takes place in a hotel's larger room meant for small conventions or whatever.
- Brought on as Java developers, told there was Java work for all of us
- By the end of it, there wasn't
- Sit at our company's office for a month doing nothing, waiting for work
- It's summer time, 90F+ heat, and the A/C not only wasn't on most of the time, when it was on it was actually heating the building instead of cooling
- Get on a project, join the client site, takes at least a week to get a laptop, takes a month to get most of the needed accesses
- Was brought on because they needed a SQL Developer, I do not know more than basic syntax which I told them
- Project is 3 months behind already
- Really no development since Offshore handles it (poorly)
- For the first year+ of my time here I am doing nothing but manual quality assurance testing, and no development

It's hard to leave when you aren't learning

Let's talk about one of the two hard things in programming - what's your preferred test naming convention and why? I'll have to create plenty of those now, while the project I'm working on is still small, and I don't know which way to go. It's Spring (Java), but I don't think it matters that much 🤷

Constantly changing conventions for everything, like naming and code formatting conventions.
And the worst part is, I do this several times during one project.
Either I have a project with different conventions or I have to redo a lot.
Most of the time I try to do the last and this costs so much time -.-'

Freaking coding conventions...
Just chose something and stick to it.
How hard can it be?
Apparently this hard:
if(condition){
//SomeCode
}
else
//SomeCode

No matter how hard I try, I just cannot stop mixing CamelCase and snake_case variable names.

Nintendo seems to use familiar naming conventions like in programming.😅

It peeves me off when I see JavaScript written with C# style conventions and no ;